@Tom-Elliott From a user point of view it is a bug when things suddenly act different then it used to be, when there are no signs of changes in the way a function is meant to work.

I have done an update to latest svn and things suddenly fails. That’s way I assume this MIGHT be a bug. Client 0.9.12 gives me an error telling “could not get security token” and “invalid security token”. The function is meant to do an client update automatically, which it now suddenly fails to do. You can of course make a statement this is not a bug, but it still act like a bug. According to the wiki this might be a problem if I uninstall/reinstall the client. This is not the case.

Putting hosts into a group and then running the suggested procedure is probably good, but how can I know which client works and which fails?

But if this is not a bug, but the way things are meant to work these days I will have to live with it. By the way, I reported a similar problem months back and then it was a bug which was fixed.