[Konsole-devel] [Bug 105824] ctrl-d doesn't always work

[Lars Doelle]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=105824         




------- Additional Comments From lars.doelle on-line de  2006-07-17 00:23 -------
gdamjan, Kurt,

in the moment, i must admit, that i'm through with my latin.

My diagnosis so far is to assume that something in the
earlier keyboard pipeline is broken.

If you don't get a ctrl-d through to the test program, it is likely
that the konsole's key processing itself does not receive it.

The key events are received in
bool TEWidget::eventFilter( QObject *obj, QEvent *e )
and routed there via 'emit keyPressedSignal(ke)' to
void TEmuVt102::onKeyPress( QKeyEvent* ev ),
and finally written to the pty.

One could add an extra diagnostic into the konsole code to
verify it, but i would assume this is true from your test. Any other
conclusion should have an effect on other keys, too.

The problem is, that i do not know how the earlier key event
processing functions, i.e. which filters are applied earlier in
the pipeline.

That the cntl-d somehow ends in the konsole-bookmark procedures,
which has been demonstrated by an ptrace in one of your earlier
posts supports this diagnosis.

Likely, that no other konsoles and programs are affected in this
state unburdens other programs e.g. the window manager, running
on the same desktop.

Thus, i would localise the origin of the effect somewhere in the
shortcut handling in the konsole. If this is the origin, too, remains
to be seen. This bug might well be one that occurs far from its
origin.

This means we would have to consider library material here.