<86>Apr 26 03:28:15 userdel[13110]: delete user `rooter' <86>Apr 26 03:28:15 userdel[13110]: remove group `rooter' <86>Apr 26 03:28:15 groupadd[13111]: new group: name=rooter, gid=501 <86>Apr 26 03:28:15 useradd[13112]: new user: name=rooter, uid=501, gid=501, home=/root, shell=/bin/bash <86>Apr 26 03:28:15 userdel[13114]: delete user `builder' <86>Apr 26 03:28:15 userdel[13114]: remove group `builder' <86>Apr 26 03:28:15 groupadd[13115]: new group: name=builder, gid=502 <86>Apr 26 03:28:15 useradd[13116]: new user: name=builder, uid=502, gid=502, home=/usr/src, shell=/bin/bash <13>Apr 26 03:28:18 rpmi: ca-certificates-2007.02.06-alt1 installed <13>Apr 26 03:28:18 rpmi: libssl6-0.9.8d-alt4 installed <13>Apr 26 03:28:18 rpmi: libgdbm-1.8.3-alt4 installed <13>Apr 26 03:28:18 rpmi: libncursesw-5.6-alt4 installed <13>Apr 26 03:28:18 rpmi: python-modules-curses-2.5.2-alt0.M41.2 installed <13>Apr 26 03:28:18 rpmi: libexpat-2.0.1-alt0.1 installed <13>Apr 26 03:28:18 rpmi: libIDL-0.8.11-alt0.M41.1 installed <13>Apr 26 03:28:18 rpmi: libORBit2-2.14.12-alt1 installed <13>Apr 26 03:28:18 rpmi: xml-common-0.6.3-alt11 installed <13>Apr 26 03:28:19 rpmi: libxml2-1:2.7.2-alt1.M41.1 installed <13>Apr 26 03:28:19 rpmi: libGConf-2.22.0-alt1 installed <13>Apr 26 03:28:19 rpmi: ORBit2-2.14.12-alt1 installed <13>Apr 26 03:28:19 rpmi: libX11-locales-3:1.1.4-alt5.M41.1 installed <13>Apr 26 03:28:19 rpmi: libXau-1.0.3-alt1 installed <13>Apr 26 03:28:19 rpmi: libXdmcp-1.0.2-alt1.0 installed <13>Apr 26 03:28:19 rpmi: libxcb-1.1-alt4 installed <13>Apr 26 03:28:19 rpmi: libX11-3:1.1.4-alt5.M41.1 installed <13>Apr 26 03:28:19 rpmi: libXrender-0.9.4-alt1 installed <13>Apr 26 03:28:19 rpmi: libfreetype-2.3.6-alt0.M41.1 installed <13>Apr 26 03:28:19 rpmi: fontconfig-2.6.0-alt0.M41.1 installed Updating fonts cache: <29>Apr 26 03:28:21 fontconfig: Updating fonts cache: succeeded [ DONE ] <13>Apr 26 03:28:21 rpmi: libXft-2.1.13-alt0.M41.1 installed <13>Apr 26 03:28:21 rpmi: libXdamage-1.1.1-alt1 installed <13>Apr 26 03:28:21 rpmi: libXext-1.0.4-alt1 installed <13>Apr 26 03:28:21 rpmi: libXfixes-4.0.3-alt1 installed <13>Apr 26 03:28:21 rpmi: libXxf86vm-1.0.2-alt0.M41.1 installed <13>Apr 26 03:28:21 rpmi: libdrm-2.4.0-alt2 installed <13>Apr 26 03:28:21 rpmi: libGL-3:7.2-alt13 installed <13>Apr 26 03:28:21 rpmi: libglitz-1:0.5.7-alt1 installed <13>Apr 26 03:28:21 rpmi: libpixman-1:0.10.0-alt3 installed <13>Apr 26 03:28:21 rpmi: libpng12-1.2.27-alt1 installed <13>Apr 26 03:28:22 rpmi: libcairo-1:1.6.4-alt2.M41.1 installed <13>Apr 26 03:28:22 rpmi: libpango-1.20.5-alt0.M41.1 installed <13>Apr 26 03:28:22 rpmi: libatk-1.22.0-alt1 installed <13>Apr 26 03:28:22 rpmi: shared-mime-info-0.30-alt0.M41.1 installed <86>Apr 26 03:28:23 groupadd[13537]: new group: name=crontab, gid=36 <13>Apr 26 03:28:23 rpmi: crontab-control-1.1-alt1 installed <13>Apr 26 03:28:23 rpmi: setproctitle-0.3.1-alt1 installed <13>Apr 26 03:28:23 rpmi: vixie-cron-4.1.20060426-alt4 installed <13>Apr 26 03:28:23 rpmi: crontabs-1.8-alt1 installed <13>Apr 26 03:28:23 rpmi: libgpg-error-1.5-alt1 installed <13>Apr 26 03:28:23 rpmi: libgcrypt-1.4.1-alt1 installed <13>Apr 26 03:28:23 rpmi: libtasn1-1.1-alt1 installed <13>Apr 26 03:28:23 rpmi: libgnutls-2.0.4-alt2 installed <13>Apr 26 03:28:23 rpmi: libjpeg-1:6b-alt8 installed <13>Apr 26 03:28:23 rpmi: libtiff-3.8.2-alt2 installed <13>Apr 26 03:28:23 rpmi: libcups-1.3.7-alt2 installed <13>Apr 26 03:28:23 rpmi: libXcomposite-0.4.0-alt1 installed <13>Apr 26 03:28:23 rpmi: libXcursor-1.1.9-alt1 installed <13>Apr 26 03:28:23 rpmi: libXi-1.1.3-alt2.M41.1 installed <13>Apr 26 03:28:23 rpmi: libXinerama-1.0.3-alt1 installed <13>Apr 26 03:28:23 rpmi: libXrandr-1.2.3-alt0.M41.1 installed <13>Apr 26 03:28:23 rpmi: libxslt-1.1.24-alt0.M41.1 installed <13>Apr 26 03:28:23 rpmi: xsltproc-1.1.24-alt0.M41.1 installed <13>Apr 26 03:28:23 rpmi: menu-devel-0.2.0-alt1 installed <13>Apr 26 03:28:23 rpmi: perl-Compress-Zlib-1.42-alt3 installed <13>Apr 26 03:28:23 rpmi: perl-Crypt-SSLeay-0.57-alt1 installed <13>Apr 26 03:28:23 rpmi: perl-DBM-1:5.8.8-alt19.M41.1 installed <13>Apr 26 03:28:23 rpmi: perl-HTML-Tagset-3.20-alt1 installed <13>Apr 26 03:28:23 rpmi: perl-libnet-1:1.22-alt1 installed <13>Apr 26 03:28:23 rpmi: perl-URI-1.36-alt1 installed <13>Apr 26 03:28:23 rpmi: sgml-common-0.6.3-alt11 installed <13>Apr 26 03:28:23 rpmi: xml-utils-1:2.7.2-alt1.M41.1 installed <13>Apr 26 03:28:23 rpmi: desktop-file-utils-0.14-alt1 installed <13>Apr 26 03:28:24 rpmi: docbook-dtds-4.4-alt1 installed <13>Apr 26 03:28:24 rpmi: libstdc++4.3-4.3.2-alt6 installed <13>Apr 26 03:28:24 rpmi: librarian-0.8.0-alt1 installed <13>Apr 26 03:28:24 rpmi: python-modules-email-2.5.2-alt0.M41.2 installed <13>Apr 26 03:28:25 rpmi: libgtk+2-common-2.12.11-alt0.M41.2 installed <13>Apr 26 03:28:25 rpmi: libgtk+2-2.12.11-alt0.M41.2 installed <13>Apr 26 03:28:25 rpmi: GConf-2.22.0-alt1 installed <13>Apr 26 03:28:25 rpmi: perl-libwww-5.812-alt1 installed <13>Apr 26 03:28:26 rpmi: perl-HTML-Parser-3.56-alt2 installed <13>Apr 26 03:28:26 rpmi: perl-XML-Parser-2.36-alt1 installed <13>Apr 26 03:28:26 rpmi: python-modules-compiler-2.5.2-alt0.M41.2 installed <13>Apr 26 03:28:26 rpmi: python-modules-encodings-2.5.2-alt0.M41.2 installed <13>Apr 26 03:28:26 rpmi: python-modules-2.5.2-alt0.M41.2 installed <13>Apr 26 03:28:27 rpmi: python-modules-xml-2.5.2-alt0.M41.2 installed <13>Apr 26 03:28:27 rpmi: python-modules-hotshot-2.5.2-alt0.M41.2 installed <13>Apr 26 03:28:27 rpmi: python-modules-bsddb-2.5.2-alt0.M41.2 installed <13>Apr 26 03:28:27 rpmi: python-modules-logging-2.5.2-alt0.M41.2 installed <13>Apr 26 03:28:27 rpmi: python-2.5.2-alt0.M41.2 installed <13>Apr 26 03:28:27 rpmi: python-dev-2.5.2-alt0.M41.2 installed <13>Apr 26 03:28:27 rpmi: glib2-devel-2.16.5-alt0.M41.1 installed <13>Apr 26 03:28:27 rpmi: libGConf-devel-2.22.0-alt1 installed Installing gnochm-0.9.11-alt1.1.src.rpm Building target platforms: ppc Building for target ppc Executing(%prep): /bin/sh -e /usr/src/tmp/rpm-tmp.94378 + umask 022 + /bin/mkdir -p /usr/src/RPM/BUILD + cd /usr/src/RPM/BUILD + cd /usr/src/RPM/BUILD + rm -rf gnochm-0.9.11 + echo 'Source #0 (gnochm-0.9.11.tar.bz2):' Source #0 (gnochm-0.9.11.tar.bz2): + /bin/bzip2 -dc /usr/src/RPM/SOURCES/gnochm-0.9.11.tar.bz2 + /bin/tar -xf - + cd gnochm-0.9.11 + /bin/chmod -c -Rf u+rwX,go-w . + echo 'Patch #0 (gnochm-0.9.5.patch):' Patch #0 (gnochm-0.9.5.patch): + /usr/bin/patch -p0 patching file gnochm.py.in Hunk #1 succeeded at 49 (offset 1 line). + /usr/bin/subst 's|$(SHAREDMIME_TOOL)|true $(SHAREDMIME_TOOL)|' data/Makefile.in + exit 0 Executing(%build): /bin/sh -e /usr/src/tmp/rpm-tmp.94378 + umask 022 + /bin/mkdir -p /usr/src/RPM/BUILD + cd /usr/src/RPM/BUILD + cd gnochm-0.9.11 + 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.in'. You should update your `aclocal.m4' by running aclocal. + ./configure --build=noarch-alt-linux --host=noarch-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 gawk... gawk checking whether make sets $(MAKE)... yes checking whether to enable maintainer-specific portions of Makefiles... no checking for a BSD-compatible install... /bin/install -c checking for python... /usr/bin/python checking for version... 2.5 checking for platform... linux2 checking for gconftool-2... /usr/bin/gconftool-2 checking for scrollkeeper-config... /usr/bin/scrollkeeper-config checking for intltool >= 0.21... 0.30 found checking for perl... /usr/bin/perl checking for XML::Parser... ok checking for iconv... /usr/bin/iconv checking for msgfmt... /usr/bin/msgfmt checking for msgmerge... /usr/bin/msgmerge checking for xgettext... /usr/bin/xgettext 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 style of include used by make... GNU checking for noarch-alt-linux-gcc... no checking for gcc... 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 gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking dependency style of gcc... none checking how to run the C preprocessor... gcc -E checking for egrep... 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 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 for gmsgfmt... /usr/bin/msgfmt checking for xgettext... /usr/bin/xgettext checking for catalogs to be installed... be cs de el es fr hu it ja pl pt_BR ru sv tr vi zh_CN zh_TW checking for update-mime-database... /usr/bin/update-mime-database configure: creating ./config.status config.status: creating Makefile config.status: creating gnochm.lsm config.status: creating gnochm.py config.status: creating gnochm.spec config.status: creating pixmaps/Makefile config.status: creating glade/Makefile config.status: creating po/Makefile.in config.status: creating help/Makefile config.status: creating help/C/Makefile config.status: creating data/Makefile config.status: executing intltool commands config.status: executing depfiles commands config.status: executing default-1 commands config.status: executing po/stamp-it commands + make make: Entering directory `/usr/src/RPM/BUILD/gnochm-0.9.11' Making all in pixmaps make[1]: Entering directory `/usr/src/RPM/BUILD/gnochm-0.9.11/pixmaps' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/usr/src/RPM/BUILD/gnochm-0.9.11/pixmaps' Making all in glade make[1]: Entering directory `/usr/src/RPM/BUILD/gnochm-0.9.11/glade' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/usr/src/RPM/BUILD/gnochm-0.9.11/glade' Making all in po make[1]: Entering directory `/usr/src/RPM/BUILD/gnochm-0.9.11/po' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/usr/src/RPM/BUILD/gnochm-0.9.11/po' Making all in help make[1]: Entering directory `/usr/src/RPM/BUILD/gnochm-0.9.11/help' Making all in C make[2]: Entering directory `/usr/src/RPM/BUILD/gnochm-0.9.11/help/C' for file in gnochm-C.omf; do \ scrollkeeper-preinstall /usr/share/gnome/help/gnochm/C/gnochm.xml ./$file $file.out; \ done; \ touch omf_timestamp make[2]: Leaving directory `/usr/src/RPM/BUILD/gnochm-0.9.11/help/C' make[2]: Entering directory `/usr/src/RPM/BUILD/gnochm-0.9.11/help' make[2]: Nothing to be done for `all-am'. make[2]: Leaving directory `/usr/src/RPM/BUILD/gnochm-0.9.11/help' make[1]: Leaving directory `/usr/src/RPM/BUILD/gnochm-0.9.11/help' Making all in data make[1]: Entering directory `/usr/src/RPM/BUILD/gnochm-0.9.11/data' LC_ALL=C ../intltool-merge -d -u -c ../po/.intltool-merge-cache ../po gnochm.desktop.in gnochm.desktop Generating and caching the translation database WARNING: ../po/de.po is not in UTF-8 but iso-8859-1, converting... Merging translations into gnochm.desktop. LC_ALL=C ../intltool-merge -k -u -c ../po/.intltool-merge-cache ../po gnochm.keys.in gnochm.keys Found cached translation database Merging translations into gnochm.keys. LC_ALL=C ../intltool-merge -s -u -c ../po/.intltool-merge-cache ../po gnochm.schemas.in gnochm.schemas Found cached translation database Merging translations into gnochm.schemas. make[1]: Leaving directory `/usr/src/RPM/BUILD/gnochm-0.9.11/data' make[1]: Entering directory `/usr/src/RPM/BUILD/gnochm-0.9.11' rm -f gnochm cp gnochm.py gnochm chmod +x gnochm make[1]: Leaving directory `/usr/src/RPM/BUILD/gnochm-0.9.11' make: Leaving directory `/usr/src/RPM/BUILD/gnochm-0.9.11' + exit 0 Executing(%install): /bin/sh -e /usr/src/tmp/rpm-tmp.84608 + umask 022 + /bin/mkdir -p /usr/src/RPM/BUILD + cd /usr/src/RPM/BUILD + /bin/chmod -Rf u+rwX -- /usr/src/tmp/gnochm-buildroot + : + /bin/rm -rf -- /usr/src/tmp/gnochm-buildroot + cd gnochm-0.9.11 + /usr/bin/make 'INSTALL=/bin/install -p' prefix=/usr/src/tmp/gnochm-buildroot/usr exec_prefix=/usr/src/tmp/gnochm-buildroot/usr bindir=/usr/src/tmp/gnochm-buildroot/usr/bin sbindir=/usr/src/tmp/gnochm-buildroot/usr/sbin sysconfdir=/usr/src/tmp/gnochm-buildroot/etc datadir=/usr/src/tmp/gnochm-buildroot/usr/share includedir=/usr/src/tmp/gnochm-buildroot/usr/include libdir=/usr/src/tmp/gnochm-buildroot/usr/lib libexecdir=/usr/src/tmp/gnochm-buildroot/usr/lib localstatedir=/usr/src/tmp/gnochm-buildroot/var/lib sharedstatedir=/usr/src/tmp/gnochm-buildroot/usr/com mandir=/usr/src/tmp/gnochm-buildroot/usr/share/man infodir=/usr/src/tmp/gnochm-buildroot/usr/share/info install make: Entering directory `/usr/src/RPM/BUILD/gnochm-0.9.11' Making install in pixmaps make[1]: Entering directory `/usr/src/RPM/BUILD/gnochm-0.9.11/pixmaps' make[2]: Entering directory `/usr/src/RPM/BUILD/gnochm-0.9.11/pixmaps' make[2]: Nothing to be done for `install-exec-am'. test -z "/usr/src/tmp/gnochm-buildroot/usr/share/pixmaps" || mkdir -p -- "/usr/src/tmp/gnochm-buildroot/usr/share/pixmaps" /bin/install -p -m 644 'chmfile.png' '/usr/src/tmp/gnochm-buildroot/usr/share/pixmaps/chmfile.png' /bin/install -p -m 644 'gnochm.png' '/usr/src/tmp/gnochm-buildroot/usr/share/pixmaps/gnochm.png' /bin/install -p -m 644 'gnochm_logo.png' '/usr/src/tmp/gnochm-buildroot/usr/share/pixmaps/gnochm_logo.png' make[2]: Leaving directory `/usr/src/RPM/BUILD/gnochm-0.9.11/pixmaps' make[1]: Leaving directory `/usr/src/RPM/BUILD/gnochm-0.9.11/pixmaps' Making install in glade make[1]: Entering directory `/usr/src/RPM/BUILD/gnochm-0.9.11/glade' make[2]: Entering directory `/usr/src/RPM/BUILD/gnochm-0.9.11/glade' make[2]: Nothing to be done for `install-exec-am'. test -z "/usr/src/tmp/gnochm-buildroot/usr/share/gnochm/glade" || mkdir -p -- "/usr/src/tmp/gnochm-buildroot/usr/share/gnochm/glade" /bin/install -p -m 644 'gnochm.glade' '/usr/src/tmp/gnochm-buildroot/usr/share/gnochm/glade/gnochm.glade' /bin/install -p -m 644 'prefdialog.glade' '/usr/src/tmp/gnochm-buildroot/usr/share/gnochm/glade/prefdialog.glade' make[2]: Leaving directory `/usr/src/RPM/BUILD/gnochm-0.9.11/glade' make[1]: Leaving directory `/usr/src/RPM/BUILD/gnochm-0.9.11/glade' Making install in po make[1]: Entering directory `/usr/src/RPM/BUILD/gnochm-0.9.11/po' if test -r ".././mkinstalldirs"; then \ .././mkinstalldirs /usr/src/tmp/gnochm-buildroot/usr/share; \ else \ /bin/sh ../mkinstalldirs /usr/src/tmp/gnochm-buildroot/usr/share; \ fi mkdir -p -- /usr/src/tmp/gnochm-buildroot/usr/share/locale/be/LC_MESSAGES installing be.gmo as /usr/src/tmp/gnochm-buildroot/usr/share/locale/be/LC_MESSAGES/gnochm.mo mkdir -p -- /usr/src/tmp/gnochm-buildroot/usr/share/locale/cs/LC_MESSAGES installing cs.gmo as /usr/src/tmp/gnochm-buildroot/usr/share/locale/cs/LC_MESSAGES/gnochm.mo mkdir -p -- /usr/src/tmp/gnochm-buildroot/usr/share/locale/de/LC_MESSAGES installing de.gmo as /usr/src/tmp/gnochm-buildroot/usr/share/locale/de/LC_MESSAGES/gnochm.mo mkdir -p -- /usr/src/tmp/gnochm-buildroot/usr/share/locale/el/LC_MESSAGES installing el.gmo as /usr/src/tmp/gnochm-buildroot/usr/share/locale/el/LC_MESSAGES/gnochm.mo mkdir -p -- /usr/src/tmp/gnochm-buildroot/usr/share/locale/es/LC_MESSAGES installing es.gmo as /usr/src/tmp/gnochm-buildroot/usr/share/locale/es/LC_MESSAGES/gnochm.mo mkdir -p -- /usr/src/tmp/gnochm-buildroot/usr/share/locale/fr/LC_MESSAGES installing fr.gmo as /usr/src/tmp/gnochm-buildroot/usr/share/locale/fr/LC_MESSAGES/gnochm.mo mkdir -p -- /usr/src/tmp/gnochm-buildroot/usr/share/locale/hu/LC_MESSAGES installing hu.gmo as /usr/src/tmp/gnochm-buildroot/usr/share/locale/hu/LC_MESSAGES/gnochm.mo mkdir -p -- /usr/src/tmp/gnochm-buildroot/usr/share/locale/it/LC_MESSAGES installing it.gmo as /usr/src/tmp/gnochm-buildroot/usr/share/locale/it/LC_MESSAGES/gnochm.mo mkdir -p -- /usr/src/tmp/gnochm-buildroot/usr/share/locale/ja/LC_MESSAGES installing ja.gmo as /usr/src/tmp/gnochm-buildroot/usr/share/locale/ja/LC_MESSAGES/gnochm.mo mkdir -p -- /usr/src/tmp/gnochm-buildroot/usr/share/locale/pl/LC_MESSAGES installing pl.gmo as /usr/src/tmp/gnochm-buildroot/usr/share/locale/pl/LC_MESSAGES/gnochm.mo mkdir -p -- /usr/src/tmp/gnochm-buildroot/usr/share/locale/pt_BR/LC_MESSAGES installing pt_BR.gmo as /usr/src/tmp/gnochm-buildroot/usr/share/locale/pt_BR/LC_MESSAGES/gnochm.mo mkdir -p -- /usr/src/tmp/gnochm-buildroot/usr/share/locale/ru/LC_MESSAGES installing ru.gmo as /usr/src/tmp/gnochm-buildroot/usr/share/locale/ru/LC_MESSAGES/gnochm.mo mkdir -p -- /usr/src/tmp/gnochm-buildroot/usr/share/locale/sv/LC_MESSAGES installing sv.gmo as /usr/src/tmp/gnochm-buildroot/usr/share/locale/sv/LC_MESSAGES/gnochm.mo mkdir -p -- /usr/src/tmp/gnochm-buildroot/usr/share/locale/tr/LC_MESSAGES installing tr.gmo as /usr/src/tmp/gnochm-buildroot/usr/share/locale/tr/LC_MESSAGES/gnochm.mo mkdir -p -- /usr/src/tmp/gnochm-buildroot/usr/share/locale/vi/LC_MESSAGES installing vi.gmo as /usr/src/tmp/gnochm-buildroot/usr/share/locale/vi/LC_MESSAGES/gnochm.mo mkdir -p -- /usr/src/tmp/gnochm-buildroot/usr/share/locale/zh_CN/LC_MESSAGES installing zh_CN.gmo as /usr/src/tmp/gnochm-buildroot/usr/share/locale/zh_CN/LC_MESSAGES/gnochm.mo mkdir -p -- /usr/src/tmp/gnochm-buildroot/usr/share/locale/zh_TW/LC_MESSAGES installing zh_TW.gmo as /usr/src/tmp/gnochm-buildroot/usr/share/locale/zh_TW/LC_MESSAGES/gnochm.mo if test "gnochm" = "glib"; then \ if test -r ".././mkinstalldirs"; then \ .././mkinstalldirs /usr/src/tmp/gnochm-buildroot/usr/share/glib-2.0/gettext/po; \ else \ /bin/sh ../mkinstalldirs /usr/src/tmp/gnochm-buildroot/usr/share/glib-2.0/gettext/po; \ fi; \ /bin/install -p -m 644 ./Makefile.in.in \ /usr/src/tmp/gnochm-buildroot/usr/share/glib-2.0/gettext/po/Makefile.in.in; \ else \ : ; \ fi make[1]: Leaving directory `/usr/src/RPM/BUILD/gnochm-0.9.11/po' Making install in help make[1]: Entering directory `/usr/src/RPM/BUILD/gnochm-0.9.11/help' Making install in C make[2]: Entering directory `/usr/src/RPM/BUILD/gnochm-0.9.11/help/C' make[3]: Entering directory `/usr/src/RPM/BUILD/gnochm-0.9.11/help/C' make[3]: Nothing to be done for `install-exec-am'. /bin/sh ../../mkinstalldirs /usr/src/tmp/gnochm-buildroot/usr/share/gnome/help/gnochm/C mkdir -p -- /usr/src/tmp/gnochm-buildroot/usr/share/gnome/help/gnochm/C for file in legal.xml gnochm.xml; do \ cp ./$file /usr/src/tmp/gnochm-buildroot/usr/share/gnome/help/gnochm/C; \ done if test ""; then \ /bin/sh ../../mkinstalldirs /usr/src/tmp/gnochm-buildroot/usr/share/gnome/help/gnochm/C/; \ for file in .//*.png; do \ basefile=`echo $file | sed -e 's,^.*/,,'`; \ /bin/install -p -m 644 $file /usr/src/tmp/gnochm-buildroot/usr/share/gnome/help/gnochm/C//$basefile; \ done \ fi /usr/bin/make install-data-hook make[4]: Entering directory `/usr/src/RPM/BUILD/gnochm-0.9.11/help/C' /bin/sh ../../mkinstalldirs /usr/src/tmp/gnochm-buildroot/usr/share/omf/gnochm mkdir -p -- /usr/src/tmp/gnochm-buildroot/usr/share/omf/gnochm for file in gnochm-C.omf; do \ /bin/install -p -m 644 $file.out /usr/src/tmp/gnochm-buildroot/usr/share/omf/gnochm/$file; \ done scrollkeeper-update -p /usr/src/tmp/gnochm-buildroot/var/lib/scrollkeeper -o /usr/src/tmp/gnochm-buildroot/usr/share/omf/gnochm make[4]: Leaving directory `/usr/src/RPM/BUILD/gnochm-0.9.11/help/C' make[3]: Leaving directory `/usr/src/RPM/BUILD/gnochm-0.9.11/help/C' make[2]: Leaving directory `/usr/src/RPM/BUILD/gnochm-0.9.11/help/C' make[2]: Entering directory `/usr/src/RPM/BUILD/gnochm-0.9.11/help' make[3]: Entering directory `/usr/src/RPM/BUILD/gnochm-0.9.11/help' make[3]: Nothing to be done for `install-exec-am'. make[3]: Nothing to be done for `install-data-am'. make[3]: Leaving directory `/usr/src/RPM/BUILD/gnochm-0.9.11/help' make[2]: Leaving directory `/usr/src/RPM/BUILD/gnochm-0.9.11/help' make[1]: Leaving directory `/usr/src/RPM/BUILD/gnochm-0.9.11/help' Making install in data make[1]: Entering directory `/usr/src/RPM/BUILD/gnochm-0.9.11/data' make[2]: Entering directory `/usr/src/RPM/BUILD/gnochm-0.9.11/data' make[2]: Nothing to be done for `install-exec-am'. test -z "/usr/src/tmp/gnochm-buildroot/usr/share/application-registry" || mkdir -p -- "/usr/src/tmp/gnochm-buildroot/usr/share/application-registry" /bin/install -p -m 644 'gnochm.applications' '/usr/src/tmp/gnochm-buildroot/usr/share/application-registry/gnochm.applications' if test -z "" ; then \ for p in gnochm.schemas ; do \ GCONF_CONFIG_SOURCE=xml:readwrite:/var/cache/gconf/gconf.xml.defaults /usr/bin/gconftool-2 --makefile-install-rule ./$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/gnochm/preferences/sync_page' to key `/apps/gnochm/preferences/sync_page' WARNING: failed to install schema `/schemas/apps/gnochm/preferences/sync_page', locale `C': Unable to store a value at key '/schemas/apps/gnochm/preferences/sync_page', 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/gnochm/preferences/sync_page', locale `pt_BR': Unable to store a value at key '/schemas/apps/gnochm/preferences/sync_page', 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/gnochm/preferences/save_path' to key `/apps/gnochm/preferences/save_path' WARNING: failed to install schema `/schemas/apps/gnochm/preferences/save_path', locale `C': Unable to store a value at key '/schemas/apps/gnochm/preferences/save_path', 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/gnochm/preferences/save_path', locale `it': Unable to store a value at key '/schemas/apps/gnochm/preferences/save_path', 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/gnochm/preferences/save_path', locale `pt_BR': Unable to store a value at key '/schemas/apps/gnochm/preferences/save_path', 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/gnochm/preferences/use_lcid' to key `/apps/gnochm/preferences/use_lcid' WARNING: failed to install schema `/schemas/apps/gnochm/preferences/use_lcid', locale `C': Unable to store a value at key '/schemas/apps/gnochm/preferences/use_lcid', 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/gnochm/preferences/use_lcid', locale `it': Unable to store a value at key '/schemas/apps/gnochm/preferences/use_lcid', 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/gnochm/preferences/use_lcid', locale `pt_BR': Unable to store a value at key '/schemas/apps/gnochm/preferences/use_lcid', 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/gnochm/preferences/recent_size' to key `/apps/gnochm/preferences/recent_size' WARNING: failed to install schema `/schemas/apps/gnochm/preferences/recent_size', locale `C': Unable to store a value at key '/schemas/apps/gnochm/preferences/recent_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/gnochm/preferences/recent_size', locale `it': Unable to store a value at key '/schemas/apps/gnochm/preferences/recent_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/gnochm/preferences/recent_size', locale `pt_BR': Unable to store a value at key '/schemas/apps/gnochm/preferences/recent_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 Attached schema `/schemas/apps/gnochm/preferences/search_previous' to key `/apps/gnochm/preferences/search_previous' WARNING: failed to install schema `/schemas/apps/gnochm/preferences/search_previous', locale `C': Unable to store a value at key '/schemas/apps/gnochm/preferences/search_previous', 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/gnochm/preferences/search_previous', locale `it': Unable to store a value at key '/schemas/apps/gnochm/preferences/search_previous', 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/gnochm/preferences/search_previous', locale `pt_BR': Unable to store a value at key '/schemas/apps/gnochm/preferences/search_previous', 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/gnochm/preferences/titles_only' to key `/apps/gnochm/preferences/titles_only' WARNING: failed to install schema `/schemas/apps/gnochm/preferences/titles_only', locale `C': Unable to store a value at key '/schemas/apps/gnochm/preferences/titles_only', 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/gnochm/preferences/titles_only', locale `it': Unable to store a value at key '/schemas/apps/gnochm/preferences/titles_only', 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/gnochm/preferences/titles_only', locale `pt_BR': Unable to store a value at key '/schemas/apps/gnochm/preferences/titles_only', 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/gnochm/preferences/whole_words' to key `/apps/gnochm/preferences/whole_words' WARNING: failed to install schema `/schemas/apps/gnochm/preferences/whole_words', locale `C': Unable to store a value at key '/schemas/apps/gnochm/preferences/whole_words', 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/gnochm/preferences/whole_words', locale `it': Unable to store a value at key '/schemas/apps/gnochm/preferences/whole_words', 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/gnochm/preferences/whole_words', locale `pt_BR': Unable to store a value at key '/schemas/apps/gnochm/preferences/whole_words', 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/gnochm/preferences/toolbar_enable' to key `/apps/gnochm/preferences/toolbar_enable' WARNING: failed to install schema `/schemas/apps/gnochm/preferences/toolbar_enable', locale `C': Unable to store a value at key '/schemas/apps/gnochm/preferences/toolbar_enable', 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/gnochm/preferences/toolbar_enable', locale `it': Unable to store a value at key '/schemas/apps/gnochm/preferences/toolbar_enable', 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/gnochm/preferences/toolbar_enable', locale `pt_BR': Unable to store a value at key '/schemas/apps/gnochm/preferences/toolbar_enable', 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/gnochm/preferences/toolbar_tooltips' to key `/apps/gnochm/preferences/toolbar_tooltips' WARNING: failed to install schema `/schemas/apps/gnochm/preferences/toolbar_tooltips', locale `C': Unable to store a value at key '/schemas/apps/gnochm/preferences/toolbar_tooltips', 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/gnochm/preferences/toolbar_tooltips', locale `it': Unable to store a value at key '/schemas/apps/gnochm/preferences/toolbar_tooltips', 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/gnochm/preferences/toolbar_tooltips', locale `pt_BR': Unable to store a value at key '/schemas/apps/gnochm/preferences/toolbar_tooltips', 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/gnochm/preferences/tree_views' to key `/apps/gnochm/preferences/index_tree' Attached schema `/schemas/apps/gnochm/preferences/tree_views' to key `/apps/gnochm/preferences/contents_tree' WARNING: failed to install schema `/schemas/apps/gnochm/preferences/tree_views', locale `C': Unable to store a value at key '/schemas/apps/gnochm/preferences/tree_views', 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/gnochm/preferences/tree_views', locale `it': Unable to store a value at key '/schemas/apps/gnochm/preferences/tree_views', 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/gnochm/preferences/tree_views', locale `pt_BR': Unable to store a value at key '/schemas/apps/gnochm/preferences/tree_views', 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/gnochm/preferences/html_bg_color' to key `/apps/gnochm/preferences/html_bg_color' WARNING: failed to install schema `/schemas/apps/gnochm/preferences/html_bg_color', locale `C': Unable to store a value at key '/schemas/apps/gnochm/preferences/html_bg_color', 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/gnochm/preferences/html_bg_color', locale `it': Unable to store a value at key '/schemas/apps/gnochm/preferences/html_bg_color', 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/gnochm/preferences/html_bg_color', locale `pt_BR': Unable to store a value at key '/schemas/apps/gnochm/preferences/html_bg_color', 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/gnochm/preferences/chm_search_path' to key `/apps/gnochm/preferences/chm_search_path' WARNING: failed to install schema `/schemas/apps/gnochm/preferences/chm_search_path', locale `C': Unable to store a value at key '/schemas/apps/gnochm/preferences/chm_search_path', 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/gnochm/preferences/chm_search_path', locale `it': Unable to store a value at key '/schemas/apps/gnochm/preferences/chm_search_path', 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/gnochm/preferences/chm_search_path', locale `pt_BR': Unable to store a value at key '/schemas/apps/gnochm/preferences/chm_search_path', 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/gnochm/preferences/http_support' to key `/apps/gnochm/preferences/http_support' WARNING: failed to install schema `/schemas/apps/gnochm/preferences/http_support', locale `C': Unable to store a value at key '/schemas/apps/gnochm/preferences/http_support', 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/gnochm/preferences/http_support', locale `it': Unable to store a value at key '/schemas/apps/gnochm/preferences/http_support', 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/gnochm/preferences/http_support', locale `pt_BR': Unable to store a value at key '/schemas/apps/gnochm/preferences/http_support', 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/gnochm/preferences/new_browser_window' to key `/apps/gnochm/preferences/new_browser_window' WARNING: failed to install schema `/schemas/apps/gnochm/preferences/new_browser_window', locale `C': Unable to store a value at key '/schemas/apps/gnochm/preferences/new_browser_window', 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/gnochm/preferences/new_browser_window', locale `it': Unable to store a value at key '/schemas/apps/gnochm/preferences/new_browser_window', 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/gnochm/preferences/new_browser_window', locale `pt_BR': Unable to store a value at key '/schemas/apps/gnochm/preferences/new_browser_window', 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/gnochm/preferences/auto_raise_window' to key `/apps/gnochm/preferences/auto_raise_window' WARNING: failed to install schema `/schemas/apps/gnochm/preferences/auto_raise_window', locale `C': Unable to store a value at key '/schemas/apps/gnochm/preferences/auto_raise_window', 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/gnochm/preferences/auto_raise_window', locale `it': Unable to store a value at key '/schemas/apps/gnochm/preferences/auto_raise_window', 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/gnochm/preferences/auto_raise_window', locale `pt_BR': Unable to store a value at key '/schemas/apps/gnochm/preferences/auto_raise_window', 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/gnochm/preferences/source_newwindow' to key `/apps/gnochm/preferences/source_newwindow' WARNING: failed to install schema `/schemas/apps/gnochm/preferences/source_newwindow', locale `C': Unable to store a value at key '/schemas/apps/gnochm/preferences/source_newwindow', 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/gnochm/preferences/source_newwindow', locale `it': Unable to store a value at key '/schemas/apps/gnochm/preferences/source_newwindow', 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/gnochm/preferences/source_newwindow', locale `pt_BR': Unable to store a value at key '/schemas/apps/gnochm/preferences/source_newwindow', 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/gnochm-buildroot/usr/share/applications" || mkdir -p -- "/usr/src/tmp/gnochm-buildroot/usr/share/applications" /bin/install -p -m 644 'gnochm.desktop' '/usr/src/tmp/gnochm-buildroot/usr/share/applications/gnochm.desktop' test -z "/usr/src/tmp/gnochm-buildroot/usr/share/mime-info" || mkdir -p -- "/usr/src/tmp/gnochm-buildroot/usr/share/mime-info" /bin/install -p -m 644 'gnochm.keys' '/usr/src/tmp/gnochm-buildroot/usr/share/mime-info/gnochm.keys' test -z "/usr/src/tmp/gnochm-buildroot/usr/share/mime-info" || mkdir -p -- "/usr/src/tmp/gnochm-buildroot/usr/share/mime-info" /bin/install -p -m 644 'gnochm.mime' '/usr/src/tmp/gnochm-buildroot/usr/share/mime-info/gnochm.mime' test -z "/usr/src/tmp/gnochm-buildroot/etc/gconf/schemas" || mkdir -p -- "/usr/src/tmp/gnochm-buildroot/etc/gconf/schemas" /bin/install -p -m 644 'gnochm.schemas' '/usr/src/tmp/gnochm-buildroot/etc/gconf/schemas/gnochm.schemas' test -z "/usr/src/tmp/gnochm-buildroot/usr/share/mime/packages" || mkdir -p -- "/usr/src/tmp/gnochm-buildroot/usr/share/mime/packages" /bin/install -p -m 644 'gnochm.xml' '/usr/src/tmp/gnochm-buildroot/usr/share/mime/packages/gnochm.xml' /usr/bin/make install-data-hook make[3]: Entering directory `/usr/src/RPM/BUILD/gnochm-0.9.11/data' if test "xtrue /usr/bin/update-mime-database" != "xno"; then \ true /usr/bin/update-mime-database /usr/src/tmp/gnochm-buildroot/usr/share/mime; \ fi make[3]: Leaving directory `/usr/src/RPM/BUILD/gnochm-0.9.11/data' make[2]: Leaving directory `/usr/src/RPM/BUILD/gnochm-0.9.11/data' make[1]: Leaving directory `/usr/src/RPM/BUILD/gnochm-0.9.11/data' make[1]: Entering directory `/usr/src/RPM/BUILD/gnochm-0.9.11' make[2]: Entering directory `/usr/src/RPM/BUILD/gnochm-0.9.11' test -z "/usr/src/tmp/gnochm-buildroot/usr/bin" || mkdir -p -- "/usr/src/tmp/gnochm-buildroot/usr/bin" /bin/install -p 'gnochm' '/usr/src/tmp/gnochm-buildroot/usr/bin/gnochm' make[2]: Nothing to be done for `install-data-am'. make[2]: Leaving directory `/usr/src/RPM/BUILD/gnochm-0.9.11' make[1]: Leaving directory `/usr/src/RPM/BUILD/gnochm-0.9.11' make: Leaving directory `/usr/src/RPM/BUILD/gnochm-0.9.11' + mv /usr/src/tmp/gnochm-buildroot/usr/bin/gnochm /usr/src/tmp/gnochm-buildroot/usr/bin/gnochm.py + ln -s gnochm.py /usr/src/tmp/gnochm-buildroot/usr/bin/gnochm + /usr/bin/subst 's,/usr/bin/python,/usr/bin/env python,' /usr/src/tmp/gnochm-buildroot/usr/bin/gnochm.py + /usr/lib/rpm/find-lang gnochm --with-gnome + /bin/rm -rf /usr/src/tmp/gnochm-buildroot/var/lib/scrollkeeper + /usr/lib/rpm/brp-alt Cleaning files in /usr/src/tmp/gnochm-buildroot (auto) Verifying and fixing files in /usr/src/tmp/gnochm-buildroot (binconfig,pkgconfig,libtool) Compressing files in /usr/src/tmp/gnochm-buildroot (auto) Verifying ELF objects in /usr/src/tmp/gnochm-buildroot (arch=normal,fhs=normal,rpath=normal,stack=normal,textrel=normal,unresolved=normal) Stripping binaries in /usr/src/tmp/gnochm-buildroot (executable,shared) Bytecompiling python modules in /usr/src/tmp/gnochm-buildroot using /usr/bin/python Can't list '/usr/src/tmp/gnochm-buildroot/usr/lib' Bytecompiling python modules with optimization in /usr/src/tmp/gnochm-buildroot using /usr/bin/python -O Can't list '/usr/src/tmp/gnochm-buildroot/usr/lib' Processing files: gnochm-0.9.11-alt1.1 Executing(%doc): /bin/sh -e /usr/src/tmp/rpm-tmp.12675 + umask 022 + /bin/mkdir -p /usr/src/RPM/BUILD + cd /usr/src/RPM/BUILD + cd gnochm-0.9.11 + DOCDIR=/usr/src/tmp/gnochm-buildroot/usr/share/doc/gnochm-0.9.11 + export DOCDIR + rm -rf /usr/src/tmp/gnochm-buildroot/usr/share/doc/gnochm-0.9.11 + /bin/mkdir -p /usr/src/tmp/gnochm-buildroot/usr/share/doc/gnochm-0.9.11 + cp -prL ABOUT-NLS AUTHORS ChangeLog NEWS README /usr/src/tmp/gnochm-buildroot/usr/share/doc/gnochm-0.9.11 + chmod -R go-w /usr/src/tmp/gnochm-buildroot/usr/share/doc/gnochm-0.9.11 + chmod -R a+rX /usr/src/tmp/gnochm-buildroot/usr/share/doc/gnochm-0.9.11 + exit 0 Finding Provides (using /usr/lib/rpm/find-provides) Executing(Provides): /bin/sh -e /usr/src/tmp/rpm-tmp.12675 + 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.82917 + umask 022 + /bin/mkdir -p /usr/src/RPM/BUILD + cd /usr/src/RPM/BUILD + /usr/lib/rpm/find-scriptlet-requires /usr/src/tmp/gnochm-buildroot/.post:gnochm + exit 0 Finding Requires(preun) (using /usr/lib/rpm/find-scriptlet-requires) Executing(Requires(preun)): /bin/sh -e /usr/src/tmp/rpm-tmp.71907 + umask 022 + /bin/mkdir -p /usr/src/RPM/BUILD + cd /usr/src/RPM/BUILD + /usr/lib/rpm/find-scriptlet-requires /usr/src/tmp/gnochm-buildroot/.preun:gnochm + exit 0 Finding Requires(postun) (using /usr/lib/rpm/find-scriptlet-requires) Executing(Requires(postun)): /bin/sh -e /usr/src/tmp/rpm-tmp.53827 + umask 022 + /bin/mkdir -p /usr/src/RPM/BUILD + cd /usr/src/RPM/BUILD + /usr/lib/rpm/find-scriptlet-requires /usr/src/tmp/gnochm-buildroot/.postun:gnochm + exit 0 Finding Requires (using /usr/lib/rpm/find-requires) Executing(Requires): /bin/sh -e /usr/src/tmp/rpm-tmp.79942 + 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) + exit 0 PreReq: python = 2.5 Requires(interp): /bin/sh, /bin/sh, /bin/sh Requires(rpmlib): rpmlib(VersionedDependencies) <= 3.0.3-1, rpmlib(PayloadFilesHavePrefix) <= 4.0-1, rpmlib(CompressedFileNames) <= 3.0.4-1 Requires(post): GConf2, scrollkeeper, desktop-file-utils, /bin/sh, /usr/bin/update-desktop-database, /usr/sbin/gconf_install_schema Requires(preun): /bin/sh, /usr/sbin/gconf_uninstall_schema Requires(postun): scrollkeeper, desktop-file-utils, /bin/sh, /usr/bin/update-desktop-database Requires: python2.5(libglade), python2.5(bonobo), /usr/bin/env, /usr/bin/python, python2.5(ConfigParser), python2.5(chm), python2.5(codecs), python2.5(gconf), python2.5(getopt), python2.5(gettext), python2.5(gnome), python2.5(gobject), python2.5(gtk), python2.5(gtkhtml2), python2.5(htmlentitydefs), python2.5(locale), python2.5(mimetypes), python2.5(os), python2.5(pickle), python2.5(re), python2.5(sgmllib), python2.5(string), python2.5(urllib), python2.5(urlparse), python2.5(webbrowser) Finding unpackaged files (using /usr/lib/rpm/check-files) Executing(check-files): /bin/sh -e /usr/src/tmp/rpm-tmp.19338 + 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/gnochm-0.9.11-alt1.1.src.rpm Wrote: /usr/src/RPM/RPMS/noarch/gnochm-0.9.11-alt1.1.noarch.rpm 5.24user 3.67system 0:14.92elapsed 59%CPU (0avgtext+0avgdata 0maxresident)k 0inputs+0outputs (0major+793086minor)pagefaults 0swaps