I think this is because bzr-gtk has started a background process in your
session, and it's stderr is for some reason connected to a closed pipe.
I think we do now globally give a short message rather than a traceback
for epipe.
** Visibility changed to: Public
** Package changed: bzr (Ubuntu) => bzr-gtk (Ubuntu)
** Changed in: bzr-gtk (Ubuntu)
Status: New => Fix Released
** Summary changed:
- bzr crashed with IOError in report_user_error()
+ bzr crashed with IOError in report_user_error() due to EPIPE on stderr
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/275933
Title:
bzr crashed with IOError in report_user_error() due to EPIPE on stderr
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
