Version: 2.5.2 (using KDE 4.5.2)
When I mount a directory with sshfs from another computer and that computer loses the connection, konsole hangs up if i try to perform any commands in directories with the mounts in them.
1) sshfs piksi@otherhost:/home/piksi ~/Tempmount (otherhost is using wireless)
2) switch wireless off at otherhost
3) try ls ~ or cd Temp<tab> at localhost, konsole hangs
using a tty the mount is shown as:
D????????? ? ? ? ? Tempmount
I have to kill konsole completely because all tabs and the whole app just freeze when accessing a disabled mount. Otherwise KDE reports after a while that konsole is not responding.
Expected results: konsole should at least not hang and show the disabled mount the same way a normal tty does.
Confirm, KDE 4.4.5, Gentoo amd64 stable.
Also it hangs after using pm-suspend. You need to wait n minutes before waking up, if ssh did not disconnect our sshfs, ls will not hang konsole.
P.S. For me it is the most annoying konsole bug.
*** This bug has been confirmed by popular vote. ***
*** Bug 257639 has been marked as a duplicate of this bug. ***
I think the one that hangs is your shell or 'ls' command, not konsole. When that hang happens, I can still create new tab or close that frozen tab using konsole menu. Killing konsole is not necessary, indeed.
And that hang is not specific to konsole. The same thing happens for me in gnome-terminal, xfce4-terminal , xterm and tty console.
"I think the one that hangs is your shell or 'ls' command, not konsole."
For me, the freezes *don't* happen in a tty console, only in konsole (haven't tested other graphical terminals). I can continue working in a tty with no problems except for the broken mount.
"And that hang is not specific to konsole"
I wish you just had read my whole report. For me this hangs the whole console resulting in KDE reporting it as unresponsive. Your configuration and results might differ but it still doesn't change the fact that for me this is a real bug manifesting itself in konsole.
also, bug #257639 might provide specific steps to encounter this issue
*** This bug has been marked as a duplicate of bug 251351 ***