[Bug 1013550] New: plasmashell freezing
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550 Bug ID: 1013550 Summary: plasmashell freezing Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs@opensuse.org Reporter: opensuse@mike.franken.de QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:50.0) Gecko/20100101 Firefox/50.0 Build Identifier: On one of my machines (Lenovo T420 notebook) I have a problem with plasmashell freezing often when a notification is shown. The notification frame shows up, but no content and then the complete desktop freezes. Killing and restarting plasmashell cures the problem for a short time - til one of the the next notifications wants to display something. It doesn't happen for all notifications, though. Using tools like notify-send the problem can not be reproduced, but notifications stemming from plasma-nm and plasma-workspace itself (like the one for a removed plasmoid) always lead to the freeze. The system originally was openSuSE Leap 42.2, but because of the problem I upgraded step by step to - the latest kernel from the kernel stable repo, - the latest X server plus everyting from the X11:Xorg repo - and the latest plasma workspace including everything from the KDE:Framework5 repo. The problem remained unchanged, though. A few more facts: - The X server is xf86-video-intel. - Switching off the compositor doesn't help either. - Everything worked with Leap 42.1 - No according entry in the journal or .xsession-errors* can be found. - And a curiosity: After removing .config/plasmarc and restarting plasmashell the problem vanishes for a few hours or even a day, before it comes back. - Logging off or restarting the machine doesn't help in case the problems exists at that time. In found a few bug reports for plasma freezes, but none of them seems to fit exactly. Reproducible: Sometimes Steps to Reproduce: 1. unlock widgets 2. remove widget 3. a notification tries to popup 4. plasmashell freezes 1. wait for a plasma-nm notification 2. plasmashell freezes Actual Results: plasmashell freezes Expected Results: plasmashell should not freeze, the notification shoold popup see details -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550
Michael Hirmke
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550#c1
Tomas Jensen
to put the following/creating in e. g. /etc/X11/xorg.conf.d/20-intel.conf:
Section "Device" Identifier "Intel Graphics" Driver "intel" Option "AccelMethod" "uxa" EndSection
I've observed same with popups in Chrome, Firefox or even Plasma when plasma reports a crash. X can be restarted by hitting CTRL+ALT+BACKSPACE or you could escape to a shell with CTRL+ALT+F12 and then ALT+F1 /Tomas -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550#c2
--- Comment #2 from Michael Hirmke
Same on a HP6320nc.
The issue is descriped here: https://bugs.kde.org/show_bug.cgi?id=349519
No, it isn't. This is why I wrote: In found a few bug reports for plasma freezes, but none of them seems to fit exactly.
Fix is to:
No, this doesn't fix my problem. Sorry, I forgot to write before, that I already tested that option. According to Xorg.0.log the uxa option was recognized, but the problem still remained. Just to be sure, I tested it a second time today - still no go. [...]
X can be restarted by hitting CTRL+ALT+BACKSPACE or you could escape to a shell with CTRL+ALT+F12 and then ALT+F1
You don't need to kill the X serverin my case, restarting plasmashell is enough. Btw.: Switching off notifications completely also is a workaround in my case.
/Tomas
Thx anyway for your answer. Bye. Michael. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550#c3
--- Comment #3 from Tomas Jensen
Same on a HP6320nc.
The issue is descriped here: https://bugs.kde.org/show_bug.cgi?id=349519
Fix is to:
to put the following/creating in e. g. /etc/X11/xorg.conf.d/20-intel.conf:
Section "Device" Identifier "Intel Graphics" Driver "intel" Option "AccelMethod" "uxa" EndSection
I've observed same with popups in Chrome, Firefox or even Plasma when plasma reports a crash.
X can be restarted by hitting CTRL+ALT+BACKSPACE or you could escape to a shell with CTRL+ALT+F12 and then ALT+F1
/Tomas
Confirmed that the fix above is working on HP6320nc. /Tomas -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550
Frerk Meyer
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550#c4
--- Comment #4 from Frerk Meyer
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550#c5
--- Comment #5 from Frerk Meyer
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550
Alessio Adamo
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550#c6
--- Comment #6 from Frerk Meyer
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550#c8
--- Comment #8 from Michael Hirmke
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550
Stefan Dirsch
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550#c9
Max Staudt
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550#c10
--- Comment #10 from Michael Hirmke
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550#c11
--- Comment #11 from Max Staudt
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550
Stefan Dirsch
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550#c12
--- Comment #12 from Michael Hirmke
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550#c13
Max Staudt
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550#c14
--- Comment #14 from Michael Hirmke
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550#c15
--- Comment #15 from Max Staudt
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550#c16
--- Comment #16 from Michael Hirmke
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550#c17
Fabian Vogt
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550#c18
--- Comment #18 from Max Staudt
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550#c19
Max Staudt
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550#c20
--- Comment #20 from Michael Hirmke
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550#c21
--- Comment #21 from Michael Hirmke
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550#c22
Wolfgang Bauer
0x00007f30b0b5a640 in QTextLine::layout_helper(int) () from /usr/lib64/libQt5Gui.so.5
Do you have any idea what may have caused the notification? I somehow have the feeling it might be related to this: https://phabricator.kde.org/D5013 There is no bugreport/backtrace mentioned there, so hard to tell. IMHO it would sound reasonable that it hangs in QTextLine::layout_helper() then though. I will prepare a testing package with this patch.
An perhaps another interesting information: With Desktop Theme "Breeze" the problems seems to occur not as often as with "Air openSUSE".
Probably just coincidence I think. A desktop theme is just a bunch of SVG files... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550#c23
--- Comment #23 from Wolfgang Bauer
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550#c24
--- Comment #24 from Michael Hirmke
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550#c25
--- Comment #25 from Wolfgang Bauer
Your kio packages have version 5.26.0-5.1, while my installed default openSUSE versions already had 5.26.0-6.2. So I had to downgrade those two packages - was that really, what you wanted me to do?
Yes. That's just the build number, and it's lower because I branched from KDE:Frameworks5:LTS and not the standard Update repo. It is not really a "downgrade", actually it contains two additional fixes...
It didn't help, though: I installed both packages and rebootet the system, but the error remained unchanged 8-(
Well, what I suspect is that if a notification that triggers the freeze is still in the history, it will trigger the freeze again whenever a new notification appears. Would explain why it works fine for you for a while and then suddenly all notifications trigger the problem, even after a reboot. That patch only helps with new notifications though, that are emitted by kio's file operations. It probably won't help if the problem exists already. So you'd need to remove that history for a proper test IMHO. I'm not sure currently where this history is saved though. You say that removing .config/plasmarc helps, so try that (with the new packages installed). But I would actually rather suspect .config/plasma-org.kde.plasma.desktop-appletsrc... The safest test would be on a new user account of course. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550#c26
--- Comment #26 from Michael Hirmke
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550
Frerk Meyer
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550#c27
--- Comment #27 from Wolfgang Bauer
So the only cur at the moment really seems not use Air openSUSE as Desktop theme.
Well, I was using the "Air openSUSE" desktop theme since then on my (radeon) system without a single problem. But yesterday, I tried on a different (intel) system, and immediately encountered the same problem, every desktop notification froze Plasma. Strange enough, I was not able to reproduce it on a different user account, so I investigated the difference in the settings. It was related to the configured font! "Sans Serif 9" (which maps to "Arial" here) causes the freeze for me, with the default "Noto Sans 10" (or even "Sans Serif 10") everything works fine. Though I suspect it would also depend on other factors, like the exact font metrics or the DPI. The theme probably only comes into play because different themes may have different margins (which affects the text layout/rendering of course). So please try whether changing the font helps in your case as well (if only to confirm that you actually experience the same issue). I vaguely remember some upstream bug reports about this (in Qt)... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550#c28
--- Comment #28 from Wolfgang Bauer
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550#c29
--- Comment #29 from Michael Hirmke
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550#c31
--- Comment #31 from Wolfgang Bauer
It might be related to https://bugs.kde.org/show_bug.cgi?id=381154
Yes, I concur. I immediately thought this might be fixed now when I saw the corresponding commit... ;-) I couldn't reproduce the problem at all anymore though (with the latest Qt5/KF5/Plasma5 versions, i.e. 5.10.0/5.42.0/5.11.95 which don't have that fix yet). So I cannot say for sure yet. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550#c32
--- Comment #32 from Wolfgang Bauer
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550
Max Staudt
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550#c35
Michael Hirmke
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550#c36
Wolfgang Bauer
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550#c37
Wolfgang Bauer
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550
Tomáš Chvátal
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550#c38
--- Comment #38 from Wolfgang Bauer
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550
http://bugzilla.opensuse.org/show_bug.cgi?id=1013550#c39
Wolfgang Bauer
participants (2)
-
bugzilla_noreply@novell.com
-
bugzilla_noreply@suse.com