On 21/11/24 15:32, Frank Bures wrote:
On
2024-11-20 22:24, Tim wrote:
Once more:
A *copy* creates a desktop file in your space that you own, and
you can
modify. The original desktop launcher file (elsewhere on the
system)
will not be changed, and will be ignored.
A *link* points to a file somewhere else on the system, and if
that
somewhere else isn't owned by you (it won't be, in this case),
you
can't modify it.
Thank you all.
Just a silly question, have you tried playing around with setfacl on
the desktop link in your home folder to give your account write
access to the file? I do that with my Thunderbird and firefox
installations where I have them installed in /opt which is owned by
root, so I run setfacl across both of the sub-folders to ensure that
configuration changes I do in both actually get retained. I know I
could install them in folders I do have access to, I just haven't
chosen to do that.
Just another silly question, are you running KDE under Wayland or
Xorg? I'm asking because experience tells me that Wayland seems to
pick and choose what properties exposed by a desktop file on the
desktop it is actually going to honour, even when the desktop file
is created manually by right clicking on the desktop and selecting
"New", which seems to be different to what is does for apps pinned
to the task bar where it seems to honour options that it doesn't
honour from the file on the desktop. I have this issue with my
firefox and Thunderbird icons on the desktop both of which were
created in F40 under Xorg. I had to do a lot of playing around with
the "launch feedback" setting in the firefox icon to get Wayland to
honour the setting, but I've been unable to get Wayland to honour
the same setting in the Thunderbird icon.
regards,
Steve
Cheers
Frank