Reboot notice

[joekamprad]

https://archlinux.org/packages/extra/x86_64/libnotify/
Last Updated: 2025-02-22 01:07 UTC

[ricklinux]

I suppose you could test by downgrading this package and install a kernel or something?

[joekamprad]

yes only a startpoint to investigate there is no log aside from what i was catching on journal.
But yes if its a change on libnotify package downgrading should remove the issue.

[joekamprad]

there you have it…

[drunkenvicar]

I just installed this:

: Searching databases for updates...
 -> Orphan (unmaintained) AUR Packages: vanilla-backgrounds
:: 7 packages to upgrade/install.
7  core/diffutils    3.10-1   -> 3.11-1
6  core/kmod         33-3     -> 34-1
5  core/libnghttp3   1.7.0-1  -> 1.8.0-1
4  core/pcre2        10.44-1  -> 10.45-1
3  core/which        2.21-6   -> 2.22-1
2  core/zstd         1.5.6-1  -> 1.5.7-2
1  aur/freetube-bin  0.23.1-1 -> 0.23.2-1

and output ended with

(1/4) Arming ConditionNeedsUpdate...
(2/4) Updating icon theme caches...
(3/4) Checking which packages need to be rebuilt
(4/4) Updating the desktop file MIME type cache...

no reboot info or bubble. but those core elements don’t need a reboot I assume.

[manuel]

Thanks guys for investigating this issue!
Downgrading libnotify helps with this.
Nice joint effort.

[manuel]

Looks like this wasn’t the only problem.
Now emacs needs package libgccjit.
More issues may be coming…

[manuel]

emacs was updated today.

[manuel]

@manuel

Downgrading libnotify helps with this.

Happy to inform you all that eos-bash-shared version 25.2.11-1 solves the issue with libnotify 0.8.4-1.
That means you don’t have to downgrade libnotify anymore.

If interested, see this: https://gitlab.gnome.org/GNOME/libnotify/-/issues/54

[anon35057613]

You are the best!

[ricklinux]

@manuel
The notification to reboot came back. I just updated and it popped up.

[2025-02-25T15:52:09-0500] [ALPM] transaction started
[2025-02-25T15:52:09-0500] [ALPM] upgraded eos-bash-shared (25.2.10-1 -> 25.2.11-1)
[2025-02-25T15:52:09-0500] [ALPM] upgraded libavif (1.1.1-2 -> 1.2.0-1)
[2025-02-25T15:52:09-0500] [ALPM] upgraded xorg-server-common (21.1.15-1 -> 21.1.16-1)
[2025-02-25T15:52:09-0500] [ALPM] upgraded xorg-server (21.1.15-1 -> 21.1.16-1)
[2025-02-25T15:52:09-0500] [ALPM] upgraded xorg-xwayland (24.1.5-1 -> 24.1.6-1)
[2025-02-25T15:52:09-0500] [ALPM] transaction completed

[manuel]

And @sammiev
Thanks for confirming!

[ricklinux]

Is it a change in the eos-bash-shared? Or another package?

[manuel]

Yes, eos-bash-shared because it shares code to some other EndeavourOS apps.
The notification call is there.

notify-send (of package libnotify from upstream) no more accepted value zero for the --expire-time parameter which it should have simply ignored for this type of notification, but instead stopped notifying.

[drunkenvicar]

got the balloon…don’t remember say 'inform user to reboot; in the code at the end of terminal output. Is this still an issue or did I miss it?

[eznix]

Seeing as how Arch Linux gives this advice:

" Upgrades are typically not applied to existing processes. You must restart processes to fully apply the upgrade. "

https://wiki.archlinux.org/title/System_maintenance#Restart_or_reboot_after_upgrades

Is a reboot notifier really needed? I say this not to take anything away from the work manuel puts in, especially tracking down the reason:

notify-send (of package libnotify from upstream) no more accepted value zero for the --expire-time parameter which it should have simply ignored for this type of notification, but instead stopped notifying.