Xorg crashed with SIGABRT in OsAbort()

Bug #1407173 reported by Lacyc3
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
xorg-server (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Xubuntu 14.10
Xorg version: 1:7.7+7ubuntu2
Xserver-xorg-core version: 2:1.16.0-1ubuntu1.2
Kernel: 3.16.0-28-generic #38-Ubuntu

Reproduce:
echo 1 | sudo tee /proc/sys/kernel/sysrq
Push: altgr+printscr+k

I expected that Xorg restarts normally, but it crashed.

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: xserver-xorg-core 2:1.16.0-1ubuntu1.2
ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
Uname: Linux 3.16.0-28-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
Date: Fri Jan 2 23:05:17 2015
ExecutablePath: /usr/bin/Xorg
ExecutableTimestamp: 1418166202
InstallationDate: Installed on 2014-12-22 (11 days ago)
InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
ProcCwd: /etc/X11
ProcEnviron:

Signal: 6
SourcePackage: xorg-server
StacktraceTop:
 OsAbort ()
 ?? ()
 FatalError ()
 ?? ()
 __libc_start_main (main=0x7f0676841740, argc=11, argv=0x7fff8bc77d28, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff8bc77d18) at libc-start.c:287
Title: Xorg crashed with SIGABRT in OsAbort()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
Lacyc3 (lacyc3) wrote :
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 xorg-server (Ubuntu):
status: New → Confirmed
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1338492, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

tags: removed: need-amd64-retrace
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.