desktop-packages team mailing list archive

[Bryce Harrington <887189@xxxxxxxxxxxxxxxxxx>]

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-panel in Ubuntu.
https://bugs.launchpad.net/bugs/887189

Title:
  gnome-panel crashed with SIGABRT in __kernel_vsyscall()

Status in “gnome-panel” package in Ubuntu:
  Incomplete

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/887189/+subscriptions