Ubuntu
gnome-panel package

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

Bug #85055 reported by Leon van der Ree on 2007-02-14

Affects		Status	Importance	Assigned to	Milestone
	gnome-panel (Ubuntu)	Invalid	Medium	Ubuntu Desktop Bugs

Bug Description

Binary package hint: gnome-panel

Happend after or during updating.

How can I see if this is a duplicate of for example: 82146
And if it is a duplicate, is this still valuable: do/don't you need this data then anymore.

ProblemType: Crash
Date: Wed Feb 14 11:04:47 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/gnome-panel
Package: gnome-panel 2.17.91-0ubuntu1
ProcCmdline: gnome-panel --sm-config-prefix /gnome-panel-xPU2Wz/ --sm-client-id 117f000101000117101407000000066460012 --screen 0
ProcCwd: /usr/bin
ProcEnviron:
LANGUAGE=nl_NL.UTF-8@euro
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
LANG=nl_NL.UTF-8@euro
SHELL=/bin/bash
Signal: 11
SourcePackage: gnome-panel
StacktraceTop:
?? () from /lib/tls/i686/cmov/libc.so.6
?? ()
__pthread_mutex_unlock_usercnt ()
malloc () from /lib/tls/i686/cmov/libc.so.6
g_malloc () from /usr/lib/libglib-2.0.so.0
Uname: Linux leon-laptop 2.6.20-8-generic #2 SMP Tue Feb 13 05:18:42 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev scanner video

Revision history for this message

Leon van der Ree (lvanderree) wrote on 2007-02-14:

Dependencies.txt Edit (7.5 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (811 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (36.3 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (666 bytes, text/plain; charset="utf-8")
Registers.txt Edit (531 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (852 bytes, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (589 bytes, text/plain; charset="utf-8")

Revision history for this message

Sebastien Bacher (seb128) wrote on 2007-02-14:

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:	Unconfirmed → Needs Info

Revision history for this message

Leon van der Ree (lvanderree) wrote on 2007-02-14:

I'm afraid I can't reproduce the bug, so let alone making it happing again while it runs under valgrind.

Any ideas on how it might be reproduced,
or might it be possible that it happens because the update replaced some libraries gnome-panel was using?

Revision history for this message

Sebastien Bacher (seb128) wrote on 2007-02-14:

closing the bug for now, feel free to reopen if you can get the required log. We have a bunch of similar bugs, without a valgrind log there is no real way to figure what is going on though. One way to try to get a valgrind log of the crash would be to run gnome-panel with valgrind until the next crash, it makes things slow and not easy to use though.