[Hardy] Psi 0.11 connects in an infinite manner without success after enabling OpenPGP (also Psi 0.12 in Jaunty)

Bug #224906 reported by BastyCDGS
16
This bug affects 1 person
Affects Status Importance Assigned to Milestone
psi (Ubuntu)
Invalid
Low
Unassigned

Bug Description

I have found a fatal bug which disallows me connecting to jabber servers (tested amessage.info and jabber.ccc.de, same result on both) whenever I enable OpenPGP support in Psi.
The expected behaviour is that when I connect to my servers, that Psi gets a connection to them. However, this does not happen, what happens instead is the following:
1. I have OpenPGP enabled before I am starting Psi (means I enabled it before last shutdown of Psi): In this case Psi does loop forever trying to connect. Interrupting connection manually works but trying to reconnect does not work! I have to turn off OpenPGP and restart Psi to be able to connect again (i.e. after a failed attempt, disabling OpenPGP and trying to reconnect results in same behaviour unless I restart Psi). EXPECTED behaviour is: Connection to jabber servers occurs normally.
2. I have OpenPGP disabled before I am starting Psi (means I disabled it before last shutdown of Psi): In this case Psi connects normally as it should. Chatting works flawlessly...when I enable OpenPGP again (i.e. selecting my private key) without restarting Psi and reconnecting to servers, I can still write to people (even encrypted), but I'm not able to receive ANYTHING furthermore from them, neither encrypted nor decrypted messages. This also stays until I restart Psi (i.e. disabling my private key again doesn't help). Also I noticed I can't change my status to "Online" (everything else in Status works). EXPECTED behaviour is, of course, that Psi works the same way as with OpenPGP disabled from beginning (except that messages are encrypted on demand) and I can also change my status to Online.

This seems to be NOT a Psi problem in general, since the same Psi version (not really sure about revision) works with Fedora 7 at my computer at work. So I think it's something inferfering either with libqca2-plugin-gnupg and/or libqca2-plugin-ossl and psi itself in Ubuntu, Maybe it's also caused by gnupg. I will check the package data on Fedora 7 soon if desired, when I'm back at work.

Output of 'lsb_release -rd':
Description: Ubuntu 8.04
Release: 8.04

(to be more precise, I installed Kubuntu 8.04 final release from DVD (from official BitTorrent link) with KDE 3.5.9, choosing de_DE.UTF8 locale).

Output of 'sudo apt-cache policy psi':
psi:
  Installed: 0.11-3
  Candidate: 0.11-3
  Version table:
 *** 0.11-3 0
        500 http://de.archive.ubuntu.com hardy/universe Packages
        100 /var/lib/dpkg/status

Output of 'sudo apt-cache policy libqca2-plugin-ossl':
libqca2-plugin-ossl:
  Installed: 0.1~20070904-3
  Candidate: 0.1~20070904-3
  Version table:
 *** 0.1~20070904-3 0
        500 http://de.archive.ubuntu.com hardy/universe Packages
        100 /var/lib/dpkg/status

Output of 'sudo apt-cache policy libqca2-plugin-gnupg':
libqca2-plugin-gnupg:
  Installed: 0.1~20070904-2
  Candidate: 0.1~20070904-2
  Version table:
 *** 0.1~20070904-2 0
        500 http://de.archive.ubuntu.com hardy/universe Packages
        100 /var/lib/dpkg/status

Output of 'sudo apt-cache policy gnupg':
gnupg:
  Installed: 1.4.6-2ubuntu5
  Candidate: 1.4.6-2ubuntu5
  Version table:
 *** 1.4.6-2ubuntu5 0
        500 http://de.archive.ubuntu.com hardy/main Packages
        100 /var/lib/dpkg/status

Marked this bug as security vulnerability since it affects encryption and thus eavesdropping of connections!
Thank you very much in advance for fixing this!

Revision history for this message
LimCore (limcore) wrote : Re: [Hardy] Psi 0.11 connects in an infinite manner without success after enabling OpenPGP

In short:

if you enable OpenPGP for self (acount - settings) then psi does not connect (nor ask for the passphrase, I guess this is the problem).

Revision history for this message
BastyCDGS (cdgs-basty) wrote :

Greetings to thee!

Yes this is exactly the case.
Thanks to your reply I realized that it doesn't even ask for the passphrase when I connect. I even rechecked this and can absolutely confirm that it doesn't ask for a passphrase (even when it connects, strangely Psi did connect at the first attempt to the jabber.ccc.de server, then I tried also to enable OpenPGP also on the amessage.info account and trying to reconnct caused again a inifinite connection loop).

Revision history for this message
LimCore (limcore) wrote :

confirmed.

Changed in psi:
status: New → Confirmed
Revision history for this message
BastyCDGS (cdgs-basty) wrote :

With the latest updates (libqca2 was within them), the bug is fixed. Tested login yesterday evening and Psi asked for the GnuPG passphrase, worked with both jabber accounts. Today I checked an encrypted connection and this worked also, I could read the decrypted text and my conservation partner also.
So check yourself if this bug is also fixed for you. If so, you can tag this bug as FIXED...
Thank you all in advance for fixing this and I wish a good weekend to anybody here!

Revision history for this message
LimCore (limcore) wrote :

I still have this problem (most up to date ubuntu 8.04 amd64)

Btw, I guess it started around time when I switched from gnome to kde and then back again.

Revision history for this message
BastyCDGS (cdgs-basty) wrote :

Greetings LimCore!

I have attached my sources.list. Could you check out with this sources.list, i.e. doing a:
sudo aptitude update && sudo aptitude dist-upgrade

solves this problem? As said, for me it did. But do a backup of your whole system before doing this, so you can revert to your installation before if desired.

Revision history for this message
BastyCDGS (cdgs-basty) wrote :

Maybe it's a good idea to post the list of recommended updates here of aptitude/apt-get before doing it, so we can enclose the candidates fixing this bug. I didn't think of that when I did my updates (how I could, since I didn't except fixing this for me at all at this point).
BTW: For a friend with me from austria, which also uses my sources.list, this bug also went away.

I personally guess that the fix is in the hardy-backports...as far as I know, Psi does use QT4 and hardy-backports had QT 4.4 in it, maybe that solved the problem.
This would also explain your assumption, why switching to KDE (which uses QT) triggered this bug for you.

Best regards!

Revision history for this message
Ralph Janke (txwikinger) wrote :

This problem seems to be fixed and available. If there is any more information that the problem is not fixed, please provide the information and set the status to new.

Thanks

Changed in psi:
importance: Undecided → Low
status: Confirmed → Fix Released
Revision history for this message
BastyCDGS (cdgs-basty) wrote :

Damn! With some of the last updates, Psi starts to bring over the same behaviour again, i.e. can't connect with OpenPGP enabled.
I assume that QT 4.4 packages from the hardy-backports repository have something to do with this. I have latest KDE 4.05 and KDE 3.5.9 on my machine, while KDE 4.x depends on QT4 and Psi 0.11 also uses QT4.
So this bug should be reopened again if someone else than confirm this...

Lovely greetz!

Revision history for this message
BastyCDGS (cdgs-basty) wrote :

See last message from me, the bug appeared again with exact the same behaviour as at the beginning when I was posting this bug.
This is some weeks ago and still no enhancement (tested just yesterday again), so I've finally decided to reopen this bug.

Changed in psi:
status: Fix Released → New
Revision history for this message
goto (gotolaunchpad) wrote :

If it does not work does Psi use QT 4.3.4 or OT 4.4 then? Psi 0.11 is not compatible with QT 4.4.

goto (gotolaunchpad)
Changed in psi:
status: New → Incomplete
Revision history for this message
goto (gotolaunchpad) wrote :

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!

Changed in psi:
status: Incomplete → Invalid
Revision history for this message
Andreas Olsson (andol) wrote :

Strange

Running Psi, and using its OpenPGP support, worked flawlessly for me in both Hardy and Intrepid. Installing Jaunty on my computers suddenly gives me pretty much the exact same symptoms as being mentioned in the original bug report. I'm using the same OpenPGP key and the same (private) jabber server as I did before.

Tested generating a new openpgp key as well as regestering a new account at jabber.org; still the same symptoms. Well, did manage to connect having an key enabled once. Just didn't manage to repeat it afterwards.

Changed in psi (Ubuntu):
status: Invalid → Incomplete
Revision history for this message
Andreas Olsson (andol) wrote :

Almost forgot to mention involved versions

andol@pc13267:~$ apt-cache policy psi
psi:
  Installerad: 0.12-2ubuntu1
  Kandidat: 0.12-2ubuntu1
  Versionstabell:
 *** 0.12-2ubuntu1 0
        500 http://se.archive.ubuntu.com jaunty/universe Packages
        100 /var/lib/dpkg/status

andol@pc13267:~$ apt-cache policy libqca2-plugin-gnupg
libqca2-plugin-gnupg:
  Installerad: 0.1~20070904-2
  Kandidat: 0.1~20070904-2
  Versionstabell:
 *** 0.1~20070904-2 0
        500 http://se.archive.ubuntu.com jaunty/universe Packages
        100 /var/lib/dpkg/status

Andreas Olsson (andol)
summary: [Hardy] Psi 0.11 connects in an infinite manner without success after
- enabling OpenPGP
+ enabling OpenPGP (also Psi 0.12 in Jaunty)
Revision history for this message
Andreas Olsson (andol) wrote :

My current OpenPGP problems might be related to bug #367317.

Revision history for this message
Andreas Olsson (andol) wrote :

Closing this report again, as my problems went away with the fix of bug #367317.

Changed in psi (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.