OK, I can confirm this bug is not a problem with my system. It happens
consistently only when I run compiz under valgrind. Without valgrind it
has never crashed.
Strangely however, it seems to be fixed by the fix for bug 1064791,
landing soon. I might be imagining things but I have triple checked.
Seems fixed by lp:~compiz-team/compiz/compiz.fix_1064791.
So this bug remains Incomplete until that fix is released and more
people can verify.
** Changed in: compiz
Status: Invalid => Confirmed
** Changed in: compiz
Status: Confirmed => Incomplete
** Changed in: compiz (Ubuntu)
Status: Invalid => Incomplete
** Changed in: compiz
Milestone: None => 0.9.9.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1044662
Title:
compiz crashed with signal 5 (SIGTRAP) in g_logv() from g_log() from
g_settings_schema_get_value() from g_settings_schema_key_init() from
g_settings_get_value()
To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/1044662/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
