Version: (using KDE KDE 3.5.0) Installed from: SuSE RPMs OS: Linux I have several accounts set to "exclude from connect all". Still kopete does not respect this on startup and connects them. Of course one could distinguish between "exclude from connect all" and "exclude from connect on startup", yet IMO it does not make sense and startup should be seen as the first "connect all".
Startup is seen as "restore previous state" - it connects to precisely those accounts which were online when Kopete was closed.
Then there is a bug, at least for IRC, as for me it always connects IRC, although they are "excluded from connect all" as well as not online when quitting kopete. Just tested, there is something really wrong with current SVN. I disabled "Connect on startup" went offline with all accounts, quit kopete. Started kopete and all accounts tried to connect. Do I understand it correctly that the expected behaviour would be as follows: "connect on startup" enabled > all accounts online at quit are restored on startup. "connect on startup" disabled > none are restored. For me it is not obvious what "connect on startup" means. Enabled: Does it mean that all accounts will be connected, even if they were offline on quit? Does it mean that restoring accounts that were online on quit is allowed? Disabled: No accounts are allowed to go online on startup. Not all accounts are brought online, but only the ones that were online at quit.
Your first description of what the expected behaviour would be is my experience of how it behaves in 3.4, so I assume that's the intended behaviour. As you say, there's still a bug if it's trying to connect everything.
Then "connect on startup" should be renamed to "restore connection-status on startup". IMHO "connect on startup" states that accounts will be connected on startup, without any exceptions. So with current SVN there are two bugs and one wish: - connection state is not restored on startup if "connect on startup" is enabled. - accounts are connected, even if "connect on startup" is disabled. - "connect on startup" does not state that only accounts that were online on quit will be restored on startup.
Please keep in mind that if you're using the connection status plugin with Kopete that it will ignore your preferences for connecting accounts on startup and connect them all anyways if it detects that you have an internet connection. (If I remember correctly) If you're not using the connection status plugin, well, then, we'd need to fix the bug. :)
I used the plug-in, yet that means that there is another bug. That plug-in should respect the user's settings! Since that plug-in is a child of kopete, disabling "connect on startup" for kopete means that the child has to obey that setting too. I disabled the plug-in: Jabber is always trying to get online, no matter if it was set to offline at quit or not. ICQ and MSN are not restored if online at quit, no matter whether "connect on startup" is enabled or not.
Another confusing thing: I was told that "exlude from connection" does not mean that accounts are kept offline, even if they were online at quit. Yet without the connection-status-plug-in, that is exactly what it does. Accounts that are marked as "exclude from connect all" are not set online, when restarting kopete, although they were online at quit. This means that apparently nobody really knows what the settings "connect at startup" and "exclude from connect all" are really about. This should be clarified and their lables changed accordingly. The main disturber in the context however is the connection-status-plug-in, as it overrides every setting in the kopete settings, which it should clearly not by default.
the "exclude from connection" setting should work exactly as it does when the connection status plugin is not enabled.
A question: since there is no extra listing for the SMPPPDCS-Plugin I check here for bugs, but sometimes it is not clear which Connection Status plugin is concerned. Could it be possible to add a component for the SMPPPDCS-Plugin so that I don't need to guess if my plugin is concerned?
1. The "exclude from connection" setting should work exactly as it means - does not connect the account. 2. "Connect automatically at startup" does not work - kopete connects independently of this option. 3. Kopete automatically changes account status when it must not - f.e. changes status from "invisible" to "online" in a few minutes.
Absolutely agree with Arthur, have the same problems. Please, fix all that stuff. I do very like kopete but those bugs are very annoing. Thanks.
*** This bug has been confirmed by popular vote. ***
I tested it a bit with KDE 4.0.99 (kopete 0.50.80) and found the following behaviour: Autoconnect Activated, no account is excluded from global connection: All accounts are connected on startup, even if one or more were offline when closing. Autoconnect Activated, one account is excluded from global connection: All accounts except for the one excluded from global connection are connected, also those that were offline when closing. Autoconnect Deactivated: None of the accounts is connected So there is nothing restored, but I think that might be another good configurable option.
And btw, there is no connection status plugin in KDE 4.0.99 (kopete 0.50.80)