feverfew added a comment.
In D23384#570016 <https://phabricator.kde.org/D23384#570016>, @ngraham wrote: > In D23384#569929 <https://phabricator.kde.org/D23384#569929>, @feverfew wrote: > > > This isn't reaching KIOFuse at all. I believe this is related to this bug and that you've also blogged about: > > https://bugs.kde.org/show_bug.cgi?id=330192 > > https://pointieststick.com/2018/01/17/videos-on-samba-shares/ > > > > This can be solved in this patch (and I did, although I removed it at Harald's request). I think I'll move it back in, and will leave it if it does solve this issue for you. > > > Great! Once it's back in, I'll re-test that. Updated the diff. give it a go... >> You must be doing something wrong. FUSE provides output of all calls that it receives (and how kio-fuse responds). Let me write the instructions more verbosely for CLI to make sure no steps are missed: >> `$ killall kio-fuse` >> `$ export QT_LOGGING_RULES="*.debug=true"` >> `$ kio-fuse $myFavLocation -d &> ~/kio-fuse-debug.txt` (I recommend `$myFabLocation` isn't empty if you haven't installed the `kio-fuse-tmpfiles.conf` exclusion file at the system level.) >> >> Then open the file in the media player. Once your done simply attach `~/kio-fuse-debug.txt` here. >> It's really important for us to know what kind of read requests are being called to help us diagnose the issue. > > I think I found part of the problem. When I follow these instructions, the log file has only a single line: > > kio-fuse: command not found > > > This is because the path it is installed to (`~/kde/usr/lib64/libexec/`) is not in `$PATH`. When I add that location to `$PATH` and try again, the log file contains the following: > > It should probably not assume that `<prefix>/usr/lib64/libexec/` is in `$PATH`, at the minimum. That's just an annoying issue locally, which is resolved by that hack. On the system level this won't be a problem at all. Also, pls put debug output into an attachment in the future (and probably edit your comment above), it's now quite hard to scroll through this diff. > > >> I'm a bit confused. Which one of the three are you doing: >> >> 1. Opening a KIO Url via Dolphin. >> 2. Opening a KIOFuse mount local URL via Dolphin. >> 3. Opening a KIOFuse URL via the media players file picker. > > #2. So as in, you're Dolphin is browsing inside `/run/user/<id>/kio-fuse-XXXXXX/some/location` and you open a file from there? REPOSITORY R241 KIO REVISION DETAIL https://phabricator.kde.org/D23384 To: feverfew, fvogt, davidedmundson, dfaure, ngraham Cc: sitter, davidedmundson, kde-frameworks-devel, ngraham, LeGast00n, GB_2, michaelh, bruns