Description of problem: In order to connect to configured accounts you need to perform the following context menu actions: 1) Select Online 2) Select Offline 3) Select Online Version-Release number of selected component (if applicable): telepathy-kde-presence-applet-0.3.0-2.mga2.i586.rpm How reproducible: Every time you try to connect for the first time in a session. Steps to Reproduce: 1. Configure one or more accounts for Telepathy (I used XMPP and WLM). 2. Select Online from the IM Presence applet context menu. 3. The tooltip for the IM Presence applet indicates "Connecting..." forever. 4. Select Offline from the IM Presence applet context menu. 5. Select Online from the IM Presence applet context menu. 6. The accounts will now be connected. 7. Further Offline and Online selections work as expected.
this seems more an upstream bug for (I have found one but from 2009), maybe you can open a new one at bugs.kde.org ?
CC: (none) => balcaen.john
It's more an upstream bug but i would wait for the update to 0.3.1 after the release before opening an upstream bug. However does it happens with both accounts ? (xmpp & WLM) ? Here i can't reproduce (using 2 xmpp accounts, WLM & an aim account ).
Yes, nothing connects first time.
Hi, This bug was filed against cauldron, but we do not have cauldron at the moment. Please report whether this bug is still valid for Mageia 2. Thanks :) Cheers, marja
Keywords: (none) => NEEDINFO
can you test against last cauldron rpms please ?
CC: (none) => nicolas.lecureuil
@Niel : Could you give us a repons at comment 4 within 2 weeks. Roelof
CC: (none) => r.wobben
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution. Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information. Closing as OLD.
Status: NEW => RESOLVEDCC: (none) => marja11Resolution: (none) => OLD