Description of problem: I configured "Online accounts" from the standard Gnome applet. But I wanted to use Empathy for other online accounts, not covered by the previously mentioned applet. One of the accounts I configured is the GTalk account, again. From that time, I have two GTalk accounts, and I'm unable to delete one of them, giving me a "Connection error" all the time, and then putting the applet on red all the time, as if I received a message. It's impossible, if I leave my machine alone and then come back, to know if there is an error, or a message, I must open the applet to check it. Version-Release number of selected component (if applicable): Fedora 17, Beefy Miracle, x86_64. Gnome Shell updated to the latest patchsets. How reproducible: Create an online account, the create it again with Empathy. One of them cannot be deleted, and gives a "connection error" all the time. The second account connects perfectly. Steps to Reproduce: 1. Create a GTalk account with "Online accounts". 2. Create the same GTalk account with "Empathy". 3. Close and open the session, and the error happens. Actual results: A connection error. Expected results: Being able to delete one of the accounts, or integrate Empathy with Online Accounts. Additional info: N/A
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.