Xdg-open refuses to open any file/folder not children of the current location

,

Here’s a head scratcher of an issue. I’m going to post it here since I’m running the KDE spin of Fedora, and I do not know if it’s a KDE or Fedora issue.

Whenever I’m working on code or LaTeX files, I’m using the terminal very often whether directly or through the bang commands in vi/vim/neovim. Thus, I often open a folder or a direct file from my current working directory through the xdg-open foo command.

However, whenever the path I want to open is not a child of the working directory (such as xdg-open ../bar), I get the following error in the terminal:

kf.kio.gui: Failed to launch process as service: app-org.kde.dolphin@262473349eb342e09349126a3710425a.service" "org.freedesktop.DBus.Error.AccessDenied" "Unit app-org.kde.dolphin@262473349eb342e09349126a3710425a.service failed to load properly, please adjust/correct and reload service manager: Operation not permitted"

along with a GUI message which contains the following message:

Unit app-org.kde.dolphin@262473349eb342e09349126a3710425a.service failed to load properly, please adjust/correct and reload service manager: Operation not permitted

Note: the result is the same whether I’m using xdg-open or kde-open, and file associations are respected since opening a text file prompts a similar error message with KWrite as the failing program.

Any idea why this might be happening ? I’m running a near-stock KDE Fedora install (haven’t made modifications to the Plasma theme, haven’t removed any core KDE apps/pkgs AFAIK). I’m running multiple users on the machine – a Framework 13 with AMD processor.

What about gio open?

1 Like

gio open does work, hadn’t thought of trying it out. It doesn’t print any message to the console either, it just works.

That doesn’t shed any light on what might be wrong, though :man_shrugging:

1 Like

I can reproduce what you see.
Either the file must be an absolute path or a child of the current directory.
No idea if this is deliberate or not.

1 Like

Whether it’s deliberate or not, the behaviour definitely changed over the past few weeks. I will open a ticket tomorrow on KDE’s bug tracker if no one has more info until then.

Sorry, I missed that this is a change in behavior.

I can confirm that using xdg-open ../a.txt is working on my f39 plasma kde VM.