Bug 896745 - [abrt] xorg-x11-server-Xorg-1.13.1-4.fc18: OsAbort: Process /usr/bin/Xorg was killed by signal 6 (SIGABRT) I'm pretty sure I managed to crash the GDM by moving my mouse as it was fading to black before logging in/clicking anything
Summary: [abrt] xorg-x11-server-Xorg-1.13.1-4.fc18: OsAbort: Process /usr/bin/Xorg was...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-server
Version: 18
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:d7bc8891738d5f946daaf44371f...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-17 22:00 UTC by NickG
Modified: 2014-02-05 15:05 UTC (History)
15 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-05 15:05:30 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (8.67 KB, text/plain)
2013-01-17 22:00 UTC, NickG
no flags Details
File: build_ids (1.44 KB, text/plain)
2013-01-17 22:00 UTC, NickG
no flags Details
File: cgroup (152 bytes, text/plain)
2013-01-17 22:00 UTC, NickG
no flags Details
File: core_backtrace (1.79 KB, text/plain)
2013-01-17 22:00 UTC, NickG
no flags Details
File: dso_list (3.01 KB, text/plain)
2013-01-17 22:00 UTC, NickG
no flags Details
File: environ (347 bytes, text/plain)
2013-01-17 22:00 UTC, NickG
no flags Details
File: limits (1.29 KB, text/plain)
2013-01-17 22:00 UTC, NickG
no flags Details
File: maps (11.26 KB, text/plain)
2013-01-17 22:00 UTC, NickG
no flags Details
File: proc_pid_status (743 bytes, text/plain)
2013-01-17 22:00 UTC, NickG
no flags Details
File: var_log_messages (1005 bytes, text/plain)
2013-01-17 22:00 UTC, NickG
no flags Details

Description NickG 2013-01-17 22:00:02 UTC
Version-Release number of selected component:
xorg-x11-server-Xorg-1.13.1-4.fc18

Additional info:
backtrace_rating: 4
cmdline:        /usr/bin/Xorg :0 -background none -verbose -auth /var/run/gdm/auth-for-gdm-FBMNiZ/database -seat seat0 -nolisten tcp vt1
crash_function: OsAbort
executable:     /usr/bin/Xorg
kernel:         3.7.2-201.fc18.i686
open_fds:       
remote_result:  602815
uid:            0

Truncated backtrace:
Thread no. 1 (10 frames)
 #3 OsAbort at utils.c:1266
 #4 ddxGiveUp at xf86Init.c:1071
 #5 AbortDDX at xf86Init.c:1115
 #6 AbortServer at log.c:652
 #7 FatalError at log.c:793
 #8 OsSigHandler at osinit.c:146
 #11 memcpy at ../sysdeps/i386/i686/multiarch/memcpy-ssse3.S:142
 #13 exaMemcpyBox at exa_migration_classic.c:59
 #14 exaCopyDirty at exa_migration_classic.c:240
 #15 exaCopyDirtyToSys at exa_migration_classic.c:285

Potential duplicate: bug 703807

Comment 1 NickG 2013-01-17 22:00:06 UTC
Created attachment 680571 [details]
File: backtrace

Comment 2 NickG 2013-01-17 22:00:09 UTC
Created attachment 680572 [details]
File: build_ids

Comment 3 NickG 2013-01-17 22:00:12 UTC
Created attachment 680573 [details]
File: cgroup

Comment 4 NickG 2013-01-17 22:00:15 UTC
Created attachment 680574 [details]
File: core_backtrace

Comment 5 NickG 2013-01-17 22:00:17 UTC
Created attachment 680575 [details]
File: dso_list

Comment 6 NickG 2013-01-17 22:00:19 UTC
Created attachment 680576 [details]
File: environ

Comment 7 NickG 2013-01-17 22:00:22 UTC
Created attachment 680577 [details]
File: limits

Comment 8 NickG 2013-01-17 22:00:24 UTC
Created attachment 680578 [details]
File: maps

Comment 9 NickG 2013-01-17 22:00:27 UTC
Created attachment 680579 [details]
File: proc_pid_status

Comment 10 NickG 2013-01-17 22:00:29 UTC
Created attachment 680580 [details]
File: var_log_messages

Comment 11 Hebert Silva 2013-01-24 14:38:36 UTC
Problem was possible triggerd while using a remote destop client window through KRDC.

backtrace_rating: 4
Package: xorg-x11-server-Xorg-1.13.1-4.fc18
OS Release: Fedora release 18 (Spherical Cow)

Comment 12 NickG 2013-02-03 15:27:56 UTC
Gnome was running away happily. Flipped up the notification bar at the bottom and all the window decorations disappeared.

backtrace_rating: 4
Package: xorg-x11-server-Xorg-1.13.1-4.fc18
OS Release: Fedora release 18 (Spherical Cow)

Comment 13 floyd smith 2013-02-24 20:44:28 UTC
I first switch out of Gnome user "u" to virtual console VC3. I then used F1 to switch back to Gnome. It crashed soon after user "floydsmith" came up.

backtrace_rating: 4
Package: xorg-x11-server-Xorg-1.13.0-11.fc18
OS Release: Fedora release 18 (Spherical Cow)

Comment 14 Kaya Saman 2013-03-25 17:16:34 UTC
I opened up a webm based video using mplayer

backtrace_rating: 4
Package: xorg-x11-server-Xorg-1.13.3-1.fc18
OS Release: Fedora release 18 (Spherical Cow)

Comment 15 aolaolaoll 2013-08-22 08:47:52 UTC
Xorg reproducibly crashes when Firefox tries to open a specific web page referencing a specific javascript file. After isolating the cause on the HTML file, I didn't do anything on the JS file yet. It is a minified file with very long lines which might be the cause: when opening the file with Kate and saving it (thus reducing each line's maximum length to 1024 characters), Firefox no longer crashes.

Chrome can open the same web page without problems, so it is specific to Firefox or to a library used by Firefox.

reporter:       libreport-2.1.5
backtrace_rating: 4
cmdline:        /usr/bin/X -background none :0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt1 -novtswitch
core_backtrace: 
crash_function: OsAbort
environ:        
executable:     /usr/bin/Xorg
kernel:         3.9.9-201.fc18.i686.PAE
open_fds:       
package:        xorg-x11-server-Xorg-1.13.3-3.fc18
reason:         Process /usr/bin/Xorg was killed by signal 6 (SIGABRT)
runlevel:       N 5
uid:            0
xsession_errors:

Comment 16 vaguelight 2013-11-03 09:20:59 UTC
I was surfing the web using Firefox

reporter:       libreport-2.1.7
backtrace_rating: 4
cmdline:        /usr/bin/X -background none :0 vt01 -nolisten tcp
crash_function: OsAbort
executable:     /usr/bin/Xorg
kernel:         3.11.4-101.fc18.i686
open_fds:       
package:        xorg-x11-server-Xorg-1.13.3-3.fc18
reason:         Process /usr/bin/Xorg was killed by signal 6 (SIGABRT)
reported_to:    uReport: BTHASH=b789db33c84ecf589e7848497b540eb7c93b6c8c
runlevel:       N 5
type:           CCpp
uid:            0

Comment 17 Fedora End Of Life 2013-12-21 10:29:34 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 '18'.

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 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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 18'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 18 Fedora End Of Life 2014-02-05 15:05:40 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

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.