Hide Forgot
Description of problem: I work with kde, and use empathy for communications. In Fedora 15, I only had to launch empathy once. (I think) Kde's session management remembered it was started when I logged out, and would automatically launch empathy again when I logged in again. In Fedora 16, this doesn't happen anymore. Each time I log in, I have to launch empathy again. Not a serious bug, but annoying enough, impractical and a regression compared to Fedora 15. Version-Release number of selected component (if applicable): empathy-3.2.2-1.fc16.i686 How reproducible: Always Steps to Reproduce: 1. Log in into kde 2. Start empathy 3. Log out and in again Actual results: Empathy is not restarted automatically. Expected results: The opposite, that empathy is restarted automatically. Additional info: This is on a system migrated from Fedora 15 to Fedora 16, and fully up to date. If any additional info is needed, let me know.
The workaround for this is: 1. Go to KDE's "System Settings" 2. Choose "Startup and Shutdown" 3. Choose "Autostart" 4. Choose "Add Program" and add Empathy to startup items Unfortunately, one gotcha here is that you'll lose autologin for some reason. It will spin and spin, fail, make you press the + sign to log in again, and present the dialog box with credentials filled in. All you have to do is press "OK" again, but you DO have to do it with every login.
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. 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 '16'. 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 16'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 16 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 to click on "Clone This Bug" and open it against that version of Fedora. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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. Thank you for reporting this bug and we are sorry it could not be fixed.
I am now running Fedora 18 and this is still a problem, so I'm reopening the bug.
I will add that at first sight the workaround mentioned in comment 1 works better now. I have added empathy to kde's autostart. It does start now at login and it will autoconnect to the the sip account I have configured. So the question that remains to be answerred is mainly this: Is a gnome program supposed to be managed by kde's session management (meaning, when the program was still open at logout, it should automatically start up at the next login) ? It used to be in Fedora 15, but apparently is not anymore. If kde's session management should be able to handle gnome apps, there is still a bug. Otherwise this can be closed as the workaround is then the normal way to handle it.
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.