Bug 458852 - Plasmashell crashes on KDE desktop start in X11 and cannot be fixed
Summary: Plasmashell crashes on KDE desktop start in X11 and cannot be fixed
Status: RESOLVED DUPLICATE of bug 420245
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (show other bugs)
Version: 5.24.6
Platform: Neon Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2022-09-07 22:10 UTC by Peter
Modified: 2022-09-19 21:17 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Apport Retrace GDB of plasmashell crash report (4.86 KB, text/plain)
2022-09-11 21:38 UTC, Peter
Details
New crash information added by DrKonqi (16.69 KB, text/plain)
2022-09-17 14:34 UTC, Robert S.
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Peter 2022-09-07 22:10:35 UTC
Application: plasmashell (5.24.6)

Qt Version: 5.15.3
Frameworks Version: 5.92.0
Operating System: Linux 5.15.0-47-generic x86_64
Windowing System: X11
Distribution: Ubuntu 22.04.1 LTS
DrKonqi: 5.24.5 [KCrashBackend]

-- Information about the crash:
Please note:  I'd be willing to try to recreate the bug with debug symbols, but I just cannot find the debug packages for the list of files mentioned by this crash handler.

- What I was doing when the application crashed:
Just before the crash recorded here, I was using Gnome, switched user, and tried to start KDE desktop.  It comes up and opens applications, but the background is black and the panels are missing.  More generally, after a system reboot a couple days ago, every time I go into KDE I see what I'm seeing now--no panels, black background.  I don't typically get asked to do a bug report.

- Unusual behavior I noticed:
I upgraded to 22.04 a couple weeks ago from 20.04, where I had no problems with KDE panels.  In 22.04, I noticed the panels were unstable.  They and the background would disappear after suspend or sometimes while I was using the desktop.  I used 'kstart5 plasmashell' to resume the panels and background, which worked.  I am using X11.

But a few days ago, I rebooted to find that the panels and background were missing, which had not happened before.  When I tried to use variations of 'kquitapp5 plasmashell && kstart5 plasmashell' to activate the panels and background to no effect.  Multiple reboots made no difference.  I reinstalled all the software related to plasma I could find, also to no effect.  

I did upgrade a couple packages before the reboot after which KDE stopped functioning properly.  I could be wrong, but I think those packages were:  kde-config-sddm and bluedevil.

- Custom settings of the application:
I moved the panels around, resized them, and added a few widgets (weather widget, widget to show all open windows, widget to minimize all).  Besides the weather widget, I don't think I'm using anything besides what I normally have for years.  The weather widget worked for a number of days before my KDE stopped functioning properly.

The crash can be reproduced every time.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault

[KCrash Handler]
#4  0x00007f3ba65b2074 in Plasma::Applet::immutability() const () from /lib/x86_64-linux-gnu/libKF5Plasma.so.5
#5  0x00007f3ba65b214d in Plasma::Applet::destroy() () from /lib/x86_64-linux-gnu/libKF5Plasma.so.5
#6  0x00007f3b9cc2df29 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/applets/org.kde.plasma.systemtray.so
#7  0x00007f3b9cc2df4d in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/applets/org.kde.plasma.systemtray.so
#8  0x00007f3ba4605a5e in QObjectPrivate::deleteChildren() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x00007f3ba4610914 in QObject::~QObject() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x00007f3ba65b6c7d in Plasma::Containment::~Containment() () from /lib/x86_64-linux-gnu/libKF5Plasma.so.5
#11 0x00007f3ba46081b3 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x00007f3ba52c8713 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#13 0x00007f3ba45dae2a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x00007f3ba45ddf17 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x00007f3ba4634a57 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x00007f3ba29acd1b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#17 0x00007f3ba2a016f8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x00007f3ba29aa3c3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007f3ba46340a8 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x00007f3ba45d974b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x00007f3ba45e1ce4 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x000055a0bb27adce in ?? ()
#23 0x00007f3ba3ef6d90 in __libc_start_call_main (main=main@entry=0x55a0bb279f70, argc=argc@entry=1, argv=argv@entry=0x7ffe7c6850f8) at ../sysdeps/nptl/libc_start_call_main.h:58
#24 0x00007f3ba3ef6e40 in __libc_start_main_impl (main=0x55a0bb279f70, argc=1, argv=0x7ffe7c6850f8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffe7c6850e8) at ../csu/libc-start.c:392
#25 0x000055a0bb27aef5 in ?? ()
[Inferior 1 (process 8436) detached]

Possible duplicates by query: bug 458503, bug 458367, bug 457069, bug 456040, bug 456037.

Reported using DrKonqi
Comment 1 Peter 2022-09-08 14:20:41 UTC
Just remembered something I should mention.  I tried going to the earlier version of my kernel at startup (so 5.15.0-46-generic rather than 5.15.0-47-generic).  I did not have these problems when I was running 5.15.0-46-generic.  However, this had zero effect on the problem.
Comment 2 Nate Graham 2022-09-09 04:29:43 UTC
Thank you for the bug report! Unfortunately the backtrace is incomplete and missing debug symbols for the following lines that we need to figure out exactly what's going wrong:

> #6  0x00007f3b9cc2df29 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/applets/org.kde.plasma.systemtray.so
> #7  0x00007f3b9cc2df4d in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/applets/org.kde.plasma.systemtray.so

I don't know exactly what the debug symbol package name for plasma-workspace is on Ubuntu, so you may have to ask in an Ubuntu-specific venue about that.
Comment 3 Peter 2022-09-09 14:10:26 UTC
(In reply to Nate Graham from comment #2)
> Thank you for the bug report! Unfortunately the backtrace is incomplete and
> missing debug symbols for the following lines that we need to figure out
> exactly what's going wrong:
> 
> > #6  0x00007f3b9cc2df29 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/applets/org.kde.plasma.systemtray.so
> > #7  0x00007f3b9cc2df4d in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/applets/org.kde.plasma.systemtray.so
> 
> I don't know exactly what the debug symbol package name for plasma-workspace
> is on Ubuntu, so you may have to ask in an Ubuntu-specific venue about that.

I've installed debug symbols for all the libraries the crash report mentions.  Problem now is that whenever I go into KDE, no crash report is triggered, even though the panels and background fail to appear.  Tried a few times already.  I accessed KDE many times before the currently reported crash report was generated.  I don't suppose there is some to encourage it to report?
Comment 4 Peter 2022-09-11 21:38:51 UTC
Created attachment 151994 [details]
Apport Retrace GDB of plasmashell crash report

I do not know if I did this in a useful way (e.g., I ran from my working desktop Gnome), but I installed apport-retrace and ran it against the plasmashell crash report that is the basis of this KDE bug report, with debug symbols in place.  Please find that enclosed.  Beyond this, I probably won't be of much help because I need a working KDE system and am about to wipe and reinstall my computer.
Comment 5 Nate Graham 2022-09-11 23:49:55 UTC
There we go, thanks!

Pasting inline for searchability:

(gdb) bt
#0  __pthread_kill_implementation (no_tid=0, signo=11, threadid=139894059489728) at ./nptl/pthread_kill.c:44
#1  __pthread_kill_internal (signo=11, threadid=139894059489728) at ./nptl/pthread_kill.c:78
#2  __GI___pthread_kill (threadid=139894059489728, signo=signo@entry=11) at ./nptl/pthread_kill.c:89
#3  0x00007f3ba3f0f476 in __GI_raise (sig=11) at ../sysdeps/posix/raise.c:26
#4  0x00007f3ba643557c in KCrash::defaultCrashHandler(int) () from /lib/x86_64-linux-gnu/libKF5Crash.so.5
#5  <signal handler called>
#6  Plasma::Applet::immutability (this=0x0) at ./src/plasma/applet.cpp:493
#7  0x00007f3ba65b214d in Plasma::Applet::destroy (this=0x0) at ./src/plasma/applet.cpp:303
#8  0x00007f3b9cc2df29 in SystemTrayContainer::~SystemTrayContainer (this=0x55a0bcba9f30, __in_chrg=<optimized out>)
    at ./applets/systemtray/container/systemtraycontainer.cpp:24
#9  0x00007f3b9cc2df4d in SystemTrayContainer::~SystemTrayContainer (this=0x55a0bcba9f30, __in_chrg=<optimized out>)
    at ./applets/systemtray/container/systemtraycontainer.cpp:26
#10 0x00007f3ba4605a5e in QObjectPrivate::deleteChildren (this=0x55a0bcb58050) at kernel/qobject.cpp:2104
#11 0x00007f3ba4610914 in QObject::~QObject (this=<optimized out>, __in_chrg=<optimized out>) at kernel/qobject.cpp:1082
#12 0x00007f3ba65b6c7d in Plasma::Containment::~Containment (this=0x55a0bcb583d0, __in_chrg=<optimized out>)
    at ./src/plasma/containment.cpp:83
#13 0x00007f3ba46081b3 in QObject::event (this=0x55a0bcb583d0, e=0x55a0bcc3c120) at kernel/qobject.cpp:1301
#14 0x00007f3ba52c8713 in QApplicationPrivate::notify_helper (this=<optimized out>, receiver=0x55a0bcb583d0, e=0x55a0bcc3c120)
    at kernel/qapplication.cpp:3637
#15 0x00007f3ba45dae2a in QCoreApplication::notifyInternal2 (receiver=0x55a0bcb583d0, event=0x55a0bcc3c120)
    at kernel/qcoreapplication.cpp:1064
#16 0x00007f3ba45ddf17 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x55a0bc58aec0)
    at kernel/qcoreapplication.cpp:1821
#17 0x00007f3ba4634a57 in postEventSourceDispatch (s=0x55a0bc672c50) at kernel/qeventdispatcher_glib.cpp:277
#18 0x00007f3ba29acd1b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007f3ba2a016f8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007f3ba29aa3c3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007f3ba46340a8 in QEventDispatcherGlib::processEvents (this=0x55a0bc673270, flags=...)
    at kernel/qeventdispatcher_glib.cpp:423
#22 0x00007f3ba45d974b in QEventLoop::exec (this=this@entry=0x7ffe7c684e40, flags=..., flags@entry=...)
    at ../../include/QtCore/../../src/corelib/global/qflags.h:69
#23 0x00007f3ba45e1ce4 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121
#24 0x000055a0bb27adce in main (argc=<optimized out>, argv=<optimized out>) at ./shell/main.cpp:238
(gdb) using
Comment 6 Nate Graham 2022-09-12 00:00:40 UTC

*** This bug has been marked as a duplicate of bug 420245 ***
Comment 7 Robert S. 2022-09-17 14:34:14 UTC
Created attachment 152156 [details]
New crash information added by DrKonqi

plasmashell (5.25.5) using Qt 5.15.6

I restarted my computer after installing about 5.5GiB of updates only to see a blank screen with a mouse cursor. I rebooted and got the same result again, so I did ctrl alt F2, logged in and started X only to be met by error message dialogues and my plasma shell not starting. I opened my terminal and tried kstart5, however that ended up having the same behaviour. Apologies if I am missing some debug symbols - not every one could be installed it seems.

-- Backtrace (Reduced):
#4  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#5  0x00007f52ab4a2859 in __GI_abort () at abort.c:79
#6  0x00007f52ab8e6bd9 in qt_message_fatal (context=..., message=<synthetic pointer>...) at global/qlogging.cpp:1914
#7  QMessageLogger::fatal(char const*, ...) const (this=this@entry=0x7fffff1caeb0, msg=msg@entry=0x7f52abcda448 "Cannot mix incompatible Qt library (%d.%d.%d) with this library (%d.%d.%d)") at global/qlogging.cpp:893
#8  0x00007f52ab8fbd71 in QObjectPrivate::checkForIncompatibleLibraryVersion(int) const (this=<optimized out>, version=<optimized out>) at ../../include/QtCore/../../src/corelib/global/qlogging.h:90
Comment 8 Robert S. 2022-09-17 14:40:26 UTC
(In reply to Robert S. from comment #7)
> Created attachment 152156 [details]
> New crash information added by DrKonqi
> 
> plasmashell (5.25.5) using Qt 5.15.6
> 
> I restarted my computer after installing about 5.5GiB of updates only to see
> a blank screen with a mouse cursor. I rebooted and got the same result
> again, so I did ctrl alt F2, logged in and started X only to be met by error
> message dialogues and my plasma shell not starting. I opened my terminal and
> tried kstart5, however that ended up having the same behaviour. Apologies if
> I am missing some debug symbols - not every one could be installed it seems.
> 
> -- Backtrace (Reduced):
> #4  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
> #5  0x00007f52ab4a2859 in __GI_abort () at abort.c:79
> #6  0x00007f52ab8e6bd9 in qt_message_fatal (context=..., message=<synthetic
> pointer>...) at global/qlogging.cpp:1914
> #7  QMessageLogger::fatal(char const*, ...) const
> (this=this@entry=0x7fffff1caeb0, msg=msg@entry=0x7f52abcda448 "Cannot mix
> incompatible Qt library (%d.%d.%d) with this library (%d.%d.%d)") at
> global/qlogging.cpp:893
> #8  0x00007f52ab8fbd71 in
> QObjectPrivate::checkForIncompatibleLibraryVersion(int) const
> (this=<optimized out>, version=<optimized out>) at
> ../../include/QtCore/../../src/corelib/global/qlogging.h:90

Alright nevermind, a sudo apt full-upgrade and sudo apt autoremove --purge seems to have fixed it.
Comment 9 Nate Graham 2022-09-19 21:17:03 UTC
It'll happen randomly; it's still ultimately the same issue as Bug 420245, which is not fixed yet.

*** This bug has been marked as a duplicate of bug 420245 ***