LyX ⇒ Lyx crashes on opening "shut down" dialog in gnome 3

[jossojjos]

Hello,

I'm using Lyx 2.1.1 on a CentOS 7 machine running Gnome version 3.8.4.
Each time I open the "shut down" or "power off" dialog in gnome, lyx immediately crashes. (FYI : choosing "shut down" allows to suspend the machine ; I'm not complaining about the fact that lyx crashes when I actually shut down ).
I've disabled all installed gnome shell extensions, and this still happens ...

So how to find out if this is a lyx or a gnome problem ? I suppose it's a lyx problem, since none of the other applications I use has this behaviour.

If you have some ideas about how to diagnose this problem more precisely, let me know.

Thanks,
Jos

[scottkosty]

Can you provide a backtrace? That's the only way we can get an idea of what's going on. As to whether it's a LyX or GNOME issue, my guess is that it's a Qt issue.

[jossojjos]

Backtrace ? Ah yes, of course, with gdb, why didn't I think of that before ?!

Well, it seems it's not a crash :

Code: Select all

(gdb) run
Starting program: /usr/bin/lyx 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Detaching after fork from child process 5400.
Detaching after fork from child process 5402.
Detaching after fork from child process 5403.
[Inferior 1 (process 5396) exited normally]
(gdb)

(Once lyx was running, I chose "shut down" in the gnome menu)

So upon choosing the gnome "shut down" dialog, gnome sends some signal to programs which lyx (or Qt) interprets as "quit" ?

But hey, I can't restart lyx in gdb again :

Code: Select all

(gdb) run
Starting program: /usr/bin/lyx 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
ICE default IO error handler doing an exit(), pid = 5427, errno = 0
[Inferior 1 (process 5427) exited with code 01]
(gdb)

What's that ?
I guess I'll have to dig up my gdb cheat sheet to see if there are other ways to get a clue about this, because there is no stack to backtrace ...

Jos

[jossojjos]

And I can't get the gnome's "shut down" dialog anymore, clicking "shut down" does not produce a visible effect.
Maybe I should contact the gnome people ...

[scottkosty]

Thanks for the extra information josso. I'm not sure what's going on here. The GNOME people might have an idea. It sounds like (still conjecture on my part) either GNOME is incorrectly sending a SIGKILL or SIGTERM to LyX; or LyX (or Qt) is misinterpreting a different signal as one of those two.

[scottkosty]

Please let us know if you find more information from the GNOME people or make any other discoveries.

[jossojjos]

There does not seem to be a forum for discussing gnome issues ... is the "GNOME Bugzilla" seems the only option ? All I want to do for now, is just to diagnose the problem ...

[scottkosty]

There does not seem to be a forum for discussing gnome issues ... is the "GNOME Bugzilla" seems the only option ? All I want to do for now, is just to diagnose the problem ...

I have no idea. Maybe look for a mailing list or IRC channel.

[jossojjos]

It seems that you're right, it's probably a Qt-related problem, or at least related to the GNOME - Qt interface.
The Qt-based applications on my computer (LyX, skype, vlc) all show the same behaviour. I opened a topic on the Qt forum : https://qt-project.org/forums/viewthread/47632/
I guess I'll have to wait and see what happens, as this is beyond my skills.

[scottkosty]

I took a quick look at the replies. It seems you've found the right place. Thanks for following through and being persistent in finding what component is responsible! Hopefully you can find the right people and leave it in their hands to fix.