Bug 148758 - Does not autostart when translucencies are enabled
Summary: Does not autostart when translucencies are enabled
Status: RESOLVED DUPLICATE of bug 75254
Alias: None
Product: kscreensaver
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: kscreensaver bugs tracking
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-08-12 01:00 UTC by David
Modified: 2008-05-19 17:59 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 David 2007-08-12 01:00:14 UTC
Version:            (using KDE KDE 3.5.7)
Installed from:    Debian testing/unstable Packages
OS:                Linux

I use KDE with tranlucencies enabled, and I set the screensaver to black screen (impossible simpler).

If I manually lock the screen, it is OK.

But it never autostarts due to inactivity (of course, I expect it to autostart because it is configured like this).
Comment 1 David 2007-08-12 03:45:46 UTC
The bug is even worse than I thought at the beginning. Even locking the screen does not work, because some minutes later the screensaver "disappears", and to make matters worse you cannot do anything with the keyboard or mouse. I had to Ctrl+Alt+Backspace

Reflection (maybe tough, but I hope not a flame): I had to quit using translucencies, and why? Because a malfunction of kwin? No. Because a malfunction of the video driver? No. Because a malfunction of the screensaver. 

I do not know much about computing, but I think a screensaver must not be so tricky as kwin or the video driver. kscreensaver is being malfunctioning for many years, with and without translucencies: not autostarting, starting but disappearing thereafter, etc.

Although a desktop is terrific (KDE), if the screensaver does not work, users may think of switching to other desktops (gnome, xfce, etc).
Comment 2 Oswald Buddenhagen 2007-11-01 21:27:33 UTC
don't be so melodramatic. ;)
the main issue is a dupe and is fixed now.
i don't know what to make of the "disappears" - probably it crashes, maybe due to some driver bugs (using closed source drivers by any chance?). open a new report if you have some substantial information.


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