Mageia forum

Just finished a clean install of Mageia3 and all was well until I restored all my data using Deja Dup from my old machine. My password was rejected at log on even though I tried the correct one for the new and old machines. Deleted myself as a user and then re-input but whenever I try to associate myself with the data, I cannot log on. If I just create a new user all works fine. I presume this is an access right problem but have no idea how to solve. All assistance appreciated.

Well, the data from the old machine, what installation was that? Also Mageia or another distro?
The permissions on the data (what exactly did you restore, only the contents of your /home folder or more?) can be easily changed
but first we need to know where exactly.

Also, what do the current permissions look like. Can you please post the output of

Code: Select all

ls -al /home

Many thanks for the reply. I am not at this PC until the weekend and I will post the output. Backup is from an Ubuntu 12.04 machine and included home directory with a few exclusions.

root cause analysis: and all was well until I restored all my data using Deja Dup from my old machine

included /home?

what else did it include

possible that the uid of your data is now owned by whatever uid owned it before.

but that would not stop authentication, may cause mounting of home and access to kde/gnome config files issues, etc

those issue may prevent window manager starting.

but /etc/shadow combined with /etc/passwd contain your userid and login.

if youve overwritten that , then i can assume you have overwritten all sorts

and at that point i say, go back to start and have another go.....

regards peter

Output as listed below. stevedata is a renamed directory of the imported data.

steve is from a new user I created

Hope this helps shed some light on the problem.

Code: Select all

[steve@localhost ~]$ ls -al /home
total 28
drwxr-xr-x  5 root  root   4096 Jan  9 17:58 ./
drwxr-xr-x 19 root  root   4096 Jan 10 19:43 ../
drwx------ 15 guest guest  4096 Jan  9 17:41 guest/
drwx------ 23 steve steve  4096 Jan 10 19:42 steve/
drwxr-xr-x 72 steve steve 12288 Jan  9 17:54 stevedata/
[steve@localhost ~]$

try this command:

Code: Select all

 cat /etc/passwd | grep steve

There should be only one line output. I'm thinking you may have more than one steve defined, and each will have its own UID - and if so, that is your problem.

Thanks for the suggestion, output below

Code: Select all

[steve@localhost ~]$  cat /etc/passwd | grep steve
steve:x:500:500:Steve:/home/steve:/bin/bash
[steve@localhost ~]$

Well, that line is correct.

I guess I don't know what you mean by "associate yourself with the data...". I'm quite sure that your user can browse into the stevedata directory; the permissions say so.

Now, it could be that file permissions inside the stevedata directory are wrong...I don't know. So what you could do is chown the entire directory:

Code: Select all

chown -R steve:steve stevedata

That will give you ownership of every file in stevedata, and then you will be able to access all of it, if you aren't able to now.

Thanks very much for the suggestion, it has sorted it. Much appreciated

And Stevertr, please don't forget to mark this topic solved.
One can do so, by editing the title/subject of the first message.
Write [SOLVED] to the left of it, and it's fixed.

Thanks ahead.