Ubuntu

plymouthd assert failure: plymouthd: ./plugin.c:697: open_input_source: Assertion `backend != ((void *)0)' failed.

Reported by Ing. Forigua on 2010-07-26
134
This bug affects 14 people
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
Medium
Unassigned

Bug Description

Binary package hint: plymouth

I work normally in gnome with ubuntu maverick and it crash

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: plymouth 0.8.2-2ubuntu3
ProcVersionSignature: Ubuntu 2.6.35-10.15-generic 2.6.35-rc5
Uname: Linux 2.6.35-10-generic i686
Architecture: i386
AssertionMessage: plymouthd: ./plugin.c:697: open_input_source: Assertion `backend != ((void *)0)' failed.
Date: Sun Jul 25 19:05:17 2010
DefaultPlymouth: /lib/plymouth/themes/kubuntu-logo/kubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
Lsusb:
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-10-generic root=UUID=0e216cf6-12c5-470b-a3d4-866bddc63146 ro quiet splash
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron: PATH=(custom, no user)
ProcFB: 0 nouveaufb
Signal: 6
SourcePackage: plymouth
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/libc.so.6
 abort () from /lib/libc.so.6
 __assert_fail () from /lib/libc.so.6
 ?? () from /lib/plymouth/renderers/frame-buffer.so
TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
Title: plymouthd assert failure: plymouthd: ./plugin.c:697: open_input_source: Assertion `backend != ((void *)0)' failed.
UserGroups:

dmi.bios.date: 03/03/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.32
dmi.board.name: 30CF
dmi.board.vendor: Quanta
dmi.board.version: 85.26
dmi.chassis.type: 10
dmi.chassis.vendor: Quanta
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnHewlett-Packard:bvrF.32:bd03/03/2009:svnHewlett-Packard:pn:pvrRev1:rvnQuanta:rn30CF:rvr85.26:cvnQuanta:ct10:cvrN/A:
dmi.product.version: Rev 1
dmi.sys.vendor: Hewlett-Packard

Ing. Forigua (ingforigua) wrote :
visibility: private → public

StacktraceTop:
 __kernel_vsyscall ()
 *__GI_raise (sig=6)
 *__GI_abort () at abort.c:92
 *__GI___assert_fail (
 open_input_source (backend=0x0, input_source=0x9184f38)

Changed in plymouth (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
MarkieB (ubunt-u-markbenjamin) wrote :

could it be that somehow thread synchronization is the cause? I'm connecting it to the general plymouth bug that is particularly noticeable in plymouth/nvidia interaction, the low chance of a desktop; as there when viewing the log messages, at times they are brief / few, at times there are more messages, it seems that possibly a successful boot is when there are more messages?

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in plymouth (Ubuntu):
status: New → Confirmed
Steve Langasek (vorlon) wrote :

According to the duplicates, this bug occurs with both the drm and the framebuffer renderers.

Stefan Felkel (stefan-felkel) wrote :

Hi, got this problem on 12.04, too.
Is there any workaround for that?

To post a comment you must log in.