SCIM Smart Pinyin character table in strange position, forgets corrected position

[Ian Clark]

Binary package hint: scim

Position of character menu in strange, upper left-hand position - away from characters being inputted.

When position is corrected, menu stays in place for around one sentence, then migrates back up to upper left-hand side.

I'd expect the menu to be below the characters being inputted (as before Hardy release). After correction, I'd expect the menu to always stay in that place.

[Arne Goetje (arnegoetje)]

I cannot reproduce this. For me the character menu is placed on the lower left side of the active window.
Can you attach your ~/.scim/config file (and optionally /etc/scim/config ), please?

[Ian Clark (blacktuzi)]

I noticed the bug happened with AbiWord 2.6.3 (not in the repositories), and indeed the placement is fine with other applications.

[Ian Clark (blacktuzi)]

I couldn't find "~/.scim/config". Am I typing this wrong? I also searched for ".scim" from the file system and nothing came up.

[Arne Goetje (arnegoetje)]

your config file is fine.

I have tested it with Abiword 2.4.6, which we have in our repository and there the placement is fine.
So, I think the problem lies either with your newer Abiword version, or the way it was compiled and installed on your system.

Because this is not in our scope, I'm closing this bug. If you find that other applications, which are in our repositories, have the same problem, you may reopen this bug again by changing the status back to "New".

[Ian Clark (blacktuzi)]

OK, it is an AbiWord bug, not a SCIM bug, but this bug is a known bug and has been around for a while. http://bugzilla.abisource.com/show_bug.cgi?id=8738

[Arne Goetje (arnegoetje)]

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

Ian Clark wrote:
> OK, it is an AbiWord bug, not a SCIM bug, but this bug is a known bug
> and has been around for a while.
> http://bugzilla.abisource.com/show_bug.cgi?id=8738
>
well, the version of Abiword we provide works fine. So, either we are
not affected by that bug, or it has been introduced in a later version
and we yet will have to deal with it, I don't know.
But unless you prove that our version is affected, this bug report
remains invalid.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIIwbCbp/QbmhdHowRAuDEAKDdhjpdauBF87iD9n2cpzTXikzqZwCgw2zn
NPzvSQ5nJ2UtxbUB65Oc+J0=
=L1e4
-----END PGP SIGNATURE-----