https://bugs.kde.org/show_bug.cgi?id=380311
--- Comment #2 from Hector Martin <hec...@marcansoft.com> --- To be clear, the problem isn't that this is an interactive process *when those scripts are executed*, it's that the appropriate display environment variables need to be available so they are inherited by an intearctive child process at a later time, in response to a user request. For now I resorted to the aforementioned hack of wrapping ksshaskpass in a script that sources the display environment variables from somewhere else filled in by an autostart script. ssh-agent still starts from env/, but now the script it calls injects the right variables before execing ksshaskpass. I did have to set DISPLAY to a dummy value in the parent script, though, because ssh-agent checks that it is set before even trying to call askpass... -- You are receiving this mail because: You are watching all bug changes.
