Package: telepathy-mission-control-5
Version: 1:5.12.1-2
Severity: serious
Justification: maintainer's opinion: poor user experience during upgrade
Tags: patch upstream
Forwarded: https://bugs.freedesktop.org/show_bug.cgi?id=42088
Telepathy upstream has moved from storing passwords in Mission Control
(which stores them in gnome-keyring if available, or in plain-text)
to querying for them interactively at connection (which, in practice, means
they come from gnome-keyring for Empathy users, or KWallet for kde-telepathy
users).
While upgrading from the version of Empathy in squeeze to the version in
wheezy, Empathy is meant to migrate passwords from Mission Control's storage
to its own separate storage in gnome-keyring. It does this in the obvious
way, described by this pseudocode:
foreach account:
if the account's connection manager can get passwords interactively:
try:
get the password from Mission Control
copy it to a different item in gnome-keyring, which Empathy uses
delete the item that Mission Control would have used
except:
log a warning and move on
Unfortunately, Mission Control has a long-standing bug that means it cannot
delete passwords from gnome-keyring, which I've recently fixed upstream.
This means you end up with two copies of the password: one that MC will
use, and one that Empathy would use if given the chance (but because MC
thinks it knows the password, it will never ask Empathy).
This is particularly annoying if you change your password. Changing the
password in Empathy will change Empathy's gnome-keyring item, which
has no effect on the leftover MC gnome-keyring item, which is the one
that is actually used!
I believe my upstream patches from fd.o #42088 should fix this. I have a
virtual machine image in which I'm going to test it, copied after
installing squeeze, adding a couple of IM test accounts and upgrading to
wheezy in a text console, but before logging in to the wheezy GUI for the
first time and triggering the automatic migration.
-- System Information:
Debian Release: wheezy/sid
APT prefers testing-proposed-updates
APT policy: (500, 'testing-proposed-updates'), (500, 'unstable'), (500,
'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages telepathy-mission-control-5 depends on:
ii dconf-gsettings-backend [gsettings-backend] 0.12.1-2
ii libc6 2.13-35
ii libdbus-1-3 1.6.4-1
ii libdbus-glib-1-2 0.100-1
ii libglib2.0-0 2.32.3-1
ii libgnome-keyring0 3.4.1-1
ii libmission-control-plugins0 1:5.12.1-2
ii libnm-glib4 0.9.4.0-5
ii libtelepathy-glib0 0.19.3-1
ii libupower-glib1 0.9.17-1
telepathy-mission-control-5 recommends no packages.
Versions of packages telepathy-mission-control-5 suggests:
ii telepathy-haze 0.6.0-1
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
