I keep getting popups about internal system errors (see screenshot below) on irregular intervals (several times a day), that I don't know what to do about. If I continue through the dialog and try to report the error back to the Ubuntu project, I get a message stating that development on this version of Ubuntu has been completed, and that I should ask for help here if I don't know what to do about it.

I don't.

enter image description here

If I show the details of the error message, the "executable path" parameter shows /usr/share/apport/apport-gpu-error-intel.py.

Is this a bug I should report to Launchpad, or just a configuration error somewhere? If it's a bug, how do I collect the data I (and the devs) need?

Update in response to comment: I am running an ASUS N53SN, sporting an Intel Core i7 2630QM CPU and an NVidia GeForce 550M GPU.

  • 5
    you are not alone my friend , me too . thanks for posting here . – rɑːdʒɑ May 24 '12 at 14:12
  • I've also noticed a lot of internal system errors since upgrading to 12.04, and clicking through does not send bugs to launchpad like it used to. Weird that apport/Cannonical think that askubuntu (a Q&A site) becomes the preferred destination for bug reports over launchpad (a bug reporting site) once development on an LTS version has "been completed". – adempewolff May 24 '12 at 14:25
  • @Tomas, I too experience this type of error reporting popups, but with various other applications. From the error it seems that your Intel GPU is triggering this window. What is your processor model and GPU model? – saji89 May 24 '12 at 14:32
  • @saji89: I'm running an ASUS N53SN, please see my update. – Tomas Aschan May 27 '12 at 21:38
  • 1
    @saji89 The mother board also has a built-in Intel graphics card, so I'm running bumblebee to help Ubuntu deal with that. – Tomas Aschan May 27 '12 at 21:40

Potential Reason for These Unreportable Errors

I think I've figured this out. I think that this particular bug reporting avenue is a hangover from the alpha and beta development stages--when the developers wanted as many bug reports as possible, regardless of whether the user was willing to file a full launchpad bug report or not. Once 12.04 was released, the developers no longer wanted anonymous bug reports so they disable this ability. They only want bug reports that the user themselves manually takes the time to file.

This is understandable but I would consider it a bug that apport/ubuntu-bug is presenting the user with non-actionable information. When development stops and they no longer want a high volume of bug-reports turning off automatic bug reporting is one thing, but leaving the user without a path (at the very least a link) to report to launchpad, and without a way to save the information contained within the bug report should be rethought.

My Solution to Non-Actionable Error Reports

I know what I am going to do next time I get one of these unreportable/unsavable errors. I'm going to take a screenshot of the window, run apport-bug apport and file a bug saying that apport should not present the user with non-actionable information. At the very least the user should be able to save the report for their own use or for manually reporting a bug.

How to Proceed Regarding your GPU Bug

As for your problem, apport was running a script to debug GPU problems.

If you aren't actually noticing problems with your GPU other than these error messages I'd say you can safely ignore them.

If you are seeing any weird graphics related behavior, keep an eye on your logs--specifically xorg.0.log and syslog, but maybe the kernel logs as well. If you are noticing errors copy them down, and try to make a best guess (or ask) whether it is a driver problem, kernel problem or X11 problem. Then use apport to file the bug against what you determine to be the best package (for example for my nvidia driver I would enter apport-bug nvidia-current-updates), be as detailed as you can be in the resulting bug report and put the symptoms you experience and any errors you noticed into the description when you file the bug. More information about filing bugs is here and here. Good luck.

  • 2
    I've now submitted a bug to Launchpad. Feel free to confirm it, if that can maybe up its attention among the developers a little =) – Tomas Aschan May 28 '12 at 15:29
  • @TomasLycken only one suggestion: edit the bug so it follows standard bug report styling, ie answering the two big questions: "What is expected to/should happen?" (the user should be able to report or save the bug, or not see the option to do so), and "What actually happened?" – adempewolff May 28 '12 at 15:47
  • @TomasLycken and try to include another screenshot of the screen that suggests they go to Ask Ubuntu – adempewolff May 28 '12 at 15:48
  • Does it look better now? =) – Tomas Aschan May 28 '12 at 17:01
  • 1
    It does, although it is a little different from the dialogues I was thinking of, that basically say "Development is now finished for 12.04" and don't tell the user what they can do with their bugs. – adempewolff May 28 '12 at 17:22

Go ahead and run xdiagnose. Uncheck "Enable automatic crash bug reporting". You will never going to be bothered again by those messages.

  • 1
    Ironic consequence: When I did this, I immediately got a popup stating that "The application xdiagnose has closed unexpectedly"... – Tomas Aschan Mar 21 '13 at 18:39
  • When I try to do that,I get a text that ends with: 'Error: Failure creating backup file for /etc/default/grub. Changes not applied. [Errno 13] Permission denied: '/etc/default/grub.bak'' – user138784 Apr 11 '13 at 9:20
  • (How do I get that in monospaced front in a grey box? I fail to do that) – user138784 Apr 11 '13 at 9:22

This may help. Open the GParted program and check if the you see an error message on one of the Ubuntu partitions.

I recently wiped my mac partitions and installed Ubuntu on my hard drive. I see that Ubuntu has created a small 977 KB partition which has the flag bios_grub.

I wonder if that is what is causing the system errors. Macs do not have a BIOS.

  • Welcome to AskUbuntu :) You haven't given a solution to the question asked in your post, feel free to add one if possible at some point otherwise add this as a comment to the original question once you have the required reputation. – Oyibo Sep 29 '12 at 14:59

If you're having NVidia drivers and experiencing frequent crashes and frozen desktops, try to switch to propitiatory NVidia driver instead of open source one.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.