|
Bugzilla – Full Text Bug Listing |
| Summary: | YaST2 user management seems to use strange defaults for new users | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.0 | Reporter: | Forgotten User QFh0D9oMPg <forgotten_QFh0D9oMPg> |
| Component: | YaST2 | Assignee: | Martin Vidner <mvidner> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | casualprogrammer, clarkt, forgotten_QFh0D9oMPg, jsuchome, monkey9, wstephenson |
| Version: | Alpha 2 | ||
| Target Milestone: | --- | ||
| Hardware: | 64bit | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
/var/log/YaST/y2log
logfiles created by YaST2 |
||
Please attach /etc/default/useradd and yast2 log files. Created attachment 197345 [details]
/var/log/YaST/y2log
user@linux:~> more /etc/default/useradd GROUP=100 HOME=/home INACTIVE=-1 EXPIRE= SHELL=/bin/bash SKEL=/etc/skel GROUPS=video,dialout CREATE_MAIL_SPOOL=no Some packages seem to be broken... - Please list /usr/share/YaST2/scrconf/etc_default_* - what about 'rpm -V'? user@linux:~> ll /usr/share/YaST2/scrconf/etc_default_* -rw-r--r-- 1 root root 571 8. Sep 2005 /usr/share/YaST2/scrconf/etc_default_passwd.scr -rw-r--r-- 1 root root 530 8. Sep 2005 /usr/share/YaST2/scrconf/etc_default_useradd.scr What exactly do you mean with "rpm -V"? The system was updated to current factory packages a few hours ago. Shouldn't YaST2 complain, if there are some problems when adding a user, instead of using faulty defaults? Ah, sorry, I mean rpm -V yast2-users rpm -V yast2-pam I (still) don't know what is wrong with the packages. One more thing: run '/sbin/yast2 users' from command line and check if there is some error output written. rpm -V gives no output at all (what is -V supposed to do?). Versions are: yast2-users-2.16.10-6.x86_64.rpm yast2-pam-2.16.0-51.noarch.rpm Running YaST2 from the command line gave no errors, YaST2 performed as if there would be no problem. Hm... try running yast2 users with 'Y2DEBUG=1 /sbin/yast2 users' and attach the new log after you reproduce the error. Created attachment 197410 [details]
logfiles created by YaST2
I deleted all /var/log/YaST/y2log* - files first. The attachment contains only the newly created logfiles after running the "users"-module.
Martin... The problem is a bug in my implementation of an improvement in agent handling: Thu Feb 7 11:09:39 CET 2008 - mvidner@suse.cz - Make SCR registration lazy: to find .foo, open only foo.scr. If that fails, only then scan all *.scr. (fate#302975) yast2-core-2.16.30 SCR::UnregisterAgent will stop looking for any other agents too, so after we unregister the agent for desktop files, the next one, for /etc/default/useradd, cannot be loaded. I should remove the stop probably. *** Bug 365668 has been marked as a duplicate of this bug. *** *** Bug 366469 has been marked as a duplicate of this bug. *** *** Bug 366426 has been marked as a duplicate of this bug. *** *** Bug 366355 has been marked as a duplicate of this bug. *** Fixed in yast2-core-2.16.39 See also http://lists.opensuse.org/archive/yast-announce/2008-03/msg00001.html for workarounds. yast2-core-2.16.38-2 is the present, so it will be up next update? The page you refer to, is probably not the right one or? (In reply to comment #17 from Robby Verberne) > yast2-core-2.16.38-2 is the present, so it will be up next update? Yes. > The page you refer to, is probably not the right one or? It is the right one. For the installation, putting Y2SCRSWEEP=1 on the boot command line should work. *** Bug 364564 has been marked as a duplicate of this bug. *** *** Bug 366665 has been marked as a duplicate of this bug. *** |
Just noticed this when trying to set up a clean new user account for testing purposes on my openSUSE factory (up-to-date) box: Added a new users - using the proposed yast2 defaults without taking too much notice of them - YaST2 gave the user ("new") the home directory "/new" and put him in the group "root" (no other group)?! The user was also given no login shell. Manually changing all this weird settings made the user account work as expected. The error seems to be reproducable. Happened with yast2-users 2.16.10-6.