KDE 3.2.1 on Mandrake 9.2 (compiled from sources)

I have a similar problem.  I use 'Slide Show' as my screen saver to display images.  After some time it fails to start after the specified time of in activity.  How ever screen is put to standby by power manager after the specified time.

Screen Saver Settings:
    Start screen saver after : 5min
    Make screen saver aware of power management : unchecked
    require password : unchecked

Display Power Control Settings
   standby ; 20 min
   suspend : 30 min
   power off : disabled.

Let me know what more information I can produce to track this bug.

KDE 3.2.1 on Gentoo
I have the same problem. The screensaver does not always start after the specified time. Sometimes it works sometimes it doesn't. Very annoying. 

I have "Make screen saver aware of power management" checked. The screensaver works as expected whenever the desktop is left idle.

This is until I leave the computer for longer and DPMS kicks in. Once DPMS has activated, the screensaver no longer functions at any future time until I log out.

Unchecking "Make screen saver aware of power management" appears to fix the problem, but obviously it would be useful if it worked as expected.

CVS commit by howells: 

This is a partial fix for 76746. It at least stops the screensaver from crashing if a non existing 
directory is added.

the screensaver crashes on the QFileInfoListIterator it(*fileinfolist); line but unfortunately my Qt is 
compiled without debugging symbols and my poor iBook 800 really can't deal with recompiling the whole lot 
with debugging symbols again so I'm going to leave this bug open.

Also I'm not sure whether this should be considered a bug in KUrlRequester or not -- there is a 
KFile::LocalOnly mask, but this only stops local files being shown in the dialog, maybe KUrlRequester 
should have an isLocal() function or similar if a lan:// or something URL is entered.

CCMAIL: 76746@bugs.kde.org

----------------------------------------------------------------------


  M +4 -0      slideshow.cpp   1.25


--- kdeartwork/kscreensaver/kdesavers/slideshow.cpp  #1.24:1.25
@@ -865,4 +865,8 @@ void kSlideShowSaver::traverseDirectory(
 {
   QDir dir(dirName);
+  if (!dir.exists())
+  {
+     return ;
+  }
   dir.setFilter(QDir::Dirs | QDir::Files);
 

Oops, comment added to wrong bug, sorry.

I have the exact same problem as Jan.  This only started happening when I installed KDE from CVS a day or so before 3.3.0 was released.  I am using xscreensaver 4.17.  A screensaver will start perfectly when the test button is prressed but if you then lock the screen or wait for the screensaver to start there will just be a blank screen.  This does not seem to happen with non-xscreensaver screensavers and is seems to be unaffected by DPMS option.  I am also using qt-copy with patches applied.

Not sure if this is the same bug, but is very similar.

For me it is all screensavers (not just kde or gl). I saw the same behavior on later 3.2 versions, and just updated to 3.3 but it is still the same.

The screensavers work fine when using the "Test" button in the configuration, but when the screen is locked, the screensaver does not come on. The screen lock works fine.

On the console, I am getting messages like this:

SetClientVersion: 0 8
SetGrabKeyState - disabled
QPixmap: Cannot create a QPixmap when no GUI is being used

X Error in laser:
X Error of failed request: BadWindow (invalid window parameter)
  Major opcode of failed request:  3 (X_GetWindowAttributes)
  Resource id in failed request:  0x7
  Serial number of failed request:  2071

I'm using SuSE 9.2, and the same problem happened when I used SuSE's rpms to upgrade 9.1 to kde 3.3. For me, the screen saver will not work like the others, but after 10 min, the screen will turn off, even though the DPMS power off settings are all at 20 min.

If I change the DPMS settings, then it starts to work at the proper times.

Err, I should add that my screen saver is set to go on at 10 min, and the screen off after 20 min. Lock the screen with password is checked, and set at 60 seconds, though in the kdesktoprc file, the password timeout parameter is 60000.

My screensaver was working fine from CVS until two weeks ago. Then, screen just goes blank, on time, but no screen saver is shown. Test works and shows the proper screensaver. Xscreensaver works when used (but I do not load the daemon with KDE). This is a new "feature" in KDE 3.4 Alpha 1.

*** This bug has been confirmed by popular vote. ***

The bugs still there in a recent CVS with xscreensaver 4.19.  Is this just because I'm using a patched QT?

This is what I get:

kdesktop: SaverEngine: starting saver
kdesktop_lock: app 0 0 false 0 0
kdecore (KConfigSkeleton): Creating KConfigSkeleton (0x8105e60)
kdecore (KConfigSkeleton): KConfigSkeleton::readConfig()
kio (KSycoca): Trying to open ksycoca from /var/tmp/kdecache-user/ksycoca
kdesktop: relPath=System/ScreenSavers/
kdesktop: mForbidden: false
kdesktop: Saver window Id: 46137351
kdesktop: Starting hack: /usr/bin/kxsrun
kdesktop: GreeterPlugin classic (classic, Username + password (classic)) loaded
QPixmap: Cannot create a QPixmap when no GUI is being used
QPixmap: Cannot create a QPixmap when no GUI is being used
kxsrun: saverdir is/usr/lib/xscreensaver/glmatrix                    

X error in glmatrix:
X Error of failed request:  BadWindow (invalid Window parameter)
  Major opcode of failed request:  3 (X_GetWindowAttributes)
  Resource id in failed request:  0x7
  Serial number of failed request:  266
  Current serial number in output stream:  267
WARNING: DCOPReply<>: cast to 'QStringList' error
WARNING: DCOPReply<>: cast to 'QString' error
kdesktop: LockProcess: stopping saver
kdesktop: SaverEngine: lock exited
kdesktop: virtual bool KPixmapServer::x11Event(XEvent*): request for DESKTOP1
kdesktop: virtual bool KPixmapServer::x11Event(XEvent*): request for DESKTOP1

If kdesktop is killed the screensaver runs (but where the desktop was :-S )
Could it be to do with how kdesktop is handling the root window?

Using KDE 3.4

KDE's screen-savers run well. but from XScreenSaver package don't.

I suppose this is due to -window-id parameter given to screensaver:
julia -window-id 46139560 -count 1000 -cycles 20 -delay 10000 -ncolors 200
This example runs within preview window.

Wrong -window-id parameter rejected with message:
X error in julia:
X Error of failed request:  BadWindow (invalid Window parameter)
  Major opcode of failed request:  3 (X_GetWindowAttributes)
  Resource id in failed request:  0x24
  Serial number of failed request:  295
  Current serial number in output stream:  296

And screensaver ends leaving black screen.

#13 is the standard xscreensaver 4.17 bug

(Stephan) If this is indeed an xscreensaver (and not a KDE) bug, shouldn't this be closed INVALID/WONTFIX?

I can't tell if all the other reporters share the same problem. If anyone would update their xscreensaver to > 4.19, we'd know

I can confirm that at least a handful of users on the kde-redhat-users mailing list who've upgraded xscreensaver have reported the problems fixed.

"Re-unconfirming" pending (more) feedback regarding xscreensaver version/upgrades.

I seem to have a similar problem om mandriva le2005 with xscreensaver 4.20.

After being logged in for a few days (?) my screensaver won't start anymore in KDE. When I start a new session it works again in that session.

I have "make aware of powermanagement" turned on, which I saw in another comment as a factor... Any way I can find out more?

Now I'm on KDE 3.4.2, and I still have the same problem. I have the screensaver set to start after 5 minutes, but nothing happens if DPMS has previously blanked the screen and "Make aware of power management" is selected.

The screensaver always starts if I lock the screen or click "Test".

sound the same ...

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