Version: (using KDE 4.3.3) OS: Linux Installed from: Archlinux Packages I'm received the error in the subject extremely frequently when using the io slave. It is not dependent on host, domain vs ip, public key vs password auth, or anything else. 1 in 3 requests with sftp succeed, the other 2 produce this error (non scientific observation). For example, to get a directory listing I'll probably need to refresh 2 or so times before I get the listing. The other times I get that error. This began happening after my upgrade to KDE 4.3.2. I'm using 4.3.3 now, and the issue persists. I used kdebugdialog to get as much output as I could, but it's not very much: kate(8813)/kio (Slave) KIO::Slave::createSlave: createSlave "sftp" for KUrl("<removed>") kate(8813)/kio (KIOConnection) KIO::ConnectionServer::listenForRemote: Listening on "local:/tmp/ksocket-mrgrim/katecS8813.slave-socket" kate(8813)/kio (Slave) KIO::Slave::createSlave: createSlave "sftp" for KUrl("<removed>") kate(8813)/kio (KIOConnection) KIO::ConnectionServer::listenForRemote: Listening on "local:/tmp/ksocket-mrgrim/kateVs8813.slave-socket" kate(8813)/Kate (Document) KateView::slotGotFocus: KateView::slotGotFocus kate(8813)/kio (KIOJob) KIO::SlaveInterface::dispatch: error 151 "unexpected SFTP error: 1 Failed to execute ssh process."
kio_sftp has been rewritten for KDE 4.4. As it doesn't execute the ssh binary this bug is fixed in KDE 4.4.
That's great, and I'm genuinely happy to hear that. Two things to note are first, kde 4.4 is not released and second, kde 4.3 will be in use for quite some time as several distros are basing their next release on it. Lets not be so quick to abondon the current release. I've been trying to track this down, and I don't think the issue is with the execution of the ssh binary itself as it is with pty allocation or stdin/stdout redirection. The annoying part is useful tools like gdb or strace are useless here as pty allocation requires the execution of a setuid binary called pt_chown usually located in /usr/lib, and execve will not honor setuid when ptrace is in use (used by gdb and strace). I'm about to resort to littering ksshprocess.cpp and process.cpp with kDebug statements. Any help you can provide would be greatly appreciated.
Also, the error goes away when running as root (I tried that to get around the execve/setuid issue) so I think this is a permissions issue somewhere. This might even be a distro issue, but I don't have enough data to conclude either way yet.
I don't know this code, but it could be something else as the code hasn't changed afaik. SELinux?
(In reply to comment #4) > I don't know this code, but it could be something else as the code hasn't > changed afaik. > > SELinux? I'm running into the same problem in ArchLinux as well. SELinux is not enabled.
> This began happening after my upgrade to KDE 4.3.2. I'm using 4.3.3 now, and > the issue persists. I am getting the same error in KDE 4.3.3 as well using ArchLinux. A post in the KDE forums shows this appears to be happening in Fedora as well: http://forum.kde.org/viewtopic.php?f=22&t=81452 When I execute "dolphin sftp://some.server.com/" I get the following output in the console when SFTP fails: "/usr/bin/dolphin(2681)" Error in thread 140477430630240 : "Unsupported operation (2)": "Invalid model" "/usr/bin/dolphin(2681)" Error in thread 140477430630240 : "Unsupported operation (2)": "Invalid model" "/usr/bin/dolphin(2681)" Error in thread 140477430630240 : "Unsupported operation (2)": "Invalid model" "/usr/bin/dolphin(2681)" Error in thread 140477430630240 : "Invalid iterator." "/usr/bin/dolphin(2681)" Error in thread 140477430630240 : "Unsupported operation (2)": "Invalid model" "/usr/bin/dolphin(2681)" Error in thread 140477430630240 : "Unsupported operation (2)": "Invalid model" "/usr/bin/dolphin(2681)" Error in thread 140477430630240 : "Unsupported operation (2)": "Invalid model" "/usr/bin/dolphin(2681)" Error in thread 140477430630240 : "Invalid iterator." As mentioned in another post, this may be distro-specific, but a few pointers for where to look would be appreciated.
*** This bug has been marked as a duplicate of bug 214334 ***