-
-
Notifications
You must be signed in to change notification settings - Fork 260
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
auto-start does not work on Debian 12 xfce #2943
Comments
Are you using a nFlatpak package or a package from the Debian repository? It is the desktop responsibility to automatically load a desktop file put inside |
The easyeffects version stated by OP is exactly the same as the latest version available in Debian 12, so I'll assume that they're using the native debian package. Either way, this sounds exactly like the kind of behavior a stock xfce install would have, so I wouldn't be suprised if "to refresh your autostart configuration GUI, restart your session or run this funny command" is the expected behavior for xfce. |
@wwmm Debian repo. The installation indeed placed a desktop file in autostart, it's just a bit of a bugbear with xfce. I do still think that a warning should be applied to the installation process if possible, as a newcomer to xfce I was not expecting to have to restart the session. There are other bugs on Debian, though, which are potentially more important |
This is also not necessary on gnome and kde. If the desktop supports the |
EasyEffects Version
7.0.0-1
What package are you using?
Other (specify below)
Distribution
Debian 12 (Bookworm)
Describe the bug
The service auto-start feature in the settings menu has no effect. To start on login, I had to manually add
easyeffects --gapplication-service
to the autostart menu in the xfce settings panel. This was entirely successful, but I don't know if this is a Debian thing or an xfce thing.However, after a restart, the auto generated entry appeared in the xfce panel - perhaps the installation of EasyEffects in an xfce environment should be accompanied by an environmental refresh or an instruction to either restart or logout and login again.
The text was updated successfully, but these errors were encountered: