plymouthd assert failure: plymouthd: ply-text-display.c:243: ply_text_display_write: Assertion `format != ((void *)0)' failed. (empty title field in text plugin theme)

Bug #758657 reported by Aquilon
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

Binary package hint: plymouth

error plymouth

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: plymouth 0.8.2-2ubuntu21
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
AssertionMessage: plymouthd: ply-text-display.c:243: ply_text_display_write: Assertion `format != ((void *)0)' failed.
CrashCounter: 1
Date: Mon Apr 11 22:22:19 2011
DefaultPlymouth: /lib/plymouth/themes/MIB-Ubuntu/MIB-Ubuntu.plymouth
ExecutablePath: /sbin/plymouthd
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100427.1)
MachineType: Packard Bell imax mini N3600
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron: PATH=(custom, no user)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic root=UUID=ce2b9275-96f5-4c53-a24c-00d0c9321002 ro acpi_enforce_resources=no quiet splash vt.handoff=7
Signal: 6
SourcePackage: plymouth
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/i386-linux-gnu/libc.so.6
 abort () from /lib/i386-linux-gnu/libc.so.6
 __assert_fail () from /lib/i386-linux-gnu/libc.so.6
 ply_text_display_write () from /lib/libply-splash-core.so.2
TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
Title: plymouthd assert failure: plymouthd: ply-text-display.c:243: ply_text_display_write: Assertion `format != ((void *)0)' failed.
UpgradeStatus: Upgraded to natty on 2011-04-08 (3 days ago)
UserGroups:

dmi.bios.date: 06/09/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: R01-A2
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: FMCP7A-ION
dmi.board.vendor: Packard Bell
dmi.chassis.type: 3
dmi.chassis.vendor: Packard Bell
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A2:bd06/09/2009:svnPackardBell:pnimaxminiN3600:pvr:rvnPackardBell:rnFMCP7A-ION:rvr:cvnPackardBell:ct3:cvr:
dmi.product.name: imax mini N3600
dmi.sys.vendor: Packard Bell

Revision history for this message
Aquilon (marc-descharles) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __kernel_vsyscall ()
 raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
 abort () at abort.c:92
 __assert_fail (assertion=0x9d11fb "format != ((void *)0)", file=0x9d11c0 "ply-text-display.c", line=243, function=0x9d12e2 "ply_text_display_write") at assert.c:81
 ply_text_display_write (display=0x9477588, format=0x0) at ply-text-display.c:243

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
Steve Langasek (vorlon) wrote : Re: plymouthd assert failure: plymouthd: ply-text-display.c:243: ply_text_display_write: Assertion `format != ((void *)0)' failed.

This crash happens when the text plugin tries to write the distribution name and version to the screen. The name is taken from the 'title' field of /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth, but in this case it appears to be empty. Please attach a copy of this file from your system to the bug.

Changed in plymouth (Ubuntu):
status: New → Incomplete
summary: plymouthd assert failure: plymouthd: ply-text-display.c:243:
- ply_text_display_write: Assertion `format != ((void *)0)' failed.
+ ply_text_display_write: Assertion `format != ((void *)0)' failed. (empty
+ title field in text plugin theme)
visibility: private → public
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for plymouth (Ubuntu) because there has been no activity for 60 days.]

Changed in plymouth (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Steve Langasek (vorlon) wrote :

hmm; we don't want this to expire out because there is a confirmed bug here, but I would still appreciate getting a copy of the file in question.

Changed in plymouth (Ubuntu):
status: Expired → Triaged
Revision history for this message
avinash pawar (avinashupawar30) wrote :

hello friends i was to find out solution for the error message i got while attempting to install UBUNTU 12.04 LTS, and the only
result on google search were three pages, out of those three i am trying to write on this page.

the error:
plymouthd: ply-text-display.c243: ply_text_display_write: Assertion format '!= ((void)=*0)'failed

I bought a Dell Vosrto 14 3000 series a week ago, which had UBUNTU 12.04 already installed. I want Windows 8 as well as UBUNTU on my new laptop. I am willing to learn UBUNTU and i really know and understand nothing about UDUNTU as of now.

What I told was that I cant install Windows 8 on UBUNTU but can vice a versa. So I took backup of UBUNTU on a pen drive, uninstalled UBUNTU and installed Windows 8 on one of three partitions. and i m now trying to install UBUNTU on another. While doing so i get the above mentioned error.

i really do not know what's happening and i want to be able to use Windows as well as UBUNTU on my laptop.

Could somebody be kind enough to explain me how to resolve this issue and could really somebody give me step to step instructions to successfully install UBUNTU. Also i request to tell me the required changes i need to do in the BIOS setup and in Windows 8 in order to start the installation. All i could do till now is disable the Secure Boot, Fast Boot, and I use My Pen Drive to boot the UBUNTU. Also, I have created 3 partitions while installing Windows 8 and the partition on which Windows 8 is installed shows BASIC type while the remaining 2 show DYNAMIC type.

Thanking you friends.

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.