plymouthd: ply-keyboard.c assertion failed

Bug #586076 reported by Mike Bianchi
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
NULL Project
Invalid
Undecided
Unassigned
plymouth (Ubuntu)
New
Undecided
Unassigned

Bug Description

I see the following line on the console

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

I have not found any core file.

affects: upstart → null
Changed in null:
status: New → Invalid
Revision history for this message
Mike Bianchi (mbianchi-foveal) wrote : Re: [Bug 586076] Re: plymouthd: ply-keyboard.c assertion failed

What does this mean?
Not a bug?
Not a problem?
        Mike

On Thu, May 27, 2010 at 09:20:45AM -0000, Scott James Remnant wrote:
> ** Project changed: upstart => null
>
> ** Changed in: null
> Status: New => Invalid
>
> ** Also affects: plymouth (Ubuntu)
> Importance: Undecided
> Status: New
>
> --
> plymouthd: ply-keyboard.c assertion failed
> https://bugs.launchpad.net/bugs/586076
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in NULL Project: Invalid
> Status in “plymouth” package in Ubuntu: New
>
> Bug description:
> I see the following line on the console
>
> plymouthd: ply-keyboard.c:384: ply_keyboard_watch_for_input: Assertion `keyboard != ((void *)0)' failed.
>
> I have not found any core file.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/null/+bug/586076/+subscribe

--
 Mike Bianchi
 Foveal Systems

 973 822-2085

 <email address hidden>
 http://www.AutoAuditorium.com
 http://www.FovealMounts.com

Revision history for this message
Blastoff (wolph) wrote :

I also get the above assertion error at start-up.

I have a Logitech keyboard and Logitech mouse connected to PS/2 ports and a Microsoft wireless USB dongle that I use for another mouse. There is also a keyboard that's supposed to go along with the MS wireless thing but that is not present.

I have
init='/sbin/init --verbose' ro nosplash
set as boot options, which may be necessary to see the error flash by.

Revision history for this message
Blastoff (wolph) wrote :

Using Lucid Lynx BTW

Revision history for this message
stiV (stefan-wehinger) wrote :

There is a similar fedora bug report. I too see this error (when adding --verbose), no idea where it's coming from.
I did try to boot using a debian initramfs, it works there...
https://bugzilla.redhat.com/show_bug.cgi?id=604927

Revision history for this message
Hobson Lane (hobs) wrote :

Identical error on Lucid Lynx (Ubuntu 10.04 LTS, dully updated to 2.6.32-24-generic) on Dell Inspiron laptop.
This may be related to an upstart problem. Upstart fails to launch some daemons like apache and mysql on my laptop ever since upgrade of kernel and some failed hibernation/suspend/resume cycles.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.