Bug 252232

Summary: Hanging konsole instance affects other instances
Product: [Applications] konsole Reporter: Robert Gomulka <rgom.debian>
Component: generalAssignee: Konsole Bugs <konsole-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: k.kapuscik
Priority: NOR    
Version First Reported In: 2.5   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Robert Gomulka 2010-09-24 11:42:08 UTC 
Version:           2.5 (using KDE 4.5.0) 
OS:                Linux

I use some proprietary FUSE libs with big timeouts. When accessing specific directory waits for timeout, konsole instance looks frozen (no output, no possibility to enter text, no possibility to work in any tab). That's understandable.
But ... I have launched second konsole instance, with hope that it will be independent. But, unfortunately, frozen (hanging) first konsole instance causes second one to hang as well.

Reproducible: Always

Steps to Reproduce:
1. Launch FUSE daemon with big timeouts
2. Launch two konsole instances
3. Enter a directory which causes FUSE to wait for timeout in first konsole instance
4. Try to use other konsole instance

Actual Results:  
It's impossible to use any konsole instance.

Expected Results:  
It should be possible to use at least second console instance or even better any other tabs from first instance.
Comment 1 Robert Gomulka 2010-09-24 11:52:19 UTC 
I have just noticed that this is somehow related to mc (Midnight Commander).
When I launched third konsole instance, I could use it. But I couldn't launch
mc from within it (hanging). On the other hand, I could launch mc from xterm
with no problems.
Comment 2 Robert Gomulka 2010-09-24 19:50:27 UTC 
Is this a duplicate of 251351?
Comment 3 Kurt Hindenburg 2011-03-04 19:48:20 UTC 

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