lyricue_display Segmentation fault when Ubuntu boots without network connection

Bug #1749182 reported by Matthias de Schepper
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lyricue
New
Undecided
Unassigned

Bug Description

I noticed a bug with Ubuntu 14.04 and lyricue 4.0.12 or 4.0.13.

When the computer boots without a network connection and I start lyricue, this works. When I start lyricue_display it fails, the complete display as well as the miniview.

When I start lyricue from the terminal with lyricue -d, it throws a segmentation fault. Running lyricue_display -d from the terminal shows te same and terminates. The connection with the mysql server on the local machine is OK, I can select all songs...
In attachment the logs of lyricue 4.0.12 on our main computer with and without network connection.

When I connect the computer to the network everything starts working fine. If I disconnect it afterwards everything is still working, even after a lyricue restart. So the bug is only valid at boot up without network. I checked ifconfig (see attachment, everyting in ifconfig seems normal but maybe lyricue_display is dependent on som system files for network status...)

Still, this makes lyricue kind of unreliable. I have a second backup computer (laptop with Ubuntu 14.04 and latest lyricue 4.0.13) which is not connected to the network. If anything would fail, people can just boot this computer and switch the beamer input. I prefer to keep these backup instructions simple. If I have to instruct people to connect to the network first... this makes the backup procedure less straightforward.
Moreover I use a second computer to have a backup, but if I am dependent on the network router we still have a single point of failure.

In the past there was a similar bug I have reported (reported on e-mail in the lds-users group on 28-07-2014)

Actually it should be a quite recent bug/regression as I am only using a network since 08-2017.

Thank you foor having a look at this.

Kind regards,
Matthias

Revision history for this message
Matthias de Schepper (matthias-deschepper) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.