Users should be enabled to ignore crashes for certain apps

Bug #79408 reported by Vincenzo Ciancia
2
Affects Status Importance Assigned to Milestone
apport (Ubuntu)
Fix Released
Low
Martin Pitt

Bug Description

Binary package hint: apport

There are applications - typically skype and gaim - that crash often and restart without interfering with my work, however that crash popup and that bomb icon in the systray are annoying: I know it crashes, I already checked, other people already reported the crash, where is "do not ask this anymore" button? We should be able to at least "snooze" the alarm for say a month - is it possible to do this manually right now?

When I click on the "bomb" icon, a popup is offered asking if I want to send debug information or not. There should be a checkbox or a button saying "don't ask me this question for this application anymore", or maybe "for this bug anymore" when a way to detect duplicates will finally be decided. BTW I offer to help in the latter since I work in programming language semantics, contact me if you wish. There should also be a checkbox saying "don't ask me this question for a while".

The situation right now is not nice for the image of ubuntu in the world: I log in with somebody new to ubuntu watching my screen, and suddenly a couple of popups come out saying that the world is crashing down - this is not nice - maybe I experience one such message for every login since crash information is left in /var/crash or this is already handled and the question is not repeated twice for the same crash information? If so I should open a separate bug.

Revision history for this message
Martin Pitt (pitti) wrote :

Agreed, this could become really annoying. Right now it doesn't report more than two crashes in a row for any given app, but the quiet time only lasts for a day. This short-term flood protection needs to be accompanied by a long-term 'get out of my eyes' option.

Changed in apport:
assignee: nobody → pitti
importance: Undecided → Low
status: Unconfirmed → Confirmed
Martin Pitt (pitti)
Changed in apport:
status: Confirmed → In Progress
Revision history for this message
Martin Pitt (pitti) wrote :

Fixed in bzr head, will upload soon.

Changed in apport:
status: In Progress → Fix Committed
Revision history for this message
Martin Pitt (pitti) wrote :
Download full text (4.0 KiB)

 apport (0.45) feisty; urgency=low
 .
   New feature: Infrastructure for package install/upgrade failures:
 .
   * Add bin/package_hook: Script for creating a report for a package
     installation/upgrade failure. It receives a package name, a number of log
     files, and an ErrorMessage: from stdin. This will be called from e.g.
     dist-upgrader.
   * setup.py, debian/apport.install: Ship package_hook.
   * apport/ui.py: If ProblemType is 'Package', call a new function
     self.ui_present_package_error() instead of presenting a crash. Add test
     suite checks for the package error report workflow.
   * apport/ui.py, create_crash_bug_title(): Create default bug title for
     package reports. Add various test cases.
   * gtk/apport-gtk{,.glade}: GTK implementation of ui_present_package_error().
 .
   New feature: Maintain a per-binary blacklist to inhibit apport crash reports
   until the binary changes. Closes: LP#79408
 .
   * apport/report.py: Add new Report methods check_ignored() and mark_ignore()
     to check for/set ignore list entries. Add test cases.
   * apport/ui.py: Add another return value of ui_present_crash() to specify
     whether or not to blacklist the current crash's executable. Check workflow
     of both responses in the test suite.
   * gtk/apport-gtk{,.glade}: Add a blacklist checkbox to the crash
     notification dialogs.
   * bin/apport: Do nothing if the current crash is blacklisted.
   * test-apport: Test blacklisting.
 .
   Bug fixes:
 .
   * gtk/apport-gtk: Fix return code for restarting the application ('reopen' ->
     'restart'). Closes: LP#81422
   * test-apport: Adapt to new core_pattern kernel interface mode:
     - Check core_pattern instead of the obsolete crashdump sysctl to determine
       whether or not apport is running.
     - Give apport max. 10 seconds to complete. The current kernel reaps the
       crashed process as soon as writing the core dump to the pipe is
       finished, but apport still needs to write the report file.
     - Do not EXFAIL the test for crashes in nonwriteable cwd any more, since
       it is now supposed to work (we do not write a core dump to the disk any
       more).
   * run-tests, use-local: Adapt to new core_pattern kernel interface.
   * apport: Improve logging of exceptions, include environment variables.
   * apport/report.py test suite: Use gdb to generate a test core dump, do not
     rely on kill(SIGSEGV) and the kernel to do it (since we now use a pipe in
     core_pattern).
   * backends/packaging-dpkg.py: Fix return value of get_modified_files() if
     dpkg .list file is missing.
   * apport/report.py, add_package_info(): Do not produce stray empty lines for
     uninstalled alternative dependencies.
   * apport/report.py: Fix test_add_gdb_info_script() to not leave behind a
     stray gzip process which randomly blocks stdin. Closes: LP#78421
   * backends/packaging-dpkg.py: Do not read the dpkg status in the
     constructor, but lazily initialize it when actually calling a query
     function. This avoids imposing the dpkg-query overhead for programs that
     import the apport package wit...

Read more...

Changed in apport:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.