Bug 129209 - KDE fails to start screensaver / auto-lock display after upgrade 3.5.2 -> 3.5.3
Summary: KDE fails to start screensaver / auto-lock display after upgrade 3.5.2 -> 3.5.3
Status: RESOLVED DUPLICATE of bug 128610
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: Slackware Linux
: NOR normal
Target Milestone: ---
Assignee: Stephan Kulow
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-06-15 18:10 UTC by Halim I
Modified: 2006-06-15 19:17 UTC (History)
0 users

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Halim I 2006-06-15 18:10:44 UTC 
Version:            (using KDE KDE 3.5.3)
Installed from:    Slackware Packages
OS:                Linux

Upon upgrading from KDE 3.5.2 -> 3.5.3 on a vanilla Slackware-current system, the KDE session does no longer auto-lock the display after xx minutes of inactivity. No settings have been change since upgrading (using standard Slackware-packages from -current). The problem exists for multiple users on the same system, and only on the computers upgraded to 3.5.3.
Screensaver is set to 10 minutes, and lock for another 180 seconds. This varies from user to user, but the failure to start screensaver is consistent. ~/.xsession-errors does not contain any relevant information.

Please advise how to debug in order for us to contribue to solving this bug.
Comment 1 Stephan Kulow 2006-06-15 19:17:32 UTC 

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