<86>Apr 26 04:22:42 userdel[23560]: delete user `rooter' <86>Apr 26 04:22:42 userdel[23560]: remove group `rooter' <86>Apr 26 04:22:42 groupadd[23561]: new group: name=rooter, gid=501 <86>Apr 26 04:22:42 useradd[23562]: new user: name=rooter, uid=501, gid=501, home=/root, shell=/bin/bash <86>Apr 26 04:22:42 userdel[23564]: delete user `builder' <86>Apr 26 04:22:42 userdel[23564]: remove group `builder' <86>Apr 26 04:22:42 groupadd[23565]: new group: name=builder, gid=502 <86>Apr 26 04:22:42 useradd[23566]: new user: name=builder, uid=502, gid=502, home=/usr/src, shell=/bin/bash <13>Apr 26 04:22:45 rpmi: ca-certificates-2007.02.06-alt1 installed <13>Apr 26 04:22:45 rpmi: libssl6-0.9.8d-alt4 installed <13>Apr 26 04:22:45 rpmi: libgdbm-1.8.3-alt4 installed <13>Apr 26 04:22:45 rpmi: libncursesw-5.6-alt4 installed <13>Apr 26 04:22:45 rpmi: python-modules-curses-2.5.2-alt0.M41.2 installed <13>Apr 26 04:22:45 rpmi: libexpat-2.0.1-alt0.1 installed <13>Apr 26 04:22:45 rpmi: libIDL-0.8.11-alt0.M41.1 installed <13>Apr 26 04:22:45 rpmi: libORBit2-2.14.12-alt1 installed <13>Apr 26 04:22:45 rpmi: xml-common-0.6.3-alt11 installed <13>Apr 26 04:22:45 rpmi: libxml2-1:2.7.2-alt1.M41.1 installed <13>Apr 26 04:22:45 rpmi: libGConf-2.22.0-alt1 installed <13>Apr 26 04:22:46 rpmi: ORBit2-2.14.12-alt1 installed <13>Apr 26 04:22:46 rpmi: libX11-locales-3:1.1.4-alt5.M41.1 installed <13>Apr 26 04:22:46 rpmi: libXau-1.0.3-alt1 installed <13>Apr 26 04:22:46 rpmi: libXdmcp-1.0.2-alt1.0 installed <13>Apr 26 04:22:46 rpmi: libxcb-1.1-alt4 installed <13>Apr 26 04:22:46 rpmi: libX11-3:1.1.4-alt5.M41.1 installed <13>Apr 26 04:22:46 rpmi: libXrender-0.9.4-alt1 installed <13>Apr 26 04:22:46 rpmi: libfreetype-2.3.6-alt0.M41.1 installed <13>Apr 26 04:22:46 rpmi: fontconfig-2.6.0-alt0.M41.1 installed Updating fonts cache: <29>Apr 26 04:22:48 fontconfig: Updating fonts cache: succeeded [ DONE ] <13>Apr 26 04:22:48 rpmi: libXft-2.1.13-alt0.M41.1 installed <13>Apr 26 04:22:48 rpmi: libXdamage-1.1.1-alt1 installed <13>Apr 26 04:22:48 rpmi: libXext-1.0.4-alt1 installed <13>Apr 26 04:22:48 rpmi: libXfixes-4.0.3-alt1 installed <13>Apr 26 04:22:48 rpmi: libXxf86vm-1.0.2-alt0.M41.1 installed <13>Apr 26 04:22:48 rpmi: libdrm-2.4.0-alt2 installed <13>Apr 26 04:22:48 rpmi: libGL-3:7.2-alt13 installed <13>Apr 26 04:22:48 rpmi: libglitz-1:0.5.7-alt1 installed <13>Apr 26 04:22:48 rpmi: libpixman-1:0.10.0-alt3 installed <13>Apr 26 04:22:48 rpmi: libpng12-1.2.27-alt1 installed <13>Apr 26 04:22:48 rpmi: libcairo-1:1.6.4-alt2.M41.1 installed <13>Apr 26 04:22:49 rpmi: libpango-1.20.5-alt0.M41.1 installed <13>Apr 26 04:22:49 rpmi: libatk-1.22.0-alt1 installed <13>Apr 26 04:22:49 rpmi: shared-mime-info-0.30-alt0.M41.1 installed <86>Apr 26 04:22:49 groupadd[23983]: new group: name=crontab, gid=36 <13>Apr 26 04:22:49 rpmi: crontab-control-1.1-alt1 installed <13>Apr 26 04:22:49 rpmi: setproctitle-0.3.1-alt1 installed <13>Apr 26 04:22:49 rpmi: vixie-cron-4.1.20060426-alt4 installed <13>Apr 26 04:22:50 rpmi: crontabs-1.8-alt1 installed <13>Apr 26 04:22:50 rpmi: libgpg-error-1.5-alt1 installed <13>Apr 26 04:22:50 rpmi: libgcrypt-1.4.1-alt1 installed <13>Apr 26 04:22:50 rpmi: libtasn1-1.1-alt1 installed <13>Apr 26 04:22:50 rpmi: libgnutls-2.0.4-alt2 installed <13>Apr 26 04:22:50 rpmi: libjpeg-1:6b-alt8 installed <13>Apr 26 04:22:50 rpmi: libtiff-3.8.2-alt2 installed <13>Apr 26 04:22:50 rpmi: libcups-1.3.7-alt2 installed <13>Apr 26 04:22:50 rpmi: libXcomposite-0.4.0-alt1 installed <13>Apr 26 04:22:50 rpmi: libXcursor-1.1.9-alt1 installed <13>Apr 26 04:22:50 rpmi: libXi-1.1.3-alt2.M41.1 installed <13>Apr 26 04:22:50 rpmi: libXinerama-1.0.3-alt1 installed <13>Apr 26 04:22:50 rpmi: libXrandr-1.2.3-alt0.M41.1 installed <13>Apr 26 04:22:50 rpmi: libxslt-1.1.24-alt0.M41.1 installed <13>Apr 26 04:22:50 rpmi: xsltproc-1.1.24-alt0.M41.1 installed <13>Apr 26 04:22:50 rpmi: perl-DBM-1:5.8.8-alt19.M41.1 installed <13>Apr 26 04:22:50 rpmi: perl-Compress-Zlib-1.42-alt3 installed <13>Apr 26 04:22:50 rpmi: perl-HTML-Tagset-3.20-alt1 installed <13>Apr 26 04:22:50 rpmi: perl-libnet-1:1.22-alt1 installed <13>Apr 26 04:22:50 rpmi: perl-URI-1.36-alt1 installed <13>Apr 26 04:22:50 rpmi: perl-Crypt-SSLeay-0.57-alt1 installed <13>Apr 26 04:22:50 rpmi: rpm-build-gnome-0.9-alt1 installed <13>Apr 26 04:22:50 rpmi: rpm-build-licenses-1.0-alt2 installed <13>Apr 26 04:22:50 rpmi: python-modules-email-2.5.2-alt0.M41.2 installed <13>Apr 26 04:22:51 rpmi: libgtk+2-common-2.12.11-alt0.M41.2 installed <13>Apr 26 04:22:52 rpmi: libgtk+2-2.12.11-alt0.M41.2 installed <13>Apr 26 04:22:52 rpmi: GConf-2.22.0-alt1 installed <13>Apr 26 04:22:52 rpmi: perl-HTML-Parser-3.56-alt2 installed <13>Apr 26 04:22:52 rpmi: perl-libwww-5.812-alt1 installed <13>Apr 26 04:22:52 rpmi: perl-XML-Parser-2.36-alt1 installed <13>Apr 26 04:22:52 rpmi: intltool-0.40.3-alt0.M41.1 installed <13>Apr 26 04:22:52 rpmi: python-modules-compiler-2.5.2-alt0.M41.2 installed <13>Apr 26 04:22:52 rpmi: python-modules-encodings-2.5.2-alt0.M41.2 installed <13>Apr 26 04:22:53 rpmi: python-modules-2.5.2-alt0.M41.2 installed <13>Apr 26 04:22:53 rpmi: python-modules-xml-2.5.2-alt0.M41.2 installed <13>Apr 26 04:22:53 rpmi: python-modules-hotshot-2.5.2-alt0.M41.2 installed Installing gnome-specimen-0.4-alt1.1.qa1.src.rpm Building target platforms: ppc Building for target ppc Executing(%prep): /bin/sh -e /usr/src/tmp/rpm-tmp.51411 + umask 022 + /bin/mkdir -p /usr/src/RPM/BUILD + cd /usr/src/RPM/BUILD + cd /usr/src/RPM/BUILD + rm -rf gnome-specimen-0.4 + echo 'Source #0 (gnome-specimen-0.4.tar.gz):' Source #0 (gnome-specimen-0.4.tar.gz): + /bin/gzip -dc /usr/src/RPM/SOURCES/gnome-specimen-0.4.tar.gz + /bin/tar -xf - + cd gnome-specimen-0.4 + /bin/chmod -c -Rf u+rwX,go-w . + exit 0 Executing(%build): /bin/sh -e /usr/src/tmp/rpm-tmp.51411 + umask 022 + /bin/mkdir -p /usr/src/RPM/BUILD + cd /usr/src/RPM/BUILD + cd gnome-specimen-0.4 + CFLAGS='-pipe -Wall -O2 -fsigned-char' + export CFLAGS + CXXFLAGS='-pipe -Wall -O2 -fsigned-char' + export CXXFLAGS + FFLAGS='-pipe -Wall -O2 -fsigned-char' + export FFLAGS + export lt_cv_deplibs_check_method=pass_all + lt_cv_deplibs_check_method=pass_all + '[' -f configure.ac -o -f configure.in ']' + libtoolize --copy --force Remember to add `AC_PROG_LIBTOOL' to `configure.ac'. You should update your `aclocal.m4' by running aclocal. + ./configure --build=ppc-alt-linux --host=ppc-alt-linux --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc --datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib --libexecdir=/usr/lib --localstatedir=/var/lib --sharedstatedir=/usr/com --mandir=/usr/share/man --infodir=/usr/share/info --disable-dependency-tracking --without-included-gettext --disable-schemas-install checking for a BSD-compatible install... /bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether to enable maintainer-specific portions of Makefiles... no checking for python... /usr/bin/python checking for python version... 2.5 checking for python platform... linux2 checking for python script directory... ${prefix}/lib/python2.5/site-packages checking for python extension module directory... ${exec_prefix}/lib/python2.5/site-packages checking for ppc-alt-linux-pkg-config... no checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for gconf... yes Using config source xml:readwrite:/var/cache/gconf/gconf.xml.defaults for schema installation Using $(sysconfdir)/gconf/schemas as install directory for schema files checking for gconftool-2... /usr/bin/gconftool-2 checking for style of include used by make... GNU checking for ppc-alt-linux-gcc... ppc-alt-linux-gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether ppc-alt-linux-gcc accepts -g... yes checking for ppc-alt-linux-gcc option to accept ISO C89... none needed checking dependency style of ppc-alt-linux-gcc... none checking how to run the C preprocessor... ppc-alt-linux-gcc -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking build system type... powerpc-alt-linux-gnu checking host system type... powerpc-alt-linux-gnu checking locale.h usability... yes checking locale.h presence... yes checking for locale.h... yes checking for LC_MESSAGES... yes checking libintl.h usability... yes checking libintl.h presence... yes checking for libintl.h... yes checking for ngettext in libc... yes checking for dgettext in libc... yes checking for bind_textdomain_codeset... yes checking for msgfmt... /usr/bin/msgfmt checking for dcgettext... yes checking if msgfmt accepts -c... yes checking for gmsgfmt... /usr/bin/msgfmt checking for xgettext... /usr/bin/xgettext checking for intltool >= 0.35.0... 0.37.0 found checking for xgettext... (cached) /usr/bin/xgettext checking for msgmerge... /usr/bin/msgmerge checking for msgfmt... (cached) /usr/bin/msgfmt checking for perl... /usr/bin/perl checking for XML::Parser... ok configure: creating ./config.status config.status: creating data/gnome-specimen.desktop.in config.status: creating data/Makefile config.status: creating data/icons/Makefile config.status: creating Makefile config.status: creating po/Makefile.in config.status: creating specimen/Makefile config.status: executing depfiles commands config.status: executing default-1 commands config.status: executing intltool commands config.status: executing po/stamp-it commands + make make: Entering directory `/usr/src/RPM/BUILD/gnome-specimen-0.4' Making all in data make[1]: Entering directory `/usr/src/RPM/BUILD/gnome-specimen-0.4/data' Making all in icons make[2]: Entering directory `/usr/src/RPM/BUILD/gnome-specimen-0.4/data/icons' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/usr/src/RPM/BUILD/gnome-specimen-0.4/data/icons' make[2]: Entering directory `/usr/src/RPM/BUILD/gnome-specimen-0.4/data' LC_ALL=C ../intltool-merge -d -u -c ../po/.intltool-merge-cache ../po gnome-specimen.desktop.in gnome-specimen.desktop Generating and caching the translation database Merging translations into gnome-specimen.desktop. LC_ALL=C ../intltool-merge -s -u -c ../po/.intltool-merge-cache ../po gnome-specimen.schemas.in gnome-specimen.schemas Found cached translation database Merging translations into gnome-specimen.schemas. make[2]: Leaving directory `/usr/src/RPM/BUILD/gnome-specimen-0.4/data' make[1]: Leaving directory `/usr/src/RPM/BUILD/gnome-specimen-0.4/data' Making all in po make[1]: Entering directory `/usr/src/RPM/BUILD/gnome-specimen-0.4/po' file=`echo ar | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file ar.po file=`echo ca | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file ca.po file=`echo cs | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file cs.po file=`echo de | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file de.po file=`echo el | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file el.po file=`echo en_GB | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file en_GB.po file=`echo es | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file es.po file=`echo fi | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file fi.po file=`echo fr | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file fr.po file=`echo it | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file it.po file=`echo ja | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file ja.po file=`echo nb | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file nb.po file=`echo nl | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file nl.po file=`echo pl | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file pl.po file=`echo pt | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file pt.po file=`echo pt_BR | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file pt_BR.po file=`echo ru | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file ru.po file=`echo sv | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file sv.po file=`echo vi | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file vi.po file=`echo zh_CN | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file zh_CN.po make[1]: Leaving directory `/usr/src/RPM/BUILD/gnome-specimen-0.4/po' Making all in specimen make[1]: Entering directory `/usr/src/RPM/BUILD/gnome-specimen-0.4/specimen' sed \ -e s!\@LOCALEDIR\@!/usr/share/locale! \ -e s!\@DATADIR\@!/usr/share! \ -e s!\@PKGDATADIR\@!/usr/share/gnome-specimen! \ -e s!\@GLADEDIR\@!/usr/share/gnome-specimen/glade! \ -e s!\@PACKAGE_NAME\@!gnome-specimen! \ -e s!\@PACKAGE_VERSION\@!0.4! \ < config.py.in \ > config.py make[1]: Leaving directory `/usr/src/RPM/BUILD/gnome-specimen-0.4/specimen' make[1]: Entering directory `/usr/src/RPM/BUILD/gnome-specimen-0.4' sed \ -e s!\@pyexecdir\@!/usr/lib/python2.5/site-packages! \ -e s!\@PYTHON\@!/usr/bin/python! \ < gnome-specimen.in \ > gnome-specimen chmod a+x gnome-specimen make[1]: Leaving directory `/usr/src/RPM/BUILD/gnome-specimen-0.4' make: Leaving directory `/usr/src/RPM/BUILD/gnome-specimen-0.4' + exit 0 Executing(%install): /bin/sh -e /usr/src/tmp/rpm-tmp.15208 + umask 022 + /bin/mkdir -p /usr/src/RPM/BUILD + cd /usr/src/RPM/BUILD + /bin/chmod -Rf u+rwX -- /usr/src/tmp/gnome-specimen-buildroot + : + /bin/rm -rf -- /usr/src/tmp/gnome-specimen-buildroot + cd gnome-specimen-0.4 + /usr/bin/make 'INSTALL=/bin/install -p' prefix=/usr/src/tmp/gnome-specimen-buildroot/usr exec_prefix=/usr/src/tmp/gnome-specimen-buildroot/usr bindir=/usr/src/tmp/gnome-specimen-buildroot/usr/bin sbindir=/usr/src/tmp/gnome-specimen-buildroot/usr/sbin sysconfdir=/usr/src/tmp/gnome-specimen-buildroot/etc datadir=/usr/src/tmp/gnome-specimen-buildroot/usr/share includedir=/usr/src/tmp/gnome-specimen-buildroot/usr/include libdir=/usr/src/tmp/gnome-specimen-buildroot/usr/lib libexecdir=/usr/src/tmp/gnome-specimen-buildroot/usr/lib localstatedir=/usr/src/tmp/gnome-specimen-buildroot/var/lib sharedstatedir=/usr/src/tmp/gnome-specimen-buildroot/usr/com mandir=/usr/src/tmp/gnome-specimen-buildroot/usr/share/man infodir=/usr/src/tmp/gnome-specimen-buildroot/usr/share/info install make: Entering directory `/usr/src/RPM/BUILD/gnome-specimen-0.4' Making install in data make[1]: Entering directory `/usr/src/RPM/BUILD/gnome-specimen-0.4/data' Making install in icons make[2]: Entering directory `/usr/src/RPM/BUILD/gnome-specimen-0.4/data/icons' make[3]: Entering directory `/usr/src/RPM/BUILD/gnome-specimen-0.4/data/icons' make[3]: Nothing to be done for `install-exec-am'. Installing application icons... /bin/mkdir -p /usr/src/tmp/gnome-specimen-buildroot/usr/share/icons/hicolor/scalable/apps; /bin/install -p -m 644 ./gnome-specimen-scalable.svg /usr/src/tmp/gnome-specimen-buildroot/usr/share/icons/hicolor/scalable/apps/gnome-specimen.svg; for SIZE in 16 22 24 32 48; do \ /bin/mkdir -p /usr/src/tmp/gnome-specimen-buildroot/usr/share/icons/hicolor/${SIZE}x${SIZE}/apps; \ /bin/install -p -m 644 ./gnome-specimen-$SIZE.png /usr/src/tmp/gnome-specimen-buildroot/usr/share/icons/hicolor/${SIZE}x${SIZE}/apps/gnome-specimen.png; \ done Updating GTK icon cache. gtk-update-icon-cache: Cache file created successfully. make[3]: Leaving directory `/usr/src/RPM/BUILD/gnome-specimen-0.4/data/icons' make[2]: Leaving directory `/usr/src/RPM/BUILD/gnome-specimen-0.4/data/icons' make[2]: Entering directory `/usr/src/RPM/BUILD/gnome-specimen-0.4/data' make[3]: Entering directory `/usr/src/RPM/BUILD/gnome-specimen-0.4/data' make[3]: Nothing to be done for `install-exec-am'. test -z "/usr/src/tmp/gnome-specimen-buildroot/usr/share/gnome-specimen" || /bin/mkdir -p "/usr/src/tmp/gnome-specimen-buildroot/usr/share/gnome-specimen" /bin/install -p -m 644 'gnome-specimen-about.png' '/usr/src/tmp/gnome-specimen-buildroot/usr/share/gnome-specimen/gnome-specimen-about.png' if test -z "" ; then \ for p in gnome-specimen.schemas ; do \ GCONF_CONFIG_SOURCE=xml:readwrite:/var/cache/gconf/gconf.xml.defaults \ /usr/bin/gconftool-2 \ --makefile-install-rule \ ../data/$p; \ done \ fi Resolved address "xml:readwrite:/var/cache/gconf/gconf.xml.defaults" to a read-only configuration source at position 0 None of the resolved addresses are writable; saving configuration settings will not be possible Attached schema `/schemas/apps/gnome-specimen/preview_text' to key `/apps/gnome-specimen/preview_text' WARNING: failed to install schema `/schemas/apps/gnome-specimen/preview_text', locale `de': Unable to store a value at key '/schemas/apps/gnome-specimen/preview_text', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-specimen/preview_text', locale `fi': Unable to store a value at key '/schemas/apps/gnome-specimen/preview_text', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-specimen/preview_text', locale `C': Unable to store a value at key '/schemas/apps/gnome-specimen/preview_text', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-specimen/preview_text', locale `es': Unable to store a value at key '/schemas/apps/gnome-specimen/preview_text', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-specimen/preview_text', locale `vi': Unable to store a value at key '/schemas/apps/gnome-specimen/preview_text', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-specimen/preview_text', locale `pt': Unable to store a value at key '/schemas/apps/gnome-specimen/preview_text', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-specimen/preview_text', locale `zh_CN': Unable to store a value at key '/schemas/apps/gnome-specimen/preview_text', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-specimen/preview_text', locale `cs': Unable to store a value at key '/schemas/apps/gnome-specimen/preview_text', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-specimen/preview_text', locale `el': Unable to store a value at key '/schemas/apps/gnome-specimen/preview_text', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-specimen/preview_text', locale `it': Unable to store a value at key '/schemas/apps/gnome-specimen/preview_text', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-specimen/preview_text', locale `pl': Unable to store a value at key '/schemas/apps/gnome-specimen/preview_text', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-specimen/preview_text', locale `en_GB': Unable to store a value at key '/schemas/apps/gnome-specimen/preview_text', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-specimen/preview_text', locale `ja': Unable to store a value at key '/schemas/apps/gnome-specimen/preview_text', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-specimen/preview_text', locale `pt_BR': Unable to store a value at key '/schemas/apps/gnome-specimen/preview_text', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-specimen/preview_text', locale `ar': Unable to store a value at key '/schemas/apps/gnome-specimen/preview_text', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-specimen/preview_text', locale `ca': Unable to store a value at key '/schemas/apps/gnome-specimen/preview_text', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-specimen/preview_text', locale `fr': Unable to store a value at key '/schemas/apps/gnome-specimen/preview_text', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-specimen/preview_text', locale `nl': Unable to store a value at key '/schemas/apps/gnome-specimen/preview_text', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-specimen/preview_text', locale `sv': Unable to store a value at key '/schemas/apps/gnome-specimen/preview_text', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-specimen/preview_text', locale `nb': Unable to store a value at key '/schemas/apps/gnome-specimen/preview_text', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-specimen/preview_text', locale `ru': Unable to store a value at key '/schemas/apps/gnome-specimen/preview_text', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/gnome-specimen/preview_size' to key `/apps/gnome-specimen/preview_size' WARNING: failed to install schema `/schemas/apps/gnome-specimen/preview_size', locale `de': Unable to store a value at key '/schemas/apps/gnome-specimen/preview_size', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-specimen/preview_size', locale `fi': Unable to store a value at key '/schemas/apps/gnome-specimen/preview_size', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-specimen/preview_size', locale `C': Unable to store a value at key '/schemas/apps/gnome-specimen/preview_size', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-specimen/preview_size', locale `es': Unable to store a value at key '/schemas/apps/gnome-specimen/preview_size', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-specimen/preview_size', locale `vi': Unable to store a value at key '/schemas/apps/gnome-specimen/preview_size', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-specimen/preview_size', locale `cs': Unable to store a value at key '/schemas/apps/gnome-specimen/preview_size', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-specimen/preview_size', locale `el': Unable to store a value at key '/schemas/apps/gnome-specimen/preview_size', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-specimen/preview_size', locale `pl': Unable to store a value at key '/schemas/apps/gnome-specimen/preview_size', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-specimen/preview_size', locale `en_GB': Unable to store a value at key '/schemas/apps/gnome-specimen/preview_size', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-specimen/preview_size', locale `ja': Unable to store a value at key '/schemas/apps/gnome-specimen/preview_size', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-specimen/preview_size', locale `pt_BR': Unable to store a value at key '/schemas/apps/gnome-specimen/preview_size', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-specimen/preview_size', locale `ar': Unable to store a value at key '/schemas/apps/gnome-specimen/preview_size', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-specimen/preview_size', locale `fr': Unable to store a value at key '/schemas/apps/gnome-specimen/preview_size', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-specimen/preview_size', locale `nl': Unable to store a value at key '/schemas/apps/gnome-specimen/preview_size', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-specimen/preview_size', locale `nb': Unable to store a value at key '/schemas/apps/gnome-specimen/preview_size', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-specimen/preview_size', locale `ru': Unable to store a value at key '/schemas/apps/gnome-specimen/preview_size', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf test -z "/usr/src/tmp/gnome-specimen-buildroot/usr/share/applications" || /bin/mkdir -p "/usr/src/tmp/gnome-specimen-buildroot/usr/share/applications" /bin/install -p -m 644 'gnome-specimen.desktop' '/usr/src/tmp/gnome-specimen-buildroot/usr/share/applications/gnome-specimen.desktop' test -z "/usr/src/tmp/gnome-specimen-buildroot/usr/share/gnome-specimen/glade" || /bin/mkdir -p "/usr/src/tmp/gnome-specimen-buildroot/usr/share/gnome-specimen/glade" /bin/install -p -m 644 'gnome-specimen.glade' '/usr/src/tmp/gnome-specimen-buildroot/usr/share/gnome-specimen/glade/gnome-specimen.glade' test -z "/usr/src/tmp/gnome-specimen-buildroot/etc/gconf/schemas" || /bin/mkdir -p "/usr/src/tmp/gnome-specimen-buildroot/etc/gconf/schemas" /bin/install -p -m 644 'gnome-specimen.schemas' '/usr/src/tmp/gnome-specimen-buildroot/etc/gconf/schemas/gnome-specimen.schemas' make[3]: Leaving directory `/usr/src/RPM/BUILD/gnome-specimen-0.4/data' make[2]: Leaving directory `/usr/src/RPM/BUILD/gnome-specimen-0.4/data' make[1]: Leaving directory `/usr/src/RPM/BUILD/gnome-specimen-0.4/data' Making install in po make[1]: Entering directory `/usr/src/RPM/BUILD/gnome-specimen-0.4/po' /bin/sh /usr/src/RPM/BUILD/gnome-specimen-0.4/install-sh -d /usr/src/tmp/gnome-specimen-buildroot/usr/share/locale linguas="ar ca cs de el en_GB es fi fr it ja nb nl pl pt pt_BR ru sv vi zh_CN "; \ for lang in $linguas; do \ dir=/usr/src/tmp/gnome-specimen-buildroot/usr/share/locale/$lang/LC_MESSAGES; \ /bin/sh /usr/src/RPM/BUILD/gnome-specimen-0.4/install-sh -d $dir; \ if test -r $lang.gmo; then \ /bin/install -p -m 644 $lang.gmo $dir/gnome-specimen.mo; \ echo "installing $lang.gmo as $dir/gnome-specimen.mo"; \ else \ /bin/install -p -m 644 ./$lang.gmo $dir/gnome-specimen.mo; \ echo "installing ./$lang.gmo as" \ "$dir/gnome-specimen.mo"; \ fi; \ if test -r $lang.gmo.m; then \ /bin/install -p -m 644 $lang.gmo.m $dir/gnome-specimen.mo.m; \ echo "installing $lang.gmo.m as $dir/gnome-specimen.mo.m"; \ else \ if test -r ./$lang.gmo.m ; then \ /bin/install -p -m 644 ./$lang.gmo.m \ $dir/gnome-specimen.mo.m; \ echo "installing ./$lang.gmo.m as" \ "$dir/gnome-specimen.mo.m"; \ else \ true; \ fi; \ fi; \ done installing ar.gmo as /usr/src/tmp/gnome-specimen-buildroot/usr/share/locale/ar/LC_MESSAGES/gnome-specimen.mo installing ca.gmo as /usr/src/tmp/gnome-specimen-buildroot/usr/share/locale/ca/LC_MESSAGES/gnome-specimen.mo installing cs.gmo as /usr/src/tmp/gnome-specimen-buildroot/usr/share/locale/cs/LC_MESSAGES/gnome-specimen.mo installing de.gmo as /usr/src/tmp/gnome-specimen-buildroot/usr/share/locale/de/LC_MESSAGES/gnome-specimen.mo installing el.gmo as /usr/src/tmp/gnome-specimen-buildroot/usr/share/locale/el/LC_MESSAGES/gnome-specimen.mo installing en_GB.gmo as /usr/src/tmp/gnome-specimen-buildroot/usr/share/locale/en_GB/LC_MESSAGES/gnome-specimen.mo installing es.gmo as /usr/src/tmp/gnome-specimen-buildroot/usr/share/locale/es/LC_MESSAGES/gnome-specimen.mo installing fi.gmo as /usr/src/tmp/gnome-specimen-buildroot/usr/share/locale/fi/LC_MESSAGES/gnome-specimen.mo installing fr.gmo as /usr/src/tmp/gnome-specimen-buildroot/usr/share/locale/fr/LC_MESSAGES/gnome-specimen.mo installing it.gmo as /usr/src/tmp/gnome-specimen-buildroot/usr/share/locale/it/LC_MESSAGES/gnome-specimen.mo installing ja.gmo as /usr/src/tmp/gnome-specimen-buildroot/usr/share/locale/ja/LC_MESSAGES/gnome-specimen.mo installing nb.gmo as /usr/src/tmp/gnome-specimen-buildroot/usr/share/locale/nb/LC_MESSAGES/gnome-specimen.mo installing nl.gmo as /usr/src/tmp/gnome-specimen-buildroot/usr/share/locale/nl/LC_MESSAGES/gnome-specimen.mo installing pl.gmo as /usr/src/tmp/gnome-specimen-buildroot/usr/share/locale/pl/LC_MESSAGES/gnome-specimen.mo installing pt.gmo as /usr/src/tmp/gnome-specimen-buildroot/usr/share/locale/pt/LC_MESSAGES/gnome-specimen.mo installing pt_BR.gmo as /usr/src/tmp/gnome-specimen-buildroot/usr/share/locale/pt_BR/LC_MESSAGES/gnome-specimen.mo installing ru.gmo as /usr/src/tmp/gnome-specimen-buildroot/usr/share/locale/ru/LC_MESSAGES/gnome-specimen.mo installing sv.gmo as /usr/src/tmp/gnome-specimen-buildroot/usr/share/locale/sv/LC_MESSAGES/gnome-specimen.mo installing vi.gmo as /usr/src/tmp/gnome-specimen-buildroot/usr/share/locale/vi/LC_MESSAGES/gnome-specimen.mo installing zh_CN.gmo as /usr/src/tmp/gnome-specimen-buildroot/usr/share/locale/zh_CN/LC_MESSAGES/gnome-specimen.mo make[1]: Leaving directory `/usr/src/RPM/BUILD/gnome-specimen-0.4/po' Making install in specimen make[1]: Entering directory `/usr/src/RPM/BUILD/gnome-specimen-0.4/specimen' make[2]: Entering directory `/usr/src/RPM/BUILD/gnome-specimen-0.4/specimen' make[2]: Nothing to be done for `install-exec-am'. test -z "/usr/src/tmp/gnome-specimen-buildroot/usr/lib/python2.5/site-packages/specimen" || /bin/mkdir -p "/usr/src/tmp/gnome-specimen-buildroot/usr/lib/python2.5/site-packages/specimen" /bin/install -p -m 644 '__init__.py' '/usr/src/tmp/gnome-specimen-buildroot/usr/lib/python2.5/site-packages/specimen/__init__.py' /bin/install -p -m 644 'main.py' '/usr/src/tmp/gnome-specimen-buildroot/usr/lib/python2.5/site-packages/specimen/main.py' /bin/install -p -m 644 'specimenwindow.py' '/usr/src/tmp/gnome-specimen-buildroot/usr/lib/python2.5/site-packages/specimen/specimenwindow.py' Byte-compiling python modules... __init__.py main.py specimenwindow.py Byte-compiling python modules (optimized versions) ... __init__.py main.py specimenwindow.py test -z "/usr/src/tmp/gnome-specimen-buildroot/usr/lib/python2.5/site-packages/specimen" || /bin/mkdir -p "/usr/src/tmp/gnome-specimen-buildroot/usr/lib/python2.5/site-packages/specimen" /bin/install -p -m 644 'config.py' '/usr/src/tmp/gnome-specimen-buildroot/usr/lib/python2.5/site-packages/specimen/config.py' Byte-compiling python modules... config.py Byte-compiling python modules (optimized versions) ... config.py make[2]: Leaving directory `/usr/src/RPM/BUILD/gnome-specimen-0.4/specimen' make[1]: Leaving directory `/usr/src/RPM/BUILD/gnome-specimen-0.4/specimen' make[1]: Entering directory `/usr/src/RPM/BUILD/gnome-specimen-0.4' make[2]: Entering directory `/usr/src/RPM/BUILD/gnome-specimen-0.4' test -z "/usr/src/tmp/gnome-specimen-buildroot/usr/bin" || /bin/mkdir -p "/usr/src/tmp/gnome-specimen-buildroot/usr/bin" /bin/install -p 'gnome-specimen' '/usr/src/tmp/gnome-specimen-buildroot/usr/bin/gnome-specimen' make[2]: Nothing to be done for `install-data-am'. make[2]: Leaving directory `/usr/src/RPM/BUILD/gnome-specimen-0.4' make[1]: Leaving directory `/usr/src/RPM/BUILD/gnome-specimen-0.4' make: Leaving directory `/usr/src/RPM/BUILD/gnome-specimen-0.4' + /usr/lib/rpm/find-lang gnome-specimen + /usr/lib/rpm/brp-alt Cleaning files in /usr/src/tmp/gnome-specimen-buildroot (auto) Verifying and fixing files in /usr/src/tmp/gnome-specimen-buildroot (binconfig,pkgconfig,libtool) Compressing files in /usr/src/tmp/gnome-specimen-buildroot (auto) Adjusting library links in /usr/src/tmp/gnome-specimen-buildroot ./usr/lib: Verifying ELF objects in /usr/src/tmp/gnome-specimen-buildroot (arch=normal,fhs=normal,rpath=normal,stack=normal,textrel=normal,unresolved=normal) Stripping binaries in /usr/src/tmp/gnome-specimen-buildroot (executable,shared) Bytecompiling python modules in /usr/src/tmp/gnome-specimen-buildroot using /usr/bin/python unlink /usr/src/tmp/gnome-specimen-buildroot/usr/lib/python2.5/site-packages/specimen/__init__.pyc unlink /usr/src/tmp/gnome-specimen-buildroot/usr/lib/python2.5/site-packages/specimen/config.pyc unlink /usr/src/tmp/gnome-specimen-buildroot/usr/lib/python2.5/site-packages/specimen/main.pyc unlink /usr/src/tmp/gnome-specimen-buildroot/usr/lib/python2.5/site-packages/specimen/specimenwindow.pyc compile /usr/src/tmp/gnome-specimen-buildroot/usr/lib/python2.5/site-packages/specimen/__init__.py compile /usr/src/tmp/gnome-specimen-buildroot/usr/lib/python2.5/site-packages/specimen/config.py compile /usr/src/tmp/gnome-specimen-buildroot/usr/lib/python2.5/site-packages/specimen/main.py compile /usr/src/tmp/gnome-specimen-buildroot/usr/lib/python2.5/site-packages/specimen/specimenwindow.py Bytecompiling python modules with optimization in /usr/src/tmp/gnome-specimen-buildroot using /usr/bin/python -O unlink /usr/src/tmp/gnome-specimen-buildroot/usr/lib/python2.5/site-packages/specimen/__init__.pyo unlink /usr/src/tmp/gnome-specimen-buildroot/usr/lib/python2.5/site-packages/specimen/config.pyo unlink /usr/src/tmp/gnome-specimen-buildroot/usr/lib/python2.5/site-packages/specimen/main.pyo unlink /usr/src/tmp/gnome-specimen-buildroot/usr/lib/python2.5/site-packages/specimen/specimenwindow.pyo compile /usr/src/tmp/gnome-specimen-buildroot/usr/lib/python2.5/site-packages/specimen/__init__.py compile /usr/src/tmp/gnome-specimen-buildroot/usr/lib/python2.5/site-packages/specimen/config.py compile /usr/src/tmp/gnome-specimen-buildroot/usr/lib/python2.5/site-packages/specimen/main.py compile /usr/src/tmp/gnome-specimen-buildroot/usr/lib/python2.5/site-packages/specimen/specimenwindow.py Processing files: gnome-specimen-0.4-alt1.1.qa1 Finding Provides (using /usr/lib/rpm/find-provides) Executing(Provides): /bin/sh -e /usr/src/tmp/rpm-tmp.90132 + umask 022 + /bin/mkdir -p /usr/src/RPM/BUILD + cd /usr/src/RPM/BUILD + /usr/lib/rpm/find-provides find-provides: running scripts (alternatives,lib,pam,perl,pkgconfig,python,shell) + exit 0 Finding Requires(post) (using /usr/lib/rpm/find-scriptlet-requires) Executing(Requires(post)): /bin/sh -e /usr/src/tmp/rpm-tmp.19318 + umask 022 + /bin/mkdir -p /usr/src/RPM/BUILD + cd /usr/src/RPM/BUILD + /usr/lib/rpm/find-scriptlet-requires /usr/src/tmp/gnome-specimen-buildroot/.post:gnome-specimen + exit 0 Finding Requires(preun) (using /usr/lib/rpm/find-scriptlet-requires) Executing(Requires(preun)): /bin/sh -e /usr/src/tmp/rpm-tmp.40520 + umask 022 + /bin/mkdir -p /usr/src/RPM/BUILD + cd /usr/src/RPM/BUILD + /usr/lib/rpm/find-scriptlet-requires /usr/src/tmp/gnome-specimen-buildroot/.preun:gnome-specimen + exit 0 Finding Requires(postun) (using /usr/lib/rpm/find-scriptlet-requires) Executing(Requires(postun)): /bin/sh -e /usr/src/tmp/rpm-tmp.61229 + umask 022 + /bin/mkdir -p /usr/src/RPM/BUILD + cd /usr/src/RPM/BUILD + /usr/lib/rpm/find-scriptlet-requires /usr/src/tmp/gnome-specimen-buildroot/.postun:gnome-specimen + exit 0 Finding Requires (using /usr/lib/rpm/find-requires) Executing(Requires): /bin/sh -e /usr/src/tmp/rpm-tmp.2871 + umask 022 + /bin/mkdir -p /usr/src/RPM/BUILD + cd /usr/src/RPM/BUILD + /usr/lib/rpm/find-requires find-requires: running scripts (files,lib,pam,perl,pkgconfig,pkgconfiglib,python,shebang,shell,static,symlinks) /usr/lib/rpm/python.req.py: /usr/src/tmp/gnome-specimen-buildroot/usr/lib/python2.5/site-packages/specimen/main.py: line=25 IGNORE module=gettext /usr/lib/rpm/python.req.py: /usr/src/tmp/gnome-specimen-buildroot/usr/lib/python2.5/site-packages/specimen/main.py: line=31 IGNORE module=pygtk /usr/lib/rpm/python.req.py: /usr/src/tmp/gnome-specimen-buildroot/usr/lib/python2.5/site-packages/specimen/main.py: line=32 IGNORE module=gtk /usr/lib/rpm/python.req.py: /usr/src/tmp/gnome-specimen-buildroot/usr/lib/python2.5/site-packages/specimen/main.py: line=37 IGNORE module=gtk /usr/lib/rpm/python.req.py: /usr/src/tmp/gnome-specimen-buildroot/usr/lib/python2.5/site-packages/specimen/main.py: line=42 IGNORE module=gnome /usr/lib/rpm/python.req.py: /usr/src/tmp/gnome-specimen-buildroot/usr/lib/python2.5/site-packages/specimen/main.py: line=47 IGNORE module=gconf /usr/lib/rpm/python.req.py: /usr/src/tmp/gnome-specimen-buildroot/usr/lib/python2.5/site-packages/specimen/main.py: line=52 IGNORE module=specimen /usr/lib/rpm/python.req.py: /usr/src/tmp/gnome-specimen-buildroot/usr/lib/python2.5/site-packages/specimen/main.py: line=63 IGNORE module=specimenwindow + exit 0 Provides: python2.5(specimen), python2.5(specimen.config), python2.5(specimen.main), python2.5(specimen.specimenwindow) Requires(interp): /bin/sh, /bin/sh, /bin/sh Requires(rpmlib): rpmlib(PayloadFilesHavePrefix) <= 4.0-1, rpmlib(CompressedFileNames) <= 3.0.4-1 Requires(post): /bin/sh, /usr/sbin/gconf_install_schema Requires(preun): /bin/sh, /usr/sbin/gconf_uninstall_schema Requires(postun): /bin/sh Requires: /usr/bin/python, python2.5(gconf), python2.5(gettext), python2.5(gobject), python2.5(gtk), python2.5(os), python2.5(pango) Finding unpackaged files (using /usr/lib/rpm/check-files) Executing(check-files): /bin/sh -e /usr/src/tmp/rpm-tmp.71299 + umask 022 + /bin/mkdir -p /usr/src/RPM/BUILD + cd /usr/src/RPM/BUILD + /usr/lib/rpm/check-files + exit 0 Wrote: /usr/src/RPM/SRPMS/gnome-specimen-0.4-alt1.1.qa1.src.rpm Wrote: /usr/src/RPM/RPMS/ppc/gnome-specimen-0.4-alt1.1.qa1.ppc.rpm 4.90user 3.56system 0:14.17elapsed 59%CPU (0avgtext+0avgdata 0maxresident)k 0inputs+0outputs (0major+760617minor)pagefaults 0swaps