empathy accounts fail to connect after manually unlocking keyring
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Empathy |
Expired
|
Low
|
|||
empathy (Ubuntu) |
Incomplete
|
Low
|
Unassigned |
Bug Description
Binary package hint: empathy
The following problem only occurs when I use auto-login.
If I DO NOT use auto-login, empathy is automatically started after logging in and my accounts connect automatically, i.e. there's a green speech bubble icon in the indicator applet and my contact list is populated.
If I DO use auto-login, upon starting up I am prompted with "Enter password to unlock your login keyring". I enter my keyring successfully, but then empathy does not appear to be started at all (e.g. no speech bubble icon in the indicator applet). If I manually start empathy via the Indicator Applet, the contacts window is blank. If I then do Edit -> Accounts, my accounts are "Offline - Status is set to offline". If I uncheck "Enabled" and then recheck "Enabled", the accounts connect and are reported as "Available". However, the contacts window remains blank. If I Quit empathy and then start empathy again, everything is fine (I finally get the green speech bubble icon and can see my contacts).
Output of `lsb_release -rd`:
Description: Ubuntu lucid (development branch)
Release: 10.04
Output of `apt-cache policy empathy`:
empathy:
Installed: 2.30.0-0ubuntu4
Candidate: 2.30.0-0ubuntu4
Version table:
*** 2.30.0-0ubuntu4 0
500 http://
100 /var/lib/
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: empathy 2.30.0-0ubuntu4
ProcVersionSign
Uname: Linux 2.6.32-19-generic i686
NonfreeKernelMo
Architecture: i386
Date: Fri Apr 9 10:59:36 2010
ExecutablePath: /usr/bin/empathy
ProcEnviron:
PATH=(custom, user)
LANG=en_AU.UTF-8
SHELL=/bin/bash
SourcePackage: empathy
Changed in empathy: | |
importance: | Unknown → Low |
status: | Unknown → New |
Changed in empathy: | |
status: | New → Incomplete |
Changed in empathy: | |
status: | Incomplete → New |
Changed in empathy: | |
status: | New → Expired |
thank you for your bug report, could you look in the account dialog if those are listed correctly when you get the issue?