http://bugzilla.opensuse.org/show_bug.cgi?id=1013550 http://bugzilla.opensuse.org/show_bug.cgi?id=1013550#c1 Tomas Jensen <tcj@tomas.dk> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tcj@tomas.dk --- Comment #1 from Tomas Jensen <tcj@tomas.dk> --- 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 -- 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 <tcj@tomas.dk> --- (In reply to Tomas Jensen from comment #1)

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 http://bugzilla.opensuse.org/show_bug.cgi?id=1013550#c4 --- Comment #4 from Frerk Meyer <frerk.meyer@gmx.de> --- I have the same problem here on my Thinkpad T400s since upgrading to openSuSE Leap 42.2 coming from openSuSE Leap 42.1 (no problem). Today there was a patch coming in with a link to a bug id I had no access to, which was for xf86-video-intel. But I searched and found this description. I tried to reproduce by adding / locking and unlocking widgets but could not trigger the freeeze with it. I will wait and watch if the bug shows up again or not. If it shows up I will try the 'uxa' conf trick. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1013550 Alessio Adamo <alessio.adamo@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alessio.adamo@gmail.com -- 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#c8 --- Comment #8 from Michael Hirmke <opensuse@mike.franken.de> --- For me switching to the modesetting driver didn't help. Instead I got some crashes on top 8-( 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#c9 Max Staudt <mstaudt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mstaudt@suse.com --- Comment #9 from Max Staudt <mstaudt@suse.com> --- Just to be sure: Do you have hybrid graphics, i.e. an AMD or NVIDIA graphics chip besides the integrated Intel graphics? -- 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#c11 --- Comment #11 from Max Staudt <mstaudt@suse.com> --- Is the NVIDIA chip completely disabled in the BIOS? -- 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#c12 --- Comment #12 from Michael Hirmke <opensuse@mike.franken.de> --- At the moment I only have remote access to the notebook. The Nvidia adapter is not visible through lspci and there are no messages in the log for it - does this answer your question? -- 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#c14 --- Comment #14 from Michael Hirmke <opensuse@mike.franken.de> --- Besides the problem, that plasmashell freezes on every notfication, I have no problem with graphics whatsoever. Switching off notifications cures the problem - which is the actual situation. So if it takes too much time and power, just close the bug. It is a bit annoying, but not critical. But: Are you really sure, that it has to do with the graphics adapter/driver? I am not. For me it looks like a bug either in plasmashell or in the notifications applet. -- 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#c16 --- Comment #16 from Michael Hirmke <opensuse@mike.franken.de> --- I tried each and everything today to track it down, and the most astonishing fact from my original bug report is still that one: - 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. It is reproducable. There must be a problem with plasmahshell itself. In my plasmarc the only entry, though is the one for the desktop theme, which in my case is "Air openSUSE". -- 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#c18 --- Comment #18 from Max Staudt <maximilian.staudt@suse.com> --- Yep, what Fabian said. I tried to reproduce this on a Sandy Bridge machine just to be sure, and indeed notifications work as they should. This is probably because it's a fresh install though. How long do you think I need to leave the machine running for the error to come up? First one to post a backtrace wins :) -- 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#c20 --- Comment #20 from Michael Hirmke <opensuse@mike.franken.de> --- As always: If you are waiting for the bug, it won't occur 8-< Because I deleted plasmarc yesterday for testing purposes, I have to wait for the error for an uncertain amount of time. This is the behaviour, I described in that single topic. As soon as the error shows up, I'll take the backtrace. -- 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#c22 Wolfgang Bauer <wbauer@tmo.at> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wbauer@tmo.at --- Comment #22 from Wolfgang Bauer <wbauer@tmo.at> --- (In reply to Michael Hirmke from comment #21)

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#c24 --- Comment #24 from Michael Hirmke <opensuse@mike.franken.de> --- The notfication in this case comes from removing the clock applet. It should show the "Undo" button. But in other cases, notifications for example from the nm-applet also cause the hang. 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? It didn't help, though: I installed both packages and rebootet the system, but the error remained unchanged 8-( -- 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 <opensuse@mike.franken.de> --- - I moved plasmarc and plasma-org.kde.plasma.desktop-appletsrc out of the way for my actual user. - After a restart everything worked without errors/hangs. - I configured my desktop environment roughly as it was before. - Still everything worked as expected. - I rebooted the machine for a second time and the error/hang was back. - Same procedure for a completely new user. - Same procedure with and without your new packages. - This was with "Air openSUSE" Desktop Theme. I then switched to "Breeze" and repeated every step - and got no more hangs. - I forced reinstallation of frameworkintegration-plugin, plasma-framework, plasma-framework-components, plasma-framework-lang and plasma-framework-private, because Air openSUSE is part of plasma-framework, but that didn't help either. So the only cur at the moment really seems not use Air openSUSE as Desktop theme. -- 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#c27 --- Comment #27 from Wolfgang Bauer <wbauer@tmo.at> --- (In reply to Michael Hirmke from comment #26)

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#c29 --- Comment #29 from Michael Hirmke <opensuse@mike.franken.de> --- Ok, finally I had the time to test your observations. And yes, I can confirm that changing the font to Noto Sans cures the problem. I tried the following fonts as "General Font": Good: - Nobile 9 - Noto Sans 9 Bad: - Arial 9 - Droid Sans 9 - Liberation Sans 9 It seems, that primarily fonts are causing the problem, that look more condensed, while fonts looking wider are working without causing problems. Sadly I better like the more condensed ones. -- 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 <wbauer@tmo.at> --- Correction: I actually CAN still reproduce it (I just forgot to switch the desktop theme to "Air openSUSE"). Unfortunately, that upstream commit doesn't fix it either. -- 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#c35 Michael Hirmke <opensuse@mike.franken.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #35 from Michael Hirmke <opensuse@mike.franken.de> --- Can't test it any more, because my notebook now runs Tumbleweed. No Problems so far with this release regarding freezes of plasmashell. -- 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#c37 Wolfgang Bauer <wbauer@tmo.at> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |akontsevich@gmail.com --- Comment #37 from Wolfgang Bauer <wbauer@tmo.at> --- *** Bug 1111769 has been marked as a duplicate of this bug. *** -- 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#c38 --- Comment #38 from Wolfgang Bauer <wbauer@tmo.at> --- It seems that this will finally be fixed in Plasma 5.16, probably as a side-effect of the notification rewrite/redesign. At least I cannot reproduce the freeze anymore since upgrading to the beta (no other changes to the system), with the same fonts that still reliably caused the freeze with 5.15.5. It's not feasible to backport the changes to Leap 15.0/15.1 though I think. -- You are receiving this mail because: You are on the CC list for the bug.