remote crash via ssh kills local machine

[meredrica]

If you connect to another machine via ssh and that machine crashes, the whole system just hangs. A few things like the taskswitcher and killing windows via alt+f4 still work, but most things don't.

It happened to me on 2 different computers both running on Kubuntu 9.10

ProblemType: Bug
Architecture: amd64
Date: Thu Dec 3 16:40:42 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/kdeinit4
NonfreeKernelModules: nvidia
Package: kdelibs-bin 4:4.3.2-0ubuntu7
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-15.50-generic
SourcePackage: kde4libs
Uname: Linux 2.6.31-15-generic x86_64
XsessionErrors: (polkit-gnome-authentication-agent-1:2601): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

[David (davidboy)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

[Colin Watson (cjwatson)]

How are you connecting to the other machine? If it's by ssh in a terminal, then this might be openssh's fault (although I have precisely no idea how; this just doesn't fit any reasonable model of how ssh works ...). However, I think it's more likely that you're using some KDE feature for connecting to other machines using the SSH protocol. The kioslave for sftp uses libssh rather than openssh, and in any case it seems likely that this would be a bug somewhere in the KIO subsystem in this case.

[Colin Watson (cjwatson)]

As described in my previous comment, I think this can only be a bug in the SFTP kioslave.

[Jonathan Thomas (echidnaman)]

We are closing this bug report because it lacks the information we need to investigate the problem, as requested in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the "Status" column, and change the status back to "New". Thanks again!

[Colin Watson (cjwatson)]

I don't see how it can be libssh's fault - surely the KIO system should be robust against individual slaves hanging! But whatever.