Description of problem:
When I lock my GNOME session using the Lock Screen menu item and go away
for some time, I come back and the system is sitting at the GDM login prompt.
This suggests that the X server died.
Steps to Reproduce:
1. Click on the "Lock Screen" menu item in GNOME
2. Leave the machine for some time
Get a GDM login prompt.
Get an Xscreensaver password prompt, then am returned to running GNOME/X session.
I have an i810/i815 video card and am running the "Molecule" Xscreensaver
module. I will post additional information (X server log, etc.) soon.
Created attachment 89707 [details]
first X server log
Created attachment 89708 [details]
second X server log
First server log is from /var/log/XFree86.0.log.old, dated from about 2 hours
ago. This would seem to be the log from the last X server crash.
Second server log is from /var/log/XFree86.0.log, dated about 15 minutes ago.
This would seem to be the log from the current (still running) X server.
An older issue that seems to be similar to this is bug 73827.
I'm running Red Hat Linux 8.0.92 (Phoebe) on an HP Vectra workstation
(Pentium III, 128 MB RAM, i815 mainboard and video).
Package versions are those from default Phoebe install:
I'll try changing my screensaver settings in case the bug is being
triggered by some tricky graphics (maybe OpenGL or DRI) in the
screensaver used when the screen is locked.
Created attachment 89709 [details]
XFree86 server configuration file
I'm adding my X server configuration file in case it's useful.
Is there anything in /var/log/messages around the times of the crashes?
Only the following, which is probably to be expected:
Jan 30 09:38:41 selene gdm: gdm_slave_xioerror_handler: Fatal X error -
Is this with Phoebe 1 or 2? If 1, please install 2 and see if that fixes it.
If not, make sure you run up2date to see if anything has been sent down, maybe
even check rawhide packages to see if this helps fix the problem.
Does this problem still occur in the latest builds?
Please respond ASAP, because 10 day gaps between responses might mean that
if this issue is still present, that it may not get addressed or given the
attention it deserves before XFree86 4.3.0 is released.
Thanks in advance.
I installed XFree86-18.104.22.1681-20030213.1 and all its dependent packages
from Raw Hide today, and as yet I am unable to reproduce this problem.
Thanks for the update, closing bug as fixed in RAWHIDE.