Control: reassign -1 scim-gtk-immodule Control: retitle -1 scim-gtk-immodule breaks pinentry-gtk2 and impairs gnome-keyring Control: severity -1 critical Control: affects -1 pinentry-gtk2 gnome-keyring
The pinentry-curses symptom was not actually a bug; doing "anything | pinentry-curses" makes it unable to detect the correct tty; the correct invocation that works is: $ mytty=$(tty); echo GETPIN | pinentry-gtk-2 --ttyname="$mytty" The cause of the pinentry-gtk2 bug is very likely to be scim-gtk-immodule. Uninstalling this package and restarting SCIM, makes this work for me again: $ echo GETPIN | pinentry-gtk-2 (However, of course SCIM stops working in GTK applications.) Installing (e.g.) hime-gtk3-immodule does not cause a similar break, suggesting that the problem is in SCIM and not pinentry-gtk2. Furthermore, another weird behaviour I had noticed, is fixed by uninstalling scim-gtk-immodule: where pressing tab or enter in a gnome-keyring unlock dialog boxs adds a (what I assume is a) literal "tab" or "enter" character *into the password input* instead of (respectively) tabbing to the next GUI element or confirming the input. This further suggests that the problem is in SCIM and not gnome-keyring. X -- GPG: 4096R/1318EFAC5FBBDBCE git://github.com/infinity0/pubkeys.git -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
