Xorg crashed with SIGABRT

Bug #1289514 reported by Rene Pieters
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
fglrx-installer (Ubuntu)
New
Undecided
Unassigned

Bug Description

Think this happened on coming out of screensaver blanking.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: xserver-xorg-core 2:1.15.0-1ubuntu6
ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
Uname: Linux 3.11.0-17-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
Date: Fri Mar 7 19:16:05 2014
ExecutablePath: /usr/bin/Xorg
InstallationDate: Installed on 2014-03-04 (3 days ago)
InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
ProcCmdline: /usr/bin/X -core :1 -seat seat0 -auth /var/run/lightdm/root/:1 -nolisten tcp vt8 -novtswitch
ProcEnviron:

Registers:
 .
 Thread 1 (LWP 21553):
 #0 0x00007fad32964f79 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7fffc7f05f78
Signal: 6
SourcePackage: xorg-server
StacktraceTop:

ThreadStacktrace: No symbol table is loaded. Use the "file" command.
Title: Xorg crashed with SIGABRT
UpgradeStatus: Upgraded to trusty on 2014-03-07 (0 days ago)
UserGroups:

Revision history for this message
Rene Pieters (rene-pieters) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 0x00007fad32964f79 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7fffc7f05f78
StacktraceSource: #0 0x00007fad32964f79 in ?? ()
StacktraceTop: ?? ()
ThreadStacktrace:
 .
 Thread 1 (LWP 21553):
 #0 0x00007fad32964f79 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7fffc7f05f78

tags: added: apport-failed-retrace
tags: removed: need-amd64-retrace
affects: xorg-server (Ubuntu) → fglrx-installer (Ubuntu)
information type: Private → Public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.