Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 590925 - "stty -onlcr"-looking console boot messages
Summary: "stty -onlcr"-looking console boot messages
Keywords:
Status: CLOSED DUPLICATE of bug 585128
Alias: None
Product: Fedora
Classification: Fedora
Component: plymouth
Version: 13
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-11 00:18 UTC by Roland McGrath
Modified: 2010-05-12 22:04 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-05-12 22:04:07 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Roland McGrath 2010-05-11 00:18:08 UTC 
Description of problem:

I'm not sure whose fault this is.  I'm using the vanilla graphical boot with default kernel args from a fresh install, and then hit ESC to see the messages.

I had done some rescue-mode fiddling and upon rebooting it was taking forever to I hit ESC to see messages and it was the "*** Warning -- SELinux ..." relabel message.  The lines following that one (three more '***" lines for that message) were stair-stepped, i.e. looking like output after "stty -onlcr".  All the lines with a green "OK" (before and after this) were terminated correctly.  Later messages (long after the end of rc.sysinit) that weren't the colorized OK or FAILED sort, also had the stair-step problem.

Version-Release number of selected component (if applicable):
initscripts-9.12-1.fc13.x86_64
plymouth-0.8.2-2.fc13.x86_64

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Ray Strode [halfline] 2010-05-12 22:04:07 UTC 
I think this is fixed in plymouth-0.8.3-3.fc13.x86_64.  There was a bug where we weren't properly unlocking the tty on shutdown (and presumably on escape)

I'm going to close this one out, but if installing plymouth-0.8.3-3.fc13 and rebuilding your initrd (with /usr/libexec/plymouth/plymouth-update-initrd) doesn't fix the issue, then please reopen and I will investigate further.

*** This bug has been marked as a duplicate of bug 585128 ***
Note You need to log in before you can comment on or make changes to this bug.