[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [kscreensaver] [Bug 224200] multiple kblankscrn.kss in memory
From:       Wolfgang Bauer <wbauer () tmo ! at>
Date:       2014-05-14 18:26:55
Message-ID: bug-224200-17878-3rsusb5E7M () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=224200

--- Comment #58 from Wolfgang Bauer <wbauer@tmo.at> ---
(In reply to comment #57)
> I just noticed the same issue in Kubuntu 14.04 (with kclock.kss).
> 
Again, Kubuntu 14.04 ships kde-workspace 4.11.8, this should be fixed in
4.11.9.

I have no idea when (K)Ubuntu releases updated packages, but according to
https://launchpad.net/ubuntu/+source/kde-workspace an update for 14.04 is
already proposed at least.

> Curiously, it does NOT occur in the 4.11.3 KDE environment available with
> Linux Mint Debian, which does seem to use the same kscreensaver code. Could
> that have something to do with the fact I use the proprietary fglrx Radeon
> driver under LMDE as opposed to the open source driver under Kubuntu?
Maybe, or maybe it depends on the Xorg version or something else.
I have no idea, sorry.

On my openSUSE 13.1 systems (one with radeon and one with intel driver) I could
only reproduce this issue with kswarm.kss and kblankscrn.kss (I haven't really
tried _all_ though, kclock.kss definitely did not stay in memory here).
But IMHO _all_ screensavers should actually keep running after unblanking the
screen in the grace period.

Well, my guess is that they get killed by X/die themselves because some
operation they do is now invalid when the screenlocker window is not there any
more, or something like that. And that behaviour might differ across
distributions/drivers/Xorg versions I suppose.

-- 
You are receiving this mail because:
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]