Broken pipes

[1richard]

I have installed Lucid on 2 laptops and 2 desktops and all say the same thing upon booting
"broken pipes...could not write ..bytes"

But the system appears to be ok and stable, can anyone tell me what this means??

Also when installing on 2 Acer laptops using the daily version from the cd it will not let me partition the HD, so I have to install 9.04 and then upgrade to get the partitions I want. (maybe a bug)

[vinnywright]

Re: Broken pipes

I have installed Lucid on 2 laptops and 2 desktops and all say the same thing upon booting
"broken pipes...could not write ..bytes"

But the system appears to be ok and stable, can anyone tell me what this means??

I get that to but seems OK

Also when installing on 2 Acer laptops using the daily version from the cd it will not let me partition the HD, so I have to install 9.04 and then upgrade to get the partitions I want. (maybe a bug)

do your self a faver and get a Gparted livecd and do your partitioning before installing so you just half to point the instaler to your partitions

VINNY

[hunkirdowne]

Re: Broken pipes

I have installed Lucid on 2 laptops and 2 desktops and all say the same thing upon booting
"broken pipes...could not write ..bytes"

But the system appears to be ok and stable, can anyone tell me what this means??

I get that to but seems OK

Not only where 1richard explains but due to off-topic reasons I would get a crash that would restart X and I would switch to tty to take care of some business related to the crash. Attempting to return to the login was "futile". I would hit <CTRL+ALT+F7> and see the broken pipes message. Only recently I discovered that if I hit <CTRL+ALT+F8> I would return to the login (I was grabbing .xsession-errors so I didn't want to restart the session until I copied the file from the previous session).

While I wouldn't say that my system is unusable, this would hint that something is amiss at least within that session. I wouldn't have thought of tty8 being the place to look had it not been for perusing the output of 'ps aux'.

[kubicle]

Re: Broken pipes

AFAIK these issues (broken pipe messages, bumping X session to tty8) are caused by plymouth (the bootsplash screen).

[hunkirdowne]

Re: Broken pipes

AFAIK these issues (broken pipe messages, bumping X session to tty8) are caused by plymouth (the bootsplash screen).

That makes sense, but not being a voice of authority on this matter I'll leave that part to others. ;-)

Not a pressing issue, IMO, but assuming that plymouth is GTK+ and the kwin session Qt, is this a case of a conflict between the two? I guess if this is happening in the Ubuntu beta the answer would be 'no' but I haven't checked (and having limited time at the moment, do not intend to -- at least not this morning (lol)).

My treatment of my system, being that this is beta, is almost entirely "stock" so I would not likely choose to disable (or at least attempt) plymouth. But if it would serve the beta team I might reconsider (given the available block of time that I think would be required). So is this something worth pursuing or not is my question and I'm open to input. There are a couple of other issues that I'm working on with respect to the beta but I could certainly add this to my list.

And let me define what "working on" means to me: I'm not a programmer (in the Linux sense, anyway) but am working on discovery through somewhat common usage. I had originally thought some of the problems I was facing was due to the old hardware I'm running but I'm finding out more and more that the age of the technology, cpu speed, ram installed, etc. have little to do with the problems I'm seeing and the beta is performing quite well overall. There are some issues that are definitely "age-related" like firefox debug tools not having enough memory to do it's thing or the fact that I cannot use compositing and such. But to be able to run KDE4 on 6-7 year old laptops is, IMO, an accomplishment not to be taken lightly. I've tried other distros including Kubuntu 9.10 and they haven't fared this well.

[kubicle]

Re: Broken pipes

I disabled plymouth a while back, and haven't had these issues since. Disabling plymouth is a tad tricky now that mountall depends on the plymouth package so it can't be simply removed (and I don't recommend messing with upstart configuration unless you're sure you know what you're doing)

As for the tty bumping, my guess is that plymouth reserves tty7 for itself, and when kdm starts, it takes the next available tty, which is tty8.

I don't know it this also happens on ubuntu, or if it only happens on the kubuntu side of things.

[Rog131]

Re: Broken pipes

> Broken Pipe (Ubuntu Forums)
> Bug #521298: could not write byte broken pipe
> Bug #558695: Ubuntu Lucid crashes with message "could not write bytes: broken pipe"