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

Bug 10177

Summary:	RedHat 6.1 locking up
Product:	[Retired] Red Hat Linux	Reporter:	rltheis
Component:	xlockmore	Assignee:	Cristian Gafton <gafton>
Status:	CLOSED WORKSFORME	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.1	CC:	tim.taylor
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:	2000-06-27 18:09:52 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 rltheis 2000-03-15 00:49:31 UTC

RedHat 6.1 has locked up on me a number of times while I had lock screen
running. I had my system in lock screen for a number of hours when this
happens. For other programs running, it has veried from nothing to having
Applix, kpppload, kedit, and/or other programs running. The system has also
locked up while I was working. This has only happened a 2 to 4 times over
the last couple of months.
 Does RedHat supply the latest kernals in rpm format? Or do you know of a
site that does?

Thank you,
  Richard Theisen

Comment 1 rltheis 2000-04-14 00:31:59 UTC

Has this been looked into yet? A couple of days ago, I was running Netscape and
the hung twice within 10 minutes.

Thank you,
  Richard Theisen

Comment 2 Jeff Johnson 2000-05-14 20:58:59 UTC

Changing component to xlockmore ...

Comment 3 Bill Nottingham 2000-06-11 18:47:20 UTC

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

Comment 4 Rob Kearey 2000-06-13 03:21:41 UTC

Note that this bug /only/ occurs in the "penetrate" screensaver. I'm not having
any lockup problems as per bug 10177.

I have an strace out if that would help.

Rob K

Comment 5 pdenis2 2000-06-25 19:09:05 UTC

"Penetrate" -- I assume that's the component of GNOME's "random screensaver" 
that leaves a garbled, orange, "Level 1 Cleared" screen -- is locking up 2 of my 
RH6.1 systems, requiring hard reset ( I couldn't even ping to it).  Different 
machines, different video cards.  Only recent change has been to run X at 100 
dpi instead of 75 dpi.  Questions: how to get rid of "penetrate" from system 
(rpm -e xscreensaver I assume).  How to turn on Magic sysreq (and where is it 
documented??!)

Comment 6 pdenis2 2000-06-27 18:09:52 UTC

The "penetrate" lockup occurs _ONLY_ when I run X in 100 dpi mode (startx -- 
-dpi 100).  Alt-sysrq-k will free it up to the extent of allowing a ctrl-alt-del 
reboot.

Comment 7 Bill Nottingham 2000-08-08 03:17:43 UTC

We've never seen this with penetrate here, or with xlock.

To remove it, you can a) pick a different screensaver
b) edit it out of /usr/X11R6/lib/X11/app-defaults/XScreenSaver

Comment 8 rltheis 2000-08-09 00:51:26 UTC

  After downloading my e-mail, I left my system running without starting xlock
and I had 5 terminals, 1 kpppload, 1 xosview, and 1 KDE World Watch View
running. When I turned my monitor back on, my system had locked up. I could not
change virtual windows or move the mouse. When I run xlock, I use the random
option and I've noticed the system locking up on different screen savers. The
only time I have not had a lock-up is when I logout and have the gui login
screen showing. In this case the KDE login screen.
  Is there anything I can run to trap any possible errors? I did not see
anything in /var/logs/messages that indicated any problem. Is there anything you
want me to try?

Thanks!
  Richard Theisen