Plythouth doesn't start with --attach-to-session

  I can confirm this on both the MSI Wind U100 with Intel graphic and on an AMD Phenon II x4 with nvidia graphics.

Text seems to be involved in a lot of bugs in plymouth: --attach-to-session redirects text from console to log, and the password prompt and message bugs also involves text.

For me it just removes the error message, "Mountall-could not connect to Plymouth"
ATIX300-Open source driver

@plun:For me it just removes the error message, "Mountall-could not connect to Plymouth"
ATIX300-Open source driver

+1
ATI HD3650-xorg-edgers

Sorry, I forgot to mention: It works with 2.6.32-9 and with this patch warning is gone.
It doesn't work with 2.6.33-999.

@zika, correct, I was running 2.6.33-RC2 from Ubuntu Mainline
and it works just fine with Lucids kernel, 2.6.32-9.

Thanks !

At one point I found that I had mistakenly set Plymouth to use the text splash rather than a graphic one resulting in not seeing/noticing Plymouth during boot. Switching back to a graphic one, ubuntu-logo, I was able to see the screen.

I did my troubleshooting by breaking the boot process and working at the (initramfs) shell prompt.
(see here https://wiki.ubuntu.com/DebuggingKernelBoot)

At the grub menu:
1. Press 'e' to edit the boot commands.
2. At the end of the line starting with linux:
    a. Remove "quiet"
    b. Add "break=modules"
3. Press Ctrl-x to boot.
     - It will drop you into (initramfs) immediately after the scripts in
        "/scripts/init-top/" are run.
     - If plymouth is running you will see the splash.
       You can blindly type "plymouth --hide-splash<enter>" to see (initramfs)

Confirm that plymouthd fails if run with --attach-to-session
4. (initramfs) /sbin/plymouthd --mode=boot --attach-to-session --pid-file=/dev/.initramfs/plymouth.pid
5. (initramfs) ps |grep `cat /dev/.initramfs/plymouth.pid`
     - shows that plymouthd is not running despite the presence
       of /dev/.initramfs/plymouth.pid

Show that plymouthd runs without --attach-to-session
6. (initramfs) rm /dev/.initramfs/plymouth.pid
7. (initramfs) /sbin/plymouthd --mode=boot --pid-file=/dev/.initramfs/plymouth.pid
8. (initramfs) ps |grep `cat /dev/.initramfs/plymouth.pid`
     - plymouthd should be running

Test plymouth splash screen and continue boot process:
9. (initramfs) plymouth --show-splash && exit
    - Should see plymouth splash screen and boot process should continue

Sorry should have mentioned my graphics chipset.

$ lspci
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GME Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)

Tried to rebuild plymouth with tracing and got a bit more information. Looks like it is "session->pseudoterminal_master_fd = posix_openpt (O_RDWR | O_NOCTTY);" that fails in open_pseudoterminal function. The statement returns -1 and errno is set to "No such file or directory". The strange thing is that /dev/ptmx exists. Maybe it is due to some permission issues?

Hope above can help someone to nail down this bug.

This bug was fixed in the package plymouth - 0.8.0~-7

---------------
plymouth (0.8.0~-7) lucid; urgency=low

  * Fixed a bug where we couldn't load the script plugin if it were
    compiled without optimisations.
  * Attempt to work around issues with VT switching and fbcon reasserting
    over our output. LP: #496784, #497115.
  * Don't attach to the session for now, this code path doesn't work with
    the current console/VT code. LP: #502494.
 -- Scott James Remnant <email address hidden> Mon, 11 Jan 2010 13:47:36 +0000

Just up graded and it works nicely now.

The message just reapear in the new update:

$ apt-cache policy plymouth
plymouth:
  Instalados: 0.8.1-1ubuntu1
  Candidato: 0.8.1-1ubuntu1
  Tabla de versión:
 *** 0.8.1-1ubuntu1 0
        500 http://archive.ubuntu.com/ubuntu/ lucid/main Packages
        100 /var/lib/dpkg/status

$ uname -a
Linux laptop 2.6.32-17-generic-pae #26-Ubuntu SMP Sat Mar 20 01:28:23 UTC 2010 i686 GNU/Linux

Please file a separate bug report.