SUMMARY Sometimes, seemingly at random (it did help twice in 15 minutes when doing a Duolingo lesson though), a small area (a quarter of the screen in the lower right region) will just pop into the screen and "take over" the desktop functions? The mouse doesn't move back into the rest of the screen and it's impossible to do anything recognisable, but depending on what I do with the mouse and keyboard random stuff appears on that corner of the screen. The solution is to open a virtual console, ps -ax my way to wayland processes, and kill them all, restarting the whole session. This is incredibly annoying STEPS TO REPRODUCE 1. No idea, but maybe try doing a duolingo lesson on Firefox? I'm sorry but I'm not very good at knowing how to get useful debug messages out of the gate or what log files to look at, if you tell me what to do I can hopefully provide useful data OBSERVED RESULT Everything goes to hell EXPECTED RESULT This doesn't happen Operating System: openSUSE Tumbleweed 20250128 KDE Plasma Version: 6.2.5 KDE Frameworks Version: 6.10.0 Qt Version: 6.8.1 Kernel Version: 6.13.0-1-default (64-bit) Graphics Platform: Wayland Processors: 6 × AMD Ryzen 5 3500X 6-Core Processor Memory: 15.5 GiB of RAM Graphics Processor: NV106 ADDITIONAL INFORMATION
Created attachment 177879 [details] What happens when I press alt+F2
Created attachment 177880 [details] The moment it happens
Hello, If something crashed, we need a backtrace of it so we can figure out what's going on. Can you please attach a backtrace of the crash using the coredumpctl command-line program, as detailed in https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl? Thanks! Daniel
Hi Daniel, thanks for the pointers! So I expected the crash to be with plasma or wayland or something but the only thing in the coredumpctl list around the time of the most recent break was "/usr/bin/plasma-browser-integration-host". Which makes sense seeing as I was using the browser every time something like this happened. Then again the browser is never closed when I'm using the computer, but I think I was *actively* using the browser. (sorry if pasting the backtrace here is going to be annoying but I couldn't find any markdown help regarding how to wrap this as code) #0 __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 #1 0x00007f15c069a1c3 in __pthread_kill_internal (threadid=<optimized out>, signo=6) at pthread_kill.c:78 #2 0x00007f15c0641436 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #3 0x00007f15c062891a in __GI_abort () at abort.c:79 #4 0x00007f15c0ef3cd1 in qAbort () at /usr/src/debug/qtbase-everywhere-src-6.8.1/src/corelib/global/qassert.cpp:49 #5 qt_message_fatal<QString&> (context=..., message=...) at /usr/src/debug/qtbase-everywhere-src-6.8.1/src/corelib/global/qlogging.cpp:2116 #6 qt_message(QtMsgType, const QMessageLogContext &, const char *, typedef __va_list_tag __va_list_tag *) (msgType=msgType@entry=QtFatalMsg, context=..., msg=msg@entry=0x7f15c1dc2744 "%s", ap=ap@entry=0x7ffd19734ee8) at /usr/src/debug/qtbase-everywhere-src-6.8.1/src/corelib/global/qlogging.cpp:382 #7 0x00007f15c0ef4be8 in QMessageLogger::fatal (this=this@entry=0x7ffd197353e0, msg=msg@entry=0x7f15c1dc2744 "%s") at /usr/src/debug/qtbase-everywhere-src-6.8.1/src/corelib/global/qlogging.cpp:884 #8 0x00007f15c1773e01 in init_platform (pluginNamesWithArguments=..., platformPluginPath=..., platformThemeName=..., argc=@0x7ffd1973579c: 3, argv=<optimized out>) at /usr/src/debug/qtbase-everywhere-src-6.8.1/src/gui/kernel/qguiapplication.cpp:1327 #9 QGuiApplicationPrivate::createPlatformIntegration (this=0x556b07b27450) at /usr/src/debug/qtbase-everywhere-src-6.8.1/src/gui/kernel/qguiapplication.cpp:1580 #10 0x00007f15c1811e78 in QGuiApplicationPrivate::createEventDispatcher (this=<optimized out>) at /usr/src/debug/qtbase-everywhere-src-6.8.1/src/gui/kernel/qguiapplication.cpp:1599 #11 0x00007f15c0faf80d in QCoreApplicationPrivate::init (this=this@entry=0x556b07b27450) at /usr/src/debug/qtbase-everywhere-src-6.8.1/src/corelib/kernel/qcoreapplication.cpp:928 #12 0x00007f15c1811efe in QGuiApplicationPrivate::init (this=this@entry=0x556b07b27450) at /usr/src/debug/qtbase-everywhere-src-6.8.1/src/gui/kernel/qguiapplication.cpp:1627 #13 0x00007f15c25dae7d in QApplicationPrivate::init (this=0x556b07b27450) at /usr/src/debug/qtbase-everywhere-src-6.8.1/src/widgets/kernel/qapplication.cpp:474 #14 0x00007f15c25daf7e in QApplication::QApplication (this=<optimized out>, argc=<optimized out>, argv=<optimized out>, this=<optimized out>, argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/qtbase-everywhere-src-6.8.1/src/widgets/kernel/qapplication.cpp:462 #15 0x0000556ae80497d0 in main (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/plasma-browser-integration-6.2.5/host/main.cpp:82
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone!
I probably forgot to set the bug to "reported" when I provided the backtrace, cause I don't know what the bug janitor's talking about... Please let me know if I can provide any more information.
All done now for you. Now just weit to get developer attention.
(In reply to Daniel Frantes from comment #7) > All done now for you. > Now just weit to get developer attention. I just wanted to add that I hadn't had that problem since then because I had disabled plasma-browser-integration-host (I don't remember if only in the browser of I'd uninstalled it). However I messed up my system and had to do a reinstall, and there it was again, not on Duolingo but looking at the local Plex instance via the browser. I'm going to try uninstalling the browser integration altogether, but just out of curiosity, is there a way of shutting down a "wayland session" (if such a thing exists) on a tty so I can just restart the graphical session? I hate having to reboot the whole thing.