Bug#1054227: /usr/bin/josm: Randomly stops processing hotkeys until mouse is clicked

Matija Nalis mnalis-debianbug at voyager.hr
Thu Oct 19 18:16:13 BST 2023


Package: josm
Version: 0.0.svn18822+dfsg-1~bpo12+1
Followup-For: Bug #1054227
X-Debbugs-Cc: mnalis-debianbug at voyager.hr


Still happens with bookworm-backports JOSM version.

See the screencast at https://mnalis.com/tmp/simplescreenrecorder-2023-10-19_18.35.02.mp4

(the issue happens even without screenkey and SimpleScreenRecoreder, of course, 
 there are in the video to show when I press the keys that they don't work anymore)

It seem main actors problem is F3 key for opening list of presets, but also other hotkeys that open separate window
(like ctrl-f for finding objects, or ctrl-h for history). Changing editing mode (e.g. 's' / 'a') even when pressed many 
times do not seem to trigger the problem.

You can note I remove previous JOSM directories and start fresh.
Issue happens both when dismissing presets window with "ESC" as well as with clicking cancel button.

I usually use icewm window manager (no any desktop environment); however I've reproduced the same problem in aewm++,
evilwm, flwm, fvwm3, lwm and icewm out of several that I tried, and the issue is reproducable in all of them (in some
even quicker; i.e. it blocks every time, not just every second or third or forth time as it does in icewm).

However, much to my surprise, I've found that the issue does not seem to happen (or at least happen much more rarely,
i.e. I can't easily reproduce it in ~30+ keypresses) in openbox, twm and i3 window managers!

All other apps (browser, video players, libreoffice etc) show no problem with any of the window managers.
I do not use any other java GUI apps, though.
Also, as noted before, even JOSM worked perfectly in Bullseye for years, and the bug only manifested itself in Bookworm.

Does that gives a clue? It seems like it might be some strange interaction between JOSM (or maybe java itself, that is,
some of its GUI components) and window managers?

Can you reproduce it with one of window managers above?
Anything else I could try to pinpoint it down?

-- System Information:
Debian Release: 12.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-13-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=hr_HR.UTF-8, LC_CTYPE=hr_HR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages josm depends on:
ii  default-jre [java9-runtime]     2:1.17-74
ii  fonts-noto                      20201225-1
ii  jmapviewer                      2.16+dfsg-2
ii  libcommons-compress-java        1.22-1
ii  libgettext-commons-java         0.9.6-6
ii  openjdk-17-jre [java9-runtime]  17.0.8+7-1~deb12u1
ii  openjfx                         11.0.11+1-3
ii  proj-data                       9.1.1-1

Versions of packages josm recommends:
pn  josm-l10n  <none>

josm suggests no packages.

-- no debconf information



More information about the Pkg-grass-devel mailing list