Hmm... This stacktrace doesn't seem possible to me. I mean, it's a reasonable trace, but I can't see how we get ourselves into this situation [1]. Which, if true, makes me lean toward memory being corrupted by either my patch or something else.
I'd really like to try to reproduce these crashes so I can investigate rather than guess. Let me get some more info from you so I can try myself: * Are you in unity or classic desktop? If in classic, do you have the appmenu applet running? * Do you switch resolutions or just try to (I know you just try to on the last time, when it crashes, but other times you open the dialog, you actually switch resolutions?) * Any pattern to crashes vs. non-crashes that might be a clue? [1] Looks like a dbus call is coming in after we've destroyed the server object, but one of the things the server does as it dies is make sure that doesn't happen. Though I may be missing something. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/729230 Title: gnome-display-properties crashed with SIGSEGV in invoke_get_all_properties_in_idle_cb() -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
