[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 351
  • Last Modified:

Xfree86 crash when shutting down Red Hat 6.2

Hi experts,

whenever I log out from KDE interface and shut down my brand new indiRed Hat 6.2 installation, I get an error message which says that my Xfree86 server crashed.

Can you please tell me how Ican fix this problem?

With kind regards


Mathes

0
mathes
Asked:
mathes
  • 4
  • 3
1 Solution
 
jlevieCommented:
Dunno, every RH 6.2 I've seen does that. It's not harmful as far as I can tell, just an irritation.
0
 
mathesAuthor Commented:
Dear jlevie,


thank you for your comment. I am not sure if it is really harmless. I should have mentioned that I havv to click on the logout button several times if I want to quit a KDE session. Moreover: when I tried SuSE 6.4, this problem never occured. So it should be possiblke to run Xfree386 on my machine without this error message. But how can I accomplish this? During installation of Redhat 6.2, the hardware was configured successfully. The control messages during the configuration of
Xfree386 were displayed without problems. My graphic card is a STB nVidia ZX 8MB, and the monitor is a
Dell D1025HE.


With kind regards

Mathes


0
 
jlevieCommented:
Right now I don't know if it's an X or an RH system problem. It's on my list of things to track down as I've not seen anything so far that indicates where the problem lies. I'm using 3.3.6 on a 6.1 system, which doesn't exhibit that fault so I don't have any evidence to suggest that it's an X problem, per se.

I've not experienced a problem with logging out of KDE, but I have seen delays of several seconds when I ask for a shutdown or reboot. I do see the "server crash" message when the shutdown actually begins. This happens with both the stock kernel and custom kernels which would lead me to believe that the problem isn't necessarily with X or the kernel.

There are a couple of updates and security fixes on the Red Hat site that you might want to apply, although I don't see anything that specifically adresses this issue.
0
Free learning courses: Active Directory Deep Dive

Get a firm grasp on your IT environment when you learn Active Directory best practices with Veeam! Watch all, or choose any amount, of this three-part webinar series to improve your skills. From the basics to virtualization and backup, we got you covered.

 
mathesAuthor Commented:
Dear jlevie,

The error message explicitely says that is a xFree problem and asks to inform www.xfree.org. to report this bug.

I would like to post ou this message.

Can you please tell me, in which logfile this message is stored?

With kind regards

Mathes
0
 
jlevieCommented:
I believe I may know what's happening now and I have some evidence to suggest that it's not the server that's at fault. If you escape back to a console via the ctrl-alt-F1 hotkey and invoke shutdown you don't get a server crash. Accordingly I suspect that the problem lies in KDE, specifically in how it goes about shutting down the server for a "Shutdown" or "Shutdown and reboot".
0
 
mathesAuthor Commented:
Dear jlevie,

yes, you are right.

If I shutdown Linux from a textconsole, there are no problems at all.

Does this mean I have to update KDE ? Both the SuSE 6.4 and Redhat 6.2 distribution contain  
the KDE 1.1.2 desktop manager.

SuSE 6.4 can be terminated via graphical login, the same procedere causes an error within the Redhat 6.2 distribution. Actually I would expect the same shutdown behaviour, if the software equipment is equal.

Are SuSE and Redhat really that different ?


With kind regards

Mathes
0
 
jlevieCommented:
The other thing that I've found is that I can inititate a shutdown from the KDE login pane, and it looks like it didn't work. The screen will blank, then the server restarts and shows the login pane. But if I don't do anything it will blank one more time and shutdwon the server, usually without error.

I don't think there's a later stable version of KDE than what we've got. The problem looks to be an interaction between KDE and the 3.3.6 server. I don't know which server SuSE 6.4 uses. I do know that RH 6.1 doesn't exhibit this problem, but it uses the 3.3.5 X server. And there's also the possibility that later kernel and/or system utils in RH 6.2 has some bearing on this.
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now