fyi, I fixed this by removing .config/dconf/user
--
You received this bug notification because you are a member of compiz
packagers, which is subscribed to compiz in Ubuntu.
https://bugs.launchpad.net/bugs/750386
Title:
compiz crashed with SIGABRT in raise() from abort() 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 compiz
packagers, which is subscribed to compiz in Ubuntu.
https://bugs.launchpad.net/bugs/750386
The latest compiz packages that installed (2012-11-06) have fixed the
problem.
--
You received this bug notification because you are a member of compiz
packagers, which is subscribed to compiz in Ubuntu.
https://bugs.launchpad.net/bugs/1067820
Title:
compiz crashed with SIGABRT in raise()
To
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 compiz
packagers, which is
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 compiz
packagers, which is subscribed to compiz in Ubuntu.
https://bugs.launchpad.net/bugs/750386
Title:
compiz crashed with SIGABRT in raise() from
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
Just this one: deb http://dl.google.com/linux/talkplugin/deb/ stable
main
--
You received this bug notification because you are a member of compiz
packagers, which is subscribed to compiz in Ubuntu.
https://bugs.launchpad.net/bugs/750386
Title:
compiz crashed with SIGABRT in raise() from
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
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
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
Further to my comment #17:
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/750386/comments/17
I found that the as of Beta 2 that trick by itself doesn't work any
longer. I have to rm -rf /home/me/.cache/compiz* and restart lightdm
to get it to work. It's a reliable (for me) fix such that
I should also add this happens only on two of my machines (a system76
model and a zareason model) both with NVIDIA cards, but not my Thinkpad
(Intel card).
--
You received this bug notification because you are a member of compiz
packagers, which is subscribed to compiz in Ubuntu.
I had the same problem. I tried the above suggestions without success.
I also tried gconf-cleaner with no luck. I was finally able to fix this
by doing an rm -rf .compiz* from my home directory and restarting
lightdm.
--
You received this bug notification because you are a member of compiz
14 matches
Mail list logo
