I have now narrowed this down to a sigsegv in Qt code called from here
in mythimage.cpp
bool MythImage::Load(const QString &filename)
{
if (filename.isEmpty())
return false;
QImage *im = NULL;
***** if (filename.startsWith("myth://")) ******
This is reproducible but the large number of threads running at this
time in the start up sequence (parallel loading of loads of theme
images), make hard to analyse exactly what is going on.
If anyone knows any easy ways of finding the actual data in QDataArrays
in GDB please let me know.
Roger
--
You received this bug notification because you are a member of UBUNTU -
AL - BR, which is subscribed to Mythbuntu.
https://bugs.launchpad.net/bugs/1635685
Title:
mythfrontend exits with status one before gui appears
Status in Mythbuntu:
New
Bug description:
Using mythbuntu 16.04 with mythfrontend configured to run via
.config/autostart when the gui desktop boots. Randomly mythfrontend
exits before any gui is displayed. Because the shell exit status is
one (process exit 0x100) the mythfrontend wrapper script does not try
to restart. This appears to be some kind of race condition in the
start up environment. Putting a 60 second sleep in the wrapper script
appears to cure it.
It appears that mythfrontend main.cpp is getting as far as launching
the housekeeper but is exiting before the gui is drawn by the message
loop.
Has anyone else seen this?
Roger
To manage notifications about this bug go to:
https://bugs.launchpad.net/mythbuntu/+bug/1635685/+subscriptions
--
Mailing list: https://launchpad.net/~linux-traipu
Post to : linux-traipu@lists.launchpad.net
Unsubscribe : https://launchpad.net/~linux-traipu
More help : https://help.launchpad.net/ListHelp
