Chris Shoemaker <[EMAIL PROTECTED]> writes:
> Thanks for the error reports. This bug has been #1 on my hit-list for
> a while, but I hadn't been able to reproduce it. It turns out that
> the "unable to delete split" behavior was a big clue, and something I
> could finally reproduce. I'm hoping
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thomas Bushnell BSG schrieb:
>> Thanks for the error reports. This bug has been #1 on my hit-list for
>> a while, but I hadn't been able to reproduce it. It turns out that
>> the "unable to delete split" behavior was a big clue, and something I
>> co
Quoting Thomas Bushnell BSG <[EMAIL PROTECTED]>:
> Chris Shoemaker <[EMAIL PROTECTED]> writes:
>
>> Thanks for the error reports. This bug has been #1 on my hit-list for
>> a while, but I hadn't been able to reproduce it. It turns out that
>> the "unable to delete split" behavior was a big clue,
Chris Shoemaker <[EMAIL PROTECTED]> writes:
> Thanks for the error reports. This bug has been #1 on my hit-list for
> a while, but I hadn't been able to reproduce it. It turns out that
> the "unable to delete split" behavior was a big clue, and something I
> could finally reproduce. I'm hoping
Chris Shoemaker <[EMAIL PROTECTED]> writes:
> Thanks for the error reports. This bug has been #1 on my hit-list for
> a while, but I hadn't been able to reproduce it. It turns out that
> the "unable to delete split" behavior was a big clue, and something I
> could finally reproduce. I'm hoping
Thomas, et al.,
Thanks for the error reports. This bug has been #1 on my hit-list for
a while, but I hadn't been able to reproduce it. It turns out that
the "unable to delete split" behavior was a big clue, and something I
could finally reproduce. I'm hoping that these bug(s) have been fixed
by
Derek Atkins <[EMAIL PROTECTED]> writes:
> There are clearly two different bugs here. One was there already.
> The one you're reporting, Thomas, is a regression from a patch that
> went into 2.0.2. Can you file a bugzilla report so we don't forget?
Done.
Quoting Thomas Bushnell BSG <[EMAIL PROTECTED]>:
>> same message as http://bugzilla.gnome.org/show_bug.cgi?id=348469 are
>> they related?
>
> Well, that bug is apparently nondeterministic. The one I am reporting
> happens every time.
There are clearly two different bugs here. One was there alre
Andrew Sackville-West <[EMAIL PROTECTED]> writes:
> On Tue, Oct 10, 2006 at 04:35:27PM +0200, Herbert Thoma wrote:
>> I can confirm this bug :-(
>>
>> And I got a crash when entering a new transaction, too.
>> I did not get a blank split line at the end of the
>> transaction in the auto-split mod
On Tue, Oct 10, 2006 at 04:35:27PM +0200, Herbert Thoma wrote:
> I can confirm this bug :-(
>
> And I got a crash when entering a new transaction, too.
> I did not get a blank split line at the end of the
> transaction in the auto-split mode. When I tried to
> enter the transaction by hitting retu
I can confirm this bug :-(
And I got a crash when entering a new transaction, too.
I did not get a blank split line at the end of the
transaction in the auto-split mode. When I tried to
enter the transaction by hitting return I got a
crash and this error message in the shell:
** ERROR **: file sp
I always use auto-split, which may be relevant. This is with 2.0.2.
I create a new transaction, by filling in part of the memo field and
hitting tab. The details are all filled in, which include two debits
and a credit.
I try to delete one of the debits with "Delete Transaction" from the
right
12 matches
Mail list logo
