[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1022972: konsole: Konsole does not handle arrow keys correctly anymore



Followup-For: Bug #1022972
Package: konsole
Version: 4:22.08.1-1

Dear Maintainer,

I can confirm the pinentry and konsole issue, but I'll focus on konsole, even 
though I suspect they may share a root cause.

I found that konsole behaves correctly if I switch my keyboard layout to de 
nodeadkeys or us. If I use my normal layout Neo2 (`setxkbmap de neo`), the 
incorrect behaviour occurs.

This can be traced down to the keyboard configuration of konsole. When going 
to: Edit Current Profile... -> Keyboard -> Default (XFree 4) -> Edit...

and then using the "input" field for testing, it can be observed that for the 
arrow up key, different rules trigger depending on the keyboard layout:

Layout   Rule                                     Escape Sequence
de neo   Up-Shift+Ansi+AnyModifier                \E[1;1A
us       Up-Shift+Ansi-AppCursorKeys-AnyModifier  \E[A

The former escape sequence is not recognized by my shell (zsh) or by many 
other applications. This affects other keys, too (e.g. End, Home, and function 
keys). Ctrl+Arrow keys work fine, generating a \E[1;5A sequence for Ctrl+Up, 
which is identical between both layouts.

It seems to me as if neo2 somehow causes konsole (or potentially all of Qt, 
looking at the pinentry thing) to assume some unnamed modifier to be active at 
all times.

Max, Nathanael, could you confirm that you're too using Neo2, or similarly 
"exotic" layouts? Otherwise we're probably looking at different issues.

kind regards,
Jonas Schäfer

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.0.0-2-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages konsole depends on:
ii  kio                    5.98.0-1
ii  konsole-kpart          4:22.08.1-1
ii  libc6                  2.35-4
ii  libkf5configcore5      5.98.0-2
ii  libkf5configwidgets5   5.98.0-1
ii  libkf5coreaddons5      5.98.0-1
ii  libkf5crash5           5.98.0-1
ii  libkf5dbusaddons5      5.98.0-1
ii  libkf5globalaccel-bin  5.98.0-1
ii  libkf5globalaccel5     5.98.0-1
ii  libkf5guiaddons5       5.98.0-2
ii  libkf5i18n5            5.98.0-1+b1
ii  libkf5kiowidgets5      5.98.0-1
ii  libkf5notifyconfig5    5.98.0-1
ii  libkf5service-bin      5.98.0-1
ii  libkf5service5         5.98.0-1
ii  libkf5widgetsaddons5   5.98.0-1
ii  libkf5windowsystem5    5.98.0-1
ii  libkf5xmlgui5          5.98.0-1+b1
ii  libqt5core5a           5.15.6+dfsg-2
ii  libqt5gui5             5.15.6+dfsg-2
ii  libqt5widgets5         5.15.6+dfsg-2
ii  libstdc++6             12.2.0-3

konsole recommends no packages.

Versions of packages konsole suggests:
pn  lrzsz  <none>

-- no debconf information


Reply to: