Gwenview, version 15.08.2 (not selectable in version field), or some other component that Gwenview triggers ask for SSH key password when viewing a local image. Likely cause are some places with fish://-URLs. Reproducible: Always Steps to Reproduce: 1. Have some place with fish://-URL. 2. Have no SSH keys in ssh-agent, i.e.: ssh-add -D 2. Open a local image. Actual Results: Asks for SSH key password. Expected Results: Does not attempt to access places unless I tell it to do so. Likely related or even same cause: Bug 354475 - VPN "Places" cause gwenview to show "Timeout connecting to ..." even though they weren't clicked.
*** Bug 356962 has been marked as a duplicate of this bug. ***
*** Bug 354475 has been marked as a duplicate of this bug. ***
*** Bug 344153 has been marked as a duplicate of this bug. ***
*** Bug 274673 has been marked as a duplicate of this bug. ***
I confirm this, as I did in 2014 in comment https://bugs.kde.org/show_bug.cgi?id=274673#c1
*** Bug 292580 has been marked as a duplicate of this bug. ***
*** Bug 335498 has been marked as a duplicate of this bug. ***
Turns out this isn't Gwenview but rather KIO's KFilePlacesModel, which Gwenview uses. It's especially visible for Gwenview because Gwenview has a Places panel equivalent like Dolphin--but unlike Dolphin, Gwenview's can't be hidden. *** This bug has been marked as a duplicate of bug 272361 ***
Nate: Thanks for working on this, but did you actually try the steps to reproduce in every bug before mass-duplicating them? Having "Place" in the title does not immediately mean it's the same underlying problem. For example in this bug, I'm not even able to replicate the problem anymore (while according to you it is still an open issue): I can add a "fish://" entry to the places panel in Gwenview just fine (and in Dolphin too), and after a restart only when actively clicking on it I'm asked for the credentials.
Ah, that's great! Feel free to un-dupe this and mark it as RESOLVED, or NEEDSINFO (with a comment for Martin S.) if you're not comfortable closing this bug report based on a single failure to reproduce the issue..