← Back to team overview

desktop-packages team mailing list archive

[Bug 1364630] Re: init: Error while reading from descriptor: Broken pipe


Most of this is way over my head.  Man, do I envy and admire all you who are light years ahead of this 59 yr. old who never touched a computer until a few yrears ago.  I'm posting this for the many newbie users out there like me.
  I too was getting the "init: Error while reading from descriptor: Broken pipe" error in Lubuntu 14.10 with Nvidia GE 7300 Force using the recommended Nvidia 304 drivers (I got the error most of the time- but not always- although the boot always completed and I was always able to use the machine with no other errors).
  It just bugged me enough to start researching the error.  I've read all the posts above and I'm really confused now.  From the posts it seems the concensus is that its not necessarily Nvidia-related, but I decided anyhow to revert back to the basic Nouveau drivers...just for giggles and kicks.... the error is no more, and Lubuntu still seems to be flawless. Hmmm.
  Maybe this will help someone who gets the error and can't even get their machine to boot.  Worth a try.

You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.

  init: Error while reading from descriptor: Broken pipe

Status in Upstart:
Status in nvidia-graphics-drivers-304 package in Ubuntu:

Bug description:
  [   16.934379] init: Error while reading from descriptor: Broken pipe

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: init 1.20ubuntu3
  ProcVersionSignature: Ubuntu 3.16.0-11.16-generic 3.16.1
  Uname: Linux 3.16.0-11-generic x86_64
  ApportVersion: 2.14.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Sep  2 17:23:15 2014
  InstallationDate: Installed on 2014-04-27 (128 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2)
  SourcePackage: init-system-helpers
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to: