does not complete Empathy 3 password migration if MC < 1:5.12.1-3 was ever used

Bug #1060964 reported by Simon McVittie on 2012-10-03
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Telepathy Mission Control 5
Unknown
Unknown
telepathy-mission-control-5 (Debian)
Fix Released
Unknown
telepathy-mission-control-5 (Ubuntu)
Undecided
Unassigned

Bug Description

This is Debian #687933 and is fixed upstream in 5.12.3 and 5.13.2. (We'll be doing a 5.14.0 stable-branch release shortly, with the same code as 5.13.2.)

Steps to reproduce
==================

* Have Empathy on an old Ubuntu version (Empathy 2.x) with an IM (e.g. Jabber) account
* Upgrade to a version of Ubuntu that had
  empathy (>= 3) but telepathy-mission-control-5 (<< 1:5.12.1-3)
* Change your IM password (e.g. via your provider's website)

Expected result
===============

* Empathy tries to sign in with your saved password, fails, and prompts
  you for your password. You provide the new password. It works.

Actual result
=============

* Mission Control still knows your old password and tries to sign in with it.
  Empathy is never asked for your password, and does not have the opportunity
  to ask you for the new one. Sign-in fails and it is non-obvious how
  to recover.

Workaround
==========

Run seahorse and delete Mission Control's version of the password -
the one that seahorse calls a "Telepathy password" (as opposed to
"Instant messaging password", which is Empathy's version).

Simon McVittie (smcv) wrote :

Here is the patch for this specific bug:

http://cgit.freedesktop.org/telepathy/telepathy-mission-control/commit/?h=telepathy-mission-control-5.12&id=eaefb264316f206186b2ac7f1f36e6a4692deb3d

although I recommend upgrading to 5.14.0 instead. 5.13.x were a development branch and will not receive bugfix releases.

tags: added: patch-accepted-upstream quantal
Changed in telepathy-mission-control-5 (Debian):
status: Unknown → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

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