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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1082742 Title: plymouthd: ply-terminal.c: 611 ply_terminal_open: Assertion `terminal != ((void *)0)' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1082742/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
