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 <1077...@bugs.launchpad.net>
Reply-to: Bug 1077536 <1077...@bugs.launchpad.net>
To: kev...@nvtech.com.au
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 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



** Attachment added: "NVTECH EMAIL BANNERHEAD 800X139.jpg"
   
https://bugs.launchpad.net/bugs/1077536/+attachment/3546980/+files/NVTECH%20EMAIL%20BANNERHEAD%20800X139.jpg

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1077536

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mythtv/+bug/1077536/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to