Version: (using KDE 4.0.4) Installed from: Fedora RPMs Description of problem: The screensaver does not start automatically after X minutes. I can lock the screen normally. The screensaver only starts if I explicitly re-apply it, each time I log in KDE, even if the system-settings says it is already enabled with X minutes delay. Version-Release number of selected component (if applicable): I'm running Fedora 9, KDE 4.0.4. Did not notice this issue in KDE 4.0.3 How reproducible: Always Steps to Reproduce: 1. enable the screensaver, set X minutes 2. log off KDE 3. log on Actual results: After X+1 minutes of inactivity the screensave does not start Expected results: The screensaver shouls start after X minues of inactivity Additional info: If I re apply it, after logging in KDE, then it starts after X minutes of inactivity.
fwiw, this seems difficult to reproduce (I can't), but there's a not insignificant # of folks seeing this, including mattr (as mentioned on #kde-devel irc the other day), this should be considerred confirmed (imo). See also: https://bugzilla.redhat.com/show_bug.cgi?id=448183
I have just tried KDE 4.0.5 and it seems to work again.
Spoke too early. It worked the first day, the it stopped again. There must be something that gets corrupted after an update (?). I'm still using xscreensaver (that works) but I'd rather stick to KDE's. Any help available?
what video hw/driver are you using? Still ati radeon?
Same situation. ati radeon (not fglrx). 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon RV250 [Mobility FireGL 9000] (rev 02) Fedora updated to the most recent rpms.
This has been fixed by Dirk Mueller a month ago. It is already fixed in: trunk and 4.1 branch: http://websvn.kde.org/?view=rev&revision=822339 4.0 branch: http://websvn.kde.org/?view=rev&revision=822345 Fedora 9: http://cvs.fedoraproject.org/viewcvs/rpms/kdebase-workspace/F-9/kdebase-workspace-4.0.5-screensaver-xautolock.patch?hideattic=0&rev=1.1&view=markup Rawhide: since upgrading to 4.0.84 (Rawhide has been tracking 4.1 development for a while) The first official KDE release with the fix will be 4.1.0.
actually, dirk's fix was suboptimal, to put it mildly. fixed properly for kde 4.2 and 4.1.1.