*** This bug is a duplicate of bug 85776 ***
https://bugs.launchpad.net/bugs/85776
** Attachment removed: CoreDump.gz
http://launchpadlibrarian.net/6838861/CoreDump.gz
--
[apport] gnome-panel crashed with SIGSEGV in __pthread_mutex_unlock_usercnt() -
srashed today when updating the
** Attachment added: CoreDump.gz
http://librarian.launchpad.net/6838861/CoreDump.gz
** Attachment added: Dependencies.txt
http://librarian.launchpad.net/6838862/Dependencies.txt
** Attachment added: Disassembly.txt
http://librarian.launchpad.net/6838863/Disassembly.txt
** Attachment
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). Right that
looks like a duplicate
** Changed in: gnome-panel (Ubuntu)
Importance: Undecided =
Could you try to get a valgrind log for it?
not really, it happened only once and spontaneously while update manager was
doing something in the background :(
Iv seen gnome-panel crash in dapper when some applet died (bubblemon,netspeed),
but I have no applets but the clock in feisty (not even
umm no, I have netspeed :)
anyway in dapper there was applet 'would you like to cancel/reload applet X'
message before gnome-panel crashed, so its something different
--
[apport] gnome-panel crashed with SIGSEGV in __pthread_mutex_unlock_usercnt() -
srashed today when updating the kernel
*** This bug is a duplicate of bug 85776 ***
no problem, marking duplicate then
** This bug has been marked a duplicate of bug 85776
[apport] gnome-panel crashed with SIGSEGV on package installation, valgrind
log required
--
[apport] gnome-panel crashed with SIGSEGV in
