Bug 48537

Summary:	kdm isn't appearing when i do a lock screen
Product:	kdm	Reporter:	Paulo Dias <pcd>
Component:	general	Assignee:	kdm bugs tracker <kdm-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal	CC:	rdieter
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed In:

Description Paulo Dias 2002-10-01 09:35:13 UTC

Version:            (using KDE Devel)
Installed from:    Compiled sources
Compiler:          gcc 2.95.3 
OS:          Linux

I'm running kde 3.1 beta 2 (3.0.8 cvs version date 29/9/2002 -although this behaviour is current for almost a month now) compiled by hand in slackware 8.1.
The problem: when i click on the lock button, kdesktop_lock is properly called with the --forcelock option but instead of locking my area, running kscreensaver and opening a second X with the KDM logon, which is the standard procedure, only the kscreensaver is called.
No second X, no nothing. I've runned genkdmconf --no-old to toss the old scripts and create the news ones which appear to be fine in /opt/kde3/share/config/kdm, but still no new X (running Xfree86 4.2.1 BTW).
This was working till past month, now it appears to be broken. i've runned out of ideas. Calling kdesktop_lock via dcop also doesn't open a second KDM.

Comment 1 Oswald Buddenhagen 2002-10-01 14:51:57 UTC

Subject: Re:  New: kdm isn't appearing when i do a lock screen

well, this is intentional. most users didn't even know about this
feature (as the older genkdmconf picked up their old Xservers without
modification). those that were faced with it seemed highly confused by
it. the proper solution is to put buttons everywhere to explicitly open 
a new session - patch is at
http://lists.kde.org/?l=kde-core-devel&m=103248620916086&w=2 - but it's
too late to include it in kde 3.1.
you can re-enable the old behaviour by uncommenting the AUTO_RESERVE
define at the end of kdm/backend/dm.h.

Comment 2 Paulo Dias 2002-10-02 02:50:16 UTC

Subject: Re:  kdm isn't appearing when i do a lock screen

On Tuesday 01 October 2002 12:51, you wrote:

> well, this is intentional. most users didn't even know about this
> feature (as the older genkdmconf picked up their old Xservers without
> modification). those that were faced with it seemed highly confused by
> it. the proper solution is to put buttons everywhere to explicitly open
> a new session - patch is at
> http://lists.kde.org/?l=kde-core-devel&m=103248620916086&w=2 - but it's
> too late to include it in kde 3.1.
> you can re-enable the old behaviour by uncommenting the AUTO_RESERVE
> define at the end of kdm/backend/dm.h.

Thanks for your prompt response:) it's working now:)

best regards:)

Comment 3 adi 2002-10-03 20:41:06 UTC

For KDE 3.0.9 (SuSE8.1/binary rpms for 8.1) this feature seems all right.   I call "kdesktop_lock --forcelock" from a script on pressing fn+s on my notebook and I just dont want to have kdm letting a second user login. How can this be disabled?? Or: How can I just lock my screen with password query?

Comment 4 Oswald Buddenhagen 2002-10-09 03:07:08 UTC

ok, the patch made it into kde 3.1.

Comment 5 Behzad A 2022-02-09 19:20:02 UTC

*** Bug 449880 has been marked as a duplicate of this bug. ***