** Changed in: compiz
Importance: Undecided => High
** Changed in: compiz
Status: New => Fix Released
** Changed in: compiz
Assignee: (unassigned) => Canonical Desktop Experience Team
(canonical-dx-team)
--
You received this bug notification because you are a member of Ubuntu
** Changed in: compiz (Ubuntu)
Status: Confirmed = Fix Released
** Changed in: compiz (Ubuntu Quantal)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Removing .config/dconf/user also worked for me (so far).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/750386
Title:
compiz crashed with SIGABRT in raise() from abort() from
__libc_message() from
Confirming that removing that file worked for me as well. Can anyone
else comment on whether this works or doesn't work? If it works in the
general case, not just bug #1096457, we can update the problem
description to include this workaround (as I did in the other ticket).
--
You received this
fyi, I fixed this by removing .config/dconf/user
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/750386
Title:
compiz crashed with SIGABRT in raise() from abort() from
__libc_message() from
@vanvugt, I've started posting more diagnostics against @colan's bug of
bug #1096457 since I see the same errors he is getting.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/750386
Title:
compiz
Sorry, I'm not working on Compiz right now. Unsubscribing myself...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/750386
Title:
compiz crashed with SIGABRT in raise() from abort() from
I was able to file a new bug with that debug mode on: bug #1096457
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/750386
Title:
compiz crashed with SIGABRT in raise() from abort() from
The bug I describe in my comment above is bug #1071092 .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/750386
Title:
compiz crashed with SIGABRT in raise() from abort() from
__libc_message() from
@vanvugt: How do we create new bugs with crash reports now that they go
to errors.ubuntu.com instead of Launchpad? Is there a way to do this,
or must we wait until both are supported? I haven't been able to create
new bugs recently because of this problem.
--
You received this bug notification
This still happens for me on two machines. I'm updated current on
2012-08-17.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/750386
Title:
compiz crashed with SIGABRT in raise() from abort() from
** Also affects: compiz (Ubuntu Quantal)
Importance: High
Assignee: Canonical Desktop Experience Team (canonical-dx-team)
Status: Fix Released
** Also affects: unity (Ubuntu Quantal)
Importance: High
Assignee: Canonical Desktop Experience Team (canonical-dx-team)
** Tags added: apport-request-retrace
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/750386
Title:
compiz crashed with SIGABRT in raise() from abort() from
__libc_message() from malloc_printerr()
@joey, @jgs-colorado, @shakaran: can you please try again reporting the
crash? This will open a new bug thanks to the new tag and we can get a
fresh stacktrace.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
some updates...
I've attached two valgrind logs. The problem I had though was gnome-
session was grabbing compiz.bin and executing directly when the crashes
occurred so the valgrind logs I do have don't cover that exact case.
However, they do show a bunch of errors.
I took a video of what's
On 18/10/12 08:59, Joey Stanford wrote:
some updates...
I've attached two valgrind logs. The problem I had though was gnome-
session was grabbing compiz.bin and executing directly when the crashes
occurred so the valgrind logs I do have don't cover that exact case.
However, they do show a
I restarted this with valgrind again and I can't get it crash when it's
called from valgrind. As soon as I put the original compiz back it
causes a freeze (which is not in the video). I did get two more grinds
out of though in case they are of any help.
** Attachment added: valgrind logs
Just this one: deb http://dl.google.com/linux/talkplugin/deb/ stable
main
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/750386
Title:
compiz crashed with SIGABRT in raise() from abort() from
fwiw, after the valgrind experiment I had to include another line item
to my workaround... normally removing .compiz and .cache/compiz and
restarting lightdm works. I added the compiz.desktop to keep it from
picking up the test script I was using.
#!/bin/sh
sudo service lightdm stop
rm -rf
I don't think it's sensible to reopen/reuse this old bug for quantal.
Heap corruption can be introduced by any manner of new logic. And the
crash it produces will often have an old-looking call stack like this
one.
Instead we should focus on finding the corruption at its source. To do that,
Joey,
Please log a new bug about any crash you can produce with valgrind or
otherwise.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/750386
Title:
compiz crashed with SIGABRT in raise() from
This is making 12.10 beta nearly unusable for me. This happened
following login and no other activity.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/750386
Title:
compiz crashed with SIGABRT in
@vanvugt I try to produce a better crash report but it is difficult
because when unity/compiz crash you don't windows borders for move
windows and pressing keys for write doesn't write anything.
So, I boot the pc. Enter in a lightdm session. Then I open a terminal. I
fire up google-chrome. Then
** Attachment added: unity-replace2.log
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/750386/+attachment/3379714/+files/unity-replace2.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: unity-replace.log
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/750386/+attachment/3379734/+files/unity-replace.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
100% reproducible bug in quantal with several machines using even FOSS
drivers with ati. Very annoning bug. The only temporal workaround that
works for me was commented previously. Just my 2 cent using one command
less:
sudo service lightdm stop
rm -rf ~/.compiz* ~/.cache/.compiz*
sudo service
All - Please try this to produce a better crash report that will help us
find the root cause of the problem:
env MALLOC_CHECK_=3 G_SLICE=always-malloc unity --replace
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Apparently this is still happening to many people (including myself) and
I'm getting pings and emails about the work-around that I've discovered.
This is the script that I use. Don't trust me... research this
yourself.
1) I login at lightdm and verify that launching anything from Unity causes a
28 matches
Mail list logo
