[Bug 1140777] New: Plasma shell freezes and/or stops rendering elements
http://bugzilla.opensuse.org/show_bug.cgi?id=1140777 Bug ID: 1140777 Summary: Plasma shell freezes and/or stops rendering elements Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Major Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs@opensuse.org Reporter: sb56637@gmail.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Hi, I started experiencing this major bug in one of the recent Plasma/KDE/KF5 updates for openSUSE Tumbleweed within the past week. Very frequently (within an hour or less) I notice that the Plama panel clock stops updating, and the App Menu and Calendar popups stop rendering (just the outline), and notification popups show black with a copy of the panel underneath. When I restart `plasmashell` it fixes it for a while, but later starts glitching again. This is on a Thinkpad T530 laptop with integrated Intel graphics, running the X modesetting drivers. I also tried switching to the Xorg Intel driver, but it still behaves the same. I tried switching the KWin compositor from X11 rendering to openGL, but it made no difference. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140777
http://bugzilla.opensuse.org/show_bug.cgi?id=1140777#c1
--- Comment #1 from S. B.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140777
http://bugzilla.opensuse.org/show_bug.cgi?id=1140777#c2
--- Comment #2 from S. B.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140777
http://bugzilla.opensuse.org/show_bug.cgi?id=1140777#c3
Wolfgang Bauer
Hi, I started experiencing this major bug in one of the recent Plasma/KDE/KF5 updates for openSUSE Tumbleweed within the past week. Hm, can you narrow that down a bit maybe?
There haven't been any relevant Plasma/KDE/KF5 updates last week. Plasma 5.12.2 was published on Fri, Jun 28th already. Qt has been upgraded to 5.13 on Sun 30th (which of course *might* be the reason). But, there was a kernel update as well. Have you tried to boot the previous kernel? It might be a problem/regression in the intel kernel driver. And there was a Mesa update too (to 19.1.0 and 19.1.1). Btw, kwin's compositing settings are (likely) irrelevant here. The desktop and notifications are rendered using QML/QtQuick, which always uses OpenGL. You can switch to software rendering in "kcmshell5 qtquicksettings", maybe that would help as a workaround at least. Also, it's not really clear from your description, but does the desktop freeze completely, or is it "just" a rendering problem? Do applications continue to work? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140777
http://bugzilla.opensuse.org/show_bug.cgi?id=1140777#c4
--- Comment #4 from Wolfgang Bauer
http://bugzilla.opensuse.org/show_bug.cgi?id=1140777
http://bugzilla.opensuse.org/show_bug.cgi?id=1140777#c5
--- Comment #5 from Wolfgang Bauer
I'll prepare a package without it for you to test. Please try kwin5 from here: https://download.opensuse.org/repositories/home:/wolfi323:/test/openSUSE_Tum...
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140777
http://bugzilla.opensuse.org/show_bug.cgi?id=1140777#c6
--- Comment #6 from S. B.
Hm, can you narrow that down a bit maybe?
There haven't been any relevant Plasma/KDE/KF5 updates last week. Plasma 5.12.2 was published on Fri, Jun 28th already.
Qt has been upgraded to 5.13 on Sun 30th (which of course *might* be the reason).
Ah, yes, I should have mentioned that I sometimes let a few weeks go by without updating. I see in my YaST Packages history that there were a ton of libKF5* updates to 5.59.0 on 27 June. But I'm pretty sure that's NOT the issue, because I just started hitting this bug yesterday or maybe the day before at the earliest. I got the Qt 5.13 upgrade on 3 July, and on Friday 6 July I had trouble when I used VirtualBox for the first time after the upgrade due to a major confirmed Qt 5.13 bug. I also see 2019-07-03 11:13:48|install|kwin5|5.16.2-1.2 Then on 4 July I see some Mesa updates and also a lot of plasma5-* at 5.16.2-1.1 and also plasma-framework 5.59.0. So I'm not sure why I started hitting this issue yesterday. I somehow suspect it has something to do with system load, especially RAM situations, since yesterday was the first day after the major updates that I was running my Windows VM in VirtualBox. I use zRAM and sometimes hit the memory pretty hard. It seemed to be after high RAM usage situations, even after freeing up plenty of RAM, that this glitch started happening. But I'm not 100% certain.
But, there was a kernel update as well. Have you tried to boot the previous kernel?
Ah, you're right. I'll give that a try later. Thanks.
It might be a problem/regression in the intel kernel driver.
But remember that I usually use X modesetting. I did try installing the Intel driver after running into this bug yesterday, which made no difference.
Btw, kwin's compositing settings are (likely) irrelevant here. The desktop and notifications are rendered using QML/QtQuick, which always uses OpenGL. You can switch to software rendering in "kcmshell5 qtquicksettings", maybe that would help as a workaround at least.
Wow, first time for me seeing that one! :-)
Also, it's not really clear from your description, but does the desktop freeze completely, or is it "just" a rendering problem? Do applications continue to work?
It's not a complete system freeze. It mainly seems to be the panel and notifications. Applications continue to work, as does Alt+Tab switching. But clicking on running applications in the panel does nothing. Also files on my ~/Desktop do not update after adding or removing them when this bug appears. Also Krunner does continue to work, which lets me kill and restart plasmashell.
Please try kwin5 from here: https://download.opensuse.org/repositories/home:/wolfi323:/test/openSUSE_Tum...
Great, that's what I'll test throughout my workday today, no other changes. Still kernel 5.1.15-1-default and X modesetting driver. Oh, and do you need a `hwinfo` dump from me? Thanks for the help! -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140777
http://bugzilla.opensuse.org/show_bug.cgi?id=1140777#c7
--- Comment #7 from S. B.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140777
http://bugzilla.opensuse.org/show_bug.cgi?id=1140777#c8
--- Comment #8 from S. B.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140777
http://bugzilla.opensuse.org/show_bug.cgi?id=1140777#c9
--- Comment #9 from Wolfgang Bauer
[Tue Jul 9 14:03:12 2019] i915 0000:00:02.0: GPU HANG: ecode 7:1:0xfffffffe, in kwin_x11 [1478], hang on rcs0 [Tue Jul 9 14:03:12 2019] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [Tue Jul 9 14:03:12 2019] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [Tue Jul 9 14:03:12 2019] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [Tue Jul 9 14:03:12 2019] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [Tue Jul 9 14:03:12 2019] [drm] GPU crash dump saved to /sys/class/drm/card0/error [Tue Jul 9 14:03:12 2019] i915 0000:00:02.0: Resetting chip for hang on rcs0
This comes from the kernel module (which is the same whether you use modesetting or intel), re-assigning. The message suggests to file a bug report upstream though, as you can see. As I suggested already, I'd try to boot the previous kernel to see if it helps. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140777
Wolfgang Bauer
http://bugzilla.opensuse.org/show_bug.cgi?id=1140777
http://bugzilla.opensuse.org/show_bug.cgi?id=1140777#c10
Takashi Iwai
http://bugzilla.opensuse.org/show_bug.cgi?id=1140777
http://bugzilla.opensuse.org/show_bug.cgi?id=1140777#c11
--- Comment #11 from S. B.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140777
http://bugzilla.opensuse.org/show_bug.cgi?id=1140777#c12
--- Comment #12 from S. B.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140777
http://bugzilla.opensuse.org/show_bug.cgi?id=1140777#c14
--- Comment #14 from S. B.
In doubt, better to report even if you are not sure whether there have been already the same one. Often it's a different issue in subtle manner, and the upstream devs would resolve as duplicate if it's really so.
Got it: https://bugs.freedesktop.org/show_bug.cgi?id=111100 (Nice binary bug id number!) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140777
http://bugzilla.opensuse.org/show_bug.cgi?id=1140777#c15
--- Comment #15 from S. B.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140777
http://bugzilla.opensuse.org/show_bug.cgi?id=1140777#c16
--- Comment #16 from S. B.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140777
http://bugzilla.opensuse.org/show_bug.cgi?id=1140777#c17
S. B.
participants (1)
-
bugzilla_noreply@novell.com