The only thing internally consistent in the backtrace is that passing NULL to gtk_path_bar_unmap() would cause a crash -- gtk_path_bar_unmap() passes the argument along to gtk_path_bar_stop_scrolling(), which dereferences it immediately without testing for NULL. (This is true in both GTK+ 3.1.10 and in Oneiric's 3.2.0).
However the rest of the crash report is corrupt. gtk_menu_get_monitor() (at gtkmenu.c:5760 in GTK+ 3.1.10) doesn't have anything to do with gtk_path_bar_unmap(), so just as cjcurran says, a proper stack trace would help a lot here. Is anyone still experiencing this in Oneiric? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/816182 Title: unity-panel-service crashed with SIGSEGV in g_type_check_class_cast() To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-sound/+bug/816182/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
