About 2 months now heavy duty core stuff gets installed but no reboot warning.
I did not disable this.
I’m a big boy and I always reboot after kernel updates etc anyway…
…but I do miss the security blanket though.
How do I re-enable? is this a gsetting or conf dealio?
thanks
Check whether you have the ‘eos-reboot-recommended’ package from the endeavouros repository installed. I accidentally removed mine at some point. Perhaps the same thing has happened to you.
$ yay -Ss eos-reboot-recommended
endeavouros/eos-reboot-recommended 26.4-1 (17.9 KiB 7.7 KiB)
Notify if a reboot is recommended after system upgrade.
You were right it’s not installed. It had to get removed as a dep or revdep because I have never typed-Rns eos-reboot-recommended in my life…either way no sleuthing for me. Glad to have it back, Thank you
I noticed my reboot message wasn’t coming up after the last two kernel updates. . . I rebooted none-the-less out of habit. Nice to have this running again. . . . we’ll see in the next kernel update.
Rich 
See here:
It’s apparently no longer required by any other package, so you probably cleaned orphan packages and did not notice that it was being removed. Reminder: always pay attention to what’s beinng removed if you clean orphans.
this had to be during a monthly pacman -Qtdq cut and paste batch delete, then. This is the most likely scenario.
Re-reading ^ the linked info dated 3-16. That one got by me.
Note to self 
Thank you kindly
You can mark it as explicitly installed to prevent it from being deleted as orphaned:
sudo pacman -D --asexplicit eos-reboot-recommended
done! muchas
The package was reinstalled, so it was already explicitly installed; this would have prevented it from being removed if applied when it showed up in the orphans list, but is redundant once it has been reinstalled, as that reinstall was explicit.
the more I learn the better I am off
I did what was suggested above to get the reboot message to run. It didn’t work. I just finished installing kernel 7.0.3 - 1-2 on 2 computers. . . no ‘reboot’ message popped up. . . . any idea’s?
Rich;)
Just got home from work. Coincidentally there were 19 cores items to update/install.
Check if user should be informed about rebooting after certain system package upgrades.
I knew when I got this ^^^ at the end i would be allright. And lo and behold the message was back upper right of the screen.
My sequence was:
cry about this last night at forum
took advice to reinstall it
made it sexplicit
which was redudant
drink beer
surf
shut down computer and go to sleep
wake up and go to work
get home now, boot up, update Endeavour’s 19 core packages
get reboot screen
I think you need to repeat this sequence ^^ action-for-action with emphasis on the beer
But seriously @rich52 I would reboot once or twice. don’t know why you don’t have it. You re-installed that package, right?
Thought I did . . . the package according to Octopi wasn’t installed. . . re-installed it from there. Now I have a longer wait till the next kernel update. . . .
Rich
yay -S eos-reboot-recommended
if you did this ^^ and rebooted…I got nothing.
unless there’s a sytemd service component to this (which I doubt)?
or you are missing deps/revdeps (which I doubt)?
pacman -Qi eos-reboot-recommended
Name : eos-reboot-recommended
Version : 26.4-1
Description : Notify if a reboot is recommended after system upgrade.
Architecture : any
URL : https://github.com/endeavouros-team/PKGBUILDS/raw/master/eos-reboot-recommended
Licenses : GPL
Groups : None
Provides : None
Depends On : eos-bash-shared libnotify
Optional Deps : None
Required By : None
Optional For : None
Conflicts With : None
Replaces : None
Installed Size : 7.74 KiB
Packager : manuel manuel@endeavouros.com
Build Date : Wed 22 Apr 2026 02:48:38 AM MST
Install Date : Fri 01 May 2026 05:20:02 PM MST
Install Reason : Explicitly installed
Install Script : No
Validated By : Signature
or try to remove and re-install, reboot, sometimes that works too
I’m lost with the sequence of my events this morning. . . I can only say now it is installed. My pacman -Qi eos-reboot-recommended now looks familiar to your’s. . . that’s all I can say for now.
Sorry for problems I may have caused.
Rich
No idea why I’m not getting the reboot pop-up, but I’m not. And eos-reboot-recommended is installed. I just had kernel and Nvidia updates and there was no reboot pop-up.
─❯ pacman -Qi eos-reboot-recommended
Name : eos-reboot-recommended
Version : 26.4-1
Description : Notify if a reboot is recommended after system upgrade.
Architecture : any
URL : https://github.com/endeavouros-team/PKGBUILDS/raw/master/eos-reboot-recommended
Licenses : GPL
Groups : None
Provides : None
Depends On : eos-bash-shared libnotify
Optional Deps : None
Required By : None
Optional For : None
Conflicts With : None
Replaces : None
Installed Size : 7.74 KiB
Packager : manuel <manuel@endeavouros.com>
Build Date : Wed 22 Apr 2026 04:48:38 AM CDT
Install Date : Sat 02 May 2026 12:48:53 AM CDT
Install Reason : Explicitly installed
Install Script : No
Validated By : Signature
─❯
eos-reboot-recommended is installed on everyone’s system in this thread.
Works for some Endeavour users
Does not work for other Endeavour users.
What does this mean? Wish I knew.
Only thing I can think of is
some kind of triggers were ripped out after deprecation? (long shot)
maybe yours is set to flash for .5 second (half a second) and it got by you?
I wish devs would chime in about this non-functioning package…unless this is upstream and we haven’t researched hard enough?
perplexed
Same here. I even went through the last 2 topics (now closed) regarding this issue…
Nothing seems to work. This command: sudo pacman -S mesa should trigger the reboot pop up. And it doesn’t. I also verified that /etc/eos-reboot-recommended.conf was present, and it is…
#!/bin/bash
## REBOOT_MAX_TOTAL_WAIT defines the maximum time in seconds
## to wait before notifying about recommended reboot.
## If you install or update a package that requires more time,
## consider increasing the value accordingly to have more accurate notifications.
## Default: 300
#
REBOOT_MAX_TOTAL_WAIT=300
## REBOOT_WAIT_DIFF defined how many seconds to wait after checking again if all
## pacman-like processes have finished and the database lock filehas been released.
## This time is typically from 3 to 5 seconds.
## Default: 4
#
REBOOT_WAIT_DIFF=4
## REBOOT_NOTIFICATION_USER defines the user name to get notification about reboot recommendations.
## Then other users don't receive the notifications.
## Default: empty
## Example: REBOOT_NOTIFICATION_USER=username
#
REBOOT_NOTIFICATION_USER=""
## REBOOT_EXPIRE_TIME defines the time (in seconds) to show the reboot notification.
## Default: empty
## Example: REBOOT_EXPIRE_TIME=30
#
REBOOT_EXPIRE_TIME=""
So yeah, I have no clue as to why this has turned into an issue.
I thought I’d try with all kernels I have installed in case it was kernel related…
─❯ pacman -Q $(pacman -Qsq linux kernel | grep ^linux | grep -v headers)
linux 7.0.3.arch1-2
linux-cachyos 7.0.3-1
linux-lts 6.18.26-2
linux-zen 7.0.3.zen1-2
─❯
Same issue with all 4 kernels.
rule out kernel?
updating Solus right now. Will try these later and at least look at text