Version: 1.2.2 (using KDE Devel) Installed from: Compiled sources OS: Linux Everytime I log into KDE two instances of akregator are started and I have to close the warning message box, quit the instances and start akregator manually. This is annoying. I've used from time to time another X session parallel. Could this be the cause as the warning message talks about another display? I've disabled the akregator plugin in Konqueror: still the same. Tell me in which config files I should look or which files I can delete. I tried it already myself but without luck.
Are there really two instances running (which I doubt) or did you conclude that from the error message? The problem in 3.5.2 that the akregator PID in the lockfile $KDEHOME/share/apps/akregator/lock isn't resetted on Akregator shutdown, so if Akregator gets the same PID again on next start, the warning dialog appears. This happens only on systems where the startup sequence is fixed in a way that every app gets the same PID on every startup. Which is not the case on my system, so this one slipped through... A workaround until 3.5.3 is to delete the lock file on KDE startup (before akregator is started). This is fixed in SVN, so if it is the cause of your problems (which I assume), this bug can be closed.
Just for clarification the error message: "Akregator already seems to be running on another display on this machine. Running akregator more than once is not supported by the Metakit backend and can cause ..." The process table shows me just one akregator process and some kio slaves (file and http). The kio_file ones disappear after a short time. I've updated to 544821. No change so far. Quitted the current session, deleted the lock file, restarted kdm, logged in, issue rises up again.
I'll get two tray icons and clicking on them raises a separate akregator main window for each.
KDE build from sources (SVN 544821) Qt 3.3.6 (qt-copy w/ applied patches) SUSE Linux 10.1 kernel 2.6.16.13-4-default (SUSE) gcc (GCC) 4.1.0 (SUSE Linux)
Is this still an issue with 3.5.4?
Yes, the second icon has vanished, but the error message stayed. And I have to restart Akregator to make it usable.
I don't know, wether you have changed anything with respect to the lock, but it seems to work again (3.5 branch, 588368).