unity-2d-panel crashed with SIGABRT in _XError()

Bug #856817 reported by Séverin Lemaignan
32
This bug affects 5 people
Affects Status Importance Assigned to Milestone
unity-2d
Expired
Critical
Unassigned
unity-2d (Ubuntu)
Invalid
Critical
Unassigned

Bug Description

...

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: unity-2d-panel 4.8.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic i686
ApportVersion: 1.23-0ubuntu1
Architecture: i386
Date: Thu Sep 22 23:12:17 2011
ExecutablePath: /usr/bin/unity-2d-panel
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
ProcCmdline: unity-2d-panel
ProcEnviron:
 LANGUAGE=fr:en
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 LC_MESSAGES=fr_FR.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: unity-2d
StacktraceTop:
 ?? () from /usr/lib/libgdk-3.so.0
 ?? () from /usr/lib/libgdk-3.so.0
 _XError () from /usr/lib/i386-linux-gnu/libX11.so.6
 ?? () from /usr/lib/i386-linux-gnu/libX11.so.6
 ?? () from /usr/lib/i386-linux-gnu/libX11.so.6
Title: unity-2d-panel crashed with SIGABRT in _XError()
UpgradeStatus: Upgraded to oneiric on 2011-09-06 (16 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Séverin Lemaignan (skadge) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 detach (this=<optimized out>) at /usr/include/qt4/QtCore/qdebug.h:85
 data (this=<optimized out>) at /usr/include/qt4/QtCore/qbytearray.h:412
 ~QDebug (this=<optimized out>, __in_chrg=<optimized out>) at /usr/include/qt4/QtCore/qdebug.h:85
 KeyMonitor::registerEvents (this=0xbfee362c) at /build/buildd/unity-2d-4.10.0/libunity-2d-private/src/keymonitor.cpp:127
 QByteArray::operator= (this=0x3, other=...) at tools/qbytearray.cpp:866

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 unity-2d (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Changed in unity-2d:
importance: Undecided → Critical
Changed in unity-2d (Ubuntu):
importance: Medium → Critical
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in unity-2d (Ubuntu):
status: New → Confirmed
Revision history for this message
Albert Astals Cid (aacid) wrote :

Looking at the stack trace it seems keymonitor.cpp:127 (frame #11) ends up calling qFatal (frame #9), but in line 127 there is an UQ_WARNING call, not a qFatal call, so that abort you are seeing should not happen. Is it possible that you were running with the QT_FATAL_WARNINGS environment variable defined?

Revision history for this message
Gerry Boland (gerboland) wrote :

We need more information on this. Anybody who can reproduce this, please get in touch with us so we can investigate further

Changed in unity-2d:
status: New → Incomplete
Revision history for this message
Séverin Lemaignan (skadge) wrote :

aacid: I was not using any particular QT specific environment variable.

Revision history for this message
madbiologist (me-again) wrote :

Official support for Ubuntu 11.10 "Oneiric Ocelot" has ended. If this error is still occurring on Ubuntu 14.10 "Utopic Unicorn" please run ubuntu-bug to file a new bug report so that we can get a fresh set of log files and system information.

Changed in unity-2d (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for unity-2d because there has been no activity for 60 days.]

Changed in unity-2d:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.