Red Hat Bugzilla – Bug 865967
RHEL 5.9 BUG: Logging out of desktop produces traceback in /var/log/Xorg.0.log.old
Last modified: 2013-01-08 02:40:02 EST
Created attachment 626336 [details]
Description of problem:
We've found that some errors are reported when you log out of the RHEL 5.9 desktop. This occurs on any system with an nVidia or AMD graphics card installed, with the in-box open source drivers or with the third party closed source driver installed. We do see that it happens when the card-2-monitor connection is DP. This error does not seem to happen when you're connected to a DVI connection.
The following backtrace can be found in the Xorg.log.old file:
0: /usr/bin/Xorg(xf86SigHandler+0x81) [0x80c3511]
2: /usr/bin/Xorg [0x81186b4]
3: /usr/bin/Xorg [0x8129d94]
4: /usr/lib/xorg/modules/libramdac.so [0x98e837]
5: /usr/bin/Xorg [0x81229f5]
6: /usr/bin/Xorg [0x815f0cd]
7: /usr/bin/Xorg(FreeCursor+0x6a) [0x807ee3a]
8: /usr/bin/Xorg(main+0x4d7) [0x80709a7]
9: /lib/libc.so.6(__libc_start_main+0xdc) [0x14eebc]
10: /usr/bin/Xorg(FontFileCompleteXLFD+0x205) [0x806fc51]
Fatal server error:
Caught signal 11. Server abortin
Version-Release number of selected component (if applicable):
How reproducible: 100%
Steps to Reproduce:
1. Install RHEL 5.9/SS1/64
2. Reboot and answer firstboot questions
3. Login and proceed to desktop
4. Use the menu option to log out
Upon logging back into the desktop, you will see a /var/log/Xorg.0.log.old file which contains the backtrace shown above
No errors, no backtrace
Raising for 5.9, this is probably due to some memory leak fixes applied in 5.9.
Devel ack for fixing this, it's clearly a regression introduced by the memory leak fixes already applied.
Probably fixed by this build:
As far as I can tell, the trace back issue has been fixed by these changes.
Would this have been expected to be in snapshot 5? I'm not seeing it there...
I reproduced the backtrace on xorg-x11-server-1.1.1-48.98.el5. Upon installing xorg-x11-server-1.1.1-48.100.el5, the backtrace did not reappear.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.