+---------------------------------------------------------------------+ | You don't have the time or experience to become a Debian developer? | | Nevertheless you want to help? | | or | | You are a hacker, longing for a task that is up to your abilities? | +---------------------------------------------------------------------+ | H U N T T H E B U G ! | +---------------------------------------------------------------------+ | A few minutes of your time can already help! | +---------------------------------------------------------------------+
Hello, Bug #740 is the oldest open bug report in the Debian archive. We have two options: 1) Leave it there, as a symbol of the eternity of our Bug Tracking System, or 2) Hunt it, localize it, fix it. Although 1) is very tempting, I thought we could at least try to find a reliable way to reproduce the bug, so we can forward it upstream. Background information: Some people report that xclock leaves "droppings" in the window, this means, the handles are not deleted correctly, some pixel remain. Possible causes of the problem: XClock callls XDrawLines() and XFillPolygon() to update the handles twice, both times with the very same arguments, so the bug seems to be hidden in the X libraries and/or servers or even in the FPU unit of the processor. If anyone does find droppings, please supply relevant information like: - which version of the xbase and xlib6/xlib6g packages you use - which Xserver you use (name and version) - how the Xserver is configured in /etc/X11/XF86Config (FastRam activated? etc) - which video card you have and how fast the memory is (70 or 60ns?) - which kernel you are using (self-compiled or Debian, FPU emulation?) - which libc version have - which kind of CPU you have (as detailed as possible, because this 'bug' could be caused by FPU errors) - the exact command you start xclock with, including all parameters and switches - versions of other important things I probably have forgotten +-----------------------------------------------------------------------+ | Please run the attached `fastclock' binary, it is an `optimized' | | version of xclock, which runs about 60 times faster than the original.| | As I have never seen droppings, I can't tell you how long you have to | | run the program. If you see artifacts, please submit the information | | above to [EMAIL PROTECTED] | +-----------------------------------------------------------------------+ Thank you for your help, Marcus -- "Rhubarb is no Egyptian god." Debian GNU/Linux finger brinkmd@ Marcus Brinkmann http://www.debian.org master.debian.org [EMAIL PROTECTED] for public PGP Key http://homepage.ruhr-uni-bochum.de/Marcus.Brinkmann/ PGP Key ID 36E7CD09
fastclock
Description: Binary data
