EOS-reboot-required stopped working

General system EndeavourOS repo
1

There are some older messages about this problem but they seem to have been resolved. I stopped getting the reboot notification maybe a week ago, don’t know for sure when. Besides the service, which is enabled, and the hooks, which seem to be in place, what else can I look at to troubleshoot? My understanding is that the timer doesn’t need to be enabled.

2

I installed EOS on another computer today using the Titan ISO, and the package eos-reboot-recommended was missing for no apparent reason. If it hasn’t been replaced by something else, you should install it:

sudo pacman -S eos-reboot-recommended
3

I think some changes where made to it a few days ago (I must be going blind because I was just looking at the thread, I’ll see if I can find it again)

4
5

It’s installed. But thanks!

6

This one is about the notification hanging around. My problem is that it doesn’t show up. But thanks!

7

Have you checked the file that it mentions to make sure that it is set to show up?

8

eos-reboot-recommended.conf? Just defaults there.

Just noticed that the hook target (eos-reboot-required2) has this line:

[ “$EOS_REBOOT_RECOMMENDING” = “no” ] && return 0

but eos-script-lib-yad.conf has

EOS_REBOOT_RECOMMENDING=yes

I don’t know if that’s a contradiction, or which one rules.

var/log/reboot-recommendation-trigger.log indicates a recommendation was triggered this afternoon by systemd*

So the recommendation is being triggered–there’s just no notification.

9

IIRC that package got removed the last time I ran sudo pacman -Rns $(pacman -Qdtq) (using this command as alias for orphan).

10

So what is the solution? My .conf files have the same options you listed, yet I don’t get reboot notifications either. I remember I used to get notifications for reboot, but something changed a few weeks/months ago and now that notification is no longer active.

11

@MrSmartepants, see here (and my response after @manuel’s)…

12

The package showed up on my orphan list so I used pacman to mark as explicitly installed, problem solved :grin:

sudo pacman -D --asexplicit eos-reboot-recommended

13

So the takeaway seems to be that the new conf file with its defaults doesn’t produce the notification. Adding a user and a expire time makes it work. At least that’s how it is for me.

I was happy the way it worked pre-26.1, and just assumed that the defaults would continue to work.

14

Well what I did was removing the orphan package assuming it was a old version, than I noticed the package was not installed anymore just installing the package again made it work with the default settings. To be honest I also was happy with the package as it was too. But a certain someone wasn’t and that triggered this whole thing,

15

Thanks for the reports!
I’ll look into it during the following days.

16

Guys, made some minor changes to eos-reboot-recommended, new version is 26.2-1.
Please test it and report.

Note that you probably want to check if the changes in file /etc/eos-reboot-recommended.conf.pacnew need merging to your /etc/eos-reboot-recommended.conf.
For example:

sudo meld /etc/eos-reboot-recommended.conf.pacnew /etc/eos-reboot-recommended.conf
17

Default conf doesn’t notify, still requires user and/or expire time.

18

I set it on 30 (seconds) and :ok_hand:t2:

19

Here it works with all old and new settings.

So some questions:

  1. Is your system fully updated?
  2. Can you show the full contents of your /etc/eos-reboot-recommended.conf that doesn’t notify?
  3. Did you try command: sudo pacman -S mesa
20

Yes, fully updated. Yes, testing with mesa.

#!/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=""