SUMMARY Selecting text using the mouse in the color fields to pick a color triggers a crash with wayland Probably a upstream bug since this is not a issue on X11 STEPS TO REPRODUCE Add color picker widget to desktop (do NOT use plasmawindowed it will not crash if you do) right click and open the color selector highlight a rgb with the mouse OBSERVED RESULT plasma crashes screen capture: https://mega.nz/file/BZ8g0JSZ#x4c8KWbibBZSV2tCa12IYK4GewUZQ5cp0KNcnwFz_BU https://mega.nz/file/1U9AVIjb#G1gAyiJ4Y52BjAAp2S1PKUUhZ9_d7XC9hrpxF8gvOHo EXPECTED RESULT plasma continues running SOFTWARE/OS VERSIONS apt-cache policy plasma-widgets-addons Installed: 4:5.23.4-0ubuntu1 Candidate: 4:5.23.4-0ubuntu1 Version table: *** 4:5.23.4-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages 100 /var/lib/dpkg/status Operating System: Kubuntu 22.04 KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 Kernel Version: 5.16.0-051600rc4-generic (64-bit) Processors: 12 × AMD Ryzen 5 3600 6-Core Processor Memory: 15.6 GiB of RAM Graphics Processor: Radeon RX 580 Series
Can you attach a backtrace of the crash? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
looks like i would need to run the applet by passing it through the gdb command, how would i do that without running via plasmawindowed as doing that makes it not crash? unable to crash in virutalbox, looks like you need to use bare metal I am also able to get this crash using a ryzen 5 5600G as well as dell with a 2ed gen intel CPU Operating System: Kubuntu 22.04 (daily live: Dec 1 2021) KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 Kernel Version: 5.13.0-19-generic (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i3-2100 CPU @ 3.10GHz Memory: 3.7 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 2000
normally when something crashes the os will detect it as ask if i want to report it (dev. branch and all) this has not happened with this crash
by running plasmashell --replace i was able to get this in the console when i trigger the crash Error sending request: Broken pipe The Wayland connection broke. Did the Wayland compositor die? KCrash: Attempting to start /usr/bin/plasmashell
Sounds like KWin crashed, then. You'll need to get a backtrace for kwin_wayland, not plasmashell.
so how do it run kwin_wayland from a terminal without crashing the terminal? cause that what kwin_wayland --replace does is there someway i can just see all the console output over ssh?
You can run kwin_wayland from another VT in gdb, or you can use the command-line `coredumpctl` utility to get a backtrace of a previous crash.
Created attachment 144356 [details] backtrace I think i got it the crash reporter picked it up this time hopefully that was not from me trying to run kwin_wayland --replace
coredumpctl -1 dump -o /tmp/crash holy crap file is massive uses max lzma compression on it still too big to attach here, but 9.4 MiB is better than 663 MiB https://mega.nz/file/AI9lySDb#5fSMIqrW9qf6h_CcRjehtJpCtBmQhSgdretQUCgmOWA
We don't need the whole dump; you use it to get a backtrace. See the instructions at https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl.
Created attachment 144376 [details] backtrace i think this is what you wanted
Created attachment 144377 [details] coredumpctl gdb 1430 or maybe you wanted this? both?
Yep that's it, thanks! Pasting inline for searchability: [KCrash Handler] #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140426250739968) at pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=140426250739968) at pthread_kill.c:80 #6 __GI___pthread_kill (threadid=140426250739968, signo=signo@entry=6) at pthread_kill.c:91 #7 0x00007fb78cec8476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x00007fb78ceae7b7 in __GI_abort () at abort.c:79 #9 0x00007fb78d355ba3 in QMessageLogger::fatal(char const*, ...) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x00007fb78b588e45 in ?? () from /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #11 0x00007fb78b59906a in QtWaylandClient::QWaylandDisplay::flushRequests() () from /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #12 0x00007fb78d5b5dd8 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x00007fb78d5d7802 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x00007fb78d57cdeb in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x00007fb78d585374 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x00005572f716ad0e in ?? () #17 0x00007fb78ceaffd0 in __libc_start_call_main (main=main@entry=0x5572f7169eb0, argc=argc@entry=1, argv=argv@entry=0x7fff6a3279a8) at ../sysdeps/nptl/libc_start_call_main.h:58 #18 0x00007fb78ceb007d in __libc_start_main_impl (main=0x5572f7169eb0, argc=1, argv=0x7fff6a3279a8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff6a327998) at ../csu/libc-start.c:409 #19 0x00005572f716ae35 in ?? () [Inferior 1 (process 1430) detached] It looks like plasma might have crashed because kwin_wayland crashed. Do you also have any kwin_wayland crash logs in `coredumpctl` if so can you paste the backtrace for that one?
that was the only one that showed up... let me crash it again... this is very easily reproducible are you having issues? should i test it on more hardware? i have access to some old nvidia cards (1GB GT 430 / 2GB 650 Ti Boost) and amd cpus (Phenom II) $ coredumpctl TIME PID UID GID SIG COREFILE EXE SIZE Wed 2021-12-08 13:58:01 EST 1623 1000 1000 SIGABRT present /usr/bin/plasmashell 41.3M Wed 2021-12-08 14:01:38 EST 4334 1000 1000 SIGABRT present /usr/bin/plasmashell 15.1M Wed 2021-12-08 14:04:55 EST 12990 1000 1000 SIGABRT present /usr/bin/plasmashell 14.7M Wed 2021-12-08 22:39:49 EST 1430 1000 1000 SIGABRT present /usr/bin/plasmashell 40.4M Wed 2021-12-08 22:49:38 EST 1230 1000 1000 SIGABRT present /usr/bin/kwalletd5 812.7K Wed 2021-12-08 22:49:39 EST 13554 1000 1000 SIGABRT present /usr/lib/x86_64-linux-gnu/libexec/drkonqi 388.7K Wed 2021-12-08 22:49:39 EST 13562 1000 1000 SIGABRT present /usr/lib/x86_64-linux-gnu/libexec/org_kde_powerdevil 498.8K Wed 2021-12-08 22:49:39 EST 13567 1000 1000 SIGABRT present /usr/lib/x86_64-linux-gnu/libexec/drkonqi 389.0K Wed 2021-12-08 22:49:39 EST 13565 1000 1000 SIGABRT present /usr/lib/x86_64-linux-gnu/libexec/drkonqi 390.3K Wed 2021-12-08 22:49:39 EST 13569 1000 1000 SIGABRT present /usr/lib/x86_64-linux-gnu/libexec/drkonqi 389.2K Wed 2021-12-08 22:49:39 EST 13566 1000 1000 SIGABRT present /usr/bin/kded5 281.7K Wed 2021-12-08 22:49:39 EST 13568 1000 1000 SIGABRT present /usr/lib/x86_64-linux-gnu/libexec/drkonqi 389.3K Wed 2021-12-08 22:49:39 EST 13570 1000 1000 SIGABRT present /usr/bin/plasmashell 600.0K Wed 2021-12-08 22:49:40 EST 1480 1000 1000 SIGABRT present /usr/lib/x86_64-linux-gnu/libexec/kactivitymanagerd 624.8K Wed 2021-12-08 22:49:40 EST 1440 1000 1000 SIGABRT present /usr/lib/x86_64-linux-gnu/libexec/org_kde_powerdevil 735.2K Wed 2021-12-08 22:49:40 EST 1466 1000 1000 SIGABRT present /usr/lib/x86_64-linux-gnu/libexec/DiscoverNotifier 938.3K Wed 2021-12-08 22:49:40 EST 2529 1000 1000 SIGABRT present /usr/bin/plasmashell 16.2M Wed 2021-12-08 22:49:40 EST 1423 1000 1000 SIGABRT present /usr/bin/kded5 6.5M Wed 2021-12-08 23:00:47 EST 15497 1000 1000 SIGSEGV present /usr/bin/dolphin 29.9M Thu 2021-12-09 10:08:21 EST 2364 1000 1000 SIGSEGV present /usr/bin/dolphin 4.0M Thu 2021-12-09 12:57:34 EST 2448 1000 1000 SIGABRT present /usr/bin/plasmashell 41.7M Note: That entire series on Wed afternoon is a separate issue from a single crash in dolphin and i backtracked everything and reported it under it's own bug report
is there a reason that coredumpctl deos not get a crash from kwin? does a lack of it mean it does not crash?
Hmm, probably means that it's aborting rather than crashing.
If kwin crashes, please provide the backtrace of its crash. The backtraces above are for plasmashell, which is a separate process.
if it had crashed it would have been included, this is very easy to reproduce yourself in under 60 seconds in my testing, it does not seem to be hardware specific, if you do not believe me when i say there is never a kwin crash file try it yourself
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
Requested info in kwin crash log, but kwin does NOT CRASH thus requested info can not exist
Changing to reported as the requested info does NOT exist
I just watched the video. kwin definitely didn't exit. Plasmashell was killed because of a protocol error. I was unable to reproduce following the same steps. Can you confirm it's still an issue? Also attach the command line output of running "plasmashell --replace " and then reproduce the issue.
Well this is odd, i no longer have a option to login with wayland running kubuntu 22.04
Sounds like the package that provides it got uninstalled during some upgrade.
plasma-workspace-wayland was the missing package I am unable to reproduce the crash (AMD GPU)
Setting status as works for me as i can no long reproduce this issue