Bug 449234 - I'm getting a code 100 error every time I try to open a directory through a program or my super menu, after switching from XFCE
Summary: I'm getting a code 100 error every time I try to open a directory through a p...
Status: RESOLVED DUPLICATE of bug 305136
Alias: None
Product: frameworks-kio
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 5.96.0
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KIO Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-01-27 10:49 UTC by Dae Lakin
Modified: 2022-08-11 17:21 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
attachment-32290-0.html (1.34 KB, text/html)
2022-01-29 11:04 UTC, Dae Lakin
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Dae Lakin 2022-01-27 10:49:28 UTC
SUMMARY
I'm getting a code 100 error every time I try to open a directory through a program or my super menu, after switching from XFCE

STEPS TO REPRODUCE
1. Install KDE on a system with only XFCE
2. Uninstall XFCE
3. Open Documents from KDE super menu

EXPECTED RESULT
Documents Directory opens in Dolphin (My default file manager)

OBSERVED RESULT
I get an error window:

Unknown error code 100
Could not find the program 'exo-open'
Please send a full bug report at https://bugs.kde.org.

and the logs read:

23.553 D Opening directory "/home/daedalus/UserFiles/Documents"
kf.service.services: KApplicationTrader: mimeType "x-scheme-handler/file" not found
Icon theme "gnome" not found.
kf.kio.gui: "Could not find the program 'exo-open'"


SOFTWARE/OS VERSIONS
Linux Kernel: 5.16.2-arch1-1
KDE Plasma Version: Plasma 5.23.5 (using bspwm as wm, plasma as de)
KDE Frameworks Version: 5.90.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
This functionality worked fine before uninstalling XFCE, but now that it's gone, KDE is still trying to use XFCE's preferred program manager instead of it's own
Comment 1 Nicolas Fella 2022-01-27 13:57:36 UTC
What is the value of $XDG_CURRENT_DESKTOP ?
Comment 2 Nate Graham 2022-01-27 21:00:20 UTC
> Could not find the program 'exo-open'

This means that your system's file manager is still trying to use some old XFCE thing. You'll need to manually reset it by going to System Settings > Applications > Default Applications > File Manager > change it to "Dolphin".

Normally this happens automatically at system installation, but evidently it is a manual process when you install the system manually like you've done.
Comment 3 Nicolas Fella 2022-01-27 21:07:42 UTC
(In reply to Nate Graham from comment #2)
> > Could not find the program 'exo-open'
> 
> This means that your system's file manager is still trying to use some old
> XFCE thing. You'll need to manually reset it by going to System Settings >
> Applications > Default Applications > File Manager > change it to "Dolphin".
> 
> Normally this happens automatically at system installation, but evidently it
> is a manual process when you install the system manually like you've done.

The actual cause is somewhat different. xdg-open calls exo-open when it detects that it's running on XFCE, and kde-open when it detects that it's running on Plasma. It does that detection based on the value of XDG_CURRENT_DESKTOP. Setting that to "KDE" should make things work
Comment 4 Nate Graham 2022-01-27 21:20:29 UTC
Ah, thanks for the correction!

Good that you found that, since XDG_CURRENT_DESKTOP being set to xfce would cause a million other things to break as well.
Comment 5 Dae Lakin 2022-01-28 04:07:35 UTC
(In reply to Nicolas Fella from comment #3)
> (In reply to Nate Graham from comment #2)
> > > Could not find the program 'exo-open'
> > 
> > This means that your system's file manager is still trying to use some old
> > XFCE thing. You'll need to manually reset it by going to System Settings >
> > Applications > Default Applications > File Manager > change it to "Dolphin".
> > 
> > Normally this happens automatically at system installation, but evidently it
> > is a manual process when you install the system manually like you've done.
> 
> The actual cause is somewhat different. xdg-open calls exo-open when it
> detects that it's running on XFCE, and kde-open when it detects that it's
> running on Plasma. It does that detection based on the value of
> XDG_CURRENT_DESKTOP. Setting that to "KDE" should make things work

Actually, it's not set to XFCE
using `wmctrl -m` I checked and my current window manager is registered as bspwm, which is, indeed, the wm I'm using. I'll try adding a script to my bspwm loader to change XDG_CURRENT_DESKTOP to KDE on login, and report back to tell you if this worked
Comment 6 Dae Lakin 2022-01-28 04:15:43 UTC
(In reply to Dae Lakin from comment #5)
> (In reply to Nicolas Fella from comment #3)
> > (In reply to Nate Graham from comment #2)
> > > > Could not find the program 'exo-open'
> > > 
> > > This means that your system's file manager is still trying to use some old
> > > XFCE thing. You'll need to manually reset it by going to System Settings >
> > > Applications > Default Applications > File Manager > change it to "Dolphin".
> > > 
> > > Normally this happens automatically at system installation, but evidently it
> > > is a manual process when you install the system manually like you've done.
> > 
> > The actual cause is somewhat different. xdg-open calls exo-open when it
> > detects that it's running on XFCE, and kde-open when it detects that it's
> > running on Plasma. It does that detection based on the value of
> > XDG_CURRENT_DESKTOP. Setting that to "KDE" should make things work
> 
> Actually, it's not set to XFCE
> using `wmctrl -m` I checked and my current window manager is registered as
> bspwm, which is, indeed, the wm I'm using. I'll try adding a script to my
> bspwm loader to change XDG_CURRENT_DESKTOP to KDE on login, and report back
> to tell you if this worked

Alright, I should have checked this way before instead of using wmctrl but I was dumb about it
anyway, $XDG_CURRENT_DESKTOP is now set to KDE, as verified by sending `echo $XDG_CURRENT_DESKTOP` in Konsole, and things are worse XD
I have the exact same problem, and now plasma windows won't even open at all on top of that
Comment 7 Dae Lakin 2022-01-28 04:33:25 UTC
(In reply to Dae Lakin from comment #6)
> [ -snip- ]

Alright, disregard that, it was an unrelated issue that I solved
I removed the line from my WM script and the XDG_CURRENT_DESKTOP variable is still KDE
everything is acting as it was, including the bug
I am presuming that the variable has been set to KDE since I installed, as I have not experienced any other intergration issue at all since I started using KDE over XFCE in october, and as was mentioned I should have it the variable were not set to KDE, and the system wants to use exo-open regardless of the setting it seems
is it possible that the KDE open program is not installed somehow?
that's my only theory as to why the system would insist on using exo-open right now...
but I have no idea how I would go about installing kde-open if that were the case
and I have a feeling I'm just talking nonsense anyway XD
Comment 8 Dae Lakin 2022-01-28 04:38:02 UTC
(In reply to Dae Lakin from comment #7)
> [ -snip- ]

How frustrating, the middle of my message was cut out
it should read:

> ...as I have not experienced any other integration issue at all since I started using KDE over XFCE in october, and as was mentioned I should have been experiencing multiple issues if the variable was set to anything other than KDE.
> For some reason, the system wants to use exo-open regardless of the setting it seems.
> Is it possible...
Comment 9 Dae Lakin 2022-01-28 08:02:58 UTC
As an addendum, I forgot to mention as it was one of the first things I tried, that when I disable BSPWM and use pure kde & plasma WM and DE, I get the same problem, so it's nothing to do with my bspwm window placement interfering
Comment 10 Nicolas Fella 2022-01-28 13:32:28 UTC
> is it possible that the KDE open program is not installed somehow?

make sure kde-cli-tools is installed
Comment 11 Dae Lakin 2022-01-28 14:10:41 UTC
(In reply to Nicolas Fella from comment #10)
> > is it possible that the KDE open program is not installed somehow?
> 
> make sure kde-cli-tools is installed

yep, the package kde-cli-tools-5.23.5-1 is installed
Comment 12 Nicolas Fella 2022-01-28 14:36:08 UTC
Does "xdg-open $HOME" work?
Comment 13 Dae Lakin 2022-01-29 11:04:43 UTC
Created attachment 146032 [details]
attachment-32290-0.html

Nope!

*$ xdg-open $HOME*
kf.service.services: KApplicationTrader: mimeType "x-scheme-handler/file"
not
found
Icon theme "gnome" not found.
kf.kio.gui: "Could not find the program 'exo-open'"



On Fri, 28 Jan 2022 at 11:36, Nicolas Fella <bugzilla_noreply@kde.org>
wrote:

> https://bugs.kde.org/show_bug.cgi?id=449234
>
> --- Comment #12 from Nicolas Fella <nicolas.fella@gmx.de> ---
> Does "xdg-open $HOME" work?
>
> --
> You are receiving this mail because:
> You reported the bug.
Comment 14 Nicolas Fella 2022-01-29 12:33:36 UTC
What"s the output of "xdg-mime query default inode/directory"?
Comment 15 Dae Lakin 2022-01-29 15:12:40 UTC
(In reply to Nicolas Fella from comment #14)
> What"s the output of "xdg-mime query default inode/directory"?

$ xdg-mime query default inode/directory
org.kde.dolphin.desktop
Comment 16 Dae Lakin 2022-02-01 15:34:15 UTC
Bump
Comment 17 Mike 2022-08-10 21:44:09 UTC
I recently upgraded from Ubuntu 20.04 to 22.04 (KDE: 5.92 ) and I'm seeing the same problem.

$XDG_CURRENT_DESKTOP=KDE

But when I try to open files (ie: view downloaded images from Chrome), or even open the "Home" icon my desktop, I get an error:

Unknown error code 100
Could not find the program 'exo-open'

$ xdg-mime query default inode/directory
org.kde.dolphin.desktop
Comment 18 Mike 2022-08-10 22:02:52 UTC
Looks like I was able to resolve the issue by removing any line that mentions "exo" from files within: ~/.local/share/applications

For example:
exo-file-manager.desktop:Exec=exo-open --launch FileManager %u
mimeapps.list:x-scheme-handler/file=exo-file-manager.desktop
Comment 19 Nate Graham 2022-08-11 17:21:54 UTC
Argh, I guess this has the same root cause as Bug 305136, then.

*** This bug has been marked as a duplicate of bug 305136 ***