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.
** Changed in: gnome-panel (Ubuntu)
Status: Needs Info => Rejected
--
[apport] gnome-panel crashed with SIGSEGV in __pthread_mutex_unlock_usercnt()
https://launchpad.net/bugs/85055
--
desktop-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs