EOS Update-notifier requires acces to plasma remote control

I have reinstalled EOS, but this is new to me.

After displaying eos-update-notifier in the tray, I get this display

After clicking OK I get to the update process

Is there a way to automate this. I mean without having to take the indirect route via remote control?

Could be wrong here but I think it might be related to this

1 Like

eos-notifier work perfectly.
I have found out that it has something to do with xdg-desktop-portal-kde. But I have no idea what it’s all about. However, my knowledge does not go that far. Maybe I’ll find out something

It called in german entfernte Arbeitsflächen, when i click it it goes to xdg-desktop-portal-kde . Dont have a clue

Well I take it you get a popup mesage when a update is upstream. Now I did some research on what Yad does, and as far as I understand it this takes care of that popup messages in one way or another. That’s all I can tell you I’m afraid. Could it be you enabled the notifier on a (virtual) desktop you removed ?

1 Like

Are you using wayland? If so, does it work with x11?

For what it is worth I am using Wayland and it works perfectly.

1 Like

I am on Plasma Wayland. Update Notifier does exactly what it is supposed to do. Send pop-up and tray notification. I don’t understand what xdg-desktop-portal-kde has to do with it and why remote workspaces are requested or notified

Sounds like a plasma issue as the update notifier is working.

The notifier used a simple command notify-send, does that also cause this problem?
Note that package libnotify was updated about 9 days ago, and the changes seemed quite big to me. So the problem might be related to the update of libnotify too.
BTW I’m currently using Xfce, will try the notifier on KDE.

So I did some further testing and I saw that if I click on operation test in the screen from my screenshot, yad will popup. If you click on edit config you will get the yad config file.

libnotifyist installed

notify-test says:

 ❯ LANG=C  notify-send -t 5000 "Test" "This is a test" 
Error calling StartServiceByName for org.freedesktop.Notifications: Timeout was reached

status eos-notifer

 ❯ systemctl status --user eos-update-notifier.timer
â—Ź eos-update-notifier.timer - EOS update notifier runs periodically, and optionally after each boot, or if missed.
     Loaded: loaded (/home/swh/.config/systemd/user/eos-update-notifier.timer; enabled; preset: enabled)
     Active: active (waiting) since Mon 2025-04-07 15:17:01 CEST; 12min ago
 Invocation: c6424ef1e08549198eb30846ac1d4765
    Trigger: Tue 2025-04-08 00:07:50 CEST; 8h left
   Triggers: â—Ź eos-update-notifier.service

Apr 07 15:17:01 starship systemd[969]: Started EOS update notifier runs periodically, and optionally after each boot, or if missed..

Works here

works too

EDIT: Notify operation test runs ok but I dont get any systray-icon anymore…

Thanks for taking the time to report issues. I’ll look into the tray problem.

BTW, eos-update-notifier is essentially on a low maintenance since it is not really needed by users who already know how to update system.

Naturally it is great to have reports on any of our tools because a report can reveal an issue also in another app that share the common code. :ok_hand:

1 Like

You’re welcome :enos_flag:

It’s fine to have an update-notifier, but in general I don’t need it because I am doing update daily in the morning when taking my coffee :hot_beverage:

1 Like

I’m not using the notifier either since there always are updates.
I simply run eos-update with some nice options like --fast and/or --aur anytime I like to see if there are updates available.

BTW, just noticed that the notify+tray setting shows the systray icon on Xfce.
So next to try KDE.

1 Like

I’ve had to reboot twice today and I’ve just noticed that the icon in the tray has disappeared, as has the indication in the status messages of the remote workspace. This is what i have described in the starting thread but its no longer there

I did a complete eos reinstallation over the weekend with plasma except discover and flatpak. It’s only been one or two updates since yesterday.

I noticed the above because I didn’t have this in my last plasma installation.
I thought I would share it with you

I have two aliases for that

alias upd='eos-update'
alias ua='eos-update --aur'
1 Like

Just tested this in KDE using notify+tray configuration for eos-update-notifier.

  1. Wayland: it gives the same first window like in your first post (access to input devices) and does not update if I refuse the access.
  2. X11: everything works as expected.

That really sounds like a wayland vs. libnotify issue to me.

1 Like

Thanks for testing. :vulcan_salute:

I simply uninstalled the eos-notifier. It’s not that important. At least now you know if there are any more questions. I make your post as solution . Thanks a lot mate :enos_flag:

Thank you for bringing it up! :+1:

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.