Explorer commit error 32

[Rob Umfreville]

When commiting a change the bazaar explorer interface returns an error window with a message e.g.

bzr: ERROR: [Error 32] C:/worksp/stack/.bzr/branch/lock/held/*

I am then offered to ignore the error or close the application. On ignoring it I can't do anything useful and closing the application means I need to continually reload bazaar explorer which is very annoying.

Although this file reference may change. I am running Windows XP and have disabled the virus scanner (or beleive I have disabled it).

[Jonathan Riddell (jr)]

Does this happen on every branch or just this one?
Did this happen with previous versions of bzr-explorer? What version are you running?
Is there any backtrace?

[Rob Umfreville (rob-umfreville)]

Hi

This happens with every branch I use. I've not had the problem before (although I can't remember what version I was using before). I'm now running Bazaar explorer version: 1.2.1. I'm running Bazaar version 2.4.0.

I don't know how to run a traceback. If you can le me know I can send it over.

Thanks

[Martin Pool (mbp)]

Hi Rob,

If you run 'bzr --version' in the terminal that will tell you where
the .bzr.log file is, and if you look in that file you should find the
traceback.

[Rob Umfreville (rob-umfreville)]

OK no problem, this is the most recent traceback in the log:

16.156 Traceback (most recent call last):
  File "C:/Program Files/Bazaar/plugins\explorer\lib\view_workingtree.py", line 142, in refresh_view
  File "C:/Program Files/Bazaar/plugins\explorer\lib\view_workingtree.py", line 116, in _add_file_watcher_paths
  File "bzrlib\osutils.pyo", line 1772, in _walkdirs_utf8
  File "_walkdirs_win32.pyx", line 227, in bzrlib._walkdirs_win32.Win32ReadDir.read_dir (bzrlib\_walkdirs_win32.c:1837)
WindowsError: [Error 32] C:/worksp/SPStack/Testing/gtest/LibraryModules/RotorkDefinitions/.bzr/branch/lock/releasing.1tseuwsmmfoap9xtubux.tmp/*

Is it easier to post the whole log?

[Martin Pool (mbp)]

Thatsy what we need for now I think.

[Gilles (gsopub)]

I confirm this bug