Bug 471142 - Koko doesn`t show samba-Images
Summary: Koko doesn`t show samba-Images
Status: REPORTED
Alias: None
Product: Koko
Classification: Applications
Component: General (show other bugs)
Version: 23.04.2
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-06-17 09:45 UTC by Leo
Modified: 2023-11-28 18:05 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Images not displayed. (330.41 KB, image/png)
2023-06-17 09:45 UTC, Leo
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Leo 2023-06-17 09:45:38 UTC
Created attachment 159736 [details]
Images not displayed.

SUMMARY
Everything works like expected. In the previewscreen all images in the folder get loaded correctly but if I open an Image the screen stays black. Only the bottom previewspace shows the images in the Folder.

STEPS TO REPRODUCE
1. Open the smb-share with Dolphin and open the image on the network-samba-share


OBSERVED RESULT
See the attachment

EXPECTED RESULT
Picture displayed

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux/X11/Nvidia
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.107.0
Qt Version: 5.15.10

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2023-06-22 05:51:26 UTC
Can you run `koko` in a terminal window and paste the text displayed in the terminal window when using Koko in this way? Maybe there are some clues there.
Comment 2 Leo 2023-06-22 21:52:39 UTC
That Idea is so simple. I didn't think of it. It was to obvious. 

[username@archlinux ~]$ koko "smb://user@nas/photo/2016/2016 Ausflüge/2016 Schrecksee/20160716_211030.jpg"
("/home/username/Bilder")
Cannot initialize model with data QJsonObject(). missing: QJsonValue(string, "urls")
qml: smb://user@nas/photo/2016/2016 Ausflüge/2016 Schrecksee
Cannot initialize model with data QJsonObject(). missing: QJsonValue(string, "urls")
QFSFileEngine::open: No file name specified
QFSFileEngine::open: No file name specified
QFSFileEngine::open: No file name specified
QFSFileEngine::open: No file name specified
QFSFileEngine::open: No file name specified
QFSFileEngine::open: No file name specified
qml: Unknown file type for URL smb://user@nas/photo/2016/2016 Ausflüge/2016 Schrecksee/20160716_153914.jpg
qml: Unknown file type for URL smb://user@nas/photo/2016/2016 Ausflüge/2016 Schrecksee/20160716_160410.jpg
QFSFileEngine::open: No file name specified
QFSFileEngine::open: No file name specified
QFSFileEngine::open: No file name specified
QFSFileEngine::open: No file name specified
QFSFileEngine::open: No file name specified
QFSFileEngine::open: No file name specified
file:///usr/lib/qt/qml/org/kde/kirigami.2/private/PrivateActionToolButton.qml:70:5: QML Binding: Binding loop detected for property "value"
qml: Unknown file type for URL smb://user@nas/photo/2016/2016 Ausflüge/2016 Schrecksee/20160716_211030.jpg
qml: Unknown file type for URL smb://user@nas/photo/2016/2016 Ausflüge/2016 Schrecksee/20160716_211400.jpg
Comment 3 Leo 2023-06-22 21:56:53 UTC
Might be because of the spaces in the path? No it isn't. I tried it. The log is the same.
Comment 4 Bug Janitor Service 2023-07-07 03:45:10 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 berturion 2023-11-28 18:05:18 UTC
Hello I have the exact same problem as described by Leo. Using Arch Linux with KDE Desktop.
Image is not displayed by Koko, though, all previews are present at the bottom.
The same share mounted with cifs in my fstab show no problems at all.
It seems related to kio-fuse and the smb:// mounting mecanism.

I can't find the place where kio-fuse mounts the smb share. It is not in my "/run/user/1001" folder :

[horus@horus ~]$ ls -al /run/user/1001/
total 4
drwx------ 14 horus horus 420 28 nov.  18:55 .
drwxr-xr-x  3 root  root   60 28 nov.  18:32 ..
drwxr-xr-x  2 horus horus 120 28 nov.  18:32 akonadi
drwx------  2 horus horus  60 28 nov.  18:32 at-spi
srw-rw-rw-  1 horus horus   0 28 nov.  18:32 bus
drwx------  3 horus horus  60 28 nov.  18:32 dbus-1
drwx------  2 horus horus  60 28 nov.  18:32 dconf
dr-x------  2 horus horus   0  1 janv.  1970 doc
drwx------  2 horus horus  60 28 nov.  18:32 gcr
drwx------  2 horus horus 140 28 nov.  18:32 gnupg
drwx------  2 horus horus  80 28 nov.  18:32 keyring
-rw-r--r--  1 horus horus  66 28 nov.  18:32 KSMserver__0
srwxr-xr-x  1 horus horus   0 28 nov.  18:32 kwallet5.socket
drwxr-xr-x  2 horus horus  60 28 nov.  18:32 Nextcloud
drwxr-xr-x  2 horus horus  60 28 nov.  18:32 p11-kit
srw-rw-rw-  1 horus horus   0 28 nov.  18:32 pipewire-0
-rw-r-----  1 horus horus   0 28 nov.  18:32 pipewire-0.lock
srw-rw-rw-  1 horus horus   0 28 nov.  18:32 pipewire-0-manager
-rw-r-----  1 horus horus   0 28 nov.  18:32 pipewire-0-manager.lock
drwx------  2 horus horus  80 28 nov.  18:32 pulse
drwxr-xr-x  7 horus horus 180 28 nov.  18:32 systemd

I want to try to launch koko from command line from this "virtual" mount but I don't know how.
Any help appreciated.