Red Hat Bugzilla – Bug 193520
No mouse cursor with nVidia driver (work around included)
Last modified: 2018-04-11 10:33:09 EDT
Description of problem:
No visible mouse cursor on login screen or once logged in. However, it is
possible to click on things.
Version-Release number of selected component (if applicable):
100% - always happens
Steps to Reproduce:
1. Boot to login screen (no mouse cursor), login (no mouse cursor)
No visible mouse cusor
Visible mouse cursor
If I set default init level to 3, reboot, login as root, execute init 5, I do
have a visible mouse cursor. However, if the default init level is 5 when I
boot then there is no visible mouse cursor.
I believe this is a duplicate of bug #182517. Please disable or uninstall
Red Hat graphical boot (rhgb), and try to boot in runlevel 5. One person
in bug #182517 has indicated that disabling rhgb has made the problem vanish
I suspect that when you boot into runlevel 3 as indicated above, that you're
accomplishing the same thing indirectly - avoiding rhgb.
In general, having 2 X servers running at the same time on the same hardware
is a bad idea. This is a strong weakness in the Red Hat graphical boot
design which I wish had never happened, as it causes end users to experience
a lot of corner case bugs in the X server, video drivers, kernel, etc. which
one would never encounter under normal circumstances.
Alas, pretty boot seems to be more popular than "stable" to more people,
so rhgb won the war. Now we get to pick up the pieces. ;o)
Anyhow, let me know if disabling rhgb works around the problem for you too,
and this might help find a real solution sooner.
Thanks in advance.
Fedora Core 5 is no longer supported, please, could you reproduce this bug with
the updated version of the currently supported distribution (Fedora Core 6, or
Fedora 7, or Rawhide)? If this issue turns out to still be reproducible, please
let us know in this bug report. If after a month's time we have not heard back
from you, we will have to close this bug as CANTFIX/INSUFFICIENT_DATA.
Setting status to NEEDINFO, and awaiting information from the reporter.
Thanks in advance.
Can't test this until 175784 is fixed.
Do you have RHEL4 or FC5? (bug 175784 is against RHEL4)
If you have really FC5, I am afraid that this bug will be closed pretty soon,
unless you will be able to reproduce with the later version of Fedora. I would
suggest you upgrading to FC6 anyway (if you have really FC5 and not RHEL4 on
this computer), because even bug 175184 might be fixed in meantime.
See also https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=182517
which is closed, but contains a report that this bug is still in FC7. Is it
still worth testing FC6 if there are problems reported with both 5 and 7?
What is the correct way to report a bug that appears in multiple releases?
It's presumably the same problem with the same code if it keeps appearing over
and over again.
I have FC5, but it won't boot due to bug 175784. No fix is reported. Is
there really any hope that FC6 will boot on my system if I download it and try
to test it for you?
No, it isn't worth it. However, you are right this really looks like a duplicate
of bug 182517, so I am closing this bug (also because FC5 is not supported anymore).
Concerning FC6 -- yes, there is a lot of hope -- bug 175784 is against RHEL4,
which corresponds roughly to Fedora Core 3 (of course, updated all the time, but
still the core was once FC3). There was a huge development between FC3 and FC6
so it is quite possible that bug 175784 has been fixed in meantime.
*** This bug has been marked as a duplicate of 182517 ***