On Thu, 02 Apr 2009, Isaac Hailperin wrote:
After confirming, the autoinstall process continues. Right before I can log in, I get "Could not update ICEauthority file /var/lib/gdm/.ICEauthority" I confirm, and get: "There is a problem with the configuration server. (/usr/lib/GConf/2/gconf-sanity-check-2 exited with status 256)"
(Sorry to reply to an 18-month-old message, but I thought I would share the solution for the archives...) I recently encountered the exactly same problem. I also thought it was related to adding packages to my autoinst.xml. The problem is described by this Novell KB article, although they do not mention adding/removing packages: http://www.novell.com/support/search.do?cmd=displayKC&externalId=7006641 The "Could not update ICEauthority file /var/lib/gdm/.ICEauthority" happens because the ownership of the /var/lib/gdm directory is incorrect. This in turn happens because the "gdm" user is explicitly created by autoinst.xml (as it will when you "clone" a system using "yast2 autoyast"), instead of being created dynamically by the gdm package itself. My guess is that when you add or remove packages that themselves create users (in my case, it was vsfptd), it changes which UID is assigned to the gdm user when the gdm package itself is installed. (Both packages call "useradd" without specifying a specific ID, so they will just grab consecutive UIDs on the system.) Then when you have explicitly listed the gdm user in the <users> section of autoinst.xml, the UID gets changed to whatever it was on the system you cloned. The solution is to remove the gdm user -- and any others that are created by package installed -- from the <users> section. This is a very nasty failure mode, by the way. Perhaps the "clone" functionality of autoyast could be made smarter? - Pat -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org