Notification for reboot

After a kernel update I get following output

(5/6) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 5.9.2-arch1-1
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: xhci_pci
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [encrypt]
  -> Running build hook: [lvm2]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: 5.9.2-arch1-1
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: wd719x
==> WARNING: Possibly missing firmware for module: aic94xx
==> WARNING: Possibly missing firmware for module: xhci_pci
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [encrypt]
  -> Running build hook: [lvm2]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-fallback.img
==> Image generation successful
(6/6) Inform user to reboot after certain system package upgrades.

Is there a way to generate a notification on the desktop for the reboot?

Christoph

That text is an indication that you have a pacman hook (/etc/pacman.d/hooks/eos-reboot-required.hook) from eos-update-notifier in use.
If eos-update-notifier is correctly installed, you should have a program
/usr/bin/eos-reboot-required available, and that should give you a system notification after kernel updates.

If all the above is in order, the system notification may not be working. Which DE are you using?

I’m on GNOME.

Just checked this, and indeed by running this I get a message. Is there a way to check why I did not get this message after the upgrade?

And you are not using TTY when updating? Just making sure…

I’m on the desktop using guake and sudo pacman -Syu

Would it be possible to a line like this

Target = *

to /etc/pacman.d/hooks/eos-reboot-required.hook in order to get a message on a random update?

Yes, for testing that is OK.
Alternatively, some single package like

Target = xed

would not cause many notifications when it works. :wink:
The you could simply reinstall xed and see what happens:

sudo pacman -S xed

Hmmm I tried with

Target = code

and sudo pacman -S code but I only get the message

Inform user to reboot after certain system package upgrades.

Edit: I tried again as su and it worked then!

Edit 2: But I get three messages.

I probably need to install Gnome and see if it works here.

Anyway, this is a source of more information: https://wiki.archlinux.org/index.php/Desktop_notifications

2 Likes

Interesting results!

Just to check something: what does command

users

show?

csteinforth csteinforth csteinforth

Seems I am logged in more than once?!

Looks that way…

Hmm but why? I just rebooted, and logged in via gdm.

Edit: Found the reason. When I disable the autostart in guake there is only one of me…

1 Like

Just finished installing EndeavourOS with Gnome.
Command users gives only one manuel.

Edit: OK, great that the reason was found.

Looks like it is only related to su vs. sudo!
I’ll have to find a solution, but please don’t hold your breath… :wink:

So, as you said, it works with

 su -c ...

but not with

 sudo ...
1 Like

There seems to be a long standing bug in guake which starts a new session for every new tab.

1 Like

So far I haven’t found a solution to the su/sudo issue.

As a workaround, you might want to modify the config file /etc/eos-update-notifier.conf:

  ShowHowAboutUpdates=window 

Then it will show you a window (not a notification though) about updates, and if you click Update, it will allow you to update the system.

1 Like