Hi everyone,
I am looking for a way to modify the position of a desktop icon so that it doesn’t follow the automatic default grid sorting of the other desktop icons present - but rather that it alone is positioned in the middle right of the screen.
Normally, this should be trivial to implement by just dragging the icon to the correct position or editing the [Containments][1][General] section in plasma-org.kde.plasma.desktop-appletsrc with the desired row and column of the icon in question.
The system I’m building, however, is a read-only live appliance that only runs from RAM - so every configuration needs to be applied during the build process, as any changes to the live system are lost after rebooting. This also means that every launch of Plasma 6 is the first time Plasma actually runs on the built system.
So far I’ve tried to go the easy route: I dragged the icon in question to the right position on the desktop of the live system, copied the resulting plasma-org.kde.plasma.desktop-appletsrc to my build host and re-built the appliance with the altered desktop-appletsrcin the .config directory.
Result: Plasma overwrites the file when launched → instead of the correct [Containments][1][General] section, there suddenly is a [Containments][18][General] section with default settings present upon login. Consequently, the icons are ordered by default.
Second try: Remove write permissions for the altereddesktop-appletsrccopied from the live system. Results in failure as well: All icons are ordered by default and the wallpaper is gone.
Which now leads me to my plea for help: Is there any way to launch a scriptable command during login that either moves the icon in question to the right position (maybe some qdbus magic I haven’t yet stumbled upon?) or that adds the correct postion of the icon to the desktop-appletsrc that is generated upon the first login? Preferably, this would happen immediately after login so that a user doesn’t even see the icon being moved.
Sorry for bothering you with such a trivial thing but this turns out to be surprisingly hard to implement via any configuration avenue I can think of.
Best wishes, Dreepy