Bug 3784 - gnome logout freezes the computer
Summary: gnome logout freezes the computer
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: distribution
Version: 6.0
Hardware: i386
OS: Linux
high
medium
Target Milestone: ---
Assignee: Michael Fulbright
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 1999-06-28 22:46 UTC by chauvin
Modified: 2008-05-01 15:37 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 1999-08-02 23:45:55 UTC
Embargoed:


Attachments (Terms of Use)

Description chauvin 1999-06-28 22:46:33 UTC
after a virgin rh6 install to Dell 410 server (Pentium
II/450, S3 768 2Mb video RAM 1024 x 768), I am able to
use gnome as lanched from the login gdm screen.

the problem:  about half the time, when i choose "logout"
from the menu bar the machine freezes.  not just X11, the
entire machine.  it won't even respond to ping.  the only
recourse is pushing the reset button.

this same exact computer runs kde without problems and for
the last 6 months has been running rh5.2 and fvwm2, so i
suspect that the problem is not the hardware.

a kernel upgrade to linux-2.2.10 didn't help.  both the
uniprocessor and the multiprocessor kernels exhibit the
same behaviour.

Comment 1 David Lawrence 1999-07-01 19:04:59 UTC
Does the problem continue with the lastest XFree packages available
from ftp://updates.redhat.com?

Comment 2 piller 1999-07-05 04:51:59 UTC
I have RH6.0 running on a Celeron 400 system.  I installed all
update rpms including XFree86 but not kernel updates, I downloaded
2.2.10 source which I compiled and installed.
 A user rebooted the computer, I asked
why and he said that when he logged out of Gnome everything froze
up on him.  This has only happened once so far.

Comment 3 Elliot Lee 1999-08-02 23:45:59 UTC
This sounds like a kernel or XFree86 problem - there is no way
unprivileged GNOME programs could do something like this.


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