-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unit tray.target not found #2064
Comments
Unfortunately, the tray.target is only created if xsession management is enabled in HM. The creation of said systemd target should be moved elsewhere. In the meantime, you can create the systemd target manually from the xsession.nix? file and add |
Ah, this explains why I encountered that error on my wayland system. We should definitely fix that. |
I have this problem on X11. |
Can confirm the problem on X11 with |
@vyorkin I should probably mention that I worked around this for the time being with the following in my systemd.user.targets.tray = {
Unit = {
Description = "Home Manager System Tray";
Requires = [ "graphical-session-pre.target" ];
};
}; which I lifted from |
This comment was marked as outdated.
This comment was marked as outdated.
Still an issue. The home-manager udiskie service doesn't work on my nixos 21.05. |
I've since enabled xsession management, but I'm assuming that with this change, someone that's not running sway nor xsession management will still have this issue? |
What I noticed is that I can't start any service in |
Fixes "Failed to start syncthingtray.service: Unit tray.target not found." nix-community/home-manager#2064
I believe this should be reopened? I'm using marco (rather than sway) without xsession management, and I'm coming across this issue. |
I can see two solutions:
|
Just some thought to add: I've been trying to wrap my head around what this target is for and how it's supposed to be used for. By the description it seems like the target being active indicates that there is a system tray active. This caused a lot of confusion for me because all 3rd party bars providing a system tray out there actually start after graphical-session.target creating dependency cycles on most desktops. Then again apps that use a system tray will request the tray from the dbus, which most likely will start the bar for the tray which makes their systemd service only a backup in case dbus hasn't started them yet. As far as I understand the only requirement for tray.target to be met seems to be dbus.service and possibly (xdg-desktop-portal.service ?). Am I right so far? |
Wasn't able to start network manager applet because of the missing |
Interestingly, using @zeorin's fix for |
Doesn't seem to work on NixOS 24.05 with GNOME using wayland either. Cross-Referencing: NiXium-org/NiXium#115 |
Confirming I'm seeing this on unstable now with
Any other details I can provide that would help debug this? |
i too am encountering this issue on unstable after an update
This fixed it |
Issue description
On current master, I get the error
Unit tray.target not found
when I try to start some systemd units (like udiskie or blueman).I'm using waybar, I think this error is related to #2027
Meta
Maintainer CC
@berbiche @NickHu
Technical details
The text was updated successfully, but these errors were encountered: