@Petter Flensburg To make your new stack trace (also called a backtrace) maximally helpful, it would be good if you were to install some debug symbol packages. Some of the applicable packages are only available in the -dbgsym (rather than -dbg) variety, so first follow the instructions at https://wiki.ubuntu.com/DebuggingProgramCrash to enable the ddebs repositories. Then run "sudo apt-get update; sudo apt-get install indicator-sound-dbgsym libglib2.0-0-dbg libdbusmenu-glib4-dbgsym libgtk-3-0-dbg unity-services-dbgsym unity-dbgsym" (all on one line, without the quotes) to install the debug symbol packages that are most clearly useful to this bug. Then you'll need to reproduce the crash and get a stack trace. Probably the easiest way to do that is to let Apport create a new bug report and indicate which bug it is here (as there are already some duplicates). Conor Curran may have a different way he'd prefer for you to do it (such as manually with gdb, see https://wiki.ubuntu.com/Backtrace), so whatever he says should be taken to supersede this suggestion.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/819116 Title: unity-panel-service crashed with SIGSEGV in g_variant_type_info_unref() To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-sound/+bug/819116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
