Xorg crashed with SIGABRT in _XSERVTransClose()

Bug #1061580 reported by Marius B. Kotsbak
48
This bug affects 7 people
Affects Status Importance Assigned to Milestone
xorg-server (Ubuntu)
Expired
Low
Unassigned

Bug Description

N/A

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: xserver-xorg-core 2:1.13.0-0ubuntu5
ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
Uname: Linux 3.5.0-16-generic i686
.tmp.unity.support.test.0:

ApportVersion: 2.6.1-0ubuntu1
Architecture: i386
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
Date: Thu Oct 4 13:20:48 2012
DistUpgraded: 2012-08-31 14:36:26,019 DEBUG disabling apt cron job (0755)
DistroCodename: quantal
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 4.1.18, 3.5.0-13-generic, i686: installed
 virtualbox, 4.1.18, 3.5.0-14-generic, i686: installed
 virtualbox, 4.1.18, 3.5.0-15-generic, i686: installed
 virtualbox, 4.1.18, 3.5.0-16-generic, i686: installed
 virtualbox, 4.1.18, 3.6.0-030600-generic, i686: installed
ExecutablePath: /usr/bin/Xorg
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a011] (rev 02) (prog-if 00 [VGA controller])
   Subsystem: Giga-byte Technology Device [1458:b100]
   Subsystem: Giga-byte Technology Device [1458:b100]
MachineType: GIGABYTE T1005
ProcCmdline: /usr/bin/X :1 -background none -verbose -auth /run/gdm/auth-for-gdm-MOGj4X/database -nolisten tcp vt7
ProcEnviron:
 LANG=nb_NO.UTF-8
 LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
 PATH=(custom, no user)
 TERM=linux
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-16-generic root=UUID=f1d0446d-3ea3-46a7-9842-8773acca78e6 ro crashkernel=384M-2G:64M,2G-:128M quiet
Signal: 6
SourcePackage: xorg-server
StacktraceTop:
 ?? ()
 CloseWellKnownConnections ()
 ?? ()
 FatalError ()
 ?? ()
Title: Xorg crashed with SIGABRT in CloseWellKnownConnections()
UpgradeStatus: Upgraded to quantal on 2012-08-31 (33 days ago)
UserGroups:

dmi.bios.date: 08/30/2010
dmi.bios.vendor: GIGABYTE
dmi.bios.version: GSBF05
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: T1005
dmi.board.vendor: GIGABYTE
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnGIGABYTE:bvrGSBF05:bd08/30/2010:svnGIGABYTE:pnT1005:pvrGSBF05:rvnGIGABYTE:rnT1005:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
dmi.product.name: T1005
dmi.product.version: GSBF05
dmi.sys.vendor: GIGABYTE
version.compiz: compiz 1:0.9.8.4-0ubuntu1
version.libdrm2: libdrm2 2.4.39-0ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 9.0~git20120917.7cfd42ce-0ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.0~git20120917.7cfd42ce-0ubuntu3
version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu5
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu2

Revision history for this message
Marius B. Kotsbak (mariusko) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 _XSERVTransClose (ciptr=0xb8b48d78) at /usr/include/X11/Xtrans/Xtrans.c:902
 CloseWellKnownConnections () at ../../os/connection.c:515
 AbortServer () at ../../os/log.c:649
 FatalError (f=f@entry=0xb773e7b8 "%s: VT_ACTIVATE failed: %s\n") at ../../os/log.c:793
 switch_to (vt=7, from=from@entry=0xb773e841 "xf86CloseConsole") at ../../../../../hw/xfree86/os-support/linux/lnx_init.c:64

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in xorg-server (Ubuntu):
importance: Undecided → Medium
summary: - Xorg crashed with SIGABRT in CloseWellKnownConnections()
+ Xorg crashed with SIGABRT in _XSERVTransClose()
tags: removed: need-i386-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in xorg-server (Ubuntu):
status: New → Confirmed
Timo Aaltonen (tjaalton)
visibility: private → public
Revision history for this message
penalvch (penalvch) wrote :

Marius B. Kotsbak, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p xorg-server REPLACE-WITH-BUG-NUMBER

Please note, given that the information from the prior release is already available, doing this on a release prior to the development one would not be helpful.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

tags: added: bios-outdated-f9
Changed in xorg-server (Ubuntu):
importance: Medium → Low
status: Confirmed → Incomplete
tags: added: trusty
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.]

Changed in xorg-server (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Karsten Wilmesmeyer (kharst) wrote :

Hello, i got the same error after log into my brandnew installed ubuntu 14.04. It was the second time installing the system
with no error at the first installation.
The difference lies in activating the SATA-AHCI-BIOS-option for my hdd at the second installation. Switching it back no error
appears.

K. Wilmesmeyer.

Revision history for this message
penalvch (penalvch) wrote :

Karsten Wilmesmeyer, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report by executing the following in a terminal:
ubuntu-bug xorg

Please ensure you have xdiagnose installed, and that you click the Yes button for attaching additional debugging information.

For more on this, please see the official Ubuntu documentation:
Ubuntu X.Org Team, Ubuntu Bug Control, and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report will delay your problem being addressed as quickly as possible.

Thank you for your understanding.

To post a comment you must log in.