desktop-packages team mailing list archive
-
desktop-packages team
-
Mailing list archive
-
Message #143496
[Bug 417432]
Created attachment 118909
certificate.workaround.patch
telepathy-haze 0.8.0 path certificates
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to telepathy-haze in Ubuntu.
https://bugs.launchpad.net/bugs/417432
Title:
Groupwise Messenger - Empathy / telepthy-haze
Status in Telepathy Haze:
Confirmed
Status in telepathy-haze package in Ubuntu:
Triaged
Bug description:
Ubuntu Juanty 9.04
Empathy:
Installed: 2.27.5-0ubuntu1~ppa9.04+1
telepathy-haze:
Installed: 0.3.1-1~ppa9.04+1
Reported This Bug Upstream.
Expected Behavior: Once you open empathy. Go to Accounts and create a Groupwise
Messenger Account, After you close the create accounts, you should be connected to
Groupwise Messenger Server or prompted to accept the server certificate, and after accepting
it use the account without any required further actions on the Users Part.
What Actually Occurs: The Groupwise Messenger account is created, but does not
open/connect. If you go back to the accounts area you will see that the
Groupwise Messenger account icon indicator is flashing, which alerts that there
is an issue with the account not connecting properly.
Discovered Workaround: cp
~/.purple/certificates/x509/tls_peers/<gwmessenger_servername>
/tmp/haze-<random_generated_per_session>/certificates/x509/tls_peers
It seems as though when a new empathy session is started, a new
/tmp/-haze-<random_generated_per_session>/certificates/x509/tls_peers is
created.
The groupwise session certificate needs to by copied from the
~/.purple/certificates/x509/tls_peers directory to the /tmp/haze- directory
generated with the connection.
This has occurred in both default empathy as well as the Daily PPA
version (2.27.5 on the machine I reported to bugzilla from), in
Jaunty. Will test and report back with Karmic on Monday.
To manage notifications about this bug go to:
https://bugs.launchpad.net/telepathy-haze/+bug/417432/+subscriptions