Bug 366469

Summary: yast2 users default settings for new users empty and refuse to be set
Product: [openSUSE] openSUSE 11.0 Reporter: Casual J. Programmer <casualprogrammer>
Component: YaST2Assignee: Jiří Suchomel <jsuchome>
Status: RESOLVED DUPLICATE QA Contact: Jiri Srain <jsrain>
Severity: Normal    
Priority: P5 - None    
Version: Alpha 2   
Target Milestone: ---   
Hardware: x86   
OS: openSUSE 11.0   
Whiteboard:
Found By: Beta-Customer Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: yast2logs

Description Casual J. Programmer 2008-03-02 14:46:09 UTC 
After a clean install from alpha2 DVD and update from factory new users are created with home directory /user and no login shell. Digging deeper shows that the default settings are empty. Filling them in does not stick. On restarting yast2 users they are empty again.

Notebook: Fujitsu Siemens Amilo Si 1520
Graphics: Fujitsu Siemens Mobile 945GM/GMS/GME, 943/940GML Express
Monitor:  QUANTADISPLAY LCD Monitor 1280x800@60Hz
Wireless: Intel PRO/Wireless 3945ABG Network Connection
Sound:    82801G (ICH7 Family) High Definition Audio Controller
Desktop:  gnome2-SuSE-10.3-160
YaST GUI: yast2-qt-2.16.31-3
OS:       openSUSE 11.0 (i586) Alpha2 VERSION = 11.0
Kernel:   2.6.24-6-default

rpm -qa | grep yast2 | sort

autoyast2-installation-2.16.7-8
yast2-2.16.30-3
yast2-add-on-2.16.1-17
yast2-apparmor-2.16.0-7
yast2-backup-2.16.1-33
yast2-bootloader-2.16.5-19
yast2-control-center-2.16.0-28
yast2-control-center-gnome-2.13.2-155
yast2-control-center-qt-2.16.0-28
yast2-core-2.16.38-3
yast2-country-2.16.11-5
yast2-country-data-2.16.11-5
yast2-fingerprint-reader-2.16.2-33
yast2-firewall-2.15.8-65
yast2-hardware-detection-2.16.1-14
yast2-inetd-2.15.1-101
yast2-installation-2.16.19-7
yast2-irda-2.15.1-152
yast2-iscsi-client-2.16.5-8
yast2-kerberos-client-2.16.4-4
yast2-ldap-2.16.0-3
yast2-ldap-client-2.16.9-6
yast2-libyui-2.16.38-3
yast2-mail-2.16.0-18
yast2-metapackage-handler-0.7.3-44
yast2-mouse-2.16.0-43
yast2-ncurses-2.16.17-5
yast2-ncurses-pkg-2.16.3-4
yast2-network-2.16.22-18
yast2-nfs-client-2.15.0-82
yast2-nis-client-2.16.0-53
yast2-ntp-client-2.16.4-9
yast2-online-update-2.16.7-3
yast2-online-update-frontend-2.16.7-3
yast2-packager-2.16.22-3
yast2-pam-2.16.0-54
yast2-perl-bindings-2.16.3-4
yast2-pkg-bindings-2.16.15-3
yast2-printer-2.16.7-18
yast2-profile-manager-2.16.0-43
yast2-qt-2.16.31-3
yast2-qt-pkg-2.16.27-3
yast2-registration-2.16.0-44
yast2-repair-2.16.4-20
yast2-restore-2.16.0-45
yast2-runlevel-2.16.0-45
yast2-scanner-2.15.5-100
yast2-schema-2.15.0-175
yast2-security-2.15.1-82
yast2-slp-2.15.0-89
yast2-sound-2.16.3-4
yast2-storage-2.16.11-14
yast2-storage-lib-2.16.11-14
yast2-sudo-2.16.0-18
yast2-support-2.15.3-72
yast2-sysconfig-2.15.3-115
yast2-theme-openSUSE-2.16.13-9
yast2-trans-en_US-2.16.1-3
yast2-transfer-2.16.1-27
yast2-trans-stats-2.15.0-62
yast2-tune-2.15.7-83
yast2-tv-2.16.3-26
yast2-update-2.16.4-22
yast2-users-2.16.13-3
yast2-x11-2.15.11-89
yast2-xml-2.16.0-32
yast2-ycp-ui-bindings-2.16.37-4
Comment 1 Casual J. Programmer 2008-03-02 14:47:52 UTC 
Created attachment 198150 [details]
yast2logs
Comment 2 Jiří Suchomel 2008-03-04 06:54:37 UTC 

*** This bug has been marked as a duplicate of bug 365116 ***