<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Jul 26, 2020 at 12:42 PM Bill Meek <<a href="mailto:keemllib@gmail.com">keemllib@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 7/26/20 10:53 AM, DryHeat122 wrote:<br>
> <br>
> On Sat, Jul 25, 2020 at 1:11 PM Bill Meek <<a href="mailto:keemllib@gmail.com" target="_blank">keemllib@gmail.com</a> <mailto:<a href="mailto:keemllib@gmail.com" target="_blank">keemllib@gmail.com</a>>> wrote:<br>
> <br>
> On 7/25/20 2:58 PM, DryHeat122 wrote:<br>
> ><br>
> ><br>
> > On Sat, Jul 25, 2020 at 12:41 PM DryHeat122 <<a href="mailto:dryheat122@gmail.com" target="_blank">dryheat122@gmail.com</a> <mailto:<a href="mailto:dryheat122@gmail.com" target="_blank">dryheat122@gmail.com</a>> <mailto:<a href="mailto:dryheat122@gmail.com" target="_blank">dryheat122@gmail.com</a><br>
> <mailto:<a href="mailto:dryheat122@gmail.com" target="_blank">dryheat122@gmail.com</a>>>> wrote:<br>
> ><br>
> > On Sat, Jul 25, 2020 at 12:37 PM Bill Meek <<a href="mailto:keemllib@gmail.com" target="_blank">keemllib@gmail.com</a> <mailto:<a href="mailto:keemllib@gmail.com" target="_blank">keemllib@gmail.com</a>> <mailto:<a href="mailto:keemllib@gmail.com" target="_blank">keemllib@gmail.com</a><br>
> <mailto:<a href="mailto:keemllib@gmail.com" target="_blank">keemllib@gmail.com</a>>>> wrote:<br>
> ><br>
> > On 7/25/20 2:26 PM, DryHeat122 wrote:<br>
> > [snip]<br>
> ><br>
> > That's *perfect*, maybe. The entries in ~ and ~mythtv should be symbolic links to<br>
> > the one in /etc/mythtv. I'm asking because it's common for one of those links to<br>
> > be broken and be replaced by a file and I've never been able to find out why.<br>
> ><br>
> > This please:<br>
> ><br>
> > ls -ld /etc/mythtv/config.xml {~,~mythtv}/.mythtv/config.xml<br>
> ><br>
> ><br>
> > -rw-rw---- 1 mythtv mythtv 452 Jul 25 07:54 /etc/mythtv/config.xml<br>
> > lrwxrwxrwx 1 root root 22 Jul 25 07:54 /home/mythtv/.mythtv/config.xml -> /etc/mythtv/config.xml<br>
> > -rw-rw-r-- 1 steve steve 565 Jul 25 11:23 /home/steve/.mythtv/config.xml<br>
> ><br>
> > ...You know, I'm thinking the mistake I made was not installing the OS as user mythtv, and maybe I should just start over and do that.<br>
> <br>
> <br>
> I wouldn't start over. Note that /home/steve/.mythtv/config.xml is a file, not a<br>
> symbolic like like /home/mythtv/.mythtv/config.xml is. Also note that the two<br>
> files have different sizes. This *can* be OK as long as the DB credentials are<br>
> the same. This is where folks get in trouble. Common report is that the backend<br>
> runs OK, but the user can't start the frontend ('cause it connect to the DB.)<br>
> <br>
> I'd rm /home/steve/.mythtv/config.xml and link it to /etc/mythtv/config.xml<br>
> <br>
> ln -s /etc/mythtv/config.xml /home/steve/.mythtv/config.xml<br>
> <br>
> *Assuming the backend is running OK*, proving that the data in /etc/mythtv/config.xml<br>
> is correct.<br>
> <br>
> -- <br>
> Bill<br>
<br>
> Bill thanks for all the advice. I'm really grateful. I have started over just to get back to square one and undo anything I have screwed up. <br>
> I have two questions about xmltv I will post on the other thread. Re installation: Should I run everything--i.e. mythtv-setup, xmltv <br>
> config--as user mythtv rather than as user steve? I'm thinking the answer is yes and this is where I started developing problems before.<br>
<br>
mythtv-setup is always to be run as user mythtv, but in reality, it probably isn't. In the past, that meant that<br>
things like Storage Directories can't be read and the tests for them fail (if proper 'normal' permissions were<br>
used.)<br>
<br>
XMLTV adds a new reason for that. But I didn't use it, rather did the configuration from the command line.<br>
And in that case also ran it as user mythtv.<br>
<br>
Being practical, or perhaps lazy/forgetful, I added a line in my .bashrc so I can run mythfilldatabase<br>
without thinking too hard:<br>
<br>
alias mfdbrun='sudo --login --user=mythtv mythfilldatabase'<br>
<br>
<br>
-- <br>
Bill<br></blockquote><div><br></div><div>Here's my problem with trying to run mythtv-setup as user 'mythtv'. I just confirmed this on a fresh Ubuntu 20.04 system. When the Ubuntu system was installed the initial user was 'jim'. The mythtv install created the 'mythtv' user but it is not a normal login user so to run mythtv-setup as 'mythtv' I had to give user 'mythtv' a password. If I do that I have to logout and back in as user 'mythtv' and run mythtv-setup otherwise I get some xhost error. </div><div><br></div><div>When you exit. mythtv-setup, it asks to start the backend and if you say yes, it asks for a password which will not work with user 'mythtv' unless you've added mythtv to the sudo group.</div><div><br></div><div>To avoid all these issues, while user jim, I just sudo su mythtv and create the recordings directory with mkdir /home/mythtv/recordings and then it has the right permissions. While I'm there I set up XMLTV since I'm user mythtv. Once that's done I exit back to user jim and run mythtv-setup.</div><div><br></div><div>Never had a problem. However if I have to run mythfilldatabase manually, I sudo su mythtv and then run it.</div><div><br></div><div>JIm A</div><div><br></div></div></div>