pinentry-gtk2 does not register keys while scim-bridge is running

[Louis-Dominique Dubeau]

Binary package hint: pinentry-gtk2

Versions
=====

I'm running a current installation of Gutsy Gibbon (by "current" I mean all packages are at the latest published version).

pinentry-gtk2 is at version 0.7.3-1ubuntu2

How to reproduce
==========

Your input method configuration must be set to scim-pinyin. Then, try to perform any operation that requires a gpg key. (I've gotten the problem while trying to sign a binary file and also while running dpkg-buildpackage). pinentry-gtk-2 will come up but it won't register any keystrokes.

If I tell gpg not to use an agent, I can enter my password to the terminal prompt without any problem.

Here is how my input method configuration is set up:

$ im-switch -l
Your input method setup under en_US locale as below.
=======================================================
The configuration "/home/ldd/.xinput.d/en_US" is defined as a link pointing to
scim-pinyin
This private configuration supersedes the system wide default.
=======================================================
The system wide default is pointed by "/etc/alternatives/xinput-all_ALL" .
xinput-all_ALL - status is auto.
 link currently points to default
default - priority 10
none - priority 0
scim - priority 0
scim-immodule - priority 0
Current `best' version is default.
=======================================================
The available input method configuration files are:
default none scim scim-chewing scim-immodule scim-pinyin scim_xim th-xim
=======================================================

References:

This bug was reported in OpenSUSE also:

https://bugzilla.novell.com/show_bug.cgi?id=330073#c5

Unfortunately this next reference is in Japanese, a language I don't understand:

http://lists.sourceforge.jp/mailman/archives/scim-imengine-dev/2006-November/001429.html

[Charlie Kravetz (cjkgeek)]

Thank you for taking the time to report this bug and helping to make Xubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Xubuntu release, Hardy Heron 8.04.01 or Intrepid Ibex 8.10? The bug that was reported in OpenSUSE also: https://bugzilla.novell.com/show_bug.cgi?id=330073#c5 has been closed. However, there is an open bug at http://bugzilla.xfce.org/show_bug.cgi?id=4082 that I will link this to if it is still valid for you. Thanks in advance.

[Charlie Kravetz (cjkgeek)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

[Louis-Dominique Dubeau (ldd)]

This bug is no longer a problem for me. I'm running Ubuntu 8.10 and I have changed my input method to scim-bridge instead of scim-pinyin:

$ im-switch -l
Your input method setup under en_US locale as below.
=======================================================
The configuration "/home/ldd/.xinput.d/en_US" is defined as a link pointing to
scim-bridge
This private configuration supersedes the system wide default.
=======================================================
The system wide default is pointed by "/etc/alternatives/xinput-all_ALL" .
xinput-all_ALL - status is auto.
 link currently points to default
default - priority 10
default-xim - priority 0
none - priority 0
Current `best' version is default.
=======================================================
The available input method configuration files are:
default default-xim none scim scim-bridge scim-chewing scim-immodule scim-pinyin th-xim
=======================================================

I do not know whether the problem has in fact been properly fixed by an upgrade or whether changing from scim-pinyin to scim-bridge worked around the problem. Both scim-pinyin and scim-bridge use the scim-bridge module but they do it in slightly different ways.

[Rolf Leggewie (r0lf)]

it turns out this actually still a problem

[Dominik Viererbe (dviererbe)]

Thank you for reporting this bug to Ubuntu.

Ubuntu 23.10 (mantic) reached end-of-life on July 11, 2024.
Ubuntu 23.04 (lunar) reached end-of-life on January 25, 2024.
Ubuntu 22.10 (kinetic) reached end-of-life on July 20, 2023.
Ubuntu 21.10 (impish) reached end-of-life on July 14, 2022.
Ubuntu 21.04 (hirsute) reached end-of-life on January 20, 2022.
Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019.
Ubuntu 18.04 (bionic) reached end-of-standard-support on May 31, 2023.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.
Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018.
Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016.
Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015.
Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019.
Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014.
Ubuntu 13.04 (raring) reached end-of-life on January 27, 2014.
Ubuntu 12.10 (quantal) reached end-of-life on May 16, 2014.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013.
Ubuntu 11.04 (natty) reached end-of-life on October 28, 2012.
Ubuntu 10.10 (maverick) reached end-of-life on April 10, 2012.
Ubuntu 10.04 (lucid) reached end-of-life on May 9, 2013.
Ubuntu 9.10 (karmic) reached end-of-life on April 30, 2011.
Ubuntu 9.04 (jaunty) reached end-of-life on October 23, 2010.
Ubuntu 8.10 (intrepid) reached end-of-life on April 30, 2010.
Ubuntu 8.04 (hardy) reached end-of-life on May 12, 2011.
Ubuntu 7.10 (gutsy) reached end-of-life on April 18th, 2009.
Ubuntu 7.04 (feisty) reached end-of-life on October 19, 2008.
Ubuntu 6.10 (edgy) reached end-of-life on April 26, 2008.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it anymore. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in.