Bug 59224 - System crash after KDE logout
Summary: System crash after KDE logout
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: XFree86-Servers
Version: 7.2
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Mike A. Harris
QA Contact: David Lawrence
Depends On:
TreeView+ depends on / blocked
Reported: 2002-02-02 22:54 UTC by utmue
Modified: 2007-04-18 16:39 UTC (History)
1 user (show)

Clone Of:
Last Closed: 2003-01-24 15:57:16 UTC

Attachments (Terms of Use)
/var/log/messages (131.33 KB, text/plain)
2002-02-04 19:17 UTC, utmue
no flags Details
XFree.log (20.47 KB, text/plain)
2002-02-04 19:18 UTC, utmue
no flags Details
XFreeConfig (16.30 KB, text/plain)
2002-02-04 19:20 UTC, utmue
no flags Details

Description utmue 2002-02-02 22:54:51 UTC
Description of Problem:
Since new installation of Red Hat with more packages after installing 
a network adapter the X-Server crashes every time I log out from KDE (no difference if I start 
runlevel 5 or if I start X manually). The main problem is that not only the X-Server crashes but the 
whole system - I even can't switch off the computer, only the reset switch works. Without X-Server 
there is no problem. And there's no problem with GNOME.

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

How Reproducible:
every time

Steps to Reproduce:
log in to KDE (manually or with runlevel 5)
2. log out from KDE

Actual Results:

Expected Results:
either stopping the X-Server (when starting KDE from runlevel 3) 
or shutting down the system (when starting with runlevel 5)

Additional Information:
video card: Intel 810 chipset

Comment 1 Mike A. Harris 2002-02-03 23:15:04 UTC
If you are using graphical boot mode (runlevel 5), try switching to
using gdm instead of KDM nd see if the problem goes away.  Also, try
changing to runlevel 3 and see if X works properly.  This will provide
helpful information.

Also, please attach your X server log and config file, and the
/var/log/messages file.

Comment 2 utmue 2002-02-04 19:17:29 UTC
Created attachment 44438 [details]

Comment 3 utmue 2002-02-04 19:18:48 UTC
Created attachment 44439 [details]

Comment 4 utmue 2002-02-04 19:20:28 UTC
Created attachment 44440 [details]

Comment 5 utmue 2002-02-04 19:25:32 UTC
As mentionned above ;-) it makes no difference if I start KDE automatically 
runlevel 5 or manually with startx from runlevel 3. Also it is only KDE which 
causes the problem, there's no problem with GNOME.

Comment 6 Wendy Hung 2002-02-26 21:40:04 UTC
Similar bug on an IBM xSeries system running runlevel 3.  
When running gdm, kde crashes when logging out.
When running kdm, GNOME crashes when logging out.

Comment 7 Mike McLean 2003-01-02 18:55:42 UTC
This bug has been inappropriately marked MODIFIED. Please review the bug life
cycle information at 

Changing bug status to ASSIGNED.

Comment 8 Mike A. Harris 2003-01-24 15:57:16 UTC
IMB xSeries as far as I know is unsupported

This bug was closed by the reporter putting it in MODIFIED state
about 8 months ago, and is rather old now.  Red Hat Linux 7.1, 7.2, 7.3
are only getting security fixes for XFree86 now.  While there may be
some backported bug fixes thrown in also, no real major bug fixing
occurs in old releases.

You've indicated above it doesn't occur in GNOME, so there is a workaround
available to you.

As an addiitonal note, the problems I have seen reported like this that
are similar, many have turned out to be the kernel hanging when KDE starts
trying to play sound effects during startup due to sound driver and/or
hardware bugs.

Recommended solution #1: Make sure your system is completely up2date
Recommended solution #2: Disable KDE sound
Recommended solution #3: Upgrade to Red Hat Linux 8.0, or test drive our new
                         beta release.

Closing as WONTFIX for 7.2, as it isn't clear what the problem might be,
and it's an aged problem now.  If the problem recurs in Red Hat Linux 8.0,
please open a new bug report, and include all of the details that were
asked above in this one also.


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