Bug 438009 - Open File Manager context menu entry no longer working
Summary: Open File Manager context menu entry no longer working
Status: RESOLVED DOWNSTREAM
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: 21.04.1
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-06-02 18:32 UTC by Unknown
Modified: 2021-06-04 15:28 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
kf5-kio patches applied in Fedora (27.58 KB, image/png)
2021-06-04 13:41 UTC, Yaroslav Sidlovsky
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Unknown 2021-06-02 18:32:32 UTC
SUMMARY
Open File Manager context menu entry no longer working.

STEPS TO REPRODUCE
1. Open Konsole.
2. Press right mouse button and select the "Open File Manager" context menu entry.

OBSERVED RESULT
Unknown mime-type association dialog for the "octet/stream" will be shown.

EXPECTED RESULT
Dolphin should be opened with current directory.

SOFTWARE/OS VERSIONS
Operating System: Fedora 34
KDE Frameworks Version: 5.82.0
Qt Version: 5.15.2
Kernel Version: 5.12.8-300.fc34.x86_64
OS Type: 64-bit
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz
Memory: 15.4 GiB of RAM

ADDITIONAL INFORMATION
Konsole version 21.04.1.
Comment 1 Nate Graham 2021-06-04 12:54:46 UTC
Works for me. What is the path that you're asking Dolphin to open?
Comment 2 Unknown 2021-06-04 12:58:29 UTC
> Works for me. What is the path that you're asking Dolphin to open?

You can use home directory: cd ~

RMB -> Open File Manager -> Unknown mime-type association dialog for the "octet/stream" will be shown.
Comment 3 Nate Graham 2021-06-04 13:14:47 UTC
That works fine for me. What does `file --mime-type ~` say for you?

For me it says "inode/directory".

I gather that for you it says "octet/stream"?
Comment 4 Unknown 2021-06-04 13:24:39 UTC
> That works fine for me. What does `file --mime-type ~` say for you?

$ file --mime-type ~
/home/vitaly: inode/directory
Comment 5 Rex Dieter 2021-06-04 13:25:26 UTC
Odd, I'm experiencing this now too.  I'll dig deeper, Nate's probably right that's it's a mimetype issue.
Comment 7 Unknown 2021-06-04 13:28:28 UTC
I have the same issue also with some text files.

Visit /usr/lib/rpm/macros.d/ on Fedora and click on any *.macros files, for example macros.qt5. Unknown mime-type association dialog for the "octet/stream" will be shown.

$ file --mime-type macros.qt5
macros.qt5: text/plain
Comment 8 Unknown 2021-06-04 13:30:44 UTC
> I'll dig deeper, Nate's probably right that's it's a mimetype issue.

Definitely not. "xdg-open ~" works absolutely fine.
Comment 9 Yaroslav Sidlovsky 2021-06-04 13:41:40 UTC
Created attachment 138992 [details]
kf5-kio patches applied in Fedora

FYI: Fedora packages has been built with some extra patches, some of them are affecting mime detection.
Comment 10 Ahmad Samir 2021-06-04 13:53:01 UTC
It works for me with current git master of the Frameworks, which includes all those patches. (FWIW, it worked before those patches were merged in KIO too,  I use Konsole on a daily basis, if it broke I'd have been hit by this).

This is weird, the open text file (I assume you mean opening by Ctrl+Click) is one code path, the open file manager is a different code path... so yeah, could be KIO (or anything else... :)).

For the text file, to get more debug:
export QT_LOGGING_RULES="*konsole*=true"
konsole

You should see something like:
org.kde.konsole: FileFilterHotSpot: mime type for "/home/ahmad/123" : QMimeType("text/plain")
org.kde.konsole: fullCmd: "/usr/bin/kate /home/ahmad/123"

(I'll see if I can create a Fedora VM to test, at least it's rpm-based, which is the only package manager I am familiar with).
Comment 11 Rex Dieter 2021-06-04 14:01:03 UTC
kde-open5 ~

Fails for me the same way, for what it's worth.

Fedora's kio patches are upstream commits backported that were recommended for distro packagers.
Comment 12 Nate Graham 2021-06-04 14:05:39 UTC
FWIW I am using Fedora with all KDE packages built from source and cannot reproduce the issue.
Comment 13 Unknown 2021-06-04 14:08:28 UTC
> export QT_LOGGING_RULES="*konsole*=true"

$ export QT_LOGGING_RULES="*konsole*=true"
$ konsole
org.kde.konsole: The font to use in the terminal can not be matched exactly on your system.
org.kde.konsole:  Selected:  "Monospace,11.5,-1,2,50,0,0,0,0,0"
org.kde.konsole:  System  :  "DejaVu Sans Mono,11.25,-1,2,50,0,0,0,0,0"
Comment 14 Ahmad Samir 2021-06-04 14:09:25 UTC
And you tried to open a text file from Konsole?
Comment 15 Unknown 2021-06-04 14:18:28 UTC
> And you tried to open a text file from Konsole?

Yes. Tried both ~ and macros.qt5:

$ kde-open5 ~
$ kde-open5 /usr/lib/rpm/macros.d/macros.qt5
Comment 16 Rex Dieter 2021-06-04 15:10:14 UTC
I'll try new kio builds without those backported patches to see if that changes anything.
Comment 17 Rex Dieter 2021-06-04 15:14:03 UTC
Arg, looks like I botched the fedora kf5 update, which included only the first batch of requested patches in build 
kf5-kio-5.82.0-2.fc34

There was a subsquent request to packagers to include another patch or 2 included in build:
kf5-kio-5.82.0-3.fc34

But that build was never pushed to users, testing that build works for me.

I'll take the liberty of closing this as a downstream issue, sorry for the noise.
Comment 18 Nate Graham 2021-06-04 15:16:38 UTC
Thanks for the investigation and the fix, Rex! <3
Comment 19 Unknown 2021-06-04 15:28:11 UTC
I can confirm that kf5-kio-5.82.0-3.fc34 fixes issue. Many thanks.