When using KDevelop in a preexisting svn checkout, I am not prompted for my SourceForge credentials, I only get an error. Using svn ci from a terminal works fine.
CC'ing Christoph who might be interested in looking at this.
Using "SSH_ASKPASS=ksshaskpass" (https://wiki.archlinux.org/index.php/KDE_Wallet) or "SSH_ASKPASS=" (password will be asked in the terminal) I cannot confirm the issue. Some problems were fixed in commit 9fd4f6c25f6c712a76672e0b3acbefef7d4fd155, but they are not directly related to ssh authentication. What kind of error do you get?
Well, I wasn't running KDevelop in a terminal before and unfortunately I don't remember what the error was, but I'm certain it was because I couldn't enter my password for SVN. I didn't have any error this time because I was able to enter my password, but even though I used SSH_ASKPASS=ksshaskpass kdevelop the prompt was still in the terminal rather than as a dialog. I don't think it should be necessary to change environment variables or run the IDE from a terminal just to enter your SVN password though---KDevelop should be smart enough to find an ssh askpass program if there isn't one specified in an environment variable.
You are right, when run from a terminal, the password seems to be always requested there inside (which is not specific for svn). I was referring to having SSH_ASKPASS=ksshaskpass set for the environment, when starting the usual way. The point is, that the SVN library never gives a response to KDevelop requesting a password, since it directly calls ssh. And ssh prompts for the password in the terminal if there is one or uses SSH_ASKPASS otherwise. I don't see how this could easily be fixed. Maybe consider setting the environment variable as a workaround.
Couldn't you set SSH_ASKPASS with putenv() before calling SVN-related functions? I imagine ssh is a child process started by svn...?
Sounds like a feasible approach. Some other *cough*QtCreator*cough* famous IDE does that as well. [1] That's a great junior job. So in case you're interested in getting this fixed this is also something you could work on! [1] See: https://github.com/qt-creator/qt-creator/blob/master/src/plugins/vcsbase/commonvcssettings.cpp#L45 (and related lines in that file)
Ok, but what should it be set to? KDevelop doesn't really know what kind of program could be used to query a password, no? Maybe a call to KDevelop itself with a new parameter could be used? Like: SSH_ASKPASS="kdevelop --query-pw"
@Christoph: Well, see the code I linked to. QtCreator does just use platform defaults (and also respects the SSH_ASKPASS env var if available).
@Kevin: I'm not fully convinced. One problem is, that SSH_ASKPASS is ignored if a terminal is set [1]. So one would have to trick ssh into believing that there is no terminal; which is explained in [1]. Interestingly ssh-askpass is not part of my system (probably due to relying on the environment variable). That's where the idea of making KDevelop itself some kind of default askpass program was coming from. Nevertheless, setting the environment variable to some default value would surely be a start. [1] https://unix.stackexchange.com/a/272524
*** Bug 184845 has been marked as a duplicate of this bug. ***