[Bug 521298] Re: could not write byte broken pipe

[MightyPork]

I can confirm this bug is still present in Kubuntu 12.04, I decided to
upgrade my system to get new KDE and all these security fixes, but this
bug was obviously included as a bonus. The update came from kubuntu-
backports.

It does not show the splash animation, only the text-only logo with flashing dots. 
At the end, something about broken pipe and writing bytes appears for a moment, then it either dies and shows the F1 login prompt, or - sometimes - it proceeds to KDM and lets me log in normally.

I tried to find "broken pipe" in system logs, with no success.

After logging into the console at F1, startx seems to work all right.

-- 
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/521298

Title:
  could not write byte broken pipe

Status in “plymouth” package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: plymouth

  When I boot up the latest lucid livecd i get the message "Could not
  write byte, broken pipe" in the middle of the screen while the three
  colored bars are filling up at the bottom of the screen.

  Just a cosmetic bug, ubuntu started afterwards.

  ProblemType: Bug
  Architecture: amd64
  Date: Sat Feb 13 08:09:00 2010
  DistroRelease: Ubuntu 10.04
  LiveMediaBuild: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100210)
  Package: plymouth 0.8.0~-9
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-12.17-generic
  SourcePackage: plymouth
  Uname: Linux 2.6.32-12-generic x86_64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/521298/+subscriptions