I noticed in the dupe bug #741403 that the stack trace starts inside libwnck! From update_client_list() inside libwnck's screen.c line 1771. Apparently wnck emits a "window-closed" inside the Compiz process.
Exactly how wnck has ended up inside compiz is unclear, but it definitely shouldn't be there... Maybe a rogue plugin? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/741674 Title: compiz crashed with SIGSEGV in g_closure_invoke() -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
