-
Notifications
You must be signed in to change notification settings - Fork 54
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
Tray doesn't work as a service #130
Comments
@coldfix Was this reproducible on your machine? |
I hope to have time to check this evening. I believe to have experienced similar issue in the past when starting via service files (irrespectively of the auto/smart flag). It could be related to X not being started up when udiskie is creating the BTW: I do currently not recommend starting udiskie as service. |
I'm also having this problem--any updates? And might as well ask questions: Is |
My recommendation for now is: do not use udiskie tray/notifications as a systemd service. GUI service components should be started with the window manager, i.e. in If you sometimes log in without window manager but still want udiskie running, you can start an udiskie instance without notifications/tray via systemd. In this case you would start an additional udiskie instance with notifications/tray but without automount with the window manager as described above. I'm pretty short on time right now, and this is not my top priority, since there is a workaround. |
About your other questions:
Personally, I usually go for detach when I know I'm gonna remove the drive physically. |
From #129, @mindstormer12:
The text was updated successfully, but these errors were encountered: