Xorg crashed with SIGABRT

Bug #1251259 reported by Thaddaeus Tintenfisch
This bug report is a duplicate of:  Bug #1274893: Xorg crashed with SIGABRT. Edit Remove
38
This bug affects 7 people
Affects Status Importance Assigned to Milestone
fglrx-installer (Ubuntu)
Incomplete
Critical
Unassigned

Bug Description

NA

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: xserver-xorg-core 2:1.14.3-3ubuntu4
ProcVersionSignature: Ubuntu 3.12.0-2.7-generic 3.12.0
Uname: Linux 3.12.0-2-generic i686
NonfreeKernelModules: fglrx
.tmp.unity.support.test.0:

ApportVersion: 2.12.6-0ubuntu1
Architecture: i386
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Thu Nov 14 15:14:08 2013
Disassembly: => 0xb752a424: Cannot access memory at address 0xb752a424
DistUpgraded: 2013-11-08 18:12:18,776 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus:
 fglrx, 13.101, 3.12.0-2-generic, i686: installed
 virtualbox, 4.2.16, 3.12.0-2-generic, i686: installed
ExecutablePath: /usr/bin/Xorg
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Redwood XT [Radeon HD 5670/5690/5730] [1002:68d8] (prog-if 00 [VGA controller])
   Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e152]
InstallationDate: Installed on 2013-09-21 (53 days ago)
InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130920)
JockeyStatus:
 kmod:fglrx - ATI Fire GL (Proprietary, Enabled, In use)
 kmod:fglrx_updates - Video driver for the AMD graphics accelerators (Proprietary, Disabled, Not in use)
LightdmGreeterLog:
 ** (lightdm-gtk-greeter:1803): WARNING **: Failed to open sessions directory: Error opening directory '/usr/share/lightdm/sessions': No such file or directory

 ** (lightdm-gtk-greeter:1803): WARNING **: Failed to open sessions directory: Error opening directory '/usr/share/lightdm/remote-sessions': No such file or directory
LightdmGreeterLogOld:
 ** (lightdm-gtk-greeter:1601): WARNING **: Failed to open sessions directory: Error opening directory '/usr/share/lightdm/sessions': No such file or directory

 ** (lightdm-gtk-greeter:1601): WARNING **: Failed to open sessions directory: Error opening directory '/usr/share/lightdm/remote-sessions': No such file or directory
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 002: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for Bluetooth
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: ASUSTeK Computer INC. P5N-T DELUXE
MarkForUpload: True
ProcCmdline: /usr/bin/X -core :1 -auth /var/run/lightdm/root/:1 -nolisten tcp vt8 -novtswitch
ProcEnviron:

ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.12.0-2-generic root=UUID=a6709709-1790-4bc3-9403-71a352932211 ro rootflags=subvol=@ quiet splash nomodeset video=uvesafb:mode_option=1400x1050-32,mtrr:3,scroll=ywrap
Signal: 6
SourcePackage: fglrx-installer
Stacktrace:
 #0 0xb752a424 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0xbfe232f4
StacktraceTop: ?? ()
ThreadStacktrace:
 .
 Thread 1 (LWP 5464):
 #0 0xb752a424 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0xbfe232f4
Title: Xorg crashed with SIGABRT
UpgradeStatus: Upgraded to trusty on 2013-11-08 (5 days ago)
UserGroups:

dmi.bios.date: 01/22/2009
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: ASUS P5N-T DELUXE ACPI BIOS Revision 1402
dmi.board.name: P5N-T DELUXE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 1.XX
dmi.chassis.asset.tag: 123456789000
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSP5N-TDELUXEACPIBIOSRevision1402:bd01/22/2009:svnASUSTeKComputerINC.:pnP5N-TDELUXE:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N-TDELUXE:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: P5N-T DELUXE
dmi.product.version: System Version
dmi.sys.vendor: ASUSTeK Computer INC.
version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
version.fglrx-installer: fglrx-installer N/A
version.libdrm2: libdrm2 2.4.46-4
version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.2-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.2-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu1
xserver.bootTime: Thu Nov 14 15:09:21 2013
xserver.configfile: /etc/X11/xorg.conf
xserver.devices:
 input Power Button KEYBOARD, id 6
 input Power Button KEYBOARD, id 7
 input Microsoft Microsoft® 2.4GHz Transceiver v8.0 KEYBOARD, id 8
 input Microsoft Microsoft® 2.4GHz Transceiver v8.0 KEYBOARD, id 9
 input Microsoft Microsoft® 2.4GHz Transceiver v8.0 KEYBOARD, id 10
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.14.3-3ubuntu4
xserver.video_driver: fglrx

Revision history for this message
Thaddaeus Tintenfisch (thad-fisch-deactivatedaccount) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 0xb752a424 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0xbfe232f4
StacktraceTop: ?? ()
ThreadStacktrace:
 .
 Thread 1 (LWP 5464):
 #0 0xb752a424 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0xbfe232f4

tags: added: apport-failed-retrace
tags: removed: need-i386-retrace
information type: Private → Public
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in fglrx-installer (Ubuntu):
status: New → Confirmed
Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

Renders the system temporarily or permanently unusable.

Changed in fglrx-installer (Ubuntu):
importance: Undecided → Critical
Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

At a minimum, we need:
1. the specific steps or actions you took that caused you to encounter the problem,
2. the behavior you expected, and
3. the behavior you actually encountered (in as much detail as possible).

:)

Changed in fglrx-installer (Ubuntu):
status: Confirmed → Incomplete
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.