[Expired for Compiz because there has been no activity for 60 days.]
** Changed in: compiz
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1067820
Title:
compiz
[Expired for compiz (Ubuntu) because there has been no activity for 60
days.]
** Changed in: compiz (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1067820
The latest compiz packages that installed (2012-11-06) have fixed the
problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1067820
Title:
compiz crashed with SIGABRT in raise()
To manage
Joey,
A full system freeze is a kernel bug. But I doubt you have a full system
freeze. Please try logging into the VT (or logging in via SSH) before it
happens...?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On 10/18/2012 08:18 PM, Daniel van Vugt wrote:
Joey,
That valgrind log is from a python process (probably the unity script)
and not from compiz/unity.
Please do:
env MALLOC_CHECK_=3 G_SLICE=always-malloc unity --replace
And you might wish to retry valgrind with:
This valgrind log is for unity 6.8.0-0ubuntu amd64
** Attachment added: valgrind log
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1067820/+attachment/3402845/+files/valgrind.log.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Joey,
That valgrind log is from a python process (probably the unity script)
and not from compiz/unity.
Please do:
env MALLOC_CHECK_=3 G_SLICE=always-malloc unity --replace
And you might wish to retry valgrind with:
--trace-children=yes
--
You received this bug notification because
Sorry, two things:
1. There is no stack trace in this bug. So we can't do anything with it.
2. If it is heap corruption like bug 750386 then we need to find its source.
If you're not game enough to get valgrind working then please do this:
env MALLOC_CHECK_=3 G_SLICE=always-malloc unity
P.S. All sources of heap corruption in the compiz process over the past
few weeks have come from the unityshell plugin. But I thought they were
mostly fixed already...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Daniel: maybe try with thumper, Joey is telling that he has the same
issue reliably in one of his box.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1067820
Title:
compiz crashed with SIGABRT in
There is also a heap corruption crash waiting in the -proposed archives
(should migrate there soon from unapproved to approved). Look for unity
6.10.0 there and maybe it will fix your particular issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
11 matches
Mail list logo
