@Thad-daddyslick: I can see you filed a range of bugs (and very much thanks for that! :-)) where the stacktrace ends somewhere down in libdee. If there are serious issues in libdee basically nothing relating to Unity Places ought to work (for everyone, not just you) and we should be swamped in duplicates of your bugs. So I'm kinda puzzled that we don't see those tonnes of dupes.
This got me thinking if there maybe is something special about your system that trigger this? Ideas could be: a) Custom compiled libunity, libdee, unity, or compiz and there is an ABI mismatch somewhere giving you memory corruption b) You graphics (or other) driver is buggy and gives some memory corruption that for some reason is likely to manifest itself inside Dee Alternatively i) there is some very elusive race condition in dee that is just much more likely to happen on your particular hardware ii) The Unity plugin for Compiz is accessing deleted rows from the DeeModels or messing up with the ref count on the GVariants from the models If you have time to help get to the bottom of this you can rule out a) and b) (unless or course you know 100% that they are not the case) by: + Rule out a) : Run a clean install with all latest packages + Rule out b) : Run Unity2D (see https://wiki.ubuntu.com/Unity2D for instructions) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/742085 Title: compiz crashed with SIGSEGV in PlaceEntryRemote::GetResult() -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
