Bug 13508 - userdrake should inform the user that he needs to logout for the new group settings to take effect
Summary: userdrake should inform the user that he needs to logout for the new group se...
Status: NEW
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal enhancement
Target Milestone: ---
Assignee: Thierry Vignaud
QA Contact:
URL:
Whiteboard:
Keywords: USABILITY
Depends on:
Blocks:
 
Reported: 2014-06-10 16:10 CEST by nikos papadopoulos
Modified: 2015-09-21 12:17 CEST (History)
0 users

See Also:
Source RPM: userdrake
CVE:
Status comment:


Attachments

Description nikos papadopoulos 2014-06-10 16:10:42 CEST
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:
Manuel Hiebel 2014-06-12 00:48:05 CEST

Keywords: (none) => USABILITY
Assignee: bugsquad => thierry.vignaud
Summary: userdrake doesn't inform the user that he needs to logout for the new team settings to take effect => userdrake doesn't inform the user that he needs to logout for the new group settings to take effect

Thierry Vignaud 2015-09-03 14:13:54 CEST

Severity: normal => enhancement

Samuel Verschelde 2015-09-21 12:17:08 CEST

Hardware: i586 => All
Version: 4 => Cauldron
Summary: userdrake doesn't inform the user that he needs to logout for the new group settings to take effect => userdrake shouldt inform the user that he needs to logout for the new group settings to take effect
Source RPM: userdrake-2.5-1.mga4.src.rpm => userdrake

Samuel Verschelde 2015-09-21 12:17:29 CEST

Summary: userdrake shouldt inform the user that he needs to logout for the new group settings to take effect => userdrake should inform the user that he needs to logout for the new group settings to take effect


Note You need to log in before you can comment on or make changes to this bug.