[HD5000]Application 'compiz.desktop' killed by signal 6

[Daniel Ejsing-Duun]

Not sure if it's Compiz or Unity.

When I log in, half of the times Unity seems to crash. It seems to recover every time when waiting for maybe a minute or so. Switching to another shell and starting up unity works. I stumbled on these syslog lines, which is all it logged during the event:

Oct 28 11:46:11 zelito gnome-session[18339]: WARNING: Application 'compiz.desktop' killed by signal 6
Oct 28 11:46:11 zelito gnome-session[18339]: WARNING: App 'compiz.desktop' respawning too quickly
Oct 28 11:46:11 zelito gnome-session[18339]: CRITICAL: We failed, but the fail whale is dead. Sorry....
Oct 28 11:46:53 zelito gnome-session[18339]: WARNING: App 'compiz.desktop' respawning too quickly
Oct 28 11:46:53 zelito gnome-session[18339]: WARNING: Application 'compiz.desktop' killed by signal 6
Oct 28 11:46:53 zelito gnome-session[18339]: WARNING: App 'compiz.desktop' respawning too quickly

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: unity 6.10.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
Uname: Linux 3.5.0-18-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.6.1-0ubuntu6
Architecture: amd64
CompizPlugins: [core,composite,opengl,compiztoolbox,imgjpeg,decor,move,regex,scale,loginout,workarounds,obs,inotify,commands,vpswitch,addhelper,text,imgpng,place,grid,unitymtgrabhandles,mousepoll,resize,notification,screenshot,expo,wall,ring,unityshell]
Date: Sun Oct 28 12:23:33 2012
InstallationDate: Installed on 2010-11-13 (714 days ago)
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
MarkForUpload: True
SourcePackage: unity
UpgradeStatus: Upgraded to quantal on 2012-10-19 (8 days ago)

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

Now open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

[Daniel Ejsing-Duun (zilvador)]

I'm still waiting to be able to do this, when it happens again. Unfortunately it seems not to write crash reports because several others are already in that directory because of other crashes (maxreports amount reached?). Can I do something about this? Can they be deleted?

[Daniel van Vugt (vanvugt)]

Yes, I believe the crash reports are safe to delete.

[Still (still)]

Hi guys!

  This bug is affecting me too. I can't use my system anymore.
  I have tried the command ubuntu-bug /var/crash/_usr_bin_compiz.1000.crash, but it's not working and is asking to send. It simply stops.
  What can I do?

Kind regards,

Still

[Still (still)]

Hi guys!

  I guess I have figured out how to solve the problem. After I have removed ~/.compiz, ~/.config/compiz*, ~/.gconf* and rebboted, my system works like a charm.
  What have caused the bug, I have no clue.

[]'s,

Still

[Daniel van Vugt (vanvugt)]

No crash details have been provided. Therefore incomplete.

[Daniel Ejsing-Duun (zilvador)]

My apologies. I wrote a comment before setting the status, but it seems not to have been saved.

The error keeps appearing in the syslog and Unity still goes down at most restarts, but no crash file is generated. Is there any other way I can help?

And thanks for your comment, Still.

[Daniel Ejsing-Duun (zilvador)]

I tries on several occasions to submit a crash report (on unity) generated on this crash, but I'm not directed to any new bug report, like Still said.
I can upload the crash file here, if it helps.

[Daniel Ejsing-Duun (zilvador)]

*the crash report was on compiz...not on unity

[Daniel Ejsing-Duun (zilvador)]

After another crash, I tried to run Unity in a terminal and got a segfault a few seconds later. This was the output.

[Daniel Ejsing-Duun (zilvador)]

Changed according to https://wiki.ubuntu.com/X/Triaging .

[Launchpad Janitor (janitor)]

[Expired for fglrx-installer (Ubuntu) because there has been no activity for 60 days.]

[LufoX11 (lufox11)]

hi, this is still happening (ubuntu 14.04.3). my system is crashing very often and the log says always the same:

17 Nov 11 10:53:03 Paula gnome-session[2022]: WARNING: Application 'compiz.desktop' killed by signal 6
18 Nov 11 10:53:03 Paula gnome-session[2022]: WARNING: App 'compiz.desktop' respawning too quickly
19 Nov 11 10:53:03 Paula gnome-session[2022]: CRITICAL: We failed, but the fail whale is dead. Sorry....

but it only happens when I'm running jdownloader on the bg and the exact moment is when this app tries to show me the captcha. maybe something related to java?

$ java -version
java version "1.7.0_85"
OpenJDK Runtime Environment (IcedTea 2.6.1) (7u85-2.6.1-5ubuntu0.14.04.1)
OpenJDK 64-Bit Server VM (build 24.85-b03, mixed mode)

$ lsb_release -a | grep Desc
No LSB modules are available.
Description: Ubuntu 14.04.3 LTS

$ uname -a
Linux Paula 3.19.0-32-generic #37~14.04.1-Ubuntu SMP Thu Oct 22 09:41:40 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux