Application: plasmashell (5.24.2) Qt Version: 5.15.2 Frameworks Version: 5.91.0 Operating System: Linux 5.13.0-22-generic x86_64 Windowing System: Wayland Distribution: Ubuntu 21.10 DrKonqi: 5.24.2 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: Just login to the pc. - Unusual behavior I noticed: The splash appears, after that I can see the wallpaper but no panels are loaded. After some seconds the crash modal appears and the wallpaper dissapears. Just a black screen. - Custom settings of the application: I am using some widgets like inline battery, configurable button widget and Toggle Panel button widget. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted [KCrash Handler] #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140181637702848) at pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=140181637702848) at pthread_kill.c:80 #6 __GI___pthread_kill (threadid=140181637702848, signo=signo@entry=6) at pthread_kill.c:91 #7 0x00007f7e98c28476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x00007f7e98c0e7b7 in __GI_abort () at abort.c:79 #9 0x00007f7e990b3ba3 in QMessageLogger::fatal(char const*, ...) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x00007f7e972d9354 in QtWaylandClient::QWaylandDisplay::checkError() const () from /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #11 0x00007f7e972da06a in QtWaylandClient::QWaylandDisplay::flushRequests() () from /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #12 0x00007f7e99313a88 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x00007f7e993355db in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x00007f7e992daa9b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x00007f7e992e3024 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x000055e00af68da9 in ?? () #17 0x00007f7e98c0ffd0 in __libc_start_call_main (main=main@entry=0x55e00af67f50, argc=argc@entry=1, argv=argv@entry=0x7ffceff1e3a8) at ../sysdeps/nptl/libc_start_call_main.h:58 #18 0x00007f7e98c1007d in __libc_start_main_impl (main=0x55e00af67f50, argc=1, argv=0x7ffceff1e3a8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffceff1e398) at ../csu/libc-start.c:409 #19 0x000055e00af68ec5 in ?? () [Inferior 1 (process 2582) detached] Possible duplicates by query: bug 450707, bug 450663, bug 450646, bug 450320, bug 450112. Reported using DrKonqi
Are you using fish shell?
No, I am not using Fish Shell.
Thanks. Can't tell from the backtrace what might be happening. Hopefully someone more senior can take over.
Thank you so much for your answer Nate, I'll keep updating every version and testing this. Maybe I'll try a clean install too.
*** Bug 451472 has been marked as a duplicate of this bug. ***
After upgrading my distro(kubuntu) to 22.04, the issue is gone for my laptop with AMD iGpu. My desktop with Nvidia is not working yet, however, that's in some way expected.
The crash reporting assistant treats a bug I have which is complimentary to this one as a duplicate. This was a person for whom Kubuntu Wayland was not working in 21.10 but the upgrade to 22.04 fixed it. I had Wayland working fine in 21.10 but the upgrade in place to 22.04 broke it. There was an anomaly during my upgrade process which I had to restart, but after that everything else on the system worked fine. Everything works under X11. I am even running this program under Wayland because I know how to get to a shell and to launch programs from it. Just like using X11 without a window manager in the 1990's. However, this is unacceptable for a modern desktop in the 2020's! We must not be cavalier about these problems. The original problem should not have existed for Orlando Rodriguez under 21.10 and my working Wayland should not have been broken by an update in place. NO, a total clean wipe of my system drive at this point is not desirable as in every other way this system works like a well tuned beast. Finally.
Created attachment 148492 [details] Terminal input and crash report
Hmm, I wonder if Plasma crashed because KWin crashed. do you see any "kwin_wayland" crashes in the output of `coredumpctl --reverse`?
Created attachment 148571 [details] New crash information added by DrKonqi plasmashell (5.24.4) using Qt 5.15.3 - What I was doing when the application crashed: This bug was created after upgrade my OS from Ubuntu Studio 21.10 to Ubuntu Studio 22.04. Plasma works on X11, but crash when login with Wayland, so I could not do anything but seeing error message. -- Backtrace (Reduced): #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140180712290752) at ./nptl/pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=140180712290752) at ./nptl/pthread_kill.c:78 #6 __GI___pthread_kill (threadid=140180712290752, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #7 0x00007f7e61c6d476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x00007f7e61c537f3 in __GI_abort () at ./stdlib/abort.c:79
(In reply to Nate Graham from comment #9) > Hmm, I wonder if Plasma crashed because KWin crashed. do you see any > "kwin_wayland" crashes in the output of `coredumpctl --reverse`? I have not noticed that. I can try. That said if Kwin crashed then, under X11 that used to mean no ability to manage windows. No resize, close, move etc. I can do all of that but I know Wayland works differently.
(In reply to Nate Graham from comment #9) > Hmm, I wonder if Plasma crashed because KWin crashed. do you see any > "kwin_wayland" crashes in the output of `coredumpctl --reverse`? $ coredumpctl --reverse TIME PID UID GID SIG COREFILE EXE SIZE Thu 2022-05-05 07:38:10 CDT 1973 1000 1000 SIGABRT present /usr/bin/ksplashqml 2.9M Thu 2022-05-05 07:37:40 CDT 3114 1000 1000 SIGSYS present /usr/lib/insync/PySide2/Qt/libexec/QtWebEngineProcess 918.3K Thu 2022-05-05 07:37:39 CDT 3077 1000 1000 SIGSYS present /usr/lib/insync/PySide2/Qt/libexec/QtWebEngineProcess 918.3K Thu 2022-05-05 07:37:22 CDT 2324 1000 1000 SIGABRT present /usr/bin/plasmashell 23.4M Thu 2022-05-05 07:33:35 CDT 48982 1000 1000 SIGABRT present /usr/lib/x86_64-linux-gnu/libexec/ksmserver-logout-greeter 3.4M Thu 2022-05-05 07:32:13 CDT 48359 1000 1000 SIGSYS present /usr/lib/insync/PySide2/Qt/libexec/QtWebEngineProcess 918.6K Thu 2022-05-05 07:32:12 CDT 48346 1000 1000 SIGSYS present /usr/lib/insync/PySide2/Qt/libexec/QtWebEngineProcess 918.6K Thu 2022-05-05 07:32:02 CDT 47595 1000 1000 SIGABRT present /usr/bin/plasmashell 6.5M Kwin is not crashing Plasmashell is. In fact other key parts are also crashing. If I ctrl-alt-del to log out of this "session" the logout greeter also fails. All of these same programs (?) work in X11. They previously worked under 21.10 for Wayland.
OK, thanks.
I'd like to point out that exactly once I was able to login to plasma wayland BUT for some reason my sound didn't work. Like devices were not detected. No idea if this was a coincidence.
*** Bug 454419 has been marked as a duplicate of this bug. ***
Same problem here. I just update today my old laptop. Just to test new Kubuntu 22.04. 5.24.4 After a fresh instal,l Plasma x11 is fine but Wayland crashes. I updated also to latest Kubuntu backports plasma 5.24.5 Same problem. I only see my mouse cursor and a black background. If try to run plasma-shell --replace, it crashes. The GPU is Nvidia. For now, no way to use Wayland in Kubuntu 22.04 regards Galder
Created attachment 150852 [details] New crash information added by DrKonqi plasmashell (5.24.4) using Qt 5.15.3 - What I was doing when the application crashed: installed plasma-workspace-wayland package to test on wayland on kubuntu - Unusual behavior I noticed: plasma crashed on login - Custom settings of the application: -- Backtrace (Reduced): #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140157175019968) at ./nptl/pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=140157175019968) at ./nptl/pthread_kill.c:78 #6 __GI___pthread_kill (threadid=140157175019968, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #7 0x00007f78e6d89476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x00007f78e6d6f7f3 in __GI_abort () at ./stdlib/abort.c:79
Just to add some findings. for me Wayland crashes in 5.24.6, however it does work in 5.25.3. My system is based in Ubuntu 21.10 with Nvidia drivers. Regards.
These logs show that kwin quit. We have no backtraces of kwin to proceed. If we get traces on that, lets open them as new kwin bug reports.