mythbuntu-bugs team mailing list archive
-
mythbuntu-bugs team
-
Mailing list archive
-
Message #09354
[Bug 1083392] Re: Mythtv frontend launch script is causing bad user experience.
We really do appreciate you opening this ticket to help improve
Mythbuntu, but it needs to be closed for a number of reasons. The
biggest one is that upstream has moved on to a new version and believes
this to be fixed. Could you please verify if this issue still exists in
the latest version?
Please do not let the closing of this ticket dissuade you from opening a
new ticket if this (or any other) problem occurs with the newer
versions.
** Changed in: mythbuntu
Status: New => Expired
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to Mythbuntu.
https://bugs.launchpad.net/bugs/1083392
Title:
Mythtv frontend launch script is causing bad user experience.
Status in Mythbuntu, Ubuntu derivative focused upon MythTV:
Expired
Status in mythtv package in Ubuntu:
Invalid
Bug description:
in several scenario's the launch scripts is causing bad user experience.
With bad user experience I mean that the script causing and endless restart of the frontend. Less experience users get frustrated by this behaviour.
some examples that force the endless looping of restarting mythtv
frontend.
- a double click on the icon on mythtv frontend.
- starting mythtv frontend when another user on the computer already has mythtv frontend running.
- launching the frontend when the backend server is not available.
In general I think there should be two scripts provided to the user to
launch mythtv frontend. One script to run mythtv on a 'tv' that has
some logic to restart the frontend when it crashes; a second script to
launch mythtv on a 'regular' computer. Here the auto restart is of no
use. A user on a regular computer can easily restart the fronend
himself. At least more easy then stopping a looping restart of the
frontend.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mythbuntu/+bug/1083392/+subscriptions
References