| Summary: | Adding a new automatically starting application generates deprecated/invalid .desktop file | ||
|---|---|---|---|
| Product: | [Applications] systemsettings | Reporter: | Szőts Ákos <akos+kde> |
| Component: | kcm_autostart | Assignee: | Nicolas Fella <nicolas.fella> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | info, kde, nate, plasma-bugs-null |
| Priority: | NOR | ||
| Version First Reported In: | 5.21.0 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | https://invent.kde.org/plasma/plasma-workspace/-/commit/ced23fc177a665d1c9fec64fdda0de4b0b24b7d6 | Version Fixed/Implemented In: | |
| Sentry Crash Report: | |||
|
Description
Szőts Ákos
2021-02-20 08:59:47 UTC
Does this cause any or is this purely cosmetic? *any noticable issue Currently, it's only cosmetic (apart from the scary-looking red and yellow lines in the journal). In the future, though, I don't know how these programs will behave and what will be their reactions. (In reply to Nicolas Fella from comment #1) > Does this cause any or is this purely cosmetic? When I added a startup application (actually a script) and checked the Terminal options Run in terminal Do not close when command exits my script runs, but I don't see any terminal nor does it stick around, maybe because something is ignoring TerminalOptions=\s--noclose in the generated .desktop file. As a workaround my script writes debug messages to /tmp/myscript.$$.out , but I would like to see them in a terminal. If these terminal options aren't going to have any effect, then kcm_autostart shouldn't offer them (which is a slightly different bug, I guess). (In reply to skierpage from comment #4) > (In reply to Nicolas Fella from comment #1) > > Does this cause any or is this purely cosmetic? > > When I added a startup application (actually a script) and checked the > Terminal options > Run in terminal > Do not close when command exits > my script runs, but I don't see any terminal nor does it stick around, maybe > because something is ignoring > TerminalOptions=\s--noclose > in the generated .desktop file. > > As a workaround my script writes debug messages to /tmp/myscript.$$.out , > but I would like to see them in a terminal. If these terminal options aren't > going to have any effect, then kcm_autostart shouldn't offer them (which is > a slightly different bug, I guess). That's unrelated to the original report, can you please open a new bug so we can track this properly? (In reply to Nicolas Fella from comment #5) > (In reply to skierpage from comment #4) > > (In reply to Nicolas Fella from comment #1) > > When I added a startup application (actually a script) and checked the > > Terminal options > > Run in terminal > > Do not close when command exits > > my script runs, but I don't see any terminal nor does it stick around, ... > > That's unrelated to the original report, can you please open a new bug so we > can track this properly? Thanks for responding 😽! I filed bug 437883. A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/3089 Git commit e9c4626b94a21ed80f438ee8a40d2d57610ed3db by Nate Graham, on behalf of Thenujan Sandramohan. Committed on 24/07/2023 at 23:15. Pushed by ngraham into branch 'master'. Do not write empty path to desktop file M +0 -1 libkworkspace/autostartscriptdesktopfile.cpp https://invent.kde.org/plasma/plasma-workspace/-/commit/e9c4626b94a21ed80f438ee8a40d2d57610ed3db Git commit ced23fc177a665d1c9fec64fdda0de4b0b24b7d6 by Nate Graham, on behalf of Thenujan Sandramohan. Committed on 24/07/2023 at 23:44. Pushed by ngraham into branch 'Plasma/5.27'. Do not write empty path to desktop file (cherry picked from commit e9c4626b94a21ed80f438ee8a40d2d57610ed3db) M +0 -1 libkworkspace/autostartscriptdesktopfile.cpp https://invent.kde.org/plasma/plasma-workspace/-/commit/ced23fc177a665d1c9fec64fdda0de4b0b24b7d6 |