Bug 239688

Summary:	Initial user created with invalid group id
Product:	[openSUSE] openSUSE 10.2	Reporter:	Juha Laiho <Juha.Laiho>
Component:	Installation	Assignee:	Jiří Suchomel <jsuchome>
Status:	RESOLVED FIXED	QA Contact:	Jiri Srain <jsrain>
Severity:	Normal
Priority:	P5 - None	CC:	christophe.dr
Version:	Final
Target Milestone:	---
Hardware:	i586
OS:	Other
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Bug Depends on:
Bug Blocks:	218393
Attachments:	Yast logs covering the installation

Description Juha Laiho 2007-01-28 13:56:03 UTC

The initial non-root user created during openSUSE 10.2 installation
is created with uid=1000,gid=1000, but no group matching that gid is
created.

The immediate result of this is that resmgr session setup for the user
concerned will fail when logging in via kdm;
/var/log/warn will contain lines like:
Jan 28 14:42:00 chaos kdm: :0[17221]: pam_resmgr: resmgr login failed
Jan 28 14:59:11 chaos kdm: :0[17221]: pam_resmgr: resmgr logout failed

... and after such a login "/sbin/resmgr dump sessions" will indicate
that no sessions exist. Running resmgrd with debug output enabled will
show the error message revealing the problem, that it is refusing the
connection due to non-existence of group with gid 1000.

The further effect of this is that f.ex. scanner access is blocked - so
this is one root cause for bug 218393. I suspect that this does also
affect a number of other "desktop device" access grants.

Comment 1 Matej Horvath 2007-01-31 17:54:49 UTC

Please attach your yast logs.
http://en.opensuse.org/Bugs/YaST

Comment 2 Juha Laiho 2007-02-01 17:55:10 UTC

Created attachment 116901 [details]
Yast logs covering the installation

Comment 3 Jiří Suchomel 2007-02-02 13:59:47 UTC

Hm, it's the case user was imported from previous system, where he had group 1000 as a default group...

Comment 4 Juha Laiho 2007-02-02 22:05:36 UTC

This seems odd. I think I did have such a user on the previous installation, but I'm pretty confident I chose to make a new installation, instead of any kind of update. But then, that'd explain the invalid gid.

Comment 5 Jiří Suchomel 2007-02-05 10:22:42 UTC

fixed for SLES10SP1 and openSUSE 10.3

Comment 6 Jiří Suchomel 2007-03-29 11:43:53 UTC

*** Bug 253279 has been marked as a duplicate of this bug. ***