Bug#904009: reportbug: Backspace, arrow keys and more thing like ctrl+c are not working in some programs
Package: reportbug Version: 7.5.0 Severity: normal In some programs like Filezilla or PhotoFilmStrip, partially in some CodeBlocks, dialogs some keys are plain not working. Also happens in fresh installed systems using buster / debian mate. Affected are in any case: backspace, arrow keys and shortcuts like ctrl+c and ctrl+v. -- Package-specific info: ** Environment settings: INTERFACE="gtk2" ** /home/smir/.reportbugrc: reportbug_version "7.1.10" mode advanced ui gtk2 email "develo...@oldunreal.com" smtphost "mail.masterlogin.de" smtpuser "develo...@oldunreal.com" smtptls -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.16.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages reportbug depends on: ii apt1.6.3 ii python33.6.5-3 ii python3-reportbug 7.5.0 ii sensible-utils 0.0.12 reportbug recommends no packages. Versions of packages reportbug suggests: pn claws-mail pn debconf-utils pn debsums pn dlocate pn emacs24-bin-common | emacs25-bin-common ii exim4-daemon-light [mail-transport-agent] 4.91-5 ii file 1:5.33-3 ii gnupg 2.2.8-3 pn python3-urwid pn reportbug-gtk ii xdg-utils 1.1.3-1 Versions of packages python3-reportbug depends on: ii apt1.6.3 ii file 1:5.33-3 ii python33.6.5-3 ii python3-apt1.6.2 ii python3-debian 0.1.32 ii python3-debianbts 2.7.2 ii python3-requests 2.18.4-2 python3-reportbug suggests no packages. -- no debconf information
Bug#895123: libsdl2-2.0-0: This is normally a bug in some application using the D-Bus library.
Package: libsdl2-2.0-0 Version: i386 Severity: important -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.15.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#895121: bugs.debian.org: SDL2 won't get keyboard key release state since update to Buster
Package: bugs.debian.org Severity: normal Trying to use debian libsdl2-2.0-0:i386 is giving me: dbus[27552]: arguments to dbus_message_new_method_call() were incorrect, assertion "path != NULL" failed in file ../../../dbus/dbus-message.c line 1362. This is normally a bug in some application using the D-Bus library. (reported in another bug report) However, using a self compiled SDL2 library (i386) produces an odd problem, it appears that sometimes a key release is plain not noticed by SDL2, neither in SDL_KEYUP nor with SDL_GetKeyboardState. This problem did not happen in Stretch and does not happen in some other distro like OpenSuSE using the same application and/or SDL2 library. Was able to reproduce this behavior on 2 machines running Buster. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.15.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
