| Summary: | screensaver doesn't turn on | ||
|---|---|---|---|
| Product: | [Unmaintained] kscreensaver | Reporter: | Victor <mcquantum> |
| Component: | general | Assignee: | kscreensaver bugs tracking <kscreensaver-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | bluedzins, cnrpub, david.maillists, fago, h, jm, js, jsvrp.gw, kde-bugs, kde, l.lunak, linus.sylven, Marcin.Kasperski, robert.voigt, sunnysachanandani, theosib, wajih_ahmed |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Slackware | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Victor
2004-02-15 00:53:57 UTC
I actually got it to work eventually with kde 3.2.0 by setting it up from Ctl Ctr. I am wondering, is it there a bug such that right-clicking on the desktop and setting up the screen saver doesn't work, or in 3.2.0 it is not supposed to work at all unless it is set up from the control center? I'm having problems with this as well. Test works great. but when I go idle for x many mins and the screen saver *should* turn on.. it doesn't. instead it just freezes the image. So if I'm just sitting here and it "turns on" I don't know this until I move the mouse or hit a key and the screen will update. As an update to this I was able to get a few screen savers to actually work. Blank Screen, Clock and Polygons. Only way tho was I checked the "Make aware of power management" The rest however just freeze the screen. (I want my swarms :'( RUN FOR IT LITTLE WHITE LINE!) The Swarm screensaver is broken and indeed just appears to freeze the screen. Was the Swarm screensaver involved? If you chose another one does it work? Thanks. irreproducible, other than bug 74663 (the one stephen observed). ok, there are quite some very similar reports. lats make this one the "master". from where it is set is most certainly irrelevant. the other bugs indicate that it is sort of random. *** Bug 76746 has been marked as a duplicate of this bug. *** *** Bug 93045 has been marked as a duplicate of this bug. *** *** Bug 102341 has been marked as a duplicate of this bug. *** *** Bug 118873 has been marked as a duplicate of this bug. *** *** Bug 122680 has been marked as a duplicate of this bug. *** *** Bug 128610 has been marked as a duplicate of this bug. *** *** Bug 129062 has been marked as a duplicate of this bug. *** *** Bug 131967 has been marked as a duplicate of this bug. *** *** Bug 136161 has been marked as a duplicate of this bug. *** *** Bug 136891 has been marked as a duplicate of this bug. *** *** Bug 137070 has been marked as a duplicate of this bug. *** *** Bug 140687 has been marked as a duplicate of this bug. *** *** Bug 76008 has been marked as a duplicate of this bug. *** *** Bug 137591 has been marked as a duplicate of this bug. *** this is by far the most reported kscreensaver issue - some of the duplicates have in turn duplicates ... bug #128610 documents a failed attempt to fix it. bug #136315 has some good analysis and a patch. I've reported bug #136315: it has a patch and should at least fix some of the dupes. But probably not all or even most of them: There does not seem to be a single bug only here. I don't think it was a good idea to merge all "very similar" reports to this one. I'm pretty sure at least some of those have been fixed meanwhile, but with the mess this bugreport is right now it's hard to tell what still needs fixing. I'd suggest to close this one (no response from reporter anyway) and whoever still has some problem with 3.5.7 should file reopen their duplicate or file a new one. i *think* i fixed this now ... What does now refer to? I want to upgrade to a version which includes the fix. I'm using kde-base/kscreensaver-3.5.7 on gentoo atm. *** Bug 148758 has been marked as a duplicate of this bug. *** *** Bug 152377 has been marked as a duplicate of this bug. *** *** Bug 176824 has been marked as a duplicate of this bug. *** |