seems likely a plytmouth issue
** Description changed:
With grub2 quiet splash commented out, I get the message "could not
write bytes: Broken pipe" during shutdown.
It is reproducible, but not every shutdown.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
- Package: gedit 2.30.3-0u
When I do not know what package to report a bug to, I always report to
gedit, then select the I don't know option for package.
Please correct that, this bug has nothing to do with gedit.
The printed message occurs with all other verbose messages during
shutdown.
--
You received this bug notific
hum, I'm still trying to understand how that's a bug with the text
editor (gedit, which is the component you reported the bug on) ... where
is that message printed? do you run gedit from a command line, shutdown
and see that message printed in the text editor?
--
You received this bug notificatio
Note that I am also having trouble with Bug #667926, Bug #736253, Bug
#972708.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/1007807
Title:
could not write bytes: Broken pipe
To ma
1. the specific steps or actions you took that caused you to encounter the
problem: shutdown
2. the behavior you expected: no message at all about broken pipe
3. the behavior you actually encountered: the message "could not write bytes:
Broken pipe" during shutdown
Is there any system log file y
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs
** Package changed: ubuntu => gedit (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/1007807
Title:
could not write bytes: Broken pipe
To manage notifications about this bug
