hi, I've posted some of these questions before in (I guess) an unofficial KDE website forum, but got no response. My apology if you are reading this for the second time.

KDE has been getting some good reviews, we tried it, it looked good, but when we were piloting it for a few users, we noticed a few strange things:
1. when one of the users wanted to switch kde to their timezone, it asked for the password for root. ( root lives in its own timezone, it has nothing to do with those users )
2. when another user on that machine switched to her own timezone, the setting for the first user reverted to that of the second user. What are we doing wrong?!

Googling deep and wide - we still didn't find a solution.

Is KDE marketed as being ready for prime time? I mean it looks good -- neah, KDE looks GREAT!!

Or is KDE 4.6 only a preliminary version of KDE, and these basic issues will be resolved in KDE 5? Will KDE 5 be ready for prime time?

thanks a bunch
md

separate time zones per user is not considered a normal/popular use case (why your search didn't find anything) and not handled by KDE (and probably not any de) but can be done, see the following:

http://www.cyberciti.biz/faq/howto-linu ... ser-basis/
http://publib.boulder.ibm.com/infocente ... onment.htm

if you wish this to be configurable thru systemsettings or another gui tool you'll need to make a request

I think there are two settings for timezone. The one for the global/machine's timezone and the one being displayed in the clock.

The latter can be changed in context menu of clock -> settings of clock. Actually the configuration allows to select multiple timezones and specify which on to display by default.

As someone who uses KDE in multi-user mode I have found that KDE is almost completely functional in multi-user mode. Each of the users on my machine has different settings for nearly everything. If something can be changed without invoking root, then it can be set for that user.

The only obvious area which does not appear to have been addressed is that the Akonadi server appears effectively to be single user.

john_hudson wrote:The only obvious area which does not appear to have been addressed is that the Akonadi server appears effectively to be single user.

There should be no interaction between Akonadi servers of different users.
By default all communication between it and its clients happen on Unix domain sockets private to each user.

Cheers,
_

I would have expected that but Akonadi only appears to handle email from one user; the others' email appears to be handled traditionally without intervention from Akonadi.

john_hudson wrote:I would have expected that but Akonadi only appears to handle email from one user

As I said, there should be no interference whatsoever between the Akonadi servers of two users.

john_hudson wrote:the others' email appears to be handled traditionally without intervention from Akonadi.

Well, unless you are running a KDE PIM 4.6 beta or have setup Akonadi mail handling manually, then there won't be any access from Akonadi regarding mail, i.e. traditional access by a single end user application.

Cheers,
_

Why then is my first user's default address book described as an Akonadi type with a different storage location from the others? When this happened, it caused a dislocation in the contacts with some duplicates and some inaccessible. I eventually resolved the problem from copying the entries manually from the old address book where they only appeared as 'read only' into the Akonadi address book.

Now everything works the same in all users but one users' contacts are in a completely different default location.

As someone who uses KDE in multi-user mode I have found that KDE is almost completely functional in multi-user mode. Each of the users on my machine has different settings for nearly everything

I manage some machines like that, where almost everything, including the language, is different, and it works very well indeed as one would expect. That said, I can see a use case where you may want to have per-user timezones (won't anybody think of The Cloud! ) so that might be worth filling in a bug request for.

Anda,

There should be no interaction between Akonadi servers of different users.

One begs to disagree there. I have a use case where five users share access to the same 700GB directory as their $HOME/Documents/ You can imagine the amount of wastage caused by Akonadi trying to index the same files once per user. An architecture more like updatedb/locate would be worth considering, in my opinion.

B4700011 wrote:Anda,

There should be no interaction between Akonadi servers of different users.

One begs to disagree there. I have a use case where five users share access to the same 700GB directory as their $HOME/Documents/ You can imagine the amount of wastage caused by Akonadi trying to index the same files once per user. An architecture more like updatedb/locate would be worth considering, in my opinion.

Akonadi is not involved with indexing files.

Cheers,
_