From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040806 Firefox/0.9.3 Description of problem: When booting up if I hit enter to show the boot details the first few lines of ouput are jumbled together and corrupted. I've seen this with fc3t2 as well. It happens on multiple machines with different graphics hardware. It doesn't actually look like a problem with the graphics. It looks like a problem with rhgb. Its almost like its not sending a line feed properly or something. Version-Release number of selected component (if applicable): 0.13.5-2 How reproducible: Always Steps to Reproduce: 1. boot 2. hit enter to see boot details once in graphical mode 3. watch for corrupted lines at top of screen Actual Results: first few boot messages are jumbled together Expected Results: display all boot messages correctly Additional info: ati included open source driver in an ibm laptop nvidia commercial driver with a GF5900ultra
What locale?
i just hit 'next' through the installer using all the English defaults.
I have tried rhgb on Matrox, ATI, Dell laptop with either opensource or binary Nvidia driver and didn't see the problem myself. Since it comes from very early on, either 1/ it's an rhgb bug around the new rhgb-console output 2/ it's a weird vte initialization 3/ for some reason the initscripts drop garbage in rhgb-console 4/ this is some newline handling bug for rhgb-console handling Seems 4/ is the most likely, but I don't fully understand what is being seen "jumbled together and corrupted" is not very precise. Some kind of dump of the text seen would be better, Daniel
is there any kind of screen capture capability in rhgb?
no, rhgb starts on a very very minimal system. Daniel
Same here. The first few lines of initscript output in detailed rhgb screen overwrite eachother and are printed in different order than when booting in text mode. It's as if no linefeeds are executed. After "Enabling local filesystem quotas:" everything is okay here.
Caused by a bug in initscripts, should be fixed in next initscripts release. *** This bug has been marked as a duplicate of 192604 ***