https://bugzilla.novell.com/show_bug.cgi?id=337809 Summary: Upgrade installation over 10.1 system corrupts xdmrc startup file Product: openSUSE 10.3 Version: Final Platform: i686 OS/Version: SuSE Linux 10.1 Status: NEW Severity: Normal Priority: P5 - None Component: Update Problems AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: dmk@applied-cs-inc.com QAContact: jsrain@novell.com Found By: Other [from my upgrade remarks file] 2007/10/29 The upgrade of my SuSE 10.1 system to 10.3, went pretty smoothly, except that the automatic "genkdmconf" upgrade of the (installation default from 10.1) /opt/kde3/share/config/kdm/kdmrc file garbled it so badly that the kdm startup failed (with lots of "multiple entries" errors (see below). This may be an artifact of skipping 10.2, but I don't know. If this is the case, it may not be critical, but should probably be fixed. Fortunately, there was a handy README file in the /opt/kde3/share/config/kdm/ directory: --------- This automatically generated configuration consists of the following files: - /opt/kde3/share/config/kdm/kdmrc - /opt/kde3/share/config/kdm/backgroundrc This config was derived from existing files. As the used algorithms are pretty dumb, it may be broken. Information from these files was extracted: - /etc/inittab Old files that would have been overwritten were renamed to <oldname>.bak. Try 'genkdmconf --help' if you want to generate another configuration. You may delete this README. --------- and the output of 'genkdmconf --help' was VERY helpful! --------- genkdmconf - generate configuration files for kdm If an older xdm/kdm configuration is found, its config files are "absorbed"; if it lives in the new target directory, its scripts are reused (and possibly modified) as well, otherwise the scripts are ignored and default scripts are installed. options: --in /path/to/new/kdm-config-dir In which directory to put the new configuration. You can use this to support a $(DESTDIR), but not to change the final location of the installation - the paths inside the files are not affected. Default is /opt/kde3/share/config/kdm. --old-xdm /path/to/old/xdm-dir Where to look for the config files of an xdm/older kdm. Default is to scan /etc/X11/kdm, $XLIBDIR/kdm, /etc/X11/xdm, $XLIBDIR/xdm; there in turn look for kdm-config and xdm-config. Note that you possibly need to use --no-old-kde to make this take effect. --old-kde /path/to/old/kde-config-dir Where to look for the kdmrc of an older kdm. Default is to scan /opt/kde3/share/config and {/usr,/usr/local,{/opt,/usr/local}/{kde3,kde,kde2,kde1}}/share/config. --no-old Don't look at older xdm/kdm configurations, just create default config. --no-old-xdm Don't look at older xdm configurations. --no-old-kde Don't look at older kdm configurations. --old-scripts Directly use all scripts from the older xdm/kdm configuration. --no-old-scripts Don't use scripts from the older xdm/kdm configuration even if it lives in the new target directory. --old-confs Directly use all ancillary config files from the older xdm/kdm configuration. This is usually a bad idea. --no-backup Overwrite/delete old config files instead of backing them up. --no-in-notice Don't put the notice about --in being used into the generated README. --------- So, the solution was to run (as root) the command: genkdmconf --no-old which did NOT try to incorporate anything from the default kdmrc file installed with SuSE 10.1. After that, a reboot brought up X, with me auto-logged-in - I don't know why it did this, perhaps because that was the user of the "previous" KDE session. I used sax2 (the SuSE KDE configuration GUI) to modify this behavior to my liking: ConfigureDesktop->KdeControlCenter->AdminMode->LoginMgr->Convenience-> PreselectUser->none After that, on logging out of the KDE/X session, the login manager came up, and all is well. Other than this, everything seems to be 100%... good job folks! Dave ============================================================================ ---------------- kdm startup errors (from /var/log/messages) --------------- Oct 29 09:27:54 ns2 kdm_config[20494]: Multiple occurrences of key 'Enable' in section [Xdmcp] of /opt/kde3/share/config/kdm/kdmrc Oct 29 09:27:54 ns2 kdm_config[20494]: Multiple occurrences of key 'AllowRootLogin' in section [X-*-Core] of /opt/kde3/share/config/kdm/kdmrc Oct 29 09:27:54 ns2 kdm_config[20494]: Multiple occurrences of key 'Language' in section [X-*-Greeter] of /opt/kde3/share/config/kdm/kdmrc Oct 29 09:27:54 ns2 kdm_config[20494]: Multiple occurrences of key 'ShowUsers' in section [X-*-Greeter] of /opt/kde3/share/config/kdm/kdmrc Oct 29 09:27:54 ns2 kdm_config[20494]: Multiple occurrences of key 'UseBackground' in section [X-*-Greeter] of /opt/kde3/share/config/kdm/kdmrc Oct 29 09:27:54 ns2 kdm_config[20494]: Multiple occurrences of key 'UseTheme' in section [X-*-Greeter] of /opt/kde3/share/config/kdm/kdmrc Oct 29 09:27:54 ns2 kdm_config[20494]: Multiple occurrences of key 'Theme' in section [X-*-Greeter] of /opt/kde3/share/config/kdm/kdmrc Oct 29 09:27:54 ns2 kdm_config[20494]: Multiple occurrences of key 'AllowNullPasswd' in section [X-:*-Core] of /opt/kde3/share/config/kdm/kdmrc Oct 29 09:27:54 ns2 kdm_config[20494]: Multiple occurrences of key 'AllowShutdown' in section [X-:*-Core] of /opt/kde3/share/config/kdm/kdmrc Oct 29 09:27:54 ns2 kdm_config[20494]: Multiple occurrences of key 'AllowRootLogin' in section [X-:*-Core] of /opt/kde3/share/config/kdm/kdmrc Oct 29 09:27:54 ns2 kdm_config[20494]: Multiple occurrences of key 'AutoLoginEnable' in section [X-:0-Core] of /opt/kde3/share/config/kdm/kdmrc Oct 29 09:27:54 ns2 kdm_config[20494]: Multiple occurrences of key 'AutoLoginUser' in section [X-:0-Core] of /opt/kde3/share/config/kdm/kdmrc Oct 29 09:27:54 ns2 kdm_config[20494]: Multiple occurrences of key 'NoPassEnable' in section [X-:0-Core] of /opt/kde3/share/config/kdm/kdmrc Oct 29 09:27:55 ns2 kdm[20528]: X server "/usr/X11R6/bin/X" cannot be executed Oct 29 09:27:55 ns2 kdm[20493]: X server for display :0 can't be started, session disabled -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.