Bug 185817 - Konsole session/tab becomes unresponsive when connection to an ssh server interrupts
Summary: Konsole session/tab becomes unresponsive when connection to an ssh server int...
Status: RESOLVED DUPLICATE of bug 251351
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: 2.2
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords:
: 173783 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-02-28 18:46 UTC by Krenar Qehaja
Modified: 2011-08-03 08:00 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Krenar Qehaja 2009-02-28 18:46:20 UTC 
Version:           2.2 (using KDE 4.2.0)
OS:                Linux
Installed from:    Ubuntu Packages

Konsole session/tab becomes unresponsive when connection to an ssh server interrupts. It happens when changing networks, laptop suspend/resume or it happens after keeping the ssh session idle for a while (not interacting with the shell). It should disconnect but it rarely happens, most of the time it just hangs.

This bug might also relate to: https://bugs.kde.org/show_bug.cgi?id=185466

Thanks.
Comment 1 Pavel Reznicek 2009-08-11 13:16:39 UTC 
Hello, just one more, very mostly probably related issue with ssh. I have a profile that invokes ssh command at the startup. If I open a tab/window with such a profile, but then close it without typing the ssh password (typically if I accidentally choose a profile I didn't want), konsole (all windows and tabs) becomes totally unresponsive (and no new konsole windows can be opened) until the ssh command expires.
Comment 2 Kurt Hindenburg 2010-06-02 15:44:02 UTC 
*** Bug 173783 has been marked as a duplicate of this bug. ***
Comment 3 Otso Helenius 2011-07-20 17:08:08 UTC 
*** This bug has been confirmed by popular vote. ***
Comment 4 Jekyll Wu 2011-08-03 08:00:57 UTC 
Mark it as a duplicate of #251351, as they are both caused by broken ssh connection and that one contains clear steps to reproduce the problem.

*** This bug has been marked as a duplicate of bug 251351 ***