init: Error while reading from descriptor: Broken pipe

[Cristian Aravena Romero]

[ 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)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[dehein (dehein)]

Came up after installing the nvidia 331.89 driver from the Driver tool, in Ubuntu Gnome 14.10

[Alexander Gabriel (einalex)]

This also happens on systems that neither have nvidia graphic cards nor the nvidia driver installed

[Alexander Gabriel (einalex)]

Uhm erong bug report. Disregard my last comment please

[Kaspar Tint (kaspar-tint)]

Can confirm, this messes up my Plymouth splash also.

[kbngmal (s-missions)]

Confirmed. It seems to be something to do with xconsole :

one@one-P35:/var/log$ cat syslog|grep pipe
Oct 24 12:17:24 one-P35 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Oct 24 12:26:58 one-P35 kernel: [ 24.812375] init: Error while reading from descriptor: Broken pipe
Oct 24 12:26:58 one-P35 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Oct 24 12:36:40 one-P35 kernel: [ 23.837473] init: Error while reading from descriptor: Broken pipe
Oct 24 12:36:40 one-P35 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]

[kbngmal (s-missions)]

From dmesg|grep pipe :

[ 4.615130] random: nonblocking pool is initialized
[ 6.403587] init: plymouth-upstart-bridge main process (173) terminated with status 1
[ 6.403597] init: plymouth-upstart-bridge main process ended, respawning
[ 6.404797] init: plymouth-upstart-bridge main process (189) terminated with status 1
[ 6.404806] init: plymouth-upstart-bridge main process ended, respawning
[ 6.406101] init: plymouth-upstart-bridge main process (191) terminated with status 1
[ 6.406109] init: plymouth-upstart-bridge main process ended, respawning
[ 23.837473] init: Error while reading from descriptor: Broken pipe
[ 23.839118] init: failsafe main process (619) killed by TERM signal

[Bryan Hill (brhill45)]

Appeared after installing nvidia 331 drivers

[Dan Cropley (teracow+tcnp6113srq)]

Also present in Kubuntu 14.10

[Gannet (ken20001)]

Also have this problem in Kubuntu 14.10:

kernel: [ 36.205270] init: Error while reading from descriptor: Broken pipe

[Mark Fraser (launchpad-mfraz)]

Upgraded to Kubuntu 14.10 and I now have:
[ 16.461669] init: Error while reading from descriptor: Broken pipe

[Philip Collins (pa-collins)]

I am also experiencing this message. A couple of the previous posts mentioned experiencing the problem after installing Nvidia 331 drivers. Although I do have Nvidia, I was (and still am) on version 304. Not sure if that's significant, though.

[Philip Collins (pa-collins)]

Forgot to mention ....message started appearing after upgrading to kubuntu 14.10

[Muhammad Gelbana (m-gelbana)]

I was recently using Ubuntu 14.04 and I upgraded to 14.10. I'm not sure if this error was being logged before but now I can see it clearly because it replaces the splash screen (plymouth) which doesn't appear at all. I'm using Unity.

Message: init: Error while reading from descriptor: Broken pipe
Log file: /var/log/dmesg

[Springnuts (simon-springnuts-orangehome)]

Affected. Appeared after upgrading to 14.10 from 14.04. ?related to inability to set wallpaper and to clear last window above destktop - see https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1385457

Springnuts.

[Springnuts (simon-springnuts-orangehome)]

Have updated BIOS but problem remains.

[Si Dedman (si-dedman)]

Overwrote existing but incorrectly configured 340.46 nvidia driver with nvidia current (316 I think)? Rebooted, have this problem now, xubuntu won't start.

[Roland (Rolandixor) Taylor (rolandixor)]

Affects multiple flavours.

[Cavsfan (cavsfan)]

I just got this again with Utopic Mate Remix and I have 331.89 Nvidia drivers installed.

[William Lee (wlee753159)]

I don't have Nvidia graphics but I still get this error

[Tele Laci (laci-tele)]

I can make it disappear, but I'm not sure what is the real cause :

$ sudo sed -i "s,or starting rc-sysinit,or spawned rc-sysinit," /etc/init/failsafe.conf

A patch in failsafe.conf and its gone.

[Tele Laci (laci-tele)]

I don't have nvidia driver nor nvidia anything.
This bugreport is in wrong place, it affects others as well, not the nvidia-driver.

[Tele Laci (laci-tele)]

In my experience this bug will occur in Utopic (not in Trusty) upstart network initializaton, if DHCP is set ( not static )
It has nothing to do with the display drivers.

[Dan Cropley (teracow+tcnp6113srq)]

yes, same here - Trusty was OK, error only started in Utopic, and I'm using DHCP.

[Mark Fraser (launchpad-mfraz)]

I'm not using DHCP on Utopic and I am getting the error. On my desktop I am using nVidia drivers and I get the error, on an Intel laptop I also get the error.

[Aaron Planell (aaronplanell)]

I have the same problem. Two weeks with out Linux :(

[guerin (valereguerin)]

I have AMD graphic driver FGLRX-update ! and i have the same problèm ! it' not a problem "Nvidia Driver" !!!!

ubuntu 14.10 utopic Unicorn sous Unity 7.3.1 winows manager : compiz
xorg 1.16.0
Binutils 2.24.90.2141014 gcc 4.9.1 Linux C Lib 2.19 GNU Make 4.0
Intel proc i7 930
R9 280 HD radeon !!!!! with Gallium 0.4 on AMD TAHITI
Architecture: amd64
SSD samsung 840 evo 500g
Gigabyte G1 Sniper
6 giga Ram ddr3
Open GL version 3.0 Mesa 10.3.0
client glx version 1.4
Serveur glx vendor SGI/1.4

I can't boot with Kernel 3.16 but i can with my old kernel !!!!
i have the message with my old kernel 3.13.0.38 generic when i boot it (error while reading descriptor : broken pipe)but i can use it without problem....sorry for the other

[Iraklis Tsoupouroglou (irtsoup)]

I upgraded from Kubuntu 14.04 to 14.10 and I am, too, affected by this. I do "wear" the nvidia drivers, but I can't seem to correlate this issue with the drivers. Although, this message appears on my start up screen, I can actually log in and work like I usually do without any glitches. :/

[Alex (alex-volos)]

Hello

I upgraded from Ubuntu 14.04 to 14.10 yesterday and I also get this warning.
I am using an NVIDIA card too.

[jldr (jldr)]

I upgraded from Ubuntu 14.04 to 14.10 and I also get this warning.
I am using an NVIDIA card too.

AMD Athlon(tm) 64 X2 Dual Core Processor 4600+ × 2 4 Gio memory
GeForce 7300 GT/PCIe/SSE2

[ 0.997148] Corrupted low memory at ffff88000000fe68 (fe68 phys) = 380000a210
[ 0.997199] Memory corruption detected in low memory
[ 1.928035] ata4: softreset failed (device not ready)
[ 1.928097] ata1: softreset failed (device not ready)
[ 24.458468] init: Error while reading from descriptor: Broken pipe

[A. Eibach (andi3)]

Wish I knew *WHERE* this "error while reading" message comes from!

"init" can mean quite a lot.

On Ubuntu & flavors, /sbin/init is actually init from upstart package. But just FWIW, I've grep'd recursively (-ir) for both "broken pipe" and "error while reading" messages. None there.

So this "init: Error while..." must come from the kernel itself.

[A. Eibach (andi3)]

Wait...

Found a match on this error message in 'io.c' which is part of libnih, which on its part is needed by /sbin/init.
So if anyone wants to debug the reason of this, he should start debugging libnih (even adding a printf will do to see what's going on) and check what (illegal?) parameter is fed into it.

[Roland Meier (rm369)]

Nov 15 12:36:51 hp8740w kernel: [ 19.613358] nvidia: module verification failed: signature and/or required key missing - tainting kernel
Nov 15 12:36:51 hp8740w kernel: [ 19.618671] vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=none:owns=none
Nov 15 12:36:51 hp8740w kernel: [ 19.619294] [drm] Initialized nvidia-drm 0.0.0 20130102 for 0000:01:00.0 on minor 0
Nov 15 12:36:51 hp8740w kernel: [ 19.619305] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 331.89 Tue Jul 1 13:30:18 PDT 2014
Nov 15 12:36:51 hp8740w kernel: [ 20.894036] init: Error while reading from descriptor: Broken pipe
Nov 15 12:36:51 hp8740w kernel: [ 20.897467] init: failsafe main process (642) killed by TERM signal
Nov 15 12:36:51 hp8740w kernel: [ 21.764054] audit: type=1400 audit(1416051411.907:11): apparmor="STATUS"
operation="profile_load" profile="unconfined" name="/usr/lib/lightdm/lightdm-guest-session" pid=719 comm="apparmor_parser"
Nov 15 12:36:51 hp8740w rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]

[Leandro Boari (v-contato)]

I'm using Nvidia card version 331.104 (open source) and I have this problem.

[A. Eibach (andi3)]

Added upstart to affected software. Reason: mentioned in dupe #1389044.

[Gannet (ken20001)]

I have no nVidia, only AMD and "broken pipe" massage during booting Linux 3.18RC6 also still is. What does this have to Nvidia? о_О

[Brian Kleszyk (bkleszyk)]

I have the same problem, and do not have nVidia. I have the Intel Graphics i915 driver. (14.10 Ubuntu)

[Patrick Hetu (patrick-hetu)]

I think I have this bug too on 14.10 and it makes the boot process to hang.
So I have to boot in single user mode and launch networking and then resume to get to the desktop.
I don't have any nvidia driver though.

[rik (rikkroondijk)]

this started 12-13-2014 after Ubuntu 14.10 regular system update which also incorporated nvidia update.
i now have a black screen and broken pipe !

[delvi luis redondo cardoso (mcboextrem)]

+1 lubuntu used

[K (kaeseblatt)]

+1 Xubuntu 14.10
with kernel
3.18.0-031800-generic #201412071935 SMP Mon Dec 8 00:36:34 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

[K (kaeseblatt)]

Maybe

-8<-
rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
->8-

has something to do with this?

https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/459730/comments/33

seems to not only resolve this rsyslogd-warning, but the init-error as well, at least here.

[Johnny Woods (kill8r)]

Happens even without nvidia graphics as error appears on intel integrated graphics

[Shomz (shomz)]

Again, not related to nVidia - happens on my Intel graphics on 14.10

[Aaron Planell (aaronplanell)]

Two months without Linux. I have the next errors:
systemd-logind[931]: Failed to start unit [e-mail]: Unknown unit: [e-mail]
systemd-logind[931]: Failed to start user service: Unknown unit: [e-mail]

Should I reinstall the OS? :(

[Randy (rrlindsey)]

  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.

[Randy (rrlindsey)]

I'm not sure if this is correct forum protocol but I'd like to add info to my previous post about substituting the Nouveau drivers for the proprietary Nvidia drivers in Lubuntu 14.10 with Nvidia GeForce 7300GS drivers. As stated that eliminated the broken pipe error, but I've since upgraded the Linux kernel in my OS to 3.18.0, reinstalled the Nvidia 304.125 drivers and...no broken pipe error!

[jimav (james-avera)]

Same message here but somewhat different dmesg output.
I'm running 14.10 upgraded from 14.04, and nvidia binary driver 331.113

dmesg (excerpted):
...
init: plymouth-upstart-bridge main process (294) killed by TERM signal
  (the *only* mention of "plymouth")
... then much later...
Disabling lock debugging due to kernel taint
nvidia: module verification failed: signature and/or required key missing - tainting kernel
vgaarb: device changed decodes: PCI:0000:03:00.0,olddecodes=io+mem,decodes=none:owns=none
Initialized nvidia-drm 0.0.0 20130102 for 0000:03:00.0 on minor 0
NVRM: loading NVIDIA UNIX x86_64 Kernel Module 331.113 Mon Dec 1 21:08:13 PST 2014
input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:07.0/0000:03:00.1/sound/card1/input12
input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:07.0/0000:03:00.1/sound/card1/input13
floppy0: no floppy controllers found
work still pending
EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null)
init: Error while reading from descriptor: Broken pipe
init: failsafe main process (904) killed by TERM signal

[Paul Abrahams (abrahams)]

I too get this message in Kubuntu 14.10. I have a Lenovo laptop with Intel integrated graphics.

I actually have two Kubuntu 14.10's in different partitions on this machine. I'm writing this from what I'll call P1, which I had abandoned because the partition was too small for my needs. So I created P2, which has plenty of space. P2 was running just fine for a couple of months when it suddenly started misbehaving badly. After a reboot (to P2) I got just a black screen, though I was able to get to a virtual console with Ctl-Alt-F1 and thus get much more information about the system. When I booted P2 via a slightly different route I got the "error while reading from descriptor" message.

So I now have P1, which works but is not fully usable, and P2, which gives me a black screen. That opens up some potential ways of diagnosing the problem since I can compare the two systems. In particular, I ran dmsg in both systems and compared the two outputs to find the first significant difference. I found this sequence in P2:

[ 1.143424] [drm] Replacing VGA console driver
[ 1.143428] checking generic (e0000000 410000) vs hw (e0000000 10000000)
[ 1.143429] fb: switching to inteldrmfb from VESA VGA
[ 1.143449] Console: switching to colour dummy device 80x25

But in P1 (the correct one) the lines 428 and 429 are absent.

This probably points directly to the bug if only I knew how to interpret it. P2 was fully updated when it started misbehaving; P1 was not.

[Paul Abrahams (abrahams)]

This bug report is mistitled since the same bug appears on machines (like mine) with Intel integrated graphics.

[Paul Abrahams (abrahams)]

i just installed the 3.18 kernel and still get the broken pipe.

[Paul Abrahams (abrahams)]

After poking around I learned that the cure is to install a correction to the Intel microcode. That in turn requires installing the"intel-microcode 2.20140913.1ubuntu2 source package, which is available from Launchpad. However, I haven't yet figured out how to actually do that. The Archlinux folks have some information on this subject. I didn't realize that Linux actually has the ability to install mods to the Intel microcode.

If any one else decides to follow through on this, please post your findings here.

[rhk (rhk)]

Why do you think it comes from intel-microcode?

You can find the built packages here :

amd64
https://launchpad.net/ubuntu/+source/intel-microcode/2.20140913.1ubuntu2/+build/6387490/+files/intel-microcode_2.20140913.1ubuntu2_amd64.deb

i386
https://launchpad.net/ubuntu/+source/intel-microcode/2.20140913.1ubuntu2/+build/6387491/+files/intel-microcode_2.20140913.1ubuntu2_i386.deb

[Paul Abrahams (abrahams)]

I.ve installed the 20140923 microcode update. It solved the buffer underrun problem I was having but not the broken pipe problem. The reason I thought it would help is that I saw a post somewhere saying that this update worked but the previous one (20140624) did not. I've been trying without success to find that post again to see just what it was that this update was supposed to have fixed.

With this update I get the line in dmesg that says

CPU0 microcode updated early to revision 0x29, date = 2013-06-12

The form of the line seems correct but the date looks suspicious.

Meanwhile thes primary problem remains unsolved -- I can't get past the "broken pipe" message. After it comes up I get bounced to a virtual console.

[Gannet (ken20001)]

Kubuntu 14.10. Linux 3.19RC4 x86_64. Just restarted my machine after full freeze (because of buggy video decode hardware acceleration testing) when broken pipe error appeared during boot.

[Gannet (ken20001)]

BTW, I have no problems with CPU microcode and I have no Intel videos on my machine - only AMD (HD2600XT).

[Gannet (ken20001)]

Restarted my machine again and no more "broken pipe" message at boot.

[Samueldasilva5448 (samueldasilva5448)]

this bug affect me to. i've a nvidia video card and use binary driver v331.113. Have you got any information for resolve it ? thanks

[rik (rikkroondijk)]

i have to machines both runnning 14.10 , both nvidia cards

1 machine cannot be used anymore , black screen and broken pipe,
1 machine shows broken pipe and then boots after all into a working screen
??

On Thu, Jan 15, 2015 at 10:46 AM, Samueldasilva5448 <
<email address hidden>> wrote:

> this bug affect me to. i've a nvidia video card and use binary driver
> v331.113. Have you got any information for resolve it ? thanks
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1364630
>
> Title:
> init: Error while reading from descriptor: Broken pipe
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/upstart/+bug/1364630/+subscriptions
>

[Samueldasilva5448 (samueldasilva5448)]

my unit boot after this error message and no problem after log in on my ubuntu linux system but it is a strange error message

[Patrick (patrickstar777)]

My System also shows this error, is able to boot though, but with messed up hyprid text and logo splash.
I'm experiencing this ever since I upgraded to Utopic from Trusty. I'm using "fglrx-updates" ATI drivers.

Since, it also shows the following errors when I log in via tty1 in text mode, and in "auth.log":

systemd-logind[1420]: Failed to start unit [e-mail]: Unknown unit: [e-mail]
systemd-logind[1420]: Failed to start user service: Unknown unit: [e-mail]

[OlivierT (olivier-tribout)]

With nvidia package on 14.10, I have the same message.
I can't boot anymore.
(note that at installation I had to use the "nomodeset" parameter, otherwise the screen would have been broken the same)

[Ron Tharp (lowrides)]

 Intel graphics with the same problem. Anyone find a solution?

[Paul Abrahams (abrahams)]

I just "upgraded" a system from Kubuntu 14.04 to Kubuntu 14.10, and the "broken pipe" error popped up. Some questions for the suffering populace:

1. Does the error occur with 14.04 or only with 14.10?

2. Does it occur with 14.10 installed directly or only with 14.10 upgraded from 14.04?

In my experience it is specifically associated with upgrading 14.04 to 14.10 but is not associated with specific video hardware since it has been reported both for Nvidia video and Intel video. Does anyone have experience to the contrary?

[Paul Abrahams (abrahams)]

The keepers of the archive need to do something about this bug to reflect the fact that it is not Nvidia-specific. Several people have reported encountering it with Intel hardware.

[Ron Tharp (lowrides)]

Paul, My problem occurred when upgrading from 14.04 to 14.10. I definitely are agree with post #70!

[rik (rikkroondijk)]

my problem occurred upgrading in 14.10 doing a regular Ubuntu base upgrade

On Wed, Jan 28, 2015 at 12:10 PM, Ron Tharp <email address hidden> wrote:

> Paul, My problem occurred when upgrading from 14.04 to 14.10. I
> definitely are agree with post #70!
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1364630
>
> Title:
> init: Error while reading from descriptor: Broken pipe
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/upstart/+bug/1364630/+subscriptions
>

[Urop (urop)]

I have got this problem upgrading three machines from Ubuntu 14.04 to 14.10, two nVidia, one AMD. It's now not possible to log into the AMD one - the desktop is missing and the system is frozen not responding to anything. I have switched to XFCE on that machine and its working fine. The nVidia machines freeze after about 10 mins on standard graphics. They are almost usable if I use the nVidia drivers, but then after 10 minutes the background will stop updating so that moving any windows around leaves an annoying trail, and when minimizing a window it appears as if it is still there. I don't if any of that is related to this bug or not. I'm also suffering from bug 1359439. All in all, this update has been a complete disaster.

[Roland Meier (rm369)]

Paul (#69), for me the message occurrs in a freshly installed 14.10 system (which boots fine after the message).
I think there may be multiple conditions for the error message (broken pipe), some possibly related to the nvidia driver (according to the position in the message log, see #37), others not.

[Paul Abrahams (abrahams)]

Re #74 (Roland Meier): the message in #37 is "Could no open output pipe", which is somewhat different from the "broken pipe" message. Interestingly, I've also seen the broken pipe message in an older 13.10 system, which brought up the graphical interface but froze after a while.

[Domar (domar)]

Re #74:
The message also occurs on my freshly installed 14.10.
My system is working fine after this message too.

[Sanket (sbenade96)]

what to do avoid this problem

[Todd Stoffel (toddstoffel)]

Graphics are set to low during bootsplash. Follow these steps to fix:
 http://www.binarytides.com/ubuntu-fix-nvidia-graphics/

[rik (rikkroondijk)]

thanks for your suggestions ! will try as soon as I am back home at my PC
 :-)

On Mon Feb 02 2015 at 19:35:37 Todd Stoffel <email address hidden> wrote:

> Graphics are set to low during bootsplash. Follow these steps to fix:
> http://www.binarytides.com/ubuntu-fix-nvidia-graphics/
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1364630
>
> Title:
> init: Error while reading from descriptor: Broken pipe
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/upstart/+bug/1364630/+subscriptions
>

[Folour (folour)]

For fix this error need install thermald.

apt-get install thermald linux-image-generic

[Climax (pieterwjordaanpc)]

I have thermald installed.

On Sun, 08 Feb 2015, 15:20 Folour <email address hidden> wrote:

> For fix this error need install thermald.
>
> apt-get install thermald linux-image-generic
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1364630
>
> Title:
> init: Error while reading from descriptor: Broken pipe
>
> Status in Upstart:
> Confirmed
> Status in nvidia-graphics-drivers-304 package in Ubuntu:
> Confirmed
>
> 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:
> https://bugs.launchpad.net/upstart/+bug/1364630/+subscriptions
>

[Daniel Antlinger (d-antlinger)]

Hey, I have the same problem and are looking for a solution as well. I am not sure if you need more system/hardware informations. I added the dmesg output anyway.

I have the same error with ubuntu 14.04, ubuntu 14.10 and I tried Linux Mint (with is the same then ubuntu 14.04) as well. Just on ubuntu 14.04 I have the "... broken pipe" message additional to the normal output.

Let me know if you need more information.

[Daniel Antlinger (d-antlinger)]

I installed thermald too, doesn't change anyhting on my system.

[Patrick (patrickstar777)]

Installing thermald:
no change either.

[Al Abrar Abdul Wahid (abrar-abdulwahid)]

Im also having similar problem . Initally due to display driver update but then it effected with failure on the display - blank screen, then fail to login at terminal (looping) then missing launcher-desktop.. now is like total unusable.

[Константин (lamdos)]

In Ubuntu 14.10 x64 with nvidia 346.47 also this problem

[Mark Greenwood (fatgerman-m)]

I'm also having this. It started on 14.04 but has got significantly worse on the upgrade to 14.10 - it is intermittent. It would happen only occasionally on 14.04 but now happens almost all the time on 14.10. I have nVidia graphics but am using nouveau. What's particularly bad about this in my case (Sony VAIO laptop) is that when it happens my ethernet port completely stops working, it's not even detected (doesn't show up in lspci), making my laptop almost useless.

[leouss (leouss4dev)]

I'm also having this in ubuntu Gnome 14.10 64bit and when I opened the link apeared in the log by this command :
------------------------------------------
cat /var/log/syslog|grep pipe
init: Error while reading from descriptor: Broken pipe
rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
------------------------------------------
the solution is just there http://www.rsyslog.com/e/2039
/************************************************************************************/
In Ubuntu 12.04.3 LTS, Precise Pangolin, you may get the following error in syslog:

Dec 10 09:17:37 dl6-c4331 rsyslogd-2039: Could not open output pipe '/dev/xconsole' [try http://www.rsyslog.com/e/2039 ]

The package rsyslog-5.8.6-1ubuntu8.6.deb expects /dev/xconsole to be installed, but 'apt-file search /dev/xconsole' found no packages that provide it.

Comment it out near the end of /etc/rsyslog.d/50-default.conf :

# daemon.*;mail.*;\
# news.err;\
# *.=debug;*.=info;\
# *.=notice;*.=warn |/dev/xconsole

You can restart rsyslog with 'sudo service rsyslog restart' to confirm the error is gone.
/************************************************************************************/
it works in ubuntu gnome 14.10 64bit
Good Luck

[Teddy Larsen (o-teddy)]

Commenting out:
****
# daemon.*;mail.*;\
# news.err;\
# *.=debug;*.=info;\
# *.=notice;*.=warn |/dev/xconsole
****
in /etc/rsyslog.d/50-default.conf did not work for me on Xubuntu 14.10, however doing the following did work:

terminal code:
sudo mknod -m 640 /dev/xconsole p
sudo chown root:adm /dev/xconsole

I now no longer have the broken pipe message during boot.

It seems to me, that the following function in /etc/init.d/rsyslog is never run:
create_xconsole() {
        XCONSOLE=/dev/xconsole
        if [ "$(uname -s)" != "Linux" ]; then
                XCONSOLE=/run/xconsole
                ln -sf $XCONSOLE /dev/xconsole
        fi
        if [ ! -e $XCONSOLE ]; then
                mknod -m 640 $XCONSOLE p
                chown root:adm $XCONSOLE
                [ -x /sbin/restorecon ] && /sbin/restorecon $XCONSOLE
        fi
}

Kind regards
Teddy

[myron (myron620)]

Init error reading from descriptor:Broken pipe.

[Arnaud LE CAM (alc-b)]

This bug doesn't affect nvidia-graphics-drivers-304 : fews persons have reported it with Intel or AMD chipsets

[Reinaert Albrecht (reinaert-albrecht)]

This bug still occurs with nvidia-graphics-drivers-304 as with nvidia-graphics-drivers-304-updates and nvidia-graphics-drivers-331. It's not visible though and you have to do a 'cat /var/log/syslog|grep pipe' to see it.

[Vilis (vilis)]

I experienced this problem today on my Dell Latitude D630 laptop with a fresh install of Ubuntu 14.10, installed today. The problem came up immediately after I installed Intel GM 965 Graphics driver intel-linux-graphics installer_1.0.8-0intel1_amd64.deb
When I shut down my laptop following this install, during shutdown there was a kernel crash. I can enter my Ubuntu installation using the Grub screen recovery mode option. In recovery mode, the system seems to run perfectly, better than ever before, which proves that the Intel graphics driver update I installed fixed the problems plaguing Linux Mint and Ubuntu on this laptop. I may have to reinstall my system to get rid of having to enter Ubuntu via Grup recovery mode.

Now that there is a fix to the Intel GM 965 Graphics driver problem bugging thousands of users, somebody at Ubuntu should get this fixed. Unfortunately, Teddy's hopeful fix did not work for me.

[Hayet Mahmud (hayetfahad)]

This problem still exists in the UBUNTU 15.04 x64 bit version.
I tried the above advised fix but it did not solved my problem. :(

I am using NVIDIA 346.59 driver

Please somebody find the solution.

[Deep Thought (ti-42-plus)]

Same error after upgrading Xubuntu 14.04 to 14.10 with Intel integrated graphics. Also present on 15.04.

This issue does not prevent my computer from booting successfully, but it does add an eight-second delay to the boot process:

...
[ 3.500278] acer_wmi: Disabling ACPI video driver
[ 3.500468] input: Acer WMI hotkeys as /devices/virtual/input/input12
[ 3.500916] input: Acer BMA150 accelerometer as /devices/virtual/input/input13
[ 11.263256] init: Error while reading from descriptor: Broken pipe
[ 11.265347] init: failsafe main process (859) killed by TERM signal
[ 11.317147] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
...

[owen (owski-phillips)]

Hi, To all i am still seeing this error, I am a developer for a linux operating system called: The Linux Schools Project. I maintain the client and i am seeing this error when I try and boot the new version i am creating! My output from
cat /var/log/syslog | grep pipe, is the same as everyone elses. I hope this is still active, i need to release this os in the next 2 weeks and this is the only thing getting in the way.

[Roland Meier (rm369)]

Re #75 (Paul Abrahams): the message in #37 is both "Could no open output pipe" and "broken pipe"

[bam (mybigspam)]

Happened to me after upgrading from 15.10 to 16.04.
"broken pipe", can't boot. Intel graphics.
Problem occurs only if boot with Upstart (Systemd doesn't suffer) !
It seems like there are rase conditions somewhere because after all day of unsuccessful battle it's turned out that sometimes system just boots normally, but sometimes not..

[Yuri W (wildylion)]

Happened to me too, and too after upgrade from 15.10 to 16.04. Since we're using crypttab with the keyscript= option, we can't yet use systemd, and it seems like the system affected can boot once in ~5 times fine, suggesting there is indeed a race condition somewhere inside upstart (?)

Despite wasting 5 hours of my time yesterday I can't yet gather enough data for a consistent bug report.

PS. Considering systemd's inability to coexist with the keyscript= option - maybe we guys should raise a petition so that we can finally be heard? It's a very longstanding issue systemd developers are intentionally turning their heads away from. Don't think that's exactly how open-source software should be built. :(

[Yuri W (wildylion)]

I have noticed that if the machine has been shut down uncleanly, then the success rate of it getting to boot normally is nearly 100%. Must have to do something with fsck delaying the startup sequence enough for this bug not to trigger?

[gdm85 (gdm85)]

How to reproduce this:

1) go to /etc/init.d
2) rename mountall.sh to disabled-mountall.sh

So perhaps a broken symlink in the /etc/rc* levels causes this?

Should be fairly easy to verify for the people affected.