[opensuse-factory] Leap 42.2 - plasmashell freezing
Hi *, 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. Is this a known problem? Can I debug it and if so, how? TIA. Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Il 29/11/2016 20:32, Michael Hirmke ha scritto:
Hi *,
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. It'a frankenstein distro now ;)
A few more facts:
- The X server is xf86-video-intel.
Well, you can try to switch AccelMethod to uxa, something like: Section "Device" Identifier "Intel Graphics" Driver "intel" Option "AccelMethod" "uxa" EndSection (Search on google for more info about uxa VS sna) or get rid of xf86-video-intel. In this way Modeset driver is used instead of Intel. HTH. Daniele. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi Daniele, thx for your answer! [...]
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. It'a frankenstein distro now ;)
it was for a short time - a restore killed the useless monster :))
A few more facts:
- The X server is xf86-video-intel.
Well, you can try to switch AccelMethod to uxa, something like:
Section "Device" Identifier "Intel Graphics" Driver "intel" Option "AccelMethod" "uxa" EndSection (Search on google for more info about uxa VS sna)
I added this option and the driver obviously recognized it: [ 14.594] (II) UXA(0): Driver registered support for the following operations: [ 14.594] (II) solid [ 14.595] (II) copy [ 14.595] (II) composite (RENDER acceleration) [ 14.595] (II) put_image [ 14.595] (II) get_image But the plasmashell freezes till occurred.
or get rid of xf86-video-intel. In this way Modeset driver is used instead of Intel.
That didn't help either. The modeset driver was loaded without any problem, but the plasmashell freeze stayed.
HTH.
Daniele.
Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Il 29/11/2016 22:31, Michael Hirmke ha scritto:
But the plasmashell freezes till occurred.
or get rid of xf86-video-intel. In this way Modeset driver is used instead of Intel.
That didn't help either. The modeset driver was loaded without any problem, but the plasmashell freeze stayed.
HTH.
Daniele.
Bye. Michael.
Nothing in log files (~/.xsession-errors-:0 - /var/log/Xorg.0.log) ? Did you look at kde bugs ? Daniele. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi Daniele,
Il 29/11/2016 22:31, Michael Hirmke ha scritto:
But the plasmashell freezes till occurred.
or get rid of xf86-video-intel. In this way Modeset driver is used instead of Intel.
That didn't help either. The modeset driver was loaded without any problem, but the plasmashell freeze stayed. [...]
Nothing in log files (~/.xsession-errors-:0 - /var/log/Xorg.0.log) ?
no 8-(
Did you look at kde bugs ?
Yes, there are a few bugs related to plasmashell freezes with notifications, but none of them really fits exactly - and no solution at all.
Daniele.
Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 30 November 2016 at 09:55, Michael Hirmke <mh@mike.franken.de> wrote:
Hi Daniele,
Il 29/11/2016 22:31, Michael Hirmke ha scritto:
But the plasmashell freezes till occurred.
or get rid of xf86-video-intel. In this way Modeset driver is used instead of Intel.
That didn't help either. The modeset driver was loaded without any problem, but the plasmashell freeze stayed. [...]
Nothing in log files (~/.xsession-errors-:0 - /var/log/Xorg.0.log) ?
no 8-(
Did you look at kde bugs ?
Yes, there are a few bugs related to plasmashell freezes with notifications, but none of them really fits exactly - and no solution at all.
Daniele.
Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
https://bugzilla.redhat.com/show_bug.cgi?id=1193742 seems to have several commentaries with very similar symptoms -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wed, 2016-11-30 at 22:22 +0100, nicholas cunliffe wrote:
On 30 November 2016 at 09:55, Michael Hirmke <mh@mike.franken.de> wrote:
Hi Daniele,
Il 29/11/2016 22:31, Michael Hirmke ha scritto:
But the plasmashell freezes till occurred.
or get rid of xf86-video-intel. In this way Modeset driver is used instead of Intel.
That didn't help either. The modeset driver was loaded without any problem, but the plasmashell freeze stayed.
[...]
Nothing in log files (~/.xsession-errors-:0 - /var/log/Xorg.0.log) ?
no 8-(
Did you look at kde bugs ?
Yes, there are a few bugs related to plasmashell freezes with notifications, but none of them really fits exactly - and no solution at all.
Daniele.
Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
https://bugzilla.redhat.com/show_bug.cgi?id=1193742 seems to have several commentaries with very similar symptoms
Hi everyone. I hope this comes through OK, since I have had to change my e-mails setup for this list dramatically because my company automatically appends a massive signature including a picture to my e- mails. I am having the same issues on OpenSuse Tumbleweed using XOrg from: http://download.opensuse.org/repositories/X11:/XOrg/openSUSE_Factory/ and kernel 4.8.11-2.ge617052-default (don't judge). I also have TeamViewer, Pipelight, Citrix, freshplayer, Oracle Java etc installed so there is a chance it is just my environment. I too am running an Intel graphics card as primary. In fact, I am running an HP laptop (i7 with 12Gb RAM) with Intel and Radeon graphics, here is an xrandr --listproviders: Providers: number : 2 Provider 0: id: 0x7c cap: 0xb, Source Output, Sink Output, Sink Offload crtcs: 4 outputs: 5 associated providers: 0 name:Intel Provider 1: id: 0x53 cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload crtcs: 2 outputs: 2 associated providers: 0 name:OLAND @ pci:0000:01:00.0 I often have to manually kill and restart plamashell since all widgets, including the task bar, lock up. Windows can still be flipped with alt- tab and I can still launch a terminal using the keyboard shortcut I had set up. Compositing and desktop effects (such as wobbly windows etc) still seem to work fine while this is locked up. I can still open save/open dialogs. I can't test if plasmashell does this under wayland since it restarts a lot all by itself to the point of being unusable. Gnome seems unaffected (but not for me) and everything else runs fine. The logs say nothing. One second it is working and chatting loudly, the next second nothing at all in the logs. My XOrg log looks pristine, and the laptop runs smoothly and is generally great to use. I am up to date fully (except for the very last update not having a reboot yet). I have tried getting update and/or get rid of some widgets, but I run WAY TOO MANY widgets! I hate not being able to rely on the clock though. It seems very random. Just when I think it is fixed, all of a sudden it locks again. It seems to happen most when a widget updates (such as when I get a message) or I am about to go to lunch or really busy. I am not sure if it is related, the only strange parts in my .xsession logs relate to screen changes detected, as well as an annoying accompanying OSD that tells me I have "No External Display". org.kde.kurifilter-ikws: "http://download.opensuse.org/repositories/X11 :/XOrg/openSUSE_Factory/" org.kde.kurifilter-ikws: "4.8.11-2.ge617052-default" org.kde.kurifilter-ikws: "Providers: number : 2 Provider 0: id: 0x7c cap: 0xb, Source Output, Sink Output, Sink Offload crtcs: 4 outputs: 5 associated providers: 0 name:Intel Provider 1: id: 0x53 cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload crtcs: 2 outputs: 2 associated providers: 0 name:OLAND @ pci:0000:01:00.0" org.kde.kurifilter-ikws: "kscreen.kded: Change detected" console.error: CustomizableUI: unable to normalize widget kscreen.kded: displayBtn triggered kscreen.kded: displayBtn triggered kscreen.kded: Too fast, cowboy kscreen.kded: displayButton: 1 kscreen.kded: doApplyConfig() kscreen.kded: Monitor for changes: false kscreen.kded: Config applied kscreen.kded: Monitor for changes: true kscreen: Requesting missing EDID for outputs (119) kscreen.kded: Change detected kscreen.kded: KScreen::Output( 119 "eDP1" connected enabled QPoint(0,0) QSize(1920, 1080) "125" ) kscreen.kded: Saving current config to file kscreen.kded: Config saved on: "/home/ben/.local/share/kscreen/de797ccaf4b129478af23f23a6adbfe7" kscreen.kded: KScreen::Output( 119 "eDP1" connected enabled QPoint(0,0) QSize(1920, 1080) "125" ) libva info: VA-API version 0.39.3 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib64/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_0_39 libva info: va_openDriver() returns 0 libva info: VA-API version 0.39.3 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib64/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_0_39 libva info: va_openDriver() returns 0 All of the bugs on KDE seem to be "almost" related, but not quite. -- Ben -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi nicholas, [...]
https://bugzilla.redhat.com/show_bug.cgi?id=1193742 seems to have several commentaries with very similar symptoms
yes, similar - but none of them really fits. Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Il 01/12/2016 21:00, Michael Hirmke ha scritto:
Hi nicholas,
[...]
https://bugzilla.redhat.com/show_bug.cgi?id=1193742 seems to have several commentaries with very similar symptoms
yes, similar - but none of them really fits.
Bye. Michael.
Well, time to fill a new bugreport.. IMHO, on both side (kde and suse) for better tracking the problem. Daniele. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi Daniele,
Il 01/12/2016 21:00, Michael Hirmke ha scritto:
Hi nicholas,
[...]
https://bugzilla.redhat.com/show_bug.cgi?id=1193742 seems to have several commentaries with very similar symptoms
yes, similar - but none of them really fits.
Bye. Michael.
Well, time to fill a new bugreport.. IMHO, on both side (kde and suse) for better tracking the problem.
seems to be a good idea. Only thing is: I don't have any error messages, useful logs etc. I can provide the same description I wrote here, thats it. And from my experience this is not enough for developers to even notice the problem. But I'll try it once more.
Daniele.
Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Just stumbled on this thread. Me too. Same repo, stock kernel. I'm on the NVidia proprietary driver though, on a desktop with stock taskbar. I noticed memory goes up (20GiB yesterday) while plasmashell is locked up - I found it before it had caused OOM for once. CPU tends to go moderately high (40-60%) to 100% and is very abnormal to it's nominal operation - and there seems to be a short time (sufficient for human interaction) that things escalate from working-> frozen. Kwin/dbus are both alive and windows can be manipulated, not sure about the health of kded - is there some quick check via qdbus to see if kded is up and in good health? Everything plasma related though just ignores input. And before someone quips that's not this bug, I believe it is. App doesn't respond to kquitapp, so I kill it. -Jason On Sat, Dec 3, 2016 at 5:02 AM, Michael Hirmke <linux@mike.franken.de> wrote:
Hi Daniele,
Il 01/12/2016 21:00, Michael Hirmke ha scritto:
Hi nicholas,
[...]
https://bugzilla.redhat.com/show_bug.cgi?id=1193742 seems to have several commentaries with very similar symptoms
yes, similar - but none of them really fits.
Bye. Michael.
Well, time to fill a new bugreport.. IMHO, on both side (kde and suse) for better tracking the problem.
seems to be a good idea. Only thing is: I don't have any error messages, useful logs etc. I can provide the same description I wrote here, thats it. And from my experience this is not enough for developers to even notice the problem. But I'll try it once more.
Daniele.
Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Why is this thread here on os-factory? I fail to see what it has to do with the development of Tumbleweed. It should be on plain os@opensuse.org or even better, filed as a bug over at bugs.opensuse.org //Bjørn -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Bjørn Lie composed on 2016-12-03 22:33 (UTC+0100):
Why is this thread here on os-factory? I fail to see what it has to do with the development of Tumbleweed.
If you'd been around for the OP you should have known that 42.2 wouldn't work right, so the OP upgraded to BS kernel, BS Xorg and BS KDE in trying to solve a problem apparently common to multiple distros' users of various gfxchips.
It should be on plain os@opensuse.org
Not the best place. IMO, better 3rd-best on opensuse-kde, next here (and appropriate), best on a kde list, or maybe an Xorg list.
or even better, filed as a bug over at bugs.opensuse.org
Better yet, upstream. KDE freezes in recent weeks and months are not unique to openSUSE, or to Intel or NVidia gfx. I see little difference between this thread's complaints and those in Fedora, Debian and generic Linux forums. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi,
Why is this thread here on os-factory? I fail to see what it has to do with the development of Tumbleweed.
Felix explained it.
It should be on plain os@opensuse.org or even better, filed as a bug over at bugs.opensuse.org
I filed a bug for this problem yesterday on bugs.opensuse.org and I will file it on the KDE bugzilla, too, as soon as I got the time.
//Bj?rn
Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi,
Why is this thread here on os-factory? I fail to see what it has to do with the development of Tumbleweed.
Felix explained it.
It should be on plain os@opensuse.org or even better, filed as a bug over at bugs.opensuse.org
I filed a bug for this problem yesterday on bugs.opensuse.org and I will file it on the KDE bugzilla, too, as soon as I got the time.
//Bj?rn
Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
tirsdag den 29. november 2016 20.32.00 CET skrev Michael Hirmke:
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
I have had some freezes also on my T410 with intel gfx (i915 driver). Hasn't been triggered by notifications though. Only upgraded to 42.2 two days ago, and am yet to see any pattern in the freezes. But fiddling with desktop effects/compositing settings would be my first step. Toggle effects off temporarily with alt+shift+f12 and see if you can still reproduce it. After you have confirmed that the issue is triggered by effects, you can start to zone in and disable the specific effects which might fall under suspicion. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi Martin,
tirsdag den 29. november 2016 20.32.00 CET skrev Michael Hirmke:
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
I have had some freezes also on my T410 with intel gfx (i915 driver). Hasn't been triggered by notifications though. Only upgraded to 42.2 two days ago, and am yet to see any pattern in the freezes.
But fiddling with desktop effects/compositing settings would be my first step. Toggle effects off temporarily with alt+shift+f12 and see if you can still reproduce it.
Thats what I wrote:
- switching off the compositor doesn't help.
[...] Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (9)
-
Ben Holmes -
Bjørn Lie -
Daniele -
Felix Miata -
Jason Newton -
linux＠mike.franken.de -
Martin Schlander -
mh＠mike.franken.de -
nicholas cunliffe