'mountall cannot connect to plymouth', followed by 'run-parts: /etc/update-motd.d/91-release-upgrade exited with return 1'

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage. I have classified this bug as a bug in mountall

I can confirm that i notice this message during bootup

Oh , oops..! I notice only this > "mountall cannot connect to plymouth" but I'm able to boot into the session properly

Is Bug #504219 a dup?

I am still stuck in tty1 - I will attach some .txt log files I obtained by accessing /var/log via my karmic installation. Hope they help. Some of the log files may include some of my (poor) attempts to fix the problem. One other issue is that nvidia-glx-185 package will not uninstall - I suspect that may be causing the reason for dropping into a shell.

Can you please be a bit more precise about what you mean with 'sutck in tty1' does gdm fail to start? Does it even try to start? If you're using kdm then please notice it's broken right now (bug 505627) and won't start on boot. Please login into a tty and start kdm with 'sudo start kdm' in this case. If you have a message that indicates a maintenance shell will be started you might have to press Ctrl+Alt+F2 to switch to TTY2 first if you can't use tty1 (bug 505583).

Thank you for your suggestion. I however use gnome and thus gdm - it doesn't start at all. Typing sudo start gdm gives the output
gdm start/running, process 1781
It does nothing else, except go to the next command prompt. tty2 did not do any better - same message, except the process was 1923 instead of 1781.

Ok, can you please run 'startx' from a terminal in this case? On IRC we
had cases where X segfaulted on start or the 'xserver-xorg' package was
removed on upgrade. Also please note that the Xorg packages are in a
pretty broken state in Lucid right now and it should get better for Alpha2.

On 01/11/2010 04:30 PM, Ian Mayne wrote:
> Thank you for your suggestion. I however use gnome and thus gdm - it doesn't start at all. Typing sudo start gdm gives the output
> gdm start/running, process 1781
> It does nothing else, except go to the next command prompt. tty2 did not do any better - same message, except the process was 1923 instead of 1781.
>

Lucid Lynx 10.04 Alpha 1 2.6.32.10 Boots to Cannot find Plymouth.

Does not make it to Splash screen and hangs. Same with 2.6.32.9 and 2.6.32.6

HP G71-340US with Intel core duo T6600

64 bit Lucid Lynx

Cannot boot into will supply more info when available.

start x does not do anything either, other give a whole lot of error messages, which I can't remember off the top of my head. I have also tried to reinstall xserver xorg and a number of other things - but so far nothing has looked close to sorting things out. I will keep doing updates and hope that it will sort itself out. Of course if there are any other suggestions, I will try them, but xorg and the nvidia driver seems pretty broken at present.

I have fixed the problem I was having with graphics and currently running in vesa mode - however, mountall does not connect to plymouth is still occuring

Install the vesa driver seems to solve that hangs, but you still get the plymouth warning. Anyway, I understand that the vesa driver should be in the system for video fallback, but somehow, was removed by some X upgrade...

The message 'mountall cannot connect to plymouth' seems to have gone with the last plymouth upgrade (0.8.0~-8)
Can anyone confirm this?

I have not had the plymouth problem for some time - I found that plymouth had not been installed ( for whatever reason),once installed the message went away.

Confirm that this warning that doesn't show up in version 0.8.0~-8

Good, I think this can be set fix released.

plymouth:
  Installato: 0.8.1-1ubuntu1
  Candidato: 0.8.1-1ubuntu1
  Tabella versione:
 *** 0.8.1-1ubuntu1 0
        500 http://archive.ubuntu.com/ubuntu/ lucid/main Packages
        100 /var/lib/dpkg/status

with latest plymouth i have message mountall cannot connect to plymouth

I also am getting the "mountall: cannot connect to plymouth" message on bootup with the latest updates to Lucid Netbook Edition on my Acer Aspire One.

I also am getting the "mountall: cannot connect to plymouth" message on bootup with the latest updates to Lucid on my Fujitsu siemens Amilo Xi 1526...

I am also having this problem with the latest release/ updates of Kubuntu 10.04 x86. My computer is a Dell XPS Studio16, model PP35L. For me there has been no real success no matter what the update. It has been an ongoing problem from the inception of Beta 1.

I am also getting this problem on my Gigabyte 945GZM-S2 motherboard with intel integrated graphics. After about fifteen seconds from boot I reach the desktop but no menus are there. It takes about another 25 seconds for the menus to appear. Everything is running well in Beta 1 now, except for this issue.