[apport] gnome-panel crashed with SIGSEGV

Bug #92776 reported by useResa
2
Affects Status Importance Assigned to Milestone
gnome-panel (Ubuntu)
Incomplete
Medium
Ubuntu Desktop Bugs

Bug Description

I am running Feisty in VirtualBox. My main OS is Edgy and my hardware is a Dell Latitude D620.

Received a notification from Update Manager that updates were available and started update manager. Just out of curiosity and to monitor progress I normally switch on "Show details"

The last manage in the details window shows "setting up linux-restricted-modules-generic (2.6.20.11.7)". The window however also indicates that all changes were applied. This is when the error showed up.

ProblemType: Crash
Architecture: i386
Date: Fri Mar 16 12:07:55 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/gnome-panel
Package: gnome-panel 2.18.0-0ubuntu2
PackageArchitecture: i386
ProcCmdline: gnome-panel --sm-client-id default1
ProcCwd: /home/rdrijsen
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: gnome-panel
StacktraceTop:
 ?? () from /lib/tls/i686/cmov/libc.so.6
 ?? ()
 ?? ()
 ?? () from /lib/tls/i686/cmov/libc.so.6
 ?? ()
Uname: Linux rdrijsen-feisty 2.6.20-10-generic #2 SMP Mon Mar 12 00:02:49 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Revision history for this message
useResa (rdrijsen) wrote :
Revision history for this message
useResa (rdrijsen) wrote :

Please find attached the window status of the update manager when the error popped up.

Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

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

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for your bug report. The crash looks like a memory corruption. Could you try to get a valgrind log for it? (you can follow the instructions from https://wiki.ubuntu.com/Valgrind for that)

Changed in gnome-panel:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: Confirmed → Needs Info
Revision history for this message
useResa (rdrijsen) wrote :

Since it happened during running update-manager and based on your request I have issued the following command:
G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck --leak-check=full --num-callers=12 --log-file=valgrind.log /usr/bin/update-manager

Please find attached the result in the tar file

Revision history for this message
useResa (rdrijsen) wrote :

Sorry for the typo: The description of the file should of course be: "valgrind log tar file"

Revision history for this message
Sebastien Bacher (seb128) wrote :

thank you for your work

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.