<86>Apr 21 00:59:51 userdel[7127]: delete user 'rooter' <86>Apr 21 00:59:51 groupadd[7132]: group added to /etc/group: name=rooter, GID=591 <86>Apr 21 00:59:51 groupadd[7132]: group added to /etc/gshadow: name=rooter <86>Apr 21 00:59:51 groupadd[7132]: new group: name=rooter, GID=591 <86>Apr 21 00:59:51 useradd[7137]: new user: name=rooter, UID=591, GID=591, home=/root, shell=/bin/bash <86>Apr 21 00:59:51 userdel[7144]: delete user 'builder' <86>Apr 21 00:59:51 userdel[7144]: removed group 'builder' owned by 'builder' <86>Apr 21 00:59:51 groupadd[7151]: group added to /etc/group: name=builder, GID=592 <86>Apr 21 00:59:51 groupadd[7151]: group added to /etc/gshadow: name=builder <86>Apr 21 00:59:51 groupadd[7151]: new group: name=builder, GID=592 <86>Apr 21 00:59:51 useradd[7156]: new user: name=builder, UID=592, GID=592, home=/usr/src, shell=/bin/bash <13>Apr 21 00:59:55 rpmi: perl-Encode-2.83-alt1 1459157776 installed <13>Apr 21 00:59:55 rpmi: perl-HTTP-Date-6.02-alt1 1348645274 installed <13>Apr 21 00:59:55 rpmi: libexpat-2.2.4-alt0.M80P.1 1503871120 installed <13>Apr 21 00:59:55 rpmi: xml-utils-1:2.9.4.0.12.e905-alt1 1488560683 installed <13>Apr 21 00:59:55 rpmi: perl-LWP-MediaTypes-6.02-alt1 1329754558 installed <13>Apr 21 00:59:55 rpmi: perl-libnet-1:3.08-alt1 1458419902 installed <13>Apr 21 00:59:55 rpmi: perl-URI-1.71-alt1 1455181348 installed <13>Apr 21 00:59:55 rpmi: perl-Compress-Raw-Zlib-2.069-alt1.1 1448470036 installed <13>Apr 21 00:59:55 rpmi: perl-WWW-RobotRules-6.02-alt1 1329756211 installed <13>Apr 21 00:59:55 rpmi: rpm-build-gir-0.7.2-alt3 1489330162 installed <13>Apr 21 00:59:55 rpmi: perl-File-Listing-6.04-alt1 1329758996 installed <13>Apr 21 00:59:55 rpmi: perl-Encode-Locale-1.05-alt1 1444608613 installed <13>Apr 21 00:59:55 rpmi: perl-IO-HTML-1.001-alt1 1404821752 installed <13>Apr 21 00:59:55 rpmi: sgml-common-0.6.3-alt15 1423664786 installed <13>Apr 21 00:59:55 rpmi: docbook-dtds-4.5-alt1 1223476557 installed <13>Apr 21 00:59:55 rpmi: perl-IO-Socket-IP-0.37-alt1 1444921335 installed <13>Apr 21 00:59:55 rpmi: perl-HTML-Tagset-3.20-alt2 1317725093 installed <13>Apr 21 00:59:55 rpmi: perl-HTML-Parser-3.72-alt1 1455170565 installed <13>Apr 21 00:59:55 rpmi: perl-Compress-Raw-Bzip2-2.069-alt1.1 1448470068 installed <13>Apr 21 00:59:55 rpmi: perl-IO-Compress-2.069-alt1 1444618007 installed <13>Apr 21 00:59:55 rpmi: perl-HTTP-Message-6.11-alt1 1444616672 installed <13>Apr 21 00:59:55 rpmi: perl-HTTP-Cookies-6.01-alt1 1329759964 installed <13>Apr 21 00:59:55 rpmi: perl-HTTP-Negotiate-6.01-alt1 1329760563 installed <13>Apr 21 00:59:55 rpmi: perl-Net-HTTP-6.09-alt1 1432310023 installed <13>Apr 21 00:59:55 rpmi: perl-libwww-6.15-alt1 1449505512 installed <13>Apr 21 00:59:55 rpmi: libX11-locales-3:1.6.3-alt1 1431956885 installed <13>Apr 21 00:59:55 rpmi: libXdmcp-1.1.1-alt1 1334617699 installed <13>Apr 21 00:59:55 rpmi: libXau-1.0.8-alt1 1369565807 installed <13>Apr 21 00:59:56 rpmi: libxcb-1.12-alt2 p8.218219.300 1545313310 installed <13>Apr 21 00:59:56 rpmi: libX11-3:1.6.3-alt1 1431956911 installed <13>Apr 21 00:59:56 rpmi: rpm-build-xdg-0.2-alt1 1250461503 installed <13>Apr 21 00:59:56 rpmi: shared-mime-info-1.9-alt0.M80P.1 1506021412 installed <13>Apr 21 00:59:56 rpmi: gsettings-desktop-schemas-data-3.24.1-alt0.M80P.1 1504768054 installed <13>Apr 21 00:59:56 rpmi: liblz4-1:1.7.5-alt1 1488766699 installed <13>Apr 21 00:59:56 rpmi: libgpg-error-1.31-alt1.M80P.1 1529024730 installed <13>Apr 21 00:59:56 rpmi: libgcrypt20-1.8.3-alt4 p8+219793.200.6.1 1551112986 installed <13>Apr 21 00:59:56 rpmi: libsystemd-1:239-alt1.M80P.1 p8+226956.200.2.1 1555431492 installed <13>Apr 21 00:59:56 rpmi: libdbus-1.10.24-alt4.M80P.1 1518773282 installed <13>Apr 21 00:59:56 rpmi: libxslt-1.1.28-alt4 1448210404 installed <13>Apr 21 00:59:56 rpmi: xsltproc-1.1.28-alt4 1448210404 installed <13>Apr 21 00:59:56 rpmi: libtinfo-devel-5.9-alt8 1456756459 installed <13>Apr 21 00:59:56 rpmi: libncurses-devel-5.9-alt8 1456756459 installed <13>Apr 21 00:59:56 rpmi: python-modules-curses-2.7.11-alt6.M80P.1 1527682470 installed <13>Apr 21 00:59:56 rpmi: libverto-0.2.6-alt1_6 1455633234 installed <13>Apr 21 00:59:56 rpmi: libkeyutils-1.5.10-alt0.M80P.2 p8+216694.100.6.1 1547827915 installed <13>Apr 21 00:59:56 rpmi: libcom_err-1.42.13-alt2 1449075846 installed <13>Apr 21 00:59:56 rpmi: libgdbm-1.8.3-alt10 1454943313 installed <13>Apr 21 00:59:56 rpmi: ca-certificates-2016.02.25-alt1 1462368370 installed <13>Apr 21 00:59:56 rpmi: libcrypto10-1.0.2n-alt0.M80P.1 1512766129 installed <13>Apr 21 00:59:56 rpmi: librarian-0.8.1-alt6 1384178686 installed <13>Apr 21 00:59:56 rpmi: perl-XML-Parser-2.44-alt2 1456264144 installed <13>Apr 21 00:59:56 rpmi: desktop-file-utils-0.22.0.patchset1-alt1 1412210843 installed <13>Apr 21 00:59:56 rpmi: libgio-2.52.3-alt0.M80P.1 1504533271 installed <13>Apr 21 00:59:56 rpmi: libssl10-1.0.2n-alt0.M80P.1 1512766129 installed <13>Apr 21 00:59:56 rpmi: libdbus-glib-1:0.106-alt1 1454672851 installed <86>Apr 21 00:59:56 groupadd[19565]: group added to /etc/group: name=messagebus, GID=499 <86>Apr 21 00:59:56 groupadd[19565]: group added to /etc/gshadow: name=messagebus <86>Apr 21 00:59:56 groupadd[19565]: new group: name=messagebus, GID=499 <86>Apr 21 00:59:56 useradd[19607]: new user: name=messagebus, UID=499, GID=499, home=/run/dbus, shell=/dev/null <13>Apr 21 00:59:56 rpmi: dbus-1.10.24-alt4.M80P.1 1518773282 installed <86>Apr 21 00:59:56 groupadd[19748]: group added to /etc/group: name=_keytab, GID=498 <86>Apr 21 00:59:56 groupadd[19748]: group added to /etc/gshadow: name=_keytab <86>Apr 21 00:59:56 groupadd[19748]: new group: name=_keytab, GID=498 <13>Apr 21 00:59:56 rpmi: libkrb5-1.14.6-alt1.M80P.1 1525355673 installed <86>Apr 21 00:59:56 groupadd[20129]: group added to /etc/group: name=sasl, GID=497 <86>Apr 21 00:59:56 groupadd[20129]: group added to /etc/gshadow: name=sasl <86>Apr 21 00:59:56 groupadd[20129]: new group: name=sasl, GID=497 <13>Apr 21 00:59:56 rpmi: libsasl2-3-2.1.26-alt7 1479477445 installed <13>Apr 21 00:59:57 rpmi: libldap-2.4.45-alt1.M80P.1 1513980376 installed <13>Apr 21 00:59:57 rpmi: libGConf-3.2.6-alt3 1455932632 installed <13>Apr 21 00:59:57 rpmi: dbus-tools-gui-1.10.24-alt4.M80P.1 1518773282 installed <13>Apr 21 00:59:57 rpmi: gsettings-desktop-schemas-3.24.1-alt0.M80P.1 1504768052 installed <13>Apr 21 00:59:57 rpmi: libpolkit-0.113-alt2 1469643478 installed <13>Apr 21 00:59:57 rpmi: dbus-tools-1.10.24-alt4.M80P.1 1518773282 installed <13>Apr 21 00:59:57 rpmi: python-modules-compiler-2.7.11-alt6.M80P.1 1527682470 installed <13>Apr 21 00:59:57 rpmi: python-modules-email-2.7.11-alt6.M80P.1 1527682470 installed <13>Apr 21 00:59:57 rpmi: python-modules-unittest-2.7.11-alt6.M80P.1 1527682470 installed <13>Apr 21 00:59:57 rpmi: python-modules-2.7.11-alt6.M80P.1 1527682470 installed <13>Apr 21 00:59:57 rpmi: python-modules-xml-2.7.11-alt6.M80P.1 1527682470 installed <13>Apr 21 00:59:57 rpmi: python-modules-encodings-2.7.11-alt6.M80P.1 1527682470 installed <13>Apr 21 00:59:57 rpmi: python-modules-hotshot-2.7.11-alt6.M80P.1 1527682470 installed <13>Apr 21 00:59:57 rpmi: python-modules-bsddb-2.7.11-alt6.M80P.1 1527682470 installed <13>Apr 21 00:59:57 rpmi: python-modules-ctypes-2.7.11-alt6.M80P.1 1527682470 installed <13>Apr 21 00:59:57 rpmi: python-modules-multiprocessing-2.7.11-alt6.M80P.1 1527682470 installed <13>Apr 21 00:59:57 rpmi: python-modules-logging-2.7.11-alt6.M80P.1 1527682470 installed <13>Apr 21 00:59:57 rpmi: python-2.7.11-alt6.M80P.1 1527682470 installed <13>Apr 21 00:59:57 rpmi: python-dev-2.7.11-alt6.M80P.1 1527682470 installed <13>Apr 21 00:59:57 rpmi: glib2-devel-2.52.3-alt0.M80P.1 1504533271 installed <13>Apr 21 00:59:57 rpmi: GConf-3.2.6-alt3 1455932632 installed <13>Apr 21 00:59:57 rpmi: libGConf-devel-3.2.6-alt3 1455932632 installed Installing gnochm-0.9.11-alt1.2.qa1.1.src.rpm Building target platforms: x86_64 Building for target x86_64 Executing(%prep): /bin/sh -e /usr/src/tmp/rpm-tmp.62918 + 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). + sed -i 's|$(SHAREDMIME_TOOL)|true $(SHAREDMIME_TOOL)|' data/Makefile.in + exit 0 Executing(%build): /bin/sh -e /usr/src/tmp/rpm-tmp.62918 + umask 022 + /bin/mkdir -p /usr/src/RPM/BUILD + cd /usr/src/RPM/BUILD + cd gnochm-0.9.11 + CFLAGS='-pipe -Wall -g -O2' + export CFLAGS + CXXFLAGS='-pipe -Wall -g -O2' + export CXXFLAGS + FFLAGS='-pipe -Wall -g -O2' + export FFLAGS + '[' -n '' ']' ++ printf %s '-pipe -Wall -g -O2' ++ sed -r 's/(^|[[:space:]]+)-[^m][^[:space:]]*//g' + ASFLAGS= + export ASFLAGS + export lt_cv_deplibs_check_method=pass_all + lt_cv_deplibs_check_method=pass_all + readlink -e -- ./configure + xargs -ri find '{}' -type f '(' -name config.sub -or -name config.guess ')' -printf '%h/\n' + sort -u + xargs -rn1 install -pm755 -- /usr/share/gnu-config/config.sub /usr/share/gnu-config/config.guess + xargs -ri dirname -- '{}' + ./configure --build=x86_64-alt-linux --host=x86_64-alt-linux --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc --datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib64 --libexecdir=/usr/lib --localstatedir=/var/lib --sharedstatedir=/var/lib --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.7 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 x86_64-alt-linux-gcc... x86_64-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 x86_64-alt-linux-gcc accepts -g... yes checking for x86_64-alt-linux-gcc option to accept ANSI C... none needed checking dependency style of x86_64-alt-linux-gcc... none checking how to run the C preprocessor... x86_64-alt-linux-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.88886 + 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/lib64 libexecdir=/usr/src/tmp/gnochm-buildroot/usr/lib localstatedir=/usr/src/tmp/gnochm-buildroot/var/lib sharedstatedir=/usr/src/tmp/gnochm-buildroot/var/lib 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 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 killall: /proc lacks process entries (not mounted ?) 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 + sed -i '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 + rm -rf /usr/src/tmp/gnochm-buildroot/var/lib/scrollkeeper + desktop-file-install --dir /usr/src/tmp/gnochm-buildroot/usr/share/applications --remove-category=Utility --remove-category=Application --add-category=Office --add-category=Viewer /usr/src/tmp/gnochm-buildroot/usr/share/applications/gnochm.desktop /usr/src/tmp/gnochm-buildroot/usr/share/applications/gnochm.desktop: error: (will be fatal in the future): value "gnochm.png" for key "Icon" in group "Desktop Entry" is an icon name with an extension, but there should be no extension as described in the Icon Theme Specification if the value is not an absolute path + /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,desktop) /usr/share/applications/gnochm.desktop: performed minor cleanup: 2d1 < Encoding=UTF-8 23c22 < Icon=gnochm.png --- > Icon=gnochm 28c27 < MimeType=application/x-chm --- > MimeType=application/x-chm; Compressing files in /usr/src/tmp/gnochm-buildroot (auto) Verifying ELF objects in /usr/src/tmp/gnochm-buildroot (arch=normal,fhs=normal,lfs=relaxed,lint=relaxed,rpath=normal,stack=normal,textrel=normal,unresolved=normal) 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' Hardlinking identical .pyc and .pyo files Processing files: gnochm-0.9.11-alt1.2.qa1.1 Executing(%doc): /bin/sh -e /usr/src/tmp/rpm-tmp.59931 + 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: /bin/sh -e /usr/src/tmp/rpm-tmp.OvmyUu find-provides: running scripts (alternatives,debuginfo,gir,lib,pam,perl,pkgconfig,python,shell,typelib) Finding Requires (using /usr/lib/rpm/find-requires) Executing: /bin/sh -e /usr/src/tmp/rpm-tmp.yLiJUf find-requires: running scripts (cpp,debuginfo,files,gir-js,gir-python,gir,lib,pam,perl,pkgconfig,pkgconfiglib,python,rpmlib,shebang,shell,static,symlinks,typelib) python.req: /usr/src/tmp/gnochm-buildroot/usr/bin/gnochm.py: skipping sys python.req: /usr/src/tmp/gnochm-buildroot/usr/bin/gnochm: skipping sys find-requires: FINDPACKAGE-COMMANDS: python Finding Requires(post) (using /usr/lib/rpm/find-scriptlet-requires) Executing: /bin/sh -e /usr/src/tmp/rpm-tmp.buK595 Finding Requires(preun) (using /usr/lib/rpm/find-scriptlet-requires) Executing: /bin/sh -e /usr/src/tmp/rpm-tmp.cT5q9Y PreReq: python = 2.7 Requires: python2.7(libglade), python2.7(bonobo), /usr/bin/env, python-base, python-modules, python2.7(chm), python2.7(gconf), python2.7(gnome), python2.7(gobject), python2.7(gtk), python2.7(gtkhtml2), python2.7(mimetypes) Requires(interp): /bin/sh, /bin/sh Requires(post): GConf2, scrollkeeper, desktop-file-utils, /bin/sh, /usr/sbin/gconf_install_schema Requires(preun): /bin/sh, /usr/sbin/gconf_uninstall_schema Requires(postun): scrollkeeper, desktop-file-utils Wrote: /usr/src/RPM/RPMS/noarch/gnochm-0.9.11-alt1.2.qa1.1.noarch.rpm 4.12user 2.76system 0:10.81elapsed 63%CPU (0avgtext+0avgdata 30368maxresident)k 0inputs+0outputs (0major+494450minor)pagefaults 0swaps 11.32user 7.59system 0:22.53elapsed 83%CPU (0avgtext+0avgdata 122108maxresident)k 1832inputs+0outputs (0major+763377minor)pagefaults 0swaps --- gnochm-0.9.11-alt1.2.qa1.1.noarch.rpm.repo 2011-11-22 03:37:22.000000000 +0000 +++ gnochm-0.9.11-alt1.2.qa1.1.noarch.rpm.hasher 2019-04-21 01:00:11.134663525 +0000 @@ -53,9 +53,6 @@ Requires: /usr/bin/env -Requires: /usr/bin/python -Requires: python2.7(ConfigParser) +Requires: python-base +Requires: python-modules Requires: python2.7(chm) -Requires: python2.7(codecs) Requires: python2.7(gconf) -Requires: python2.7(getopt) -Requires: python2.7(gettext) Requires: python2.7(gnome) @@ -64,13 +61,3 @@ Requires: python2.7(gtkhtml2) -Requires: python2.7(htmlentitydefs) -Requires: python2.7(locale) Requires: python2.7(mimetypes) -Requires: python2.7(os) -Requires: python2.7(pickle) -Requires: python2.7(re) -Requires: python2.7(sgmllib) -Requires: python2.7(string) -Requires: python2.7(urllib) -Requires: python2.7(urlparse) -Requires: python2.7(webbrowser) Requires: /usr/sbin/gconf_install_schema