Opened 9 years ago
Closed 8 years ago
Last modified 8 years ago
#12735 closed Bug Report - Crash (fixed)
Regression: MythFrontend fails when config.xml is not set up
Reported by: | Peter Bennett | Owned by: | stuartm |
---|---|---|---|
Priority: | blocker | Milestone: | 0.28.1 |
Component: | MythTV - General | Version: | 0.28.0 |
Severity: | high | Keywords: | |
Cc: | Ticket locked: | no |
Description
This worked in 0.27 but fails in 0.28.
If you start mythfrontend and either the config.xml does not exist, or the database server is down, the program prompts for Language and Country, then ends with a failure (sometimes segfault, sometimes just ends). In the case of a new remote frontend installation, a user will not know what to do.
In version 0.27 in these cases it would proceed to the prompt for database details, and after entering those, the frontend could start.
The user can work around this by either of the following methods:
- Copy the config.xml from the master backend to .mythtv directory in the remote frontend user home directory.
or
- Run mythtv-setup on the remote frontend. This prompts for database settings and creates the config.xml. The user must exit out of mythtv-setup after configuring those, and not go into any other setup options.
After doing one of these workarounds they can start the frontend.
Change History (7)
comment:1 Changed 9 years ago by
Milestone: | unknown → 0.28.1 |
---|---|
Priority: | minor → blocker |
Severity: | medium → high |
comment:2 Changed 9 years ago by
Owner: | set to stuartm |
---|---|
Status: | new → assigned |
comment:3 Changed 8 years ago by
Reporter: | changed from Peter Bennett <pgbennett@…> to Peter Bennett |
---|
I am thinking about taking a look at this, and improving the general frontend startup for when the database or backend are down. Currently if the database is down the user is prompted for country and language. This is not appropriate behavior. It should warn that the database is inaccessible and allow the user to wait for it to come up and allow the user to wait or exit. If the database is up and the backend is down it does just that, although it fills up the log with repeated error messages while retrying.
If you set up a database wake on lan string it behaves somewhat better if it can wake the database, although while it is waking the database the screen is blank.
Let me know if you would like me to take over this ticket, and make some startup improvement at the same time.
comment:4 Changed 8 years ago by
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
comment:5 follow-up: 7 Changed 8 years ago by
Peter,
One thought I had the other day, is to add support for Network Manager to the frontend, so it can leverage network manager to determine if the networking is online.
You can trigger the database selection screen on a frontend that start from SSD, as the frontend starts up before the network is ready, and therefore the database cannot be found.
Regards Stuart
Backtrace occurs when hitting save on the country/language selection screen