Created attachment 165457 [details] Log from crash handler 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 *** STEPS TO REPRODUCE 1. Plug in external monitor 2. Wait for computer to lock the screen 3. Compter crashes and gives instructions to reboot using terminal. OBSERVED RESULT Rebooting is necessary to restore proper operation. EXPECTED RESULT login prompt SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: kubuntu 22.04 (available in About System) KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.104.4 Qt Version: 5.15.3 ADDITIONAL INFORMATION Using an HP 8470w with AMD turks graphics proccessor
Application: kded5 (kded5), signal: Aborted [KCrash Handler] #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=139718111189056) at ./nptl/pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=139718111189056) at ./nptl/pthread_kill.c:78 #6 __GI___pthread_kill (threadid=139718111189056, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #7 0x00007f12a8442476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x00007f12a84287f3 in __GI_abort () at ./stdlib/abort.c:79 #9 0x00007f12a8c90ba3 in QMessageLogger::fatal(char const*, ...) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x00007f12a532b3e4 in QtWaylandClient::QWaylandDisplay::checkError() const () from /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #11 0x00007f12a532c11a in QtWaylandClient::QWaylandDisplay::flushRequests() () from /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #12 0x00007f12a8ef17c8 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x00007f12a8ef4cb3 in QSocketNotifier::activated(QSocketDescriptor, QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x00007f12a8ef54e3 in QSocketNotifier::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x00007f12a9b6c713 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x00007f12a8eb9e3a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x00007f12a8f13cc5 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x00007f12a7bc7d3b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x00007f12a7c1d258 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #20 0x00007f12a7bc53e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #21 0x00007f12a8f130b8 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x00007f12a8eb875b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #23 0x00007f12a8ec0cf4 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x000055a6f68bbf52 in ?? () #25 0x00007f12a8429d90 in __libc_start_call_main (main=main@entry=0x55a6f68bb5e0, argc=argc@entry=1, argv=argv@entry=0x7ffe83acd198) at ../sysdeps/nptl/libc_start_call_main.h:58 #26 0x00007f12a8429e40 in __libc_start_main_impl (main=0x55a6f68bb5e0, argc=1, argv=0x7ffe83acd198, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffe83acd188) at ../csu/libc-start.c:392 #27 0x000055a6f68bc625 in ?? () [Inferior 1 (process 1284) detached]
What instructions did it give you? Can you take a phone photo of the message?
(In reply to Nate Graham from comment #2) > What instructions did it give you? Can you take a phone photo of the message? https://photos.app.goo.gl/hTXCaGe82RpHTYdz6 None of these commands displayed seem to have any effect.
Ah, it's this issue. :( Fortunately it's fixed in Plasma 6. Unfortunately the next Kubuntu LTS release won't use it. Oh well, such is life sometimes.
Thank you for the information! Looking forward to using Plasma 6.0. My first Linux experience was with KDE in the early 2000's and nothing else will do. The improvements over the years have been astounding and I do appreciate the hard work of all who have made KDE what it is. Thank you!
You're very welcome! Thanks for the kind words. It's always nice to know one's work is appreciated!