This happens because: 1. When a GConf key does not exist, its value is null. 2. mouse_button_mods_handler(), which is the handler for the key "/apps/metacity/general/mouse_button_modifier", calls meta_ui_accelerator_parse() with the value of that key. 3. meta_ui_accelerator_parse() immediately deferences that value, which may be null. Optimisation may cause this to appear as though it had happened within mouse_button_mods_handler().
The solution is to make mouse_button_mods_handler() ignore the value if the key is missing. I've just committed this upstream. The more interesting question is why on earth this key was missing for you in the first place. -- metacity crashed with SIGSEGV in mouse_button_mods_handler() https://bugs.launchpad.net/bugs/258074 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
