Bug 13508

Description of problem:
When you use userdrake and make changes in a users team(s),
if that user is logged in,
he must logout and login before the change takes effect.

But there is no message telling the user that.
He will have to figure it out, for himself, by trail an error.

And I don't know if that applies only to team settings...

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:

A.
1. Log to your system as UserSomething.
2. Open "userdrake" as root.
3. Change the default team of the user UserSomething (eg. from "live" to "usersomething").
4. Open your file manager and create a file in UserSomething's home directory.
5. The files properties will show it has been created under the old team (in the example, the team will still be "live" )



B. 
1. Log to your system as UserSomething.
2. Open "userdrake" as root.
3. Add user UserSomething to team "fileshare" (create the team first if it doesn't exist)
4. As root, create the folder "/home/share/", define as team "fileshare", and give read-write-execute access to the team.
5. As UserSomething, open a file manager and try to create a file in /home/share .
6. It will reply you can't.

In both scenarios above, you will have to log out as UserSomething, and then log in again,
to be able to use the new team settings.

Reproducible: 

Steps to Reproduce: