Counterintuitive behaviour of "Start at login" option
- Dominant language
- Python
- Stars
- 4.7k
- Forks
- 604
- PR merge metrics
- No merged PRs in 30d
Description
If guake has been added to autostart using an external tool (e.g. gnome-tweak-tool) rather than its own new internal "start at login" option, it silently removes itself from autostart on first start - because the new option's default is set to false and the code enforces it on start up. The culprit seems to be 24fee821e471263036bbd01c88283124c322a6c0 that added the option.
This is a very counterintuitive and annoying behaviour I've ran into after recently upgrading guake, I had to waste some time to find out what was messing up with my autostart! Please respect user's freedom to manage autostart on his own and don't set/remove entries without an explicit choice from the user.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.