A few thoughts: 1. The corrupt line #2 in Stacktrace is likely to be indicator- appmenu/src/huddbusmenucollector.c's hud_dbusmenu_collector_property_changed(). dbusmenuitem's "property- changed" signal is the only one whose signature matches the void-string- variant one in Stacktrace's 3rd line.
2. So it looks like this crash is coming in huddbusmenucollector.c when the collector->items hashtable pointer is corrupt (to the very suspicious value 0xaaaaaaaa). However I don't see in the source code how that's happening. 3. Also, indicator-appmenu's gone through very heavy development over the last couple of months. In fact there have been 5 releases (the latest being 0.3.97) since the one involved in this crash (0.3.92) and the code involved in this crash has gone through heavy rewrites in that interval. So I think what we need here is to know whether the crash is reproducible in a newer version of Ubuntu. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/ . Thanks again and we appreciate your help. ** Changed in: indicator-appmenu Status: Confirmed => Incomplete ** Changed in: indicator-appmenu (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/953482 Title: hud-service crashed with SIGSEGV in g_hash_table_lookup_node() To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-appmenu/+bug/953482/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
