Bug 698536 - [abrt] xorg-x11-server-Xorg-1.10.99.1-2.20110418.fc16: OsAbort: Process /usr/bin/Xorg was killed by signal 6 (SIGABRT)
Summary: [abrt] xorg-x11-server-Xorg-1.10.99.1-2.20110418.fc16: OsAbort: Process /usr/...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-server
Version: rawhide
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:c6aab929d41fe27a22948e02da7...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-21 07:41 UTC by Ola Thoresen
Modified: 2012-02-09 18:17 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-09 18:17:54 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (6.89 KB, text/plain)
2011-04-21 07:41 UTC, Ola Thoresen 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Ola Thoresen 2011-04-21 07:41:25 UTC 
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 7051 bytes
cmdline: /usr/bin/Xorg :0 -br -verbose -auth /var/run/gdm/auth-for-gdm-RwpgIC/database -nolisten tcp
comment: Log in with gdm
component: xorg-x11-server
Attached file: coredump, 3555328 bytes
crash_function: OsAbort
executable: /usr/bin/Xorg
kernel: 2.6.39-0.rc4.git2.0.fc16.i686.PAE
package: xorg-x11-server-Xorg-1.10.99.1-2.20110418.fc16
rating: 4
reason: Process /usr/bin/Xorg was killed by signal 6 (SIGABRT)
release: Fedora release 16 (Rawhide)
time: 1303371251
uid: 0

How to reproduce
-----
1. 
2. 
3.
Comment 1 Ola Thoresen 2011-04-21 07:41:28 UTC 
Created attachment 493727 [details]
File: backtrace
Comment 2 Ola Thoresen 2011-04-21 17:53:05 UTC 
This seems to be somehow related to any password-dialog.
Xorg will crash after entering the right password after screen lock, and will also crash if I enter the password to unlock gnome-keyring.
Comment 3 Adam Jackson 2012-02-09 18:17:54 UTC 
Pretty sure this is fixed in xserver 1.11.2, if not earlier.  Please reopen if you're still seeing this.
Note You need to log in before you can comment on or make changes to this bug.