Should have expired at this point.
** Changed in: compiz (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/746848
Title:
compiz crashed with SIGSEGV in g_c
What appears to have happened here is that 0x600 was treated as a
closure, which it wasn't, and the field read from there as the pointer
to the code must have been 0x0. The trouble is that we have no way of
knowing from this what the closure was *supposed* to be, unless we can
reproduce the bug
** Changed in: compiz (Ubuntu)
Status: New => Confirmed
** Changed in: compiz (Ubuntu)
Assignee: (unassigned) => Thomas Thurman (marnanel)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/746
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/746848
Title:
compiz crashed with SIGSEGV in g_closure_invoke()
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.
