Bug#928046: dosbox: input issues under Wayland (some keys not behaving)

2023-07-21 Thread Patrick Frank
Package: dosbox
X-Debbugs-Cc: foss.conn...@kaffeeschluerfer.com
Version: 0.74-3-4+b1
Severity: normal

Hello,

it is true that the config option "usescancodes=false" affects the problem
of keys not functioning as expected, but only by ~50% in combination with
"keyboardlayout=de". You can get only one of both halfs of the special
keys. Very curious for me - either you get the ":" char or the arrow keys
and the "-" char. So it locks me out of several use cases. At least when
you install / configure they keyboard layout "German" and the system
language "English".


-- System Information:

Debian Release: 12.0
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages dosbox depends on:
ii  libasound2   1.2.8-1+b1
ii  libc62.36-9
ii  libgcc-s112.2.0-14
ii  libgl1   1.6.0-1
ii  libpng16-16  1.6.39-2
ii  libsdl-net1.21.2.8-6+b1
ii  libsdl-sound1.2  1.0.3-9+b2
ii  libsdl1.2debian  1.2.15+dfsg2-8
ii  libstdc++6   12.2.0-14
ii  libx11-6 2:1.8.4-2+deb12u1
ii  zlib1g   1:1.2.13.dfsg-1



Bug#928046: ~ Re: Bug#928046: dosbox: input issues under Wayland (some keys not behaving)

2019-05-12 Thread Jonathan Dowland

Hi all

On Sat, May 11, 2019 at 11:36:00AM +, Niels Thykier wrote:

Have you tried Stephen's suggestion of setting "usescancodes" and see if
that fixes the issue?


I hadn't, until now, but I can now confirm that this does resolve the issue.


Thanks,

--

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Jonathan Dowland
⢿⡄⠘⠷⠚⠋⠀ https://jmtd.net
⠈⠳⣄



Bug#928046: dosbox: input issues under Wayland (some keys not behaving)

2019-05-11 Thread Niels Thykier
On Fri, 26 Apr 2019 23:14:59 +0200 Stephen Kitt  wrote:
> Hi Jonathan,
> 
> On Fri, 26 Apr 2019 20:05:34 +0100, Jonathan Dowland  wrote:
> > Under GNOME/Wayland, when I launch DOOM2.EXE under DOSBOX, the arrow keys
> > are not recognised. Other keys are (ESC in particular works) and I can type
> > alphanumeric keys w/o error. DOOM relies upon raw keyboard input from DOS.
> > 
> > Logging into GNOME/Xorg and the problem goes away.
> 
> Thanks for the bug report. Does setting
> 
>   usescancodes=false
> 
> in dosbox-0.74-2.conf help?
> 
> Regards,
> 
> Stephen

Hi Jonathan,

Have you tried Stephen's suggestion of setting "usescancodes" and see if
that fixes the issue?

Thanks,
~Niels



Bug#928046: dosbox: input issues under Wayland (some keys not behaving)

2019-04-26 Thread Stephen Kitt
Hi Jonathan,

On Fri, 26 Apr 2019 20:05:34 +0100, Jonathan Dowland  wrote:
> Under GNOME/Wayland, when I launch DOOM2.EXE under DOSBOX, the arrow keys
> are not recognised. Other keys are (ESC in particular works) and I can type
> alphanumeric keys w/o error. DOOM relies upon raw keyboard input from DOS.
> 
> Logging into GNOME/Xorg and the problem goes away.

Thanks for the bug report. Does setting

usescancodes=false

in dosbox-0.74-2.conf help?

Regards,

Stephen


pgp78jAdRj__H.pgp
Description: OpenPGP digital signature


Bug#928046: dosbox: input issues under Wayland (some keys not behaving)

2019-04-26 Thread Jonathan Dowland
Package: dosbox
Version: 0.74-2-3
Severity: normal

Under GNOME/Wayland, when I launch DOOM2.EXE under DOSBOX, the arrow keys are
not recognised. Other keys are (ESC in particular works) and I can type
alphanumeric keys w/o error. DOOM relies upon raw keyboard input from DOS.

Logging into GNOME/Xorg and the problem goes away.

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-debug'), (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages dosbox depends on:
ii  libasound2   1.1.8-1
ii  libc62.28-8
ii  libgcc1  1:8.3.0-6
ii  libgl1   1.1.0-1
ii  libpng16-16  1.6.36-5
ii  libsdl-net1.21.2.8-6
ii  libsdl-sound1.2  1.0.3-9
ii  libsdl1.2debian  1.2.15+dfsg2-4
ii  libstdc++6   8.3.0-6
ii  libx11-6 2:1.6.7-1
ii  zlib1g   1:1.2.11.dfsg-1

dosbox recommends no packages.

dosbox suggests no packages.

-- no debconf information
# This is the configurationfile for DOSBox 0.74. (Please use the latest version 
of DOSBox)
# Lines starting with a # are commentlines and are ignored by DOSBox.
# They are used to (briefly) document the effect of each option.

[sdl]
#   fullscreen: Start dosbox directly in fullscreen. (Press ALT-Enter to go 
back)
#   fulldouble: Use double buffering in fullscreen. It can reduce screen 
flickering, but it can also result in a slow DOSBox.
#   fullresolution: What resolution to use for fullscreen: original or fixed 
size (e.g. 1024x768).
# Using your monitor's native resolution with aspect=true 
might give the best results.
# If you end up with small window on a large screen, try an 
output different from surface.
# windowresolution: Scale the window to this size IF the output device supports 
hardware scaling.
# (output=surface does not!)
#   output: What video system to use for output.
#   Possible values: surface, overlay, opengl, openglnb.
# autolock: Mouse will automatically lock, if you click on the screen. 
(Press CTRL-F10 to unlock)
#  sensitivity: Mouse sensitivity.
#  waitonerror: Wait before closing the console if dosbox has an error.
# priority: Priority levels for dosbox. Second entry behind the comma 
is for when dosbox is not focused/minimized.
# pause is only valid for the second entry.
#   Possible values: lowest, lower, normal, higher, highest, 
pause.
#   mapperfile: File used to load/save the key/event mappings from. 
Resetmapper only works with the defaul value.
# usescancodes: Avoid usage of symkeys, might not work on all operating 
systems.

fullscreen=false
fulldouble=true
fullresolution=original
windowresolution=1024x768
output=opengl
autolock=true
sensitivity=100
waitonerror=true
priority=higher,normal
mapperfile=mapper-0.74.map
usescancodes=true

[dosbox]
# language: Select another language file.
#  machine: The type of machine tries to emulate.
#   Possible values: hercules, cga, tandy, pcjr, ega, vgaonly, svga_s3, 
svga_et3000, svga_et4000, svga_paradise, vesa_nolfb, vesa_oldvbe.
# captures: Directory where things like wave, midi, screenshot get captured.
#  memsize: Amount of memory DOSBox has in megabytes.
# This value is best left at its default to avoid problems with 
some games,
# though few games might require a higher value.
# There is generally no speed advantage when raising this value.

language=
machine=svga_s3
captures=capture
memsize=16

[render]
# frameskip: How many frames DOSBox skips before drawing one.
#aspect: Do aspect correction, if your output method doesn't support 
scaling this can slow things down!.
#scaler: Scaler used to enlarge/enhance low resolution modes.
#  If 'forced' is appended, then the scaler will be used even if 
the result might not be desired.
#Possible values: none, normal2x, normal3x, advmame2x, advmame3x, 
advinterp2x, advinterp3x, hq2x, hq3x, 2xsai, super2xsai, supereagle, tv2x, 
tv3x, rgb2x, rgb3x, scan2x, scan3x.

frameskip=0
aspect=false
scaler=normal2x

[cpu]
#  core: CPU Core used in emulation. auto will switch to dynamic if 
available and appropriate.
#Possible values: auto, dynamic, normal, simple.
#   cputype: CPU Type used in emulation. auto is the fastest choice.
#Possible values: auto, 386, 386_slow, 486_slow, pentium_slow, 
386_prefetch.
#cycles: Amount of instructions DOSBox tries to emulate each millisecond.
#Setting this value too high results in sound dropouts and lags.
#Cycles can be set in 3 ways:
#