From Bugzilla Helper:
User-Agent: Mozilla/4.79 [en] (X11; U; Linux 2.4.18-14 i686)
Description of problem:
I'm trying to run xhangglider as the "background program"
of the gdm login screen. This works fine on one box (a Duron)
but on an Athlon box the execution is slow and jerky, somewhat synchronized with
the pulsing of the cursor. I can't figure out why.
Possibly some problem with the Athlon kernel I'm using
(kernel-2.4.18-14.athlon.rpm) ? It's definitely not because the program
requires too many cycles: it runs standalone fine using just 1% of the CPU.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. install xhangglider
2. BackgroundProgram=/usr/local/bin/xhangglider -noflicker -pilot 8 in
Actual Results: xhangglider program runs slowly and jerkily
Expected Results: smooth and fast execution
If you can track this down more definitively to a Red Hat problem
we can look at it, but we aren't likely to download xhangglider and try
to debug that. Can you reproduce it with any Red Hat provided software?
Why is the cursor pulsing? Perhaps the problem is an interaction between OpenGL or
other graphics and the software cursor. That would be an XFree86 issue.
In any case, it's more likely to be XFree86 or kernel than gdm.
1. xfishtank works fine as the background program
2. It's the username/password cursor that pulses, not the "pointer" cursor;
I presume this is deliberate. It's the same cursor pulsing that is
happening in this browser window as I type.
3. The same version of XFree86 is running on the Duron/Athlon boxen, but the
video cards and hence drivers are different.
4. The reason I was considering this to be a gdm problem is that xhangglider
runs fine as a user program.
Must just be an X/kernel scheduling issue, I can't see how gdm would
The errata kernel for RHL9 may be much better in this respect.
Thanks for the bug report. However, Red Hat no longer maintains this version of
the product. Please upgrade to the latest version and open a new bug if the problem
The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases,
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at: http://bugzilla.fedora.us/