Clicking systray applet icon does nothing
Closed this issue · 5 comments
arch-update 2.0.1
when left clicking the icon in the system tray (hyprland / waybar) nothing happend
when right clicking the icon an small white line appears just at the base of the arch logo
(for now i have set up a keybind)
Hi,
Can you stop the currently running systray applet (either by killing the process or stopping the systemd service if you used that), relaunch a new one by running arch-update --tray in a terminal, click it and post the terminal output here please?
receive the following message (also note i did not have an icon i just guessed where it would be)
gio: Unable to launch application ‘/usr/share/applications/arch-update.desktop’: Unable to find terminal required for application
using kitty terminal
Hi,
Can you stop the currently running systray applet (either by killing the process or stopping the systemd service if you used that), relaunch a new one by running
arch-update --trayin a terminal, click it and post the terminal output here please?
receive the following message (also note i did not have an icon i just guessed where it would be)
Since you're running Wayland, make sure you have qt6-wayland installed.
gio: Unable to launch application ‘/usr/share/applications/arch-update.desktop’: Unable to find terminal required for application
This is not an issue with Arch-Update specifically but with gio/glib2 that as a limited list of known/supported terminals. You would probably have the same issue trying to launch any other terminal app via their .desktop file (like htop from the htop.desktop file for instance).
To workaround this, you can either copy the arch-update.desktop file to $HOME/.local/share/applications/arch-update.desktop (see this for more details) and modify the Exec line in it to "force" arch-update to launch with your terminal (e.g. alacritty -e arch-update) or create a symlink for your terminal that points to /usr/bin/xterm (e.g. sudo ln -s /usr/bin/alacritty /usr/bin/xterm), which is the fallback option for gio.
Alternatively, you can obviously install one of the terminal known/supported by gio/glib2 instead.
While waiting for Gnome to implement a way to allow people using their terminal of choice in gio (which will hopefully happen at some point), I'm gonna document the workaround somewhere (maybe in the Tips and Tricks section of the README/man page?), as I assume you won't be the only one facing this situation 😅