lxqt-session dumped core after upgrade to qt 5.15.10 about liblxqt HOT 8 CLOSED

Not reproducible with git LXQt and with the same version of qt5-base.

Keeping it open for now, in case someone wants to add more info...

from liblxqt.

Hmm - I updated the software on another machine, and had no problem starting LXQt. The machine with the problem is an older laptop with an Intel Core 2 Duo processor and Radeon graphics.

This seems tricky. I don't know whether to blame the compiler, the C libs, the Qt libs, LXQt, or some uninitialized pointer somewhere. Any suggestions about how to track the problem, looking at the stack trace?

from liblxqt.

See https://wiki.archlinux.org/title/Core_dump and https://wiki.archlinux.org/title/Debugging/Getting_traces. A stack trace with source filenames, line numbers and function arguments is better for diagnosis.

from liblxqt.

I've only just noticed that the problem with starting LXQt is directly related to interaction with SDDM, the Simple Desktop Display Manager. On the laptop machine, LXQt is started by sddm, and on the desktop machine, using startx. Starting LXQt on the laptop with startx works fine. I can poke-around more on this as time permits. Currently, I have sddm 0.20.0-1, a recent upgrade as of 2023-06-23. See: https://github.com/sddm/sddm/blob/develop/ChangeLog

from liblxqt.

... is directly related to interaction with SDDM.... Currently, I have sddm 0.20.0-1

It can't be about SDDM; I have its version 0.20.0-1 too.

Please attach a clean backtrace, as @yan12125 mentioned.

from liblxqt.

gdbTrace.txt

#0  0x00007f80e333ce05 in initFontUnlocked () at kernel/qguiapplication.cpp:249

from liblxqt.

It looks like a basic problem somewhere outside LXQt.

from liblxqt.

As we are using Qt6 now closing this.

from liblxqt.