[Bug 1082742] Re: plymouthd: ply-terminal.c: 611 ply_terminal_open: Assertion `terminal != ((void *)0)' failed.
Jay Zee
jayzee at electriczen.com
Wed Feb 5 17:01:03 UTC 2014
Just a bit of extra info -- it's possible that this has been mentioned
before.
I am using Acer C710-2834 with Chrome OS installed via s9ryd script.
In my case there are two (2) distinct behaviors.
1. Happens when the Chromebook is Running on Battery power.
The message >>> plymouthd: ply-terminal.c:611: ply_terminal_open: Assertion 'terminal != ((void *)0)' failed
appears and stays on the screen (forever, I guess).
The log-in screen will not appear by itself.
To get to the log-in screen, I have to close the cover and then reopen it.
At various tries, different elements of the log-in screen will appear but I typically get the password text box.
Typing the password will get me to the desktop.
2. Happens when the Chromebook is Running on Power Supply / Mains (the battery is inserted and "charging")
The message >>> plymouthd: ply-terminal.c:611: ply_terminal_open: Assertion 'terminal != ((void *)0)' failed
appears and stays on the screen for short time (2 to 3 sec).
The fully rendered and working log-in screen will appear by itself.
Typing the password will get me to the desktop.
Hope this helps
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to plymouth in Ubuntu.
https://bugs.launchpad.net/bugs/1082742
Title:
plymouthd: ply-terminal.c: 611 ply_terminal_open: Assertion `terminal
!= ((void *)0)' failed.
Status in “plymouth” package in Ubuntu:
Confirmed
Bug description:
Plymouth on Chromebook always ends with this message. I added manual
overrides for all plymouth jobs in /etc/init/ but I am tired of
telling each user how to work around a problem.
There were suggestions that this is because of kernel cmdline: "cros_secure console= console=tty1 printk.time=1 quiet nosplash rootwait root=/dev/mmcblk0p7 rw loglevel=0" because plymouth only takes first one while kernel is using the last one...
---
ApportVersion: 2.6.2-0ubuntu5
Architecture: armhf
DefaultPlymouth: Error: command ['readlink', '/etc/alternatives/default.plymouth'] failed with exit code 1:
DistroRelease: Ubuntu 13.04
MarkForUpload: True
Package: plymouth 0.8.8-0ubuntu1
PackageArchitecture: armhf
ProcCmdLine: cros_secure console= console=tty1 printk.time=1 quiet nosplash rootwait root=/dev/mmcblk0p7 rw loglevel=0
ProcFB: 0
ProcKernelCmdLine: cros_secure console= console=tty1 printk.time=1 quiet nosplash rootwait root=/dev/mmcblk0p7 rw loglevel=0
Tags: raring
TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
Uname: Linux 3.4.0 armv7l
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip plugdev video
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1082742/+subscriptions
More information about the foundations-bugs
mailing list