Page 1 of 1

Mageia 5 - ownership changes to "nobody" after KDE login

PostPosted: Jul 20th, '15, 01:01
by macxi
Hi,
1 - I did a clean install Mageia 5 DVD (classic) KDE, 64, a physical machine, with grub boot (no grub2 and without UEFI).
2 - After installing, I set up the media, updated and then installed about 40-50 applications listed in the post installation tips (see topic Mageia 2 - Configuration tips after installing Mageia). Everything worked perfectly.
3 - When I restarted the machine, appeared to the user list, but was unable to access KDE with the common user, I had created. The KDE desktop environment not opened and the warning:

      "Call to lnusertemp failed {temporary directories full?}. Check your installation?"
.

I could access the common user-graphical environment IceWM and saw that the owner of the common user folders became the "Nobody".

Dolphin accessed as root, and fix the owner of folders.
But because restarting a few times, the error was repeated.

So I opened the bug 16420.

Then I saw that the error was repeated in other partitions with the Mageia 3 installed
What can this be?
Does error in HD can cause change in the owner?

Note: the same topic in forum Mageia of Brasil

Re: Mageia 5 - issue - common user owner change for nobody

PostPosted: Jul 21st, '15, 19:38
by doktor5000
Check the /home/username folder for the affected user, and also check / and /tmp sizes and free space via df -h
See also the comments for the same issue in an old bugreport: https://bugs.mageia.org/show_bug.cgi?id=978#c12
and also http://tech.anoj.net/2008/10/call-to-ln ... dding.html

Please also create a new user, and try to reproduce with that user.

Re: Mageia 5 - ownership changes to "nobody" after KDE login

PostPosted: Jul 22nd, '15, 14:20
by macxi
doktor5000 wrote:Check the /home/username folder for the affected user, and also check / and /tmp sizes and free space via df -h
See also the comments for the same issue in an old bugreport: https://bugs.mageia.org/show_bug.cgi?id=978#c12
and also http://tech.anoj.net/2008/10/call-to-ln ... dding.html
Please also create a new user, and try to reproduce with that user.


doktor5000,
I've created a new user
It seems to me that does not have any error in Mageia 5. It seems to me that the error was caused because the home partition was full.
I checked with the KDF and saw that the / home partition was 100% full, despite having 1GB of free space.
I'm still checking it. I've got 20GB of free space on the / home partition.
I'll check if the error is repeated and notice here.
thanks

Re: Mageia 5 - ownership changes to "nobody" after KDE login

PostPosted: Dec 15th, '15, 14:25
by macxi
The same error still occurs:

      [mageia5@localhost ~]$ su -
      Senha:
      [root@localhost ~]# ls -al /home
      total 44
      drwxr-x--x 8 root adm 4096 Jul 16 13:48 ./
      drwxr-xr-x 19 root adm 4096 Nov 7 10:35 ../
      lrwxrwxrwx 1 root root 16 Nov 7 10:23 live -> /home/mageia5/
      drwxr-x--x 2 root root 16384 Jan 30 2010 lost+found/
      drwxr-x--x 35 nobody nogroup 4096 Nov 7 18:12 mageia3/
      drwxr-x--x 43 nobody nogroup 4096 Jun 21 2013 mageia2/
      drwxr-x--x 31 mageia5 mageia5 4096 Nov 8 08:13 mageia5/
      drwxr-x--x 27 nobody nogroup 4096 Nov 1 13:11 mageia4/
      drwxr-x--x 13 nobody nogroup 4096 Mai 21 2012 xguest/
      [root@localhost ~]#
      [root@localhost ~]#
      [root@localhost ~]# df -m
      Sist. Arq. 1M-blocos Usado Disponível Uso% Montado em
      devtmpfs 487 0 487 0% /dev
      tmpfs 493 2 492 1% /dev/shm
      tmpfs 493 1 492 1% /run
      /dev/sda5 10474 6141 3779 62% /
      tmpfs 493 0 493 0% /sys/fs/cgroup
      tmpfs 493 1 493 1% /tmp
      /dev/sda1 80133 54911 25222 69% /mnt/windows
      /dev/sda8 10049 8394 1122 89% /mnt/linux
      /dev/sda7 12056 8679 3361 73% /home
      tmpfs 99 1 99 1% /run/user/1000
      [root@localhost ~]#

When the user's owner change for nobody/nogroup, if I try to access the user, an error message appears::

    "Call to lnusertemp failed {temporary directories full?}. Check your installation?"

To fix, I access a terminal as root and type:

    chown -R mageia5:mageia5 /home/mageia5
    or
    chown -R mageia3:mageia3 /home/mageia3

So I restart the computer and access the user

Re: Mageia 5 - ownership changes to "nobody" after KDE login

PostPosted: Dec 15th, '15, 15:50
by doktor5000
macxi wrote:The same error still occurs:

Code: Select all
[root@localhost ~]# ls -al /home
drwxr-x--x 31 mageia5 mageia5        4096 Nov  8 08:13 mageia5/

To fix, I access a terminal as root and type:
chown -R mageia5:mageia5 /home/mageia5

This doesn't make much sense, it already had owner and group as mageia5, see above in your output.

Question is, how do you access that /home partition, seems also from other Mageia versions.
Is it maybe also exported via NFS at some time? As the UID and GID for nobody:nogroup would be 65535, which seems really strange,
as nothing usually changes the ownership of folders in /home.

You should also be aware about the different default UID/GID in Mageia 5 compared to previous Mageia versions.
This is briefly mentioned in release notes. Since Mageia 5, new users are created starting with UID >= 1000, previously UID >= 500 was used.
This is important if you also want to access folders from a different distro.


Please also provide the output of
Code: Select all
ls -aln /home
so we can see the numerical user IDs used.

FWIW, to me the ownership of /home itself and / with root and group adm also looks strange, that's not the default.

Re: Mageia 5 - ownership changes to "nobody" after KDE login

PostPosted: Dec 15th, '15, 19:01
by macxi
This computer is a Notebook. Currently it has five partitions: Win, home, mageia3, mageia5 and swap.
The Mageia2 and Mageia4 aren't installed

    Code: Select all
    [mageia5@localhost ~]$ su -
    Senha:
    [root@localhost ~]# ls -aln /home
    total 44
    drwxr-x--x  8     0     4  4096 Jul 16 13:48 ./
    drwxr-xr-x 19     0     4  4096 Nov  8 15:11 ../
    lrwxrwxrwx  1     0     0    16 Nov  7 10:23 live -> /home/mageia5/
    drwxr-x--x  2     0     0 16384 Jan 30  2010 lost+found/
    drwxr-x--x 35 65534 65534  4096 Nov  7 18:12 mageia3/
    drwxr-x--x 43 65534 65534  4096 Jun 21  2013 mageia2/
    drwxr-x--x 35  1000  1000  4096 Dez 15 14:29 mageia5/
    drwxr-x--x 27 65534 65534  4096 Nov  1 13:11 mageia4/
    drwxr-x--x 13 65534 65534  4096 Mai 21  2012 xguest/
    [root@localhost ~]#
    [root@localhost ~]#
    [root@localhost ~]#
    [root@localhost ~]# df -m
    Sist. Arq.     1M-blocos Usado Disponível Uso% Montado em
    devtmpfs             487     0        487   0% /dev
    tmpfs                493     2        492   1% /dev/shm
    tmpfs                493     1        492   1% /run
    /dev/sda5          10474  7202       2718  73% /
    tmpfs                493     0        493   0% /sys/fs/cgroup
    tmpfs                493     1        493   1% /tmp
    /dev/sda7          12056 11774        266  98% /home
    /dev/sda1          80133 55513      24621  70% /mnt/windows
    /dev/sda8          10049  8395       1121  89% /mnt/linux
    tmpfs                 99     1         99   1% /run/user/1000
    [root@localhost ~]#
    [root@localhost ~]#
    [root@localhost ~]# ls -al /home
    total 44
    drwxr-x--x  8 root       adm         4096 Jul 16 13:48 ./
    drwxr-xr-x 19 root       adm         4096 Nov  8 15:11 ../
    lrwxrwxrwx  1 root       root          16 Nov  7 10:23 live -> /home/mageia5/
    drwxr-x--x  2 root       root       16384 Jan 30  2010 lost+found/
    drwxr-x--x 35 nobody     nogroup     4096 Nov  7 18:12 mageia3/
    drwxr-x--x 43 nobody     nogroup     4096 Jun 21  2013 mageia2/
    drwxr-x--x 35 mageia5    mageia5     4096 Dez 15 14:29 mageia5/
    drwxr-x--x 27 nobody     nogroup     4096 Nov  1 13:11 mageia4/
    drwxr-x--x 13 nobody     nogroup     4096 Mai 21  2012 xguest/
    [root@localhost ~]#

With the situation shown above, I can access the Mageia5 without problem. But if I try to access the Mageia 3, I'll have to type the command: chown -R mageia3:mageia3 /home/mageia3
If I linger a long time using Mageia3, can occur changes Mageia5 ownership to "nobody".
.
As soon as I can, I will update the "Mageia 3" to "Mageia 5" and see if this error continues to happen
.
.