Bug 251351

*** Bug 252232 has been marked as a duplicate of this bug. ***

possibly a duplicate of #256301

*** Bug 256301 has been marked as a duplicate of this bug. ***

*** Bug 185817 has been marked as a duplicate of this bug. ***

*** Bug 177077 has been marked as a duplicate of this bug. ***

I've seen this happen without ssh, but haven't figured out how to reproduce it. Latest time it happened, I typed "ls" in one konsole and switched to another virtual desktop. I got a truss trace (BSD equivalent of strace) in another konsole, running as another user, where I am su'ed to root:

lseek(20,0x3000,0)                               = 12288 (0x3000)
read(0x14,0x2a31f000,0x1000)                     = 4096 (0x1000)
lseek(20,0x1000,0)                               = 4096 (0x1000)
read(0x14,0x2a31b000,0x1000)                     = 4096 (0x1000)
close(20)                                        = 0 (0x0)
munmap(0x2ce9c000,0x4000)                        = 0 (0x0)
__sysctl(0xbfbfe540,0x4,0xbfbbe540,0xbfbfe558,0x0,0x0) = 0 (0x0)
__sysctl(0xbfbfe548,0x4,0x0,0xbfbfe55c,0x0,0x0)  = 0 (0x0)
__sysctl(0xbfbfe548,0x4,0x2a0ec240,0xbfbfe55c,0x0,0x0) = 0 (0x0)
mmap(0x0,16384,0x3,0x1002,-1,0x0)                = 753516544 (0x2ce9c000)
stat("/etc/nsswitch.conf",0xbfbfe388)            = 0 (0x0)
geteuid()                                        = 1021 (0x3fd)
stat("/etc/pwd.db",0xbfbfe168)                   = 0 (0x0)
open("/etc/pwd.db",0x0,00)                       = 20 (0x14)
fcntl(0x14,0x2,0x1)                              = 0 (0x0)
read(0x14,0x2ef91160,0x104)                      = 260 (0x104)
lseek(20,0x6000,0)                               = 24576 (0x6000)
read(0x14,0x2a319000,0x1000)                     = 4096 (0x1000)
lseek(20,0x4000,0)                               = 16384 (0x4000)
read(0x14,0x2a31b000,0x1000)                     = 4096 (0x1000)
lseek(20,0x5000,0)                               = 20480 (0x5000)
read(0x14,0x2a31d000,0x1000)                     = 4096 (0x1000)
lseek(20,0x7000,0)                               = 28672 (0x7000)
read(0x14,0x2a316000,0x1000)                     = 4096 (0x1000)
lseek(20,0x8000,0)                               = 32768 (0x8000)
read(0x14,0x2a314000,0x1000)                     = 4096 (0x1000)
lseek(20,0xd000,0)                               = 53248 (0xd000)
read(0x14,0x2f8a1000,0x1000)                     = 4096 (0x1000)
lseek(20,0x2000,0)                               = 8192 (0x2000)
read(0x14,0x2a312000,0x1000)                     = 4096 (0x1000)
lseek(20,0x3000,0)                               = 12288 (0x3000)
read(0x14,0x2a31f000,0x1000)                     = 4096 (0x1000)
lseek(20,0x1000,0)                               = 4096 (0x1000)
read(0x14,0x2a31c000,0x1000)                     = 4096 (0x1000)
close(20)                                        = 0 (0x0)
munmap(0x2ce9c000,0x4000)                        = 0 (0x0)
__sysctl(0xbfbfe540,0x4,0xbfbbe540,0xbfbfe558,0x0,0x0) = 0 (0x0)
__sysctl(0xbfbfe548,0x4,0x0,0xbfbfe55c,0x0,0x0)  = 0 (0x0)
__sysctl(0xbfbfe548,0x4,0x2a0ec240,0xbfbfe55c,0x0,0x0) = 0 (0x0)
mmap(0x0,16384,0x3,0x1002,-1,0x0)                = 753516544 (0x2ce9c000)
stat("/etc/nsswitch.conf",0xbfbfe388)            = 0 (0x0)
geteuid()                                        = 1021 (0x3fd)
stat("/etc/pwd.db",0xbfbfe168)                   = 0 (0x0)
open("/etc/pwd.db",0x0,00)                       = 20 (0x14)
fcntl(0x14,0x2,0x1)                              = 0 (0x0)

Moving nsswitch.conf had no effect other than changing the output of the stat command. Sending konsole an ALRM signal results in its death.

DragonFly v2.11.0.681.g0eed2f-DEVELOPMENT
Konsole 2.5.4
KDE 4.5.5

*** Bug 296903 has been marked as a duplicate of this bug. ***

*** Bug 297899 has been marked as a duplicate of this bug. ***

*** Bug 279133 has been marked as a duplicate of this bug. ***

Git commit 1ce424142f1ee31a25cbb9398c79df9d98d81d71 by Kurt Hindenburg.
Committed on 18/06/2012 at 14:56.
Pushed by hindenburg into branch 'master'.

Use readlink instead of QFileInfo to prevent non-responsive issues.

The current code using QFileInfo on the /proc/%pid/cwd and for some
situations, this may cause issues as QFileInfo hangs if unable to read that
file.  The new code uses readlink which appears to work w/o issue.

The Solaris  code needs fixed as well.

M  +16   -12   src/ProcessInfo.cpp

http://commits.kde.org/konsole/1ce424142f1ee31a25cbb9398c79df9d98d81d71

This bug was also reported in the Red Hat Bugzilla for Fedora 16 on https://bugzilla.redhat.com/show_bug.cgi?id=794974 .

This bug still exists on the latest gentoo packages.
If the ssh connection is lost, we cannot input anything in the konsole tab. 
If waiting long enough (a couple of hours?), then some timeout appears to kick in and a message "connection lost" is displayed and only then can we type anything (e.g. type 'exit' to close the tab).

How to reproduce:
https://bugs.kde.org/show_bug.cgi?id=185466#c2

2) ssh to a server in one tab (lets say tab A)
3) Disconnect the connection abruptly (turn off the wireless/network)
4) Now the tab A will be frozen, no keys will work (it should be a bug i think). But the right click context menu will work !
5) Close tab A. A confirmation dialog box with a warning message will appear "The program 'ssh' is currently running in this session.  Are you sure you want to close it?"

After about one hour of the tab with the  ssh process being frozen, this was output: 
 packet_write_wait: Connection to nnn.nnn.nnn.nnn port nnnn: Broken pipe
and control was restored.

Why would the ssh be broken (broken pipe) in the first place?

This is still an issue on git master.

I can't even kill the konsole process with ksysguard.

This issue still exists on Konsole 21.12.2.

let us know if you still have this issue on a recent version

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Problem still persists on Konsole 24.02.1:

1. Log in using SSH
2. Kill the connection
3. Although Konsole is active, the terminal itself is not available for new commands. The only way to be able to further use the Konsole window is by creating a new tab and killing the SSH tab.

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!