(replying to Ed, Samuel, and Patrick) The upgrade phase (step 7) generated a line of output for each package(?) being upgraded. The clean-up phase (step 7) generated a line of output for each upgraded package(?). The verify phase (step 7) generated a line of output for each upgraded package(?). Then came the automatic reboot. After the grub menu disappeared,... The left rectangle brightened, then dimmed. Then the middle rectangle brightened, then dimmed. Then the right rectangle brightened, then dimmed. A bunch of error messages (ACPI errors, addressed in a prior thread, back in May) flew by. Then 15+ minutes of nothing but black screen with slowly blinking cursor. I have a 3+ gigahertz quad-core chip, and 16 gb memory. I don't know the speed rating of the hard drive, but it has plenty of empty space. 15+ minutes of black screen with one slowly blinking cursor had me thinking something was "stuck", caught in a loop, aborted, crashed, or something else nasty. Processes that take a while should generate output somehow indicating progress, as does * dnf's download, upgrade, clean-up, and verification phases; * file browsers when copying large amounts of files to a usb stick (a growing percent done bar, or a pie chart gradually filling in). * k3b when copying stuff to a cd/dvd/blu-ray; * (many other examples). Question: If I were to submit an enhancement request bugzilla on this, would it likely get done (preferably in time for Fedora 28)? If yes, then Question: Which bugzilla (or other tracking system) should I use (please provide url)? Endif. Ed: When I had fedora HYPERKITTY issues in early July, Kevin Fenzi referred me to the Fedora infrastructure site: "https://pagure.io/fedora-infrastructure/issues"; to report the issues. I submitted issue #6146 in response. Thank-you. Bill. _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
