Latest Kernel Update didn't trigger reboot message

Was noticing I wasn’t getting a reboot notification after a kernel update. After looking around, I noticed that I don’t seem to have the /etc/pacman.d/hooks directory. Can’t see anything in pacman.conf that would point me anywhere else for it.

Not sure what’s going on. Any thoughts?

NOTE: dracut did run after the kernel update, I just didn’t get the expected notification that I should reboot. While looking into it, I noticed I didn’t have the hooks directory.

Do you have eos-bash-shared installed?

I do.

Also, pulling from the logs the day my kernel updated, it certainly appears the hooks are being run…

[2023-09-10T14:18:26-0400] [ALPM] running ‘95-systemd-boot.hook’…
[2023-09-10T14:18:26-0400] [ALPM] running ‘arch-audit-gtk.hook’…
[2023-09-10T14:18:26-0400] [ALPM] running ‘dbus-reload.hook’…
[2023-09-10T14:18:26-0400] [ALPM] running ‘eos-reboot-required.hook’…
[2023-09-10T14:18:26-0400] [ALPM] running ‘rebuild-detector.hook’…
[2023-09-10T14:18:27-0400] [ALPM] running ‘systemd-boot.hook’…
[2023-09-10T14:18:27-0400] [ALPM-SCRIPTLET] Skipping “/efi/EFI/systemd/systemd-bootx64.efi”, same boot loader version in place already.
[2023-09-10T14:18:27-0400] [ALPM-SCRIPTLET] Skipping “/efi/EFI/BOOT/BOOTX64.EFI”, same boot loader version in place already.
[2023-09-10T14:18:27-0400] [ALPM] running ‘update-desktop-database.hook’…

…I just didn’t get a notification to reboot, which I was expecting.

Oh, that is because the hooks are in /usr/share/libalpm/hooks

Figured it might be something like that. Looking at pacman.conf, I can’t see anything pointing me there. I’ll check again in case I just missed it.

Ok…there’s nothing I can see in pacman.conf that does anything other than identify the default hooks location. For my own edification, where is the pointer to /usr/share/libalpm/hooks ?

It doesn’t need to be in /etc/pacman.conf, that is the default location for hooks.

Ok, that clarifies a bit. That line (in pacman.d) identifying the default location is commented out (because it’s the default). However, this is what it says…


The following paths are commented out with their default values listed.

If you wish to use different paths, uncomment and update the paths.

#RootDir = /
#DBPath = /var/lib/pacman/
#CacheDir = /var/cache/pacman/pkg/
#LogFile = /var/log/pacman.log
#GPGDir = /etc/pacman.d/gnupg/
#HookDir = /etc/pacman.d/hooks/

I suppose I could manually update that to the correct default location for reference.

…of course, there’s still the question of why I didn’t get an reboot notification when my running kernel updated but…one thing at a time :wink:

Your file is correct. That path isn’t listed because it is included no matter what you specify in the conf file.

You can see in your log output that the hook ran. Is there any chance you missed the notification?

Maybe, but it’s hard to miss as it’s a pop-up that occurs at the top of my screen, and I was expecting it and, thus, looking for it. Maybe I did miss it, maybe a Gnome Glitch. I’ll keep an eye on it.

I noticed this yesterday when I updated that I didn’t get any notice to reboot after updating the kernel. Unfortunately I can’t share the logs as I ended up doing a reinstall later in the day to switch my file system over to btrfs.

Which kernel are you both using?


Since we seemed to have zeroed in on a possible glitch with the reboot notification, I’ve re-titled the thread accordingly.

Interesting…I noticed the same thing yesterday when I updated the 6.5.2-zen1-1-zen. I just shrugged & rebooted anyway…didn’t think more about it until I read this…Same as everyone else…eos-bash-shared is installed & I looked at the pacman log & the hook was run…

[2023-09-10T08:21:34-0700] [ALPM-SCRIPTLET] ==> Image generation successful
[2023-09-10T08:21:34-0700] [ALPM] running 'dbus-reload.hook'...
[2023-09-10T08:21:34-0700] [ALPM] running 'eos-reboot-required.hook'...
[2023-09-10T08:21:34-0700] [ALPM] running 'rebuild-detector.hook'...
[2023-09-10T08:21:35-0700] [ALPM] running 'update-desktop-database.hook'...
[2023-09-10T14:22:33-0700] [PACMAN] Running 'pacman -S --config /etc/pacman.conf -- extra/adriconf'

I also noticed it on grub? :man_shrugging:

Yes—that was with grub.

Not sure why but i did notice as i didn’t see it triggered either on grub is what i meant.

Ah…so another non-notice notice :wink:

I noticed the same, updating the arch kernel with systemd. I am on plasma Wayland desktop.