![]() ![]() Sudo rm /usr/local/share/applications/feh.desktop # This part will remove the old 3.0 / 2018 version of feh: So there is a difference in the path feh sees, which depends on the smb host and on the type of mount. I tried a temporary mount via pcmanfm's network connect option: working like a charm. Showing the pictures on the NAS is no problem at all. 223_grotere.jpg - File does not existįeh WARNING. 222_grotere.jpg - File does not existįeh WARNING. 221_grotere.jpg - File does not existįeh WARNING. 220_grotere.jpg - File does not existįeh WARNING. 219_grotere.jpg - File does not existįeh WARNING. In a terminal I get "File does not exist" messages, but all files do $ fehshow Biezenstraat156įeh WARNING. Only one-by-one, no show, no "next/previous picture". Ok, I did, the warning disappeared but no joy of showing pictures on that share. When I tried to show pictures from a Windows share, feh told me to recompile with the "stat64=1" option. The shares are in the fstab, so mounted at boot time. I have pictures shared on a NAS and on a Windows 10 pc. So my best suggestion is to Google around and check out some of the other forums on this site that deal specifically with remotely-accessed storage devices.īeautiful script, it installed Feh faster than in 3 minutes. Although this doesn't tell me the exact cause, it tells me all I need to know at the 30,000-foot level: For whatever reason, your remotely-accessed storage device is not behaving as a completely normal, locally-accessed Ext4 device.Īnd that's a problem - because no matter how a storage device is actually connected behind the scenes, it should still "look" and behave like any other storage device in order for mainstream applications to use it. GPicView is a totally separate program from my solution, yet on your system it can't even move through standard image files on your remote device. My image-viewing solution is merely an "innocent bystander" to whatever is going on. This is definitely some kind of networking issue - or an issue with the external device's configuration. Do you have any idea what the problem may be? The 500G HDD is accessed by other Pi by mounting it with the following entry in that Pi's /etc/fstab. ![]() However it will not display an image mounted on a remote drive. ![]()
0 Comments
Leave a Reply. |