Bug 493268 - Kdesktop_lock does not work on multiuser systems (and how to fix this)
Summary: Kdesktop_lock does not work on multiuser systems (and how to fix this)
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kdebase
Version: 4.7
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
: ---
Assignee: Than Ngo
QA Contact: desktop-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-04-01 08:00 UTC by Staffan Hamala
Modified: 2012-06-20 16:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 498990 499442 (view as bug list)
Environment:
Last Closed: 2012-06-20 16:11:41 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Staffan Hamala 2009-04-01 08:00:56 UTC
Description of problem:

Kdesktop_lock does not run on multiuser systems. If one user has a kdesktop_lock.bin running, it won't start for another user!

Version-Release number of selected component (if applicable):

RHEL 4.7

How reproducible:

Always

Steps to Reproduce:

Select "Lock session" in KDE menu, or run kdesktop_lock.
  
Actual results:

Does not start

Expected results:

Starts

Additional info:

How to fix it:
kdesktop_lock.bin is started by a script /usr/bin/kdesktop_lock (in RHEL 4.7 - this was not so in earlier versions).

The first line in the script begins with:
LIST=`ps ax --format "%p:%a" ....

Change this to:
LIST=`ps x --format "%p:%a"  ....

I don't know why it would want to check for kdesktop_lock run by other users. It really does not work that way.

Comment 1 Jiri Pallich 2012-06-20 16:11:41 UTC
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.


Note You need to log in before you can comment on or make changes to this bug.