Public bug reported:

note: AI assisted me in reporting

ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: update-notifier 3.207.2
ProcVersionSignature: (from ubuntu-bug output)
Uname: Linux (from ubuntu-bug output)
ApportVersion: (from ubuntu-bug output)
Architecture: amd64
Date: Sat Nov 21 2026
UpgradeStatus: No upgrade log present (probably fresh install)

--- Description ---

The update-notifier daemon (PID from gnome-session autostart) exits
cleanly (exit code 0, no signal, no crash) after approximately 33
minutes. It is supposed to run as a persistent daemon until logout,
periodically checking for pending updates and sending desktop
notifications.

Because the process exits early, no notification is ever delivered
to the user about pending regular updates (the 7-day interval is
never reached while the process is alive).

--- Expected behaviour ---

update-notifier should run continuously from login until logout,
checking for updates every ~5 minutes via apt-check, and send a
desktop notification when the regular-auto-launch-interval (default:
7 days) has elapsed since the last notification.

--- Actual behaviour ---

The process starts successfully at login (confirmed via journal),
prints the known libayatana-appindicator deprecation warning, then
exits cleanly after ~32 minutes 45 seconds with no error, no signal,
and no further log output.

--- Steps to reproduce ---

1. Fresh install of Ubuntu 26.04 (GNOME, Wayland)
2. Log in (manual or auto-login)
3. Wait ~35 minutes without logging out
4. Run: ps aux | grep update-notifier | grep -v grep
5. Observe: no process running

--- Journal evidence ---

$ journalctl --user -b | grep "update.*notifier.*2472"

Nov 21 10:38:15 HP260G9 systemd[1804]: Started 
app-gnome-update\x2dnotifier-2472.scope - Application launched by 
gnome-session-service.
Nov 21 10:38:16 HP260G9 update-notifier[2472]: libayatana-appindicator is 
deprecated. Please use libayatana-appindicator-glib in newly written code.
Nov 21 10:38:21 HP260G9 update-notifier[2472]: libayatana-appindicator is 
deprecated. Please use libayatana-appindicator-glib in newly written code.
Nov 21 10:38:21 HP260G9 update-notifier[2472]: libayatana-appindicator is 
deprecated. Please use libayatana-appindicator-glib in newly written code.
Nov 21 11:11:00 HP260G9 systemd[1804]: app-gnome-update\x2dnotifier-2472.scope: 
Consumed 10.499s CPU time over 32min 45.480s wall clock time, 384.8M memory 
peak.

No "Main process exited" line (expected for scopes), no signal, no
OOM kill, no segfault. The scope is simply cleaned up after the
process self-exits.

$ journalctl --since "11:10" --until "11:12" | grep -i 
"gnome-session\|scope.*stop\|scope.*deactivat"
(empty - no external actor stopped the scope)

$ ps aux | grep update-notifier | grep -v grep
(no output after the ~33 minute mark)

--- Workaround ---

A systemd user service with Restart=always keeps the process alive:

[Service]
ExecStart=/usr/bin/update-notifier
Restart=always
RestartSec=10

--- Related ---

Bug #2159587 (fixed in 3.207.2) addressed the notification not
firing when the tray icon is disabled. This is a separate issue:
the process itself does not survive long enough to deliver any
notification.

--- Tags ---
regression, update-notifier, gnome, wayland, resolute

** Affects: update-notifier (Ubuntu)
     Importance: Undecided
         Status: New

** Summary changed:

- update-notifier 3.207.2 exits after ~33 minutes, no notification delivered   
update-notifier 3.207.2 exits after ~33 minutes, no notification delivered
+ update-notifier 3.207.2 exits after ~33 minutes, no notification delivered

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2175463

Title:
  update-notifier 3.207.2 exits after ~33 minutes, no notification
  delivered

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/2175463/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to