| Summary: | rsibreak does not start automatically after install | ||
|---|---|---|---|
| Product: | [Applications] rsibreak | Reporter: | Florian Jacob <accounts+bugs.kde> |
| Component: | general | Assignee: | Albert Astals Cid <aacid> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | 0.12.1 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Florian Jacob
2016-04-16 13:37:55 UTC
what is the value of AutoStart in your .config/rsibreakrc file? It was directly after installation, so the config file didn't exist at all. I did some testing and was very irritated by the behaviour, I thought the results might be wrong due to automatic session restore. I now found http://l10n.kde.org/docs/admin/autostart-and-runonce.html and that I made a wrong assumption, I thought the false in /etc/xdg meant the needed value of the setting to autostart is false, which turned out to be wrong: “The value true at the end of the line is used as default value if the key or config file is not present.” In case it's intentional to start rsibreak automatically on login but requiring that it was started manually once, everything is fine. ;) Sorry for the noise! Yes, we want the user to start it at least once, it's the least intrusive thing to do. Thanks alot for maintaining rsibreak then, it's a really useful tool to me. :) |