I'm sorry that this doesn't contain any important information.  The following is some helpful information from the downstream report:

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://au.archive.ubuntu.com/ubuntu/ lucid/main Packages
        100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: empathy 2.30.0-0ubuntu4
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-19-generic i686
NonfreeKernelModules: nvidia
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

I don't know if a CM log would help.  Or even if this is an empathy problem, which should have been found out downstream before.  Let me know what else you'd need to help you out.

Sorry about lack of info. First time reporting bug. There's more info in people's discussion in the downstream bug.

Apparently it doesn't happen if you have a gwibber IM account setup in indicator-me, but I can't confirm that.

What else do I need to help out?

@Peter, it's nothing you've done.  The report is here and thats the most important thing :)

I'd be interested in seeing the telepathy-mission-control logs. You can get them using empathy-debugger.

Created attachment 183647 [details]
mission-control log from empathy-debugger

@Guillaume, here's the log you requested. I've replaced my gmail account details in the log with '<#Acc Removed#>'

This log was generated by following these steps:
- clean boot
- ubuntu login bypassed, presented with multiple "Unlock Keyring" dialogs 
 /* more than one widget needs access, e.g. Docky gmail-checker, indicator-me (empathy) */
- enter keyring pw in 1st dialog, press esc to cancel the rest
- run empathy-debugger from terminal and save log (there were more logs before reboot, now just the mission-control one)

Hope this helps.

I just want to add my OS & empathy version info:

$ lsb_release -rd
Description:	Ubuntu 10.10
Release:	10.10

$ apt-cache policy empathy
empathy:
  Installed: 2.32.1-0ubuntu1.1
  Candidate: 2.32.1-0ubuntu1.1
  Version table:
 *** 2.32.1-0ubuntu1.1 0
        500 http://ftp.sun.ac.za/ftp/ubuntu/ maverick-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     2.32.0-0ubuntu2 0
        500 http://ftp.sun.ac.za/ftp/ubuntu/ maverick/main amd64 Packages

Any progress on this bug? I've given the extra info requested over a month ago.
Why still Staus:NEEDINFO? What other info can I provide?

Upgraded to Ubuntu 11.04 - it's still happening.

-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/empathy/issues/351.