Re: devel/sdl2 bug since update to 2.0.5
On Sun, May 14, 2017 at 12:50:16PM -0700, Ryan Freeman wrote:
> On Sun, May 14, 2017 at 12:42:34PM -0700, Ryan Freeman wrote:
> > On Fri, Dec 02, 2016 at 10:46:32AM -0800, Ryan Freeman wrote:
> > > I wish I had noticed this sooner when the update was posted...
> > >
> > > For whatever reason, certain applications with SDL2 2.0.5 are receving
> > > duplicate keyboard events. Mouse seems unaffected, but the menus of some
> > > games are very hard to navigate.
> > >
> > > If the Esc key opens a menu, instead what happens is it opens and closes
> > > before you can do anything. If you happen to be in a menu, arrow keys
> > > for navigation move the selector up or down two spaces at a time. Trying
> > > to open a console, would make it open and close immediately as well.
> > >
> > > Gameplay-type keys would work normally in my testing.
> > >
> > > games/quakespasm shows this problem. I haven't found others just yet that
> > > are in ports, but it was while checking the SDL2 branch of chocolate-doom
> > > currently in development that led me to this discovery.
> > > Initially thought it was just a local problem with that project until i
> > > duplicated it also with doomretro (not in ports,
> > > http://github.com/bradharding/doomretro) and quakespasm.
> > >
> > > My workstation at work still has a snapshot from Nov 8th, running SDL2
> > > 2.0.4.
> > > As a result I can't reproduce the issue here.
> > >
> > > My workstation at home ran a snapshot from Nov 17th when I found the
> > > problem.
> > > I updated it to Dec 1 snapshot and verified the problem still exists.
> > >
> > > I found this post in the SDL2 changelog:
> > > http://hg.libsdl.org/SDL/rev/aea47b61c640
> > > ...and wondered if it was somehow related. I manually reverted this patch
> > > and gave it a go, but the problem persists.
> > >
> > > Has anyone else noticed duplicated key events in SDL2 programs? Any other
> > > examples? I am not sure where to look, but don't want to keep this to
> > > myself
> > > for too long...
> >
> >
> > FWIW, I finally found a solution for this. The problem only happened for me
> > when using Gnome3 and SDL2 games, any other window manager was fine. So I
> > had stopped using Gnome3.
> >
> > But, I wasn't the only one :D
> >
> > Lazy perusing the problem description led me here:
> > https://bbs.archlinux.org/viewtopic.php?id=219751
> >
> > Which led here:
> > https://github.com/spurious/SDL-mirror/commit/2468785f0ac318a1afd0e6ad08b8d2a7d65a42a6
> >
> > Which led to creating this patch for our sdl2. after applying and upgrading
> > the sdl2 package, all affected programs above are no-longer affected.
> > Without
> > rebuilding any of them, either.
> >
> > Can we slip this in for now until (hopefully) sdl2-2.0.6 arrives?
> >
> > Cheers!
> > -ryan
>
> I screwed up the patch somehow, sorry. fixed patch.
>
Bah, premature celebration. While this patch at least removes
duplicate events to menus and such, it actually eats some events in
other situations. So sometimes in a quakespasm or yquake2 game,
a movement key gets stuck 'on' until it is pressed again.
Stranger still, in yquake2 i can't open the console at all anymore,
and in quakespasm the console opens but no keypresses are registered...
except when i flutter the shift keys while hitting the key I want.
Seems like it needs to be flooded with enough key events before it
actually accepts the input. Needless to say it took awhile to
type 'quit' ;)
I will keep nosing around this though, or perhaps try a more current
checkout of sdl2 altogether to see if I can at least expect to see
SDL2 + gnome3 + radeon graphics to have this key issue resolved finally.
>
> ? sdl2_duplicate_event_fix.diff
> Index: Makefile
> ===
> RCS file: /cvs/ports/devel/sdl2/Makefile,v
> retrieving revision 1.16
> diff -u -p -r1.16 Makefile
> --- Makefile 14 May 2017 06:40:35 - 1.16
> +++ Makefile 14 May 2017 19:46:46 -
> @@ -4,7 +4,7 @@ COMMENT= cross-platform multimedia libra
> BROKEN-hppa= src/atomic/SDL_spinlock.c:101:2: error: \#error Please
> implement for your platform.
>
> V= 2.0.5
> -REVISION=0
> +REVISION=1
> DISTNAME=SDL2-${V}
> PKGNAME= sdl2-${V}
> CATEGORIES= devel
> Index: patches/patch-src_video_x11_SDL_x11events_c
> ===
> RCS file: patches/patch-src_video_x11_SDL_x11events_c
> diff -N patches/patch-src_video_x11_SDL_x11events_c
> --- /dev/null 1 Jan 1970 00:00:00 -
> +++ patches/patch-src_video_x11_SDL_x11events_c 14 May 2017 19:46:46
> -
> @@ -0,0 +1,24 @@
> +$OpenBSD$
> +
> +Index: src/video/x11/SDL_x11events.c
> +--- src/video/x11/SDL_x11events.c.orig
> src/video/x11/SDL_x11events.c
> +@@ -571,12 +571,18 @@ X11_DispatchEvent(_THIS)
> + if (orig_keycode) {
> + /* Make sure dead key press/release events are sent */
> +
Re: devel/sdl2 bug since update to 2.0.5
On Fri, Dec 02, 2016 at 10:46:32AM -0800, Ryan Freeman wrote:
> I wish I had noticed this sooner when the update was posted...
>
> For whatever reason, certain applications with SDL2 2.0.5 are receving
> duplicate keyboard events. Mouse seems unaffected, but the menus of some
> games are very hard to navigate.
>
> If the Esc key opens a menu, instead what happens is it opens and closes
> before you can do anything. If you happen to be in a menu, arrow keys
> for navigation move the selector up or down two spaces at a time. Trying
> to open a console, would make it open and close immediately as well.
>
> Gameplay-type keys would work normally in my testing.
>
> games/quakespasm shows this problem. I haven't found others just yet that
> are in ports, but it was while checking the SDL2 branch of chocolate-doom
> currently in development that led me to this discovery.
> Initially thought it was just a local problem with that project until i
> duplicated it also with doomretro (not in ports,
> http://github.com/bradharding/doomretro) and quakespasm.
>
> My workstation at work still has a snapshot from Nov 8th, running SDL2 2.0.4.
> As a result I can't reproduce the issue here.
>
> My workstation at home ran a snapshot from Nov 17th when I found the problem.
> I updated it to Dec 1 snapshot and verified the problem still exists.
>
> I found this post in the SDL2 changelog:
> http://hg.libsdl.org/SDL/rev/aea47b61c640
> ...and wondered if it was somehow related. I manually reverted this patch
> and gave it a go, but the problem persists.
>
> Has anyone else noticed duplicated key events in SDL2 programs? Any other
> examples? I am not sure where to look, but don't want to keep this to myself
> for too long...
FWIW, I finally found a solution for this. The problem only happened for me
when using Gnome3 and SDL2 games, any other window manager was fine. So I
had stopped using Gnome3.
But, I wasn't the only one :D
Lazy perusing the problem description led me here:
https://bbs.archlinux.org/viewtopic.php?id=219751
Which led here:
https://github.com/spurious/SDL-mirror/commit/2468785f0ac318a1afd0e6ad08b8d2a7d65a42a6
Which led to creating this patch for our sdl2. after applying and upgrading
the sdl2 package, all affected programs above are no-longer affected. Without
rebuilding any of them, either.
Can we slip this in for now until (hopefully) sdl2-2.0.6 arrives?
Cheers!
-ryan
? sdl2_duplicate_event_fix.diff
Index: Makefile
===
RCS file: /cvs/ports/devel/sdl2/Makefile,v
retrieving revision 1.16
diff -u -p -r1.16 Makefile
--- Makefile14 May 2017 06:40:35 - 1.16
+++ Makefile14 May 2017 19:35:03 -
@@ -4,7 +4,7 @@ COMMENT=cross-platform multimedia libra
BROKEN-hppa= src/atomic/SDL_spinlock.c:101:2: error: \#error Please
implement for your platform.
V= 2.0.5
-REVISION= 0
+REVISION= 1
DISTNAME= SDL2-${V}
PKGNAME= sdl2-${V}
CATEGORIES=devel
Index: patches/patch-src_video_x11_SDL_x11events_c
===
RCS file: patches/patch-src_video_x11_SDL_x11events_c
diff -N patches/patch-src_video_x11_SDL_x11events_c
--- /dev/null 1 Jan 1970 00:00:00 -
+++ patches/patch-src_video_x11_SDL_x11events_c 14 May 2017 19:35:03 -
@@ -0,0 +1,24 @@
+$OpenBSD$
+
+Index: src/video/x11/SDL_x11events.c
+--- src/video/x11/SDL_x11events.c.orig
src/video/x11/SDL_x11events.c
+@@ -571,12 +571,18 @@ X11_DispatchEvent(_THIS)
+ if (orig_keycode) {
+ /* Make sure dead key press/release events are sent */
+ SDL_Scancode scancode = videodata->key_layout[orig_keycode];
++ videodata->filter_code = orig_keycode;
++ videodata->filter_time = xevent.xkey.time;
++
+ if (orig_event_type == KeyPress) {
+ SDL_SendKeyboardKey(SDL_PRESSED, scancode);
+ } else {
+ SDL_SendKeyboardKey(SDL_RELEASED, scancode);
+ }
+ }
++return;
++} else if (orig_keycode == videodata->filter_code && xevent.xkey.time ==
videodata->filter_time) {
++/* This is a duplicate event, resent by an IME - skip it. */
+ return;
+ }
+
Index: patches/patch-src_video_x11_SDL_x11video_h
===
RCS file: patches/patch-src_video_x11_SDL_x11video_h
diff -N patches/patch-src_video_x11_SDL_x11video_h
--- /dev/null 1 Jan 1970 00:00:00 -
+++ patches/patch-src_video_x11_SDL_x11video_h 14 May 2017 19:35:03 -
@@ -0,0 +1,16 @@
+$OpenBSD$
+
+Index: src/video/x11/SDL_x11video.h
+--- src/video/x11/SDL_x11video.h.orig
src/video/x11/SDL_x11video.h
+@@ -133,10 +133,6 @@ typedef struct SDL_VideoData
+ #if SDL_VIDEO_DRIVER_X11_HAS_XKBKEYCODETOKEYSYM
+ XkbDescPtr xkb;
+ #endif
++
++KeyCode filter_code;
++Timefilter_time;
++
+ }
Re: devel/sdl2 bug since update to 2.0.5
On Sun, May 14, 2017 at 12:42:34PM -0700, Ryan Freeman wrote:
> On Fri, Dec 02, 2016 at 10:46:32AM -0800, Ryan Freeman wrote:
> > I wish I had noticed this sooner when the update was posted...
> >
> > For whatever reason, certain applications with SDL2 2.0.5 are receving
> > duplicate keyboard events. Mouse seems unaffected, but the menus of some
> > games are very hard to navigate.
> >
> > If the Esc key opens a menu, instead what happens is it opens and closes
> > before you can do anything. If you happen to be in a menu, arrow keys
> > for navigation move the selector up or down two spaces at a time. Trying
> > to open a console, would make it open and close immediately as well.
> >
> > Gameplay-type keys would work normally in my testing.
> >
> > games/quakespasm shows this problem. I haven't found others just yet that
> > are in ports, but it was while checking the SDL2 branch of chocolate-doom
> > currently in development that led me to this discovery.
> > Initially thought it was just a local problem with that project until i
> > duplicated it also with doomretro (not in ports,
> > http://github.com/bradharding/doomretro) and quakespasm.
> >
> > My workstation at work still has a snapshot from Nov 8th, running SDL2
> > 2.0.4.
> > As a result I can't reproduce the issue here.
> >
> > My workstation at home ran a snapshot from Nov 17th when I found the
> > problem.
> > I updated it to Dec 1 snapshot and verified the problem still exists.
> >
> > I found this post in the SDL2 changelog:
> > http://hg.libsdl.org/SDL/rev/aea47b61c640
> > ...and wondered if it was somehow related. I manually reverted this patch
> > and gave it a go, but the problem persists.
> >
> > Has anyone else noticed duplicated key events in SDL2 programs? Any other
> > examples? I am not sure where to look, but don't want to keep this to
> > myself
> > for too long...
>
>
> FWIW, I finally found a solution for this. The problem only happened for me
> when using Gnome3 and SDL2 games, any other window manager was fine. So I
> had stopped using Gnome3.
>
> But, I wasn't the only one :D
>
> Lazy perusing the problem description led me here:
> https://bbs.archlinux.org/viewtopic.php?id=219751
>
> Which led here:
> https://github.com/spurious/SDL-mirror/commit/2468785f0ac318a1afd0e6ad08b8d2a7d65a42a6
>
> Which led to creating this patch for our sdl2. after applying and upgrading
> the sdl2 package, all affected programs above are no-longer affected. Without
> rebuilding any of them, either.
>
> Can we slip this in for now until (hopefully) sdl2-2.0.6 arrives?
>
> Cheers!
> -ryan
I screwed up the patch somehow, sorry. fixed patch.
? sdl2_duplicate_event_fix.diff
Index: Makefile
===
RCS file: /cvs/ports/devel/sdl2/Makefile,v
retrieving revision 1.16
diff -u -p -r1.16 Makefile
--- Makefile14 May 2017 06:40:35 - 1.16
+++ Makefile14 May 2017 19:46:46 -
@@ -4,7 +4,7 @@ COMMENT=cross-platform multimedia libra
BROKEN-hppa= src/atomic/SDL_spinlock.c:101:2: error: \#error Please
implement for your platform.
V= 2.0.5
-REVISION= 0
+REVISION= 1
DISTNAME= SDL2-${V}
PKGNAME= sdl2-${V}
CATEGORIES=devel
Index: patches/patch-src_video_x11_SDL_x11events_c
===
RCS file: patches/patch-src_video_x11_SDL_x11events_c
diff -N patches/patch-src_video_x11_SDL_x11events_c
--- /dev/null 1 Jan 1970 00:00:00 -
+++ patches/patch-src_video_x11_SDL_x11events_c 14 May 2017 19:46:46 -
@@ -0,0 +1,24 @@
+$OpenBSD$
+
+Index: src/video/x11/SDL_x11events.c
+--- src/video/x11/SDL_x11events.c.orig
src/video/x11/SDL_x11events.c
+@@ -571,12 +571,18 @@ X11_DispatchEvent(_THIS)
+ if (orig_keycode) {
+ /* Make sure dead key press/release events are sent */
+ SDL_Scancode scancode = videodata->key_layout[orig_keycode];
++ videodata->filter_code = orig_keycode;
++ videodata->filter_time = xevent.xkey.time;
++
+ if (orig_event_type == KeyPress) {
+ SDL_SendKeyboardKey(SDL_PRESSED, scancode);
+ } else {
+ SDL_SendKeyboardKey(SDL_RELEASED, scancode);
+ }
+ }
++return;
++} else if (orig_keycode == videodata->filter_code && xevent.xkey.time ==
videodata->filter_time) {
++/* This is a duplicate event, resent by an IME - skip it. */
+ return;
+ }
+
Index: patches/patch-src_video_x11_SDL_x11video_h
===
RCS file: patches/patch-src_video_x11_SDL_x11video_h
diff -N patches/patch-src_video_x11_SDL_x11video_h
--- /dev/null 1 Jan 1970 00:00:00 -
+++ patches/patch-src_video_x11_SDL_x11video_h 14 May 2017 19:46:46 -
@@ -0,0 +1,16 @@
+$OpenBSD$
+
+Index: src/video/x11/SDL_x11video.h
+---
Re: devel/sdl2 bug since update to 2.0.5
On Thu, Dec 08, 2016 at 07:18:57PM -0800, Ryan Freeman wrote: > On Fri, Dec 02, 2016 at 10:46:32AM -0800, Ryan Freeman wrote: > > I wish I had noticed this sooner when the update was posted... > > > > For whatever reason, certain applications with SDL2 2.0.5 are receving > > duplicate keyboard events. Mouse seems unaffected, but the menus of some > > games are very hard to navigate. > > > > If the Esc key opens a menu, instead what happens is it opens and closes > > before you can do anything. If you happen to be in a menu, arrow keys > > for navigation move the selector up or down two spaces at a time. Trying > > to open a console, would make it open and close immediately as well. > > > > Gameplay-type keys would work normally in my testing. > > > > games/quakespasm shows this problem. > > I have updated to today's snapshot (Dec 8th) and unfortunately the problem > still persists, albeit only within gnome3. > > I haven't had anyone reply to this thread yet that is running gnome3 with > sdl2 games, so I can't be sure yet I am not the only one. and of course I missed a reply from Toby on Dec 6th who did try this within Gnome. Maybe best to just let this rest for now, sorry for the noise everyone. > > Any window manager I try outside of gnome3 does NOT exhibit this issue, > so I am enjoying cwm again for now for these things. > > I have tried the following within gnome to try and resolve the issue > - alternate keyboard > - create fresh account with fresh/default gnome setup > - update snapshot + packages > > No luck thus far, I can't seem to find anyone else running this combination > of things on OpenBSD yet, so if anyone has, please chime in! > > Cheers, > -ryan > > OpenBSD 6.0-current (GENERIC.MP) #23: Thu Dec 8 16:00:49 MST 2016 > bu...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > real mem = 16357261312 (15599MB) > avail mem = 15856967680 (15122MB) > mpath0 at root > scsibus0 at mpath0: 256 targets > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xf06e0 (71 entries) > bios0: vendor American Megatrends Inc. version "1206" date 04/16/2009 > bios0: ASUSTeK Computer INC. P5K3 Deluxe > acpi0 at bios0: rev 2 > acpi0: sleep states S0 S1 S3 S4 S5 > acpi0: tables DSDT FACP APIC MCFG OEMB HPET OSFR > acpi0: wakeup devices P0P2(S4) P0P1(S4) UAR1(S4) PS2K(S4) EUSB(S4) USBE(S4) > P0P4(S4) P0P5(S4) P0P6(S4) P0P7(S4) P0P8(S4) P0P9(S4) GBEC(S4) USB0(S4) > USB1(S4) USB2(S4) [...] > acpitimer0 at acpi0: 3579545 Hz, 24 bits > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > cpu0 at mainbus0: apid 0 (boot processor) > cpu0: Intel(R) Core(TM)2 Quad CPU Q9300 @ 2.50GHz, 2504.97 MHz > cpu0: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF,PERF > cpu0: 3MB 64b/line 8-way L2 cache > mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges > cpu0: apic clock running at 333MHz > cpu1 at mainbus0: apid 2 (application processor) > cpu1: Intel(R) Core(TM)2 Quad CPU Q9300 @ 2.50GHz, 2504.63 MHz > cpu1: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF,PERF > cpu1: 3MB 64b/line 8-way L2 cache > cpu2 at mainbus0: apid 1 (application processor) > cpu2: Intel(R) Core(TM)2 Quad CPU Q9300 @ 2.50GHz, 2504.63 MHz > cpu2: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF,PERF > cpu2: 3MB 64b/line 8-way L2 cache > cpu3 at mainbus0: apid 3 (application processor) > cpu3: Intel(R) Core(TM)2 Quad CPU Q9300 @ 2.50GHz, 2504.63 MHz > cpu3: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF,PERF > cpu3: 3MB 64b/line 8-way L2 cache > ioapic0 at mainbus0: apid 4 pa 0xfec0, version 20, 24 pins > acpimcfg0 at acpi0 addr 0xe000, bus 0-255 > acpihpet0 at acpi0: 14318179 Hz > acpiprt0 at acpi0: bus 0 (PCI0) > acpiprt1 at acpi0: bus 1 (P0P2) > acpiprt2 at acpi0: bus 4 (P0P1) > acpiprt3 at acpi0: bus 3 (P0P4) > acpiprt4 at acpi0: bus -1 (P0P6) > acpiprt5 at acpi0: bus -1 (P0P7) > acpiprt6 at acpi0: bus -1 (P0P8) > acpiprt7 at acpi0: bus 2 (P0P9) > acpicpu0 at acpi0: C1(@1 halt!), PSS > acpicpu1 at acpi0: C1(@1 halt!), PSS > acpicpu2 at acpi0: C1(@1 halt!), PSS > acpicpu3 at acpi0: C1(@1 halt!), PSS > aibs0 at acpi0 RTMP RVLT RFAN GGRP GITM SITM > "PNP0501" at acpi0 not configured > "PNP0303" at acpi0 not configured > "PNP0C32" at acpi0 not configured > acpibtn0 at acpi0: PWRB > cpu0: Enhanced SpeedStep 2504 MHz: speeds: 2497, 1998 MHz > pci0 at mainbus0 bus 0 > pchb0 at pci0 dev 0
Re: devel/sdl2 bug since update to 2.0.5
On Fri, Dec 02, 2016 at 10:46:32AM -0800, Ryan Freeman wrote: > I wish I had noticed this sooner when the update was posted... > > For whatever reason, certain applications with SDL2 2.0.5 are receving > duplicate keyboard events. Mouse seems unaffected, but the menus of some > games are very hard to navigate. > > If the Esc key opens a menu, instead what happens is it opens and closes > before you can do anything. If you happen to be in a menu, arrow keys > for navigation move the selector up or down two spaces at a time. Trying > to open a console, would make it open and close immediately as well. > > Gameplay-type keys would work normally in my testing. > > games/quakespasm shows this problem. I have updated to today's snapshot (Dec 8th) and unfortunately the problem still persists, albeit only within gnome3. I haven't had anyone reply to this thread yet that is running gnome3 with sdl2 games, so I can't be sure yet I am not the only one. Any window manager I try outside of gnome3 does NOT exhibit this issue, so I am enjoying cwm again for now for these things. I have tried the following within gnome to try and resolve the issue - alternate keyboard - create fresh account with fresh/default gnome setup - update snapshot + packages No luck thus far, I can't seem to find anyone else running this combination of things on OpenBSD yet, so if anyone has, please chime in! Cheers, -ryan OpenBSD 6.0-current (GENERIC.MP) #23: Thu Dec 8 16:00:49 MST 2016 bu...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 16357261312 (15599MB) avail mem = 15856967680 (15122MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xf06e0 (71 entries) bios0: vendor American Megatrends Inc. version "1206" date 04/16/2009 bios0: ASUSTeK Computer INC. P5K3 Deluxe acpi0 at bios0: rev 2 acpi0: sleep states S0 S1 S3 S4 S5 acpi0: tables DSDT FACP APIC MCFG OEMB HPET OSFR acpi0: wakeup devices P0P2(S4) P0P1(S4) UAR1(S4) PS2K(S4) EUSB(S4) USBE(S4) P0P4(S4) P0P5(S4) P0P6(S4) P0P7(S4) P0P8(S4) P0P9(S4) GBEC(S4) USB0(S4) USB1(S4) USB2(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM)2 Quad CPU Q9300 @ 2.50GHz, 2504.97 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF,PERF cpu0: 3MB 64b/line 8-way L2 cache mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 333MHz cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM)2 Quad CPU Q9300 @ 2.50GHz, 2504.63 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF,PERF cpu1: 3MB 64b/line 8-way L2 cache cpu2 at mainbus0: apid 1 (application processor) cpu2: Intel(R) Core(TM)2 Quad CPU Q9300 @ 2.50GHz, 2504.63 MHz cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF,PERF cpu2: 3MB 64b/line 8-way L2 cache cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Core(TM)2 Quad CPU Q9300 @ 2.50GHz, 2504.63 MHz cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF,PERF cpu3: 3MB 64b/line 8-way L2 cache ioapic0 at mainbus0: apid 4 pa 0xfec0, version 20, 24 pins acpimcfg0 at acpi0 addr 0xe000, bus 0-255 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (P0P2) acpiprt2 at acpi0: bus 4 (P0P1) acpiprt3 at acpi0: bus 3 (P0P4) acpiprt4 at acpi0: bus -1 (P0P6) acpiprt5 at acpi0: bus -1 (P0P7) acpiprt6 at acpi0: bus -1 (P0P8) acpiprt7 at acpi0: bus 2 (P0P9) acpicpu0 at acpi0: C1(@1 halt!), PSS acpicpu1 at acpi0: C1(@1 halt!), PSS acpicpu2 at acpi0: C1(@1 halt!), PSS acpicpu3 at acpi0: C1(@1 halt!), PSS aibs0 at acpi0 RTMP RVLT RFAN GGRP GITM SITM "PNP0501" at acpi0 not configured "PNP0303" at acpi0 not configured "PNP0C32" at acpi0 not configured acpibtn0 at acpi0: PWRB cpu0: Enhanced SpeedStep 2504 MHz: speeds: 2497, 1998 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel 82G33 Host" rev 0x02 ppb0 at pci0 dev 1 function 0 "Intel 82G33 PCIE" rev 0x02: msi pci1 at ppb0 bus 1 radeondrm0 at pci1 dev 0 function 0 "ATI Radeon HD 4870" rev 0x00 drm0 at radeondrm0 radeondrm0: msi azalia0 at pci1 dev 0 function 1 "ATI Radeon HD 48xx HD Audio" rev 0x00: msi azalia0: no supported codecs uhci0 at pci0 dev 26 function 0 "Intel 82801I USB" rev 0x02: apic 4 int 16 uhci1 at pci0 dev
Re: devel/sdl2 bug since update to 2.0.5
Le 2016-12-05 18:53, Ryan Freeman a écrit : On Sun, Dec 04, 2016 at 12:43:33PM +0100, Solène Rapenne wrote: Le 2016-12-02 19:46, Ryan Freeman a écrit : >I wish I had noticed this sooner when the update was posted... > >For whatever reason, certain applications with SDL2 2.0.5 are receving >duplicate keyboard events. Mouse seems unaffected, but the menus >of some >games are very hard to navigate. > -snip- Hello, I've been playing games/tome (the port is currently in work) which requires SDL2. I have SDL 2.0.5 and never noticed any problem if this kind. I'm using stumpwm started from xdm. I will try games/quakespasm to check if I can reproduce it on my computer. Hey, Thanks for giving it a go, but after Jonathan noticed no problems whatsoever, I discovered the issue only occurs when I run the Gnome desktop. If you happen to have it installed as well alongside your xdm/stumpwm setup, I am curious if the issue can be reproduced by another user in Gnome other than myself. I have since tested all the problem games/programs with SDL2 2.0.5 and using just cwm, and cannot reproduce the issue. So its somewhere in the mammoth complexity of running a full DE, as long as its on more than just my machine :-) Cheers! -ryan I tried the game with the demo files and it was perfectly playable. I didn't notice any issue with the keyboard. I upgraded my system yesterday, I have sdl2-2.0.5 package installed. My desktop configuration : xdm with stumpwm, intel graphics 4gen
Re: devel/sdl2 bug since update to 2.0.5
Hi Ryan, >I am curious if the issue can be reproduced by >another user in Gnome other than myself. Just for the sake of it I got quakespasm going (just using `pkg_add') and was unable to reproduce your menu bugs in GNOME. Please note that this was my first time running quakespasm but it seemed to work fine for me (today's snapshot and packages, ThinkPad T430. toby/
Re: devel/sdl2 bug since update to 2.0.5
On Sun, Dec 04, 2016 at 12:43:33PM +0100, Solène Rapenne wrote: > Le 2016-12-02 19:46, Ryan Freeman a écrit : > >I wish I had noticed this sooner when the update was posted... > > > >For whatever reason, certain applications with SDL2 2.0.5 are receving > >duplicate keyboard events. Mouse seems unaffected, but the menus > >of some > >games are very hard to navigate. > > -snip- > > Hello, > > I've been playing games/tome (the port is currently in work) which > requires SDL2. > I have SDL 2.0.5 and never noticed any problem if this kind. I'm > using stumpwm > started from xdm. I will try games/quakespasm to check if I can > reproduce it > on my computer. Hey, Thanks for giving it a go, but after Jonathan noticed no problems whatsoever, I discovered the issue only occurs when I run the Gnome desktop. If you happen to have it installed as well alongside your xdm/stumpwm setup, I am curious if the issue can be reproduced by another user in Gnome other than myself. I have since tested all the problem games/programs with SDL2 2.0.5 and using just cwm, and cannot reproduce the issue. So its somewhere in the mammoth complexity of running a full DE, as long as its on more than just my machine :-) Cheers! -ryan
Re: devel/sdl2 bug since update to 2.0.5
Le 2016-12-02 19:46, Ryan Freeman a écrit : I wish I had noticed this sooner when the update was posted... For whatever reason, certain applications with SDL2 2.0.5 are receving duplicate keyboard events. Mouse seems unaffected, but the menus of some games are very hard to navigate. If the Esc key opens a menu, instead what happens is it opens and closes before you can do anything. If you happen to be in a menu, arrow keys for navigation move the selector up or down two spaces at a time. Trying to open a console, would make it open and close immediately as well. Gameplay-type keys would work normally in my testing. games/quakespasm shows this problem. I haven't found others just yet that are in ports, but it was while checking the SDL2 branch of chocolate-doom currently in development that led me to this discovery. Initially thought it was just a local problem with that project until i duplicated it also with doomretro (not in ports, http://github.com/bradharding/doomretro) and quakespasm. My workstation at work still has a snapshot from Nov 8th, running SDL2 2.0.4. As a result I can't reproduce the issue here. My workstation at home ran a snapshot from Nov 17th when I found the problem. I updated it to Dec 1 snapshot and verified the problem still exists. I found this post in the SDL2 changelog: http://hg.libsdl.org/SDL/rev/aea47b61c640 ...and wondered if it was somehow related. I manually reverted this patch and gave it a go, but the problem persists. Has anyone else noticed duplicated key events in SDL2 programs? Any other examples? I am not sure where to look, but don't want to keep this to myself for too long... dmesg below of the most recent snapshot I've tried this with, cheers! -ryan Hello, I've been playing games/tome (the port is currently in work) which requires SDL2. I have SDL 2.0.5 and never noticed any problem if this kind. I'm using stumpwm started from xdm. I will try games/quakespasm to check if I can reproduce it on my computer.
Re: devel/sdl2 bug since update to 2.0.5
On Sat, Dec 03, 2016 at 07:10:20PM -0800, Ryan Freeman wrote: > On Sun, Dec 04, 2016 at 01:34:33PM +1100, Jonathan Gray wrote: > > On Fri, Dec 02, 2016 at 10:46:32AM -0800, Ryan Freeman wrote: > > > I wish I had noticed this sooner when the update was posted... > > > > > > For whatever reason, certain applications with SDL2 2.0.5 are receving > > > duplicate keyboard events. Mouse seems unaffected, but the menus of some > > > games are very hard to navigate. > > > > > > If the Esc key opens a menu, instead what happens is it opens and closes > > > before you can do anything. If you happen to be in a menu, arrow keys > > > for navigation move the selector up or down two spaces at a time. Trying > > > to open a console, would make it open and close immediately as well. > > > > > > Gameplay-type keys would work normally in my testing. > ---snip--- > > > > I haven't seen this with quakespasm, yquake2 or redeclipse. > > > > Perhaps try a different keyboard? > > Well, a different keyboard did not help, but you got me thinking about other > causes. Gnome seems to be playing a role. Exiting, switching off gdm > entirely, and then running cwm or openbox causes these problems to go away. > > Restarting Gnome again still causes the problem to occur, so this is a wierd > combination of things. I'll try and provide more detail if I can get a clue. > > I'll hazard a guess that you aren't running Gnome? no gnome, just cwm > > It is odd that similar fullscreen programs using SDL1 seem unaffected, as > well as normal typing pretty much anywhere else. > > Cheers! > > -ryan > > > > > > > dmesg below of the most recent snapshot I've tried this with, > > > > > > cheers! > > > -ryan > > > > > > OpenBSD 6.0-current (GENERIC.MP) #0: Thu Dec 1 12:16:22 MST 2016 > > > bu...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > > > real mem = 16357261312 (15599MB) > > > avail mem = 15856971776 (15122MB) > > > mpath0 at root > > > scsibus0 at mpath0: 256 targets > > > mainbus0 at root > > > bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xf06e0 (71 entries) > > > bios0: vendor American Megatrends Inc. version "1206" date 04/16/2009 > > > bios0: ASUSTeK Computer INC. P5K3 Deluxe > > > acpi0 at bios0: rev 2 > > > acpi0: sleep states S0 S1 S3 S4 S5 > > > acpi0: tables DSDT FACP APIC MCFG OEMB HPET OSFR > > > acpi0: wakeup devices P0P2(S4) P0P1(S4) UAR1(S4) PS2K(S4) EUSB(S4) > > > USBE(S4) P0P4(S4) P0P5(S4) P0P6(S4) P0P7(S4) P0P8(S4) P0P9(S4) GBEC(S4) > > > USB0(S4) USB1(S4) USB2(S4) [...] > > > acpitimer0 at acpi0: 3579545 Hz, 24 bits > > > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > > > cpu0 at mainbus0: apid 0 (boot processor) > > > cpu0: Intel(R) Core(TM)2 Quad CPU Q9300 @ 2.50GHz, 2504.99 MHz > > > cpu0: > > > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF,PERF > > > cpu0: 3MB 64b/line 8-way L2 cache > > > mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges > > > cpu0: apic clock running at 333MHz > > > cpu1 at mainbus0: apid 2 (application processor) > > > cpu1: Intel(R) Core(TM)2 Quad CPU Q9300 @ 2.50GHz, 2504.63 MHz > > > cpu1: > > > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF,PERF > > > cpu1: 3MB 64b/line 8-way L2 cache > > > cpu2 at mainbus0: apid 1 (application processor) > > > cpu2: Intel(R) Core(TM)2 Quad CPU Q9300 @ 2.50GHz, 2504.63 MHz > > > cpu2: > > > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF,PERF > > > cpu2: 3MB 64b/line 8-way L2 cache > > > cpu3 at mainbus0: apid 3 (application processor) > > > cpu3: Intel(R) Core(TM)2 Quad CPU Q9300 @ 2.50GHz, 2504.63 MHz > > > cpu3: > > > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF,PERF > > > cpu3: 3MB 64b/line 8-way L2 cache > > > ioapic0 at mainbus0: apid 4 pa 0xfec0, version 20, 24 pins > > > acpimcfg0 at acpi0 addr 0xe000, bus 0-255 > > > acpihpet0 at acpi0: 14318179 Hz > > > acpiprt0 at acpi0: bus 0 (PCI0) > > > acpiprt1 at acpi0: bus 1 (P0P2) > > > acpiprt2 at acpi0: bus 4 (P0P1) > > > acpiprt3 at acpi0: bus 3 (P0P4) > > > acpiprt4 at acpi0: bus -1 (P0P6) > > > acpiprt5 at acpi0: bus -1 (P0P7) > > > acpiprt6 at acpi0: bus -1 (P0P8) > > > acpiprt7 at acpi0: bus 2 (P0P9) > > > acpicpu0 at acpi0: C1(@1 halt!), PSS > > > acpicpu1 at acpi0: C1(@1 halt!), PSS > > > acpicpu2 at acpi0: C1(@1 halt!), PSS > > > acpicpu3 at acpi0: C1(@1 halt!), PSS > > > aibs0 at acpi0 RTMP RVLT RFAN GGRP GITM SITM > > >
Re: devel/sdl2 bug since update to 2.0.5
On Sun, Dec 04, 2016 at 01:34:33PM +1100, Jonathan Gray wrote: > On Fri, Dec 02, 2016 at 10:46:32AM -0800, Ryan Freeman wrote: > > I wish I had noticed this sooner when the update was posted... > > > > For whatever reason, certain applications with SDL2 2.0.5 are receving > > duplicate keyboard events. Mouse seems unaffected, but the menus of some > > games are very hard to navigate. > > > > If the Esc key opens a menu, instead what happens is it opens and closes > > before you can do anything. If you happen to be in a menu, arrow keys > > for navigation move the selector up or down two spaces at a time. Trying > > to open a console, would make it open and close immediately as well. > > > > Gameplay-type keys would work normally in my testing. ---snip--- > > I haven't seen this with quakespasm, yquake2 or redeclipse. > > Perhaps try a different keyboard? Well, a different keyboard did not help, but you got me thinking about other causes. Gnome seems to be playing a role. Exiting, switching off gdm entirely, and then running cwm or openbox causes these problems to go away. Restarting Gnome again still causes the problem to occur, so this is a wierd combination of things. I'll try and provide more detail if I can get a clue. I'll hazard a guess that you aren't running Gnome? It is odd that similar fullscreen programs using SDL1 seem unaffected, as well as normal typing pretty much anywhere else. Cheers! -ryan > > > > dmesg below of the most recent snapshot I've tried this with, > > > > cheers! > > -ryan > > > > OpenBSD 6.0-current (GENERIC.MP) #0: Thu Dec 1 12:16:22 MST 2016 > > bu...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > > real mem = 16357261312 (15599MB) > > avail mem = 15856971776 (15122MB) > > mpath0 at root > > scsibus0 at mpath0: 256 targets > > mainbus0 at root > > bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xf06e0 (71 entries) > > bios0: vendor American Megatrends Inc. version "1206" date 04/16/2009 > > bios0: ASUSTeK Computer INC. P5K3 Deluxe > > acpi0 at bios0: rev 2 > > acpi0: sleep states S0 S1 S3 S4 S5 > > acpi0: tables DSDT FACP APIC MCFG OEMB HPET OSFR > > acpi0: wakeup devices P0P2(S4) P0P1(S4) UAR1(S4) PS2K(S4) EUSB(S4) USBE(S4) > > P0P4(S4) P0P5(S4) P0P6(S4) P0P7(S4) P0P8(S4) P0P9(S4) GBEC(S4) USB0(S4) > > USB1(S4) USB2(S4) [...] > > acpitimer0 at acpi0: 3579545 Hz, 24 bits > > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > > cpu0 at mainbus0: apid 0 (boot processor) > > cpu0: Intel(R) Core(TM)2 Quad CPU Q9300 @ 2.50GHz, 2504.99 MHz > > cpu0: > > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF,PERF > > cpu0: 3MB 64b/line 8-way L2 cache > > mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges > > cpu0: apic clock running at 333MHz > > cpu1 at mainbus0: apid 2 (application processor) > > cpu1: Intel(R) Core(TM)2 Quad CPU Q9300 @ 2.50GHz, 2504.63 MHz > > cpu1: > > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF,PERF > > cpu1: 3MB 64b/line 8-way L2 cache > > cpu2 at mainbus0: apid 1 (application processor) > > cpu2: Intel(R) Core(TM)2 Quad CPU Q9300 @ 2.50GHz, 2504.63 MHz > > cpu2: > > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF,PERF > > cpu2: 3MB 64b/line 8-way L2 cache > > cpu3 at mainbus0: apid 3 (application processor) > > cpu3: Intel(R) Core(TM)2 Quad CPU Q9300 @ 2.50GHz, 2504.63 MHz > > cpu3: > > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF,PERF > > cpu3: 3MB 64b/line 8-way L2 cache > > ioapic0 at mainbus0: apid 4 pa 0xfec0, version 20, 24 pins > > acpimcfg0 at acpi0 addr 0xe000, bus 0-255 > > acpihpet0 at acpi0: 14318179 Hz > > acpiprt0 at acpi0: bus 0 (PCI0) > > acpiprt1 at acpi0: bus 1 (P0P2) > > acpiprt2 at acpi0: bus 4 (P0P1) > > acpiprt3 at acpi0: bus 3 (P0P4) > > acpiprt4 at acpi0: bus -1 (P0P6) > > acpiprt5 at acpi0: bus -1 (P0P7) > > acpiprt6 at acpi0: bus -1 (P0P8) > > acpiprt7 at acpi0: bus 2 (P0P9) > > acpicpu0 at acpi0: C1(@1 halt!), PSS > > acpicpu1 at acpi0: C1(@1 halt!), PSS > > acpicpu2 at acpi0: C1(@1 halt!), PSS > > acpicpu3 at acpi0: C1(@1 halt!), PSS > > aibs0 at acpi0 RTMP RVLT RFAN GGRP GITM SITM > > "PNP0501" at acpi0 not configured > > "PNP0303" at acpi0 not configured > > "PNP0C32" at acpi0 not configured > > acpibtn0 at acpi0: PWRB > > cpu0: Enhanced SpeedStep 2504 MHz: speeds: 2497, 1998 MHz > > pci0 at mainbus0 bus 0 > > pchb0 at pci0 dev 0 function 0 "Intel 82G33 Host" rev
Re: devel/sdl2 bug since update to 2.0.5
On Fri, Dec 02, 2016 at 10:46:32AM -0800, Ryan Freeman wrote: > I wish I had noticed this sooner when the update was posted... > > For whatever reason, certain applications with SDL2 2.0.5 are receving > duplicate keyboard events. Mouse seems unaffected, but the menus of some > games are very hard to navigate. > > If the Esc key opens a menu, instead what happens is it opens and closes > before you can do anything. If you happen to be in a menu, arrow keys > for navigation move the selector up or down two spaces at a time. Trying > to open a console, would make it open and close immediately as well. > > Gameplay-type keys would work normally in my testing. > > games/quakespasm shows this problem. I haven't found others just yet that > are in ports, but it was while checking the SDL2 branch of chocolate-doom > currently in development that led me to this discovery. > Initially thought it was just a local problem with that project until i > duplicated it also with doomretro (not in ports, > http://github.com/bradharding/doomretro) and quakespasm. > > My workstation at work still has a snapshot from Nov 8th, running SDL2 2.0.4. > As a result I can't reproduce the issue here. > > My workstation at home ran a snapshot from Nov 17th when I found the problem. > I updated it to Dec 1 snapshot and verified the problem still exists. > > I found this post in the SDL2 changelog: > http://hg.libsdl.org/SDL/rev/aea47b61c640 > ...and wondered if it was somehow related. I manually reverted this patch > and gave it a go, but the problem persists. > > Has anyone else noticed duplicated key events in SDL2 programs? Any other > examples? I am not sure where to look, but don't want to keep this to myself > for too long... I haven't seen this with quakespasm, yquake2 or redeclipse. Perhaps try a different keyboard? > > dmesg below of the most recent snapshot I've tried this with, > > cheers! > -ryan > > OpenBSD 6.0-current (GENERIC.MP) #0: Thu Dec 1 12:16:22 MST 2016 > bu...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > real mem = 16357261312 (15599MB) > avail mem = 15856971776 (15122MB) > mpath0 at root > scsibus0 at mpath0: 256 targets > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xf06e0 (71 entries) > bios0: vendor American Megatrends Inc. version "1206" date 04/16/2009 > bios0: ASUSTeK Computer INC. P5K3 Deluxe > acpi0 at bios0: rev 2 > acpi0: sleep states S0 S1 S3 S4 S5 > acpi0: tables DSDT FACP APIC MCFG OEMB HPET OSFR > acpi0: wakeup devices P0P2(S4) P0P1(S4) UAR1(S4) PS2K(S4) EUSB(S4) USBE(S4) > P0P4(S4) P0P5(S4) P0P6(S4) P0P7(S4) P0P8(S4) P0P9(S4) GBEC(S4) USB0(S4) > USB1(S4) USB2(S4) [...] > acpitimer0 at acpi0: 3579545 Hz, 24 bits > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > cpu0 at mainbus0: apid 0 (boot processor) > cpu0: Intel(R) Core(TM)2 Quad CPU Q9300 @ 2.50GHz, 2504.99 MHz > cpu0: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF,PERF > cpu0: 3MB 64b/line 8-way L2 cache > mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges > cpu0: apic clock running at 333MHz > cpu1 at mainbus0: apid 2 (application processor) > cpu1: Intel(R) Core(TM)2 Quad CPU Q9300 @ 2.50GHz, 2504.63 MHz > cpu1: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF,PERF > cpu1: 3MB 64b/line 8-way L2 cache > cpu2 at mainbus0: apid 1 (application processor) > cpu2: Intel(R) Core(TM)2 Quad CPU Q9300 @ 2.50GHz, 2504.63 MHz > cpu2: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF,PERF > cpu2: 3MB 64b/line 8-way L2 cache > cpu3 at mainbus0: apid 3 (application processor) > cpu3: Intel(R) Core(TM)2 Quad CPU Q9300 @ 2.50GHz, 2504.63 MHz > cpu3: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF,PERF > cpu3: 3MB 64b/line 8-way L2 cache > ioapic0 at mainbus0: apid 4 pa 0xfec0, version 20, 24 pins > acpimcfg0 at acpi0 addr 0xe000, bus 0-255 > acpihpet0 at acpi0: 14318179 Hz > acpiprt0 at acpi0: bus 0 (PCI0) > acpiprt1 at acpi0: bus 1 (P0P2) > acpiprt2 at acpi0: bus 4 (P0P1) > acpiprt3 at acpi0: bus 3 (P0P4) > acpiprt4 at acpi0: bus -1 (P0P6) > acpiprt5 at acpi0: bus -1 (P0P7) > acpiprt6 at acpi0: bus -1 (P0P8) > acpiprt7 at acpi0: bus 2 (P0P9) > acpicpu0 at acpi0: C1(@1 halt!), PSS > acpicpu1 at acpi0: C1(@1 halt!), PSS > acpicpu2 at acpi0: C1(@1 halt!), PSS > acpicpu3 at acpi0: C1(@1 halt!), PSS > aibs0 at acpi0 RTMP RVLT RFAN GGRP GITM SITM > "PNP0501" at acpi0
devel/sdl2 bug since update to 2.0.5
I wish I had noticed this sooner when the update was posted... For whatever reason, certain applications with SDL2 2.0.5 are receving duplicate keyboard events. Mouse seems unaffected, but the menus of some games are very hard to navigate. If the Esc key opens a menu, instead what happens is it opens and closes before you can do anything. If you happen to be in a menu, arrow keys for navigation move the selector up or down two spaces at a time. Trying to open a console, would make it open and close immediately as well. Gameplay-type keys would work normally in my testing. games/quakespasm shows this problem. I haven't found others just yet that are in ports, but it was while checking the SDL2 branch of chocolate-doom currently in development that led me to this discovery. Initially thought it was just a local problem with that project until i duplicated it also with doomretro (not in ports, http://github.com/bradharding/doomretro) and quakespasm. My workstation at work still has a snapshot from Nov 8th, running SDL2 2.0.4. As a result I can't reproduce the issue here. My workstation at home ran a snapshot from Nov 17th when I found the problem. I updated it to Dec 1 snapshot and verified the problem still exists. I found this post in the SDL2 changelog: http://hg.libsdl.org/SDL/rev/aea47b61c640 ...and wondered if it was somehow related. I manually reverted this patch and gave it a go, but the problem persists. Has anyone else noticed duplicated key events in SDL2 programs? Any other examples? I am not sure where to look, but don't want to keep this to myself for too long... dmesg below of the most recent snapshot I've tried this with, cheers! -ryan OpenBSD 6.0-current (GENERIC.MP) #0: Thu Dec 1 12:16:22 MST 2016 bu...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 16357261312 (15599MB) avail mem = 15856971776 (15122MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xf06e0 (71 entries) bios0: vendor American Megatrends Inc. version "1206" date 04/16/2009 bios0: ASUSTeK Computer INC. P5K3 Deluxe acpi0 at bios0: rev 2 acpi0: sleep states S0 S1 S3 S4 S5 acpi0: tables DSDT FACP APIC MCFG OEMB HPET OSFR acpi0: wakeup devices P0P2(S4) P0P1(S4) UAR1(S4) PS2K(S4) EUSB(S4) USBE(S4) P0P4(S4) P0P5(S4) P0P6(S4) P0P7(S4) P0P8(S4) P0P9(S4) GBEC(S4) USB0(S4) USB1(S4) USB2(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM)2 Quad CPU Q9300 @ 2.50GHz, 2504.99 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF,PERF cpu0: 3MB 64b/line 8-way L2 cache mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 333MHz cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM)2 Quad CPU Q9300 @ 2.50GHz, 2504.63 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF,PERF cpu1: 3MB 64b/line 8-way L2 cache cpu2 at mainbus0: apid 1 (application processor) cpu2: Intel(R) Core(TM)2 Quad CPU Q9300 @ 2.50GHz, 2504.63 MHz cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF,PERF cpu2: 3MB 64b/line 8-way L2 cache cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Core(TM)2 Quad CPU Q9300 @ 2.50GHz, 2504.63 MHz cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF,PERF cpu3: 3MB 64b/line 8-way L2 cache ioapic0 at mainbus0: apid 4 pa 0xfec0, version 20, 24 pins acpimcfg0 at acpi0 addr 0xe000, bus 0-255 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (P0P2) acpiprt2 at acpi0: bus 4 (P0P1) acpiprt3 at acpi0: bus 3 (P0P4) acpiprt4 at acpi0: bus -1 (P0P6) acpiprt5 at acpi0: bus -1 (P0P7) acpiprt6 at acpi0: bus -1 (P0P8) acpiprt7 at acpi0: bus 2 (P0P9) acpicpu0 at acpi0: C1(@1 halt!), PSS acpicpu1 at acpi0: C1(@1 halt!), PSS acpicpu2 at acpi0: C1(@1 halt!), PSS acpicpu3 at acpi0: C1(@1 halt!), PSS aibs0 at acpi0 RTMP RVLT RFAN GGRP GITM SITM "PNP0501" at acpi0 not configured "PNP0303" at acpi0 not configured "PNP0C32" at acpi0 not configured acpibtn0 at acpi0: PWRB cpu0: Enhanced SpeedStep 2504 MHz: speeds: 2497, 1998 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel 82G33 Host" rev 0x02 ppb0 at pci0 dev 1 function 0 "Intel 82G33 PCIE" rev 0x02: msi pci1 at ppb0 bus 1 radeondrm0 at pci1 dev 0
