Bug 129209

Summary:	KDE fails to start screensaver / auto-lock display after upgrade 3.5.2 -> 3.5.3
Product:	[I don't know] kde	Reporter:	Halim I <yallaone>
Component:	general	Assignee:	Stephan Kulow <coolo>
Status:	RESOLVED DUPLICATE
Severity:	normal
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Slackware
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

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 ***