Xorg crashed with SIGABRT in fbBltOne()

Bug #1543638 reported by Amr Ibrahim
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xorg-server-lts-vivid (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

When I start LibreOffice, the whole session crashes and brings me back to the login screen. This crash started to happen after I purged fglrx and relied on the FOSS driver. The crash didn't happen with fglrx.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: xserver-xorg-core-lts-vivid 2:1.17.1-0ubuntu3.1~trusty1
ProcVersionSignature: Ubuntu 3.19.0-49.55~14.04.1-generic 3.19.8-ckt12
Uname: Linux 3.19.0-49-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
Date: Tue Feb 9 17:15:52 2016
ExecutablePath: /usr/bin/Xorg
ExecutableTimestamp: 1441967742
InstallationDate: Installed on 2015-06-16 (237 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
ProcCwd: /
ProcEnviron:

Signal: 6
SourcePackage: xorg-server-lts-vivid
Title: Xorg crashed with SIGABRT in fbBltOne()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
Amr Ibrahim (amribrahim1987) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceSource:
 #0 0x00007f66c5ba6cc9 in ?? ()
 #1 0x00007f66c5baa0d8 in ?? ()
 #2 0x0000000000000020 in ?? ()
 #3 0x0000000000000000 in ?? ()
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in xorg-server-lts-vivid (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

no debug symbol package found for libevdev2
no debug symbol package found for libxshmfence1
no debug symbol package found for libbz2-1.0
no debug symbol package found for libnih-dbus1
no debug symbol package found for libpciaccess0
no debug symbol package found for libnih1
no debug symbol package found for libepoxy0
no debug symbol package found for libgpg-error0
no debug symbol package found for libelf1
no debug symbol package found for libmtdev1

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

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