Bug 365547

The problem is not with missing warning message, but with the unsuccessful change to non-encrypted directory.

Please attach the log files: http://en.opensuse.org/Bugs/YaST#I_reported_a_YaST2_bug.2C_and_now_I_am_asked_to_.22attach_y2logs.22._What_does_that_mean.2C_and_how_do_I_do_that.3F

Created attachment 197644 [details]
y2logs

I could not fully reproduce the problem, but here's what I did

- Logged with user 'test';
- open up yast2;
- remove encryption of home directory selection;
- save the changes;

The results are
- I cannot log in on X with user 'test', some files are missing plus other errors

"User's $HOME/.dmrc file is being ignored. This prevents the default session and language from being saved. File should be owned by user and have 644 permissions. User's $HOME direcroty must be owned by user not writable by other users."

"The GNOME session manager was unable to lock the file '/home/test/.ICEauthority'. Please report this ......."


When I say that I could not fully reproduce the problem, it is because the first encounter of this problem was with a encrypted home directory file of 20GB. When I wanted to revert back to unencrypted home directory, nothing was left of the previous home directory (which is not deleted when you apply for encrypted home directory). I did not manage to mount back the encrypted home directory.



Note that when I do this procedure on user 'test' while being loggeg with another user, then everything works without any problem.

I must also add that a warning message is not the problem as you say - but this process is fragile and dangerous and when it breaks, the user gets his home directory corrupted.

Created attachment 197663 [details]
patch for /usr/share/YaST2/modules/UsersRoutines.pm

Please patch your /usr/share/YaST2/modules/UsersRoutines.pm, try to reproduce the buggy behavior again and attach the new log files.

And, what was the name of the user with the first problem (comment 0)? I'm asking to find it quicker in the logs (if it is there).

Unfortunately, I did cleared up folder /var/log before making this new test, so you will not find the problem I had with the 20GB in the logs...

(In reply to comment #6 from Issa Gorissen)
> Unfortunately, I did cleared up folder /var/log before making this new test, so
> you will not find the problem I had with the 20GB in the logs...

OK, try at least the 'test' problem with the enhanced logging with the patch.

Created attachment 197670 [details]
y2logs after 1st patch

'test' was logged in during the test, right? Is the result different when it is logged out?

OK. I tested myself and

a) was not able to reproduce the behavior described in comment 0. 
b) was able to reproduce the behavior with user "test": the problem was that "test" was logged while yast tried to uncompress 

In other words, disabling encrypted directory always works for me if the user is not logged in. Could you please confirm this?


Solution (for openSUSE11) is to disable the operation when user is logged in. 

Additionally, I could add some more checks if some operations (like mount, mkdir etc.) fail during the decompression. This is actually my only idea why the case from comment 0 happened.

Yes I confirm that when done with a user different from the one being manipulated, then the procedure works.

OK, so I will move the bug to openSUSE, and the only fix will be, not allowing to uncheck Encrypted directory when the user is logged in.

Just another hint to your original problem: even if something failed during decrypting, maybe there left the files $HOME/<your_user>.img and $HOME/<your_user>.key. It is possible to extract the data from the img file using the key file via "cryptconfig open" command.

(In reply to comment #12 from Jiří­ Suchomel)
> OK, so I will move the bug to openSUSE, and the only fix will be, not allowing
> to uncheck Encrypted directory when the user is logged in.

Done in yast2-users-2.16.16