Bug 880022 - [abrt] xorg-x11-server-Xorg-1.12.3-2.fc17: Xorg server crashed
Summary: [abrt] xorg-x11-server-Xorg-1.12.3-2.fc17: Xorg server crashed
Keywords:
Status: CLOSED INSUFFICIENT_DATA
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:bad99067da98ecb23b5ca1ae0fe...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-26 03:00 UTC by Fernando Garcia-Flores
Modified: 2012-11-28 19:48 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-11-28 19:48:11 UTC
Type: ---


Attachments (Terms of Use)

Description Fernando Garcia-Flores 2012-11-26 03:00:09 UTC
Version-Release number of selected component:
xorg-x11-server-Xorg-1.12.3-2.fc17

Additional info:
libreport version: 2.0.18
abrt_version:   2.0.18
kernel:         3.6.6-1.fc17.x86_64

backtrace:
:0: /usr/bin/Xorg (xorg_backtrace+0x36) [0x4652d6]
:1: /usr/lib64/xorg/modules/input/synaptics_drv.so (0x7f3cf1921000+0x2e77) [0x7f3cf1923e77]
:2: /usr/lib64/xorg/modules/input/synaptics_drv.so (0x7f3cf1921000+0x4563) [0x7f3cf1925563]
:3: /usr/lib64/xorg/modules/input/synaptics_drv.so (0x7f3cf1921000+0x6fa4) [0x7f3cf1927fa4]
:4: /usr/bin/Xorg (0x400000+0x807b7) [0x4807b7]
:5: /usr/bin/Xorg (0x400000+0xa4ab0) [0x4a4ab0]
:6: /lib64/libpthread.so.0 (0x3b8fa00000+0xefe0) [0x3b8fa0efe0]
:7: /lib64/libc.so.6 (setitimer+0x7) [0x3b8eeae077]
:8: /usr/bin/Xorg (SmartScheduleStopTimer+0x4b) [0x46c69b]
:9: /usr/bin/Xorg (WaitForSomething+0x8ce) [0x462f8e]
:10: /usr/bin/Xorg (0x400000+0x34141) [0x434141]
:11: /usr/bin/Xorg (0x400000+0x23485) [0x423485]
:12: /lib64/libc.so.6 (__libc_start_main+0xf5) [0x3b8ee21735]
:13: /usr/bin/Xorg (0x400000+0x2375d) [0x42375d]

Comment 1 Adam Jackson 2012-11-28 19:48:11 UTC
This backtrace is a bit useless, setitimer shouldn't be a blocking call (for the input signal handler to be able to fire here) but even if it is there's no context here for why that could happen.


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