Bug 604927 - plymouthd ply-keyboard assertion error
Summary: plymouthd ply-keyboard assertion error
Alias: None
Product: Fedora
Classification: Fedora
Component: plymouth   
(Show other bugs)
Version: 13
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2010-06-17 02:39 UTC by Wendall Cada
Modified: 2011-06-02 17:59 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2011-06-02 17:59:16 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Wendall Cada 2010-06-17 02:39:38 UTC
plymouthd hangs for almost ten minutes before resuming after throwing the following error:

plymouthd: ply-keyboard.c:384: ply_keyboard_watch_for_input: Assertion 'keyboard != ((void *)0)' failed.


Hardware is a  Lenovo Y530 Ideapad with an Intel GM45

Additionally, if I open and close the cd tray when plymouthd throws the error, boot continues normally.

Instead of waiting for a patch that might fix this error. Is there a way to force plymouthd to start regardless of errors, like shorten the time it's waiting on whatever the heck it does?  Would be nice to have some idea how to debug this.

Comment 1 Marek Zdunek 2010-10-31 08:48:03 UTC
I have the same error, but system boots and runs fine
It started when enabled bootchart

system run:

Comment 2 Bug Zapper 2011-06-02 10:32:27 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 

Comment 3 Ray Strode [halfline] 2011-06-02 17:59:16 UTC
this was fixed some time ago i believe

Note You need to log in before you can comment on or make changes to this bug.