Bug 869067 - unable to change plymouth themes
Summary: unable to change plymouth themes
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F18-accepted, F18FinalFreezeExcept
TreeView+ depends on / blocked
 
Reported: 2012-10-22 22:41 UTC by Dan Mashal
Modified: 2012-11-26 14:12 UTC (History)
9 users (show)

Fixed In Version: anaconda-18.22-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-11-21 16:55:45 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Dan Mashal 2012-10-22 22:41:44 UTC 
[root@localhost dan]#  plymouth-set-default-theme -R mate
/etc/sysconfig/keyboard: line 1: vconsole.keymap=us: command not found
Comment 1 Dan Mashal 2012-10-22 22:52:40 UTC 
correction, the theme changes but gives that error.
Comment 2 Bill Nottingham 2012-10-23 20:58:59 UTC 
99% sure that error is coming from dracut.
Comment 3 Jens Petersen 2012-10-30 03:27:17 UTC 
Why do we need both /etc/vconsole.conf and /etc/sysconfig/keyboard?
Comment 4 Harald Hoyer 2012-11-19 13:23:58 UTC 
This seems like a wrong entry in /etc/sysconfig/keyboard

/etc/sysconfig/keyboard: line 1: vconsole.keymap=us:

and no.. this is _not_ dracut stuff.. Somebody/something has misconfigured /etc/sysconfig/keyboard
Comment 5 Bill Nottingham 2012-11-20 16:03:41 UTC 
This was a bug in an earlier anaconda build. However, I'm pretty sure it's been fixed. Can you reproduce this with current TC trees?
Comment 6 Chris Lumens 2012-11-21 16:55:45 UTC 
commit 96f844476268cefbc8779d037be386834974fd0a
Author: Bill Nottingham <notting>
Date:   Thu Oct 25 23:56:25 2012 -0400

    /etc/sysconfig/keyboard doesn't support vconsole.xyz options.
Comment 7 Kamil Páral 2012-11-26 14:12:46 UTC 
Removing CommonBugs because this has been fixed before F18 Beta release.
Note You need to log in before you can comment on or make changes to this bug.