bzr crashed with IOError in callHandlers()

Bug #464492 reported by NeilGreenwood
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bazaar
Invalid
Undecided
Unassigned
bzr (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: bzr

Not sure if it was caused through Diffuse merge tool or Ubuntu Software Centre, since I was using both at the time. Hopefully the full stack trace will help.

I wasn't using bzr directly at the time.

ProblemType: Crash
Architecture: i386
Date: Fri Oct 30 09:32:54 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/bzr
InterpreterPath: /usr/bin/python2.6
Package: bzr 2.0.0-0ubuntu1
ProcCmdline: /usr/bin/python /usr/bin/bzr status -SV ./apt
ProcEnviron:
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
PythonArgs: ['/usr/bin/bzr', 'status', '-SV', './apt']
SourcePackage: bzr
Title: bzr crashed with IOError in callHandlers()
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
NeilGreenwood (neil-greenwood) wrote :
visibility: private → public
tags: removed: need-duplicate-check
Jelmer Vernooij (jelmer)
Changed in bzr (Ubuntu):
status: New → Confirmed
Changed in bzr:
status: New → Confirmed
Revision history for this message
Jelmer Vernooij (jelmer) wrote :

This is a strange error, apparently the python logging module has problems writing to standard error. Are you just running bzr on the command-line?

Revision history for this message
NeilGreenwood (neil-greenwood) wrote :

Not directly. I was running diffuse and the Software Centre, when apport popped up in the status area.

I've not seen it since, but I've not run diffuse much, and I've upgraded a couple of times since.

Revision history for this message
dino99 (9d9) wrote :

This version has expired long ago; no more supported

Changed in bzr (Ubuntu):
status: Confirmed → Invalid
Changed in bzr:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.