-
Notifications
You must be signed in to change notification settings - Fork 70
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
Desktop mode won't let me change icons, says no write access to .local #1744
Comments
I can reproduce this issue. Here's the problem:
The Flatpak got installed as root-owned. Changing the desktop file involves changing the app's .desktop file. There's a check to see if the desktop file is root-owned; if it is, the system makes a copy. In this case the situation is more subtle: the desktop file itself is not root-owned, but it's a symlink pointing to the file that is root-owned. As a result, the system mis-detects it as being user-owned, tried to change it directly, and fails. That's when using the properties dialog; when trying to do the same using KMenuEdit, it instead fails silently. |
Can you specify what application you're having this problem with and provide the output of This is likely (going to be) resolved with https://invent.kde.org/plasma/kmenuedit/-/merge_requests/41, but I'd like to confirm. |
Misleading directory because there is not much in it. The real problem is everywhere else.
The items in the launcher menus point directly to those. |
When you modify an application launcher, a copy of it is saved to It seems that, via the file properties dialog, where the original being copied was a symlink, it would copy the symlink itself rather than the file referenced, such that it ends up trying to access the symlink and modify the original, which it can't due to permissions. I've introduced changes into KDE Menu Editor to remove an already existing symlink so that it won't block this. It does not appear to have this flaw that creates symlinks. If you share the specific application and |
It's every application.. Here is my ~/.local/share/applications folder.. as you can see, it is not much. I have many more apps installed, not sure how this folder gets populated. The only ones that had direct user intervention from me was the screenlocker script, a generated file for an appimage, and kfontview-2 was me testing something using the kde dialogs. So just 3 items. All the rest was generated by other stuff.
|
And you see this problem happen with Haruna and Yuzu? If so, then it should be fixed in KDE Plasma 6.4 with KMenuEdit. I'm also looking into the file properties dialog to see if anything needs changing & backporting there. |
You should be able to work around this for now by using KDE Menu Editor (kmenuedit), after deleting the symlinks manually — I don't believe it ever erroneously made symlinks, but would get stuck on them. I'm not certain if SteamOS ships it. |
It doesn't ship it. Those two in the folder were both installed by Discover app (which is included by SteamOS). Ugh.. Plasma 6.4 is probably a year away.. SteamOS 3.7 (guessing June stable channel) is only going to be 6.2.5. Icon packs run in SU mode so they can change a bunch of icons at once so that's nice. But yeah, looks like SU mode is the order of the day if someone wants to edit the menu entries because of where they point to, using VLC as an example which was also installed using Discover (though it didn't make a link in that .local folder). |
Your system information
Please describe your issue in as much detail as possible:
In desktop mode in the favourites menu, if one wants to change an icon, it won't save the chosen icon. It pops up an error dialog saying:
"Could not save properties due to insufficient write access to: '/home/deck/.local/share/applications/org.flatpakappname.desktop'."
Steps for reproducing this issue:
I feel that the home folder SHOULD have write access to allow people to change the icons.. why are the .desktop files write protected???
The text was updated successfully, but these errors were encountered: