Bug 248667 - screensavers not recovering from emergency blackout
Summary: screensavers not recovering from emergency blackout
Status: RESOLVED DUPLICATE of bug 179924
Alias: None
Product: kscreensaver
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR minor
Target Milestone: ---
Assignee: kscreensaver bugs tracking
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-22 08:36 UTC by Ben Gouhier
Modified: 2011-05-12 06:52 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ben Gouhier 2010-08-22 08:36:45 UTC
Version:           unspecified (using KDE 4.4.5) 
OS:                Linux

I'm using the science screensaver (bowl wandering on a screenshot of the screen), but when a notification pops up (for instance amarok changes songs, and uses knotify to display a notification), the screens turns black BUT the bowl of the screensaver uncovers it. Its a bit hard to explain..

Reproducible: Always

Steps to Reproduce:
Find away to trigger notifications from knotify regularly (every 2 minutes for intance). The easiest way is to configure amarok to use knotify and to launch a playlist

Configure the 'science' screensaver to trigger after 1 minute (just not to wait too long). I'm using sphere mode but i think all the modes do the same.

Wait for the screensaver to start. It should work.

Wait until amarok changes song and displays a notification via knotify.

Actual Results:  
The screen should turn black but the scrensaver goes on, slowly uncovering the previous screenshot.

Expected Results:  
The scrren should not turn black.

widget style: Kaleban but also happen with other styles.
Using up to date Debian squeeze with radeon free driver with kms, kernel 2.6.32, KDE 4.4.5, french locale.
 Also happens on another laptop with Linux mint 9 Kde (Ubuntu 10.04), kernel 2.6.32, fglrx, no kms, KDE 4.5.0, italian locale.
Comment 1 Oswald Buddenhagen 2010-08-22 10:43:41 UTC
the turning black is explained in bug 179924, comment 19 explains why it stays black.
Comment 2 Ben Gouhier 2011-05-12 06:52:08 UTC

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