Application: plasmashell (5.25.4) (Compiled from sources) Qt Version: 5.15.5 Frameworks Version: 5.96.0 Operating System: Linux 5.19.1-gentoo-Ja.KooLit x86_64 Windowing System: Wayland Distribution: "Gentoo Base System release 2.8" DrKonqi: 5.25.4 [KCrashBackend] -- Information about the crash: Id like to add as well that I use all live wallpaper plugins available on the store, whenever I choose a video, at some point it will crash plasmashell. And then it will leave on the panel that states "plasma desktop workspace" 2 spaces. When right clicking and trying to close, it does nothing this is the screenshot of the 2 spaces which cannot be close and stays there. https://imgur.com/a/RbWqFhA This only happen on Plasma-Wayland. X11 does not seem to suffer from this bug The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted [KCrash Handler] #4 0x00007f3f46292c7c in () at /lib64/libc.so.6 #5 0x00007f3f46245a22 in raise () at /lib64/libc.so.6 #6 0x00007f3f46230469 in abort () at /lib64/libc.so.6 #7 0x00007f3f466a5cc7 in () at /usr/lib64/libQt5Core.so.5 #8 0x00007f3f481f9e16 in QSGRenderLoop::handleContextCreationFailure(QQuickWindow*) () at /usr/lib64/libQt5Quick.so.5 #9 0x00007f3f46ca51e5 in QWindow::event(QEvent*) () at /usr/lib64/libQt5Gui.so.5 #10 0x00007f3f48ae54a5 in PlasmaQuick::Dialog::event(QEvent*) () at /usr/lib64/libKF5PlasmaQuick.so.5 #11 0x00007f3f4753fa2f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #12 0x00007f3f468961f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #13 0x00007f3f46c9af11 in QGuiApplicationPrivate::processExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*) () at /usr/lib64/libQt5Gui.so.5 #14 0x00007f3f46c78fbb in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Gui.so.5 #15 0x00007f3f44971320 in () at /usr/lib64/libQt5WaylandClient.so.5 #16 0x00007f3f44dd433b in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #17 0x00007f3f44dd45f8 in () at /usr/lib64/libglib-2.0.so.0 #18 0x00007f3f44dd46af in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #19 0x00007f3f468e8514 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #20 0x00007f3f46894bdb in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #21 0x00007f3f4689d23d in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5 #22 0x0000564504e53799 in () #23 0x00007f3f4623134a in () at /lib64/libc.so.6 #24 0x00007f3f462313fc in __libc_start_main () at /lib64/libc.so.6 #25 0x0000564504e539d1 in () [Inferior 1 (process 6328) detached] Reported using DrKonqi
Does this happen after you've updated your graphics drivers, but before you've rebooted? If so, does it stop happening after you reboot?
Hi Nate, no my gpu drivers was not updated, or there were no update on mesa at that time. I added a plugin (live wallpaper plugins available on store (smart video live wallpaper) and when I add a video for the live wallpaper, I noticed that system hangs for some time. After about a min or less, live wallpaper played but got also a plasmashell crash. I thought about something wrong with plugin, so I downloaded and use other live wallpaper plugin. All same thing.. plug ins I further added are smarter video wallpaper video video lockscreen. All same thing.... Then I switched to x11 session, live wallpapers are running great with no issues. rebooted, updated drivers, vulkan, mesa etc... nothing helps. Seems like only happening on plasma wayland. Id like to point out though that this only happen on my gentoo-plasma system. my all other plasma distros (Arch and Fedora) does not have these bug.
(In reply to Nate Graham from comment #1) > Does this happen after you've updated your graphics drivers, but before > you've rebooted? If so, does it stop happening after you reboot? Hi Nate, no my gpu drivers was not updated, or there were no update on mesa at that time. I added a plugin (live wallpaper plugins available on store (smart video live wallpaper) and when I add a video for the live wallpaper, I noticed that system hangs for some time. After about a min or less, live wallpaper played but got also a plasmashell crash. I thought about something wrong with plugin, so I downloaded and use other live wallpaper plugin. All same thing.. plug ins I further added are smarter video wallpaper video video lockscreen. All same thing.... Then I switched to x11 session, live wallpapers are running great with no issues. rebooted, updated drivers, vulkan, mesa etc... nothing helps. Seems like only happening on plasma wayland. Id like to point out though that this only happen on my gentoo-plasma system. my all other plasma distros (Arch and Fedora) does not have these bug.
Does it happen if you use one of the default wallpaper plugins, rather than the 3rd-party video plugins you're trying?
(In reply to Nate Graham from comment #4) > Does it happen if you use one of the default wallpaper plugins, rather than > the 3rd-party video plugins you're trying? no it does not happen to any default plugins.. However, no issues as well on any other 3rd party plugins apart from animated or video type of wallpapers. So it seems that its only limited to that cause. I also have updated to latest Plasma and Framewrks version But this happen only on wayland session. When I load 3rd party plugin on X11 sessions, no issues, no crashing. My system is all AMD so no propriety drivers installed (if that matters)
(In reply to Ja Koolit from comment #5) > (In reply to Nate Graham from comment #4) > > Does it happen if you use one of the default wallpaper plugins, rather than > > the 3rd-party video plugins you're trying? > > no it does not happen to any default plugins.. However, no issues as well on > any other 3rd party plugins apart from animated or video type of wallpapers. > So it seems that its only limited to that cause. I also have updated to > latest Plasma and Framewrks version > > But this happen only on wayland session. When I load 3rd party plugin on X11 > sessions, no issues, no crashing. > > My system is all AMD so no propriety drivers installed (if that matters) Operating System: Gentoo Linux 2.8 KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 Kernel Version: 5.19.1-gentoo-Ja.KooLit (64-bit) Graphics Platform: X11 Processors: 32 × AMD Ryzen 9 5950X 16-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 6900 XT Manufacturer: ASUS
Thanks. Regardless, the presence of > QSGRenderLoop::handleContextCreationFailure in the backtrace tells me that it's a graphics-related issue. There are a few possibilities: 1. The 3rd-party wallpaper effect is at fault for causing a graphics glitch 2. Your graphics drivers are at fault for not handling this condition properly 3. KWin is at fault for not handling this condition properly. 1 and 2 are outside of KDE's control, so I'll move this to the kwin component for now so the KWin maintainers can see if there's anything KWin can do to handle it. If not, it'll most likely be up to your graphics drivers to handle this better.
(In reply to Nate Graham from comment #7) > Thanks. > > Regardless, the presence of > > > QSGRenderLoop::handleContextCreationFailure > > in the backtrace tells me that it's a graphics-related issue. There are a > few possibilities: > 1. The 3rd-party wallpaper effect is at fault for causing a graphics glitch > 2. Your graphics drivers are at fault for not handling this condition > properly > 3. KWin is at fault for not handling this condition properly. > > 1 and 2 are outside of KDE's control, so I'll move this to the kwin > component for now so the KWin maintainers can see if there's anything KWin > can do to handle it. If not, it'll most likely be up to your graphics > drivers to handle this better. Cool. thanks
(In reply to Ja Koolit from comment #8) > (In reply to Nate Graham from comment #7) > > Thanks. > > > > Regardless, the presence of > > > > > QSGRenderLoop::handleContextCreationFailure > > > > in the backtrace tells me that it's a graphics-related issue. There are a > > few possibilities: > > 1. The 3rd-party wallpaper effect is at fault for causing a graphics glitch > > 2. Your graphics drivers are at fault for not handling this condition > > properly > > 3. KWin is at fault for not handling this condition properly. > > > > 1 and 2 are outside of KDE's control, so I'll move this to the kwin > > component for now so the KWin maintainers can see if there's anything KWin > > can do to handle it. If not, it'll most likely be up to your graphics > > drivers to handle this better. > Cool. thanks for looking into this.. Best thing for me right now is to then not use 3rd party plugin, and ill observe if any crash and then try again once got update on gpu drivers or plugin updates. thanks alot for looking into this
You're welcome!
(In reply to Nate Graham from comment #10) > You're welcome! Hey Nate, Just to give you an update, I found out what is causing. Its hardware video acceleration system wide. I disable it, kwin is not crashing anymore and my live wallpaper is not back to normal :)
Thanks for the info!
This bug is a crash report that is over a year old without any activity, as our software is always changing, the information in this ticket is unlikely to still be useful. If this issue is still reproducible in a newer version of kwin (5.27.5 or 6.0) please reopen this ticket with a bumped version number or it will be closed in 30 days.
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!