Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#15723 - [psi] 0.13 does not connect

Attached to Project: Arch Linux
Opened by Andrej Podzimek (andrej) - Wednesday, 29 July 2009, 18:31 GMT
Last edited by Pierre Schmitz (Pierre) - Saturday, 03 October 2009, 17:01 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Pierre Schmitz (Pierre)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

Psi 0.13 can't connect to OpenFire server. Psi 0.12, Pidgin and about five other Jabber clients work fine. The connection is TLS encrypted.

* config and/or log files etc.

Psi outputs this on the console after each failed connection attempt:

Unknown signature value: 795

Steps to reproduce:

Try to connect to OpenFire over TLS with Psi 0.13.
This task depends upon

Closed by  Pierre Schmitz (Pierre)
Saturday, 03 October 2009, 17:01 GMT
Reason for closing:  Upstream
Comment by Roman Kyrylych (Romashka) - Wednesday, 29 July 2009, 18:39 GMT
Hm.. Looks like upstream bug.
Andrej, did you report it to psi develoepers? If no then please do.
Comment by Roman Kyrylych (Romashka) - Wednesday, 29 July 2009, 18:41 GMT
Also, did you try to connect to some other Jabber server?
Comment by Pierre Schmitz (Pierre) - Wednesday, 29 July 2009, 18:55 GMT
I use PSI 0.13 on different machines to connect to an openfire server over TLS.
Comment by Pierre Schmitz (Pierre) - Wednesday, 29 July 2009, 20:36 GMT
OK, I get the same output:

psi
qca-gnupg: disabling keyring monitoring due to buggy Qt version
Iconset::load(): Failed to load iconset.xml
Unknown signature value: 795

Although these errors are strange they seem not to describe the problem as it still works for me.
Comment by Roman Kyrylych (Romashka) - Wednesday, 29 July 2009, 20:41 GMT
"disabling keyring monitoring due to buggy Qt version"? What does it mean?
Is it some incompatibility between qca and Qt?
Comment by Andrej Podzimek (andrej) - Saturday, 03 October 2009, 16:45 GMT
  • Field changed: Percent Complete (100% → 0%)
Doesn't work at all for me.

Please note that this is an IPv6 compatibility issue. If you don't have an IPv6-only network with DNS over IPv6, then you can't see the bug in action.
Comment by Pierre Schmitz (Pierre) - Saturday, 03 October 2009, 17:01 GMT
Sorry, but there is nothing I could do about this.

Loading...