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

Bug #619021 reported by Chris J
122
This bug affects 20 people
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: plymouth

One minute X is there, the next it's not. This happened while trying to get it back.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: plymouth 0.8.2-2ubuntu2
ProcVersionSignature: Ubuntu 2.6.32-24.39-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-generic i686
Architecture: i386
AssertionMessage: plymouthd: ply-keyboard.c:384: ply_keyboard_watch_for_input: Assertion `keyboard != ((void *)0)' failed.
Date: Tue Aug 17 02:11:49 2010
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
MachineType: Acer Aspire 3610
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: root=UUID=a04bb17f-998b-4045-9ff3-1d731de0ef08 ro resume=/dev/sda2 gfxpayload=true crashkernel=384M-2G:64M,2G-:128M
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron: PATH=(custom, no user)
ProcFB: 0 inteldrmfb
Signal: 6
SourcePackage: plymouth
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/tls/i686/cmov/libc.so.6
 abort () from /lib/tls/i686/cmov/libc.so.6
 __assert_fail () from /lib/tls/i686/cmov/libc.so.6
 ply_keyboard_watch_for_input ()
TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
Title: plymouthd assert failure: plymouthd: ply-keyboard.c:384: ply_keyboard_watch_for_input: Assertion `keyboard != ((void *)0)' failed.
UserGroups:

dmi.bios.date: 09/26/2005
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: V1.07
dmi.board.name: Morar
dmi.board.vendor: Acer
dmi.board.version: Rev
dmi.chassis.asset.tag: None
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.07:bd09/26/2005:svnAcer:pnAspire3610:pvr0100:rvnAcer:rnMorar:rvrRev:cvnAcer:ct10:cvrN/A:
dmi.product.name: Aspire 3610
dmi.product.version: 0100
dmi.sys.vendor: Acer

Revision history for this message
Chris J (chriscf) wrote :
Chris J (chriscf)
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __kernel_vsyscall ()
 *__GI_raise (sig=6)
 *__GI_abort () at abort.c:92
 *__GI___assert_fail (
 ply_keyboard_watch_for_input (keyboard=0x0)

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in plymouth (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Ayke (ayke) wrote :

Compiz restarted (also some strange bug). Then a few seconds nothing happened. Then this bug appeared. There were errors while mounting devices (dropped to root shell, fixed fstab, Ctrl+D to retry, and the login window appeared). Other times when Compiz restarted I didn't have this bug.

Changed in plymouth (Ubuntu):
status: New → Confirmed
Steve Langasek (vorlon)
Changed in plymouth (Ubuntu):
status: Confirmed → Fix Committed
Revision history for this message
Azmodeus (azmodeus) wrote :

Error in my system with booting:
root/kernel args args nosplash
or args w/o splash option

work normally with splash option

vga=792 incompatible with splash

Sorry my bad English, I'm @#$@#$ hungarian :'( :'(
Azmodeus

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package plymouth - 0.8.2-2ubuntu29

---------------
plymouth (0.8.2-2ubuntu29) precise; urgency=low

  * debian/patches/main-Don-t-watch-for-keyboard-input-if-no-keyboard.patch:
    Cherry-pick from upstream; don't watch for keyboard input if no keyboard
    is set, as is the case when should_ignore_show_splash_calls() returns
    true, fixing an assert failure. LP: #619021.
  * debian/ubuntu-logo.png: remove in favor of the logo included in the
    ubuntu-logo theme which has the correct branding. This has no impact on
    the default user experience, but fixes the branding when using certain
    non-default themes available in the archive. (We still ship a copy in
    the main plymouth package for this reason.) LP: #667262.
  * debian/patches/tty1-after-boot.patch: Switch back to tty1 on exit if
    started with vt.handoff. Closes LP: #913731.
  * debian/plymouth-theme-{k,}ubuntu-text.{triggers,postinst}: regenerate
    our theme when /etc/lsb-release changes. LP: #957380.
 -- Steve Langasek <email address hidden> Wed, 11 Apr 2012 04:59:54 +0000

Changed in plymouth (Ubuntu):
status: Fix Committed → Fix Released
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.