update-notifier does not always trigger apport for existing crashes

Bug #1779639 reported by Jean-Baptiste Lallement on 2018-07-02
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
update-notifier (Ubuntu)
Medium
Unassigned

Bug Description

update-notifier does not always check existing crashes until another crash file is created

Test Case.
1. Stop update-notifier
2. Create a crash file: sh -c 'kill -SEGV $$'
3. Start update-notifier (you may need to stop and start more than once to trigger the issue)
4. Wait for the 3min timeout

Expected Result
Apport UI is triggered if reporting is set to manual.

Actual Result
In debug mode the following message is displayed on start then nothing happens even after waiting for the 3 minutes timeout
** (update-notifier:22999): DEBUG: 12:09:05.768: tray_applet_ui_destroy: hook-notifier
** (update-notifier:22999): DEBUG: 12:09:05.768: trayapplet_create()
** (update-notifier:22999): DEBUG: 12:09:07.309: crashreport_check

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: update-notifier 3.192.6
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.10-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul 2 12:09:49 2018
InstallationDate: Installed on 2014-07-15 (1448 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
SourcePackage: update-notifier
UpgradeStatus: Upgraded to cosmic on 2018-03-24 (99 days ago)

Jean-Baptiste Lallement (jibel) wrote :
tags: added: rls-cc-incoming
Changed in update-notifier (Ubuntu):
importance: Undecided → Medium
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers