Xorg crashed with SIGABRT

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

Bug Description

After updating system today with, apt-get update, apt-get upgrade, my KDE session of Ubuntu Studio crashed 3 times on log-in.
On log-in all the applications are freezing but compositing seems to work fine.

On loggin-in using Ubuntu Studio session this report was generated.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: xserver-xorg-core 2:1.15.0-1ubuntu7
ProcVersionSignature: Ubuntu 3.13.0-8.28-lowlatency 3.13.2
Uname: Linux 3.13.0-8-lowlatency x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Wed Mar 26 19:52:24 2014
Disassembly: => 0x7fbc6933ef79: Cannot access memory at address 0x7fbc6933ef79
ExecutablePath: /usr/bin/Xorg
InstallationDate: Installed on 2014-02-13 (41 days ago)
InstallationMedia: Ubuntu-Studio 14.04 "Trusty Tahr" - Alpha amd64 (20140211)
ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
ProcEnviron:

Signal: 6
SourcePackage: xorg-server
Stacktrace: No symbol table is loaded. Use the "file" command.
StacktraceTop:

Title: Xorg crashed with SIGABRT
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
bhatta (bhattacharya-abhishek) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

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

tags: added: apport-failed-retrace
tags: removed: need-amd64-retrace
Timo Aaltonen (tjaalton)
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.