Bug#345278: marked as done (kasteroids bug: key up event not recognized)
Your message dated Sun, 14 May 2006 16:43:57 +0200
with message-id <200605141643.57810@nivalis.org>
and subject line the problem disappeared!!
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: kasteroids bug: key up event not recognized
- From: Peter Mao <peter.mao@gmail.com>
- Date: Thu, 29 Dec 2005 17:32:27 -0800
- Message-id: <6da7452a0512291732j305bd980l8378a8684dab3973@mail.gmail.com>
Package: kdegames
Version: 3.4.0-1
kasteroids doesn't seem to recognize key-up events. when I fire,
it fires forever, when I hit UP, it keeps UP held until I die.
Turning LEFT or RIGHT stops if I hit the opposite key, but then turning
is impossible. I have included my is my kasteroids version and
hardware summary.
It used to work fine on FC3 with kdegames-3.3.0-2.
$ kasteroids --version
Qt: 3.3.4
KDE: 3.4.0-6 Red Hat
KAsteroids: 2.3
$ uname -a
Linux chupa 2.6.11-1.1369_FC4 #1 Thu Jun 2 22:55:56 EDT 2005 i686 i686 i386 GNU/Linux
--- End Message ---
--- Begin Message ---
- To: Undisclosed.Recipients: ;
- Cc: 345278-done@bugs.debian.org
- Subject: Re: the problem disappeared!!
- From: Olivier Trichet <nive@nivalis.org>
- Date: Sun, 14 May 2006 16:43:57 +0200
- Message-id: <200605141643.57810@nivalis.org>
- Reply-to: nive@nivalis.org
- In-reply-to: <6da7452a0601071843u23850fa7r76d2cb23fd847e88@mail.gmail.com>
- References: <6da7452a0601071843u23850fa7r76d2cb23fd847e88@mail.gmail.com>
Le Dimanche 8 Janvier 2006 03:43, Peter Mao <peter.mao@gmail.com> a écrit :
> I imagine one of the following packages solved the problem (although I
> don't know which)
> I noticed today that it was all fine now. These are the packages I
> updated since I sent the initial bug report.
>
If it works... let's close this bug.
--- End Message ---
Reply to: