Bug 188408 - Don't show OSD when screensaver is active
Summary: Don't show OSD when screensaver is active
Status: RESOLVED DUPLICATE of bug 179924
Alias: None
Product: kscreensaver
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: kscreensaver bugs tracking
Depends on:
Reported: 2009-03-29 17:16 UTC by Davide Rondini
Modified: 2009-04-13 17:10 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:


Note You need to log in before you can comment on or make changes to this bug.
Description Davide Rondini 2009-03-29 17:16:08 UTC
Version:           2.02 (using KDE 4.2.1)
OS:                Linux
Installed from:    Fedora RPMs

When the screensaver is activated (for example when you leave the PC idle for a while), but Amarok is playing in background, when a message from Amarok's on screen display (OSD) appears, the screen blinks for a moment. I use the black screen as a screensaver. I use KDE 4.2.1 and Amarok 2.0.2 taken from Fedora 10 x86_64 repositories. I enabled Kwin's Desktop effects (I don't know if it matters).

How to reproduce:

1. Start a playlist with Amarok.
2. Start screensaver (automatically or by blocking session)
3. wait for the song change (or any event which generates a amarok OSD message)
Comment 1 Mark Kretschmann 2009-03-29 18:57:44 UTC
Well the question is if this can be seen as an Amarok bug, or rather as a problem with a different component (e.g. window manager). 

At any rate, we might be able to detect that a screensaver is running (is this possible?), and then suppress the OSD.

How to detect this, does anyone know?
Comment 2 Dan Meltzer 2009-03-29 19:07:20 UTC
I'm pretty sure this is a kwin bug... I've seen it in other cases as well, an osd + full screen window does not play well together.
Comment 3 Mark Kretschmann 2009-03-29 19:07:58 UTC
Yay, just asked some friendly KDE devs on IRC, and got this reply:

"<mpyne> markey: qdbus org.freedesktop.ScreenSaver /ScreenSaver org.freedesktop.ScreenSaver.GetActive"

So I guess we could try that :)
Comment 4 Seb Ruiz 2009-04-01 13:05:53 UTC
Doesn't hurt to add that check, but fwiw, I coudln't reproduce the problem.
Comment 5 Kevin Funk 2009-04-04 12:05:27 UTC
This really shouldn't be solved by Amarok. As Dan said, this is a bug in kwin or something as the screensaver should not be overlapped by any widget if active. I've seen knotify "breaking through" aswell, but I think it got fixed by some KDE/Qt upgrade. Amarok's OSD doesnt pop up here, so cant reproduce.
Comment 6 Mark Kretschmann 2009-04-04 12:19:40 UTC
Ok, Kevin is probably right then. No need to add ugly workarounds for bugs in other software (which will get fixed anyway, most likely).

Please report the bug at the right place then.
Comment 7 Dan Meltzer 2009-04-04 15:32:35 UTC
Or, you know, you could reassign this bug...
Comment 8 Martin Flöser 2009-04-04 16:18:09 UTC
given the same problem with Plasma Notifications in bug #179924 and this had to be fixed in Plasma, I think this has to be fixed in Amarok as well.

So back to Amarok, but I keep kwin ML in CC.
Comment 9 Lubos Lunak 2009-04-04 16:29:28 UTC
It is a responsibility of the screen locker to hide everything else on the screen. There must be a bug in its code.
Comment 10 Lubos Lunak 2009-04-04 16:31:37 UTC
*sigh* the new "improved" bugzilla ui sucks so badly.
Comment 11 Chani 2009-04-11 18:16:55 UTC
from my memory of the screensaver restacking code, I don't know what could be wrong. there's actually a confused comment in there from me... but in new code, and afaik we've had this problem since kde3 or longer. lubos, have you looked at that code recently? workspace/krunner/lock/lockprocess.cc:1311
Comment 12 Oswald Buddenhagen 2009-04-13 17:10:06 UTC

*** This bug has been marked as a duplicate of bug 179924 ***