[apport] gnome-panel crashed with SIGSEGV

[jkuhnert]

Binary package hint: gnome-panel

Have no idea. Happens every time I login through gdm.

ProblemType: Crash
Date: Mon Feb 5 20:18:15 2007
Disassembly: 0xb754c984:
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/jkuhnert
ProcEnviron:
 PATH=/usr/local/ant/bin:/usr/local/maven/bin:/usr/local/java/bin:/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
Stacktrace:
 Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
 #0 0xb754c984 in ?? ()
StacktraceTop: ?? ()
ThreadStacktrace:

Uname: Linux spaz 2.6.20-6-generic #2 SMP Wed Jan 31 20:53:39 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

[Sebastien Bacher (seb128)]

Thank you for your bug. The coredump attach to the bug is not correct which is probably due to a problem with linux on feisty at the moment, could you try to get a new one with gnome-panel-dbg libglib2.0-0-dbg libgtk2.0-0-dbg installed?

[jkuhnert (jkuhnert)]

I can't find gnome-panel-dbg searching through apt but did find the others. Expect a new "automated" bug report momentarily.

(somehow I feel like a middle man, maybe it would be easier if you could tell my computer what you wanted it to do for me ;) )

[Sebastien Bacher (seb128)]

the wiki page https://wiki.ubuntu.com/DebuggingProgramCrash has instructions to install -dbgsym packages, you can use that for gnome-panel

[jkuhnert (jkuhnert)]

ack - installing and re-submitting now (though I'm sure i'm just spamming with duplicates by this point)

[Freddy Martinez (freddymartinez9)]

Can you tell us what architecture you are running? also, do you have another crash report that can be found in /var/crash? Thanks.

[jkuhnert (jkuhnert)]

I must have a lot of old tickets floating around out there. This was eventually fixed by one of the various updates and I've not ever seen this particular bug happen again.

[Sebastien Bacher (seb128)]

closing for now then, feel free to reopen if that happens again