Xorg crashed with SIGABRT
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xorg-server (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
acer d250
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: xserver-xorg-core 2:1.11.4-0ubuntu10
ProcVersionSign
Uname: Linux 3.2.0-23-
NonfreeKernelMo
.tmp.unity.
ApportVersion: 2.0.1-0ubuntu4
Architecture: i386
CompizPlugins: No value set for `/apps/
CompositorRunning: compiz
CurrentDmesg: [ 450.904070] eth1: no IPv6 routers present
Date: Tue Apr 17 19:59:50 2012
DistUpgraded: Fresh install
DistroCodename: precise
DistroVariant: ubuntu
DkmsStatus:
bcmwl, 5.100.82.38+bdcom, 3.2.0-20-
bcmwl, 5.100.82.38+bdcom, 3.2.0-23-
ExecutablePath: /usr/bin/Xorg
ExtraDebuggingI
GraphicsCard:
Intel Corporation Mobile 945GSE Express Integrated Graphics Controller [8086:27ae] (rev 03) (prog-if 00 [VGA controller])
Subsystem: Acer Incorporated [ALI] Device [1025:022f]
Subsystem: Acer Incorporated [ALI] Device [1025:022f]
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120328)
ProcCmdline: /usr/bin/X :0 -auth /var/run/
ProcEnviron:
ProcKernelCmdLine: BOOT_IMAGE=
Signal: 6
SourcePackage: xorg-server
Stacktrace:
#0 0xb7514424 in __kernel_vsyscall ()
No symbol table info available.
Cannot access memory at address 0xbfd08350
StacktraceTop:
ThreadStacktrace:
.
Thread 1 (Thread 0xb70b4a40 (LWP 5394)):
#0 0xb7514424 in __kernel_vsyscall ()
No symbol table info available.
Cannot access memory at address 0xbfd08350
Title: Xorg crashed with SIGABRT
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 12/18/2010
dmi.bios.vendor: Acer
dmi.bios.version: V1.29
dmi.board.
dmi.board.vendor: Acer
dmi.board.version: V1.29
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.
dmi.modalias: dmi:bvnAcer:
dmi.product.
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.7.6-0ubuntu1
version.libdrm2: libdrm2 2.4.32-1ubuntu1
version.
version.
version.
version.
version.
version.
version.
version.
caught this bug while working with update manager (switching off autocheck)