Compiz related non-specific (Compiz application closed unexpectedly due to error)

[honeybuntu]

crash takes place immediately (within 1st 20 minutes of updating software after fresh install of Ubuntu 12.04.3 LTS). The crash occurs without any noticeable kernel/system incapacitation. There are no "screen freezes" or signs of operational degradation involving the display. Each time the indication of the Compiz "crash" occurs I have elected to leave the Compiz application closed pending further Xorg system diagnostics. Pleae advise re: resolve related to the Compiz program app (update) "bug".

I have applied the test packages as prescribed below as of 30 minutes prior to posting this brief report (although I am unsure if this resolve is specific to the bug exhibitted on my particular computer:
obtained at Ubuntu URL: https://wiki.ubuntu.com/X/Troubleshooting/HighMemory

------------------------------------------------------------------
Installing the test packages

Please do the following to upgrade to the proposed X server with the fix:

      sudo add-apt-repository ppa:ubuntu-x-swat/x-updates
      sudo apt-get update
      sudo apt-get dist-upgrade

After that, reboot and log in.
-------------------------------------------------------------------

Unable to determine relative possibility of security vulnerabilities related to the Compiz (compositing manager for Open GL - desktop appearance/settings/functionality inline with manipulating Intel graphics chip instructions).

Installing the test packages

Please do the following to upgrade to the proposed X server with the fix:

      sudo add-apt-repository ppa:ubuntu-x-swat/x-updates
      sudo apt-get update
      sudo apt-get dist-upgrade

After that, reboot and log in.

The error is not uncommon and have discussed with other end-users in Ubuntu "freenode" discussions. Hopefully, a resolve (other than the PPA debug session and debug for the update) can be compiled for this and future distributions of Ubuntu 12.04 LTS, &c. I intend to re-install Ubuntu 12.04.3 LTS directly (as of this writing) and avoid updates to Compiz (or in the alternative uninstall the offending application = Compiz updates to Ubuntu 12.04.3 LTS). If I am in error in following this course in remedying the spontaneous crashing of the internal application - could you kindly advise as to alternative measures (if at all possible) for the benefit of all Ubuntu 12.04 LTS users, if you please.

Thank you for your time and considerations regarding this issue.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: xorg 1:7.6+12ubuntu2
ProcVersionSignature: Ubuntu 3.8.0-35.50~precise1-generic 3.8.13.13
Uname: Linux 3.8.0-35-generic x86_64
.tmp.unity.support.test.0:

ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
CompositorRunning: compiz
Date: Thu Jan 23 09:59:14 2014
DistUpgraded: Fresh install
DistroCodename: precise
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:10fd]
InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1)
MachineType: ASUSTeK COMPUTER INC. S500CA
MarkForUpload: True
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-35-generic.efi.signed root=UUID=079dc985-9107-4080-9b1b-2d1ca8a4deb5 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/05/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: S500CA.204
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: S500CA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrS500CA.204:bd02/05/2013:svnASUSTeKCOMPUTERINC.:pnS500CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnS500CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: S500CA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.7.12-0ubuntu3
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.46-1ubuntu0.0.0.1
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

[penalvch (penalvch)]

honeybuntu, thank you for reporting this and helping make Ubuntu better. However, your crash report is missing. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal:
cd /var/crash && sudo rm * ; sudo apt-get update && sudo apt-get -y upgrade && sudo service apport start force_start=1

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

Now reproduce the crash, then 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'. If you run the command against the crash report and a window pops up asking you to report this, but then never opens a new report, you would be affected by https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 . In order to WORKAROUND this, one would need to open the following file via a command line:
sudo nano /etc/apport/crashdb.conf

and comment out the line:
'problem_types': ['Bug', 'Package'],

by changing it to:
# 'problem_types': ['Bug', 'Package'],

Save, close, and try to file the crash report again via:
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.

Please feel free to subscribe me to this new report.

Also, please do not attach your crash report manually to this report and reopen it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs