[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 105824] ctrl-d doesn't always work
From:       gdamjan () mail ! net ! mk
Date:       2006-07-13 0:37:34
Message-ID: 20060713003734.12075.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=105824         
gdamjan mail net mk changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |UNCONFIRMED
         Resolution|WORKSFORME                  |



------- Additional Comments From gdamjan mail net mk  2006-07-13 02:37 -------
> The problem is unlikely to be caused by the konsole.  It is not the
> konsole, that treats the ctrl-d different, but the client (program) resp.
> the program in connection with the line discipline. 

Lars, please see comment 2 and also comment 17 the part about using strace.
I'm fully aware that the application running inside Konsole is responsible for the \
doing something when ctrl-d is pressed. The problem is that nothing is sent to the \
application when konsole is in this "weird" state.

AND the problem IS localy reproduceable, because once Konsole enters the "weird" \
state, ctrl-d doesn't even work for new, local shell sessions but also for every \
other session!!! The ssh example given at the time is only because it seemed to \
trigger the weird behaviour most often.

ALSO, how do you explain that when konsole is in the "weird" state, ctrl-d does \
something with the bookmarks file, while when everything is normal ctrl-d in a shell \
just closes the shell and doesn't touch any bookmark files.

I understand that the problem is hard to reproduce, it doesn't happen very often to \
me too. BUT I spend a lot of time in Konsole, and my Konsole sessions are often very \
long lasting for several days and weeks, maybe even months, and eventually this \
"weird" behaviour would happen. Once I thought it only happened to me, but eventually \
it happened to a coleague of mine, and that's when I decided to file a bug.

As I said, if someone can leave me a  jabber contact I can arrange a VNC session, \
when this thing happens!


[prev in list] [next in list] [prev in thread] [next in thread]