https://bugs.kde.org/show_bug.cgi?id=497929

TraceyC <kde...@tlcnet.info> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REPORTED                    |CONFIRMED
     Ever confirmed|0                           |1

--- Comment #6 from TraceyC <kde...@tlcnet.info> ---
For the native apps - that is likely a problem with how Arch is packaging
Discord. I can't reproduce this with native apps (including Discord) on Solus
(on Plasma or Budgie). Each distro determines where the .desktop files go. (It
looks like Discord is the only app you've found with this issue). I recommend
reporting the problem with Discord to them. 

Let's focus on the flatpak menu items in this report.
I've narrowed down the problem that the Properties dialog of the menu entry is
creating the broken symlink, other DEs / menu editors do not and are able to
save changes

# Background ##

Where flatpaks  store the .desktop file is up to each flatpak. This is true no
matter if you install them through Discover or via command line.  The default
and usual place for the .desktop file is under /var/lib/flatpak/app/appname/...
e.g.
app/org.wezfurlong.wezterm/current/active/export/share/applications/org.wezfurlong.wezterm.desktop

My testing showed that the error in Plasma when editing a flatpak menu item
happens regardless of distro whenever the .desktop file trying to be saved is
in a place the user can't write to or it has a bad symlink. 

## The problem : the menu Property entry saves a symlink to the main .desktop
file with a broken symlink instead of a new .desktop file under the user
directory ##

After testing on KDE Plasma and Budgie, installing a flatpak through command
line, I observed:

- On both Plasma and Budgie, flatpaks installed their .deskop file correctly to
/var/lib/flatpak/app/appname/current/active/export/share/applications/org.appname.desktop.
At this point, no .desktop file exists under ~/.local/share/applications/
- After attempting to edit a menu entry for a flatpak (for example Obsidian)
  - On Budgie, by editing the entry through MenuLibre - Changes can be saved
and a .desktop file is created at 
    ~/.local/share/applications/md.obsidian.desktop
  - On Plasma, by right clicking the menu entry - the error appears, changes
are not saved, and a broken symlink is created at 
    ~/.local/share/applications/md.obsidian.Obsidian.desktop which points to 
    md.obsidian.Obsidian.desktop ->
../../../app/md.obsidian.Obsidian/current/active/export/share/applications/md.obsidian.Obsidian.desktop


Testing details:
My results were the same on Plasma 6.2.4 and git-master (Solus) as well as KDE
Neon.  I have a few flatpaks and quite a few native packages, but no .desktop
files in /opt

### Native apps ###

- Discord - ok  ✅

### flatpaks ###

- WezTerm - same error as in the report.
Could not save properties due to insufficient write access to:
`/home/user/.local/share/applications/org.wezfurlong.wezterm.desktop`
The .desktop file is a broken symlink

file ~/.local/share/applications/org.wezfurlong.wezterm.desktop
/home/user/.local/share/applications/org.wezfurlong.wezterm.desktop: broken
symbolic link to
../../../app/org.wezfurlong.wezterm/current/active/export/share/applications/org.wezfurlong.wezterm.desktop

- SysD Manager - same error as WezTerm, same cause (broken symlink)
- VSCodium (com.vscodium.codium) - same error, same cause

On KDE Neon, I get the same error for the Visual Studio flatpak. The broken
link is the same. 

~/.local/share/applications/com.visual...

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to