bazaar explorer closes with bzr: ERROR: [Errno 9] Bad file descriptor

Bug #595251 reported by Bruce Mutton
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Bazaar Explorer
New
Undecided
Unassigned

Bug Description

Bazaar Explorer ALWAYS closes with the error dialog

bzr: ERROR: [Errno 9] Bad file descriptor

I'm using Windows XP

Snippet of the log file follows..

Revision history for this message
Bruce Mutton (dangle) wrote :

oops, here it is

Thu 2010-06-17 08:10:33 +1200

0.172 looking for plugins in C:/Documents and Settings/Bruce/Application Data/bazaar/2.0/plugins
0.172 looking for plugins in C:/Program Files/Bazaar/plugins
9.063 encoding stdout as osutils.get_user_encoding() 'cp1252'

Thu 2010-06-17 08:10:42 +1200
0.140 bazaar version: 2.1.1
0.140 bzr arguments: [u'qsubprocess', u'--bencode', u'l7:versione']
0.156 looking for plugins in C:/Documents and Settings/Bruce/Application Data/bazaar/2.0/plugins
0.156 looking for plugins in C:/Program Files/Bazaar/plugins
0.359 encoding stdout as osutils.get_user_encoding() 'cp1252'
0.484 bazaar version: 2.1.1
0.484 bzr arguments: [u'version']
0.484 encoding stdout as osutils.get_user_encoding() 'cp1252'
0.531 Transferred: 0KiB (0.0K/s r:0K w:0K)
0.531 return code 0

Revision history for this message
Andrew Bennetts (spiv) wrote :

There's not many clues in that log file, unfortunately.

What exactly are you doing when it closes? Or does it close as soon as you try to open it?

affects: bzr → bzr-explorer
Revision history for this message
Bruce Mutton (dangle) wrote :

Sorry , my post was ambiguous.
Bazaar Explorer (BE) opens and can be used as intended (subject to quite a high rate of possibly unrelated errors and crashes that never occur with the command line bazaar or tortoise bazaar).

After the user closes the application, a dialog remains with the error message noted.
The is an OK button which clears the dialog.

And on playing around I see that the error does __not__ __always__ occur, it only occurs when activated from certain folders.
A particular case in point; I opened BE from a trunk that used to have a feature branch named scrunchDuplicateSurveyFiles.
When i was finished with it I deleted it using Windows Explorer.
Now whenever I open BE from that trunk it displays the message (in red).

 Not a branch: "C:/Documents and Settings/Bruce/My Documents/Bruce/Outdoor/Cave/Therion Data and Notes/th_RiwakaCaveSystemData/scrunchDuplicateSurveyFiles/".

I was not too concerned about this, but now I am wondering if it could be related to bug 595251

Anyway, this is one of the scenarios that causes this error dialog?

For what it is worth here is the result of bzr version.

Run command: bzr version
Bazaar (bzr) 2.1.1
  Python interpreter: C:\Program Files\Bazaar\python25.dll 2.5.4
  Python standard library: C:\Program Files\Bazaar\lib\library.zip
  Platform: Windows-XP-5.1.2600-SP3
  bzrlib: C:\Program Files\Bazaar\lib\library.zip\bzrlib
  Bazaar configuration: C:\Documents and Settings\Bruce\Application Data\bazaar\2.0
  Bazaar log file: C:\Documents and Settings\Bruce\My Documents\.bzr.log

Revision history for this message
Bruce Mutton (dangle) wrote :

Sorry, I'm in too much of a hurry...
The dialog has 'close' and 'ignore' buttons, no OK button.

Revision history for this message
Alexander Belchenko (bialix) wrote :
Revision history for this message
Rufus V. Smith (rufuss) wrote :

Bug #556992 states the problem as a "crash", which I believe is a misnomer for this issue.
Bazaar is not crashing, but rather this window pops up upon exit.
But it only pops up if Bazaar explorer is initiated from the Windows right-click context menu, NOT
if it is started from a command window.

I stated my theory (in the other report) that perhaps system trying to access one of the standard
handles stdin, stdout, or stderr, which may not be available if a process is started from the context menu.

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.