MythTV Backend Configuration Application shows Terminal Screen instead of Graphical User Interface

This is an excellent tool for reporting bugs. I found out about it on U-Tube. I could not find it when looking on the Ubuntu site. It is possible it is somewhere there but I couldn't find it which suggests I may have been unlucky or that it is difficult to find.
I would suggest you emphasise to newbies the existence of this bug reporting tool and refer them either to the U-Tube video or a video you have prepared on the Ubuntu site.

I am very appreciative of your efforts and hope I have been helpful. If you need any further assistance, please let me know and I will do whatever I can.

I view MythTV as being a very important tool for introducing everyday users to the wonders of Open Source Software and Ubuntu. At present I am trying to put together a demonstration notebook PC for the Campervan and Motorhome Club of Australia; an organisation with 60,000 members. I feel their membership would benefit greatly from what Ubuntu and Open Source Software, generally, have to offer.

Thanks again.

Status changed to 'Confirmed' because the bug affects multiple users.

I can reproduce this by booting the 12.10 amd64 LiveCD on my system, installing the mythtv package and trying to run mythtv-setup. I will be re-installing 12.04 and not "upgrading" to newer releases until this is fixed.

I also can confirm this bug, I'm using Ubuntu 12.10 and MythTV 2.6 fully upgraded and instead of loading a gui it hangs at a terminal window and I eventually it crashes and says

The problem cannot be reported:

You have some obsolete package versions installed. Please upgrade the following packages and check if the problem still occurs:

libssl1.0.0, openssl

...I was doing that as I typed that, and it totally fixes the problem use these terminal lines below to fix the problem.

sudo apt-get install libssl1.0.0

sudo apt-get install openssl

Ok, so the backend did load after doing that, but I didn't have a chance to setup my tv at the time, I booted the computer today and I have the same problem. I'm going to let the backend run until it crashes and try it again, maybe that's the trick.

I also ran the backend from the terminal at one point using "mythbackend" in a terminal window, maybe that had something to do with it. I deffinetly have this problem too and got it to work somehow yesterday but apparently I blew my opportunity to set it up and it's still not working right.

OK, I got it to work again, make sure the mythtv backend setup is closed, open a terminal window, run "mythbackend" and wait until you see that "Running housekeeping thread" is done and hit CTRL+C to close the backend again, then for some reason, loading the gui version of the backend setup works after this for me. (you might have to update libssl and openssl if you didn't already)

Dear All

Not sure if I am breaking protocol by writing to you in this manner so
please excuse me if I am and disregard this correspondence.

I found that my problems ceased when I firstly installed 12.04 and then
installed 12.10. (This week, I plan to work with another colleague
installing 12.10 from on a "blank" machine and then compiling from
source MythTV on that machine to see if a number of other problems I am
experiencing go away.

Related to that, have you, when you have your MythTV running experienced
problems with scheduled programs disappearing from the schedule if they
are set to "Record this show each week"? Some scheduled programs
"stick". Others have to be reset just before a screening for the
recording to take place. Next week, they are gone again! I haven't as
yet reported it as a bug because it may be that I have just not
configured MythTV setup properly.

As a final point, something that may be helpful to other enthusiasts, I
have discovered there is a fault in the start up script with MythTV in
that it checks to see if the network interface is up. If it is not,
MythTV fails to start. So if you, as I did, disconnect your notebook
from the wall or WiFi and take it to seminar to demonstrate the virtues
and value of Open Source Software, it won't work. (Luckily I had
plenty of other material to demonstrate!) Correcting the "If then else"
clause in the script fixes the problem.

Hope this is helpful.

Kevin Loughrey CPEng
Owner

-----Original Message-----
From: Mike Johnston <email address hidden>
Reply-to: Bug 1077536 <email address hidden>
To: <email address hidden>
Subject: [Bug 1077536] Re: MythTV Backend Configuration Application
shows Terminal Screen instead of Graphical User Interface
Date: Sat, 23 Feb 2013 14:24:03 -0000

Ok, so the backend did load after doing that, but I didn't have a chance
to setup my tv at the time, I booted the computer today and I have the
same problem. I'm going to let the backend run until it crashes and try
it again, maybe that's the trick.

That isn't a bug in the upstart script, that is by design. Most MythTV
installations have a network connection, which is why we wait for
networking to start before starting the backend. You can easily remove that
part of the startup script if you want.

Thanks,

Thomas Mashos

On Sat, Feb 23, 2013 at 12:44 PM, Kevin Loughrey <email address hidden>wrote:

> Dear All
>
> Not sure if I am breaking protocol by writing to you in this manner so
> please excuse me if I am and disregard this correspondence.
>
> I found that my problems ceased when I firstly installed 12.04 and then
> installed 12.10. (This week, I plan to work with another colleague
> installing 12.10 from on a "blank" machine and then compiling from
> source MythTV on that machine to see if a number of other problems I am
> experiencing go away.
>
> Related to that, have you, when you have your MythTV running experienced
> problems with scheduled programs disappearing from the schedule if they
> are set to "Record this show each week"? Some scheduled programs
> "stick". Others have to be reset just before a screening for the
> recording to take place. Next week, they are gone again! I haven't as
> yet reported it as a bug because it may be that I have just not
> configured MythTV setup properly.
>
> As a final point, something that may be helpful to other enthusiasts, I
> have discovered there is a fault in the start up script with MythTV in
> that it checks to see if the network interface is up. If it is not,
> MythTV fails to start. So if you, as I did, disconnect your notebook
> from the wall or WiFi and take it to seminar to demonstrate the virtues
> and value of Open Source Software, it won't work. (Luckily I had
> plenty of other material to demonstrate!) Correcting the "If then else"
> clause in the script fixes the problem.
>
> Hope this is helpful.
>
> Kevin Loughrey CPEng
> Owner
>
> -----Original Message-----
> From: Mike Johnston <email address hidden>
> Reply-to: Bug 1077536 <email address hidden>
> To: <email address hidden>
> Subject: [Bug 1077536] Re: MythTV Backend Configuration Application
> shows Terminal Screen instead of Graphical User Interface
> Date: Sat, 23 Feb 2013 14:24:03 -0000
>
>
> Ok, so the backend did load after doing that, but I didn't have a chance
> to setup my tv at the time, I booted the computer today and I have the
> same problem. I'm going to let the backend run until it crashes and try
> it again, maybe that's the trick.
>
>
>
> ** Attachment added: "NVTECH EMAIL BANNERHEAD 800X139.jpg"
>
> https://bugs.launchpad.net/bugs/1077536/+attachment/3543756/+files/NVTECH%20EMAIL%20BANNERHEAD%20800X139.jpg
>
> --
> You received this bug notification because you are a member of Mythbuntu
> Bug Team, which is subscribed to mythtv in Ubuntu.
> https://bugs.launchpad.net/bugs/1077536
>
> Title:
> MythTV Backend Configuration Application shows Terminal Screen instead
> of Graphical User Interface
>
> Status in “mythtv” package in Ubuntu:
> Confirmed
>
> Bug description:
> This bug relates to:
> 1. Description: Ubuntu 12.10 Release: 12.10
> 2. Installing a combined MythTV frontend and backend on the same PC.
> mythtv:
> ...

Dear Thomas

Thank you for your speedy reply. It is much appreciated.

I have searched the Internet and MythTV documentation and can't find
this feature documented. I also can't find any documentation that would
instruct a "newbie" how to disable this "feature".

As much as I can determine, this is a new feature as earlier versions of
MythTV (which I have demonstrated in circumstances where a network
connection was not available), where the backend and frontend were on
the same machine, did not require a network connection in order to
operate.

I suggest therefore that the team review this decision and that this
criteria be abolished or at least that the requirement the network IF be
up not be the default condition. In the main, newbies will use an
all-in-one configuration, ie, the backend and frontend on the same
machine. There is no need therefore for this machine to be on a network
except if the user wished to either upgrade the system or use net-based
TV. Persons who use a separate machine for a backend are on a high
plane of expertise and so would/should be capable of working out how to
configure a script such that the network has to be present for MythTV to
function in those circumstances.

I'd be grateful to hear the opinions of others on this matter. Possibly
there is something that I do not understand. (I hope by raising this I
am not distracting people from more important matters.)

Once again thank you.

Kevin Loughrey CPEng
Owner

-----Original Message-----
From: Thomas Mashos <email address hidden>
Reply-to: Bug 1077536 <email address hidden>
To: <email address hidden>
Subject: Re: [Mythbuntu-bugs] [Bug 1077536] Re: MythTV Backend
Configuration Application shows Terminal Screen instead of Graphical
User Interface
Date: Sat, 23 Feb 2013 20:59:25 -0000

That isn't a bug in the upstart script, that is by design. Most MythTV
installations have a network connection, which is why we wait for
networking to start before starting the backend. You can easily remove that
part of the startup script if you want.

Thanks,

Thomas Mashos

On Sat, Feb 23, 2013 at 12:44 PM, Kevin Loughrey <email address hidden>wrote:

> Dear All
>
> Not sure if I am breaking protocol by writing to you in this manner so
> please excuse me if I am and disregard this correspondence.
>
> I found that my problems ceased when I firstly installed 12.04 and then
> installed 12.10. (This week, I plan to work with another colleague
> installing 12.10 from on a "blank" machine and then compiling from
> source MythTV on that machine to see if a number of other problems I am
> experiencing go away.
>
> Related to that, have you, when you have your MythTV running experienced
> problems with scheduled programs disappearing from the schedule if they
> are set to "Record this show each week"? Some scheduled programs
> "stick". Others have to be reset just before a screening for the
> recording to take place. Next week, they are gone again! I haven't as
> yet reported it as a bug because it may be that I have just not
> configured MythTV setup properly.
>
> As a final point, something that may be helpful to other enthusiasts, I
> have discovered there i...

Kevin,

The backend starts when any network interface that isn't lo is up (and the other conditions are met). This accounts for most user situations. We've made the decision to wait for networking to start because systems are becoming fast enough that they would finish starting before any networking was up, causing the backend to not listen on any external interface.

You mention that people with more than one system are more experienced people. I disagree. With the number of devices in people's homes (tablets/phones/computers), it is more likely that someone will want to attach use one of these devices to access their MythTV system in some way (eg. third party frontend, remote control, etc). I don't believe that most of the new users you talk about would take their systems off network in order to watch tv. Most of those cases would be laptops, and those shouldn't be MythTV backends unless they are used for demonstration purposes (and IMO, anybody doing a MythTV demonstration should be one of the more experienced users you talk about and thus able to edit the upstart file). Now for those more experienced users, that have a system that needs to be off network (eg. they are giving a demonstration, they never put their system on a network), there is an easy way to configure what you are asking for (eg. removing the net-device-up requirement). Any changes made to this file don't get overwritten by the packaging.

Now I'm more than willing to keep discussing this with you, but I can't think of a reason that we would change this. There are simply more reasons to keep it than revert the change. If you can give some solid reasons why we should revert the change and ignore all the users that needed that in the first place (there were a not insignificant amount of users that were having issues with the backend starting before networking), I'll certainly entertain the idea.

Thanks,

Thomas Mashos

Dear Thomas

Thank you very much for taking so much time to give me such a detailed
account as to why you have decided to take the steps you have. I
understand entirely.

I am very grateful. As a final point, might I suggest we modify the
script such that it tells the user, "This computer does not appear to be
connected to a network." [new line] "Would you still like to start
MythTV?"

If we were to do that, it would give the system enough time to sort
things out such that the backend database was connected and MythTV was
ready to function properly. It would also provide the user with:
1. An explanation as to why MythTV had not started.
2. The opportunity to connect a network cable or examine why the
network was down and would allow them, if they wanted, to use MythTV
without a network connection being present. If you need any help with
this, my engineer-associates, who are much more learned than I, might be
able to supply you with the script.

If it would not be too much trouble could you give me some hints as to
what I should explore to determine why MythTV seems to be unreliable in
its scheduling? I have found that one can set the schedule to: "Record
in this Timeslot Every Week" , and then go back sometime later and find
that this has disappeared. I am reticent to declare this a bug because
it could just be that I have not properly configured either the front or
backend.... As the Americans say, "My Bad!"

I have tried a number of things to get to the bottom of this. For
example, I have exited out of the front end and then come back in to
check if the schedule was still green. It usually is. I have shut down
the PC and then restarted it. I find that the scheduled item is there
when I return.

But at some later time, for some unknown reason, it often disappears.
As a further clue, some schedulings remain, as they should, set
"forever".

Once again thank you very much. I really do appreciate your giving me
your time and advice as you have.

Warm regards

Kevin Loughrey CPEng
Owner

-----Original Message-----
From: Thomas Mashos <email address hidden>
Reply-to: Bug 1077536 <email address hidden>
To: <email address hidden>
Subject: [Bug 1077536] Re: MythTV Backend Configuration Application
shows Terminal Screen instead of Graphical User Interface
Date: Mon, 25 Feb 2013 23:00:41 -0000

Kevin,

The backend starts when any network interface that isn't lo is up (and
the other conditions are met). This accounts for most user situations.
We've made the decision to wait for networking to start because systems
are becoming fast enough that they would finish starting before any
networking was up, causing the backend to not listen on any external
interface.

You mention that people with more than one system are more experienced
people. I disagree. With the number of devices in people's homes
(tablets/phones/computers), it is more likely that someone will want to
attach use one of these devices to access their MythTV system in some
way (eg. third party frontend, remote control, etc). I don't believe
that most of the new users you talk about would take their systems off
network in order to watch tv. Most of those cases w...

Had the same problem after a reinstall, but this old solution did not work. I found an answer somewhere else though, I just used "sudo mythtv-setup" and it had to add the sudo user to mythtv's users and had me logout and login, then i ran "sudo mythtv-setup" again and it loaded up that time