Tag Info

Hot answers tagged

191

What's whoopsie ? It's the "Ubuntu Error Reporting" daemon, and is installed by default in both desktop/server installations. When something crashes, whoopsie does two things: Collects the crash report generated by Apport and Can send them to Ubuntu/Canonical (specifically to https://daisy.ubuntu.com :) Whoopsie won't send your crash reports without ...


135

you need to edit /etc/default/apport Graphical: After pushed the combo key (ALT+F2) or (CTRL+ALT+T), type this: gksudo gedit /etc/default/apport and then push ENTER (password will be asked). or Command line: sudo nano /etc/default/apport A file editor is now open. Change enabled from "0" to a "1" so it looks like this: enabled=1 To turn ...


37

Thanks for your interest in the Ubuntu error tracker project. As of Precise 12.04, this behavior and workflow changed. As I discovered in Bug #993450 “Apport fails to submit bug report”, by default apport no longer opens a bug report (and it is awkward but not impossible to get it to do so). Apport never created bug reports post-release. When a release ...


27

Whoopsie is part of the Ubuntu error tracker. It takes the crash reports that apport creates and presents whenever an application fails and sends them to a Canonical server for further processing. The data collected from these reports help us prioritize and track the most pressing issues: http://errors.ubuntu.com The small whoopsie daemon process is run by ...


26

Click on ubuntu icon, search for "System settings" Select Privacy > Diagnostics tab Unlock Tick "Send error reports to Canonical"


24

The following answer by rubo77 here fixed it for me: Ubuntu has an error reporting system called apport which tries to catch all program crashes in the background and report them to help the developers. It seems that after a dist-upgrade there are stuck some reports that are tried to resubmitted somehow, but disabling apport is not a desirable solution. ...


19

sudo service apport stop ; sudo sed -ibak -e s/^enabled\=1$/enabled\=0/ /etc/default/apport ; sudo mv /etc/default/apportbak ~ The above script should stop apport, then take a backup of its configuration file, disable apport on boot, and lastly moves the backup to your home directory.


17

Yes, you can remove apport but unless you actually agree(d) on apport sending information it will never send any data. Even better: The automatic crash interception component of apport is disabled by default in stable releases for a number of reasons: Apport collects potentially sensitive data, such as core dumps, stack traces, and log files. They can ...


15

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


14

I had the same issue and all I had to do was issue this command in terminal sudo rm /var/crash/* and it realy worked.


12

To expand on fluteflute's answer, which is mostly right, the automated retracer does not set the bug public. It merely adds a stack trace to the bug so that it is more clear where the problem lies. The sensitive information is kept in the bug report, as it can be invaluable to a developer working on a fix. The bug is reviwed by members of the ...


10

Coredump.gz is the (compressed) memory accessible by the program that crashed. It is a binary file. Coredumps are a treasure trove, with all sorts of private data to be mined. Coredumps can be viewed by running 'gdb': gdb --core=mycoredump Of course, you will still need the debug packages associated with this core. You can, then, generate a stacktrace ...


8

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, ...


7

So far the only thing that has actually worked is: Purge the apport program with its configuration sudo apt-get purge apport Remove packages that are no longer needed (ex. auto-installed dependencies of apport) sudo apt-get autoremove Clean APT cache from old packages sudo apt-get clean Install back apport sudo apt-get install apport Hopefully ...


6

Try the following commands: sudo apt-get purge apport sudo apt-get autoremove sudo apt-get clean sudo apt-get install apport The commands will remove the apport program remove packages that are no longer needed (ex. dependencies of apport) remove all packages files saved in the cache (re)install apport More details on apt-get can be found in the ...


6

This is a bug with Ubuntu's error-reporting utility called Apport that a lot of people are experiencing. There is not currently a fix, but you can disable Apport so that it will not keep popping up. To do this run gksudo gedit /etc/apport.conf After you enter in your password, Gedit will open up. You need to change the enabled=1line toenabled=0` ...


6

This issue is caused by a conflict with TeamViewer and has been addressed on the official Ubuntu bugtracker. A solution is provided by "gerlos (gerlosgm)" in comment #39 of said link. Also, a Ticket has been sent to Teamviewer on 2013-5-8 by MRiekerk (mattijs-riekerk) in comment #54 of same link. In the meanwhile, the crash can be averted by removing ...


6

This seems to be a problem with your system language (Turkish). See this bug report for details. Fortunately there has already been a fix released and pushed to the natty-proposed repository. This is the repository where all fixes for a stable Ubuntu release land for testing before they are moved to natty-updates. It's not recommended to enable this (it's ...


5

Sometimes, but not usually. Reporting Crashes in System Processes Most of the time when an application crashes or you report a bug manually, you don't have to put in a password for information to be automatically gathered and sent to Launchpad. However, when a program or service that runs as root crashes, collecting data about that crash requires ...


5

Apport decided that the attachments/logs/etc you submitted automatically in that bug report may contain information that compromises your privacy. In time (usually within a few hours, certainly with a few days) then an automatic process will look through your bug report attachments, "retrace" them (which I believe both helps the developers find useful ...


5

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 ...


5

apt-get -s purge whoopsie The following packages will be REMOVED whoopsie* apt-get purge whoopsie I've had no problems as I am in the process of building my own Ubuntu Desktop but so far that thing keeps crashing my system, but now I have got rid of it :)


5

It is probably safe to remove Apport, but doing so is completely unnecessary for protecting your privacy. Apport's core dump interception is disabled by default on stable versions of Ubuntu. To completely disable Apport, edit /etc/default/apport. Change enabled=1 to enabled=0. (1 means it's enabled. 0 means it's disabled.) Then reboot (or manually stop the ...


5

Take a look and delete all files in /var/crash/: rm /var/crash/* I suddenly had the same problem apport-gtk taking 100% on every restart. Seemed there was a huge (2GB+) bogus crash file in /var/crash/ that couldn't be parsed. After several minutes of waiting I always ended up with this rather mysterious dialog: This problem report is damaged and cannot ...


4

The /proc/sys/kernel/core_pattern configuration setting is set when the apport crash reporting service starts on system boot. So the first step in the process would be to disable apport. This can be done by editing the /etc/default/apport file, and setting enabled=0. At this point, the kernel default core pattern should remain on boot. If you want to ...


4

All crash bug reports filed by Apport are marked private by default and are only visible to people with relevant privileges (generally, the Bug Control members for bugs filed on packages from the repository). Usually, crash bug reports don't contain any sensitive information (mostly because they don't involve software that deal with private information). ...


4

It sounds like you should choose () Continue. I don't need technical support at that screen, based on what you're saying in the question. You experienced a crash, but aren't getting it consistently, and can't force it to happen. But you want to file the bug report, so that it is known and tracked.


3

For me it works in ubuntu 12.04 (final release) to edit /etc/apport/crashdb.conf and add 'Crash' to the 'problem_types': ['Bug', 'Package', 'Crash'] Some references https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 https://bugs.launchpad.net/ubuntu/+source/apport/+bug/993450/comments/13 https://bugs.launchpad.net/apport/+bug/997283


3

Can I get some statistics somewhere on which applications crash the most? Would be awesome to get some quality metrics available. https://errors.ubuntu.com/ It has the statistics you want, filterable by package and/or time period.


3

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 ...



Only top voted, non community-wiki answers of a minimum length are eligible