Do you think the xconfig line is causing it to pick bluecurve? We're passing the --defaultdesktop gnome option on it. -- Todd Blake Systems/Network Administrator Physics & Astronomy Department Johns Hopkins University Bloomberg 439 (410)516-4332 On Fri, 8 Apr 2005, Troy Dawson wrote: > Date: Fri, 08 Apr 2005 10:26:25 -0500 > From: Troy Dawson <[log in to unmask]> > To: Todd Blake <[log in to unmask]> > Cc: [log in to unmask] > Subject: Re: background.png problem with bluecurve theme and gdm after > kickstart? > > Well, it's slightly odd, but not really. > You see what is usually in the Bluecurve is really Fedora's gdm theme. > RedHat actually has a seperate little tarball and they install their gdm > theme as RHEL, and then make a link called 'Default' that points to RHEL. > We just took the same concept and put in SL and Scientific themes. (I > wrote SL, starting with William Somsky's logo. William wrote the other > one. We haven't decided which is best yet, and both will probrubly be > left in) > But since I didn't want someone accidentally having Fedora show up on > their screen, I put the Scientific theme and put it in bluecurve. I am > not quite sure why it's picking bluecurve on your kickstart. But it > should be fixed in the next release, which hopefully should be a > 'criticize now cuz this is what you'll get' release. > > Troy > > Todd Blake wrote: > > Sorry, I typoed the path, I had to transcribe it since it was a graphical > > dialogue and nothing I could cipy and paste. I find it odd that this is > > the first anyone has mentioned it, I'd think someone would've come across > > it and said something first. Oh well, thanks alot for the prompt > > response! > > > > On Fri, 8 Apr 2005, Troy Dawson wrote: > > > > > >>Date: Fri, 08 Apr 2005 09:50:34 -0500 > >>From: Troy Dawson <[log in to unmask]> > >>To: Todd Blake <[log in to unmask]> > >>Cc: [log in to unmask] > >>Subject: Re: background.png problem with bluecurve theme and gdm after > >> kickstart? > >> > >>Hi Todd, > >>Sure enough, that file isn't there, and it's supposed to be. (Although > >>it's /usr/share/gdm/themes/Bluecurve/background.png) I happen to be > >>editing the rpm right now, so I'll get it fixed. Looks like we missed a > >>tweek in the makefile. > >> > >>Troy > >> > >>Todd Blake wrote: > >> > >>>We're currently using kickstart to install our fleet of linux machines > >>>and I'm setting up a kickstart install for future deployment. I got it > >>>all working perfectly. It installs, the post sections runs, and I have > >>>a functioning SL4 RC2 machine, except for one minot problem. After > >>>booting up, a gtk error dialogue pops up and says "There was an error > >>>loading the theme Bluecurve. Failed to open file > >>>'/usr/share/gdm/themes/background.png': No such file or directory". An > >>>ok button is there and I can click it but the dialogue just pops up > >>>repeatedly. As a temporary workaround, I just copied the background > >>>from another theme into the bluecurve theme directory and all is well, > >>>but obviously I shouldn't have to hack in another png file to get it to > >>>work. > >>> > >>>It may be worth noting that I've been working with SL4 since the alpha > >>>release and this problem wasn't present in the initial alpha release. > >>>It first happened with RC1, and is still present in RC2. > >>> > >>>As far as troubleshooting goes I've scoured a zillion rpms looking for > >>>the specific background.png file, thinking maybe it wasn't installed, > >>>and can't find what rpm it should be in to be installed. I've pasted > >>>our kickstart file below, and X'd out various items like hostnames and > >>>what not. Anyone have any ideas? > >>> > >>> > >>> > >>> > >>># Kickstart file automatically generated by anaconda. > >>> > >>>install > >>>text > >>>nfs --server=XXXXXXXXXXXXX --dir=/export/src-a/kickstart/sl-4.0_rc2/i386 > >>>lang en_US.UTF-8 > >>>langsupport --default=en_US.UTF-8 en_US.UTF-8 > >>>keyboard us > >>>xconfig --depth 24 --startxonboot --defaultdesktop gnome > >>>network --device eth0 --bootproto dhcp > >>>rootpw --iscrypted XXXXXXXXXXXXXXXXXXXXXXXX > >>>firewall --disabled > >>>selinux --disabled > >>>authconfig --enableshadow --enablenis --nisdomain XXXXXXXX --nisserver > >>>XXXXXXXXXXXXXXXXX > >>>timezone America/New_York > >>>bootloader --location=mbr --append="rhgb quiet" > >>>clearpart --linux > >>>part /boot --fstype "ext3" --size 50 > >>>part / --fstype "ext3" --size 6000 > >>>part swap --size=2000 > >>>part /export/data1 --fstype "ext3" --size=200 --grow > >>>reboot > >>># The same packages that were in the rh9 install > >>>%packages > >>>@ kde-software-development > >>>@ office > >>>@ kde-desktop > >>>@ x-software-development > >>>@ legacy-software-development > >>>@ system-tools > >>>@ sound-and-video > >>>@ network-server > >>>@ editors > >>>@ authoring-and-publishing > >>>@ base-x > >>>@ printing > >>>@ gnome-desktop > >>>@ gnome-software-development > >>>@ graphics > >>>@ mysql > >>>@ development-tools > >>>@ engineering-and-scientific > >>>@ games > >>>@ text-internet > >>>@ graphical-internet > >>>grub > >>>kernel-smp > >>>kernel-smp-devel > >>>e2fsprogs > >>>tftp > >>>vim-X11 > >>>transfig > >>>xpdf > >>>xfig > >>>amanda-client > >>>finger > >>>finger-server > >>>xcdroast > >>># This is fairly all self documenting > >>>%post > >>>mkdir /mnt/ks > >>>mount -o ro,nolock XXX.XXX.XXX.XXX:/export/src-a/kickstart/sl-4.1alpha > >>>/mnt/ks > >>>exec > /root/ks-post.log 2>&1 > >>>echo adding root .shosts entries > >>>echo eta.pha.jhu.edu root > /root/.shosts > >>>echo rio-grande.pha.jhu.edu root >> /root/.shosts > >>>chmod 0600 /root/.shosts > >>>echo making /usr/site and /usr/local links > >>>mv /usr/local /usr/local.local > >>>ln -s /sa4/site-i386-linux /usr/site > >>>ln -s /sa4/local-i386-linux /usr/local > >>>echo adding hosts to /etc/hosts > >>>echo XXX.XXX.XXX.XXX XXXXXXXXXXXXXXXXXX XX XXX >> /etc/hosts > >>>echo XXX.XXX.XXX.XXX XXXXXXXXXXXXXXXXXX XX XXX >> /etc/hosts > >>>echo XXX.XXX.XXX.XXX XXXXXXXXXXXXXXXXXX XX XXX >> /etc/hosts > >>>echo installing miscellaneous/updated rpms... > >>>cd /mnt/ks/updates > >>># Hrm, pondering some sorta automated rpm repository here so freshly > >>>installed machines > >>># are up to date > >>>rpm -Uvh *.rpm > >>>mkdir /etc/bak > >>>cd /mnt/ks/os-config-files ; \ > >>> cp nsswitch.conf resolv.conf auto.master DIR_COLORS passwd shosts.equiv \ > >>> auto_direct auto_home auto_master auto.misc mime.types mailcap shadow \ > >>> hosts.allow phacomment motd syslog.conf /etc > >>> cp sysconfig/sendmail /etc/sysconfig > >>> cp sysconfig/autofs /etc/sysconfig > >>>#cp cups/printers.conf /etc/cups/printers.conf > >>> cp ssh/* /etc/ssh > >>> cp init.d/* /etc/init.d > >>> cp X11/fs/config /etc/X11/fs > >>> cp X11/gdm/gdm.conf /etc/X11/gdm > >>> cp xinetd.d/* /etc/xinetd.d > >>> cp pam.d/* /etc/pam.d > >>> cp ld.so.conf.d/* /etc/ld.so.conf.d > >>> cp cshrc /root/.cshrc > >>> cp tcshrc /root/.tcshrc > >>> cp security/console.apps/* /etc/security/console.apps > >>> cp mail/* /etc/mail > >>># This strips the .XXX.XXX.XXX from the hostname in > >>># /etc/sysconfig/network. Automagically saves a backup > >>># in /etc/sysconfig/network.orig > >>># The -e executes the perl code, the -i backs up the file > >>># to the file.orig, and the -p wraps a while loop and a print > >>># statement around the code > >>>/usr/bin/perl -pi.orig -e 's/HOSTNAME=(.*)\.XXX\.XXX\.XXX/HOSTNAME=$1/g' > >>>/etc/sysconfig/network > >>>ldconfig > >>>############################################################# > >>>echo removing some profile.d and cron scripts > >>>mkdir /etc/cron-removed > >>>mv /etc/cron.daily/00-logwatch /etc/cron-removed > >>>mkdir /etc/profile.d/removed > >>>mv /etc/profile.d/vim.csh /etc/profile.d/removed > >>>mv /etc/profile.d/vim.sh /etc/profile.d/removed > >>>mv /etc/profile.d/colorls.csh /etc/profile.d/removed > >>>mv /etc/profile.d/colorls.sh /etc/profile.d/removed > >>>/mnt/ks/finish-scripts/linux-direct.sh > >>>/mnt/ks/finish-scripts/fixmail.sh > >>>/mnt/ks/finish-scripts/configure-iraf.sh > >>>echo removing miscellaneous rpms... > >>>rpm -e --nodeps `rpm -qa |grep mozilla` > >>>rpm -e --nodeps `rpm -qa |grep tetex` > >>>rpm -e --nodeps `rpm -qa |grep firefox` > >>>rpm -e --nodeps `rpm -qa |grep thunderbird` > >>>rpm -e --nodeps `rpm -qa |grep samba-client` > >>>rpm -e --nodeps `rpm -qa |grep samba-common` > >>>/bin/rm -rf /etc/samba > >>>echo configuring ntp > >>>echo XXX-XXXXXX.XXX.XXX > /etc/ntp/step-tickers > >>>echo server XXX-XXXXXX.XXX.XXX.XXX > /etc/ntp.conf > >>>/sbin/chkconfig --level 345 ntpd on > >>>/sbin/chkconfig --level 2345 lisa on > >>>/sbin/chkconfig --levels 2345 yum off > >>>rm /etc/rc3.d/K20nfs /etc/rc5.d/K20nfs > >>>ln -s /etc/init.d/nfs /etc/rc5.d/S20nfs > >>>ln -s /etc/init.d/nfs /etc/rc3.d/S20nfs > >>>/sbin/chkconfig --level 345 nfsd on > >>>rpm --import /usr/share/rhn/RPM-GPG-KEY > >>># This is because for *some* reason the bluecurve default background > >>># isn't getting installed. This was needed when we moved up to > >>># SL 4.0, RC1, and is still apparently needed in RC2 > >>>/bin/cp /usr/share/gdm/themes/Default/background.png > >>>/usr/share/gdm/themes/Bluecurve > >>>echo "get Kickstart_End /tmp/Kickstart_End" | /usr/bin/tftp XXX.XXX.XXX > >> > >> > >>-- > >>__________________________________________________ > >>Troy Dawson [log in to unmask] (630)840-6468 > >>Fermilab ComputingDivision/CSS CSI Group > >>__________________________________________________ > >> > > > -- > __________________________________________________ > Troy Dawson [log in to unmask] (630)840-6468 > Fermilab ComputingDivision/CSS CSI Group > __________________________________________________ >