Ubuntu
gnome-panel package

gnome-panel crashed with SIGABRT in __kernel_vsyscall()

Bug #887189 reported by Eliah Kagan
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-panel (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

On a Precise i386 system with ubuntu-desktop 1.245, gnome-session-fallback 3.2.1-0ubuntu1, and gnome-panel 1:3.2.0-0ubuntu1, I had installed gnome-session-fallback (which installed gnome-panel as a dependency) while in a Unity 2D session, and then I had logged out and logged in to a "GNOME Classic" session, and then I had logged out again and logged in to a "GNOME Classic (no effects)" session. Since this is a VMware Workstation 8.0.0 build-741780 virtual machine with no graphics acceleration, I wonder if perhaps the latter two sessions were equivalent. In any case, while there had been no crash prior to entering the "GNOME Classic (no effects)" session, shortly after the start of that session I was informed by Apport that gnome-panel had crashed with SIGABRT in __kernel_vsyscall(). The stack trace has no more symbols and doesn't look very good, but perhaps the Apport retracing service will be able to make something of it.

I did not see any other incorrect or undesirable behaviour from gnome-panel; the panel seemed to work fine, and did not even visibly flicker momentarily.

This might be the same as invalid bug 876799 (which occurred under somewhat similar circumstances and could not be effectively retraced), and/or as any one of a few valid bugs: bug 759451, bug 850113, or bug 507062. Hopefully a retracing will provide the necessary information to tell.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-panel 1:3.2.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.1.0-2.3-generic 3.1.0
Uname: Linux 3.1.0-2-generic i686
ApportVersion: 1.25-0ubuntu1
Architecture: i386
Date: Sun Nov 6 11:33:04 2011
ExecutablePath: /usr/bin/gnome-panel
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
ProcCmdline: gnome-panel
Signal: 6
SourcePackage: gnome-panel
StacktraceTop:
 __kernel_vsyscall ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: gnome-panel crashed with SIGABRT in __kernel_vsyscall()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

See original description
Revision history for this message
Eliah Kagan (degeneracypressure) wrote :
visibility: private → public
Eliah Kagan (degeneracypressure)
description: updated
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __kernel_vsyscall ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()

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 gnome-panel (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 an useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

libsqlite3-0 version 3.7.7-2ubuntu2 required, but 3.7.9-1ubuntu1 is available
libnih1 version 1.0.3-4ubuntu4 required, but 1.0.3-4ubuntu5 is available
libnih-dbus1 version 1.0.3-4ubuntu4 required, but 1.0.3-4ubuntu5 is available

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-i386-retrace
Revision history for this message
Eliah Kagan (degeneracypressure) wrote :

This is almost certainly bug 507062, see https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/507062/comments/94.

Revision history for this message
Bryce Harrington (bryce) wrote :

As per my comment on bug #507062, unduping this bug until more definitive evidence can be gathered that this is the same bug; apport unfortunately could not get a proper stacktrace for this one. Would you mind collecting one by hand via gdm? I think that would probably help. Or, if you could elaborate on how you're concluding it's the same bug, that might help.

Also, bug #507062 appears to be tripping a Launchpad bug (it repeatedly OOPSes for me), so if this is a dupe it will be very hard to work on it on that bug report.

Changed in gnome-panel (Ubuntu):
status: Invalid → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in gnome-panel (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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