apt - What does "No apport report written because MaxReports is reached already" mean?

17
2014-04
  • badp

    When installing a Linux kernel image package, I got, amongst other errors:

    No apport report written because MaxReports is reached already

    Where can I delete old reports so that Apport can resume doing its bug reporting magic again?

  • Answers
  • Octavian Damiean

    The crash files are gathered in /var/crash.

    In a session, if apport collects information, there are also apport files in /tmp/apport.appname....

  • Redoubts

    When I received this error message, I found it had to do with the /boot partition being filled with many old kernel images and headers that were not removed after dist-upgrades. A temporary solution from this launchpad bug comment is quoted at the bottom of this post.

    It's worth noting that Ubuntu is working on a fix through Apt, which as of 2013-03-26 is implemented in Precise, but pending on Quantal.

    Warning: removing kernel packages can be dangerous, and might even leave your system unable to boot, so please don't do this if you don't understand what is going on.

    I fixed this on my system by removing some old kernels, that I am not using any more.

    I checked what kernel I am using like this:

    uname -r

    This gave me a version number of a kernel I MUST NOT remove because I am using it.

    Then I checked what kernels were installed like this:

    sudo apt-get remove linux-

    I.e. I typed "sudo apt-get remove linux-" and pressed the TAB key twice to see a list of possible completions. I chose the linux-image-* and linux-image-extra-* packages that contained versions of the kernel that I was not running, and removed them like this:

    sudo apt-get remove linux-image-3.5.0-17-generic linux-image-extra-3.5.0-17-generic linux-image-3.5.0-19-generic linux-image-extra-3.5.0-19-generic

    The exact list of packages in the "remove" line might be different for you - I found it out by doing what I describe at the top.

    Then I made sure the recently-downloaded kernel packages that failed to configure were ok by running:

    sudo apt-get upgrade

    Warning: removing kernel packages can be dangerous, and might even leave your system unable to boot, so please don't do this if you don't understand what is going on.


  • Related Question

    bug reporting - How can i report a bug about apport-gpu-error-intel.py crashing?
  • fain182

    Everytime my gpu crash and i have to reboot, after the boot appears:

    • the window to report the gpu crash bug
    • when I try to report it, apport-gpu-error-intel.py crashes
    • another window appears suggesting me to report the crash of apport-gpu-error-intel.py
    • then i try to report it, but when launchpad is opened I see that is reporting the original gpu bug and there is no more trace about apport-gpu-error-intel.py crash.

    So, how can I report it?

    UPDATE: I know that i can report it manually, but how can I give more information, like a backtrace or something similar?


  • Related Answers
  • Lekensteyn

    Actually, apport-gpu-error-intel.py belongs to the xserver-xorg-video-intel package:

    Run dpkg -S apport-gpu-error-intel.py to check which package contains this file:

    xserver-xorg-video-intel: /usr/share/apport/apport-gpu-error-intel.p
    

    Find out the source package for the binary package xserver-xorg-video-intel using apt-cache showsrc xserver-xorg-video-intel | grep '^Package:'

    Package: xserver-xorg-video-intel
    Package: xserver-xorg-video-intel
    

    In this case, the source package has the same name as the binary package (xserver-xorg-video-intel), but that may not always be the case (e.g. binary package apt-utils has source apt)

    Bugs for that package can be reported on https://launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bugs

  • Eliah Kagan

    It seems like my problem began when I installed a Windows program through Wine. I deleted all of Wine's components and all of the remaining install data from the game and everything began to work fine. Maybe that just applies to me but I think everything is working okay now... fingers crossed. This issue plagued me all day long. I hope you get it resolved.

  • desgua

    You can go "manually" to launchpad at https://bugs.launchpad.net/ubuntu/+source/apport/+filebug and file this bug.

    It seems like it has happened before, see this.