error with "bzr gcommit": 'NoneType' object has no attribute 'abort'

Bug #179325 reported by Michael B. Trausch
2
Affects Status Importance Assigned to Milestone
Bazaar
Invalid
Undecided
Unassigned

Bug Description

This is what I got from attempting to commit using “bzr gcommit” to my local repository. I was able to make the commit using “bzr commit” and entering a log entry using the provided editor window. It was repeatable twice in a row with the same commit, and different log entries. I have, however, used the gcommit command successfully several times before, which leads me to believe that there was a problem with the specific commit that I made, which should (obviously) not happen with any RCS.

I am using bzr version 1.0 and bzr-gtk 0.93.0 on Ubuntu 7.10, which according to the web site is the version to use with bzr 1.0. If there is any additional information that I can provide, I am happy to provide it; I can provide copies of the repository, I think, in a state where the bug can be replicated. I am not quite sure about that, though. I am going to take a snapshot of the directory as it is currently, however, so that the chances are better—I am actively working in this repository, so I am at the point of making several commits relatively often.

What follows is the shell session that led to the problem. Subsequent attempts at interacting with the repository required me to break the lock on it and then re-commit my changes using the shell—which was successful, as I mentioned earlier.

mbt@garlic:~/projects/programming/trausch-software/zenmoney$ bzr gcommit
Committing to: /home/mbt/projects/programming/trausch-software/zenmoney/
missing aclocal.m4
modified utils/clean-directory-tree
deleted aclocal.m4
bzr: ERROR: exceptions.AttributeError: 'NoneType' object has no attribute 'abort'

Traceback (most recent call last):
  File "/usr/lib/python2.5/site-packages/bzrlib/commands.py", line 802, in run_bzr_catch_errors
    return run_bzr(argv)
  File "/usr/lib/python2.5/site-packages/bzrlib/commands.py", line 758, in run_bzr
    ret = run(*run_argv)
  File "/usr/lib/python2.5/site-packages/bzrlib/commands.py", line 492, in run_argv_aliases
    return self.run(**all_cmd_args)
  File "/usr/lib/python2.5/site-packages/bzrlib/plugins/gtk/__init__.py", line 370, in run
    wt.unlock()
  File "/usr/lib/python2.5/site-packages/bzrlib/workingtree_4.py", line 1132, in unlock
    self.branch.unlock()
  File "/usr/lib/python2.5/site-packages/bzrlib/branch.py", line 1361, in unlock
    self.repository.unlock()
  File "/usr/lib/python2.5/site-packages/bzrlib/repofmt/pack_repo.py", line 1935, in unlock
    self.abort_write_group()
  File "/usr/lib/python2.5/site-packages/bzrlib/repository.py", line 482, in abort_write_group
    self._abort_write_group()
  File "/usr/lib/python2.5/site-packages/bzrlib/repofmt/pack_repo.py", line 1779, in _abort_write_group
    self._pack_collection._abort_write_group()
  File "/usr/lib/python2.5/site-packages/bzrlib/repofmt/pack_repo.py", line 1583, in _abort_write_group
    self._new_pack.abort()
AttributeError: 'NoneType' object has no attribute 'abort'

bzr 1.0.0 on python 2.5.1.final.0 (linux2)
arguments: ['/usr/bin/bzr', 'gcommit']
encoding: 'UTF-8', fsenc: 'UTF-8', lang: 'en_US.UTF-8'
plugins:
  gtk /usr/lib/python2.5/site-packages/bzrlib/plugins/gtk [0.93.0]
  launchpad /usr/lib/python2.5/site-packages/bzrlib/plugins/launchpad [unknown]
  multiparent /usr/lib/python2.5/site-packages/bzrlib/plugins/multiparent.pyc [unknown]
*** Bazaar has encountered an internal error.
    Please report a bug at https://bugs.launchpad.net/bzr/+filebug
    including this traceback, and a description of what you
    were doing when the error occurred.
mbt@garlic:~/projects/programming/trausch-software/zenmoney$

Revision history for this message
Michael B. Trausch (mtrausch) wrote :

Well, I was going to attach a copy of the repository here, but that seems moot; I cannot reproduce the bug a third time. I was able to get it twice in a row, but now it seems that if I uncommit and then recommit, even using the same log message, it does not crash again. I will need help to get the appropriate information to get this looked at, I’m afraid.

Revision history for this message
James Westby (james-w) wrote :

Hi,

I think you will find this a manifestation of bug #180208. It
is is usually related to disk space issues, could that be the
case for you?

The bug should be fixed in 1.1 anyway. Or at least this error
should be gone, which would reveal the underlying problem.

Thanks,

James

Revision history for this message
Michael B. Trausch (mtrausch) wrote : Re: [Bug 179325] Re: error with "bzr gcommit": 'NoneType' object has no attribute 'abort'

On Wed, 2008-01-30 at 19:17 +0000, James Westby wrote:
> I think you will find this a manifestation of bug #180208. It
> is is usually related to disk space issues, could that be the
> case for you?

Actually, no. I have no fewer than 10 GiB free on any partition in my
system, and the repository was only a couple of MiB...

 --- Mike

Revision history for this message
James Westby (james-w) wrote : Re: [Bug 179325] Re: error with "bzr gcommit": 'NoneType' object has no attribute 'abort'

On Wed, 2008-01-30 at 19:40 +0000, Michael B. Trausch wrote:
> On Wed, 2008-01-30 at 19:17 +0000, James Westby wrote:
> > I think you will find this a manifestation of bug #180208. It
> > is is usually related to disk space issues, could that be the
> > case for you?
>
> Actually, no. I have no fewer than 10 GiB free on any partition in my
> system, and the repository was only a couple of MiB...

Interesting. There is another problem then. As I said, when you have
1.1 and encounter it again we will see what the underlying problem is.

If you want to patch locally for this problem then bug #180208 has a
(slightly mangled) patch.

Thanks,

James

Revision history for this message
Michael B. Trausch (mtrausch) wrote :

I can no longer reproduce this issue, so keeping it open seems to be moot. Closing as invalid.

Changed in bzr:
status: New → 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.