-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

severity 607673 important
tags 607673 - moreinfo help
thanks

Hi Shannon,

Am 21.12.2010 20:01, schrieb Shannon Dealy:
> Your idea that it was SCIM related was correct, however, it wasn't the
> patch that is the problem.
> 
> I tried rebuilding and installing gnucash as you suggested without the
> "10_fix_broken_SCIM_input_bug_587298" patch and it had no effect.

Good to hear, then it is at least no regression (caused by this patch).

> However, I do run with SCIM installed (for use with other programs), and
> terminating it allowed both versions of gnucash to start working
> correctly (with and without the above patch).

Then, we have a workaround. Hence I don't believe anymore that this bug
is release critical, so I am lowering the severity again.

> Restart the background daemon and gnucash immediately stops working
> correctly.
> 
> So the problem would appear to be SCIM related, but (not knowing the
> internals of gnucash), I do find it puzzling that the problem only
> affects transaction editing (register and scheduled transactions), but
> not any other dialogs that I have tried.  I would have expected that all
> keyboard input to the program would behave the same.

I think we should re-check the issue with latest stable upstream version
Gnucash 2.4.0, which has been released some days ago. I hope I get
around to craft some experimental packages for this release soon...

Regards,
Micha
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk0SCgIACgkQWN0/4pnhQbRGbwCfWTTsT8/nzkOSG2GDR0uj9Kpr
YmkAn0NwVUkv2eU9rLnU1qhkTk7Qoxev
=loVn
-----END PGP SIGNATURE-----



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to