0.99.6 Linux (KDE): "Open in file explorer" not working

[winnylinny]

Even with previous versions, this issue still persisted.

Currently, in version 0.99.6, under KDE (Linux), I receive the following error message when trying to use:

Right-click -> "Open in file explorer"

"Error - KIO Client"

It doesn't matter if it's a local folder, external drive, or network share.

This issue does not happen on Windows. I can try to test this out on Xfce or GNOME later on.

This happens in the Viewer and the Browser.

[xnview]

This issue does not happen on Windows. I can try to test this out on Xfce or GNOME later on.

It seems that this issue comes with different version of Qt

[winnylinny]

This issue does not happen on Windows. I can try to test this out on Xfce or GNOME later on.

It seems that this issue comes with different version of Qt

You're correct. I just tried with a different installer from the AUR (xnviewmp-system-libs), and it indeed works properly when selecting "Open in file explorer".

However, using this version, while it fixes the bugs related to opening paths or invoking XnViewMP from another application (such as double-clicking the results of a "finder" app), using this "system-libs" version introduces other bugs, such as crashing when trying to view certain JPEGs or navigating with the viewer.

I wonder why it's an issue if XnViewMP is using its own Qt libraries?

[xnview]

I wonder why it's an issue if XnViewMP is using its own Qt libraries?

It seems that executing other Qt app use XnView libs and not system

[winnylinny]

It seems that executing other Qt app use XnView libs and not system

Is this something that can be fixed in XnViewMP? Perhaps, to tell it "don't use XnView libs when giving / receiving command to / from outside application"?

[winnylinny]

Is this being looked into?

It not only breaks "Open in file explorer", but it also breaks anything related to invoking XnViewMP from an outside application. For example, if XnViewMP is my default image viewer in KDE, then double-clicking on a file in a list in a separate application (e.g, Czkawka), nothing will happen. However, if I'm using the custom XnViewMP package that uses system libraries, then the above all works as expected.

So the question, why not use the custom package instead? Because the program itself is buggy if using the custom package. Even zooming in and out crashes the application.

So perhaps the solution is not to use the system libs for XnViewMP itself, yet to use system libs if another application is being invoked or invoking XnViewMP?

[xnview]

So perhaps the solution is not to use the system libs for XnViewMP itself, yet to use system libs if another application is being invoked or invoking XnViewMP?

Do you have tried to use system libs? Which qt version?

[winnylinny]

So perhaps the solution is not to use the system libs for XnViewMP itself, yet to use system libs if another application is being invoked or invoking XnViewMP?

Do you have tried to use system libs? Which qt version?

If I use the package in my Software Manager which installs "xnviewmp-system-libs", then it uses system libraries and the above issues work correctly.

However...

Other things in the application will crash or be unstable, such as zooming in or scrolling through images, if I use "xnviewmp-system-libs". (This is why I need to revert back to the default "xnviewmp" package, which sadly has the issue with "mis-matched" Qt libraries.

My system's Qt5 version: 5.15.2

(Happens on multiple PCs using Manjaro KDE.)

[xnview]

Which Manjaro KDE version?

[winnylinny]

Sorry for the late reply.

System information:

Operating System: Manjaro Linux
KDE Plasma: 5.23.5
KDE Frameworks: 5.90.0
Qt: 5.15.2
Kernel: 5.16.5
Graphics Processor: Intel Xe Graphics

I also have another PC of the same OS / software, the only difference is it uses Nvidia.

[xnview]

is it Manjaro 21.0?

[winnylinny]

is it Manjaro 21.0?

I missed this response!

As an update, the issue remains with the following versions:

XnViewMP: 0.99.7

Manjaro Linux: 21.2.5
KDE Plasma: 5.24.3
KDE Frameworks: 5.91.0
Qt Version: 5.15.3

[winnylinny]

Will this be a repeating problem, as a user's Linux system gets updated, and thus their Qt version is updated?

Is there a way around this?

[xnview]

please check this topic

[winnylinny]

That topic is a similar (but still different) issue.

The bug I'm pointing at is where XnViewMP will not open up the current location of the image in the system's "file explorer".

It works on Windows 10.

However, in Linux (such as KDE), it spits out an error about "Error - KIO Client".

This is not an issue if I use the version of XnViewMP that uses the system libraries (rather than its own bundled libraries.)