Bugzilla – Bug 554819
psi suddenly dropped gpg support 'due to buggy qt version'
Last modified: 2010-05-01 09:09:32 UTC
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.13) Gecko/2009080200 SUSE/3.0.13-0.1.2 Firefox/3.0.13 olli@acer15> psi --help qca-gnupg: disabling keyring monitoring due to buggy Qt version ^C olli@acer15> rpm -qa | grep -i Qt qt3-3.3.8b-87.11 libqt4-qt3support-4.4.3-4.8.2 libqt4-x11-4.4.3-4.8.2 dbus-1-qt3-0.62-221.222.1 yast2-qt-2.17.23-1.5 python-qt4-4.4.3-1.44 libqt4-devel-doc-data-4.4.3-4.8.1 libqt4-devel-doc-4.4.3-4.8.1 libpoppler-qt4-3-0.10.1-1.4 qt3-devel-doc-3.3.8b-87.11 libqt4-sql-4.4.3-4.8.2 dbus-1-qt3-devel-0.62-221.222.1 pinentry-qt-0.7.5-61.14 libQtWebKit4-4.4.3-4.8.1 libqt4-sql-mysql-4.4.3-11.8.1 libqt4-sql-sqlite-4.4.3-4.8.2 qtcurve-kde-0.59.5-1.83 libqt4-devel-4.4.3-4.8.2 yast2-control-center-qt-2.17.3-1.8 yast2-qt-debuginfo-2.17.23-1.5 libqt4-4.4.3-4.8.2 qtcurve-gtk2-0.59.7-2.4 libqtpod0-0.4.2-4.106 libQtWebKit-devel-4.4.3-4.8.1 yast2-qt-devel-2.17.23-1.5 yast2-qt-pkg-debuginfo-2.17.22-1.1 libpoppler-qt2-0.10.1-1.4 qt3-devel-tools-3.3.8b-87.11 qt3-devel-3.3.8b-87.11 python-qt-3.17.4-1.138 libdbus-1-qt3-0-0.8.1-17.72 yast2-qt-pkg-2.17.27-0.1.1 licq-qt4-gui-1.3.6-0.pm.1 libsvnqt4-1.0.2-1.42 vlc-qt-1.0.1-0.pm.0 olli@acer15> rpm -qa | grep psi libdvbpsi5-0.1.6-1.74 psi-0.12-28.15.1 nmapsi4-0.1.1-0.pm.1 psiconv-0.9.8-1.140 Reproducible: Always Steps to Reproduce: Donno how it happen - all worked. I did rpm -e pidgin that day, but I also 've automatic updates via cron. :/ Actual Results: psi doesn't show gpg keys avaliable in the keyring anymore (and previousely I used gpg for jabber successfully). Expected Results: psi should work w/ gpg key choosen from avaliable keyrings to sign/encrypt messages. Also it'd be nice to have option 'do not sign status', since if password phrase access expires - the automatic status changes are leading to inability to change status - it require signing, but keyring password must be entered again to do that.
olli@acer15> rpm -qa | grep -i qca-gnupg olli@acer15> rpm -qa | grep -i qca qca-1.0-98.143 libqca2-2.0.1-1.48 olli@acer15> rpm -qa | grep -i gnupg olli@acer15> rpm -qa | grep -i gpg gpg-pubkey-1abd1afb-48d62ce0 gpg-pubkey-da4fc3e9-47965b51 gpg-pubkey-3d25d3d9-36e12d04 gpg-pubkey-72fadfc8-47965691 gpg-pubkey-7e2e3b05-4816488f libgpgme11-1.1.6-25.116 gpg-pubkey-3dbdc284-49144c3f gpg-pubkey-229bc81c-48f23f7e libgpg-error-devel-1.6-6.10 gpg-pubkey-9c800aca-481f343a libgpg-error0-1.6-6.10 gpg-pubkey-233ab63d-479655fe gpg-pubkey-307e3d54-481f30aa gpg2-lang-2.0.9-25.108.1 gpg2-2.0.9-25.108.1 gpg-pubkey-0d0e4317-47965a00 libgpgme-devel-1.1.6-25.116 gpg-pubkey-0f2672c8-47965633 gpg-pubkey-56b4177a-47965b33 gpg-pubkey-79eafd54-4978a811 gpg-pubkey-c8da93d2-493f7d78 gpg-pubkey-a1912208-446a0899 gpg-pubkey-766da614-47965b2b gpg-pubkey-2c4806b9-479657ee gpg-pubkey-e558cb38-4796572c gpg-pubkey-c66b6eae-4491871e gpg-pubkey-0dfb3188-41ed929b gpg-pubkey-ab96f23f-49f6ed5b gpgme-1.1.6-25.116 olli@acer15>
Dirk: were there any updates to Qt for 11.1 recently?
yes, we just recently released a libqt4 update, but it shouldn't cause a regression. the "due to buggy qt version" warning is bogus, it has been there the whole time.
Petr: what about gpg updates? I'm pretty sure there were not psi updates recently ...
The last update to gpg2 happened in March and I can't imagine how that fix could be related to this issue. So I guess it is something else.
I found now in errorlog - the problem that xloadimage is absent and xli that is a version of one does not support name xloadimage. ln -s `which xli` /usr/bin/xloadimage fixes the problem after reloading psi. Found that on new 11.2, hopefully same will fix 11.1 . Sorry for wrong info about qt - it doesn't relate.
Can you please explain how is xli/xloadimage connected to missing gpg keys?
My guess - psi interface tries to start gpg w/ some options that assume load image attached to keys (if any). Some functionality broken when no load picture image program and gpg gives error instead of list of present keys. So the keys are absent in the list in psi (though all OK - keys are present). As I said if xloadimage is present in the path (I ln w/ xli) all work OK. Sorry - didn't digg more - now all work OK.
I fixed xli package in Factory to provide also xloadimage. Thanks for the report and investigation