I was getting these errors all the time. Not sure if there's a real underlying bug here (as noted by dnelub -- this may be something outside of xdiagnose that is very real -- and xdiagnose just seems to create the annoying xdiagnose alerts -- which this fix appears to be for).
I just wanted to disable the irritating popups that kept showing up. Here's a fix that's worked for me on my Lenovo Ideapad U300s (fingers crossed -- 1 day without xdiagnose alerts) and is incredibly simple: 1 - In terminal, type: sudo xdiagnose 2 - uncheck EVERYTHING in the xdiagnose window 3 - restart the computer I also did the following -- and I'm not sure whether it did something in addition to the items above - so I'm disclosing it just to be safe: 1 - In Software Center search for "xdiagnose" 2- Select it when you find it, and click on "More Info" 3 - In Add-ons, uncheck the box next to "Tools for debugging the intel graphics driver (intel-gpu-tools)" 4 - restart the computer. The reason I'm skeptical that the Software Center change did anything is that if I re-open the Software Center after boot, the "Tools for debugging the intel graphics driver (intel-gpu-tools)" is checked once again -- so it looks like it can't actually be disabled. Let me know if it works for you. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdiagnose in Ubuntu. https://bugs.launchpad.net/bugs/1073626 Title: Constant "false gpu hang" system alerts Status in “xdiagnose” package in Ubuntu: Confirmed Status in “xdiagnose” source package in Quantal: Fix Committed Status in “xdiagnose” source package in Raring: Confirmed Bug description: [Impact] Apport hook is triggered for GPU lockups in the stable release, in cases where the system did not freeze. We no longer need bug reports about GPU lockups for quantal (or other stable releases), so can simply disable the hook. [Test Case] On Intel gfx hardware running quantal, wait until a GPU hang occurs. The apport hook should not generate a .crash file in /var/crashes. The apport hook should not trigger a display of the bug reporting dialogs in the current or subsequent sessions. [Regression Risk] The patch comments out a udev rule, so is very low risk of regression. The side effect of this change is that GPU lockup bugs will no longer be collected for quantal. This is acceptable; we are mostly just interested in lockups in raring and newer at this point. [Original Report] My system: I'm running Ubuntu 12.10 64-bit My system is a Macbook4.1 Intel Core 2 Duo 2.4GHz / 2GB RAM / GMA X3100 with 144MB shared memory / Intel HDA audio. The image I used for installing the system is Ubuntu 12.10 64-bit (AMD64) + MAC. The issue: Every time I log onto my session, a system program error dialog is displayed. (I'll try to translate as possible since my system is running in Spanish) · "There's is a system program problem detected. Do you want to inform this now?" I pick "Yes", and then I've got to enter my password. Then, another dialog appears displaying the following message: · "We're sorry. Ubuntu 12.10 has experienced an internal error. If you continue to have problems, try to restart the system. [marked checkbox] Send a bug report to help solve this issue." [*] Picking "details" it shows a long list of components wich start with the lines "Executable path | /usr/share/apport/apport-gpu-error- intel.py" Before I even pick the "continue" button, another system dialog pops up onscreen displaying the following message: · "Apport has detected a possible GPU hang. Did your system recently lock up and/or require a hard reboot?" Since neither of the two were needed, I pick "No". Then, the system pop up another dialog: · "Your display manager log files may help developers diagnose the bug, but may contain sensitive information such as your hostname. Do you want to include these logs in your bug report?" I pick "Yes". In the next Apport dialogue "Would you be willing to do additional debugging work?", I pick "Yes". Several minutes later, nothing happens yet. No other system dialogued showed up. I never did any debugging work as I choose to do. Meanwhile, the dialogue that displays the details of the internal error (in the line marked with [*] on this report), now has completed the list. It took more than two minutes to do. I mark the checkbox for "Send a bug report to help solve this issue", and then I pick "Continue". Nothing else ever happened. I don't even know if the bug was reported. This issue will happen again some time later, and so on, being really annoying. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Wed Oct 31 10:56:49 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: bcmwl, 5.100.82.112+bdcom, 3.5.0-17-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device [106b:00a1] Subsystem: Apple Inc. Device [106b:00a1] InstallationDate: Installed on 2012-10-24 (6 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64+mac (20121017.3) MachineType: Apple Inc. MacBook4,1 MarkForUpload: True PlymouthDebug: Error: [Errno 13] Permiso denegado: '/var/log/plymouth-debug.log' ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=f1d1b864-6064-4edb-b90e-e7da9ffb7419 ro plymouth:debug splash quiet drm.debug=0xe SourcePackage: xserver-xorg-video-intel UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/09/08 dmi.bios.vendor: Apple Inc. dmi.bios.version: MB41.88Z.00C1.B00.0802091535 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F22788A9 dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 2 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22788A9 dmi.modalias: dmi:bvnAppleInc.:bvrMB41.88Z.00C1.B00.0802091535:bd02/09/08:svnAppleInc.:pnMacBook4,1:pvr1.0:rvnAppleInc.:rnMac-F22788A9:rvrPVT:cvnAppleInc.:ct2:cvrMac-F22788A9: dmi.product.name: MacBook4,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.8.4-0ubuntu3 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdiagnose/+bug/1073626/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
