Bug ID 1179261
Summary YaST doesn't copy /usr/etc/skel
Classification openSUSE
Product openSUSE Tumbleweed
Version Current
Hardware Other
OS Other
Status NEW
Severity Critical
Priority P5 - None
Component YaST2
Assignee yast2-maintainers@suse.de
Reporter fvogt@suse.com
QA Contact jsrain@suse.com
CC amajer@suse.com, dimstar@opensuse.org, fvogt@suse.com, hpj@urpla.net, kukuk@suse.com, mvetter@suse.com, sndirsch@suse.com, thorsten.behrens@cib.de, werner@suse.com
Depends on 1178296
Blocks 1178717
Found By ---
Blocker ---

Copying of /usr/etc/skel was initially added to useradd.local, but that
approach had some issues so it was implemented properly in useradd itself
instead.

Now it works properly for users created using useradd, but users created by
YaST are missing the content from /usr/etc/skel in their homes. 

YaST appears to do the copying from skel itself
(https://github.com/yast/yast-users/blob/337589043b3c41fb8e1ad18de4badfd6050a09b2/src/modules/UsersRoutines.pm#L137),
so it would need to "cp -Rn /usr/etc/skel/. ~newuser/" or so after the
/etc/skel copy.

+++ This bug was initially created as a clone of Bug #1178296 +++

node128:~ # useradd -r -d /var/lib/test0 test0
chown: cannot access '/home/test0/bin': No such file or directory

node128:~ # ls -alF /home/
total 0
drwxr-xr-x. 1 root root  62 Oct 30 10:39 ./
drwxr-xr-x. 1 root root 142 Oct 30 10:27 ../
drwx------. 1 root root  30 Oct 30 10:19 chrony/
drwx------. 1 root root  30 Oct 30 10:19 messagebus/
drwx------. 1 root root  30 Oct 30 10:19 nobody/
drwx------. 1 root root  30 Oct 30 10:19 sshd/
drwxr-xr-x. 1 root root  38 Oct 30 10:39 test0/


useradd.local creates for every system account a directory below /home, owned
by root, for copying the /usr/etc/skel files.

The current implementation seems to work only for standard users, where the
home directory is below /home, but not for system accounts, not if the
homedirectory is somewhere else, not if the skel directory shouldn't be copied
at all.

I'm afraid we need to patch the shadow suite (useradd) directly instead of
using the useradd.local helper.


You are receiving this mail because: