https://bugs.kde.org/show_bug.cgi?id=387957
--- Comment #9 from hardy.pub...@gmail.com --- You're right, this problem only occurs on Network Shares not local collections. The problem was that the drive-mapped NAS collection on P: drive had the connection dropped by windows. The root cause of this is an ongoing problem for me. If I poke the network share with Windows Explorer then open an image in digiKam, it works fine. So in summary: If the network share where the original is located is disconnected (reason TBC), digiKam must pass an empty image path. Not surprising really. It seems this action is not enough to force Windows to reconnect the network share. I had to use Explorer in this case. I guess we can close this as INVALID unless you know of a way that digiKam can force reconnection when it wants to open the original image on the network share? -- You are receiving this mail because: You are watching all bug changes.
