** 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
Bu
** 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.
https://bugs.launchpad.net/bugs/75
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 malloc_p
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
__libc_mess
@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 cra
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
__libc_messa
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
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 abort(
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,
pleas
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 /home/
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"
htt
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
__lib
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 sh
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 happ
@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.
https://bugs.launchpad.ne
** 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() f
** 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)
Stat
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
_
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 rais
** 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.
https://bugs.launchpad.net/bugs/7503
** 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.
https://bugs.launchpad.net/bugs/75
@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 un
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.
https://bugs.la
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 lig
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
** Description changed:
+ You have landed here because you encountered some heap corruption
+ causing your compiz to crash. Arguably your bug is different to this
+ one, however as most heap corruption is untraceable with regular crash
+ reports and stack traces, it is probably better to leave you
Is this really fixed? It still shows up. See bug #1059847.
--
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()
To manage notifications about this bug
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
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//.cache/compiz* and restart lightdm
to get it to work. It's a reliable (for me) fix such that I
Not fixed. Says Fix Released a year ago for Oneiric , so how can it be the
same bug a year later in Quantal, unless it's a regression? Began when I
switched to Quantal beta. Unity taskbar freezes then disappears and reappears a
few times. Can open files by clicking on desktop items but windows
Recent upgrades may have fixed it. I've got Unity working right now. I
did rm -rf .compiz* from my home directory and but was unable to restart
lightdm: lack of permissions on org.freedesktop.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
See also https://bugs.launchpad.net/ubuntu/quantal/+source/unity/+bug/1045187
which says "Changed in unity: Status:Fix Committed → Fix Released"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/750386
My Quantal installation still crashes after a minute. I tried 'apt-get
autoremove' and renaming my autostart directory in /.conf/. Trying
gconf-cleaner gets "Gtk-WARNING: cannot open display". My duplicate bug
is https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1055002.
--
You received this
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 Ubuntu
Bugs
I actually now think this had to do with some autostart applications set
in gnome-session-properties. I disabled a few and now can log in to my
desktop and have it usuable on a regular basis.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
When I log in my session, unity is unresponsive for a few minutes, then
crashes. Apport told me this was this bug report.
--
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 w
** Tags added: quantal
--
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()
To manage notifications about this bug go to:
https://bugs.launchpad.net/un
I used 'apt-get autoremove', something I had not done after upgrading to
Quantal, and then I was able to use compiz again.
--
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
I reported bug 1045965, when running quantal, which was marked as a
duplicate of this bug report.
--
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()
** Changed in: compiz (Ubuntu Oneiric)
Status: Fix Committed => Fix Released
** Changed in: compiz (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
** Branch linked: lp:ubuntu/unity
--
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()
To manage notifications about this bug go to:
https://bugs.launc
This bug was fixed in the package unity - 4.20.0-0ubuntu1
---
unity (4.20.0-0ubuntu1) oneiric; urgency=low
* New upstream release + cherry-pick:
- compiz crashed with SIGSEGV in PluginClassHandler::get() (LP: #835259)
- dash does not scroll down during keyboard navigation (L
** Branch linked: lp:~ubuntu-desktop/unity/ubuntu
--
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()
To manage notifications about this bug go to:
ht
** Changed in: unity
Status: Fix Committed => Fix Released
--
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()
To manage notifications about th
** Changed in: unity
Status: Confirmed => Fix Committed
** Changed in: compiz (Ubuntu Oneiric)
Status: Confirmed => Fix Committed
** Changed in: unity (Ubuntu Oneiric)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubunt
Seeiing if I can reproduce it.
** Changed in: unity
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/750386
Title:
compiz crashed with SIGABRT
** Tags added: didrocks-oneiric-lilst
** Tags removed: didrocks-oneiric-lilst
** Tags added: didrocks-oneiric-list
--
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 SI
** Changed in: unity
Status: Incomplete => Confirmed
** Changed in: unity
Milestone: None => 4.20.0
--
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 SIGABR
I've been able to reproduce (bug 860317)
I opened a session and had a staking problem with the switcher, opened a
terminal and entered "unity --reset" to see if it improved things.
Since I didn't run the command in the background and couldn't close the
terminal, I opened another tab and entered t
Ok, how can i reproduce that? What are the steps to reproduce please?
** Changed in: unity
Status: Confirmed => Incomplete
** Changed in: unity (Ubuntu Oneiric)
Status: Triaged => Incomplete
** Changed in: compiz (Ubuntu Oneiric)
Status: Triaged => Incomplete
--
You receiv
** Tags added: rls-mgr-o-tracking
--
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()
To manage notifications about this bug go to:
https://bugs.launc
** Also affects: compiz (Ubuntu Oneiric)
Importance: High
Assignee: Canonical Desktop Experience Team (canonical-dx-team)
Status: Triaged
** Also affects: unity (Ubuntu Oneiric)
Importance: High
Assignee: Canonical Desktop Experience Team (canonical-dx-team)
Status: T
** Changed in: unity (Ubuntu)
Status: Confirmed => Triaged
** Changed in: compiz (Ubuntu)
Status: Confirmed => Triaged
--
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:
comp
** Changed in: compiz (Ubuntu)
Assignee: (unassigned) => Canonical Desktop Experience Team
(canonical-dx-team)
** Changed in: unity (Ubuntu)
Assignee: (unassigned) => Canonical Desktop Experience Team
(canonical-dx-team)
--
You received this bug notification because you are a member
** Tags added: iso-testing
--
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()
To manage notifications about this bug go to:
https://bugs.launchpad.ne
** Tags added: oneiric
--
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()
To manage notifications about this bug go to:
https://bugs.launchpad.net/un
Apport pointed me here from bug #852826 which just happened to me on
latest Oneiric. Reopening.
** Changed in: unity
Status: Incomplete => Confirmed
** Changed in: compiz (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: unity (Ubuntu)
Status: Incomplete => Confirmed
** Tags added: bugpattern-needed
--
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()
To manage notifications about this bug go to:
https://bugs.launch
Hmm, this sounds like an old bug, and possibly one related to the fglrx
driver workaround that was released for Natty, and then reintroduced
recently in Oneiric since it's still rquired.
I'll makr this bug invalid for now. If someone can still reproduce the
issue, please reopen the bug.
** Change
** Changed in: unity
Importance: Undecided => Critical
** Changed in: compiz (Ubuntu)
Importance: Medium => Critical
** Changed in: unity (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
the duplicate bugs are from unity 3.8.8 so its definitely not fixed, you
may just not be facing the issue anymore.
** Also affects: unity (Ubuntu)
Importance: Undecided
Status: New
** Changed in: compiz (Ubuntu)
Status: New => Confirmed
** Changed in: unity (Ubuntu)
Statu
After the beta release of 11.04, this issue has gone. It has only left
the plymouth boot screen slightly 'blown up'.
Thanks !
--
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 cras
** Also affects: unity
Importance: Undecided
Status: New
--
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() after activating ATI drivers
--
** 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/750386
Title:
compiz crashed with SIGABRT in raise() after activating ATI drivers
--
ubuntu-bugs mailing list
ubuntu-
67 matches
Mail list logo
