SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** As title says plasma crash on startup. When launching through tty getting error about xcb plagin can not be loaded but has been found. Have tryed: 1. reinstalling plasma shell, plasma apps, framework anf qt 2. check db integrity via pacman 3. moving ~/.config dir away helped. plasma starts. but when moving back crashs again 4. tried deleting troll-something folder inside ~/.config dir (does not help) STEPS TO REPRODUCE don't know. This just have start happen from one of last boots OBSERVED RESULT Plasma crash on startup. If launched from sddm, apps from autostarts are opended full screen. Plasma interface does not come up. If launch from tty via startplasma-x11 gitting error about xcb plagin can not be loaded but has been found. EXPECTED RESULT Plasma starts as normal SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.23.x (available in About System) KDE Plasma Version: 5.23.x KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
Kde framework version: 5.89 Qt: 5.15.2
Created attachment 145674 [details] journalctl log
Can you please attach a *backtrace* of the crash? not a journalctl log, a backtrace. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Thanks!
(In reply to Nate Graham from comment #3) > Can you please attach a *backtrace* of the crash? not a journalctl log, a > backtrace. See > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports > > Thanks! Sure! I am following guide from arch wiki. But quiestion has occured: do I need to recompile qt itself with debugging symbols or only kde?
Depends on where the crash is. Usually just KDE stuff is enough.
(In reply to Nate Graham from comment #5) > Depends on where the crash is. Usually just KDE stuff is enough. So if the plasma itself crashes on startup, what packages should i rebuild with debug symbols?
Created attachment 145734 [details] kded5 backtrace i recompiled plasma-workspace package which provides plasmashell and startplasma-x11. Here is the result
Created attachment 145735 [details] other available backtraces
We need a backtrace from plasmashell, not kded5 (that crash should be reported separately, in another bug report). To do this, you run `coredumpctl gdb <PID of crashing process>`, which in this case looks to be 5364. So you would run `coredumpctl gdb 5364`, then when it shows you a prompt, type "bt" and the return key and it will display the backtrace. Copy and paste that hete.
Created attachment 145873 [details] trace of most recent plasmashell crash Wierd thing: plasma does not crash anymore (or does not report about that at least) but i still getting black desktop with autostarting apps but without plasmashell. journalctl reports that kded5 crashes, but does not talking anything about plasmashell itself except a couple of warnings. Also no new coredumps for plasmashell can be found in coredumpctl.
Things getting more wierd: plasmashell does not crash anymore. I still gets Black destoo when loggin via sddm. But i can succesfully load plasma when starting manually from termunal like startx .xinitrc kde. Note: i am using fish shell. May that somehow affect?
Now plasmashell report such message: starting invalid corona org.kde.plasma.desktop There are enumerouse warnings from theme installed about properties that cant be resolved
(In reply to owl-from-hogvarts from comment #10) > Created attachment 145873 [details] > trace of most recent plasmashell crash > > Wierd thing: plasma does not crash anymore (or does not report about that at > least) but i still getting black desktop with autostarting apps but without > plasmashell. journalctl reports that kded5 crashes, but does not talking > anything about plasmashell itself except a couple of warnings. Also no new > coredumps for plasmashell can be found in coredumpctl. Ops... I guess this coredump describes "crash" if i manually executes plasmashell from tty (which will not work, since xorg is not initialized well). So plasmashell is not actully crashing. But kded5 does. My guess that namely kded5 cause black desktop with cursor.
Created attachment 145881 [details] kded5 trace
#9 0x00007fe6bb349024 in () at /usr/lib/qt/plugins/kf5/kded/gtkconfig.so #10 0x00007fe6bb34ae5f in GtkConfig::setFont() const () at /usr/lib/qt/plugins/kf5/kded/gtkconfig.so #11 0x00007fe6bb35617e in GtkConfig::applyAllSettings() const () at /usr/lib/qt/plugins/kf5/kded/gtkconfig.so #12 0x00007fe6bb356891 in GtkConfig::GtkConfig(QObject*, QList<QVariant> const&) () at /usr/lib/qt/plugins/kf5/kded/gtkconfig.so #13 0x00007fe6bb356a91 in () at /usr/lib/qt/plugins/kf5/kded/gtkconfig.so
There is no info in the backtrace where exactly in `setFont` kded5 crashes, but here is my best guess: https://invent.kde.org/plasma/kde-gtk-config/-/blob/master/kded/configeditor.cpp#L46 No idea why, though. It's something on GTK side.
I guess the problem comes somewhere from configs inside "~/.config" because removing this dir completely solves the issue
Found what caused the problem. I have switched my default shell to "fish" by accident. So it not picked up some environment variables. Switching back to bash resolved issue. Thank you very much for help)