Description of Problem: After the installation completes (with the mouse having been configured during the installation and even used for the installation), kudzu detects the mouse as new hardware on the first boot after the installation (ps/2 mouse). Version-Release number of selected component (if applicable): 7.2 rc (0222.1 iso) How Reproducible: often Steps to Reproduce: 1. install, making sure that the ps/2 3-button mouse is configured 2. boot after install - is mouse detected as new hardware? Actual Results: Frequently mouse is seen as new hardware on first post-install boot Expected Results: mouse was configured during installation, it's not new hardware after installation Additional Information: This has been seen on DS10, DS20, ES45... the previous beta did not exhibit this behavior.
This is the unfortunate result of the anaconda tweak in combination with #58738; one potential fix is to only add '-s' to the kudzu args (in packages.py) if you're doing a serial install....
Looking at the anaconda I pushed, for the beta2 packages.py: argv = [ "/usr/sbin/kudzu", "-s", "-q" ] Are you saying I should drop the -q for a serial install only? Phil =--=
No, add the '-s' for the serial install only.
This is non issue as this behaviour no longer exists... closing Phil =--=