Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Plymouth is a dependency of mountall which is a dependency of upstart.
So upstart pulls in plymouth.
However, this seems like a harmless error, no?
Agreed, it is harmless ... once I researched what it was. But it's still something behaving wrong. Plymouth should not be a hard dependency. It should be possible to just leave it out. Then mountall, and anything else using it, should either try to use it in a silent way (like how rm behaves for a file that does not exist), or test for it and skip it if not present. Maybe it should funnel through a separate "boot status" package of some sort, which then spreads the states out to packages like plymouth or any others (maybe I want the boot status to be spewed out of a serial port and so I write a package or program to handle that), based on what exists or is registered or configured to be used.
Plymouth should not be a hard dependency. It should be possible to just leave it out.
All you really need is libplymouth2 and libplymouth-dev to rebuild it
Package requirements (ply-boot-client >= 0.8.0) were not met:
No package 'ply-boot-client' found
Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.
Alternatively, you may set the environment variables PLYMOUTH_CFLAGS
and PLYMOUTH_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
Hello Sorry this is an old post but I run into this problem yesterday at a client's place after installing ubuntu 12.04.2 LTS server 64bits with RAID 1
After I finished the installation and handed over the credentials to their techincal team, they have misplaced it and attempted to reinstall the OS.This problem didn't show up the first time. but after erasing the content of the RAID devices and reisntalling the OS this issued popped up. I had to press on enter before the log in shows up. From reading google I needed to reinstall this plymouth-theme-ubuntu-text or rebuild? not very clear but below are the links talking about this.