bzr crashed with IOError in report_user_error() due to EPIPE on stderr

[Scott James Remnant (Canonical)]

Binary package hint: bzr

It was a complete surprise to me that bzr was even running, I certainly wasn't using it

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/bzr
InterpreterPath: /usr/bin/python2.5
Package: bzr 1.6.1-1
ProcCmdline: /usr/bin/python /usr/bin/bzr commit-notify
ProcEnviron:
 PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=C
 SHELL=/bin/zsh
PythonArgs: ['/usr/bin/bzr', 'commit-notify']
SourcePackage: bzr
Title: bzr crashed with IOError in report_user_error()
Uname: Linux 2.6.27-rc6 i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin netdev plugdev powerdev scanner users video

Traceback (most recent call last):
  File "/usr/bin/bzr", line 131, in <module>
    exit_val = bzrlib.commands.main(sys.argv)
  File "/usr/lib/python2.5/site-packages/bzrlib/commands.py", line 848, in main
    ret = run_bzr_catch_errors(argv)
  File "/usr/lib/python2.5/site-packages/bzrlib/commands.py", line 861, in run_bzr_catch_errors
    exitcode = trace.report_exception(sys.exc_info(), sys.stderr)
  File "/usr/lib/python2.5/site-packages/bzrlib/trace.py", line 414, in report_exception
    report_user_error(exc_info, err_file)
  File "/usr/lib/python2.5/site-packages/bzrlib/trace.py", line 447, in report_user_error
    err_file.write("bzr: ERROR: %s\n" % (exc_info[1],))
IOError: [Errno 32] Broken pipe

[Martin Pool (mbp)]

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.

[Martin Pool (mbp)]

This should probably also be fixed in bzr itself, because we get quite a lot of apport reports that are essentially just because bzr has no stderr, eg bug 561804.

[Martin Pool (mbp)]

Bug 603389 is similar but distinct.