[Pkg-qof-maintainers] Bug#547905: quits on KeyRelease events

Marcin Owsiany porridge at debian.org
Tue Sep 22 14:03:52 UTC 2009


Package: gnotime
Version: 2.2.3-2

To reproduce:

1) run gnotime
2) run another application which terminates on pressing "q" (an example could
be "exec mutt" in a gnome-terminal or in an xterm)
3) press the "q" key
4) notice how both the application and gnotime terminate

This is both surprising an annoying.

Using "xev" in place of gnotime, I got the following output:

| FocusIn event, serial 30, synthetic NO, window 0x5000001,
|     mode NotifyNormal, detail NotifyNonlinear
| 
| KeymapNotify event, serial 30, synthetic NO, window 0x0,
|     keys:  2   0   0   1   0   0   0   0   0   0   0   0   0   0   0   0   
|            0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   
| 
| PropertyNotify event, serial 30, synthetic NO, window 0x5000001,
|     atom 0x148 (_NET_WM_ICON_GEOMETRY), time 194628229, state PropertyNewValue
| 
| KeyRelease event, serial 30, synthetic NO, window 0x5000001,
|     root 0x13b, subw 0x0, time 194628254, (735,-416), root:(792,208),
|     state 0x0, keycode 24 (keysym 0x71, q), same_screen YES,
|     XLookupString gives 1 bytes: (71) "q"
|     XFilterEvent returns: False

this suggests that the "KeyRelease" event for which XLookupString gives 1
byte: (71) "q" is interpreted as a keypress by gnotime.

I don't think it's an expected behaviour.

-- 
Marcin Owsiany <porridge at debian.org>             http://marcin.owsiany.pl/
GnuPG: 1024D/60F41216  FE67 DA2D 0ACA FC5E 3F75  D6F6 3A0D 8AA0 60F4 1216






More information about the Pkg-qof-maintainers mailing list