Your message dated Mon, 02 Oct 2006 17:17:54 +0300
with message-id <[EMAIL PROTECTED]>
and subject line #295289 should be closed
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 ---
Package: billard-gl
Version: 1.75-7
Severity: important

On my current hardware I can't hit ball at full strength.
(not exactly true, but you'll find out later)

It always gets hit at about 8-10% of full strength, always the same
value, after the same time.

After some testing I managed to find out it's the matter of autorepeat
times of keyboard.
When I turn off autorepeat ('xset r off') BillardGL works fine (but the
rest of my system doesn't - autorepeat is quite useful and nice feature)
So, this bug renders BillardGL practically useless to me.


Some time ago I didn't have this problem.
At that time I had different Linux kernel - 2.4 instead of current 2.6
and also different hardware (mainboard using VIA KT133 instead of KT600
chipset, and made by another manufacturer (Sono instead of Gigabyte)).

IIRC on my previous mainboard I had keyboard autorepeat turned off in
BIOS (which didn't turn off autorepeat under OS control), now I don't
even have such setting in BIOS Setup.


This bug is reported to upstream author,
http://www.ameds.de/billardgl/read.php?f=4&i=1&t=1
but BillardGL seems practically dead upstream, so forwarding bug
to Tobias Nopper probably won't solve the problem.

I tried to sort things out myself, but plenty of BillardGL code is
written/documented in German (eg. variable names).
So, unfortunately, I had to give up trying to analyze program to make
useful patch.

Anyway. It seems that BillardGL tries to read key events at level way
too low, which leads to trouble on certain, specific hardware.



-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.10-1-k7
Locale: LANG=pl_PL, LC_CTYPE=pl_PL (charmap=ISO-8859-2)

Versions of packages billard-gl depends on:
ii  billard-gl-data          1.75-7          3D billards game - data files
ii  freeglut3                2.2.0-8         OpenGL Utility Toolkit
ii  libc6                    2.3.2.ds1-20    GNU C Library: Shared libraries an
ii  libgcc1                  1:3.4.3-9       GCC support library
ii  libstdc++5               1:3.3.5-8       The GNU Standard C++ Library v3
ii  libx11-6                 4.3.0.dfsg.1-10 X Window System protocol client li
ii  libxext6                 4.3.0.dfsg.1-10 X Window System miscellaneous exte
ii  libxi6                   4.3.0.dfsg.1-10 X Window System Input extension li
ii  libxmu6                  4.3.0.dfsg.1-10 X Window System miscellaneous util
ii  xlibmesa-gl [libgl1]     4.3.0.dfsg.1-10 Mesa 3D graphics library [XFree86]
ii  xlibmesa-glu [libglu1]   4.3.0.dfsg.1-10 Mesa OpenGL utility library [XFree
ii  xlibs                    4.3.0.dfsg.1-11 X Keyboard Extension (XKB) configu

-- no debconf information


--- End Message ---
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

It seems the bug #295289 is closed and since it was cause by freeglut
which was fixed almost a year ago, we should close this.

Please reopen if you find the bug is still present.

- --
Regards,
EddyP
=============================================
"Imagination is more important than knowledge" A.Einstein
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFIR+SY8Chqv3NRNoRAtQBAKDX565iT425+3KWHQQMiBxTov8MFwCgsoBh
RvKo0cRCF8UCCBMaMiZM49o=
=YSNi
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to