[apport] gnome-panel crashed with SIGSEGV in malloc()

Bug #82679 reported by hawkes
2
Affects Status Importance Assigned to Milestone
gnome-panel (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gnome-panel

Gnome-Panel crashed after todays apt-get upgrade

ProblemType: Crash
Date: Thu Feb 1 16:11:41 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/gnome-panel
Package: gnome-panel 2.17.90-0ubuntu1
ProcCmdline: gnome-panel --sm-client-id default1
ProcCwd: /home/hawkes
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: gnome-panel
StacktraceTop:
 ?? () from /lib/libc.so.6
 malloc () from /lib/libc.so.6
 _gdk_xsettings_setting_copy ()
 _gdk_xsettings_client_get_setting ()
 gdk_screen_get_setting ()
Uname: Linux ela 2.6.20-5-generic #2 SMP Sat Jan 6 09:44:32 UTC 2007 x86_64 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip lpadmin plugdev scanner video

Revision history for this message
hawkes (hawkes) wrote : Dependencies.txt
Revision history for this message
hawkes (hawkes) wrote : Disassembly.txt
Revision history for this message
hawkes (hawkes) wrote : ProcMaps.txt
Revision history for this message
hawkes (hawkes) wrote : ProcStatus.txt
Revision history for this message
hawkes (hawkes) wrote : Registers.txt
Revision history for this message
hawkes (hawkes) wrote : Stacktrace.txt
Revision history for this message
hawkes (hawkes) wrote : ThreadStacktrace.txt
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug. That looks like a memory corruption bug, could you get a valgrind log (https://wiki.ubuntu.com/Valgrind) for it?

Changed in gnome-panel:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: Unconfirmed → Needs Info
Revision history for this message
hawkes (hawkes) wrote : Re: [Bug 82679] Re: [apport] gnome-panel crashed with SIGSEGV in malloc()

On Do, 2007-02-01 at 15:22 +0000, Sebastien Bacher wrote:
> Thank you for your bug. That looks like a memory corruption bug, could
> you get a valgrind log (https://wiki.ubuntu.com/Valgrind) for it?

Mmh - I've tried now for two hours to reproduce this bug and generate a
valgrind log, but i guess, for now, this bug is unreproducable.

Maybe we can close this bug and i reopen it, if i find a similiar
stacktrace.

Greetings,

Christoph
>
> ** Changed in: gnome-panel (Ubuntu)
> Importance: Undecided => Medium
> Assignee: (unassigned) => Ubuntu Desktop Bugs
> Status: Unconfirmed => Needs Info
>

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

ok, thank you for the work on that. Closing for now, feel free to reopen if you can get the valgrind log for the problem

Changed in gnome-panel:
status: Needs Info → Rejected
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.