Bug 855559 - [abrt] xorg-x11-server-Xorg-1.12.3-1.fc17: Xorg server crashed
Summary: [abrt] xorg-x11-server-Xorg-1.12.3-1.fc17: Xorg server crashed
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-server
Version: 17
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:ca9ef9c0dc67c1997f4b3a10684...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-08 22:19 UTC by Steevithak
Modified: 2013-08-01 19:27 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-08-01 19:27:44 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: usr_share_xorg_conf_d.tar.gz (1.57 KB, text/plain)
2012-09-08 22:19 UTC, Steevithak
no flags Details
File: etc_X11_xorg_conf_d.tar.gz (376 bytes, text/plain)
2012-09-08 22:19 UTC, Steevithak
no flags Details

Description Steevithak 2012-09-08 22:19:28 UTC
Description of problem:
Closed laptop. Returned later, open it, and found it had crashed. Desktop was non-response except for mouse pointer movement. Did a powerdown and rebooted.

Version-Release number of selected component:
xorg-x11-server-Xorg-1.12.3-1.fc17

Additional info:
libreport version: 2.0.13
abrt_version:   2.0.12
kernel:         3.5.3-1.fc17.x86_64

backtrace:
:0: /usr/bin/Xorg (xorg_backtrace+0x36) [0x4652a6]
:1: /usr/bin/Xorg (0x400000+0x6a289) [0x46a289]
:2: /lib64/libpthread.so.0 (0x306ba00000+0xefe0) [0x306ba0efe0]
:3: /usr/lib64/xorg/modules/input/synaptics_drv.so (0x7f0ac5f4e000+0x3503) [0x7f0ac5f51503]
:4: /usr/lib64/xorg/modules/input/synaptics_drv.so (0x7f0ac5f4e000+0x38cc) [0x7f0ac5f518cc]
:5: /usr/bin/Xorg (DisableDevice+0x16e) [0x42d6ee]
:6: /usr/bin/Xorg (xf86Wakeup+0x494) [0x481244]
:7: /usr/bin/Xorg (WakeupHandler+0x6b) [0x43838b]
:8: /usr/bin/Xorg (WaitForSomething+0x1a4) [0x462834]
:9: /usr/bin/Xorg (0x400000+0x34111) [0x434111]
:10: /usr/bin/Xorg (0x400000+0x23485) [0x423485]
:11: /lib64/libc.so.6 (__libc_start_main+0xf5) [0x306b621735]
:12: /usr/bin/Xorg (0x400000+0x2375d) [0x42375d]

Comment 1 Steevithak 2012-09-08 22:19:30 UTC
Created attachment 611086 [details]
File: usr_share_xorg_conf_d.tar.gz

Comment 2 Steevithak 2012-09-08 22:19:32 UTC
Created attachment 611088 [details]
File: etc_X11_xorg_conf_d.tar.gz

Comment 3 Ryan Crews 2012-09-18 15:23:45 UTC
Attempting to put the laptop to sleep will sometimes produce this problem.

The laptop (Thinkpad T420s) will not sleep, but the sleep LED will blink. Opening the laptop will eventually display some sort of 'had a problem' screen.


Package: xorg-x11-server-Xorg-1.12.3-1.fc17
OS Release: Fedora release 17 (Beefy Miracle)

Comment 4 Steevithak 2012-09-18 16:18:19 UTC
I can confirm Ryan's description. I've paid more attention to the problem since it is now happening frequently. What happens is I close the lid to the laptop, watch the LED indicate sleep mode, and then put the laptop away thinking everything is great. Later when I take the laptop out, I've noticed the indicator shows it no longer in sleep mode. When I open the lid, I get the usual login screen with the error message about "having a problem" on top of it. It's impossible to login or reboot or do anything except move the mouse cursor around. 

After I power cycle and reboot, I've noticed the temperature has gone way too high, often the CPUs are around 150F which can't be good. So I think what's happening is that the laptop is somehow going out of sleep mode on it's own and bringing the CPUs back up to full power with all the fans off. Until there's a fix I've taken to doing a full shutdown of the laptop, since this looks like a bug that could potentially damage the machine. 

I've run Fedora on this laptop as long as I've had it, back to Fedora 13 I think and it's never exhibited a problem like this before, so it's definitely a recent innovation.

FWIW, This is a Dell Studio 15 laptop, model 1558 w Intel Core i3-350M processors.

Comment 5 Adam Jackson 2012-10-18 21:50:10 UTC
Please update to at least xorg-x11-server-1.12.3-2.fc17 and reopen if this is still reproduceable.

Comment 6 Adam Jackson 2012-10-18 21:50:31 UTC
Please update to at least xorg-x11-server-1.12.3-2.fc17 and reopen if this is still reproduceable.

Comment 7 Jiri Eischmann 2012-10-29 20:14:09 UTC
I was trying to suspend the computer. 

Package: xorg-x11-server-Xorg-1.12.3-2.fc17
OS Release: Fedora release 17 (Beefy Miracle)

Comment 8 Fedora End Of Life 2013-07-04 07:23:33 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 9 Fedora End Of Life 2013-08-01 19:27:48 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


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