From kde-bugs-dist  Sun Jul 16 22:24:00 2006
From: Lars Doelle <lars.doelle () on-line ! de>
Date: Sun, 16 Jul 2006 22:24:00 +0000
To: kde-bugs-dist
Subject: [Bug 105824] ctrl-d doesn't always work
Message-Id: <20060716222400.30044.qmail () ktown ! kde ! org>
X-MARC-Message: https://marc.info/?l=kde-bugs-dist&m=115308864527578

------- 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         




------- 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.
From the other side, one could attack it from the KonsoleBookmarkHandler's
side.

Since you are determined to help here, and you can reproduce the
problem within a day or so, we could try diagnose further. It might
take some tests.

Personally, i cannot help here further, since i do not know enough
to design a proper test for shortcut material. So we have to get to
the right expert here.

Kurt, do you know, who takes care of the shortcut stuff right now?
Perhaps the facts we found so far, might already resemble him
to something...

-lars

PS.

The sequences Ctrl-0 ... Ctrl-9 should result in '1'..'9'. Again, what
you see in the test program is what the konsole actually receives
as a keyevent. Actually, i'd consider the different values artefacts,
bugs, really, but they have nothing to do with our issue.