Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 74

Summary:	xlock doesn't lock virtual terminals.
Product:	[Retired] Red Hat Linux	Reporter:	Jim Toth <jjtoth>
Component:	xlockmore	Assignee:	David Lawrence <dkl>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5.2
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	1998-11-16 14:29:58 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jim Toth 1998-11-15 10:45:48 UTC

If I have my X sesssion locked with xlock, I can get around
this by type Ctl-Alt-F1 (or whatever), hit ^Z on startx, do
a ps, and kill the xlock.

Comment 1 Aleksey Nogin 1998-11-16 14:16:59 UTC

This is not a bug, but a normal behavour. If you want to avoid it, you
should use xdm or something like
startx & ; logout

Alternatively you may choose to use vlock to lock the virtual
terminal.

You may also want to uncomment DontZap option in your XF86Config file
to make sure nobody can kill your X-session using Ctrl-Alt-Bkspace

Comment 2 Preston Brown 1998-11-16 14:29:59 UTC

Not a bug, solution(s) explained well in the previous message.

Comment 3 paolo.saggese 1999-02-04 10:08:59 UTC

> something like
> startx & ; logout

Even better -IMHO- (am I wrong?) is starting the X session by
exec-uting it:

exec startx