Bug 688071 - [abrt] xorg-x11-server-Xorg-1.9.4-1.fc14: OsAbort: Process /usr/bin/Xorg was killed by signal 6 (SIGABRT)
Summary: [abrt] xorg-x11-server-Xorg-1.9.4-1.fc14: OsAbort: Process /usr/bin/Xorg was ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-server
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:a522045c6d285f3134de205ff8d...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-16 08:53 UTC by zhanggh1978
Modified: 2012-03-22 18:55 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-22 18:55:48 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (6.16 KB, text/plain)
2011-03-16 08:53 UTC, zhanggh1978 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description zhanggh1978 2011-03-16 08:53:48 UTC 
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 6308 bytes
cmdline: /usr/bin/Xorg :0 -nr -verbose -auth /var/run/gdm/auth-for-gdm-VvwrJd/database -nolisten tcp vt1
component: xorg-x11-server
Attached file: coredump, 7643136 bytes
crash_function: OsAbort
executable: /usr/bin/Xorg
kernel: 2.6.35.11-83.fc14.i686
package: xorg-x11-server-Xorg-1.9.4-1.fc14
rating: 4
reason: Process /usr/bin/Xorg was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1300199094
uid: 0

How to reproduce
-----
1.h
2.
3.
Comment 1 zhanggh1978 2011-03-16 08:53:50 UTC 
Created attachment 485679 [details]
File: backtrace
Comment 2 zhanggh1978 2011-03-18 13:51:00 UTC 
Package: xorg-x11-server-Xorg-1.9.4-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.h
2.
3.
Comment 3 Adam Jackson 2012-03-22 18:55:48 UTC 
Mass close of F14 abrt reports.  Please reopen and update summary if this is still reproducable on F16 or later.
Note You need to log in before you can comment on or make changes to this bug.