| Summary: | Resolve symlinks when copying .desktop files into ~/.config/autostart | ||
|---|---|---|---|
| Product: | [Applications] systemsettings | Reporter: | Szczepan Hołyszewski <rulatir> |
| Component: | kcm_autostart | Assignee: | Laurent Montel <montel> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | nate, null, sthenujan2002 |
| Priority: | NOR | Keywords: | junior-jobs, usability |
| Version First Reported In: | 5.17.2 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Szczepan Hołyszewski
2019-11-11 03:50:10 UTC
To clarify the first sentence: I want the creation of user-owned copy to be performed automatically by systemsettings. It is of course possible to do that manually, but it shouldn't be necessary. Works for me. Can you verify the permissions of ~/.config/autostart/slack.desktop Does that file exist and is it writable by your user? And are you running System Settings as your own user? At this time I have a copy of the .desktop file in autostart, and I can freely modify the command using systemsettings autostart page. I may have simply copied it there in the meantime. But I distinctly remember that the file was originally a symlink to /usr/share/applications/slack.desktop, which is probably how Slack installs it when you configure autostart in Slack's options. And in THAT case the behavior was wrong. Systemsettings was unable to detect the "this file is a symlink to a file I don't own" condition. It should be able to do so, and create a "copy-on-write" of the unwritable file, replacing the symlink. The whole operation should be entirely transparent to the user who may not be a symlink-savvy technical person. Thanks, confirmed. The bug is probably somewhere in here: https://cgit.kde.org/plasma-desktop.git/tree/kcms/autostart/autostart.cpp#n274 |