Version: 1.0.2 (using KDE 3.4.0 Level "b" , SUSE 9.3) Compiler: gcc version 3.3.5 20050117 (prerelease) (SUSE Linux) OS: Linux (i686) release 2.6.11.4-21.9-smp I am a linux newbie... so when I tried to start another instance of sw,(obviously under same user), because I had not realized that the program was already running, as per icon on application bar... the second instance quitted, without no explanation/warning message at all: I really wasn't able to realize the reason why the application was quitting! A messagebox - Akregator is already running - or bringing focus on the first instance before quitting the second instance - would be, IMHO, a godsend.
It should behave like other unique applications - the running instance should be brought to foreground.
Why did you confirm that bug? Akregator correctly goes to foreground when it has been started a second time.
It doesn't do that here - With KMail it works, with Akregator it does not.
Hi, No, that is not correct, at least on my machine. I have checked:first I start Akregator, and minimize it: at this point, if I start a new instance from menuK -> internet -> RSS Rader, I see a litte mini-icon dancing near near my mouse pointer for a little, then it disappear. And Akregator is still minimized, and no warning message is issued... so, if the user has an abnormal number of applications running - or isn't a "conscious linux user" it may happen -as happened to me - to be not able to realize the reason way of such annoying behavour... Hoping this can help,.. But no problem, and thanks for the nice RSS reader: I use it anyway! ;-) Bye, Virgix -----Original Message----- From: Eckhart "Wörner" <kde@ewsoftware.de> To: dev@virgilio.org Date: 15 Nov 2005 21:42:05 -0000 Subject: [Bug 115574] request a warning message when starting a second instance of application [bugs.kde.org quoted mail]
I don't have this bug anymore since I updated kdelibs. It works now with both 3.5 branch and trunk/. I don't know if it is related to the update - I don't see any related changes (actually no changes at all) in the respective classes like KUniqueApplication. So if it works for 3.5 users but not for 3.4 users we can close this bug. Another matter is kontact - selecting the Akregator part in kontact doesn't bring running Akregator instances to foreground.
Closing. Reopen with this still is an issue in 3.5.x.