starting phase `set-SOURCE-DATE-EPOCH' phase `set-SOURCE-DATE-EPOCH' succeeded after 0.0 seconds starting phase `set-paths' environment variable `PATH' set to `/gnu/store/7sa6phqdsirzj29n59mrzjr363a837b8-glib-2.70.2-bin/bin:/gnu/store/jr3sfjid7nv7bqbddwir31a6chddmady-intltool-0.51.0/bin:/gnu/store/3nw1jhybwdbbsx8v821bm71h205462wz-pkg-config-0.29.2/bin:/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/bin:/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/bin:/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/bin:/gnu/store/99c25918hl9pihix8hparmc96q6zrpwy-tar-1.34/bin:/gnu/store/l0yga4lrwwf74rz7fb0dadglg27ajpsx-gzip-1.10/bin:/gnu/store/ihakfb51zdgjz3v9nkj0ja9zk9ng8xzl-bzip2-1.0.8/bin:/gnu/store/fk24dx8qz1b5smnc4ljfw25xn7yjps0q-xz-5.2.5/bin:/gnu/store/vl1b3nq6gijpzbl03zq92m5dwgs17nik-file-5.39/bin:/gnu/store/h0rx6y95zin61fp5wlyjly4g9j2hma18-diffutils-3.8/bin:/gnu/store/7j8j7m0kgb7kv2fc18qvrdj7gs3jc4mx-patch-2.7.6/bin:/gnu/store/x4yglk9pn2s2ixl1b4lj151bd2yvlgww-findutils-4.8.0/bin:/gnu/store/vzq0il5z2d6ksllb525m9xaqzv829g3k-gawk-5.1.0/bin:/gnu/store/cnwr7widbi6470kfyb13krx46kz5anmy-sed-4.8/bin:/gnu/store/bx47clwnxn51m7jdwfimz4lw2fh8g21v-grep-3.6/bin:/gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin:/gnu/store/dhx00nrv9r52f6xivg0xa4iihpl9awyk-make-4.3/bin:/gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin:/gnu/store/4bzvr16pyax9224v9r72rqxswj9931sb-ld-wrapper-0/bin:/gnu/store/v4a7zw8w52v64kw5781ypa8gjwd098jz-binutils-2.37/bin:/gnu/store/v5xfd4vy1lvqikdl1rzs8aklgsnqwd26-gcc-10.3.0/bin:/gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/bin:/gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/sbin:/gnu/store/zn45z8pv5dkh98hi9l1q9aldbplga3m7-perl-5.34.0/bin:/gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin:/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/bin:/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/bin' environment variable `XDG_DATA_DIRS' set to `/gnu/store/jr3sfjid7nv7bqbddwir31a6chddmady-intltool-0.51.0/share:/gnu/store/3nw1jhybwdbbsx8v821bm71h205462wz-pkg-config-0.29.2/share:/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/share:/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/share:/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/share:/gnu/store/irqwih8nanv13mz8rjcg24s607lp1hcf-gnome-mime-data-2.18.0/share:/gnu/store/hj5g5b4xd94z9fbpazss2xh99161f9gs-zlib-1.2.11/share:/gnu/store/99c25918hl9pihix8hparmc96q6zrpwy-tar-1.34/share:/gnu/store/l0yga4lrwwf74rz7fb0dadglg27ajpsx-gzip-1.10/share:/gnu/store/ihakfb51zdgjz3v9nkj0ja9zk9ng8xzl-bzip2-1.0.8/share:/gnu/store/fk24dx8qz1b5smnc4ljfw25xn7yjps0q-xz-5.2.5/share:/gnu/store/vl1b3nq6gijpzbl03zq92m5dwgs17nik-file-5.39/share:/gnu/store/h0rx6y95zin61fp5wlyjly4g9j2hma18-diffutils-3.8/share:/gnu/store/7j8j7m0kgb7kv2fc18qvrdj7gs3jc4mx-patch-2.7.6/share:/gnu/store/x4yglk9pn2s2ixl1b4lj151bd2yvlgww-findutils-4.8.0/share:/gnu/store/vzq0il5z2d6ksllb525m9xaqzv829g3k-gawk-5.1.0/share:/gnu/store/cnwr7widbi6470kfyb13krx46kz5anmy-sed-4.8/share:/gnu/store/bx47clwnxn51m7jdwfimz4lw2fh8g21v-grep-3.6/share:/gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/share:/gnu/store/dhx00nrv9r52f6xivg0xa4iihpl9awyk-make-4.3/share:/gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/share:/gnu/store/v4a7zw8w52v64kw5781ypa8gjwd098jz-binutils-2.37/share:/gnu/store/v5xfd4vy1lvqikdl1rzs8aklgsnqwd26-gcc-10.3.0/share:/gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/share:/gnu/store/1s4k8h3h1ka9za4yzg0dfjnlhab5k14p-glibc-2.33-static/share:/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/share:/gnu/store/zb6b8f4h7a7q564vwfiavf1462bmqsiv-pcre-8.45/share:/gnu/store/k5vd7gxqp0irkwikgsj4z56psyrhp4d1-libffi-3.3/share:/gnu/store/zn45z8pv5dkh98hi9l1q9aldbplga3m7-perl-5.34.0/share:/gnu/store/b5zr535ypxjdqbl9xz17cf482ywfmp37-perl-xml-parser-2.46/share:/gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/share:/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/share:/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/share:/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/share:/gnu/store/wsx4kz1gh6cpdhx393frhqknmswbggq8-linux-libre-headers-5.10.35/share' environment variable `GIO_EXTRA_MODULES' set to `/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib/gio/modules' environment variable `PKG_CONFIG_PATH' set to `/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib/pkgconfig:/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib/pkgconfig:/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib/pkgconfig:/gnu/store/irqwih8nanv13mz8rjcg24s607lp1hcf-gnome-mime-data-2.18.0/share/pkgconfig:/gnu/store/hj5g5b4xd94z9fbpazss2xh99161f9gs-zlib-1.2.11/lib/pkgconfig:/gnu/store/fk24dx8qz1b5smnc4ljfw25xn7yjps0q-xz-5.2.5/lib/pkgconfig:/gnu/store/vl1b3nq6gijpzbl03zq92m5dwgs17nik-file-5.39/lib/pkgconfig:/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/lib/pkgconfig:/gnu/store/zb6b8f4h7a7q564vwfiavf1462bmqsiv-pcre-8.45/lib/pkgconfig:/gnu/store/k5vd7gxqp0irkwikgsj4z56psyrhp4d1-libffi-3.3/lib/pkgconfig:/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/pkgconfig:/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/pkgconfig:/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib/pkgconfig' find-files: /gnu/store/7sa6phqdsirzj29n59mrzjr363a837b8-glib-2.70.2-bin/xml: No such file or directory find-files: /gnu/store/jr3sfjid7nv7bqbddwir31a6chddmady-intltool-0.51.0/xml: No such file or directory find-files: /gnu/store/3nw1jhybwdbbsx8v821bm71h205462wz-pkg-config-0.29.2/xml: No such file or directory find-files: /gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/xml: No such file or directory find-files: /gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/xml: No such file or directory find-files: /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/xml: No such file or directory find-files: /gnu/store/irqwih8nanv13mz8rjcg24s607lp1hcf-gnome-mime-data-2.18.0/xml: No such file or directory find-files: /gnu/store/hj5g5b4xd94z9fbpazss2xh99161f9gs-zlib-1.2.11/xml: No such file or directory find-files: /gnu/store/99c25918hl9pihix8hparmc96q6zrpwy-tar-1.34/xml: No such file or directory find-files: /gnu/store/l0yga4lrwwf74rz7fb0dadglg27ajpsx-gzip-1.10/xml: No such file or directory find-files: /gnu/store/ihakfb51zdgjz3v9nkj0ja9zk9ng8xzl-bzip2-1.0.8/xml: No such file or directory find-files: /gnu/store/fk24dx8qz1b5smnc4ljfw25xn7yjps0q-xz-5.2.5/xml: No such file or directory find-files: /gnu/store/vl1b3nq6gijpzbl03zq92m5dwgs17nik-file-5.39/xml: No such file or directory find-files: /gnu/store/h0rx6y95zin61fp5wlyjly4g9j2hma18-diffutils-3.8/xml: No such file or directory find-files: /gnu/store/7j8j7m0kgb7kv2fc18qvrdj7gs3jc4mx-patch-2.7.6/xml: No such file or directory find-files: /gnu/store/x4yglk9pn2s2ixl1b4lj151bd2yvlgww-findutils-4.8.0/xml: No such file or directory find-files: /gnu/store/vzq0il5z2d6ksllb525m9xaqzv829g3k-gawk-5.1.0/xml: No such file or directory find-files: /gnu/store/cnwr7widbi6470kfyb13krx46kz5anmy-sed-4.8/xml: No such file or directory find-files: /gnu/store/bx47clwnxn51m7jdwfimz4lw2fh8g21v-grep-3.6/xml: No such file or directory find-files: /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/xml: No such file or directory find-files: /gnu/store/dhx00nrv9r52f6xivg0xa4iihpl9awyk-make-4.3/xml: No such file or directory find-files: /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/xml: No such file or directory find-files: /gnu/store/4bzvr16pyax9224v9r72rqxswj9931sb-ld-wrapper-0/xml: No such file or directory find-files: /gnu/store/v4a7zw8w52v64kw5781ypa8gjwd098jz-binutils-2.37/xml: No such file or directory find-files: /gnu/store/v5xfd4vy1lvqikdl1rzs8aklgsnqwd26-gcc-10.3.0/xml: No such file or directory find-files: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/xml: No such file or directory find-files: /gnu/store/1s4k8h3h1ka9za4yzg0dfjnlhab5k14p-glibc-2.33-static/xml: No such file or directory find-files: /gnu/store/6p5m4cv8psfzy5xn5yhvhmjl261wg34m-glibc-utf8-locales-2.33/xml: No such file or directory find-files: /gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/xml: No such file or directory find-files: /gnu/store/zb6b8f4h7a7q564vwfiavf1462bmqsiv-pcre-8.45/xml: No such file or directory find-files: /gnu/store/k5vd7gxqp0irkwikgsj4z56psyrhp4d1-libffi-3.3/xml: No such file or directory find-files: /gnu/store/zn45z8pv5dkh98hi9l1q9aldbplga3m7-perl-5.34.0/xml: No such file or directory find-files: /gnu/store/b5zr535ypxjdqbl9xz17cf482ywfmp37-perl-xml-parser-2.46/xml: No such file or directory find-files: /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/xml: No such file or directory find-files: /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/xml: No such file or directory find-files: /gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/xml: No such file or directory find-files: /gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/xml: No such file or directory find-files: /gnu/store/wsx4kz1gh6cpdhx393frhqknmswbggq8-linux-libre-headers-5.10.35/xml: No such file or directory environment variable `XML_CATALOG_FILES' unset environment variable `BASH_LOADABLES_PATH' unset environment variable `C_INCLUDE_PATH' set to `/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include:/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include:/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include:/gnu/store/hj5g5b4xd94z9fbpazss2xh99161f9gs-zlib-1.2.11/include:/gnu/store/ihakfb51zdgjz3v9nkj0ja9zk9ng8xzl-bzip2-1.0.8/include:/gnu/store/fk24dx8qz1b5smnc4ljfw25xn7yjps0q-xz-5.2.5/include:/gnu/store/vl1b3nq6gijpzbl03zq92m5dwgs17nik-file-5.39/include:/gnu/store/vzq0il5z2d6ksllb525m9xaqzv829g3k-gawk-5.1.0/include:/gnu/store/dhx00nrv9r52f6xivg0xa4iihpl9awyk-make-4.3/include:/gnu/store/v4a7zw8w52v64kw5781ypa8gjwd098jz-binutils-2.37/include:/gnu/store/v5xfd4vy1lvqikdl1rzs8aklgsnqwd26-gcc-10.3.0/include:/gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include:/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include:/gnu/store/zb6b8f4h7a7q564vwfiavf1462bmqsiv-pcre-8.45/include:/gnu/store/k5vd7gxqp0irkwikgsj4z56psyrhp4d1-libffi-3.3/include:/gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/include:/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include:/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include:/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include:/gnu/store/wsx4kz1gh6cpdhx393frhqknmswbggq8-linux-libre-headers-5.10.35/include' environment variable `CPLUS_INCLUDE_PATH' set to `/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include:/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include:/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include:/gnu/store/hj5g5b4xd94z9fbpazss2xh99161f9gs-zlib-1.2.11/include:/gnu/store/ihakfb51zdgjz3v9nkj0ja9zk9ng8xzl-bzip2-1.0.8/include:/gnu/store/fk24dx8qz1b5smnc4ljfw25xn7yjps0q-xz-5.2.5/include:/gnu/store/vl1b3nq6gijpzbl03zq92m5dwgs17nik-file-5.39/include:/gnu/store/vzq0il5z2d6ksllb525m9xaqzv829g3k-gawk-5.1.0/include:/gnu/store/dhx00nrv9r52f6xivg0xa4iihpl9awyk-make-4.3/include:/gnu/store/v4a7zw8w52v64kw5781ypa8gjwd098jz-binutils-2.37/include:/gnu/store/v5xfd4vy1lvqikdl1rzs8aklgsnqwd26-gcc-10.3.0/include/c++:/gnu/store/v5xfd4vy1lvqikdl1rzs8aklgsnqwd26-gcc-10.3.0/include:/gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include:/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include:/gnu/store/zb6b8f4h7a7q564vwfiavf1462bmqsiv-pcre-8.45/include:/gnu/store/k5vd7gxqp0irkwikgsj4z56psyrhp4d1-libffi-3.3/include:/gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/include:/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include:/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include:/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include:/gnu/store/wsx4kz1gh6cpdhx393frhqknmswbggq8-linux-libre-headers-5.10.35/include' environment variable `LIBRARY_PATH' set to `/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib:/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib:/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib:/gnu/store/hj5g5b4xd94z9fbpazss2xh99161f9gs-zlib-1.2.11/lib:/gnu/store/ihakfb51zdgjz3v9nkj0ja9zk9ng8xzl-bzip2-1.0.8/lib:/gnu/store/fk24dx8qz1b5smnc4ljfw25xn7yjps0q-xz-5.2.5/lib:/gnu/store/vl1b3nq6gijpzbl03zq92m5dwgs17nik-file-5.39/lib:/gnu/store/vzq0il5z2d6ksllb525m9xaqzv829g3k-gawk-5.1.0/lib:/gnu/store/v4a7zw8w52v64kw5781ypa8gjwd098jz-binutils-2.37/lib:/gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/lib:/gnu/store/1s4k8h3h1ka9za4yzg0dfjnlhab5k14p-glibc-2.33-static/lib:/gnu/store/6p5m4cv8psfzy5xn5yhvhmjl261wg34m-glibc-utf8-locales-2.33/lib:/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/lib:/gnu/store/zb6b8f4h7a7q564vwfiavf1462bmqsiv-pcre-8.45/lib:/gnu/store/k5vd7gxqp0irkwikgsj4z56psyrhp4d1-libffi-3.3/lib:/gnu/store/zn45z8pv5dkh98hi9l1q9aldbplga3m7-perl-5.34.0/lib:/gnu/store/b5zr535ypxjdqbl9xz17cf482ywfmp37-perl-xml-parser-2.46/lib:/gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/lib:/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib:/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib:/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib' environment variable `GUIX_LOCPATH' set to `/gnu/store/6p5m4cv8psfzy5xn5yhvhmjl261wg34m-glibc-utf8-locales-2.33/lib/locale' environment variable `PERL5LIB' set to `/gnu/store/zn45z8pv5dkh98hi9l1q9aldbplga3m7-perl-5.34.0/lib/perl5/site_perl:/gnu/store/b5zr535ypxjdqbl9xz17cf482ywfmp37-perl-xml-parser-2.46/lib/perl5/site_perl' phase `set-paths' succeeded after 0.0 seconds starting phase `install-locale' using 'en_US.utf8' locale for category "LC_ALL" phase `install-locale' succeeded after 0.0 seconds starting phase `unpack' gnome-vfs-2.24.4/ gnome-vfs-2.24.4/gnome-vfs-2.0.pc.in gnome-vfs-2.24.4/configure.in gnome-vfs-2.24.4/test/ gnome-vfs-2.24.4/test/auto-test gnome-vfs-2.24.4/test/test-mime-handlers-set.c gnome-vfs-2.24.4/test/Makefile.am gnome-vfs-2.24.4/test/test-mime-handlers.c gnome-vfs-2.24.4/test/test-unlink.c gnome-vfs-2.24.4/test/test-xfer.c gnome-vfs-2.24.4/test/Makefile.in gnome-vfs-2.24.4/test/vfs-run.in gnome-vfs-2.24.4/test/test-channel.c gnome-vfs-2.24.4/test/test-async-cancel.c gnome-vfs-2.24.4/test/test-uri.c gnome-vfs-2.24.4/test/test-async.c gnome-vfs-2.24.4/test/test-queue.c gnome-vfs-2.24.4/test/test-mime-info-cache.c gnome-vfs-2.24.4/test/test-callback.c gnome-vfs-2.24.4/test/test-address.c gnome-vfs-2.24.4/test/test-ssl.c gnome-vfs-2.24.4/test/test-directory.c gnome-vfs-2.24.4/test/test-mime.c gnome-vfs-2.24.4/test/test-shell.c gnome-vfs-2.24.4/test/test-dns-sd.c gnome-vfs-2.24.4/test/test-symlinks.c gnome-vfs-2.24.4/test/test-parse-ls-lga.c gnome-vfs-2.24.4/test/test-seek.c gnome-vfs-2.24.4/test/test-escape.c gnome-vfs-2.24.4/test/test-async-directory.c gnome-vfs-2.24.4/test/test-directory-visit.c gnome-vfs-2.24.4/test/test-info.c gnome-vfs-2.24.4/test/test-dirop.c gnome-vfs-2.24.4/test/test-acl.c gnome-vfs-2.24.4/test/test-find-directory.c gnome-vfs-2.24.4/test/test-sync-write.c gnome-vfs-2.24.4/test/test.input gnome-vfs-2.24.4/test/test-sync-create.c gnome-vfs-2.24.4/test/test-sync.c gnome-vfs-2.24.4/test/test.cmds gnome-vfs-2.24.4/test/test-module-selftest.c gnome-vfs-2.24.4/test/test-performance.c gnome-vfs-2.24.4/test/test-monitor.c gnome-vfs-2.24.4/test/test-volumes.c gnome-vfs-2.24.4/test/test-long-cancel.c gnome-vfs-2.24.4/test/test.output gnome-vfs-2.24.4/Makefile.am gnome-vfs-2.24.4/install-sh gnome-vfs-2.24.4/missing gnome-vfs-2.24.4/Makefile.in gnome-vfs-2.24.4/configure gnome-vfs-2.24.4/gnome-vfs.spec.in gnome-vfs-2.24.4/AUTHORS gnome-vfs-2.24.4/modules/ gnome-vfs-2.24.4/modules/sftp-method.c gnome-vfs-2.24.4/modules/ftp-method.c gnome-vfs-2.24.4/modules/network-method.c gnome-vfs-2.24.4/modules/cdda-cddb.h gnome-vfs-2.24.4/modules/Makefile.am gnome-vfs-2.24.4/modules/http-proxy.h gnome-vfs-2.24.4/modules/gzip-method.c gnome-vfs-2.24.4/modules/Makefile.in gnome-vfs-2.24.4/modules/inotify-missing.c gnome-vfs-2.24.4/modules/cdda-module.conf gnome-vfs-2.24.4/modules/dns-sd-method.c gnome-vfs-2.24.4/modules/nntp-method.c gnome-vfs-2.24.4/modules/inotify-path.c gnome-vfs-2.24.4/modules/http-proxy.c gnome-vfs-2.24.4/modules/inotify-path.h gnome-vfs-2.24.4/modules/sftp.h gnome-vfs-2.24.4/modules/inotify-diag.c gnome-vfs-2.24.4/modules/http-neon-method.c gnome-vfs-2.24.4/modules/cdda-cdrom-extensions.h gnome-vfs-2.24.4/modules/fstype.c gnome-vfs-2.24.4/modules/inotify-diag.h gnome-vfs-2.24.4/modules/file-method.c gnome-vfs-2.24.4/modules/tar-method.c gnome-vfs-2.24.4/modules/ssl-modules.conf gnome-vfs-2.24.4/modules/smb-method.c gnome-vfs-2.24.4/modules/file-method-acl.c gnome-vfs-2.24.4/modules/inotify-missing.h gnome-vfs-2.24.4/modules/computer-method.c gnome-vfs-2.24.4/modules/default-modules.conf gnome-vfs-2.24.4/modules/inotify-kernel.c gnome-vfs-2.24.4/modules/inotify-kernel.h gnome-vfs-2.24.4/modules/inotify-sub.h gnome-vfs-2.24.4/modules/nntp-method.h gnome-vfs-2.24.4/modules/smb-module.conf gnome-vfs-2.24.4/modules/inotify-helper.h gnome-vfs-2.24.4/modules/cdda-method.c gnome-vfs-2.24.4/modules/tarpet.h gnome-vfs-2.24.4/modules/cdda-cddb.c gnome-vfs-2.24.4/modules/inotify-sub.c gnome-vfs-2.24.4/modules/bzip2-method.c gnome-vfs-2.24.4/modules/test-method.c gnome-vfs-2.24.4/modules/file-method-acl.h gnome-vfs-2.24.4/modules/inotify-helper.c gnome-vfs-2.24.4/devel-docs/ gnome-vfs-2.24.4/devel-docs/Makefile.am gnome-vfs-2.24.4/devel-docs/Makefile.in gnome-vfs-2.24.4/devel-docs/gnome-vfs-tutorial/ gnome-vfs-2.24.4/devel-docs/gnome-vfs-tutorial/Makefile.am gnome-vfs-2.24.4/devel-docs/gnome-vfs-tutorial/Makefile.in gnome-vfs-2.24.4/devel-docs/gnome-vfs-tutorial/gnome-vfs-tutorial.sgml gnome-vfs-2.24.4/gnome-vfs-zip.in gnome-vfs-2.24.4/gnome-vfs-module-2.0.pc.in gnome-vfs-2.24.4/doc/ gnome-vfs-2.24.4/doc/gnome-vfs-2.0.types gnome-vfs-2.24.4/doc/gnome-vfs-2.0-docs.sgml gnome-vfs-2.24.4/doc/Makefile.am gnome-vfs-2.24.4/doc/writing-modules.sgml gnome-vfs-2.24.4/doc/Makefile.in gnome-vfs-2.24.4/doc/about.sgml gnome-vfs-2.24.4/doc/html/ gnome-vfs-2.24.4/doc/html/gnome-vfs-2.0-gnome-vfs-file-info-ops.html gnome-vfs-2.24.4/doc/html/gnome-vfs-2.0-gnome-vfs-cancellation.html gnome-vfs-2.24.4/doc/html/gnome-vfs-2.0-gnome-vfs-monitor.html gnome-vfs-2.24.4/doc/html/up.png gnome-vfs-2.24.4/doc/html/gnome-vfs-2.0-gnome-vfs-mime-database-deprecated.html gnome-vfs-2.24.4/doc/html/gnome-vfs-2.0-gnome-vfs-file-rw-ops.html gnome-vfs-2.24.4/doc/html/left.png gnome-vfs-2.24.4/doc/html/gnome-vfs-2.0-gnome-vfs-utils.html gnome-vfs-2.24.4/doc/html/gnome-vfs-2.0-gnome-vfs-module.html gnome-vfs-2.24.4/doc/html/gnome-vfs-2.0-gnome-vfs-mime-monitor.html gnome-vfs-2.24.4/doc/html/gnome-vfs-2.0-gnome-vfs-directory-find-ops.html gnome-vfs-2.24.4/doc/html/gnome-vfs-directory-ops.html gnome-vfs-2.24.4/doc/html/gnome-vfs-2.0-gnome-vfs-mime-database.html gnome-vfs-2.24.4/doc/html/gnome-vfs-2.0-gnome-vfs-dns-sd.html gnome-vfs-2.24.4/doc/html/gnome-vfs-2.0-gnome-vfs-transform.html gnome-vfs-2.24.4/doc/html/gnome-vfs-2.0-gnome-vfs-file-advanced-ops.html gnome-vfs-2.24.4/doc/html/gnome-vfs-2.0-gnome-vfs-result.html gnome-vfs-2.24.4/doc/html/about.html gnome-vfs-2.24.4/doc/html/gnome-vfs-2.0-gnome-vfs-module-callback-module-api.html gnome-vfs-2.24.4/doc/html/data-types.html gnome-vfs-2.24.4/doc/html/gnome-vfs-2.0-gnome-vfs-async-ops.html gnome-vfs-2.24.4/doc/html/gnome-vfs-first-steps.html gnome-vfs-2.24.4/doc/html/gnome-vfs-2.0-gnome-vfs-socket.html gnome-vfs-2.24.4/doc/html/gnome-vfs-2.0-gnome-vfs-inet-connection.html gnome-vfs-2.24.4/doc/html/gnome-vfs-2.0-gnome-vfs-drive.html gnome-vfs-2.24.4/doc/html/gnome-vfs-2.0-gnome-vfs-file-size.html gnome-vfs-2.24.4/doc/html/gnome-vfs-2.0-gnome-vfs-file-trunc-ops.html gnome-vfs-2.24.4/doc/html/gnome-vfs-2.0-gnome-vfs-xfer.html gnome-vfs-2.24.4/doc/html/volumes.html gnome-vfs-2.24.4/doc/html/gnome-vfs-file-and-dirs-ops.html gnome-vfs-2.24.4/doc/html/gnome-vfs-2.0.devhelp2 gnome-vfs-2.24.4/doc/html/gnome-vfs-2.0-gnome-vfs-context.html gnome-vfs-2.24.4/doc/html/mime-registry.html gnome-vfs-2.24.4/doc/html/gnome-vfs-2.0-gnome-vfs-application-registry.html gnome-vfs-2.24.4/doc/html/style.css gnome-vfs-2.24.4/doc/html/home.png gnome-vfs-2.24.4/doc/html/gnome-vfs-2.0-gnome-vfs-standard-callbacks.html gnome-vfs-2.24.4/doc/html/gnome-vfs-2.0-gnome-vfs-module-callback.html gnome-vfs-2.24.4/doc/html/gnome-vfs-2.0-gnome-vfs-volume-monitor.html gnome-vfs-2.24.4/doc/html/gnome-vfs-2.0.devhelp gnome-vfs-2.24.4/doc/html/gnome-vfs-2.0-gnome-vfs-module-shared.html gnome-vfs-2.24.4/doc/html/gnome-vfs-file-async-ops.html gnome-vfs-2.24.4/doc/html/gnome-vfs-2.0-gnome-vfs-parse-ls.html gnome-vfs-2.24.4/doc/html/gnome-vfs-2.0-gnome-vfs-uri.html gnome-vfs-2.24.4/doc/html/gnome-vfs-2.0-gnome-vfs-ssl.html gnome-vfs-2.24.4/doc/html/gnome-vfs-2.0-gnome-vfs-file-info.html gnome-vfs-2.24.4/doc/html/gnome-vfs-2.0-gnome-vfs-file-basic-ops.html gnome-vfs-2.24.4/doc/html/gnome-vfs-2.0-gnome-vfs-directory-list-ops.html gnome-vfs-2.24.4/doc/html/gnome-vfs-2.0-gnome-vfs-init.html gnome-vfs-2.24.4/doc/html/gnome-vfs-2.0-gnome-vfs-mime.html gnome-vfs-2.24.4/doc/html/gnome-vfs-basic-file-ops.html gnome-vfs-2.24.4/doc/html/gnome-vfs-2.0-gnome-vfs-socket-buffer.html gnome-vfs-2.24.4/doc/html/gnome-vfs-2.0-gnome-vfs-mime-utils.html gnome-vfs-2.24.4/doc/html/gnome-vfs-2.0-gnome-vfs-resolve.html gnome-vfs-2.24.4/doc/html/gnome-vfs-writing-modules.html gnome-vfs-2.24.4/doc/html/index.sgml gnome-vfs-2.24.4/doc/html/modules.html gnome-vfs-2.24.4/doc/html/gnome-vfs-2.0-gnome-vfs-directory-basic-ops.html gnome-vfs-2.24.4/doc/html/networking.html gnome-vfs-2.24.4/doc/html/right.png gnome-vfs-2.24.4/doc/html/gnome-vfs-2.0-gnome-vfs-method.html gnome-vfs-2.24.4/doc/html/index.html gnome-vfs-2.24.4/doc/html/gnome-vfs-2.0-gnome-vfs-volume.html gnome-vfs-2.24.4/doc/tmpl/ gnome-vfs-2.24.4/doc/tmpl/gnome-vfs-file-info-ops.sgml gnome-vfs-2.24.4/doc/tmpl/gnome-vfs-module-callback.sgml gnome-vfs-2.24.4/doc/tmpl/gnome-vfs-resolve.sgml gnome-vfs-2.24.4/doc/tmpl/gnome-vfs-utils.sgml gnome-vfs-2.24.4/doc/tmpl/gnome-vfs-uri.sgml gnome-vfs-2.24.4/doc/tmpl/gnome-vfs-module-callback-module-api.sgml gnome-vfs-2.24.4/doc/tmpl/gnome-vfs-mime.sgml gnome-vfs-2.24.4/doc/tmpl/gnome-vfs-standard-callbacks.sgml gnome-vfs-2.24.4/doc/tmpl/gnome-vfs-mime-database.sgml gnome-vfs-2.24.4/doc/tmpl/gnome-vfs-mime-database-deprecated.sgml gnome-vfs-2.24.4/doc/tmpl/gnome-vfs-parse-ls.sgml gnome-vfs-2.24.4/doc/tmpl/gnome-vfs-async-ops.sgml gnome-vfs-2.24.4/doc/tmpl/gnome-vfs-context.sgml gnome-vfs-2.24.4/doc/tmpl/gnome-vfs-module.sgml gnome-vfs-2.24.4/doc/tmpl/gnome-vfs-file-rw-ops.sgml gnome-vfs-2.24.4/doc/tmpl/gnome-vfs-ops.sgml gnome-vfs-2.24.4/doc/tmpl/gnome-vfs-volume-monitor.sgml gnome-vfs-2.24.4/doc/tmpl/gnome-vfs-xfer.sgml gnome-vfs-2.24.4/doc/tmpl/gnome-vfs-cancellation.sgml gnome-vfs-2.24.4/doc/tmpl/gnome-vfs-inet-connection.sgml gnome-vfs-2.24.4/doc/tmpl/gnome-vfs-module-shared.sgml gnome-vfs-2.24.4/doc/tmpl/gnome-vfs-metadata.sgml gnome-vfs-2.24.4/doc/tmpl/gnome-vfs-2.0-unused.sgml gnome-vfs-2.24.4/doc/tmpl/gnome-vfs-monitor.sgml gnome-vfs-2.24.4/doc/tmpl/gnome-vfs-file-size.sgml gnome-vfs-2.24.4/doc/tmpl/gnome-vfs-directory-find-ops.sgml gnome-vfs-2.24.4/doc/tmpl/gnome-vfs-find-directory.sgml gnome-vfs-2.24.4/doc/tmpl/gnome-vfs-application-registry.sgml gnome-vfs-2.24.4/doc/tmpl/gnome-vfs-directory-list-ops.sgml gnome-vfs-2.24.4/doc/tmpl/gnome-vfs-result.sgml gnome-vfs-2.24.4/doc/tmpl/gnome-vfs-socket-buffer.sgml gnome-vfs-2.24.4/doc/tmpl/gnome-vfs-ssl.sgml gnome-vfs-2.24.4/doc/tmpl/gnome-vfs-volume.sgml gnome-vfs-2.24.4/doc/tmpl/gnome-vfs-file-basic-ops.sgml gnome-vfs-2.24.4/doc/tmpl/gnome-vfs-mime-utils.sgml gnome-vfs-2.24.4/doc/tmpl/gnome-vfs-drive.sgml gnome-vfs-2.24.4/doc/tmpl/gnome-vfs-mime-monitor.sgml gnome-vfs-2.24.4/doc/tmpl/gnome-vfs-transform.sgml gnome-vfs-2.24.4/doc/tmpl/gnome-vfs-directory-basic-ops.sgml gnome-vfs-2.24.4/doc/tmpl/gnome-vfs-init.sgml gnome-vfs-2.24.4/doc/tmpl/gnome-vfs-socket.sgml gnome-vfs-2.24.4/doc/tmpl/gnome-vfs-file-info.sgml gnome-vfs-2.24.4/doc/tmpl/gnome-vfs-directory.sgml gnome-vfs-2.24.4/doc/tmpl/gnome-vfs-dns-sd.sgml gnome-vfs-2.24.4/doc/tmpl/gnome-vfs-file-trunc-ops.sgml gnome-vfs-2.24.4/doc/tmpl/gnome-vfs-file-advanced-ops.sgml gnome-vfs-2.24.4/doc/tmpl/gnome-vfs-method.sgml gnome-vfs-2.24.4/doc/gnome-vfs-2.0-sections.txt gnome-vfs-2.24.4/doc/gnome-vfs-2.0-overrides.txt gnome-vfs-2.24.4/doc/version.xml gnome-vfs-2.24.4/doc/version.xml.in gnome-vfs-2.24.4/gnome-vfs.spec gnome-vfs-2.24.4/libgnomevfs/ gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-init.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-acl.c gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-daemon-method.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-cancellation.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-dbus-utils.c gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-mime-monitor.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-context.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-socket-buffer.c gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-handle.c gnome-vfs-2.24.4/libgnomevfs/xdgmimeglob.h gnome-vfs-2.24.4/libgnomevfs/xdgmimeicon.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-filesystem-type.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-volume-monitor-client.c gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-mime-info.c gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-volume-monitor-daemon.c gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-socket.c gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-module-callback-module-api.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-mime-deprecated.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-dbus-utils.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-parse-ls.h gnome-vfs-2.24.4/libgnomevfs/check-headers.pl gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-file-size.h.in gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-mime-info-cache.c gnome-vfs-2.24.4/libgnomevfs/Makefile.am gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-inet-connection.c gnome-vfs-2.24.4/libgnomevfs/xdgmimealias.c gnome-vfs-2.24.4/libgnomevfs/xdgmimecache.c gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-enum-types.c gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-open-fd.c gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-mime-handlers.c gnome-vfs-2.24.4/libgnomevfs/xdgmimemagic.c gnome-vfs-2.24.4/libgnomevfs/Makefile.in gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-monitor-private.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-hal-mounts.c gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-job-queue.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-address.c gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-drive.c gnome-vfs-2.24.4/libgnomevfs/xdgmime.c gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-volume-monitor-daemon.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-module-shared.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-drive.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-filesystem-type.c gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-cancellation-private.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-volume-monitor.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-mime.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-async-job-map.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-handle.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-cdrom.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-dns-sd.c gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-private.c gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-file-info.c gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-mime-info.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-iso9660.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-version.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-method.c gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-job.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-acl.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-find-directory.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-context.c gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-module-callback-private.c gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-cancellable-ops.c gnome-vfs-2.24.4/libgnomevfs/xdgmimeglob.c gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-monitor.c gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-mime-info-cache.h gnome-vfs-2.24.4/libgnomevfs/xdgmimeint.h gnome-vfs-2.24.4/libgnomevfs/xdgmimemagic.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-handle-private.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-job-queue.c gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-init.c gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-monitor.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-private-utils.c gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-unix-mounts.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-file-size.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-uri.h gnome-vfs-2.24.4/libgnomevfs/xdgmimeint.c gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-application-registry.c gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-async-ops.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-standard-callbacks.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-resolve.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-private-utils.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-job-limit.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-module-callback-module-api.c gnome-vfs-2.24.4/libgnomevfs/xdgmimealias.h gnome-vfs-2.24.4/libgnomevfs/xdgmimeparent.c gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-cancellable-ops.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-directory.c gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-volume-monitor.c gnome-vfs-2.24.4/libgnomevfs/gnome-vfs.h gnome-vfs-2.24.4/libgnomevfs/xdgmime.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-mime-sniff-buffer-private.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-transform.c gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-unix-mounts.c gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-cdrom.c gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-module-callback-marshall.c gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-ops.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-enum-types.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-version.h.in gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-uri.c gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-transform.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-cancellation.c gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-module.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-mime-handlers.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-volume.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-mime-sniff-buffer.c gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-module-callback-private.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-resolve.c gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-method.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-volume-monitor-private.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-find-directory.c gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-backend.h gnome-vfs-2.24.4/libgnomevfs/xdgmimecache.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-mime-utils.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-mime-magic.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-pty.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-daemon-method.c gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-result.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-hal-mounts.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-dns-sd.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-module.c gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-ace.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-mime.c gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-volume.c gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-module-shared.c gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-async-job-map.c gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-utils.c gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-module-callback.c gnome-vfs-2.24.4/libgnomevfs/xdgmimeparent.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-configuration.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-volume-monitor-client.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-application-registry.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-parse-ls.c gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-types.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-mime-magic.c gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-xfer.c gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-utils.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-xfer.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-mime-monitor.c gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-socket-buffer.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-configuration.c gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-private.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-mime-private.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-ops.c gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-module-callback.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-socket.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-ssl.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-async-ops.c gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-mime-sniff-buffer.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-ace.c gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-directory.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-file-info.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-ssl.c gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-volume-ops.c gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-inet-connection.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-address.h gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-result.c gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-job.c gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-pty.c gnome-vfs-2.24.4/libgnomevfs/gnome-vfs-dllmain.c gnome-vfs-2.24.4/libgnomevfs/xdgmimeicon.c gnome-vfs-2.24.4/ltmain.sh gnome-vfs-2.24.4/MAINTAINERS gnome-vfs-2.24.4/TODO gnome-vfs-2.24.4/mkinstalldirs gnome-vfs-2.24.4/HACKING gnome-vfs-2.24.4/README gnome-vfs-2.24.4/imported/ gnome-vfs-2.24.4/imported/Makefile.am gnome-vfs-2.24.4/imported/Makefile.in gnome-vfs-2.24.4/imported/neon/ gnome-vfs-2.24.4/imported/neon/ne_basic.c gnome-vfs-2.24.4/imported/neon/ne_props.c gnome-vfs-2.24.4/imported/neon/ne_request.h gnome-vfs-2.24.4/imported/neon/ne_alloc.h gnome-vfs-2.24.4/imported/neon/ne_compress.c gnome-vfs-2.24.4/imported/neon/ne_defs.h gnome-vfs-2.24.4/imported/neon/ne_xmlreq.c gnome-vfs-2.24.4/imported/neon/ne_gnomevfs.h gnome-vfs-2.24.4/imported/neon/Makefile.am gnome-vfs-2.24.4/imported/neon/ne_auth.h gnome-vfs-2.24.4/imported/neon/ne_alloc.c gnome-vfs-2.24.4/imported/neon/Makefile.in gnome-vfs-2.24.4/imported/neon/ne_dates.c gnome-vfs-2.24.4/imported/neon/ne_locks.c gnome-vfs-2.24.4/imported/neon/ne_props.h gnome-vfs-2.24.4/imported/neon/ne_xmlreq.h gnome-vfs-2.24.4/imported/neon/ne_md5.c gnome-vfs-2.24.4/imported/neon/ne_i18n.h gnome-vfs-2.24.4/imported/neon/ne_session.c gnome-vfs-2.24.4/imported/neon/ne_redirect.h gnome-vfs-2.24.4/imported/neon/ne_private.h gnome-vfs-2.24.4/imported/neon/ne_md5.h gnome-vfs-2.24.4/imported/neon/ne_acl.h gnome-vfs-2.24.4/imported/neon/ne_gnomevfs.c gnome-vfs-2.24.4/imported/neon/ne_locks.h gnome-vfs-2.24.4/imported/neon/ne_socket.h gnome-vfs-2.24.4/imported/neon/README gnome-vfs-2.24.4/imported/neon/ne_compress.h gnome-vfs-2.24.4/imported/neon/ChangeLog gnome-vfs-2.24.4/imported/neon/ne_acl.c gnome-vfs-2.24.4/imported/neon/ne_xml.h gnome-vfs-2.24.4/imported/neon/ne_redirect.c gnome-vfs-2.24.4/imported/neon/ne_xml.c gnome-vfs-2.24.4/imported/neon/ne_207.h gnome-vfs-2.24.4/imported/neon/ne_utils.c gnome-vfs-2.24.4/imported/neon/ne_session.h gnome-vfs-2.24.4/imported/neon/ne_auth.c gnome-vfs-2.24.4/imported/neon/ne_basic.h gnome-vfs-2.24.4/imported/neon/ne_utils.h gnome-vfs-2.24.4/imported/neon/ne_207.c gnome-vfs-2.24.4/imported/neon/ne_request.c gnome-vfs-2.24.4/imported/neon/ne_ssl.h gnome-vfs-2.24.4/imported/neon/ne_uri.h gnome-vfs-2.24.4/imported/neon/COPYING.LIB gnome-vfs-2.24.4/imported/neon/ne_string.h gnome-vfs-2.24.4/imported/neon/ne_string.c gnome-vfs-2.24.4/imported/neon/ne_uri.c gnome-vfs-2.24.4/imported/neon/ne_dates.h gnome-vfs-2.24.4/imported/fnmatch/ gnome-vfs-2.24.4/imported/fnmatch/fnmatch.c gnome-vfs-2.24.4/imported/fnmatch/Makefile.am gnome-vfs-2.24.4/imported/fnmatch/fnmatch.h gnome-vfs-2.24.4/imported/fnmatch/Makefile.in gnome-vfs-2.24.4/gtk-doc.make gnome-vfs-2.24.4/aclocal.m4 gnome-vfs-2.24.4/acinclude.m4 gnome-vfs-2.24.4/ChangeLog gnome-vfs-2.24.4/autogen.sh gnome-vfs-2.24.4/NEWS gnome-vfs-2.24.4/po/ gnome-vfs-2.24.4/po/ja.po gnome-vfs-2.24.4/po/it.po gnome-vfs-2.24.4/po/ko.po gnome-vfs-2.24.4/po/bn_IN.po gnome-vfs-2.24.4/po/vi.po gnome-vfs-2.24.4/po/pt_BR.po gnome-vfs-2.24.4/po/sr@ije.po gnome-vfs-2.24.4/po/id.po gnome-vfs-2.24.4/po/en_GB.po gnome-vfs-2.24.4/po/fr.po gnome-vfs-2.24.4/po/ka.po gnome-vfs-2.24.4/po/pa.po gnome-vfs-2.24.4/po/sr@latin.po gnome-vfs-2.24.4/po/wa.po gnome-vfs-2.24.4/po/sv.po gnome-vfs-2.24.4/po/nl.po gnome-vfs-2.24.4/po/lt.po gnome-vfs-2.24.4/po/sq.po gnome-vfs-2.24.4/po/lv.po gnome-vfs-2.24.4/po/kn.po gnome-vfs-2.24.4/po/or.po gnome-vfs-2.24.4/po/zh_TW.po gnome-vfs-2.24.4/po/ro.po gnome-vfs-2.24.4/po/uz.po gnome-vfs-2.24.4/po/be.po gnome-vfs-2.24.4/po/mg.po gnome-vfs-2.24.4/po/hu.po gnome-vfs-2.24.4/po/is.po gnome-vfs-2.24.4/po/as.po gnome-vfs-2.24.4/po/POTFILES.skip gnome-vfs-2.24.4/po/de.po gnome-vfs-2.24.4/po/uz@cyrillic.po gnome-vfs-2.24.4/po/bs.po gnome-vfs-2.24.4/po/bg.po gnome-vfs-2.24.4/po/es.po gnome-vfs-2.24.4/po/et.po gnome-vfs-2.24.4/po/cs.po gnome-vfs-2.24.4/po/da.po gnome-vfs-2.24.4/po/az.po gnome-vfs-2.24.4/po/am.po gnome-vfs-2.24.4/po/sl.po gnome-vfs-2.24.4/po/hi.po gnome-vfs-2.24.4/po/ca.po gnome-vfs-2.24.4/po/gu.po gnome-vfs-2.24.4/po/pl.po gnome-vfs-2.24.4/po/af.po gnome-vfs-2.24.4/po/ms.po gnome-vfs-2.24.4/po/ku.po gnome-vfs-2.24.4/po/nso.po gnome-vfs-2.24.4/po/ml.po gnome-vfs-2.24.4/po/eo.po gnome-vfs-2.24.4/po/xh.po gnome-vfs-2.24.4/po/hr.po gnome-vfs-2.24.4/po/he.po gnome-vfs-2.24.4/po/ChangeLog gnome-vfs-2.24.4/po/rw.po gnome-vfs-2.24.4/po/te.po gnome-vfs-2.24.4/po/ne.po gnome-vfs-2.24.4/po/zh_CN.po gnome-vfs-2.24.4/po/ta.po gnome-vfs-2.24.4/po/zu.po gnome-vfs-2.24.4/po/bn.po gnome-vfs-2.24.4/po/mk.po gnome-vfs-2.24.4/po/tr.po gnome-vfs-2.24.4/po/ast.po gnome-vfs-2.24.4/po/gl.po gnome-vfs-2.24.4/po/uk.po gnome-vfs-2.24.4/po/LINGUAS gnome-vfs-2.24.4/po/en_CA.po gnome-vfs-2.24.4/po/eu.po gnome-vfs-2.24.4/po/el.po gnome-vfs-2.24.4/po/fa.po gnome-vfs-2.24.4/po/oc.po gnome-vfs-2.24.4/po/cy.po gnome-vfs-2.24.4/po/en@shaw.po gnome-vfs-2.24.4/po/POTFILES.in gnome-vfs-2.24.4/po/mr.po gnome-vfs-2.24.4/po/pt.po gnome-vfs-2.24.4/po/mn.po gnome-vfs-2.24.4/po/zh_HK.po gnome-vfs-2.24.4/po/mai.po gnome-vfs-2.24.4/po/th.po gnome-vfs-2.24.4/po/ga.po gnome-vfs-2.24.4/po/sk.po gnome-vfs-2.24.4/po/fi.po gnome-vfs-2.24.4/po/ca@valencia.po gnome-vfs-2.24.4/po/sr.po gnome-vfs-2.24.4/po/dz.po gnome-vfs-2.24.4/po/yi.po gnome-vfs-2.24.4/po/ru.po gnome-vfs-2.24.4/po/Makefile.in.in gnome-vfs-2.24.4/po/ar.po gnome-vfs-2.24.4/po/nn.po gnome-vfs-2.24.4/po/li.po gnome-vfs-2.24.4/po/nb.po gnome-vfs-2.24.4/depcomp gnome-vfs-2.24.4/intltool-merge.in gnome-vfs-2.24.4/intltool-extract.in gnome-vfs-2.24.4/config.h.in gnome-vfs-2.24.4/COPYING gnome-vfs-2.24.4/INSTALL gnome-vfs-2.24.4/schemas/ gnome-vfs-2.24.4/schemas/system_dns_sd.schemas.in gnome-vfs-2.24.4/schemas/Makefile.am gnome-vfs-2.24.4/schemas/Makefile.in gnome-vfs-2.24.4/schemas/desktop_gnome_url_handlers.schemas gnome-vfs-2.24.4/schemas/system_http_proxy.schemas gnome-vfs-2.24.4/schemas/desktop_default_applications.schemas gnome-vfs-2.24.4/schemas/system_smb.schemas gnome-vfs-2.24.4/schemas/desktop_gnome_url_handlers.schemas.in gnome-vfs-2.24.4/schemas/system_smb.schemas.in gnome-vfs-2.24.4/schemas/system_dns_sd.schemas gnome-vfs-2.24.4/schemas/system_http_proxy.schemas.in gnome-vfs-2.24.4/schemas/desktop_default_applications.schemas.in gnome-vfs-2.24.4/intltool-update.in gnome-vfs-2.24.4/daemon/ gnome-vfs-2.24.4/daemon/Makefile.am gnome-vfs-2.24.4/daemon/Makefile.in gnome-vfs-2.24.4/daemon/dbus-utils.h gnome-vfs-2.24.4/daemon/gnome-vfs-daemon.service.in gnome-vfs-2.24.4/daemon/daemon-connection.c gnome-vfs-2.24.4/daemon/vfs-daemon.c gnome-vfs-2.24.4/daemon/dbus-utils.c gnome-vfs-2.24.4/daemon/daemon-connection.h gnome-vfs-2.24.4/xdgmime.win32.diff gnome-vfs-2.24.4/COPYING.LIB gnome-vfs-2.24.4/programs/ gnome-vfs-2.24.4/programs/gnomevfs-mv.c gnome-vfs-2.24.4/programs/Makefile.am gnome-vfs-2.24.4/programs/gnomevfs-copy.c gnome-vfs-2.24.4/programs/Makefile.in gnome-vfs-2.24.4/programs/gnomevfs-rm.c gnome-vfs-2.24.4/programs/gnomevfs-ls.c gnome-vfs-2.24.4/programs/gnomevfs-mkdir.c gnome-vfs-2.24.4/programs/gnomevfs-info.c gnome-vfs-2.24.4/programs/gnomevfs-monitor.c gnome-vfs-2.24.4/programs/gnomevfs-cat.c gnome-vfs-2.24.4/programs/authentication.c gnome-vfs-2.24.4/programs/gnomevfs-df.c gnome-vfs-2.24.4/config.sub gnome-vfs-2.24.4/config.guess phase `unpack' succeeded after 0.6 seconds starting phase `bootstrap' GNU build system bootstrapping not needed phase `bootstrap' succeeded after 0.0 seconds starting phase `patch-usr-bin-file' patch-/usr/bin/file: ./configure: changing `/usr/bin/file' to `/gnu/store/vl1b3nq6gijpzbl03zq92m5dwgs17nik-file-5.39/bin/file' patch-/usr/bin/file: ./configure: changing `/usr/bin/file' to `/gnu/store/vl1b3nq6gijpzbl03zq92m5dwgs17nik-file-5.39/bin/file' patch-/usr/bin/file: ./configure: changing `/usr/bin/file' to `/gnu/store/vl1b3nq6gijpzbl03zq92m5dwgs17nik-file-5.39/bin/file' patch-/usr/bin/file: ./configure: changing `/usr/bin/file' to `/gnu/store/vl1b3nq6gijpzbl03zq92m5dwgs17nik-file-5.39/bin/file' patch-/usr/bin/file: ./configure: changing `/usr/bin/file' to `/gnu/store/vl1b3nq6gijpzbl03zq92m5dwgs17nik-file-5.39/bin/file' patch-/usr/bin/file: ./configure: changing `/usr/bin/file' to `/gnu/store/vl1b3nq6gijpzbl03zq92m5dwgs17nik-file-5.39/bin/file' patch-/usr/bin/file: ./configure: changing `/usr/bin/file' to `/gnu/store/vl1b3nq6gijpzbl03zq92m5dwgs17nik-file-5.39/bin/file' patch-/usr/bin/file: ./configure: changing `/usr/bin/file' to `/gnu/store/vl1b3nq6gijpzbl03zq92m5dwgs17nik-file-5.39/bin/file' patch-/usr/bin/file: ./configure: changing `/usr/bin/file' to `/gnu/store/vl1b3nq6gijpzbl03zq92m5dwgs17nik-file-5.39/bin/file' phase `patch-usr-bin-file' succeeded after 0.1 seconds starting phase `patch-source-shebangs' patch-shebang: ./autogen.sh: changing `/bin/sh' to `/gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/sh' patch-shebang: ./config.guess: changing `/bin/sh' to `/gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/sh' patch-shebang: ./config.sub: changing `/bin/sh' to `/gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/sh' patch-shebang: ./configure: changing `/bin/sh' to `/gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/sh' patch-shebang: ./depcomp: changing `/bin/sh' to `/gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/sh' patch-shebang: ./gnome-vfs-zip.in: changing `/bin/sh' to `/gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/sh' patch-shebang: ./install-sh: changing `/bin/sh' to `/gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/sh' patch-shebang: ./libgnomevfs/check-headers.pl: changing `/usr/bin/perl' to `/gnu/store/zn45z8pv5dkh98hi9l1q9aldbplga3m7-perl-5.34.0/bin/perl' patch-shebang: ./missing: changing `/bin/sh' to `/gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/sh' patch-shebang: ./mkinstalldirs: changing `/bin/sh' to `/gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/sh' patch-shebang: ./test/auto-test: changing `/bin/sh' to `/gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/sh' patch-shebang: ./test/vfs-run.in: changing `/bin/sh' to `/gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/sh' phase `patch-source-shebangs' succeeded after 0.1 seconds starting phase `ignore-deprecations' phase `ignore-deprecations' succeeded after 0.0 seconds starting phase `patch-test-async-cancel-to-never-fail' phase `patch-test-async-cancel-to-never-fail' succeeded after 0.0 seconds starting phase `configure' source directory: "/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4" (relative from build: ".") build directory: "/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4" configure flags: ("CONFIG_SHELL=/gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash" "SHELL=/gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash" "--prefix=/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4" "--enable-fast-install" "--build=i686-unknown-linux-gnu") checking for a BSD-compatible install... /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... no checking whether to enable maintainer-specific portions of Makefiles... no checking for style of include used by make... GNU checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking dependency style of gcc... gcc3 checking for library containing strerror... none required checking for gcc... (cached) gcc checking whether we are using the GNU C compiler... (cached) yes checking whether gcc accepts -g... (cached) yes checking for gcc option to accept ISO C89... (cached) none needed checking dependency style of gcc... (cached) gcc3 checking how to run the C preprocessor... gcc -E checking for gawk... (cached) gawk checking build system type... i686-unknown-linux-gnu checking host system type... i686-unknown-linux-gnu checking for a sed that does not truncate output... /gnu/store/cnwr7widbi6470kfyb13krx46kz5anmy-sed-4.8/bin/sed checking for grep that handles long lines and -e... /gnu/store/bx47clwnxn51m7jdwfimz4lw2fh8g21v-grep-3.6/bin/grep checking for egrep... /gnu/store/bx47clwnxn51m7jdwfimz4lw2fh8g21v-grep-3.6/bin/grep -E checking for fgrep... /gnu/store/bx47clwnxn51m7jdwfimz4lw2fh8g21v-grep-3.6/bin/grep -F checking for ld used by gcc... /gnu/store/4bzvr16pyax9224v9r72rqxswj9931sb-ld-wrapper-0/bin/ld checking if the linker (/gnu/store/4bzvr16pyax9224v9r72rqxswj9931sb-ld-wrapper-0/bin/ld) is GNU ld... yes checking for BSD- or MS-compatible name lister (nm)... /gnu/store/v4a7zw8w52v64kw5781ypa8gjwd098jz-binutils-2.37/bin/nm -B checking the name lister (/gnu/store/v4a7zw8w52v64kw5781ypa8gjwd098jz-binutils-2.37/bin/nm -B) interface... BSD nm checking whether ln -s works... yes checking the maximum length of command line arguments... 1572864 checking whether the shell understands some XSI constructs... yes checking whether the shell understands "+="... yes checking for /gnu/store/4bzvr16pyax9224v9r72rqxswj9931sb-ld-wrapper-0/bin/ld option to reload object files... -r checking for objdump... objdump checking how to recognize dependent libraries... pass_all checking for ar... ar checking for strip... strip checking for ranlib... ranlib checking command to parse /gnu/store/v4a7zw8w52v64kw5781ypa8gjwd098jz-binutils-2.37/bin/nm -B output from gcc object... ok 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 for dlfcn.h... yes checking for objdir... .libs checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC -DPIC checking if gcc PIC flag -fPIC -DPIC works... yes checking if gcc static flag -static works... yes checking if gcc supports -c -o file.o... yes checking if gcc supports -c -o file.o... (cached) yes checking whether the gcc linker (/gnu/store/4bzvr16pyax9224v9r72rqxswj9931sb-ld-wrapper-0/bin/ld) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes checking whether NLS is requested... yes checking for intltool >= 0.35.0... 0.51.0 found checking for intltool-update... /gnu/store/jr3sfjid7nv7bqbddwir31a6chddmady-intltool-0.51.0/bin/intltool-update checking for intltool-merge... /gnu/store/jr3sfjid7nv7bqbddwir31a6chddmady-intltool-0.51.0/bin/intltool-merge checking for intltool-extract... /gnu/store/jr3sfjid7nv7bqbddwir31a6chddmady-intltool-0.51.0/bin/intltool-extract checking for xgettext... /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/xgettext checking for msgmerge... /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgmerge checking for msgfmt... /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt checking for gmsgfmt... /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt checking for perl... /gnu/store/zn45z8pv5dkh98hi9l1q9aldbplga3m7-perl-5.34.0/bin/perl checking for perl >= 5.8.1... 5.34.0 checking for XML::Parser... ok checking for pkg-config... /gnu/store/3nw1jhybwdbbsx8v821bm71h205462wz-pkg-config-0.29.2/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for MODULES_XML... yes checking for MODULES... yes checking for MODULES_FILE... yes checking for MODULES_GCONF... yes checking for MODULES_XML_GCONF... yes checking for TEST... yes checking what warning flags to pass to the C compiler... -Wall -Wmissing-prototypes checking what language compliance flags to pass to the C compiler... checking for library containing sem_wait... no checking for library containing sem_wait... (cached) no checking size_t in ... yes checking off_t in ... yes checking for off64_t... 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... (cached) /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt checking for dcgettext... yes checking if msgfmt accepts -c... yes checking for gmsgfmt... (cached) /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt checking for xgettext... (cached) /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/xgettext checking for ngettext... yes checking for library containing gethostent... none required checking for library containing setsockopt... none required checking for library containing login_tty... -lutil checking for working alloca.h... yes checking for alloca... yes checking for getdtablesize... yes checking for open64... yes checking for lseek64... yes checking for statfs... yes checking for statvfs... yes checking for seteuid... yes checking for setegid... yes checking for setresuid... yes checking for setresgid... yes checking for readdir_r... yes checking for mbrtowc... yes checking for inet_pton... yes checking for getdelim... yes checking for sysctlbyname... no checking for poll... yes checking for posix_fadvise... yes checking for fchmod... yes checking for atoll... yes checking for mmap... yes checking for struct stat.st_blksize... yes checking for struct stat.st_rdev... yes checking for struct stat.st_blocks... yes checking for setmntent... yes checking for endmntent... yes checking for hasmntopt... yes checking for getmntinfo... no checking mntent.h usability... yes checking mntent.h presence... yes checking for mntent.h... yes checking sys/mnttab.h usability... no checking sys/mnttab.h presence... no checking for sys/mnttab.h... no checking sys/vfstab.h usability... no checking sys/vfstab.h presence... no checking for sys/vfstab.h... no checking sys/cdio.h usability... no checking sys/cdio.h presence... no checking for sys/cdio.h... no checking sys/mount.h usability... yes checking sys/mount.h presence... yes checking for sys/mount.h... yes checking sys/mntctl.h usability... no checking sys/mntctl.h presence... no checking for sys/mntctl.h... no checking sys/vfs.h usability... yes checking sys/vfs.h presence... yes checking for sys/vfs.h... yes checking sys/vmount.h usability... no checking sys/vmount.h presence... no checking for sys/vmount.h... no checking sys/sysctl.h usability... no checking sys/sysctl.h presence... no checking for sys/sysctl.h... no checking fstab.h usability... yes checking fstab.h presence... yes checking for fstab.h... yes checking fnmatch.h usability... yes checking fnmatch.h presence... yes checking for fnmatch.h... yes checking util.h usability... no checking util.h presence... no checking for util.h... no checking sys/sysmacros.h usability... yes checking sys/sysmacros.h presence... yes checking for sys/sysmacros.h... yes checking for gconftool-2... /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/bin/gconftool-2 Using config source xml:merged:/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/etc/gconf/gconf.xml.defaults for schema installation Using $(sysconfdir)/gconf/schemas as install directory for schema files checking sys/param.h usability... yes checking sys/param.h presence... yes checking for sys/param.h... yes checking sys/resource.h usability... yes checking sys/resource.h presence... yes checking for sys/resource.h... yes checking for sys/vfs.h... (cached) yes checking for sys/mount.h... (cached) yes checking sys/statfs.h usability... yes checking sys/statfs.h presence... yes checking for sys/statfs.h... yes checking sys/statvfs.h usability... yes checking sys/statvfs.h presence... yes checking for sys/statvfs.h... yes checking for sys/param.h... (cached) yes checking wctype.h usability... yes checking wctype.h presence... yes checking for wctype.h... yes checking sys/poll.h usability... yes checking sys/poll.h presence... yes checking for sys/poll.h... yes checking poll.h usability... yes checking poll.h presence... yes checking for poll.h... yes checking for struct statfs.f_type... yes checking number of arguments to statfs()... 2 checking for mbstate_t... yes checking for dirname... yes checking libgen.h usability... yes checking libgen.h presence... yes checking for libgen.h... yes checking for socket... yes checking for inet_ntop... yes checking for bzCompressInit in -lbz2... no checking bzlib.h usability... yes checking bzlib.h presence... yes checking for bzlib.h... yes checking struct linger is available... yes checking for krb5-config... none checking for gcc option to accept ISO C99... none needed checking for gcc option to accept ISO Standard C... (cached) none needed checking for inline... inline checking for an ANSI C-conforming const... yes checking for Darwin... no checking size of int... 4 checking size of long... 4 checking size of long long... 8 checking for gcc -Wformat -Werror sanity... yes checking errno.h usability... yes checking errno.h presence... yes checking for errno.h... yes checking stdarg.h usability... yes checking stdarg.h presence... yes checking for stdarg.h... yes checking for string.h... (cached) yes checking for stdlib.h... (cached) yes checking size of size_t... 4 checking how to print size_t... u checking size of off_t... 4 checking how to print off_t... ld checking size of ssize_t... 4 checking how to print ssize_t... d checking whether byte ordering is bigendian... no checking whether strerror_r is declared... yes checking for strerror_r... yes checking whether strerror_r returns char *... yes configure: using bundled neon (0.25.4) checking for strings.h... (cached) yes checking sys/time.h usability... yes checking sys/time.h presence... yes checking for sys/time.h... yes checking limits.h usability... yes checking limits.h presence... yes checking for limits.h... yes checking sys/select.h usability... yes checking sys/select.h presence... yes checking for sys/select.h... yes checking arpa/inet.h usability... yes checking arpa/inet.h presence... yes checking for arpa/inet.h... yes checking signal.h usability... yes checking signal.h presence... yes checking for signal.h... yes checking sys/socket.h usability... yes checking sys/socket.h presence... yes checking for sys/socket.h... yes checking netinet/in.h usability... yes checking netinet/in.h presence... yes checking for netinet/in.h... yes checking netinet/tcp.h usability... yes checking netinet/tcp.h presence... yes checking for netinet/tcp.h... yes checking netdb.h usability... yes checking netdb.h presence... yes checking for netdb.h... yes checking for strcasecmp... yes checking for signal... yes checking for setvbuf... yes checking for setsockopt... yes checking for stpcpy... yes checking for struct tm.tm_gmtoff... yes checking zlib.h usability... yes checking zlib.h presence... yes checking for zlib.h... yes checking for inflate in -lz... yes checking whether to enable ACL support in neon... yes checking for LIBXML... yes checking for Solaris platform... no before test, samba_includes: checking libsmbclient.h usability... no checking libsmbclient.h presence... no checking for libsmbclient.h... no have_samba_includes: no checking for Samba 3.0 libraries... no checking for OPENSSL... no checking for OpenSSL includes... "" checking openssl/ssl.h usability... no checking openssl/ssl.h presence... no checking for openssl/ssl.h... no checking openssl/x509.h usability... no checking openssl/x509.h presence... no checking for openssl/x509.h... no checking for OpenSSL libraries... no checking for AVAHI... no checking for HOWL... no checking for HAL... no checking for res_search... no checking for res_search in -lresolv... yes checking for res_ninit()... yes checking for getaddrinfo... yes checking whether to enable ipv6... yes checking for LIBGNOMEVFS... yes checking for LIBGNOMEVFSDAEMON... yes checking sys/un.h usability... yes checking sys/un.h presence... yes checking for sys/un.h... yes checking stropts.h usability... no checking stropts.h presence... no checking for stropts.h... no checking termios.h usability... yes checking termios.h presence... yes checking for termios.h... yes checking utmp.h usability... yes checking utmp.h presence... yes checking for utmp.h... yes checking for getpt... yes checking for posix_openpt... yes checking for grantpt... yes checking for unlockpt... yes checking for ptsname... yes checking for ptsname_r... yes checking for socketpair... yes checking for getxattr in -lattr... no checking for acl_get_file in -lacl... no checking for acl in -lsec... no checking for Solaris ACL... no checking for POSIX ACL... no checking sys/inotify.h usability... yes checking sys/inotify.h presence... yes checking for sys/inotify.h... yes checking for FAMOpen in -lfam... no configure: WARNING: *** FAM support will not be built (FAM library not found) Gnome-vfs depends on FAM to provide notification when files are altered (either through filesystem polling, or a kernel notification mechanism). If Gnome-vfs is built without FAM support, directories viewed with Nautilus or other applications will not remain in synch with the actual filesystem when they are altered by external processes. Particularly if you are a distributor please compile Nautilus with FAM support. FAM is available from http://oss.sgi.com/projects/fam/. A patch to add Linux Kernel 2.4 directory notify support to FAM (highly desirable) is available from http://people.redhat.com/alexl/files/ *** checking for is_selinux_enabled in -lselinux... no checking for gtkdoc-check... no checking for gtkdoc-rebase... no checking for gtkdoc-mkpdf... no checking whether to build gtk-doc documentation... no checking how to get filesystem type... 4.3BSD checking for perl5... no checking for perl... perl checking for ssh... ssh configure: creating ./config.status config.status: creating Makefile config.status: creating gnome-vfs.spec config.status: creating gnome-vfs-zip config.status: creating libgnomevfs/gnome-vfs-file-size.h config.status: creating libgnomevfs/gnome-vfs-version.h config.status: creating libgnomevfs/Makefile config.status: creating imported/Makefile config.status: creating imported/fnmatch/Makefile config.status: creating imported/neon/Makefile config.status: creating modules/Makefile config.status: creating daemon/Makefile config.status: creating schemas/Makefile config.status: creating devel-docs/Makefile config.status: creating devel-docs/gnome-vfs-tutorial/Makefile config.status: creating po/Makefile.in config.status: creating programs/Makefile config.status: creating test/Makefile config.status: creating test/vfs-run config.status: creating doc/Makefile config.status: creating doc/version.xml config.status: creating gnome-vfs-2.0.pc config.status: creating gnome-vfs-module-2.0.pc config.status: creating config.h config.status: executing depfiles commands config.status: executing libtool commands config.status: executing default-1 commands config.status: executing po/stamp-it commands Gnome VFS configuration summary: IPv6 support: yes SSL support: no Avahi support: no Howl support: no HAL support: no Enable gnome-vfs-daemon: yes SELinux support: no File ACL backends: Gtk Doc: no FS monitor backends: inotify Samba method: no CDDA method: no Enable profiler: no phase `configure' succeeded after 16.1 seconds starting phase `patch-generated-file-shebangs' phase `patch-generated-file-shebangs' succeeded after 0.2 seconds starting phase `build' make all-recursive make[1]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4' Making all in imported make[2]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/imported' Making all in neon make[3]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/imported/neon' /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -DNE_HAVE_DAV -g -O2 -I.. -I../.. -I./imported/neon -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I../.. -I../.. -I../../libgnomevfs -I../../libgnomevfs -g -O2 -MT ne_request.lo -MD -MP -MF .deps/ne_request.Tpo -c -o ne_request.lo ne_request.c /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -DNE_HAVE_DAV -g -O2 -I.. -I../.. -I./imported/neon -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I../.. -I../.. -I../../libgnomevfs -I../../libgnomevfs -g -O2 -MT ne_session.lo -MD -MP -MF .deps/ne_session.Tpo -c -o ne_session.lo ne_session.c /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -DNE_HAVE_DAV -g -O2 -I.. -I../.. -I./imported/neon -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I../.. -I../.. -I../../libgnomevfs -I../../libgnomevfs -g -O2 -MT ne_basic.lo -MD -MP -MF .deps/ne_basic.Tpo -c -o ne_basic.lo ne_basic.c /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -DNE_HAVE_DAV -g -O2 -I.. -I../.. -I./imported/neon -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I../.. -I../.. -I../../libgnomevfs -I../../libgnomevfs -g -O2 -MT ne_string.lo -MD -MP -MF .deps/ne_string.Tpo -c -o ne_string.lo ne_string.c /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -DNE_HAVE_DAV -g -O2 -I.. -I../.. -I./imported/neon -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I../.. -I../.. -I../../libgnomevfs -I../../libgnomevfs -g -O2 -MT ne_uri.lo -MD -MP -MF .deps/ne_uri.Tpo -c -o ne_uri.lo ne_uri.c /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -DNE_HAVE_DAV -g -O2 -I.. -I../.. -I./imported/neon -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I../.. -I../.. -I../../libgnomevfs -I../../libgnomevfs -g -O2 -MT ne_dates.lo -MD -MP -MF .deps/ne_dates.Tpo -c -o ne_dates.lo ne_dates.c /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -DNE_HAVE_DAV -g -O2 -I.. -I../.. -I./imported/neon -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I../.. -I../.. -I../../libgnomevfs -I../../libgnomevfs -g -O2 -MT ne_alloc.lo -MD -MP -MF .deps/ne_alloc.Tpo -c -o ne_alloc.lo ne_alloc.c /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -DNE_HAVE_DAV -g -O2 -I.. -I../.. -I./imported/neon -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I../.. -I../.. -I../../libgnomevfs -I../../libgnomevfs -g -O2 -MT ne_md5.lo -MD -MP -MF .deps/ne_md5.Tpo -c -o ne_md5.lo ne_md5.c /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -DNE_HAVE_DAV -g -O2 -I.. -I../.. -I./imported/neon -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I../.. -I../.. -I../../libgnomevfs -I../../libgnomevfs -g -O2 -MT ne_utils.lo -MD -MP -MF .deps/ne_utils.Tpo -c -o ne_utils.lo ne_utils.c /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -DNE_HAVE_DAV -g -O2 -I.. -I../.. -I./imported/neon -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I../.. -I../.. -I../../libgnomevfs -I../../libgnomevfs -g -O2 -MT ne_auth.lo -MD -MP -MF .deps/ne_auth.Tpo -c -o ne_auth.lo ne_auth.c /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -DNE_HAVE_DAV -g -O2 -I.. -I../.. -I./imported/neon -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I../.. -I../.. -I../../libgnomevfs -I../../libgnomevfs -g -O2 -MT ne_redirect.lo -MD -MP -MF .deps/ne_redirect.Tpo -c -o ne_redirect.lo ne_redirect.c /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -DNE_HAVE_DAV -g -O2 -I.. -I../.. -I./imported/neon -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I../.. -I../.. -I../../libgnomevfs -I../../libgnomevfs -g -O2 -MT ne_compress.lo -MD -MP -MF .deps/ne_compress.Tpo -c -o ne_compress.lo ne_compress.c /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -DNE_HAVE_DAV -g -O2 -I.. -I../.. -I./imported/neon -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I../.. -I../.. -I../../libgnomevfs -I../../libgnomevfs -g -O2 -MT ne_207.lo -MD -MP -MF .deps/ne_207.Tpo -c -o ne_207.lo ne_207.c /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -DNE_HAVE_DAV -g -O2 -I.. -I../.. -I./imported/neon -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I../.. -I../.. -I../../libgnomevfs -I../../libgnomevfs -g -O2 -MT ne_xml.lo -MD -MP -MF .deps/ne_xml.Tpo -c -o ne_xml.lo ne_xml.c /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -DNE_HAVE_DAV -g -O2 -I.. -I../.. -I./imported/neon -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I../.. -I../.. -I../../libgnomevfs -I../../libgnomevfs -g -O2 -MT ne_props.lo -MD -MP -MF .deps/ne_props.Tpo -c -o ne_props.lo ne_props.c /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -DNE_HAVE_DAV -g -O2 -I.. -I../.. -I./imported/neon -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I../.. -I../.. -I../../libgnomevfs -I../../libgnomevfs -g -O2 -MT ne_locks.lo -MD -MP -MF .deps/ne_locks.Tpo -c -o ne_locks.lo ne_locks.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -DNE_HAVE_DAV -g -O2 -I.. -I../.. -I./imported/neon -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I../.. -I../.. -I../../libgnomevfs -I../../libgnomevfs -g -O2 -MT ne_string.lo -MD -MP -MF .deps/ne_string.Tpo -c ne_string.c -fPIC -DPIC -o .libs/ne_string.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -DNE_HAVE_DAV -g -O2 -I.. -I../.. -I./imported/neon -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I../.. -I../.. -I../../libgnomevfs -I../../libgnomevfs -g -O2 -MT ne_session.lo -MD -MP -MF .deps/ne_session.Tpo -c ne_session.c -fPIC -DPIC -o .libs/ne_session.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -DNE_HAVE_DAV -g -O2 -I.. -I../.. -I./imported/neon -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I../.. -I../.. -I../../libgnomevfs -I../../libgnomevfs -g -O2 -MT ne_uri.lo -MD -MP -MF .deps/ne_uri.Tpo -c ne_uri.c -fPIC -DPIC -o .libs/ne_uri.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -DNE_HAVE_DAV -g -O2 -I.. -I../.. -I./imported/neon -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I../.. -I../.. -I../../libgnomevfs -I../../libgnomevfs -g -O2 -MT ne_basic.lo -MD -MP -MF .deps/ne_basic.Tpo -c ne_basic.c -fPIC -DPIC -o .libs/ne_basic.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -DNE_HAVE_DAV -g -O2 -I.. -I../.. -I./imported/neon -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I../.. -I../.. -I../../libgnomevfs -I../../libgnomevfs -g -O2 -MT ne_request.lo -MD -MP -MF .deps/ne_request.Tpo -c ne_request.c -fPIC -DPIC -o .libs/ne_request.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -DNE_HAVE_DAV -g -O2 -I.. -I../.. -I./imported/neon -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I../.. -I../.. -I../../libgnomevfs -I../../libgnomevfs -g -O2 -MT ne_alloc.lo -MD -MP -MF .deps/ne_alloc.Tpo -c ne_alloc.c -fPIC -DPIC -o .libs/ne_alloc.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -DNE_HAVE_DAV -g -O2 -I.. -I../.. -I./imported/neon -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I../.. -I../.. -I../../libgnomevfs -I../../libgnomevfs -g -O2 -MT ne_redirect.lo -MD -MP -MF .deps/ne_redirect.Tpo -c ne_redirect.c -fPIC -DPIC -o .libs/ne_redirect.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -DNE_HAVE_DAV -g -O2 -I.. -I../.. -I./imported/neon -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I../.. -I../.. -I../../libgnomevfs -I../../libgnomevfs -g -O2 -MT ne_utils.lo -MD -MP -MF .deps/ne_utils.Tpo -c ne_utils.c -fPIC -DPIC -o .libs/ne_utils.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -DNE_HAVE_DAV -g -O2 -I.. -I../.. -I./imported/neon -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I../.. -I../.. -I../../libgnomevfs -I../../libgnomevfs -g -O2 -MT ne_md5.lo -MD -MP -MF .deps/ne_md5.Tpo -c ne_md5.c -fPIC -DPIC -o .libs/ne_md5.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -DNE_HAVE_DAV -g -O2 -I.. -I../.. -I./imported/neon -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I../.. -I../.. -I../../libgnomevfs -I../../libgnomevfs -g -O2 -MT ne_dates.lo -MD -MP -MF .deps/ne_dates.Tpo -c ne_dates.c -fPIC -DPIC -o .libs/ne_dates.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -DNE_HAVE_DAV -g -O2 -I.. -I../.. -I./imported/neon -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I../.. -I../.. -I../../libgnomevfs -I../../libgnomevfs -g -O2 -MT ne_207.lo -MD -MP -MF .deps/ne_207.Tpo -c ne_207.c -fPIC -DPIC -o .libs/ne_207.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -DNE_HAVE_DAV -g -O2 -I.. -I../.. -I./imported/neon -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I../.. -I../.. -I../../libgnomevfs -I../../libgnomevfs -g -O2 -MT ne_auth.lo -MD -MP -MF .deps/ne_auth.Tpo -c ne_auth.c -fPIC -DPIC -o .libs/ne_auth.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -DNE_HAVE_DAV -g -O2 -I.. -I../.. -I./imported/neon -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I../.. -I../.. -I../../libgnomevfs -I../../libgnomevfs -g -O2 -MT ne_xml.lo -MD -MP -MF .deps/ne_xml.Tpo -c ne_xml.c -fPIC -DPIC -o .libs/ne_xml.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -DNE_HAVE_DAV -g -O2 -I.. -I../.. -I./imported/neon -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I../.. -I../.. -I../../libgnomevfs -I../../libgnomevfs -g -O2 -MT ne_compress.lo -MD -MP -MF .deps/ne_compress.Tpo -c ne_compress.c -fPIC -DPIC -o .libs/ne_compress.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -DNE_HAVE_DAV -g -O2 -I.. -I../.. -I./imported/neon -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I../.. -I../.. -I../../libgnomevfs -I../../libgnomevfs -g -O2 -MT ne_locks.lo -MD -MP -MF .deps/ne_locks.Tpo -c ne_locks.c -fPIC -DPIC -o .libs/ne_locks.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -DNE_HAVE_DAV -g -O2 -I.. -I../.. -I./imported/neon -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I../.. -I../.. -I../../libgnomevfs -I../../libgnomevfs -g -O2 -MT ne_props.lo -MD -MP -MF .deps/ne_props.Tpo -c ne_props.c -fPIC -DPIC -o .libs/ne_props.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -DNE_HAVE_DAV -g -O2 -I.. -I../.. -I./imported/neon -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I../.. -I../.. -I../../libgnomevfs -I../../libgnomevfs -g -O2 -MT ne_alloc.lo -MD -MP -MF .deps/ne_alloc.Tpo -c ne_alloc.c -o ne_alloc.o >/dev/null 2>&1 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -DNE_HAVE_DAV -g -O2 -I.. -I../.. -I./imported/neon -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I../.. -I../.. -I../../libgnomevfs -I../../libgnomevfs -g -O2 -MT ne_dates.lo -MD -MP -MF .deps/ne_dates.Tpo -c ne_dates.c -o ne_dates.o >/dev/null 2>&1 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -DNE_HAVE_DAV -g -O2 -I.. -I../.. -I./imported/neon -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I../.. -I../.. -I../../libgnomevfs -I../../libgnomevfs -g -O2 -MT ne_uri.lo -MD -MP -MF .deps/ne_uri.Tpo -c ne_uri.c -o ne_uri.o >/dev/null 2>&1 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -DNE_HAVE_DAV -g -O2 -I.. -I../.. -I./imported/neon -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I../.. -I../.. -I../../libgnomevfs -I../../libgnomevfs -g -O2 -MT ne_compress.lo -MD -MP -MF .deps/ne_compress.Tpo -c ne_compress.c -o ne_compress.o >/dev/null 2>&1 mv -f .deps/ne_alloc.Tpo .deps/ne_alloc.Plo libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -DNE_HAVE_DAV -g -O2 -I.. -I../.. -I./imported/neon -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I../.. -I../.. -I../../libgnomevfs -I../../libgnomevfs -g -O2 -MT ne_redirect.lo -MD -MP -MF .deps/ne_redirect.Tpo -c ne_redirect.c -o ne_redirect.o >/dev/null 2>&1 /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -DNE_HAVE_DAV -g -O2 -I.. -I../.. -I./imported/neon -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I../.. -I../.. -I../../libgnomevfs -I../../libgnomevfs -g -O2 -MT ne_xmlreq.lo -MD -MP -MF .deps/ne_xmlreq.Tpo -c -o ne_xmlreq.lo ne_xmlreq.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -DNE_HAVE_DAV -g -O2 -I.. -I../.. -I./imported/neon -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I../.. -I../.. -I../../libgnomevfs -I../../libgnomevfs -g -O2 -MT ne_xmlreq.lo -MD -MP -MF .deps/ne_xmlreq.Tpo -c ne_xmlreq.c -fPIC -DPIC -o .libs/ne_xmlreq.o mv -f .deps/ne_dates.Tpo .deps/ne_dates.Plo libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -DNE_HAVE_DAV -g -O2 -I.. -I../.. -I./imported/neon -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I../.. -I../.. -I../../libgnomevfs -I../../libgnomevfs -g -O2 -MT ne_utils.lo -MD -MP -MF .deps/ne_utils.Tpo -c ne_utils.c -o ne_utils.o >/dev/null 2>&1 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -DNE_HAVE_DAV -g -O2 -I.. -I../.. -I./imported/neon -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I../.. -I../.. -I../../libgnomevfs -I../../libgnomevfs -g -O2 -MT ne_md5.lo -MD -MP -MF .deps/ne_md5.Tpo -c ne_md5.c -o ne_md5.o >/dev/null 2>&1 /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -DNE_HAVE_DAV -g -O2 -I.. -I../.. -I./imported/neon -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I../.. -I../.. -I../../libgnomevfs -I../../libgnomevfs -g -O2 -MT ne_acl.lo -MD -MP -MF .deps/ne_acl.Tpo -c -o ne_acl.lo ne_acl.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -DNE_HAVE_DAV -g -O2 -I.. -I../.. -I./imported/neon -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I../.. -I../.. -I../../libgnomevfs -I../../libgnomevfs -g -O2 -MT ne_session.lo -MD -MP -MF .deps/ne_session.Tpo -c ne_session.c -o ne_session.o >/dev/null 2>&1 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -DNE_HAVE_DAV -g -O2 -I.. -I../.. -I./imported/neon -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I../.. -I../.. -I../../libgnomevfs -I../../libgnomevfs -g -O2 -MT ne_acl.lo -MD -MP -MF .deps/ne_acl.Tpo -c ne_acl.c -fPIC -DPIC -o .libs/ne_acl.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -DNE_HAVE_DAV -g -O2 -I.. -I../.. -I./imported/neon -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I../.. -I../.. -I../../libgnomevfs -I../../libgnomevfs -g -O2 -MT ne_basic.lo -MD -MP -MF .deps/ne_basic.Tpo -c ne_basic.c -o ne_basic.o >/dev/null 2>&1 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -DNE_HAVE_DAV -g -O2 -I.. -I../.. -I./imported/neon -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I../.. -I../.. -I../../libgnomevfs -I../../libgnomevfs -g -O2 -MT ne_207.lo -MD -MP -MF .deps/ne_207.Tpo -c ne_207.c -o ne_207.o >/dev/null 2>&1 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -DNE_HAVE_DAV -g -O2 -I.. -I../.. -I./imported/neon -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I../.. -I../.. -I../../libgnomevfs -I../../libgnomevfs -g -O2 -MT ne_string.lo -MD -MP -MF .deps/ne_string.Tpo -c ne_string.c -o ne_string.o >/dev/null 2>&1 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -DNE_HAVE_DAV -g -O2 -I.. -I../.. -I./imported/neon -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I../.. -I../.. -I../../libgnomevfs -I../../libgnomevfs -g -O2 -MT ne_props.lo -MD -MP -MF .deps/ne_props.Tpo -c ne_props.c -o ne_props.o >/dev/null 2>&1 mv -f .deps/ne_compress.Tpo .deps/ne_compress.Plo /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -DNE_HAVE_DAV -g -O2 -I.. -I../.. -I./imported/neon -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I../.. -I../.. -I../../libgnomevfs -I../../libgnomevfs -g -O2 -MT ne_gnomevfs.lo -MD -MP -MF .deps/ne_gnomevfs.Tpo -c -o ne_gnomevfs.lo ne_gnomevfs.c mv -f .deps/ne_redirect.Tpo .deps/ne_redirect.Plo libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -DNE_HAVE_DAV -g -O2 -I.. -I../.. -I./imported/neon -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I../.. -I../.. -I../../libgnomevfs -I../../libgnomevfs -g -O2 -MT ne_xml.lo -MD -MP -MF .deps/ne_xml.Tpo -c ne_xml.c -o ne_xml.o >/dev/null 2>&1 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -DNE_HAVE_DAV -g -O2 -I.. -I../.. -I./imported/neon -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I../.. -I../.. -I../../libgnomevfs -I../../libgnomevfs -g -O2 -MT ne_gnomevfs.lo -MD -MP -MF .deps/ne_gnomevfs.Tpo -c ne_gnomevfs.c -fPIC -DPIC -o .libs/ne_gnomevfs.o mv -f .deps/ne_uri.Tpo .deps/ne_uri.Plo mv -f .deps/ne_utils.Tpo .deps/ne_utils.Plo libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -DNE_HAVE_DAV -g -O2 -I.. -I../.. -I./imported/neon -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I../.. -I../.. -I../../libgnomevfs -I../../libgnomevfs -g -O2 -MT ne_locks.lo -MD -MP -MF .deps/ne_locks.Tpo -c ne_locks.c -o ne_locks.o >/dev/null 2>&1 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -DNE_HAVE_DAV -g -O2 -I.. -I../.. -I./imported/neon -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I../.. -I../.. -I../../libgnomevfs -I../../libgnomevfs -g -O2 -MT ne_xmlreq.lo -MD -MP -MF .deps/ne_xmlreq.Tpo -c ne_xmlreq.c -o ne_xmlreq.o >/dev/null 2>&1 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -DNE_HAVE_DAV -g -O2 -I.. -I../.. -I./imported/neon -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I../.. -I../.. -I../../libgnomevfs -I../../libgnomevfs -g -O2 -MT ne_auth.lo -MD -MP -MF .deps/ne_auth.Tpo -c ne_auth.c -o ne_auth.o >/dev/null 2>&1 mv -f .deps/ne_session.Tpo .deps/ne_session.Plo libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -DNE_HAVE_DAV -g -O2 -I.. -I../.. -I./imported/neon -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I../.. -I../.. -I../../libgnomevfs -I../../libgnomevfs -g -O2 -MT ne_acl.lo -MD -MP -MF .deps/ne_acl.Tpo -c ne_acl.c -o ne_acl.o >/dev/null 2>&1 mv -f .deps/ne_207.Tpo .deps/ne_207.Plo In file included from ../../libgnomevfs/gnome-vfs-inet-connection.h:28, from ne_gnomevfs.c:38: ../../libgnomevfs/gnome-vfs-socket.h:124:8: warning: ‘GTimeVal’ is deprecated: Use 'GDateTime' instead [-Wdeprecated-declarations] 124 | GTimeVal *timeout, | ^~~~~~~~ In file included from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from ne_utils.h:32, from ne_request.h:25, from ne_private.h:28, from ne_gnomevfs.c:28: /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:547:8: note: declared here 547 | struct _GTimeVal | ^~~~~~~~~ In file included from ../../libgnomevfs/gnome-vfs-inet-connection.h:28, from ne_gnomevfs.c:38: ../../libgnomevfs/gnome-vfs-socket.h:163:8: warning: ‘GTimeVal’ is deprecated: Use 'GDateTime' instead [-Wdeprecated-declarations] 163 | GTimeVal *timeout, | ^~~~~~~~ In file included from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from ne_utils.h:32, from ne_request.h:25, from ne_private.h:28, from ne_gnomevfs.c:28: /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:547:8: note: declared here 547 | struct _GTimeVal | ^~~~~~~~~ In file included from ne_gnomevfs.c:39: ../../libgnomevfs/gnome-vfs-ssl.h:57:12: warning: ‘GTimeVal’ is deprecated: Use 'GDateTime' instead [-Wdeprecated-declarations] 57 | GTimeVal *timeout, | ^~~~~~~~ mv -f .deps/ne_string.Tpo .deps/ne_string.Plo In file included from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from ne_utils.h:32, from ne_request.h:25, from ne_private.h:28, from ne_gnomevfs.c:28: /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:547:8: note: declared here 547 | struct _GTimeVal | ^~~~~~~~~ ne_gnomevfs.c: In function ‘ne_sock_read_timeout’: ne_gnomevfs.c:465:2: warning: ‘GTimeVal’ is deprecated: Use 'GDateTime' instead [-Wdeprecated-declarations] 465 | GTimeVal tv; | ^~~~~~~~ In file included from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from ne_utils.h:32, from ne_request.h:25, from ne_private.h:28, from ne_gnomevfs.c:28: /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:547:8: note: declared here 547 | struct _GTimeVal | ^~~~~~~~~ mv -f .deps/ne_basic.Tpo .deps/ne_basic.Plo mv -f .deps/ne_xmlreq.Tpo .deps/ne_xmlreq.Plo mv -f .deps/ne_md5.Tpo .deps/ne_md5.Plo mv -f .deps/ne_props.Tpo .deps/ne_props.Plo libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -DNE_HAVE_DAV -g -O2 -I.. -I../.. -I./imported/neon -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I../.. -I../.. -I../../libgnomevfs -I../../libgnomevfs -g -O2 -MT ne_request.lo -MD -MP -MF .deps/ne_request.Tpo -c ne_request.c -o ne_request.o >/dev/null 2>&1 mv -f .deps/ne_xml.Tpo .deps/ne_xml.Plo mv -f .deps/ne_acl.Tpo .deps/ne_acl.Plo libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -DNE_HAVE_DAV -g -O2 -I.. -I../.. -I./imported/neon -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I../.. -I../.. -I../../libgnomevfs -I../../libgnomevfs -g -O2 -MT ne_gnomevfs.lo -MD -MP -MF .deps/ne_gnomevfs.Tpo -c ne_gnomevfs.c -o ne_gnomevfs.o >/dev/null 2>&1 mv -f .deps/ne_auth.Tpo .deps/ne_auth.Plo mv -f .deps/ne_locks.Tpo .deps/ne_locks.Plo mv -f .deps/ne_gnomevfs.Tpo .deps/ne_gnomevfs.Plo mv -f .deps/ne_request.Tpo .deps/ne_request.Plo /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../../libtool --tag=CC --mode=link gcc -g -O2 -o libneon.la ne_request.lo ne_session.lo ne_basic.lo ne_string.lo ne_uri.lo ne_dates.lo ne_alloc.lo ne_md5.lo ne_utils.lo ne_auth.lo ne_redirect.lo ne_compress.lo ne_207.lo ne_xml.lo ne_props.lo ne_locks.lo ne_xmlreq.lo ne_acl.lo ne_gnomevfs.lo -lz -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -lxml2 -lutil libtool: link: ar cru .libs/libneon.a .libs/ne_request.o .libs/ne_session.o .libs/ne_basic.o .libs/ne_string.o .libs/ne_uri.o .libs/ne_dates.o .libs/ne_alloc.o .libs/ne_md5.o .libs/ne_utils.o .libs/ne_auth.o .libs/ne_redirect.o .libs/ne_compress.o .libs/ne_207.o .libs/ne_xml.o .libs/ne_props.o .libs/ne_locks.o .libs/ne_xmlreq.o .libs/ne_acl.o .libs/ne_gnomevfs.o ar: `u' modifier ignored since `D' is the default (see `U') libtool: link: ranlib .libs/libneon.a libtool: link: ( cd ".libs" && rm -f "libneon.la" && ln -s "../libneon.la" "libneon.la" ) make[3]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/imported/neon' Making all in fnmatch make[3]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/imported/fnmatch' make[3]: Nothing to be done for 'all'. make[3]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/imported/fnmatch' make[3]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/imported' make[3]: Nothing to be done for 'all-am'. make[3]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/imported' make[2]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/imported' Making all in libgnomevfs make[2]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/libgnomevfs' (cd . && glib-mkenums \ --fhead "#ifndef __LIBGNOMEVFS_ENUM_TYPES_H__\n#define __LIBGNOMEVFS_ENUM_TYPES_H__\n\n#include \n\nG_BEGIN_DECLS\n" \ --fprod "/* enumerations from \"@filename@\" */\n" \ --vhead "GType @enum_name@_get_type (void);\n#define GNOME_VFS_TYPE_@ENUMSHORT@ (@enum_name@_get_type())\n" \ --ftail "G_END_DECLS\n\n#endif /* __LIBGNOMEVFS_ENUM_TYPES_H__ */" \ gnome-vfs-address.h gnome-vfs-application-registry.h gnome-vfs-async-ops.h gnome-vfs-cancellation.h gnome-vfs-context.h gnome-vfs-directory.h gnome-vfs-drive.h gnome-vfs-file-info.h gnome-vfs-file-size.h gnome-vfs-find-directory.h gnome-vfs-handle.h gnome-vfs-init.h gnome-vfs-job-limit.h gnome-vfs-mime.h gnome-vfs-mime-deprecated.h gnome-vfs-mime-handlers.h gnome-vfs-mime-info-cache.h gnome-vfs-mime-monitor.h gnome-vfs-mime-utils.h gnome-vfs-module-callback.h gnome-vfs-monitor.h gnome-vfs-ops.h gnome-vfs-resolve.h gnome-vfs-result.h gnome-vfs-standard-callbacks.h gnome-vfs-types.h gnome-vfs-utils.h gnome-vfs-volume.h gnome-vfs-volume-monitor.h gnome-vfs-xfer.h gnome-vfs.h ) > gnome-vfs-enum-types.h (cd . && glib-mkenums \ --fhead "#include \n" \ --fhead "#include \n" \ --fhead "#include " \ --fprod "\n/* enumerations from \"@filename@\" */" \ --vhead "GType\n@enum_name@_get_type (void)\n{\n static GType etype = 0;\n if (etype == 0) {\n static const G@Type@Value values[] = {" \ --vprod " { @VALUENAME@, \"@VALUENAME@\", \"@valuenick@\" }," \ --vtail " { 0, NULL, NULL }\n };\n etype = g_@type@_register_static (\"@EnumName@\", values);\n }\n return etype;\n}\n" \ gnome-vfs-address.h gnome-vfs-application-registry.h gnome-vfs-async-ops.h gnome-vfs-cancellation.h gnome-vfs-context.h gnome-vfs-directory.h gnome-vfs-drive.h gnome-vfs-file-info.h gnome-vfs-file-size.h gnome-vfs-find-directory.h gnome-vfs-handle.h gnome-vfs-init.h gnome-vfs-job-limit.h gnome-vfs-mime.h gnome-vfs-mime-deprecated.h gnome-vfs-mime-handlers.h gnome-vfs-mime-info-cache.h gnome-vfs-mime-monitor.h gnome-vfs-mime-utils.h gnome-vfs-module-callback.h gnome-vfs-monitor.h gnome-vfs-ops.h gnome-vfs-resolve.h gnome-vfs-result.h gnome-vfs-standard-callbacks.h gnome-vfs-types.h gnome-vfs-utils.h gnome-vfs-volume.h gnome-vfs-volume-monitor.h gnome-vfs-xfer.h gnome-vfs.h ) > gnome-vfs-enum-types.c make all-am make[3]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/libgnomevfs' /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-ace.lo -MD -MP -MF .deps/gnome-vfs-ace.Tpo -c -o gnome-vfs-ace.lo gnome-vfs-ace.c /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-acl.lo -MD -MP -MF .deps/gnome-vfs-acl.Tpo -c -o gnome-vfs-acl.lo gnome-vfs-acl.c /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-application-registry.lo -MD -MP -MF .deps/gnome-vfs-application-registry.Tpo -c -o gnome-vfs-application-registry.lo gnome-vfs-application-registry.c /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-address.lo -MD -MP -MF .deps/gnome-vfs-address.Tpo -c -o gnome-vfs-address.lo gnome-vfs-address.c /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-async-job-map.lo -MD -MP -MF .deps/gnome-vfs-async-job-map.Tpo -c -o gnome-vfs-async-job-map.lo gnome-vfs-async-job-map.c /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-async-ops.lo -MD -MP -MF .deps/gnome-vfs-async-ops.Tpo -c -o gnome-vfs-async-ops.lo gnome-vfs-async-ops.c /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-cancellable-ops.lo -MD -MP -MF .deps/gnome-vfs-cancellable-ops.Tpo -c -o gnome-vfs-cancellable-ops.lo gnome-vfs-cancellable-ops.c /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-cancellation.lo -MD -MP -MF .deps/gnome-vfs-cancellation.Tpo -c -o gnome-vfs-cancellation.lo gnome-vfs-cancellation.c /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-configuration.lo -MD -MP -MF .deps/gnome-vfs-configuration.Tpo -c -o gnome-vfs-configuration.lo gnome-vfs-configuration.c /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-context.lo -MD -MP -MF .deps/gnome-vfs-context.Tpo -c -o gnome-vfs-context.lo gnome-vfs-context.c /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-directory.lo -MD -MP -MF .deps/gnome-vfs-directory.Tpo -c -o gnome-vfs-directory.lo gnome-vfs-directory.c /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-drive.lo -MD -MP -MF .deps/gnome-vfs-drive.Tpo -c -o gnome-vfs-drive.lo gnome-vfs-drive.c /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-file-info.lo -MD -MP -MF .deps/gnome-vfs-file-info.Tpo -c -o gnome-vfs-file-info.lo gnome-vfs-file-info.c /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-filesystem-type.lo -MD -MP -MF .deps/gnome-vfs-filesystem-type.Tpo -c -o gnome-vfs-filesystem-type.lo gnome-vfs-filesystem-type.c /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-find-directory.lo -MD -MP -MF .deps/gnome-vfs-find-directory.Tpo -c -o gnome-vfs-find-directory.lo gnome-vfs-find-directory.c /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-handle.lo -MD -MP -MF .deps/gnome-vfs-handle.Tpo -c -o gnome-vfs-handle.lo gnome-vfs-handle.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-acl.lo -MD -MP -MF .deps/gnome-vfs-acl.Tpo -c gnome-vfs-acl.c -fPIC -DPIC -o .libs/gnome-vfs-acl.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-application-registry.lo -MD -MP -MF .deps/gnome-vfs-application-registry.Tpo -c gnome-vfs-application-registry.c -fPIC -DPIC -o .libs/gnome-vfs-application-registry.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-ace.lo -MD -MP -MF .deps/gnome-vfs-ace.Tpo -c gnome-vfs-ace.c -fPIC -DPIC -o .libs/gnome-vfs-ace.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-address.lo -MD -MP -MF .deps/gnome-vfs-address.Tpo -c gnome-vfs-address.c -fPIC -DPIC -o .libs/gnome-vfs-address.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-async-job-map.lo -MD -MP -MF .deps/gnome-vfs-async-job-map.Tpo -c gnome-vfs-async-job-map.c -fPIC -DPIC -o .libs/gnome-vfs-async-job-map.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-cancellable-ops.lo -MD -MP -MF .deps/gnome-vfs-cancellable-ops.Tpo -c gnome-vfs-cancellable-ops.c -fPIC -DPIC -o .libs/gnome-vfs-cancellable-ops.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-async-ops.lo -MD -MP -MF .deps/gnome-vfs-async-ops.Tpo -c gnome-vfs-async-ops.c -fPIC -DPIC -o .libs/gnome-vfs-async-ops.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-cancellation.lo -MD -MP -MF .deps/gnome-vfs-cancellation.Tpo -c gnome-vfs-cancellation.c -fPIC -DPIC -o .libs/gnome-vfs-cancellation.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-configuration.lo -MD -MP -MF .deps/gnome-vfs-configuration.Tpo -c gnome-vfs-configuration.c -fPIC -DPIC -o .libs/gnome-vfs-configuration.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-drive.lo -MD -MP -MF .deps/gnome-vfs-drive.Tpo -c gnome-vfs-drive.c -fPIC -DPIC -o .libs/gnome-vfs-drive.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-context.lo -MD -MP -MF .deps/gnome-vfs-context.Tpo -c gnome-vfs-context.c -fPIC -DPIC -o .libs/gnome-vfs-context.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-filesystem-type.lo -MD -MP -MF .deps/gnome-vfs-filesystem-type.Tpo -c gnome-vfs-filesystem-type.c -fPIC -DPIC -o .libs/gnome-vfs-filesystem-type.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-directory.lo -MD -MP -MF .deps/gnome-vfs-directory.Tpo -c gnome-vfs-directory.c -fPIC -DPIC -o .libs/gnome-vfs-directory.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-find-directory.lo -MD -MP -MF .deps/gnome-vfs-find-directory.Tpo -c gnome-vfs-find-directory.c -fPIC -DPIC -o .libs/gnome-vfs-find-directory.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-file-info.lo -MD -MP -MF .deps/gnome-vfs-file-info.Tpo -c gnome-vfs-file-info.c -fPIC -DPIC -o .libs/gnome-vfs-file-info.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-handle.lo -MD -MP -MF .deps/gnome-vfs-handle.Tpo -c gnome-vfs-handle.c -fPIC -DPIC -o .libs/gnome-vfs-handle.o In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/limits.h:26, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include/glibconfig.h:11, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from gnome-vfs-ace.h:28, from gnome-vfs-ace.c:26: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/limits.h:26, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include/glibconfig.h:11, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from gnome-vfs-async-ops.h:28, from gnome-vfs-async-ops.c:26: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/limits.h:26, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include/glibconfig.h:11, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from ../libgnomevfs/gnome-vfs-directory.h:27, from gnome-vfs-cancellable-ops.h:27, from gnome-vfs-cancellable-ops.c:29: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/limits.h:26, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include/glibconfig.h:11, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from ../libgnomevfs/gnome-vfs-result.h:29, from ../libgnomevfs/gnome-vfs-address.h:25, from gnome-vfs-address.c:22: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/string.h:26, from gnome-vfs-drive.c:25: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/unistd.h:25, from gnome-vfs-job.h:35, from gnome-vfs-async-job-map.h:30, from gnome-vfs-async-job-map.c:24: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/limits.h:26, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include/glibconfig.h:11, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from gnome-vfs-configuration.h:27, from gnome-vfs-configuration.c:25: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/limits.h:26, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include/glibconfig.h:11, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from gnome-vfs-cancellation.h:29, from gnome-vfs-cancellation-private.h:28, from gnome-vfs-cancellation.c:26: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/limits.h:26, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include/glibconfig.h:11, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from gnome-vfs-acl.h:28, from gnome-vfs-acl.c:25: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/limits.h:26, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include/glibconfig.h:11, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from gnome-vfs-directory.h:27, from gnome-vfs-directory.c:25: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/limits.h:26, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include/glibconfig.h:11, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from ../libgnomevfs/gnome-vfs-cancellation.h:29, from gnome-vfs-context.h:28, from gnome-vfs-context.c:24: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/limits.h:26, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include/glibconfig.h:11, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from ../libgnomevfs/gnome-vfs-result.h:29, from ../libgnomevfs/gnome-vfs-mime-handlers.h:28, from gnome-vfs-application-registry.h:41, from gnome-vfs-application-registry.c:29: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/limits.h:26, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include/glibconfig.h:11, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from ../libgnomevfs/gnome-vfs-file-size.h:29, from gnome-vfs-file-info.h:30, from gnome-vfs-file-info.c:26: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/limits.h:26, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include/glibconfig.h:11, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from ../libgnomevfs/gnome-vfs-cancellation.h:29, from ../libgnomevfs/gnome-vfs-context.h:28, from gnome-vfs-handle.h:27, from gnome-vfs-handle.c:25: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/string.h:26, from gnome-vfs-filesystem-type.c:25: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/limits.h:26, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include/glibconfig.h:11, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from ../libgnomevfs/gnome-vfs-result.h:29, from gnome-vfs-find-directory.h:31, from gnome-vfs-find-directory.c:26: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-filesystem-type.lo -MD -MP -MF .deps/gnome-vfs-filesystem-type.Tpo -c gnome-vfs-filesystem-type.c -o gnome-vfs-filesystem-type.o >/dev/null 2>&1 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-context.lo -MD -MP -MF .deps/gnome-vfs-context.Tpo -c gnome-vfs-context.c -o gnome-vfs-context.o >/dev/null 2>&1 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-handle.lo -MD -MP -MF .deps/gnome-vfs-handle.Tpo -c gnome-vfs-handle.c -o gnome-vfs-handle.o >/dev/null 2>&1 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-find-directory.lo -MD -MP -MF .deps/gnome-vfs-find-directory.Tpo -c gnome-vfs-find-directory.c -o gnome-vfs-find-directory.o >/dev/null 2>&1 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-async-job-map.lo -MD -MP -MF .deps/gnome-vfs-async-job-map.Tpo -c gnome-vfs-async-job-map.c -o gnome-vfs-async-job-map.o >/dev/null 2>&1 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-cancellation.lo -MD -MP -MF .deps/gnome-vfs-cancellation.Tpo -c gnome-vfs-cancellation.c -o gnome-vfs-cancellation.o >/dev/null 2>&1 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-file-info.lo -MD -MP -MF .deps/gnome-vfs-file-info.Tpo -c gnome-vfs-file-info.c -o gnome-vfs-file-info.o >/dev/null 2>&1 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-ace.lo -MD -MP -MF .deps/gnome-vfs-ace.Tpo -c gnome-vfs-ace.c -o gnome-vfs-ace.o >/dev/null 2>&1 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-address.lo -MD -MP -MF .deps/gnome-vfs-address.Tpo -c gnome-vfs-address.c -o gnome-vfs-address.o >/dev/null 2>&1 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-acl.lo -MD -MP -MF .deps/gnome-vfs-acl.Tpo -c gnome-vfs-acl.c -o gnome-vfs-acl.o >/dev/null 2>&1 mv -f .deps/gnome-vfs-filesystem-type.Tpo .deps/gnome-vfs-filesystem-type.Plo /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-inet-connection.lo -MD -MP -MF .deps/gnome-vfs-inet-connection.Tpo -c -o gnome-vfs-inet-connection.lo gnome-vfs-inet-connection.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-directory.lo -MD -MP -MF .deps/gnome-vfs-directory.Tpo -c gnome-vfs-directory.c -o gnome-vfs-directory.o >/dev/null 2>&1 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-inet-connection.lo -MD -MP -MF .deps/gnome-vfs-inet-connection.Tpo -c gnome-vfs-inet-connection.c -fPIC -DPIC -o .libs/gnome-vfs-inet-connection.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-drive.lo -MD -MP -MF .deps/gnome-vfs-drive.Tpo -c gnome-vfs-drive.c -o gnome-vfs-drive.o >/dev/null 2>&1 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-cancellable-ops.lo -MD -MP -MF .deps/gnome-vfs-cancellable-ops.Tpo -c gnome-vfs-cancellable-ops.c -o gnome-vfs-cancellable-ops.o >/dev/null 2>&1 In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/limits.h:26, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include/glibconfig.h:11, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from ../libgnomevfs/gnome-vfs-cancellation.h:29, from gnome-vfs-inet-connection.h:27, from gnome-vfs-inet-connection.c:25: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ mv -f .deps/gnome-vfs-context.Tpo .deps/gnome-vfs-context.Plo libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-configuration.lo -MD -MP -MF .deps/gnome-vfs-configuration.Tpo -c gnome-vfs-configuration.c -o gnome-vfs-configuration.o >/dev/null 2>&1 /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-init.lo -MD -MP -MF .deps/gnome-vfs-init.Tpo -c -o gnome-vfs-init.lo gnome-vfs-init.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-init.lo -MD -MP -MF .deps/gnome-vfs-init.Tpo -c gnome-vfs-init.c -fPIC -DPIC -o .libs/gnome-vfs-init.o In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/limits.h:26, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include/glibconfig.h:11, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from gnome-vfs-init.h:27, from gnome-vfs-init.c:25: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ mv -f .deps/gnome-vfs-handle.Tpo .deps/gnome-vfs-handle.Plo mv -f .deps/gnome-vfs-cancellation.Tpo .deps/gnome-vfs-cancellation.Plo /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-job-queue.lo -MD -MP -MF .deps/gnome-vfs-job-queue.Tpo -c -o gnome-vfs-job-queue.lo gnome-vfs-job-queue.c /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-job.lo -MD -MP -MF .deps/gnome-vfs-job.Tpo -c -o gnome-vfs-job.lo gnome-vfs-job.c mv -f .deps/gnome-vfs-find-directory.Tpo .deps/gnome-vfs-find-directory.Plo mv -f .deps/gnome-vfs-acl.Tpo .deps/gnome-vfs-acl.Plo /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-method.lo -MD -MP -MF .deps/gnome-vfs-method.Tpo -c -o gnome-vfs-method.lo gnome-vfs-method.c /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-mime-handlers.lo -MD -MP -MF .deps/gnome-vfs-mime-handlers.Tpo -c -o gnome-vfs-mime-handlers.lo gnome-vfs-mime-handlers.c mv -f .deps/gnome-vfs-async-job-map.Tpo .deps/gnome-vfs-async-job-map.Plo libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-job-queue.lo -MD -MP -MF .deps/gnome-vfs-job-queue.Tpo -c gnome-vfs-job-queue.c -fPIC -DPIC -o .libs/gnome-vfs-job-queue.o /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-mime-info.lo -MD -MP -MF .deps/gnome-vfs-mime-info.Tpo -c -o gnome-vfs-mime-info.lo gnome-vfs-mime-info.c mv -f .deps/gnome-vfs-file-info.Tpo .deps/gnome-vfs-file-info.Plo libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-job.lo -MD -MP -MF .deps/gnome-vfs-job.Tpo -c gnome-vfs-job.c -fPIC -DPIC -o .libs/gnome-vfs-job.o /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-mime-info-cache.lo -MD -MP -MF .deps/gnome-vfs-mime-info-cache.Tpo -c -o gnome-vfs-mime-info-cache.lo gnome-vfs-mime-info-cache.c In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/unistd.h:25, from gnome-vfs-job.h:35, from gnome-vfs-job-queue.h:29, from gnome-vfs-job-queue.c:25: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-async-ops.lo -MD -MP -MF .deps/gnome-vfs-async-ops.Tpo -c gnome-vfs-async-ops.c -o gnome-vfs-async-ops.o >/dev/null 2>&1 In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/unistd.h:25, from gnome-vfs-job.h:35, from gnome-vfs-job.c:31: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-mime-handlers.lo -MD -MP -MF .deps/gnome-vfs-mime-handlers.Tpo -c gnome-vfs-mime-handlers.c -fPIC -DPIC -o .libs/gnome-vfs-mime-handlers.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-method.lo -MD -MP -MF .deps/gnome-vfs-method.Tpo -c gnome-vfs-method.c -fPIC -DPIC -o .libs/gnome-vfs-method.o In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/unistd.h:25, from gnome-vfs-method.h:35, from gnome-vfs-method.c:25: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/limits.h:26, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include/glibconfig.h:11, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from ../libgnomevfs/gnome-vfs-result.h:29, from gnome-vfs-mime-handlers.h:28, from gnome-vfs-mime-handlers.c:25: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ mv -f .deps/gnome-vfs-address.Tpo .deps/gnome-vfs-address.Plo libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-mime-info.lo -MD -MP -MF .deps/gnome-vfs-mime-info.Tpo -c gnome-vfs-mime-info.c -fPIC -DPIC -o .libs/gnome-vfs-mime-info.o /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-mime-monitor.lo -MD -MP -MF .deps/gnome-vfs-mime-monitor.Tpo -c -o gnome-vfs-mime-monitor.lo gnome-vfs-mime-monitor.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-mime-info-cache.lo -MD -MP -MF .deps/gnome-vfs-mime-info-cache.Tpo -c gnome-vfs-mime-info-cache.c -fPIC -DPIC -o .libs/gnome-vfs-mime-info-cache.o In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/limits.h:26, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include/glibconfig.h:11, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from gnome-vfs-mime-info.h:27, from gnome-vfs-mime-info.c:31: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/errno.h:25, from gnome-vfs-mime-info-cache.c:25: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-mime-monitor.lo -MD -MP -MF .deps/gnome-vfs-mime-monitor.Tpo -c gnome-vfs-mime-monitor.c -fPIC -DPIC -o .libs/gnome-vfs-mime-monitor.o In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/limits.h:26, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include/glibconfig.h:11, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/gobject/gbinding.h:28, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib-object.h:22, from gnome-vfs-mime-monitor.h:28, from gnome-vfs-mime-monitor.c:26: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-init.lo -MD -MP -MF .deps/gnome-vfs-init.Tpo -c gnome-vfs-init.c -o gnome-vfs-init.o >/dev/null 2>&1 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-inet-connection.lo -MD -MP -MF .deps/gnome-vfs-inet-connection.Tpo -c gnome-vfs-inet-connection.c -o gnome-vfs-inet-connection.o >/dev/null 2>&1 mv -f .deps/gnome-vfs-directory.Tpo .deps/gnome-vfs-directory.Plo /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-mime-sniff-buffer.lo -MD -MP -MF .deps/gnome-vfs-mime-sniff-buffer.Tpo -c -o gnome-vfs-mime-sniff-buffer.lo gnome-vfs-mime-sniff-buffer.c mv -f .deps/gnome-vfs-drive.Tpo .deps/gnome-vfs-drive.Plo libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-job-queue.lo -MD -MP -MF .deps/gnome-vfs-job-queue.Tpo -c gnome-vfs-job-queue.c -o gnome-vfs-job-queue.o >/dev/null 2>&1 mv -f .deps/gnome-vfs-ace.Tpo .deps/gnome-vfs-ace.Plo /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-mime.lo -MD -MP -MF .deps/gnome-vfs-mime.Tpo -c -o gnome-vfs-mime.lo gnome-vfs-mime.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-mime-sniff-buffer.lo -MD -MP -MF .deps/gnome-vfs-mime-sniff-buffer.Tpo -c gnome-vfs-mime-sniff-buffer.c -fPIC -DPIC -o .libs/gnome-vfs-mime-sniff-buffer.o mv -f .deps/gnome-vfs-cancellable-ops.Tpo .deps/gnome-vfs-cancellable-ops.Plo /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-mime-magic.lo -MD -MP -MF .deps/gnome-vfs-mime-magic.Tpo -c -o gnome-vfs-mime-magic.lo gnome-vfs-mime-magic.c /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-module-callback-module-api.lo -MD -MP -MF .deps/gnome-vfs-module-callback-module-api.Tpo -c -o gnome-vfs-module-callback-module-api.lo gnome-vfs-module-callback-module-api.c In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/limits.h:26, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include/glibconfig.h:11, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from ../libgnomevfs/gnome-vfs-cancellation.h:29, from ../libgnomevfs/gnome-vfs-context.h:28, from ../libgnomevfs/gnome-vfs-handle.h:27, from gnome-vfs-mime-sniff-buffer.h:30, from gnome-vfs-mime-sniff-buffer.c:30: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-mime.lo -MD -MP -MF .deps/gnome-vfs-mime.Tpo -c gnome-vfs-mime.c -fPIC -DPIC -o .libs/gnome-vfs-mime.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-mime-magic.lo -MD -MP -MF .deps/gnome-vfs-mime-magic.Tpo -c gnome-vfs-mime-magic.c -fPIC -DPIC -o .libs/gnome-vfs-mime-magic.o In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/sys/stat.h:25, from gnome-vfs-mime.h:27, from gnome-vfs-mime.c:28: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-module-callback-module-api.lo -MD -MP -MF .deps/gnome-vfs-module-callback-module-api.Tpo -c gnome-vfs-module-callback-module-api.c -fPIC -DPIC -o .libs/gnome-vfs-module-callback-module-api.o In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/limits.h:26, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include/glibconfig.h:11, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from gnome-vfs-mime-magic.h:4, from gnome-vfs-mime-magic.c:17: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/limits.h:26, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include/glibconfig.h:11, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from gnome-vfs-module-callback-module-api.h:29, from gnome-vfs-module-callback-module-api.c:2: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ mv -f .deps/gnome-vfs-configuration.Tpo .deps/gnome-vfs-configuration.Plo /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-module-callback-private.lo -MD -MP -MF .deps/gnome-vfs-module-callback-private.Tpo -c -o gnome-vfs-module-callback-private.lo gnome-vfs-module-callback-private.c mv -f .deps/gnome-vfs-init.Tpo .deps/gnome-vfs-init.Plo /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-module-callback.lo -MD -MP -MF .deps/gnome-vfs-module-callback.Tpo -c -o gnome-vfs-module-callback.lo gnome-vfs-module-callback.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-mime-monitor.lo -MD -MP -MF .deps/gnome-vfs-mime-monitor.Tpo -c gnome-vfs-mime-monitor.c -o gnome-vfs-mime-monitor.o >/dev/null 2>&1 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-module-callback-private.lo -MD -MP -MF .deps/gnome-vfs-module-callback-private.Tpo -c gnome-vfs-module-callback-private.c -fPIC -DPIC -o .libs/gnome-vfs-module-callback-private.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-method.lo -MD -MP -MF .deps/gnome-vfs-method.Tpo -c gnome-vfs-method.c -o gnome-vfs-method.o >/dev/null 2>&1 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-mime-sniff-buffer.lo -MD -MP -MF .deps/gnome-vfs-mime-sniff-buffer.Tpo -c gnome-vfs-mime-sniff-buffer.c -o gnome-vfs-mime-sniff-buffer.o >/dev/null 2>&1 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-module-callback.lo -MD -MP -MF .deps/gnome-vfs-module-callback.Tpo -c gnome-vfs-module-callback.c -fPIC -DPIC -o .libs/gnome-vfs-module-callback.o In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/limits.h:26, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include/glibconfig.h:11, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from gnome-vfs-module-callback-private.h:27, from gnome-vfs-module-callback-private.c:2: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-mime-info.lo -MD -MP -MF .deps/gnome-vfs-mime-info.Tpo -c gnome-vfs-mime-info.c -o gnome-vfs-mime-info.o >/dev/null 2>&1 In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/limits.h:26, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include/glibconfig.h:11, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from gnome-vfs-module-callback.h:31, from gnome-vfs-module-callback.c:28: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ mv -f .deps/gnome-vfs-job-queue.Tpo .deps/gnome-vfs-job-queue.Plo /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-module-shared.lo -MD -MP -MF .deps/gnome-vfs-module-shared.Tpo -c -o gnome-vfs-module-shared.lo gnome-vfs-module-shared.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-module-callback-module-api.lo -MD -MP -MF .deps/gnome-vfs-module-callback-module-api.Tpo -c gnome-vfs-module-callback-module-api.c -o gnome-vfs-module-callback-module-api.o >/dev/null 2>&1 mv -f .deps/gnome-vfs-inet-connection.Tpo .deps/gnome-vfs-inet-connection.Plo /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-module.lo -MD -MP -MF .deps/gnome-vfs-module.Tpo -c -o gnome-vfs-module.lo gnome-vfs-module.c mv -f .deps/gnome-vfs-async-ops.Tpo .deps/gnome-vfs-async-ops.Plo libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-module-shared.lo -MD -MP -MF .deps/gnome-vfs-module-shared.Tpo -c gnome-vfs-module-shared.c -fPIC -DPIC -o .libs/gnome-vfs-module-shared.o /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-monitor.lo -MD -MP -MF .deps/gnome-vfs-monitor.Tpo -c -o gnome-vfs-monitor.lo gnome-vfs-monitor.c In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/limits.h:26, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include/glibconfig.h:11, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from ../libgnomevfs/gnome-vfs-file-size.h:29, from ../libgnomevfs/gnome-vfs-file-info.h:30, from gnome-vfs-module-shared.h:33, from gnome-vfs-module-shared.c:3: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-mime-magic.lo -MD -MP -MF .deps/gnome-vfs-mime-magic.Tpo -c gnome-vfs-mime-magic.c -o gnome-vfs-mime-magic.o >/dev/null 2>&1 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-mime-info-cache.lo -MD -MP -MF .deps/gnome-vfs-mime-info-cache.Tpo -c gnome-vfs-mime-info-cache.c -o gnome-vfs-mime-info-cache.o >/dev/null 2>&1 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-module.lo -MD -MP -MF .deps/gnome-vfs-module.Tpo -c gnome-vfs-module.c -fPIC -DPIC -o .libs/gnome-vfs-module.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-monitor.lo -MD -MP -MF .deps/gnome-vfs-monitor.Tpo -c gnome-vfs-monitor.c -fPIC -DPIC -o .libs/gnome-vfs-monitor.o In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/unistd.h:25, from ../libgnomevfs/gnome-vfs-method.h:35, from gnome-vfs-module.h:27, from gnome-vfs-module.c:2: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/sys/time.h:21, from gnome-vfs-monitor.c:24: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-module-callback-private.lo -MD -MP -MF .deps/gnome-vfs-module-callback-private.Tpo -c gnome-vfs-module-callback-private.c -o gnome-vfs-module-callback-private.o >/dev/null 2>&1 mv -f .deps/gnome-vfs-module-callback-module-api.Tpo .deps/gnome-vfs-module-callback-module-api.Plo /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-open-fd.lo -MD -MP -MF .deps/gnome-vfs-open-fd.Tpo -c -o gnome-vfs-open-fd.lo gnome-vfs-open-fd.c mv -f .deps/gnome-vfs-mime-sniff-buffer.Tpo .deps/gnome-vfs-mime-sniff-buffer.Plo /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-ops.lo -MD -MP -MF .deps/gnome-vfs-ops.Tpo -c -o gnome-vfs-ops.lo gnome-vfs-ops.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-open-fd.lo -MD -MP -MF .deps/gnome-vfs-open-fd.Tpo -c gnome-vfs-open-fd.c -fPIC -DPIC -o .libs/gnome-vfs-open-fd.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-job.lo -MD -MP -MF .deps/gnome-vfs-job.Tpo -c gnome-vfs-job.c -o gnome-vfs-job.o >/dev/null 2>&1 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-mime.lo -MD -MP -MF .deps/gnome-vfs-mime.Tpo -c gnome-vfs-mime.c -o gnome-vfs-mime.o >/dev/null 2>&1 In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/errno.h:25, from gnome-vfs-open-fd.c:25: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ mv -f .deps/gnome-vfs-mime-monitor.Tpo .deps/gnome-vfs-mime-monitor.Plo libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-mime-handlers.lo -MD -MP -MF .deps/gnome-vfs-mime-handlers.Tpo -c gnome-vfs-mime-handlers.c -o gnome-vfs-mime-handlers.o >/dev/null 2>&1 mv -f .deps/gnome-vfs-method.Tpo .deps/gnome-vfs-method.Plo libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-ops.lo -MD -MP -MF .deps/gnome-vfs-ops.Tpo -c gnome-vfs-ops.c -fPIC -DPIC -o .libs/gnome-vfs-ops.o /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-private-utils.lo -MD -MP -MF .deps/gnome-vfs-private-utils.Tpo -c -o gnome-vfs-private-utils.lo gnome-vfs-private-utils.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-application-registry.lo -MD -MP -MF .deps/gnome-vfs-application-registry.Tpo -c gnome-vfs-application-registry.c -o gnome-vfs-application-registry.o >/dev/null 2>&1 /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-private.lo -MD -MP -MF .deps/gnome-vfs-private.Tpo -c -o gnome-vfs-private.lo gnome-vfs-private.c In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/limits.h:26, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include/glibconfig.h:11, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from ../libgnomevfs/gnome-vfs-file-size.h:29, from ../libgnomevfs/gnome-vfs-file-info.h:30, from gnome-vfs-ops.h:29, from gnome-vfs-ops.c:25: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-module-shared.lo -MD -MP -MF .deps/gnome-vfs-module-shared.Tpo -c gnome-vfs-module-shared.c -o gnome-vfs-module-shared.o >/dev/null 2>&1 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-module.lo -MD -MP -MF .deps/gnome-vfs-module.Tpo -c gnome-vfs-module.c -o gnome-vfs-module.o >/dev/null 2>&1 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-private-utils.lo -MD -MP -MF .deps/gnome-vfs-private-utils.Tpo -c gnome-vfs-private-utils.c -fPIC -DPIC -o .libs/gnome-vfs-private-utils.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-private.lo -MD -MP -MF .deps/gnome-vfs-private.Tpo -c gnome-vfs-private.c -fPIC -DPIC -o .libs/gnome-vfs-private.o mv -f .deps/gnome-vfs-module-callback-private.Tpo .deps/gnome-vfs-module-callback-private.Plo In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/limits.h:26, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include/glibconfig.h:11, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from gnome-vfs-private.h:28, from gnome-vfs-private.c:2: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-resolve.lo -MD -MP -MF .deps/gnome-vfs-resolve.Tpo -c -o gnome-vfs-resolve.lo gnome-vfs-resolve.c In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/limits.h:26, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include/glibconfig.h:11, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from ../libgnomevfs/gnome-vfs-cancellation.h:29, from gnome-vfs-private-utils.h:31, from gnome-vfs-private-utils.c:29: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ mv -f .deps/gnome-vfs-mime-magic.Tpo .deps/gnome-vfs-mime-magic.Plo /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-result.lo -MD -MP -MF .deps/gnome-vfs-result.Tpo -c -o gnome-vfs-result.lo gnome-vfs-result.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-resolve.lo -MD -MP -MF .deps/gnome-vfs-resolve.Tpo -c gnome-vfs-resolve.c -fPIC -DPIC -o .libs/gnome-vfs-resolve.o In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/errno.h:25, from gnome-vfs-resolve.c:24: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-result.lo -MD -MP -MF .deps/gnome-vfs-result.Tpo -c gnome-vfs-result.c -fPIC -DPIC -o .libs/gnome-vfs-result.o In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/limits.h:26, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include/glibconfig.h:11, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from gnome-vfs-result.h:29, from gnome-vfs-result.c:30: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-module-callback.lo -MD -MP -MF .deps/gnome-vfs-module-callback.Tpo -c gnome-vfs-module-callback.c -o gnome-vfs-module-callback.o >/dev/null 2>&1 mv -f .deps/gnome-vfs-module.Tpo .deps/gnome-vfs-module.Plo mv -f .deps/gnome-vfs-mime-info.Tpo .deps/gnome-vfs-mime-info.Plo libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-private.lo -MD -MP -MF .deps/gnome-vfs-private.Tpo -c gnome-vfs-private.c -o gnome-vfs-private.o >/dev/null 2>&1 /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-socket-buffer.lo -MD -MP -MF .deps/gnome-vfs-socket-buffer.Tpo -c -o gnome-vfs-socket-buffer.lo gnome-vfs-socket-buffer.c /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-socket.lo -MD -MP -MF .deps/gnome-vfs-socket.Tpo -c -o gnome-vfs-socket.lo gnome-vfs-socket.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-monitor.lo -MD -MP -MF .deps/gnome-vfs-monitor.Tpo -c gnome-vfs-monitor.c -o gnome-vfs-monitor.o >/dev/null 2>&1 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-open-fd.lo -MD -MP -MF .deps/gnome-vfs-open-fd.Tpo -c gnome-vfs-open-fd.c -o gnome-vfs-open-fd.o >/dev/null 2>&1 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-socket-buffer.lo -MD -MP -MF .deps/gnome-vfs-socket-buffer.Tpo -c gnome-vfs-socket-buffer.c -fPIC -DPIC -o .libs/gnome-vfs-socket-buffer.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-socket.lo -MD -MP -MF .deps/gnome-vfs-socket.Tpo -c gnome-vfs-socket.c -fPIC -DPIC -o .libs/gnome-vfs-socket.o In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/limits.h:26, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include/glibconfig.h:11, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from gnome-vfs-socket.h:32, from gnome-vfs-socket-buffer.h:32, from gnome-vfs-socket-buffer.c:30: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/limits.h:26, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include/glibconfig.h:11, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from gnome-vfs-socket.h:32, from gnome-vfs-socket.c:30: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-result.lo -MD -MP -MF .deps/gnome-vfs-result.Tpo -c gnome-vfs-result.c -o gnome-vfs-result.o >/dev/null 2>&1 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-ops.lo -MD -MP -MF .deps/gnome-vfs-ops.Tpo -c gnome-vfs-ops.c -o gnome-vfs-ops.o >/dev/null 2>&1 mv -f .deps/gnome-vfs-module-shared.Tpo .deps/gnome-vfs-module-shared.Plo /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-ssl.lo -MD -MP -MF .deps/gnome-vfs-ssl.Tpo -c -o gnome-vfs-ssl.lo gnome-vfs-ssl.c mv -f .deps/gnome-vfs-mime.Tpo .deps/gnome-vfs-mime.Plo /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-transform.lo -MD -MP -MF .deps/gnome-vfs-transform.Tpo -c -o gnome-vfs-transform.lo gnome-vfs-transform.c mv -f .deps/gnome-vfs-mime-info-cache.Tpo .deps/gnome-vfs-mime-info-cache.Plo /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-uri.lo -MD -MP -MF .deps/gnome-vfs-uri.Tpo -c -o gnome-vfs-uri.lo gnome-vfs-uri.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-ssl.lo -MD -MP -MF .deps/gnome-vfs-ssl.Tpo -c gnome-vfs-ssl.c -fPIC -DPIC -o .libs/gnome-vfs-ssl.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-socket.lo -MD -MP -MF .deps/gnome-vfs-socket.Tpo -c gnome-vfs-socket.c -o gnome-vfs-socket.o >/dev/null 2>&1 In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/limits.h:26, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include/glibconfig.h:11, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from ../libgnomevfs/gnome-vfs-socket.h:32, from gnome-vfs-ssl.h:29, from gnome-vfs-ssl.c:33: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-transform.lo -MD -MP -MF .deps/gnome-vfs-transform.Tpo -c gnome-vfs-transform.c -fPIC -DPIC -o .libs/gnome-vfs-transform.o In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/limits.h:26, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include/glibconfig.h:11, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from ../libgnomevfs/gnome-vfs-result.h:29, from gnome-vfs-transform.h:28, from gnome-vfs-transform.c:2: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-resolve.lo -MD -MP -MF .deps/gnome-vfs-resolve.Tpo -c gnome-vfs-resolve.c -o gnome-vfs-resolve.o >/dev/null 2>&1 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-uri.lo -MD -MP -MF .deps/gnome-vfs-uri.Tpo -c gnome-vfs-uri.c -fPIC -DPIC -o .libs/gnome-vfs-uri.o mv -f .deps/gnome-vfs-private.Tpo .deps/gnome-vfs-private.Plo In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/limits.h:26, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include/glibconfig.h:11, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from gnome-vfs-uri.h:27, from gnome-vfs-uri.c:27: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-utils.lo -MD -MP -MF .deps/gnome-vfs-utils.Tpo -c -o gnome-vfs-utils.lo gnome-vfs-utils.c mv -f .deps/gnome-vfs-result.Tpo .deps/gnome-vfs-result.Plo /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-volume-monitor.lo -MD -MP -MF .deps/gnome-vfs-volume-monitor.Tpo -c -o gnome-vfs-volume-monitor.lo gnome-vfs-volume-monitor.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-utils.lo -MD -MP -MF .deps/gnome-vfs-utils.Tpo -c gnome-vfs-utils.c -fPIC -DPIC -o .libs/gnome-vfs-utils.o mv -f .deps/gnome-vfs-monitor.Tpo .deps/gnome-vfs-monitor.Plo /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-volume.lo -MD -MP -MF .deps/gnome-vfs-volume.Tpo -c -o gnome-vfs-volume.lo gnome-vfs-volume.c mv -f .deps/gnome-vfs-open-fd.Tpo .deps/gnome-vfs-open-fd.Plo /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-xfer.lo -MD -MP -MF .deps/gnome-vfs-xfer.Tpo -c -o gnome-vfs-xfer.lo gnome-vfs-xfer.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-socket-buffer.lo -MD -MP -MF .deps/gnome-vfs-socket-buffer.Tpo -c gnome-vfs-socket-buffer.c -o gnome-vfs-socket-buffer.o >/dev/null 2>&1 In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/sys/types.h:25, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/sys/param.h:25, from gnome-vfs-utils.c:31: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-volume-monitor.lo -MD -MP -MF .deps/gnome-vfs-volume-monitor.Tpo -c gnome-vfs-volume-monitor.c -fPIC -DPIC -o .libs/gnome-vfs-volume-monitor.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-transform.lo -MD -MP -MF .deps/gnome-vfs-transform.Tpo -c gnome-vfs-transform.c -o gnome-vfs-transform.o >/dev/null 2>&1 In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/string.h:26, from gnome-vfs-volume-monitor.c:26: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-volume.lo -MD -MP -MF .deps/gnome-vfs-volume.Tpo -c gnome-vfs-volume.c -fPIC -DPIC -o .libs/gnome-vfs-volume.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-xfer.lo -MD -MP -MF .deps/gnome-vfs-xfer.Tpo -c gnome-vfs-xfer.c -fPIC -DPIC -o .libs/gnome-vfs-xfer.o mv -f .deps/gnome-vfs-job.Tpo .deps/gnome-vfs-job.Plo libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-ssl.lo -MD -MP -MF .deps/gnome-vfs-ssl.Tpo -c gnome-vfs-ssl.c -o gnome-vfs-ssl.o >/dev/null 2>&1 In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/limits.h:26, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include/glibconfig.h:11, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from ../libgnomevfs/gnome-vfs-file-size.h:29, from ../libgnomevfs/gnome-vfs-file-info.h:30, from gnome-vfs-xfer.h:27, from gnome-vfs-xfer.c:37: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ mv -f .deps/gnome-vfs-socket.Tpo .deps/gnome-vfs-socket.Plo In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/string.h:26, from gnome-vfs-volume.c:25: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT xdgmimemagic.lo -MD -MP -MF .deps/xdgmimemagic.Tpo -c -o xdgmimemagic.lo xdgmimemagic.c /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT xdgmime.lo -MD -MP -MF .deps/xdgmime.Tpo -c -o xdgmime.lo xdgmime.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT xdgmimemagic.lo -MD -MP -MF .deps/xdgmimemagic.Tpo -c xdgmimemagic.c -fPIC -DPIC -o .libs/xdgmimemagic.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT xdgmime.lo -MD -MP -MF .deps/xdgmime.Tpo -c xdgmime.c -fPIC -DPIC -o .libs/xdgmime.o mv -f .deps/gnome-vfs-ops.Tpo .deps/gnome-vfs-ops.Plo /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT xdgmimecache.lo -MD -MP -MF .deps/xdgmimecache.Tpo -c -o xdgmimecache.lo xdgmimecache.c In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/stdlib.h:25, from xdgmime.h:32, from xdgmime.c:32: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/assert.h:35, from xdgmimemagic.c:32: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ mv -f .deps/gnome-vfs-resolve.Tpo .deps/gnome-vfs-resolve.Plo /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT xdgmimeglob.lo -MD -MP -MF .deps/xdgmimeglob.Tpo -c -o xdgmimeglob.lo xdgmimeglob.c mv -f .deps/gnome-vfs-transform.Tpo .deps/gnome-vfs-transform.Plo /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT xdgmimeint.lo -MD -MP -MF .deps/xdgmimeint.Tpo -c -o xdgmimeint.lo xdgmimeint.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT xdgmimecache.lo -MD -MP -MF .deps/xdgmimecache.Tpo -c xdgmimecache.c -fPIC -DPIC -o .libs/xdgmimecache.o In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/stdio.h:27, from xdgmimecache.c:31: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT xdgmimeglob.lo -MD -MP -MF .deps/xdgmimeglob.Tpo -c xdgmimeglob.c -fPIC -DPIC -o .libs/xdgmimeglob.o In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/stdlib.h:25, from xdgmime.h:32, from xdgmimeglob.h:31, from xdgmimeglob.c:32: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT xdgmimeint.lo -MD -MP -MF .deps/xdgmimeint.Tpo -c xdgmimeint.c -fPIC -DPIC -o .libs/xdgmimeint.o In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/stdlib.h:25, from xdgmime.h:32, from xdgmimeint.h:31, from xdgmimeint.c:32: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-private-utils.lo -MD -MP -MF .deps/gnome-vfs-private-utils.Tpo -c gnome-vfs-private-utils.c -o gnome-vfs-private-utils.o >/dev/null 2>&1 mv -f .deps/gnome-vfs-ssl.Tpo .deps/gnome-vfs-ssl.Plo /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT xdgmimealias.lo -MD -MP -MF .deps/xdgmimealias.Tpo -c -o xdgmimealias.lo xdgmimealias.c mv -f .deps/gnome-vfs-mime-handlers.Tpo .deps/gnome-vfs-mime-handlers.Plo /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT xdgmimeparent.lo -MD -MP -MF .deps/xdgmimeparent.Tpo -c -o xdgmimeparent.lo xdgmimeparent.c mv -f .deps/gnome-vfs-socket-buffer.Tpo .deps/gnome-vfs-socket-buffer.Plo mv -f .deps/gnome-vfs-module-callback.Tpo .deps/gnome-vfs-module-callback.Plo /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT xdgmimeicon.lo -MD -MP -MF .deps/xdgmimeicon.Tpo -c -o xdgmimeicon.lo xdgmimeicon.c /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-enum-types.lo -MD -MP -MF .deps/gnome-vfs-enum-types.Tpo -c -o gnome-vfs-enum-types.lo gnome-vfs-enum-types.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT xdgmimealias.lo -MD -MP -MF .deps/xdgmimealias.Tpo -c xdgmimealias.c -fPIC -DPIC -o .libs/xdgmimealias.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT xdgmimeparent.lo -MD -MP -MF .deps/xdgmimeparent.Tpo -c xdgmimeparent.c -fPIC -DPIC -o .libs/xdgmimeparent.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT xdgmimeint.lo -MD -MP -MF .deps/xdgmimeint.Tpo -c xdgmimeint.c -o xdgmimeint.o >/dev/null 2>&1 In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/stdlib.h:25, from xdgmime.h:32, from xdgmimealias.h:31, from xdgmimealias.c:32: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/stdlib.h:25, from xdgmime.h:32, from xdgmimeparent.h:31, from xdgmimeparent.c:32: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT xdgmimeicon.lo -MD -MP -MF .deps/xdgmimeicon.Tpo -c xdgmimeicon.c -fPIC -DPIC -o .libs/xdgmimeicon.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-enum-types.lo -MD -MP -MF .deps/gnome-vfs-enum-types.Tpo -c gnome-vfs-enum-types.c -fPIC -DPIC -o .libs/gnome-vfs-enum-types.o In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/stdlib.h:25, from xdgmime.h:32, from xdgmimeicon.h:30, from xdgmimeicon.c:31: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/limits.h:26, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include/glibconfig.h:11, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from ../libgnomevfs/gnome-vfs-acl.h:28, from ../libgnomevfs/gnome-vfs.h:28, from gnome-vfs-enum-types.c:4: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ mv -f .deps/gnome-vfs-application-registry.Tpo .deps/gnome-vfs-application-registry.Plo libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-volume.lo -MD -MP -MF .deps/gnome-vfs-volume.Tpo -c gnome-vfs-volume.c -o gnome-vfs-volume.o >/dev/null 2>&1 /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-cdrom.lo -MD -MP -MF .deps/gnome-vfs-cdrom.Tpo -c -o gnome-vfs-cdrom.lo gnome-vfs-cdrom.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT xdgmime.lo -MD -MP -MF .deps/xdgmime.Tpo -c xdgmime.c -o xdgmime.o >/dev/null 2>&1 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT xdgmimeicon.lo -MD -MP -MF .deps/xdgmimeicon.Tpo -c xdgmimeicon.c -o xdgmimeicon.o >/dev/null 2>&1 mv -f .deps/xdgmimeint.Tpo .deps/xdgmimeint.Plo libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT xdgmimeglob.lo -MD -MP -MF .deps/xdgmimeglob.Tpo -c xdgmimeglob.c -o xdgmimeglob.o >/dev/null 2>&1 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT xdgmimealias.lo -MD -MP -MF .deps/xdgmimealias.Tpo -c xdgmimealias.c -o xdgmimealias.o >/dev/null 2>&1 /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-daemon-method.lo -MD -MP -MF .deps/gnome-vfs-daemon-method.Tpo -c -o gnome-vfs-daemon-method.lo gnome-vfs-daemon-method.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-volume-monitor.lo -MD -MP -MF .deps/gnome-vfs-volume-monitor.Tpo -c gnome-vfs-volume-monitor.c -o gnome-vfs-volume-monitor.o >/dev/null 2>&1 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-cdrom.lo -MD -MP -MF .deps/gnome-vfs-cdrom.Tpo -c gnome-vfs-cdrom.c -fPIC -DPIC -o .libs/gnome-vfs-cdrom.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT xdgmimemagic.lo -MD -MP -MF .deps/xdgmimemagic.Tpo -c xdgmimemagic.c -o xdgmimemagic.o >/dev/null 2>&1 In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/sys/types.h:25, from gnome-vfs-cdrom.c:28: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT xdgmimeparent.lo -MD -MP -MF .deps/xdgmimeparent.Tpo -c xdgmimeparent.c -o xdgmimeparent.o >/dev/null 2>&1 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-daemon-method.lo -MD -MP -MF .deps/gnome-vfs-daemon-method.Tpo -c gnome-vfs-daemon-method.c -fPIC -DPIC -o .libs/gnome-vfs-daemon-method.o In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/stdlib.h:25, from gnome-vfs-daemon-method.c:22: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ mv -f .deps/xdgmimeicon.Tpo .deps/xdgmimeicon.Plo /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-dbus-utils.lo -MD -MP -MF .deps/gnome-vfs-dbus-utils.Tpo -c -o gnome-vfs-dbus-utils.lo gnome-vfs-dbus-utils.c mv -f .deps/xdgmimealias.Tpo .deps/xdgmimealias.Plo /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-dns-sd.lo -MD -MP -MF .deps/gnome-vfs-dns-sd.Tpo -c -o gnome-vfs-dns-sd.lo gnome-vfs-dns-sd.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-dbus-utils.lo -MD -MP -MF .deps/gnome-vfs-dbus-utils.Tpo -c gnome-vfs-dbus-utils.c -fPIC -DPIC -o .libs/gnome-vfs-dbus-utils.o In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/string.h:26, from gnome-vfs-dbus-utils.c:25: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ mv -f .deps/xdgmimeparent.Tpo .deps/xdgmimeparent.Plo libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-dns-sd.lo -MD -MP -MF .deps/gnome-vfs-dns-sd.Tpo -c gnome-vfs-dns-sd.c -fPIC -DPIC -o .libs/gnome-vfs-dns-sd.o /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-module-callback-marshall.lo -MD -MP -MF .deps/gnome-vfs-module-callback-marshall.Tpo -c -o gnome-vfs-module-callback-marshall.lo gnome-vfs-module-callback-marshall.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-enum-types.lo -MD -MP -MF .deps/gnome-vfs-enum-types.Tpo -c gnome-vfs-enum-types.c -o gnome-vfs-enum-types.o >/dev/null 2>&1 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT xdgmimecache.lo -MD -MP -MF .deps/xdgmimecache.Tpo -c xdgmimecache.c -o xdgmimecache.o >/dev/null 2>&1 In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/unistd.h:25, from gnome-vfs-dns-sd.c:27: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-module-callback-marshall.lo -MD -MP -MF .deps/gnome-vfs-module-callback-marshall.Tpo -c gnome-vfs-module-callback-marshall.c -fPIC -DPIC -o .libs/gnome-vfs-module-callback-marshall.o In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/string.h:26, from gnome-vfs-module-callback-marshall.c:26: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-uri.lo -MD -MP -MF .deps/gnome-vfs-uri.Tpo -c gnome-vfs-uri.c -o gnome-vfs-uri.o >/dev/null 2>&1 mv -f .deps/gnome-vfs-private-utils.Tpo .deps/gnome-vfs-private-utils.Plo /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-parse-ls.lo -MD -MP -MF .deps/gnome-vfs-parse-ls.Tpo -c -o gnome-vfs-parse-ls.lo gnome-vfs-parse-ls.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-cdrom.lo -MD -MP -MF .deps/gnome-vfs-cdrom.Tpo -c gnome-vfs-cdrom.c -o gnome-vfs-cdrom.o >/dev/null 2>&1 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-parse-ls.lo -MD -MP -MF .deps/gnome-vfs-parse-ls.Tpo -c gnome-vfs-parse-ls.c -fPIC -DPIC -o .libs/gnome-vfs-parse-ls.o mv -f .deps/xdgmimeglob.Tpo .deps/xdgmimeglob.Plo mv -f .deps/gnome-vfs-volume.Tpo .deps/gnome-vfs-volume.Plo /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-pty.lo -MD -MP -MF .deps/gnome-vfs-pty.Tpo -c -o gnome-vfs-pty.lo gnome-vfs-pty.c /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-volume-monitor-client.lo -MD -MP -MF .deps/gnome-vfs-volume-monitor-client.Tpo -c -o gnome-vfs-volume-monitor-client.lo gnome-vfs-volume-monitor-client.c mv -f .deps/xdgmimemagic.Tpo .deps/xdgmimemagic.Plo In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/sys/stat.h:25, from gnome-vfs-parse-ls.h:31, from gnome-vfs-parse-ls.c:29: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ mv -f .deps/xdgmime.Tpo .deps/xdgmime.Plo /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-volume-ops.lo -MD -MP -MF .deps/gnome-vfs-volume-ops.Tpo -c -o gnome-vfs-volume-ops.lo gnome-vfs-volume-ops.c /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-hal-mounts.lo -MD -MP -MF .deps/gnome-vfs-hal-mounts.Tpo -c -o gnome-vfs-hal-mounts.lo gnome-vfs-hal-mounts.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-dbus-utils.lo -MD -MP -MF .deps/gnome-vfs-dbus-utils.Tpo -c gnome-vfs-dbus-utils.c -o gnome-vfs-dbus-utils.o >/dev/null 2>&1 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-pty.lo -MD -MP -MF .deps/gnome-vfs-pty.Tpo -c gnome-vfs-pty.c -fPIC -DPIC -o .libs/gnome-vfs-pty.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-volume-monitor-client.lo -MD -MP -MF .deps/gnome-vfs-volume-monitor-client.Tpo -c gnome-vfs-volume-monitor-client.c -fPIC -DPIC -o .libs/gnome-vfs-volume-monitor-client.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-volume-ops.lo -MD -MP -MF .deps/gnome-vfs-volume-ops.Tpo -c gnome-vfs-volume-ops.c -fPIC -DPIC -o .libs/gnome-vfs-volume-ops.o In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/sys/types.h:25, from gnome-vfs-pty.c:22: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-hal-mounts.lo -MD -MP -MF .deps/gnome-vfs-hal-mounts.Tpo -c gnome-vfs-hal-mounts.c -fPIC -DPIC -o .libs/gnome-vfs-hal-mounts.o In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/string.h:26, from gnome-vfs-volume-monitor-client.c:26: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/sys/types.h:25, from gnome-vfs-volume-ops.c:26: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-hal-mounts.lo -MD -MP -MF .deps/gnome-vfs-hal-mounts.Tpo -c gnome-vfs-hal-mounts.c -o gnome-vfs-hal-mounts.o >/dev/null 2>&1 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-utils.lo -MD -MP -MF .deps/gnome-vfs-utils.Tpo -c gnome-vfs-utils.c -o gnome-vfs-utils.o >/dev/null 2>&1 mv -f .deps/gnome-vfs-hal-mounts.Tpo .deps/gnome-vfs-hal-mounts.Plo /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-volume-monitor-daemon.lo -MD -MP -MF .deps/gnome-vfs-volume-monitor-daemon.Tpo -c -o gnome-vfs-volume-monitor-daemon.lo gnome-vfs-volume-monitor-daemon.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-volume-monitor-daemon.lo -MD -MP -MF .deps/gnome-vfs-volume-monitor-daemon.Tpo -c gnome-vfs-volume-monitor-daemon.c -fPIC -DPIC -o .libs/gnome-vfs-volume-monitor-daemon.o mv -f .deps/gnome-vfs-cdrom.Tpo .deps/gnome-vfs-cdrom.Plo In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/string.h:26, from gnome-vfs-volume-monitor-daemon.c:26: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-unix-mounts.lo -MD -MP -MF .deps/gnome-vfs-unix-mounts.Tpo -c -o gnome-vfs-unix-mounts.lo gnome-vfs-unix-mounts.c mv -f .deps/gnome-vfs-volume-monitor.Tpo .deps/gnome-vfs-volume-monitor.Plo libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-unix-mounts.lo -MD -MP -MF .deps/gnome-vfs-unix-mounts.Tpo -c gnome-vfs-unix-mounts.c -fPIC -DPIC -o .libs/gnome-vfs-unix-mounts.o mv -f .deps/gnome-vfs-dbus-utils.Tpo .deps/gnome-vfs-dbus-utils.Plo In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/sys/types.h:25, from gnome-vfs-unix-mounts.c:26: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ mv -f .deps/gnome-vfs-enum-types.Tpo .deps/gnome-vfs-enum-types.Plo mv -f .deps/xdgmimecache.Tpo .deps/xdgmimecache.Plo libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-pty.lo -MD -MP -MF .deps/gnome-vfs-pty.Tpo -c gnome-vfs-pty.c -o gnome-vfs-pty.o >/dev/null 2>&1 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-volume-monitor-client.lo -MD -MP -MF .deps/gnome-vfs-volume-monitor-client.Tpo -c gnome-vfs-volume-monitor-client.c -o gnome-vfs-volume-monitor-client.o >/dev/null 2>&1 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-dns-sd.lo -MD -MP -MF .deps/gnome-vfs-dns-sd.Tpo -c gnome-vfs-dns-sd.c -o gnome-vfs-dns-sd.o >/dev/null 2>&1 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-parse-ls.lo -MD -MP -MF .deps/gnome-vfs-parse-ls.Tpo -c gnome-vfs-parse-ls.c -o gnome-vfs-parse-ls.o >/dev/null 2>&1 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-xfer.lo -MD -MP -MF .deps/gnome-vfs-xfer.Tpo -c gnome-vfs-xfer.c -o gnome-vfs-xfer.o >/dev/null 2>&1 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-daemon-method.lo -MD -MP -MF .deps/gnome-vfs-daemon-method.Tpo -c gnome-vfs-daemon-method.c -o gnome-vfs-daemon-method.o >/dev/null 2>&1 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-module-callback-marshall.lo -MD -MP -MF .deps/gnome-vfs-module-callback-marshall.Tpo -c gnome-vfs-module-callback-marshall.c -o gnome-vfs-module-callback-marshall.o >/dev/null 2>&1 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-unix-mounts.lo -MD -MP -MF .deps/gnome-vfs-unix-mounts.Tpo -c gnome-vfs-unix-mounts.c -o gnome-vfs-unix-mounts.o >/dev/null 2>&1 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-volume-ops.lo -MD -MP -MF .deps/gnome-vfs-volume-ops.Tpo -c gnome-vfs-volume-ops.c -o gnome-vfs-volume-ops.o >/dev/null 2>&1 mv -f .deps/gnome-vfs-volume-monitor-client.Tpo .deps/gnome-vfs-volume-monitor-client.Plo mv -f .deps/gnome-vfs-pty.Tpo .deps/gnome-vfs-pty.Plo mv -f .deps/gnome-vfs-uri.Tpo .deps/gnome-vfs-uri.Plo mv -f .deps/gnome-vfs-parse-ls.Tpo .deps/gnome-vfs-parse-ls.Plo libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DXDG_PREFIX=_gnome_vfs_xdg -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_BINDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -g -O2 -MT gnome-vfs-volume-monitor-daemon.lo -MD -MP -MF .deps/gnome-vfs-volume-monitor-daemon.Tpo -c gnome-vfs-volume-monitor-daemon.c -o gnome-vfs-volume-monitor-daemon.o >/dev/null 2>&1 mv -f .deps/gnome-vfs-utils.Tpo .deps/gnome-vfs-utils.Plo mv -f .deps/gnome-vfs-unix-mounts.Tpo .deps/gnome-vfs-unix-mounts.Plo mv -f .deps/gnome-vfs-dns-sd.Tpo .deps/gnome-vfs-dns-sd.Plo mv -f .deps/gnome-vfs-module-callback-marshall.Tpo .deps/gnome-vfs-module-callback-marshall.Plo mv -f .deps/gnome-vfs-daemon-method.Tpo .deps/gnome-vfs-daemon-method.Plo mv -f .deps/gnome-vfs-volume-ops.Tpo .deps/gnome-vfs-volume-ops.Plo mv -f .deps/gnome-vfs-volume-monitor-daemon.Tpo .deps/gnome-vfs-volume-monitor-daemon.Plo mv -f .deps/gnome-vfs-xfer.Tpo .deps/gnome-vfs-xfer.Plo /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -version-info 2400:4:2400 -no-undefined -export-symbols-regex "^[^_].*" -o libgnomevfs-2.la -rpath /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib gnome-vfs-ace.lo gnome-vfs-acl.lo gnome-vfs-application-registry.lo gnome-vfs-address.lo gnome-vfs-async-job-map.lo gnome-vfs-async-ops.lo gnome-vfs-cancellable-ops.lo gnome-vfs-cancellation.lo gnome-vfs-configuration.lo gnome-vfs-context.lo gnome-vfs-directory.lo gnome-vfs-drive.lo gnome-vfs-file-info.lo gnome-vfs-filesystem-type.lo gnome-vfs-find-directory.lo gnome-vfs-handle.lo gnome-vfs-inet-connection.lo gnome-vfs-init.lo gnome-vfs-job-queue.lo gnome-vfs-job.lo gnome-vfs-method.lo gnome-vfs-mime-handlers.lo gnome-vfs-mime-info.lo gnome-vfs-mime-info-cache.lo gnome-vfs-mime-monitor.lo gnome-vfs-mime-sniff-buffer.lo gnome-vfs-mime.lo gnome-vfs-mime-magic.lo gnome-vfs-module-callback-module-api.lo gnome-vfs-module-callback-private.lo gnome-vfs-module-callback.lo gnome-vfs-module-shared.lo gnome-vfs-module.lo gnome-vfs-monitor.lo gnome-vfs-open-fd.lo gnome-vfs-ops.lo gnome-vfs-private-utils.lo gnome-vfs-private.lo gnome-vfs-resolve.lo gnome-vfs-result.lo gnome-vfs-socket-buffer.lo gnome-vfs-socket.lo gnome-vfs-ssl.lo gnome-vfs-transform.lo gnome-vfs-uri.lo gnome-vfs-utils.lo gnome-vfs-volume-monitor.lo gnome-vfs-volume.lo gnome-vfs-xfer.lo xdgmimemagic.lo xdgmime.lo xdgmimecache.lo xdgmimeglob.lo xdgmimeint.lo xdgmimealias.lo xdgmimeparent.lo xdgmimeicon.lo gnome-vfs-enum-types.lo gnome-vfs-cdrom.lo gnome-vfs-daemon-method.lo gnome-vfs-dbus-utils.lo gnome-vfs-dns-sd.lo gnome-vfs-module-callback-marshall.lo gnome-vfs-parse-ls.lo gnome-vfs-pty.lo gnome-vfs-volume-monitor-client.lo gnome-vfs-volume-ops.lo -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -lgmodule-2.0 -pthread -lgthread-2.0 -pthread -lgconf-2 -lxml2 -ldbus-glib-1 -ldbus-1 -lgobject-2.0 -lglib-2.0 -lresolv -lutil libtool: link: /gnu/store/v4a7zw8w52v64kw5781ypa8gjwd098jz-binutils-2.37/bin/nm -B .libs/gnome-vfs-ace.o .libs/gnome-vfs-acl.o .libs/gnome-vfs-application-registry.o .libs/gnome-vfs-address.o .libs/gnome-vfs-async-job-map.o .libs/gnome-vfs-async-ops.o .libs/gnome-vfs-cancellable-ops.o .libs/gnome-vfs-cancellation.o .libs/gnome-vfs-configuration.o .libs/gnome-vfs-context.o .libs/gnome-vfs-directory.o .libs/gnome-vfs-drive.o .libs/gnome-vfs-file-info.o .libs/gnome-vfs-filesystem-type.o .libs/gnome-vfs-find-directory.o .libs/gnome-vfs-handle.o .libs/gnome-vfs-inet-connection.o .libs/gnome-vfs-init.o .libs/gnome-vfs-job-queue.o .libs/gnome-vfs-job.o .libs/gnome-vfs-method.o .libs/gnome-vfs-mime-handlers.o .libs/gnome-vfs-mime-info.o .libs/gnome-vfs-mime-info-cache.o .libs/gnome-vfs-mime-monitor.o .libs/gnome-vfs-mime-sniff-buffer.o .libs/gnome-vfs-mime.o .libs/gnome-vfs-mime-magic.o .libs/gnome-vfs-module-callback-module-api.o .libs/gnome-vfs-module-callback-private.o .libs/gnome-vfs-module-callback.o .libs/gnome-vfs-module-shared.o .libs/gnome-vfs-module.o .libs/gnome-vfs-monitor.o .libs/gnome-vfs-open-fd.o .libs/gnome-vfs-ops.o .libs/gnome-vfs-private-utils.o .libs/gnome-vfs-private.o .libs/gnome-vfs-resolve.o .libs/gnome-vfs-result.o .libs/gnome-vfs-socket-buffer.o .libs/gnome-vfs-socket.o .libs/gnome-vfs-ssl.o .libs/gnome-vfs-transform.o .libs/gnome-vfs-uri.o .libs/gnome-vfs-utils.o .libs/gnome-vfs-volume-monitor.o .libs/gnome-vfs-volume.o .libs/gnome-vfs-xfer.o .libs/xdgmimemagic.o .libs/xdgmime.o .libs/xdgmimecache.o .libs/xdgmimeglob.o .libs/xdgmimeint.o .libs/xdgmimealias.o .libs/xdgmimeparent.o .libs/xdgmimeicon.o .libs/gnome-vfs-enum-types.o .libs/gnome-vfs-cdrom.o .libs/gnome-vfs-daemon-method.o .libs/gnome-vfs-dbus-utils.o .libs/gnome-vfs-dns-sd.o .libs/gnome-vfs-module-callback-marshall.o .libs/gnome-vfs-parse-ls.o .libs/gnome-vfs-pty.o .libs/gnome-vfs-volume-monitor-client.o .libs/gnome-vfs-volume-ops.o | sed -n -e 's/^.*[ ]\([ABCDGIRSTW][ABCDGIRSTW]*\)[ ][ ]*\([_A-Za-z][_A-Za-z0-9]*\)$/\1 \2 \2/p' | /gnu/store/cnwr7widbi6470kfyb13krx46kz5anmy-sed-4.8/bin/sed 's/.* //' | sort | uniq > .libs/libgnomevfs-2.exp libtool: link: /gnu/store/bx47clwnxn51m7jdwfimz4lw2fh8g21v-grep-3.6/bin/grep -E -e "^[^_].*" ".libs/libgnomevfs-2.exp" > ".libs/libgnomevfs-2.expT" libtool: link: mv -f ".libs/libgnomevfs-2.expT" ".libs/libgnomevfs-2.exp" libtool: link: echo "{ global:" > .libs/libgnomevfs-2.ver libtool: link: cat .libs/libgnomevfs-2.exp | sed -e "s/\(.*\)/\1;/" >> .libs/libgnomevfs-2.ver libtool: link: echo "local: *; };" >> .libs/libgnomevfs-2.ver libtool: link: gcc -shared .libs/gnome-vfs-ace.o .libs/gnome-vfs-acl.o .libs/gnome-vfs-application-registry.o .libs/gnome-vfs-address.o .libs/gnome-vfs-async-job-map.o .libs/gnome-vfs-async-ops.o .libs/gnome-vfs-cancellable-ops.o .libs/gnome-vfs-cancellation.o .libs/gnome-vfs-configuration.o .libs/gnome-vfs-context.o .libs/gnome-vfs-directory.o .libs/gnome-vfs-drive.o .libs/gnome-vfs-file-info.o .libs/gnome-vfs-filesystem-type.o .libs/gnome-vfs-find-directory.o .libs/gnome-vfs-handle.o .libs/gnome-vfs-inet-connection.o .libs/gnome-vfs-init.o .libs/gnome-vfs-job-queue.o .libs/gnome-vfs-job.o .libs/gnome-vfs-method.o .libs/gnome-vfs-mime-handlers.o .libs/gnome-vfs-mime-info.o .libs/gnome-vfs-mime-info-cache.o .libs/gnome-vfs-mime-monitor.o .libs/gnome-vfs-mime-sniff-buffer.o .libs/gnome-vfs-mime.o .libs/gnome-vfs-mime-magic.o .libs/gnome-vfs-module-callback-module-api.o .libs/gnome-vfs-module-callback-private.o .libs/gnome-vfs-module-callback.o .libs/gnome-vfs-module-shared.o .libs/gnome-vfs-module.o .libs/gnome-vfs-monitor.o .libs/gnome-vfs-open-fd.o .libs/gnome-vfs-ops.o .libs/gnome-vfs-private-utils.o .libs/gnome-vfs-private.o .libs/gnome-vfs-resolve.o .libs/gnome-vfs-result.o .libs/gnome-vfs-socket-buffer.o .libs/gnome-vfs-socket.o .libs/gnome-vfs-ssl.o .libs/gnome-vfs-transform.o .libs/gnome-vfs-uri.o .libs/gnome-vfs-utils.o .libs/gnome-vfs-volume-monitor.o .libs/gnome-vfs-volume.o .libs/gnome-vfs-xfer.o .libs/xdgmimemagic.o .libs/xdgmime.o .libs/xdgmimecache.o .libs/xdgmimeglob.o .libs/xdgmimeint.o .libs/xdgmimealias.o .libs/xdgmimeparent.o .libs/xdgmimeicon.o .libs/gnome-vfs-enum-types.o .libs/gnome-vfs-cdrom.o .libs/gnome-vfs-daemon-method.o .libs/gnome-vfs-dbus-utils.o .libs/gnome-vfs-dns-sd.o .libs/gnome-vfs-module-callback-marshall.o .libs/gnome-vfs-parse-ls.o .libs/gnome-vfs-pty.o .libs/gnome-vfs-volume-monitor-client.o .libs/gnome-vfs-volume-ops.o -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib/libgconf-2.so -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib /gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib/libORBit-2.so -lgmodule-2.0 -lgthread-2.0 /gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib/libxml2.so -L/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -ldl -lz /gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib/liblzma.so -lm /gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib/libdbus-glib-1.so -lgio-2.0 /gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/libdbus-1.so -lpthread -lgobject-2.0 -lglib-2.0 -lresolv -lutil -pthread -pthread -pthread -Wl,-soname -Wl,libgnomevfs-2.so.0 -Wl,-version-script -Wl,.libs/libgnomevfs-2.ver -o .libs/libgnomevfs-2.so.0.2400.4 libtool: link: (cd ".libs" && rm -f "libgnomevfs-2.so.0" && ln -s "libgnomevfs-2.so.0.2400.4" "libgnomevfs-2.so.0") libtool: link: (cd ".libs" && rm -f "libgnomevfs-2.so" && ln -s "libgnomevfs-2.so.0.2400.4" "libgnomevfs-2.so") libtool: link: ar cru .libs/libgnomevfs-2.a gnome-vfs-ace.o gnome-vfs-acl.o gnome-vfs-application-registry.o gnome-vfs-address.o gnome-vfs-async-job-map.o gnome-vfs-async-ops.o gnome-vfs-cancellable-ops.o gnome-vfs-cancellation.o gnome-vfs-configuration.o gnome-vfs-context.o gnome-vfs-directory.o gnome-vfs-drive.o gnome-vfs-file-info.o gnome-vfs-filesystem-type.o gnome-vfs-find-directory.o gnome-vfs-handle.o gnome-vfs-inet-connection.o gnome-vfs-init.o gnome-vfs-job-queue.o gnome-vfs-job.o gnome-vfs-method.o gnome-vfs-mime-handlers.o gnome-vfs-mime-info.o gnome-vfs-mime-info-cache.o gnome-vfs-mime-monitor.o gnome-vfs-mime-sniff-buffer.o gnome-vfs-mime.o gnome-vfs-mime-magic.o gnome-vfs-module-callback-module-api.o gnome-vfs-module-callback-private.o gnome-vfs-module-callback.o gnome-vfs-module-shared.o gnome-vfs-module.o gnome-vfs-monitor.o gnome-vfs-open-fd.o gnome-vfs-ops.o gnome-vfs-private-utils.o gnome-vfs-private.o gnome-vfs-resolve.o gnome-vfs-result.o gnome-vfs-socket-buffer.o gnome-vfs-socket.o gnome-vfs-ssl.o gnome-vfs-transform.o gnome-vfs-uri.o gnome-vfs-utils.o gnome-vfs-volume-monitor.o gnome-vfs-volume.o gnome-vfs-xfer.o xdgmimemagic.o xdgmime.o xdgmimecache.o xdgmimeglob.o xdgmimeint.o xdgmimealias.o xdgmimeparent.o xdgmimeicon.o gnome-vfs-enum-types.o gnome-vfs-cdrom.o gnome-vfs-daemon-method.o gnome-vfs-dbus-utils.o gnome-vfs-dns-sd.o gnome-vfs-module-callback-marshall.o gnome-vfs-parse-ls.o gnome-vfs-pty.o gnome-vfs-volume-monitor-client.o gnome-vfs-volume-ops.o ar: `u' modifier ignored since `D' is the default (see `U') libtool: link: ranlib .libs/libgnomevfs-2.a libtool: link: ( cd ".libs" && rm -f "libgnomevfs-2.la" && ln -s "../libgnomevfs-2.la" "libgnomevfs-2.la" ) /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -o libgnomevfsdaemon-2.la gnome-vfs-filesystem-type.lo gnome-vfs-cdrom.lo gnome-vfs-hal-mounts.lo gnome-vfs-volume-monitor-daemon.lo gnome-vfs-volume-monitor.lo gnome-vfs-unix-mounts.lo -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -lgmodule-2.0 -pthread -lgthread-2.0 -pthread -lgconf-2 -lxml2 -ldbus-glib-1 -ldbus-1 -lgobject-2.0 -lglib-2.0 -lresolv -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lglib-2.0 libgnomevfs-2.la -lutil libtool: link: ar cru .libs/libgnomevfsdaemon-2.a .libs/gnome-vfs-filesystem-type.o .libs/gnome-vfs-cdrom.o .libs/gnome-vfs-hal-mounts.o .libs/gnome-vfs-volume-monitor-daemon.o .libs/gnome-vfs-volume-monitor.o .libs/gnome-vfs-unix-mounts.o ar: `u' modifier ignored since `D' is the default (see `U') libtool: link: ranlib .libs/libgnomevfsdaemon-2.a libtool: link: ( cd ".libs" && rm -f "libgnomevfsdaemon-2.la" && ln -s "../libgnomevfsdaemon-2.la" "libgnomevfsdaemon-2.la" ) make[3]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/libgnomevfs' make[2]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/libgnomevfs' Making all in modules make[2]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/modules' /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../imported/neon -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DSSH_PROGRAM=\"ssh\" -DG_DISABLE_DEPRECATED -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"gnome-vfs-modules\" -g -O2 -MT file-method.lo -MD -MP -MF .deps/file-method.Tpo -c -o file-method.lo file-method.c /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../imported/neon -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DSSH_PROGRAM=\"ssh\" -DG_DISABLE_DEPRECATED -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"gnome-vfs-modules\" -g -O2 -MT fstype.lo -MD -MP -MF .deps/fstype.Tpo -c -o fstype.lo fstype.c /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../imported/neon -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DSSH_PROGRAM=\"ssh\" -DG_DISABLE_DEPRECATED -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"gnome-vfs-modules\" -g -O2 -MT file-method-acl.lo -MD -MP -MF .deps/file-method-acl.Tpo -c -o file-method-acl.lo file-method-acl.c /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../imported/neon -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DSSH_PROGRAM=\"ssh\" -DG_DISABLE_DEPRECATED -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"gnome-vfs-modules\" -g -O2 -MT inotify-kernel.lo -MD -MP -MF .deps/inotify-kernel.Tpo -c -o inotify-kernel.lo inotify-kernel.c /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../imported/neon -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DSSH_PROGRAM=\"ssh\" -DG_DISABLE_DEPRECATED -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"gnome-vfs-modules\" -g -O2 -MT inotify-missing.lo -MD -MP -MF .deps/inotify-missing.Tpo -c -o inotify-missing.lo inotify-missing.c /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../imported/neon -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DSSH_PROGRAM=\"ssh\" -DG_DISABLE_DEPRECATED -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"gnome-vfs-modules\" -g -O2 -MT inotify-path.lo -MD -MP -MF .deps/inotify-path.Tpo -c -o inotify-path.lo inotify-path.c /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../imported/neon -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DSSH_PROGRAM=\"ssh\" -DG_DISABLE_DEPRECATED -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"gnome-vfs-modules\" -g -O2 -MT inotify-sub.lo -MD -MP -MF .deps/inotify-sub.Tpo -c -o inotify-sub.lo inotify-sub.c /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../imported/neon -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DSSH_PROGRAM=\"ssh\" -DG_DISABLE_DEPRECATED -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"gnome-vfs-modules\" -g -O2 -MT inotify-helper.lo -MD -MP -MF .deps/inotify-helper.Tpo -c -o inotify-helper.lo inotify-helper.c /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../imported/neon -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DSSH_PROGRAM=\"ssh\" -DG_DISABLE_DEPRECATED -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"gnome-vfs-modules\" -g -O2 -MT inotify-diag.lo -MD -MP -MF .deps/inotify-diag.Tpo -c -o inotify-diag.lo inotify-diag.c /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../imported/neon -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DSSH_PROGRAM=\"ssh\" -DG_DISABLE_DEPRECATED -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"gnome-vfs-modules\" -g -O2 -MT test-method.lo -MD -MP -MF .deps/test-method.Tpo -c -o test-method.lo test-method.c /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../imported/neon -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DSSH_PROGRAM=\"ssh\" -DG_DISABLE_DEPRECATED -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"gnome-vfs-modules\" -g -O2 -MT bzip2-method.lo -MD -MP -MF .deps/bzip2-method.Tpo -c -o bzip2-method.lo bzip2-method.c /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../imported/neon -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DSSH_PROGRAM=\"ssh\" -DG_DISABLE_DEPRECATED -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"gnome-vfs-modules\" -g -O2 -MT gzip-method.lo -MD -MP -MF .deps/gzip-method.Tpo -c -o gzip-method.lo gzip-method.c /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../imported/neon -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DSSH_PROGRAM=\"ssh\" -DG_DISABLE_DEPRECATED -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"gnome-vfs-modules\" -g -O2 -MT tar-method.lo -MD -MP -MF .deps/tar-method.Tpo -c -o tar-method.lo tar-method.c /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../imported/neon -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DSSH_PROGRAM=\"ssh\" -DG_DISABLE_DEPRECATED -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"gnome-vfs-modules\" -g -O2 -MT computer-method.lo -MD -MP -MF .deps/computer-method.Tpo -c -o computer-method.lo computer-method.c /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../imported/neon -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DSSH_PROGRAM=\"ssh\" -DG_DISABLE_DEPRECATED -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"gnome-vfs-modules\" -g -O2 -MT dns-sd-method.lo -MD -MP -MF .deps/dns-sd-method.Tpo -c -o dns-sd-method.lo dns-sd-method.c /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../imported/neon -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DSSH_PROGRAM=\"ssh\" -DG_DISABLE_DEPRECATED -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"gnome-vfs-modules\" -g -O2 -MT network-method.lo -MD -MP -MF .deps/network-method.Tpo -c -o network-method.lo network-method.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../imported/neon -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DSSH_PROGRAM=\"ssh\" -DG_DISABLE_DEPRECATED -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"gnome-vfs-modules\" -g -O2 -MT inotify-kernel.lo -MD -MP -MF .deps/inotify-kernel.Tpo -c inotify-kernel.c -fPIC -DPIC -o .libs/inotify-kernel.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../imported/neon -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DSSH_PROGRAM=\"ssh\" -DG_DISABLE_DEPRECATED -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"gnome-vfs-modules\" -g -O2 -MT inotify-missing.lo -MD -MP -MF .deps/inotify-missing.Tpo -c inotify-missing.c -fPIC -DPIC -o .libs/inotify-missing.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../imported/neon -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DSSH_PROGRAM=\"ssh\" -DG_DISABLE_DEPRECATED -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"gnome-vfs-modules\" -g -O2 -MT inotify-diag.lo -MD -MP -MF .deps/inotify-diag.Tpo -c inotify-diag.c -fPIC -DPIC -o .libs/inotify-diag.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../imported/neon -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DSSH_PROGRAM=\"ssh\" -DG_DISABLE_DEPRECATED -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"gnome-vfs-modules\" -g -O2 -MT file-method-acl.lo -MD -MP -MF .deps/file-method-acl.Tpo -c file-method-acl.c -fPIC -DPIC -o .libs/file-method-acl.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../imported/neon -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DSSH_PROGRAM=\"ssh\" -DG_DISABLE_DEPRECATED -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"gnome-vfs-modules\" -g -O2 -MT fstype.lo -MD -MP -MF .deps/fstype.Tpo -c fstype.c -fPIC -DPIC -o .libs/fstype.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../imported/neon -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DSSH_PROGRAM=\"ssh\" -DG_DISABLE_DEPRECATED -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"gnome-vfs-modules\" -g -O2 -MT test-method.lo -MD -MP -MF .deps/test-method.Tpo -c test-method.c -fPIC -DPIC -o .libs/test-method.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../imported/neon -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DSSH_PROGRAM=\"ssh\" -DG_DISABLE_DEPRECATED -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"gnome-vfs-modules\" -g -O2 -MT file-method.lo -MD -MP -MF .deps/file-method.Tpo -c file-method.c -fPIC -DPIC -o .libs/file-method.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../imported/neon -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DSSH_PROGRAM=\"ssh\" -DG_DISABLE_DEPRECATED -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"gnome-vfs-modules\" -g -O2 -MT inotify-path.lo -MD -MP -MF .deps/inotify-path.Tpo -c inotify-path.c -fPIC -DPIC -o .libs/inotify-path.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../imported/neon -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DSSH_PROGRAM=\"ssh\" -DG_DISABLE_DEPRECATED -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"gnome-vfs-modules\" -g -O2 -MT bzip2-method.lo -MD -MP -MF .deps/bzip2-method.Tpo -c bzip2-method.c -fPIC -DPIC -o .libs/bzip2-method.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../imported/neon -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DSSH_PROGRAM=\"ssh\" -DG_DISABLE_DEPRECATED -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"gnome-vfs-modules\" -g -O2 -MT inotify-sub.lo -MD -MP -MF .deps/inotify-sub.Tpo -c inotify-sub.c -fPIC -DPIC -o .libs/inotify-sub.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../imported/neon -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DSSH_PROGRAM=\"ssh\" -DG_DISABLE_DEPRECATED -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"gnome-vfs-modules\" -g -O2 -MT gzip-method.lo -MD -MP -MF .deps/gzip-method.Tpo -c gzip-method.c -fPIC -DPIC -o .libs/gzip-method.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../imported/neon -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DSSH_PROGRAM=\"ssh\" -DG_DISABLE_DEPRECATED -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"gnome-vfs-modules\" -g -O2 -MT inotify-helper.lo -MD -MP -MF .deps/inotify-helper.Tpo -c inotify-helper.c -fPIC -DPIC -o .libs/inotify-helper.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../imported/neon -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DSSH_PROGRAM=\"ssh\" -DG_DISABLE_DEPRECATED -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"gnome-vfs-modules\" -g -O2 -MT tar-method.lo -MD -MP -MF .deps/tar-method.Tpo -c tar-method.c -fPIC -DPIC -o .libs/tar-method.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../imported/neon -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DSSH_PROGRAM=\"ssh\" -DG_DISABLE_DEPRECATED -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"gnome-vfs-modules\" -g -O2 -MT computer-method.lo -MD -MP -MF .deps/computer-method.Tpo -c computer-method.c -fPIC -DPIC -o .libs/computer-method.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../imported/neon -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DSSH_PROGRAM=\"ssh\" -DG_DISABLE_DEPRECATED -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"gnome-vfs-modules\" -g -O2 -MT network-method.lo -MD -MP -MF .deps/network-method.Tpo -c network-method.c -fPIC -DPIC -o .libs/network-method.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../imported/neon -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DSSH_PROGRAM=\"ssh\" -DG_DISABLE_DEPRECATED -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"gnome-vfs-modules\" -g -O2 -MT dns-sd-method.lo -MD -MP -MF .deps/dns-sd-method.Tpo -c dns-sd-method.c -fPIC -DPIC -o .libs/dns-sd-method.o In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/stdio.h:27, from fstype.c:38: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/stdio.h:27, from file-method-acl.c:31: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/limits.h:26, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include/glibconfig.h:11, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from inotify-diag.c:27: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/limits.h:26, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include/glibconfig.h:11, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from inotify-missing.c:27: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/stdio.h:27, from inotify-kernel.c:25: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/string.h:26, from inotify-sub.c:27: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/limits.h:26, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include/glibconfig.h:11, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from bzip2-method.c:27: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/unistd.h:25, from ../libgnomevfs/gnome-vfs-method.h:35, from tar-method.c:26: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/errno.h:25, from inotify-helper.c:27: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/limits.h:26, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include/glibconfig.h:11, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from gzip-method.c:26: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/stdint.h:26, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/sys/inotify.h:21, from inotify-path.c:31: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/stdlib.h:25, from computer-method.c:27: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/limits.h:26, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include/glibconfig.h:11, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from ../libgnomevfs/gnome-vfs-cancellation.h:29, from file-method.c:29: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/limits.h:26, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include/glibconfig.h:11, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gi18n-lib.h:21, from test-method.c:39: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/stdlib.h:25, from network-method.c:27: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/stdlib.h:25, from dns-sd-method.c:27: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ In file included from /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2/gconf/gconf-schema.h:26, from /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2/gconf/gconf.h:27, from /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2/gconf/gconf-client.h:25, from network-method.c:31: /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2/gconf/gconf-value.h:139:3: warning: ‘GTime’ is deprecated: Use 'GDateTime' instead [-Wdeprecated-declarations] 139 | GTime mod_time; /* time of the modification */ | ^~~~~ /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2/gconf/gconf-value.h:144:1: warning: ‘GTime’ is deprecated: Use 'GDateTime' instead [-Wdeprecated-declarations] 144 | GTime gconf_meta_info_mod_time (GConfMetaInfo *gcmi); | ^~~~~ /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2/gconf/gconf-value.h:153:46: warning: ‘GTime’ is deprecated: Use 'GDateTime' instead [-Wdeprecated-declarations] 153 | GTime mod_time); | ^~~~~ libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../imported/neon -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DSSH_PROGRAM=\"ssh\" -DG_DISABLE_DEPRECATED -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"gnome-vfs-modules\" -g -O2 -MT file-method-acl.lo -MD -MP -MF .deps/file-method-acl.Tpo -c file-method-acl.c -o file-method-acl.o >/dev/null 2>&1 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../imported/neon -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DSSH_PROGRAM=\"ssh\" -DG_DISABLE_DEPRECATED -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"gnome-vfs-modules\" -g -O2 -MT inotify-diag.lo -MD -MP -MF .deps/inotify-diag.Tpo -c inotify-diag.c -o inotify-diag.o >/dev/null 2>&1 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../imported/neon -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DSSH_PROGRAM=\"ssh\" -DG_DISABLE_DEPRECATED -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"gnome-vfs-modules\" -g -O2 -MT inotify-sub.lo -MD -MP -MF .deps/inotify-sub.Tpo -c inotify-sub.c -o inotify-sub.o >/dev/null 2>&1 inotify-kernel.c:73:2: warning: ‘GTimeVal’ is deprecated: Use 'GDateTime' instead [-Wdeprecated-declarations] 73 | GTimeVal hold_until; | ^~~~~~~~ In file included from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from inotify-kernel.c:30: /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:547:8: note: declared here 547 | struct _GTimeVal | ^~~~~~~~~ inotify-kernel.c: In function ‘ik_event_internal_new’: inotify-kernel.c:222:2: warning: ‘GTimeVal’ is deprecated: Use 'GDateTime' instead [-Wdeprecated-declarations] 222 | GTimeVal tv; | ^~~~~~~~ In file included from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from inotify-kernel.c:30: /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:547:8: note: declared here 547 | struct _GTimeVal | ^~~~~~~~~ inotify-kernel.c:226:2: warning: ‘g_get_current_time’ is deprecated: Use 'g_get_real_time' instead [-Wdeprecated-declarations] 226 | g_get_current_time (&tv); | ^~~~~~~~~~~~~~~~~~ In file included from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/giochannel.h:33, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:54, from inotify-kernel.c:30: /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gmain.h:688:8: note: declared here 688 | void g_get_current_time (GTimeVal *result); | ^~~~~~~~~~~~~~~~~~ inotify-kernel.c:227:2: warning: ‘g_time_val_add’ is deprecated [-Wdeprecated-declarations] 227 | g_time_val_add (&tv, DEFAULT_HOLD_UNTIL_TIME); | ^~~~~~~~~~~~~~ In file included from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:89, from inotify-kernel.c:30: /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtimer.h:67:10: note: declared here 67 | void g_time_val_add (GTimeVal *time_, | ^~~~~~~~~~~~~~ inotify-kernel.c: At top level: inotify-kernel.c:494:1: warning: ‘GTimeVal’ is deprecated: Use 'GDateTime' instead [-Wdeprecated-declarations] 494 | g_timeval_lt(GTimeVal *val1, GTimeVal *val2) | ^~~~~~~~~~~~ In file included from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from inotify-kernel.c:30: /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:547:8: note: declared here 547 | struct _GTimeVal | ^~~~~~~~~ inotify-kernel.c:494:1: warning: ‘GTimeVal’ is deprecated: Use 'GDateTime' instead [-Wdeprecated-declarations] 494 | g_timeval_lt(GTimeVal *val1, GTimeVal *val2) | ^~~~~~~~~~~~ In file included from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from inotify-kernel.c:30: /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:547:8: note: declared here 547 | struct _GTimeVal | ^~~~~~~~~ inotify-kernel.c:510:1: warning: ‘GTimeVal’ is deprecated: Use 'GDateTime' instead [-Wdeprecated-declarations] 510 | g_timeval_eq(GTimeVal *val1, GTimeVal *val2) | ^~~~~~~~~~~~ In file included from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from inotify-kernel.c:30: /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:547:8: note: declared here 547 | struct _GTimeVal | ^~~~~~~~~ inotify-kernel.c:510:1: warning: ‘GTimeVal’ is deprecated: Use 'GDateTime' instead [-Wdeprecated-declarations] 510 | g_timeval_eq(GTimeVal *val1, GTimeVal *val2) | ^~~~~~~~~~~~ In file included from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from inotify-kernel.c:30: /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:547:8: note: declared here 547 | struct _GTimeVal | ^~~~~~~~~ inotify-kernel.c: In function ‘ik_event_add_microseconds’: inotify-kernel.c:538:2: warning: ‘g_time_val_add’ is deprecated [-Wdeprecated-declarations] 538 | g_time_val_add (&event->hold_until, ms); | ^~~~~~~~~~~~~~ In file included from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:89, from inotify-kernel.c:30: /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtimer.h:67:10: note: declared here 67 | void g_time_val_add (GTimeVal *time_, | ^~~~~~~~~~~~~~ inotify-kernel.c: In function ‘ik_event_ready’: inotify-kernel.c:544:2: warning: ‘GTimeVal’ is deprecated: Use 'GDateTime' instead [-Wdeprecated-declarations] 544 | GTimeVal tv; | ^~~~~~~~ In file included from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from inotify-kernel.c:30: /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:547:8: note: declared here 547 | struct _GTimeVal | ^~~~~~~~~ inotify-kernel.c:547:2: warning: ‘g_get_current_time’ is deprecated: Use 'g_get_real_time' instead [-Wdeprecated-declarations] 547 | g_get_current_time (&tv); | ^~~~~~~~~~~~~~~~~~ In file included from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/giochannel.h:33, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:54, from inotify-kernel.c:30: /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gmain.h:688:8: note: declared here 688 | void g_get_current_time (GTimeVal *result); | ^~~~~~~~~~~~~~~~~~ libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../imported/neon -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DSSH_PROGRAM=\"ssh\" -DG_DISABLE_DEPRECATED -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"gnome-vfs-modules\" -g -O2 -MT inotify-helper.lo -MD -MP -MF .deps/inotify-helper.Tpo -c inotify-helper.c -o inotify-helper.o >/dev/null 2>&1 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../imported/neon -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DSSH_PROGRAM=\"ssh\" -DG_DISABLE_DEPRECATED -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"gnome-vfs-modules\" -g -O2 -MT inotify-missing.lo -MD -MP -MF .deps/inotify-missing.Tpo -c inotify-missing.c -o inotify-missing.o >/dev/null 2>&1 file-method.c: In function ‘do_read_directory’: file-method.c:1073:2: warning: ‘readdir_r’ is deprecated [-Wdeprecated-declarations] 1073 | if (readdir_r (handle->dir, handle->current_entry, &result) != 0) { | ^~ In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:473, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/limits.h:26, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include/glibconfig.h:11, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from ../libgnomevfs/gnome-vfs-cancellation.h:29, from file-method.c:29: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/dirent.h:189:12: note: declared here 189 | extern int __REDIRECT (readdir_r, | ^~~~~~~~~~ libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../imported/neon -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DSSH_PROGRAM=\"ssh\" -DG_DISABLE_DEPRECATED -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"gnome-vfs-modules\" -g -O2 -MT fstype.lo -MD -MP -MF .deps/fstype.Tpo -c fstype.c -o fstype.o >/dev/null 2>&1 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../imported/neon -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DSSH_PROGRAM=\"ssh\" -DG_DISABLE_DEPRECATED -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"gnome-vfs-modules\" -g -O2 -MT bzip2-method.lo -MD -MP -MF .deps/bzip2-method.Tpo -c bzip2-method.c -o bzip2-method.o >/dev/null 2>&1 mv -f .deps/file-method-acl.Tpo .deps/file-method-acl.Plo mv -f .deps/inotify-diag.Tpo .deps/inotify-diag.Plo /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../imported/neon -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DSSH_PROGRAM=\"ssh\" -DG_DISABLE_DEPRECATED -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"gnome-vfs-modules\" -g -O2 -MT nntp-method.lo -MD -MP -MF .deps/nntp-method.Tpo -c -o nntp-method.lo nntp-method.c /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../imported/neon -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DSSH_PROGRAM=\"ssh\" -DG_DISABLE_DEPRECATED -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"gnome-vfs-modules\" -g -O2 -MT sftp-method.lo -MD -MP -MF .deps/sftp-method.Tpo -c -o sftp-method.lo sftp-method.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../imported/neon -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DSSH_PROGRAM=\"ssh\" -DG_DISABLE_DEPRECATED -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"gnome-vfs-modules\" -g -O2 -MT gzip-method.lo -MD -MP -MF .deps/gzip-method.Tpo -c gzip-method.c -o gzip-method.o >/dev/null 2>&1 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../imported/neon -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DSSH_PROGRAM=\"ssh\" -DG_DISABLE_DEPRECATED -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"gnome-vfs-modules\" -g -O2 -MT inotify-path.lo -MD -MP -MF .deps/inotify-path.Tpo -c inotify-path.c -o inotify-path.o >/dev/null 2>&1 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../imported/neon -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DSSH_PROGRAM=\"ssh\" -DG_DISABLE_DEPRECATED -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"gnome-vfs-modules\" -g -O2 -MT nntp-method.lo -MD -MP -MF .deps/nntp-method.Tpo -c nntp-method.c -fPIC -DPIC -o .libs/nntp-method.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../imported/neon -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DSSH_PROGRAM=\"ssh\" -DG_DISABLE_DEPRECATED -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"gnome-vfs-modules\" -g -O2 -MT sftp-method.lo -MD -MP -MF .deps/sftp-method.Tpo -c sftp-method.c -fPIC -DPIC -o .libs/sftp-method.o mv -f .deps/inotify-helper.Tpo .deps/inotify-helper.Plo In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/stdlib.h:25, from nntp-method.c:35: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ mv -f .deps/inotify-missing.Tpo .deps/inotify-missing.Plo mv -f .deps/inotify-sub.Tpo .deps/inotify-sub.Plo /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../imported/neon -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DSSH_PROGRAM=\"ssh\" -DG_DISABLE_DEPRECATED -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"gnome-vfs-modules\" -g -O2 -MT http-neon-method.lo -MD -MP -MF .deps/http-neon-method.Tpo -c -o http-neon-method.lo http-neon-method.c /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../imported/neon -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DSSH_PROGRAM=\"ssh\" -DG_DISABLE_DEPRECATED -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"gnome-vfs-modules\" -g -O2 -MT http-proxy.lo -MD -MP -MF .deps/http-proxy.Tpo -c -o http-proxy.lo http-proxy.c /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../imported/neon -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DSSH_PROGRAM=\"ssh\" -DG_DISABLE_DEPRECATED -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"gnome-vfs-modules\" -g -O2 -MT ftp-method.lo -MD -MP -MF .deps/ftp-method.Tpo -c -o ftp-method.lo ftp-method.c In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/limits.h:26, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include/glibconfig.h:11, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from ../libgnomevfs/gnome-vfs-cancellation.h:29, from ../libgnomevfs/gnome-vfs-context.h:28, from sftp-method.c:54: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../imported/neon -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DSSH_PROGRAM=\"ssh\" -DG_DISABLE_DEPRECATED -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"gnome-vfs-modules\" -g -O2 -MT inotify-kernel.lo -MD -MP -MF .deps/inotify-kernel.Tpo -c inotify-kernel.c -o inotify-kernel.o >/dev/null 2>&1 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../imported/neon -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DSSH_PROGRAM=\"ssh\" -DG_DISABLE_DEPRECATED -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"gnome-vfs-modules\" -g -O2 -MT http-proxy.lo -MD -MP -MF .deps/http-proxy.Tpo -c http-proxy.c -fPIC -DPIC -o .libs/http-proxy.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../imported/neon -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DSSH_PROGRAM=\"ssh\" -DG_DISABLE_DEPRECATED -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"gnome-vfs-modules\" -g -O2 -MT ftp-method.lo -MD -MP -MF .deps/ftp-method.Tpo -c ftp-method.c -fPIC -DPIC -o .libs/ftp-method.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../imported/neon -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DSSH_PROGRAM=\"ssh\" -DG_DISABLE_DEPRECATED -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"gnome-vfs-modules\" -g -O2 -MT http-neon-method.lo -MD -MP -MF .deps/http-neon-method.Tpo -c http-neon-method.c -fPIC -DPIC -o .libs/http-neon-method.o In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/sys/types.h:25, from http-proxy.c:13: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../imported/neon -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DSSH_PROGRAM=\"ssh\" -DG_DISABLE_DEPRECATED -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"gnome-vfs-modules\" -g -O2 -MT computer-method.lo -MD -MP -MF .deps/computer-method.Tpo -c computer-method.c -o computer-method.o >/dev/null 2>&1 In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/sys/types.h:25, from ftp-method.c:29: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/limits.h:26, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include/glibconfig.h:11, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from ../libgnomevfs/gnome-vfs-acl.h:28, from ../libgnomevfs/gnome-vfs.h:28, from http-neon-method.c:26: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../imported/neon -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DSSH_PROGRAM=\"ssh\" -DG_DISABLE_DEPRECATED -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"gnome-vfs-modules\" -g -O2 -MT dns-sd-method.lo -MD -MP -MF .deps/dns-sd-method.Tpo -c dns-sd-method.c -o dns-sd-method.o >/dev/null 2>&1 mv -f .deps/fstype.Tpo .deps/fstype.Plo libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../imported/neon -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DSSH_PROGRAM=\"ssh\" -DG_DISABLE_DEPRECATED -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"gnome-vfs-modules\" -g -O2 -MT tar-method.lo -MD -MP -MF .deps/tar-method.Tpo -c tar-method.c -o tar-method.o >/dev/null 2>&1 In file included from ../libgnomevfs/gnome-vfs-socket-buffer.h:32, from nntp-method.c:50: ../libgnomevfs/gnome-vfs-socket.h:124:8: warning: ‘GTimeVal’ is deprecated: Use 'GDateTime' instead [-Wdeprecated-declarations] 124 | GTimeVal *timeout, | ^~~~~~~~ In file included from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from nntp-method.c:43: /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:547:8: note: declared here 547 | struct _GTimeVal | ^~~~~~~~~ In file included from ../libgnomevfs/gnome-vfs-socket-buffer.h:32, from nntp-method.c:50: ../libgnomevfs/gnome-vfs-socket.h:163:8: warning: ‘GTimeVal’ is deprecated: Use 'GDateTime' instead [-Wdeprecated-declarations] 163 | GTimeVal *timeout, | ^~~~~~~~ In file included from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from nntp-method.c:43: /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:547:8: note: declared here 547 | struct _GTimeVal | ^~~~~~~~~ nntp-method.c: In function ‘remove_numbers_between_dashes’: nntp-method.c:590:13: warning: Deprecated pre-processor symbol: replace with "memmove" 590 | g_memmove(left_ptr, right_ptr + 1, length_to_end); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ nntp-method.c: In function ‘remove_of_expressions’: nntp-method.c:683:13: warning: Deprecated pre-processor symbol: replace with "memmove" 683 | g_memmove(left_ptr + 1, right_ptr, length_to_end + 1); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ nntp-method.c: In function ‘filter_folder_name’: nntp-method.c:718:13: warning: Deprecated pre-processor symbol: replace with "memmove" 718 | g_memmove(left_ptr, right_ptr + 1, length_to_end); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ nntp-method.c: In function ‘remove_commas’: nntp-method.c:760:13: warning: Deprecated pre-processor symbol: replace with "memmove" 760 | g_memmove(ptr, ptr+1, strlen(ptr)); | ^~~~~~~~~~~~~~~~~~~~~~~~~~ nntp-method.c: In function ‘load_from_article’: nntp-method.c:1270:13: warning: Deprecated pre-processor symbol: replace with "memmove" 1270 | g_memmove(dest_ptr, line, line_len); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~ nntp-method.c: In function ‘copy_bytes_from_buffer’: nntp-method.c:1357:13: warning: Deprecated pre-processor symbol: replace with "memmove" 1357 | g_memmove(destination_buffer, ((char*) connection->buffer) + connection->buffer_offset, size_to_move); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../imported/neon -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DSSH_PROGRAM=\"ssh\" -DG_DISABLE_DEPRECATED -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"gnome-vfs-modules\" -g -O2 -MT network-method.lo -MD -MP -MF .deps/network-method.Tpo -c network-method.c -o network-method.o >/dev/null 2>&1 In file included from /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2/gconf/gconf-schema.h:26, from /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2/gconf/gconf.h:27, from /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2/gconf/gconf-client.h:25, from http-proxy.c:17: /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2/gconf/gconf-value.h:139:3: warning: ‘GTime’ is deprecated: Use 'GDateTime' instead [-Wdeprecated-declarations] 139 | GTime mod_time; /* time of the modification */ | ^~~~~ /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2/gconf/gconf-value.h:144:1: warning: ‘GTime’ is deprecated: Use 'GDateTime' instead [-Wdeprecated-declarations] 144 | GTime gconf_meta_info_mod_time (GConfMetaInfo *gcmi); | ^~~~~ /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2/gconf/gconf-value.h:153:46: warning: ‘GTime’ is deprecated: Use 'GDateTime' instead [-Wdeprecated-declarations] 153 | GTime mod_time); | ^~~~~ http-proxy.c: In function ‘host_port_from_string’: http-proxy.c:142:27: warning: comparison between pointer and zero character constant [-Wpointer-compare] 142 | if (port_part && '\0' != ++port_part && p_proxy_port) { | ^~ http-proxy.c:142:30: note: did you mean to dereference the pointer? 142 | if (port_part && '\0' != ++port_part && p_proxy_port) { | ^~ http-proxy.c: In function ‘proxy_init’: http-proxy.c:534:5: warning: ‘g_mutex_new’ is deprecated [-Wdeprecated-declarations] 534 | gl_mutex = g_mutex_new(); | ^~~~~~~~ In file included from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:112, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/gobject/gbinding.h:28, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib-object.h:22, from /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2/gconf/gconf-client.h:24, from http-proxy.c:17: /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/deprecated/gthread.h:277:17: note: declared here 277 | GMutex * g_mutex_new (void); | ^~~~~~~~~~~ In file included from ../libgnomevfs/gnome-vfs-ssl.h:29, from http-neon-method.c:36: ../libgnomevfs/gnome-vfs-socket.h:124:8: warning: ‘GTimeVal’ is deprecated: Use 'GDateTime' instead [-Wdeprecated-declarations] 124 | GTimeVal *timeout, | ^~~~~~~~ In file included from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from ../libgnomevfs/gnome-vfs-acl.h:28, from ../libgnomevfs/gnome-vfs.h:28, from http-neon-method.c:26: /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:547:8: note: declared here 547 | struct _GTimeVal | ^~~~~~~~~ In file included from ../libgnomevfs/gnome-vfs-ssl.h:29, from http-neon-method.c:36: ../libgnomevfs/gnome-vfs-socket.h:163:8: warning: ‘GTimeVal’ is deprecated: Use 'GDateTime' instead [-Wdeprecated-declarations] 163 | GTimeVal *timeout, | ^~~~~~~~ In file included from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from ../libgnomevfs/gnome-vfs-acl.h:28, from ../libgnomevfs/gnome-vfs.h:28, from http-neon-method.c:26: /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:547:8: note: declared here 547 | struct _GTimeVal | ^~~~~~~~~ In file included from http-neon-method.c:36: ../libgnomevfs/gnome-vfs-ssl.h:57:12: warning: ‘GTimeVal’ is deprecated: Use 'GDateTime' instead [-Wdeprecated-declarations] 57 | GTimeVal *timeout, | ^~~~~~~~ In file included from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from ../libgnomevfs/gnome-vfs-acl.h:28, from ../libgnomevfs/gnome-vfs.h:28, from http-neon-method.c:26: /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:547:8: note: declared here 547 | struct _GTimeVal | ^~~~~~~~~ http-neon-method.c:422:2: warning: ‘GTimeVal’ is deprecated: Use 'GDateTime' instead [-Wdeprecated-declarations] 422 | GTimeVal last_used; | ^~~~~~~~ In file included from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from ../libgnomevfs/gnome-vfs-acl.h:28, from ../libgnomevfs/gnome-vfs.h:28, from http-neon-method.c:26: /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:547:8: note: declared here 547 | struct _GTimeVal | ^~~~~~~~~ http-neon-method.c: In function ‘http_auth_cache_info_check’: http-neon-method.c:511:2: warning: ‘GTimeVal’ is deprecated: Use 'GDateTime' instead [-Wdeprecated-declarations] 511 | GTimeVal now; | ^~~~~~~~ In file included from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from ../libgnomevfs/gnome-vfs-acl.h:28, from ../libgnomevfs/gnome-vfs.h:28, from http-neon-method.c:26: /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:547:8: note: declared here 547 | struct _GTimeVal | ^~~~~~~~~ http-neon-method.c:513:2: warning: ‘g_get_current_time’ is deprecated: Use 'g_get_real_time' instead [-Wdeprecated-declarations] 513 | g_get_current_time (&now); | ^~~~~~~~~~~~~~~~~~ In file included from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/giochannel.h:33, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:54, from ../libgnomevfs/gnome-vfs-acl.h:28, from ../libgnomevfs/gnome-vfs.h:28, from http-neon-method.c:26: /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gmain.h:688:8: note: declared here 688 | void g_get_current_time (GTimeVal *result); | ^~~~~~~~~~~~~~~~~~ http-neon-method.c: In function ‘query_cache_for_authentication’: http-neon-method.c:601:3: warning: ‘g_get_current_time’ is deprecated: Use 'g_get_real_time' instead [-Wdeprecated-declarations] 601 | g_get_current_time (&(info->last_used)); | ^~~~~~~~~~~~~~~~~~ In file included from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/giochannel.h:33, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:54, from ../libgnomevfs/gnome-vfs-acl.h:28, from ../libgnomevfs/gnome-vfs.h:28, from http-neon-method.c:26: /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gmain.h:688:8: note: declared here 688 | void g_get_current_time (GTimeVal *result); | ^~~~~~~~~~~~~~~~~~ http-neon-method.c: In function ‘store_auth_info_in_cache’: http-neon-method.c:621:2: warning: ‘g_get_current_time’ is deprecated: Use 'g_get_real_time' instead [-Wdeprecated-declarations] 621 | g_get_current_time (&(copy->last_used)); | ^~~~~~~~~~~~~~~~~~ In file included from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/giochannel.h:33, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:54, from ../libgnomevfs/gnome-vfs-acl.h:28, from ../libgnomevfs/gnome-vfs.h:28, from http-neon-method.c:26: /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gmain.h:688:8: note: declared here 688 | void g_get_current_time (GTimeVal *result); | ^~~~~~~~~~~~~~~~~~ http-neon-method.c: At top level: http-neon-method.c:1308:2: warning: ‘GTimeVal’ is deprecated: Use 'GDateTime' instead [-Wdeprecated-declarations] 1308 | GTimeVal last_used; | ^~~~~~~~ In file included from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from ../libgnomevfs/gnome-vfs-acl.h:28, from ../libgnomevfs/gnome-vfs.h:28, from http-neon-method.c:26: /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:547:8: note: declared here 547 | struct _GTimeVal | ^~~~~~~~~ http-neon-method.c: In function ‘neon_session_pool_check’: http-neon-method.c:1352:2: warning: ‘GTimeVal’ is deprecated: Use 'GDateTime' instead [-Wdeprecated-declarations] 1352 | GTimeVal now; | ^~~~~~~~ In file included from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from ../libgnomevfs/gnome-vfs-acl.h:28, from ../libgnomevfs/gnome-vfs.h:28, from http-neon-method.c:26: /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:547:8: note: declared here 547 | struct _GTimeVal | ^~~~~~~~~ http-neon-method.c:1354:2: warning: ‘g_get_current_time’ is deprecated: Use 'g_get_real_time' instead [-Wdeprecated-declarations] 1354 | g_get_current_time (&now); | ^~~~~~~~~~~~~~~~~~ In file included from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/giochannel.h:33, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:54, from ../libgnomevfs/gnome-vfs-acl.h:28, from ../libgnomevfs/gnome-vfs.h:28, from http-neon-method.c:26: /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gmain.h:688:8: note: declared here 688 | void g_get_current_time (GTimeVal *result); | ^~~~~~~~~~~~~~~~~~ http-neon-method.c: In function ‘neon_session_pool_lookup’: http-neon-method.c:1449:3: warning: ‘g_get_current_time’ is deprecated: Use 'g_get_real_time' instead [-Wdeprecated-declarations] 1449 | g_get_current_time (&(pool->last_used)); | ^~~~~~~~~~~~~~~~~~ In file included from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/giochannel.h:33, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:54, from ../libgnomevfs/gnome-vfs-acl.h:28, from ../libgnomevfs/gnome-vfs.h:28, from http-neon-method.c:26: /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gmain.h:688:8: note: declared here 688 | void g_get_current_time (GTimeVal *result); | ^~~~~~~~~~~~~~~~~~ http-neon-method.c: In function ‘http_context_host_matches’: http-neon-method.c:1790:9: warning: ‘g_pattern_match_string’ is deprecated: Use 'g_pattern_spec_match_string' instead [-Wdeprecated-declarations] 1790 | res = g_pattern_match_string (spec, uri->host_name); | ^~~ In file included from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:65, from ../libgnomevfs/gnome-vfs-acl.h:28, from ../libgnomevfs/gnome-vfs.h:28, from http-neon-method.c:26: /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gpattern.h:55:15: note: declared here 55 | gboolean g_pattern_match_string (GPatternSpec *pspec, | ^~~~~~~~~~~~~~~~~~~~~~ mv -f .deps/inotify-path.Tpo .deps/inotify-path.Plo In file included from /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2/gconf/gconf-schema.h:26, from /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2/gconf/gconf.h:27, from /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2/gconf/gconf-client.h:25, from ftp-method.c:37: /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2/gconf/gconf-value.h:139:3: warning: ‘GTime’ is deprecated: Use 'GDateTime' instead [-Wdeprecated-declarations] 139 | GTime mod_time; /* time of the modification */ | ^~~~~ /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2/gconf/gconf-value.h:144:1: warning: ‘GTime’ is deprecated: Use 'GDateTime' instead [-Wdeprecated-declarations] 144 | GTime gconf_meta_info_mod_time (GConfMetaInfo *gcmi); | ^~~~~ /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2/gconf/gconf-value.h:153:46: warning: ‘GTime’ is deprecated: Use 'GDateTime' instead [-Wdeprecated-declarations] 153 | GTime mod_time); | ^~~~~ In file included from ../libgnomevfs/gnome-vfs-inet-connection.h:28, from ftp-method.c:39: ../libgnomevfs/gnome-vfs-socket.h:124:8: warning: ‘GTimeVal’ is deprecated: Use 'GDateTime' instead [-Wdeprecated-declarations] 124 | GTimeVal *timeout, | ^~~~~~~~ In file included from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/gobject/gbinding.h:28, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib-object.h:22, from /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2/gconf/gconf-client.h:24, from ftp-method.c:37: /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:547:8: note: declared here 547 | struct _GTimeVal | ^~~~~~~~~ In file included from ../libgnomevfs/gnome-vfs-inet-connection.h:28, from ftp-method.c:39: ../libgnomevfs/gnome-vfs-socket.h:163:8: warning: ‘GTimeVal’ is deprecated: Use 'GDateTime' instead [-Wdeprecated-declarations] 163 | GTimeVal *timeout, | ^~~~~~~~ In file included from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/gobject/gbinding.h:28, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib-object.h:22, from /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2/gconf/gconf-client.h:24, from ftp-method.c:37: /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:547:8: note: declared here 547 | struct _GTimeVal | ^~~~~~~~~ sftp-method.c: In function ‘sftp_connect’: sftp-method.c:1491:13: warning: Deprecated pre-processor symbol 1491 | if (!g_thread_supported ()) g_thread_init (NULL); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ sftp-method.c:1491:3: warning: ‘g_thread_init’ is deprecated [-Wdeprecated-declarations] 1491 | if (!g_thread_supported ()) g_thread_init (NULL); | ^~ In file included from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:112, from ../libgnomevfs/gnome-vfs-cancellation.h:29, from ../libgnomevfs/gnome-vfs-context.h:28, from sftp-method.c:54: /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/deprecated/gthread.h:265:10: note: declared here 265 | void g_thread_init (gpointer vtable); | ^~~~~~~~~~~~~ sftp-method.c:1502:3: warning: ‘g_mutex_new’ is deprecated [-Wdeprecated-declarations] 1502 | (*connection)->mutex = g_mutex_new (); | ^ In file included from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:112, from ../libgnomevfs/gnome-vfs-cancellation.h:29, from ../libgnomevfs/gnome-vfs-context.h:28, from sftp-method.c:54: /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/deprecated/gthread.h:277:17: note: declared here 277 | GMutex * g_mutex_new (void); | ^~~~~~~~~~~ libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../imported/neon -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DSSH_PROGRAM=\"ssh\" -DG_DISABLE_DEPRECATED -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"gnome-vfs-modules\" -g -O2 -MT test-method.lo -MD -MP -MF .deps/test-method.Tpo -c test-method.c -o test-method.o >/dev/null 2>&1 mv -f .deps/bzip2-method.Tpo .deps/bzip2-method.Plo /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -export_dynamic -avoid-version -module -no-undefined -o libbzip2.la -rpath /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules bzip2-method.lo -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgmodule-2.0 -pthread -lgthread-2.0 -pthread -lgobject-2.0 -lglib-2.0 -lbz2 ../libgnomevfs/libgnomevfs-2.la -lutil mv -f .deps/gzip-method.Tpo .deps/gzip-method.Plo /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -export_dynamic -avoid-version -module -no-undefined -o libgzip.la -rpath /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules gzip-method.lo -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgmodule-2.0 -pthread -lgthread-2.0 -pthread -lgobject-2.0 -lglib-2.0 -lz ../libgnomevfs/libgnomevfs-2.la -lutil mv -f .deps/inotify-kernel.Tpo .deps/inotify-kernel.Plo libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../imported/neon -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DSSH_PROGRAM=\"ssh\" -DG_DISABLE_DEPRECATED -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"gnome-vfs-modules\" -g -O2 -MT http-proxy.lo -MD -MP -MF .deps/http-proxy.Tpo -c http-proxy.c -o http-proxy.o >/dev/null 2>&1 mv -f .deps/dns-sd-method.Tpo .deps/dns-sd-method.Plo /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -export_dynamic -avoid-version -module -no-undefined -o libdns-sd.la -rpath /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules dns-sd-method.lo -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgmodule-2.0 -pthread -lgthread-2.0 -pthread -lgobject-2.0 -lglib-2.0 ../libgnomevfs/libgnomevfs-2.la -lutil libtool: link: gcc -shared .libs/bzip2-method.o -Wl,-rpath -Wl,/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/libgnomevfs/.libs -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lbz2 ../libgnomevfs/.libs/libgnomevfs-2.so -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib -L/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib/libgconf-2.so /gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib/libORBit-2.so -lgmodule-2.0 -lgthread-2.0 /gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib/libxml2.so -ldl -lz /gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib/liblzma.so -lm /gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib/libdbus-glib-1.so -lgio-2.0 /gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/libdbus-1.so -lpthread -lgobject-2.0 -lglib-2.0 -lresolv -lutil -pthread -pthread -pthread -Wl,-soname -Wl,libbzip2.so -o .libs/libbzip2.so mv -f .deps/computer-method.Tpo .deps/computer-method.Plo /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -export_dynamic -avoid-version -module -no-undefined -o libcomputer.la -rpath /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules computer-method.lo -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgmodule-2.0 -pthread -lgthread-2.0 -pthread -lgobject-2.0 -lgconf-2 -lglib-2.0 ../libgnomevfs/libgnomevfs-2.la -lutil libtool: link: gcc -shared .libs/gzip-method.o -Wl,-rpath -Wl,/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/libgnomevfs/.libs -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib ../libgnomevfs/.libs/libgnomevfs-2.so -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib -L/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib/libgconf-2.so /gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib/libORBit-2.so -lgmodule-2.0 -lgthread-2.0 /gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib/libxml2.so -ldl -lz /gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib/liblzma.so -lm /gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib/libdbus-glib-1.so -lgio-2.0 /gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/libdbus-1.so -lpthread -lgobject-2.0 -lglib-2.0 -lresolv -lutil -pthread -pthread -pthread -Wl,-soname -Wl,libgzip.so -o .libs/libgzip.so mv -f .deps/tar-method.Tpo .deps/tar-method.Plo /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -export_dynamic -avoid-version -module -no-undefined -o libtar.la -rpath /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules tar-method.lo -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgmodule-2.0 -pthread -lgthread-2.0 -pthread -lgobject-2.0 -lglib-2.0 ../libgnomevfs/libgnomevfs-2.la -lutil libtool: link: ar cru .libs/libgzip.a gzip-method.o ar: `u' modifier ignored since `D' is the default (see `U') libtool: link: ranlib .libs/libgzip.a libtool: link: ar cru .libs/libbzip2.a bzip2-method.o ar: `u' modifier ignored since `D' is the default (see `U') libtool: link: ranlib .libs/libbzip2.a libtool: link: ( cd ".libs" && rm -f "libgzip.la" && ln -s "../libgzip.la" "libgzip.la" ) libtool: link: ( cd ".libs" && rm -f "libbzip2.la" && ln -s "../libbzip2.la" "libbzip2.la" ) libtool: link: gcc -shared .libs/dns-sd-method.o -Wl,-rpath -Wl,/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/libgnomevfs/.libs -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib ../libgnomevfs/.libs/libgnomevfs-2.so -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib -L/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib/libgconf-2.so /gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib/libORBit-2.so -lgmodule-2.0 -lgthread-2.0 /gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib/libxml2.so -ldl -lz /gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib/liblzma.so -lm /gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib/libdbus-glib-1.so -lgio-2.0 /gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/libdbus-1.so -lpthread -lgobject-2.0 -lglib-2.0 -lresolv -lutil -pthread -pthread -pthread -Wl,-soname -Wl,libdns-sd.so -o .libs/libdns-sd.so mv -f .deps/network-method.Tpo .deps/network-method.Plo /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -export_dynamic -avoid-version -module -no-undefined -o libnetwork.la -rpath /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules network-method.lo -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgmodule-2.0 -pthread -lgthread-2.0 -pthread -lgobject-2.0 -lgconf-2 -lglib-2.0 ../libgnomevfs/libgnomevfs-2.la -lutil libtool: link: gcc -shared .libs/computer-method.o -Wl,-rpath -Wl,/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/libgnomevfs/.libs -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib ../libgnomevfs/.libs/libgnomevfs-2.so -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib/libgconf-2.so /gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib/libORBit-2.so -lgmodule-2.0 -lgthread-2.0 /gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib/libxml2.so -ldl -lz /gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib/liblzma.so -lm /gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib/libdbus-glib-1.so -lgio-2.0 /gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/libdbus-1.so -lpthread -lgobject-2.0 -lglib-2.0 -lresolv -lutil -pthread -pthread -pthread -Wl,-soname -Wl,libcomputer.so -o .libs/libcomputer.so mv -f .deps/http-proxy.Tpo .deps/http-proxy.Plo libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../imported/neon -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DSSH_PROGRAM=\"ssh\" -DG_DISABLE_DEPRECATED -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"gnome-vfs-modules\" -g -O2 -MT file-method.lo -MD -MP -MF .deps/file-method.Tpo -c file-method.c -o file-method.o >/dev/null 2>&1 libtool: link: ar cru .libs/libdns-sd.a dns-sd-method.o mv -f .deps/test-method.Tpo .deps/test-method.Plo ar: `u' modifier ignored since `D' is the default (see `U') libtool: link: ranlib .libs/libdns-sd.a libtool: link: gcc -shared .libs/tar-method.o -Wl,-rpath -Wl,/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/libgnomevfs/.libs -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib ../libgnomevfs/.libs/libgnomevfs-2.so -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib -L/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib/libgconf-2.so /gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib/libORBit-2.so -lgmodule-2.0 -lgthread-2.0 /gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib/libxml2.so -ldl -lz /gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib/liblzma.so -lm /gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib/libdbus-glib-1.so -lgio-2.0 /gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/libdbus-1.so -lpthread -lgobject-2.0 -lglib-2.0 -lresolv -lutil -pthread -pthread -pthread -Wl,-soname -Wl,libtar.so -o .libs/libtar.so /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -export_dynamic -avoid-version -module -no-undefined -o libvfs-test.la -rpath /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules test-method.lo -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgmodule-2.0 -pthread -lgthread-2.0 -pthread -lglib-2.0 -lxml2 ../libgnomevfs/libgnomevfs-2.la -lutil libtool: link: ( cd ".libs" && rm -f "libdns-sd.la" && ln -s "../libdns-sd.la" "libdns-sd.la" ) libtool: link: ar cru .libs/libcomputer.a computer-method.o ar: `u' modifier ignored since `D' is the default (see `U') libtool: link: ranlib .libs/libcomputer.a libtool: link: ( cd ".libs" && rm -f "libcomputer.la" && ln -s "../libcomputer.la" "libcomputer.la" ) libtool: link: ar cru .libs/libtar.a tar-method.o ar: `u' modifier ignored since `D' is the default (see `U') libtool: link: ranlib .libs/libtar.a libtool: link: gcc -shared .libs/network-method.o -Wl,-rpath -Wl,/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/libgnomevfs/.libs -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib ../libgnomevfs/.libs/libgnomevfs-2.so -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib/libgconf-2.so /gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib/libORBit-2.so -lgmodule-2.0 -lgthread-2.0 /gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib/libxml2.so -ldl -lz /gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib/liblzma.so -lm /gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib/libdbus-glib-1.so -lgio-2.0 /gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/libdbus-1.so -lpthread -lgobject-2.0 -lglib-2.0 -lresolv -lutil -pthread -pthread -pthread -Wl,-soname -Wl,libnetwork.so -o .libs/libnetwork.so libtool: link: ( cd ".libs" && rm -f "libtar.la" && ln -s "../libtar.la" "libtar.la" ) libtool: link: gcc -shared .libs/test-method.o -Wl,-rpath -Wl,/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/libgnomevfs/.libs -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib ../libgnomevfs/.libs/libgnomevfs-2.so -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib -L/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib/libgconf-2.so /gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib/libORBit-2.so -lgmodule-2.0 -lgthread-2.0 /gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib/libxml2.so -ldl -lz /gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib/liblzma.so -lm /gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib/libdbus-glib-1.so -lgio-2.0 /gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/libdbus-1.so -lpthread -lgobject-2.0 -lglib-2.0 -lresolv -lutil -pthread -pthread -pthread -Wl,-soname -Wl,libvfs-test.so -o .libs/libvfs-test.so libtool: link: ar cru .libs/libnetwork.a network-method.o ar: `u' modifier ignored since `D' is the default (see `U') libtool: link: ranlib .libs/libnetwork.a libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../imported/neon -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DSSH_PROGRAM=\"ssh\" -DG_DISABLE_DEPRECATED -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"gnome-vfs-modules\" -g -O2 -MT nntp-method.lo -MD -MP -MF .deps/nntp-method.Tpo -c nntp-method.c -o nntp-method.o >/dev/null 2>&1 libtool: link: ( cd ".libs" && rm -f "libnetwork.la" && ln -s "../libnetwork.la" "libnetwork.la" ) libtool: link: ar cru .libs/libvfs-test.a test-method.o ar: `u' modifier ignored since `D' is the default (see `U') libtool: link: ranlib .libs/libvfs-test.a libtool: link: ( cd ".libs" && rm -f "libvfs-test.la" && ln -s "../libvfs-test.la" "libvfs-test.la" ) libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../imported/neon -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DSSH_PROGRAM=\"ssh\" -DG_DISABLE_DEPRECATED -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"gnome-vfs-modules\" -g -O2 -MT ftp-method.lo -MD -MP -MF .deps/ftp-method.Tpo -c ftp-method.c -o ftp-method.o >/dev/null 2>&1 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../imported/neon -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DSSH_PROGRAM=\"ssh\" -DG_DISABLE_DEPRECATED -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"gnome-vfs-modules\" -g -O2 -MT http-neon-method.lo -MD -MP -MF .deps/http-neon-method.Tpo -c http-neon-method.c -o http-neon-method.o >/dev/null 2>&1 mv -f .deps/file-method.Tpo .deps/file-method.Plo /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -export_dynamic -avoid-version -module -no-undefined -o libfile.la -rpath /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules file-method.lo fstype.lo file-method-acl.lo inotify-kernel.lo inotify-missing.lo inotify-path.lo inotify-sub.lo inotify-helper.lo inotify-diag.lo -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgmodule-2.0 -pthread -lgthread-2.0 -pthread -lgobject-2.0 -lgconf-2 -lglib-2.0 ../libgnomevfs/libgnomevfs-2.la -lutil libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../imported/neon -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DSSH_PROGRAM=\"ssh\" -DG_DISABLE_DEPRECATED -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"gnome-vfs-modules\" -g -O2 -MT sftp-method.lo -MD -MP -MF .deps/sftp-method.Tpo -c sftp-method.c -o sftp-method.o >/dev/null 2>&1 libtool: link: gcc -shared .libs/file-method.o .libs/fstype.o .libs/file-method-acl.o .libs/inotify-kernel.o .libs/inotify-missing.o .libs/inotify-path.o .libs/inotify-sub.o .libs/inotify-helper.o .libs/inotify-diag.o -Wl,-rpath -Wl,/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/libgnomevfs/.libs -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib ../libgnomevfs/.libs/libgnomevfs-2.so -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib/libgconf-2.so /gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib/libORBit-2.so -lgmodule-2.0 -lgthread-2.0 /gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib/libxml2.so -ldl -lz /gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib/liblzma.so -lm /gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib/libdbus-glib-1.so -lgio-2.0 /gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/libdbus-1.so -lpthread -lgobject-2.0 -lglib-2.0 -lresolv -lutil -pthread -pthread -pthread -Wl,-soname -Wl,libfile.so -o .libs/libfile.so mv -f .deps/nntp-method.Tpo .deps/nntp-method.Plo /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -export_dynamic -avoid-version -module -no-undefined -o libnntp.la -rpath /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules nntp-method.lo -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgmodule-2.0 -pthread -lgthread-2.0 -pthread -lgobject-2.0 -lglib-2.0 ../libgnomevfs/libgnomevfs-2.la -lutil libtool: link: ar cru .libs/libfile.a file-method.o fstype.o file-method-acl.o inotify-kernel.o inotify-missing.o inotify-path.o inotify-sub.o inotify-helper.o inotify-diag.o ar: `u' modifier ignored since `D' is the default (see `U') libtool: link: ranlib .libs/libfile.a libtool: link: ( cd ".libs" && rm -f "libfile.la" && ln -s "../libfile.la" "libfile.la" ) libtool: link: gcc -shared .libs/nntp-method.o -Wl,-rpath -Wl,/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/libgnomevfs/.libs -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib ../libgnomevfs/.libs/libgnomevfs-2.so -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib -L/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib/libgconf-2.so /gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib/libORBit-2.so -lgmodule-2.0 -lgthread-2.0 /gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib/libxml2.so -ldl -lz /gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib/liblzma.so -lm /gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib/libdbus-glib-1.so -lgio-2.0 /gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/libdbus-1.so -lpthread -lgobject-2.0 -lglib-2.0 -lresolv -lutil -pthread -pthread -pthread -Wl,-soname -Wl,libnntp.so -o .libs/libnntp.so mv -f .deps/ftp-method.Tpo .deps/ftp-method.Plo /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -export_dynamic -avoid-version -module -no-undefined -o libftp.la -rpath /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules ftp-method.lo -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgmodule-2.0 -pthread -lgthread-2.0 -pthread -lgobject-2.0 -lgconf-2 -lglib-2.0 ../libgnomevfs/libgnomevfs-2.la -lutil libtool: link: ar cru .libs/libnntp.a nntp-method.o ar: `u' modifier ignored since `D' is the default (see `U') libtool: link: ranlib .libs/libnntp.a libtool: link: ( cd ".libs" && rm -f "libnntp.la" && ln -s "../libnntp.la" "libnntp.la" ) mv -f .deps/http-neon-method.Tpo .deps/http-neon-method.Plo /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -export_dynamic -avoid-version -module -no-undefined -o libhttp.la -rpath /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules http-neon-method.lo http-proxy.lo -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgmodule-2.0 -pthread -lgthread-2.0 -pthread -lgobject-2.0 -lgconf-2 -lglib-2.0 ../imported/neon/libneon.la ../libgnomevfs/libgnomevfs-2.la -lutil libtool: link: gcc -shared .libs/ftp-method.o -Wl,-rpath -Wl,/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/libgnomevfs/.libs -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib ../libgnomevfs/.libs/libgnomevfs-2.so -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib/libgconf-2.so /gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib/libORBit-2.so -lgmodule-2.0 -lgthread-2.0 /gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib/libxml2.so -ldl -lz /gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib/liblzma.so -lm /gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib/libdbus-glib-1.so -lgio-2.0 /gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/libdbus-1.so -lpthread -lgobject-2.0 -lglib-2.0 -lresolv -lutil -pthread -pthread -pthread -Wl,-soname -Wl,libftp.so -o .libs/libftp.so libtool: link: ar cru .libs/libftp.a ftp-method.o ar: `u' modifier ignored since `D' is the default (see `U') libtool: link: ranlib .libs/libftp.a libtool: link: ( cd ".libs" && rm -f "libftp.la" && ln -s "../libftp.la" "libftp.la" ) libtool: link: gcc -shared .libs/http-neon-method.o .libs/http-proxy.o -Wl,--whole-archive ../imported/neon/.libs/libneon.a -Wl,--no-whole-archive -Wl,-rpath -Wl,/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/libgnomevfs/.libs -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib ../libgnomevfs/.libs/libgnomevfs-2.so -L/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib/libgconf-2.so /gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib/libORBit-2.so -lgmodule-2.0 -lgthread-2.0 /gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib/libxml2.so -ldl -lz /gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib/liblzma.so -lm /gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib/libdbus-glib-1.so -lgio-2.0 /gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/libdbus-1.so -lpthread -lgobject-2.0 -lglib-2.0 -lresolv -lutil -pthread -pthread -pthread -Wl,-soname -Wl,libhttp.so -o .libs/libhttp.so libtool: link: (cd .libs/libhttp.lax/libneon.a && ar x "/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/modules/../imported/neon/.libs/libneon.a") libtool: link: ar cru .libs/libhttp.a http-neon-method.o http-proxy.o .libs/libhttp.lax/libneon.a/ne_request.o .libs/libhttp.lax/libneon.a/ne_session.o .libs/libhttp.lax/libneon.a/ne_basic.o .libs/libhttp.lax/libneon.a/ne_string.o .libs/libhttp.lax/libneon.a/ne_uri.o .libs/libhttp.lax/libneon.a/ne_dates.o .libs/libhttp.lax/libneon.a/ne_alloc.o .libs/libhttp.lax/libneon.a/ne_md5.o .libs/libhttp.lax/libneon.a/ne_utils.o .libs/libhttp.lax/libneon.a/ne_auth.o .libs/libhttp.lax/libneon.a/ne_redirect.o .libs/libhttp.lax/libneon.a/ne_compress.o .libs/libhttp.lax/libneon.a/ne_207.o .libs/libhttp.lax/libneon.a/ne_xml.o .libs/libhttp.lax/libneon.a/ne_props.o .libs/libhttp.lax/libneon.a/ne_locks.o .libs/libhttp.lax/libneon.a/ne_xmlreq.o .libs/libhttp.lax/libneon.a/ne_acl.o .libs/libhttp.lax/libneon.a/ne_gnomevfs.o ar: `u' modifier ignored since `D' is the default (see `U') libtool: link: ranlib .libs/libhttp.a libtool: link: rm -fr .libs/libhttp.lax libtool: link: ( cd ".libs" && rm -f "libhttp.la" && ln -s "../libhttp.la" "libhttp.la" ) mv -f .deps/sftp-method.Tpo .deps/sftp-method.Plo /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -export_dynamic -avoid-version -module -no-undefined -o libsftp.la -rpath /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules sftp-method.lo -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgmodule-2.0 -pthread -lgthread-2.0 -pthread -lgobject-2.0 -lglib-2.0 ../libgnomevfs/libgnomevfs-2.la -lutil libtool: link: gcc -shared .libs/sftp-method.o -Wl,-rpath -Wl,/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/libgnomevfs/.libs -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib ../libgnomevfs/.libs/libgnomevfs-2.so -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib -L/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib/libgconf-2.so /gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib/libORBit-2.so -lgmodule-2.0 -lgthread-2.0 /gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib/libxml2.so -ldl -lz /gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib/liblzma.so -lm /gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib/libdbus-glib-1.so -lgio-2.0 /gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/libdbus-1.so -lpthread -lgobject-2.0 -lglib-2.0 -lresolv -lutil -pthread -pthread -pthread -Wl,-soname -Wl,libsftp.so -o .libs/libsftp.so libtool: link: ar cru .libs/libsftp.a sftp-method.o ar: `u' modifier ignored since `D' is the default (see `U') libtool: link: ranlib .libs/libsftp.a libtool: link: ( cd ".libs" && rm -f "libsftp.la" && ln -s "../libsftp.la" "libsftp.la" ) make[2]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/modules' Making all in daemon make[2]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/daemon' gcc -DHAVE_CONFIG_H -I. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOMEVFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -I.. -I.. -I../libgnomevfs -I../libgnomevfs -g -O2 -MT dbus-utils.o -MD -MP -MF .deps/dbus-utils.Tpo -c -o dbus-utils.o dbus-utils.c gcc -DHAVE_CONFIG_H -I. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOMEVFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -I.. -I.. -I../libgnomevfs -I../libgnomevfs -g -O2 -MT vfs-daemon.o -MD -MP -MF .deps/vfs-daemon.Tpo -c -o vfs-daemon.o vfs-daemon.c gcc -DHAVE_CONFIG_H -I. -I.. -DORBIT2=1 -pthread -I/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/include/libxml2 -I/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/include/dbus-1.0 -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/include/dbus-1.0 -I/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/dbus-1.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -DDBUS_API_SUBJECT_TO_CHANGE -D_FILE_OFFSET_BITS=64 -D_BSD_SOURCE -D_LARGEFILE64_SOURCE -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -DGLIB_DISABLE_DEPRECATION_WARNINGS -DGNOME_VFS_PREFIX=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4\" -DGNOME_VFS_DATADIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share\" -DGNOME_VFS_LIBDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib\" -DGNOMEVFS_LOCALEDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale\" -DGNOME_VFS_SYSCONFDIR=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc\" -DG_LOG_DOMAIN=\"libgnomevfs\" -I.. -I.. -I../libgnomevfs -I../libgnomevfs -g -O2 -MT daemon-connection.o -MD -MP -MF .deps/daemon-connection.Tpo -c -o daemon-connection.o daemon-connection.c sed -e "s|\@libexecdir\@|/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/libexec|" gnome-vfs-daemon.service.in > gnome-vfs-daemon.service In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/sys/stat.h:25, from vfs-daemon.c:22: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/string.h:26, from dbus-utils.c:22: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ In file included from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/bits/libc-header-start.h:33, from /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/stdlib.h:25, from daemon-connection.c:22: /gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~~~~~ mv -f .deps/dbus-utils.Tpo .deps/dbus-utils.Po mv -f .deps/vfs-daemon.Tpo .deps/vfs-daemon.Po mv -f .deps/daemon-connection.Tpo .deps/daemon-connection.Po /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -o gnome-vfs-daemon dbus-utils.o vfs-daemon.o daemon-connection.o -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -lgmodule-2.0 -pthread -lgthread-2.0 -pthread -lgconf-2 -lxml2 -ldbus-glib-1 -ldbus-1 -lgobject-2.0 -lglib-2.0 -lresolv -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lglib-2.0 ../libgnomevfs/libgnomevfsdaemon-2.la ../libgnomevfs/libgnomevfs-2.la -lutil libtool: link: gcc -g -O2 -o .libs/gnome-vfs-daemon dbus-utils.o vfs-daemon.o daemon-connection.o -pthread -pthread -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib ../libgnomevfs/.libs/libgnomevfsdaemon-2.a /tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/libgnomevfs/.libs/libgnomevfs-2.so ../libgnomevfs/.libs/libgnomevfs-2.so /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib/libgconf-2.so /gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib/libORBit-2.so -lgmodule-2.0 -lgthread-2.0 /gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib/libxml2.so -ldl -lz /gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib/liblzma.so -lm /gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib/libdbus-glib-1.so -lgio-2.0 /gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/libdbus-1.so -lpthread -lgobject-2.0 -lglib-2.0 -lresolv -lutil -pthread -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib make[2]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/daemon' Making all in schemas make[2]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/schemas' make[2]: Nothing to be done for 'all'. make[2]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/schemas' Making all in devel-docs make[2]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/devel-docs' Making all in gnome-vfs-tutorial make[3]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/devel-docs/gnome-vfs-tutorial' make[3]: Nothing to be done for 'all'. make[3]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/devel-docs/gnome-vfs-tutorial' make[3]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/devel-docs' make[3]: Nothing to be done for 'all-am'. make[3]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/devel-docs' make[2]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/devel-docs' Making all in doc make[2]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/doc' make[2]: Nothing to be done for 'all'. make[2]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/doc' Making all in programs make[2]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/programs' gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DG_DISABLE_DEPRECATED -g -O2 -MT gnomevfs-cat.o -MD -MP -MF .deps/gnomevfs-cat.Tpo -c -o gnomevfs-cat.o gnomevfs-cat.c gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DG_DISABLE_DEPRECATED -g -O2 -MT gnomevfs-copy.o -MD -MP -MF .deps/gnomevfs-copy.Tpo -c -o gnomevfs-copy.o gnomevfs-copy.c gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DG_DISABLE_DEPRECATED -g -O2 -MT gnomevfs-info.o -MD -MP -MF .deps/gnomevfs-info.Tpo -c -o gnomevfs-info.o gnomevfs-info.c gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DG_DISABLE_DEPRECATED -g -O2 -MT gnomevfs-ls.o -MD -MP -MF .deps/gnomevfs-ls.Tpo -c -o gnomevfs-ls.o gnomevfs-ls.c gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DG_DISABLE_DEPRECATED -g -O2 -MT gnomevfs-monitor.o -MD -MP -MF .deps/gnomevfs-monitor.Tpo -c -o gnomevfs-monitor.o gnomevfs-monitor.c gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DG_DISABLE_DEPRECATED -g -O2 -MT gnomevfs-mkdir.o -MD -MP -MF .deps/gnomevfs-mkdir.Tpo -c -o gnomevfs-mkdir.o gnomevfs-mkdir.c gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DG_DISABLE_DEPRECATED -g -O2 -MT gnomevfs-mv.o -MD -MP -MF .deps/gnomevfs-mv.Tpo -c -o gnomevfs-mv.o gnomevfs-mv.c gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DG_DISABLE_DEPRECATED -g -O2 -MT gnomevfs-rm.o -MD -MP -MF .deps/gnomevfs-rm.Tpo -c -o gnomevfs-rm.o gnomevfs-rm.c gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DG_DISABLE_DEPRECATED -g -O2 -MT gnomevfs-df.o -MD -MP -MF .deps/gnomevfs-df.Tpo -c -o gnomevfs-df.o gnomevfs-df.c mv -f .deps/gnomevfs-rm.Tpo .deps/gnomevfs-rm.Po mv -f .deps/gnomevfs-mv.Tpo .deps/gnomevfs-mv.Po mv -f .deps/gnomevfs-cat.Tpo .deps/gnomevfs-cat.Po /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -o gnomevfs-rm gnomevfs-rm.o ../libgnomevfs/libgnomevfs-2.la -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgconf-2 -lgthread-2.0 -pthread -lglib-2.0 -lutil mv -f .deps/gnomevfs-copy.Tpo .deps/gnomevfs-copy.Po /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -o gnomevfs-mv gnomevfs-mv.o ../libgnomevfs/libgnomevfs-2.la -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgconf-2 -lgthread-2.0 -pthread -lglib-2.0 -lutil mv -f .deps/gnomevfs-mkdir.Tpo .deps/gnomevfs-mkdir.Po mv -f .deps/gnomevfs-monitor.Tpo .deps/gnomevfs-monitor.Po /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -o gnomevfs-cat gnomevfs-cat.o ../libgnomevfs/libgnomevfs-2.la -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgconf-2 -lgthread-2.0 -pthread -lglib-2.0 -lutil /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -o gnomevfs-copy gnomevfs-copy.o ../libgnomevfs/libgnomevfs-2.la -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgconf-2 -lgthread-2.0 -pthread -lglib-2.0 -lutil /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -o gnomevfs-mkdir gnomevfs-mkdir.o ../libgnomevfs/libgnomevfs-2.la -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgconf-2 -lgthread-2.0 -pthread -lglib-2.0 -lutil /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -o gnomevfs-monitor gnomevfs-monitor.o ../libgnomevfs/libgnomevfs-2.la -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgconf-2 -lgthread-2.0 -pthread -lglib-2.0 -lutil mv -f .deps/gnomevfs-df.Tpo .deps/gnomevfs-df.Po /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -o gnomevfs-df gnomevfs-df.o ../libgnomevfs/libgnomevfs-2.la -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgconf-2 -lgthread-2.0 -pthread -lglib-2.0 -lutil mv -f .deps/gnomevfs-ls.Tpo .deps/gnomevfs-ls.Po /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -o gnomevfs-ls gnomevfs-ls.o ../libgnomevfs/libgnomevfs-2.la -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgconf-2 -lgthread-2.0 -pthread -lglib-2.0 -lutil mv -f .deps/gnomevfs-info.Tpo .deps/gnomevfs-info.Po /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -o gnomevfs-info gnomevfs-info.o ../libgnomevfs/libgnomevfs-2.la -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgconf-2 -lgthread-2.0 -pthread -lglib-2.0 -lutil libtool: link: gcc -g -O2 -o .libs/gnomevfs-mv gnomevfs-mv.o -pthread ../libgnomevfs/.libs/libgnomevfs-2.so -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib /gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib/libxml2.so -ldl -lz /gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib/liblzma.so -lm -lresolv /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib/libgconf-2.so /gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib/libdbus-glib-1.so -lgio-2.0 /gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/libdbus-1.so -lpthread /gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib/libORBit-2.so -lgmodule-2.0 -lgobject-2.0 -lgthread-2.0 -lglib-2.0 -lutil -pthread -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib libtool: link: gcc -g -O2 -o .libs/gnomevfs-rm gnomevfs-rm.o -pthread ../libgnomevfs/.libs/libgnomevfs-2.so -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib /gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib/libxml2.so -ldl -lz /gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib/liblzma.so -lm -lresolv /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib/libgconf-2.so /gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib/libdbus-glib-1.so -lgio-2.0 /gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/libdbus-1.so -lpthread /gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib/libORBit-2.so -lgmodule-2.0 -lgobject-2.0 -lgthread-2.0 -lglib-2.0 -lutil -pthread -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib libtool: link: gcc -g -O2 -o .libs/gnomevfs-cat gnomevfs-cat.o -pthread ../libgnomevfs/.libs/libgnomevfs-2.so -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib /gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib/libxml2.so -ldl -lz /gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib/liblzma.so -lm -lresolv /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib/libgconf-2.so /gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib/libdbus-glib-1.so -lgio-2.0 /gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/libdbus-1.so -lpthread /gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib/libORBit-2.so -lgmodule-2.0 -lgobject-2.0 -lgthread-2.0 -lglib-2.0 -lutil -pthread -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib libtool: link: gcc -g -O2 -o .libs/gnomevfs-copy gnomevfs-copy.o -pthread ../libgnomevfs/.libs/libgnomevfs-2.so -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib /gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib/libxml2.so -ldl -lz /gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib/liblzma.so -lm -lresolv /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib/libgconf-2.so /gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib/libdbus-glib-1.so -lgio-2.0 /gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/libdbus-1.so -lpthread /gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib/libORBit-2.so -lgmodule-2.0 -lgobject-2.0 -lgthread-2.0 -lglib-2.0 -lutil -pthread -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib libtool: link: gcc -g -O2 -o .libs/gnomevfs-mkdir gnomevfs-mkdir.o -pthread ../libgnomevfs/.libs/libgnomevfs-2.so -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib /gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib/libxml2.so -ldl -lz /gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib/liblzma.so -lm -lresolv /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib/libgconf-2.so /gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib/libdbus-glib-1.so -lgio-2.0 /gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/libdbus-1.so -lpthread /gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib/libORBit-2.so -lgmodule-2.0 -lgobject-2.0 -lgthread-2.0 -lglib-2.0 -lutil -pthread -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib libtool: link: gcc -g -O2 -o .libs/gnomevfs-monitor gnomevfs-monitor.o -pthread ../libgnomevfs/.libs/libgnomevfs-2.so -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib /gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib/libxml2.so -ldl -lz /gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib/liblzma.so -lm -lresolv /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib/libgconf-2.so /gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib/libdbus-glib-1.so -lgio-2.0 /gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/libdbus-1.so -lpthread /gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib/libORBit-2.so -lgmodule-2.0 -lgobject-2.0 -lgthread-2.0 -lglib-2.0 -lutil -pthread -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib libtool: link: gcc -g -O2 -o .libs/gnomevfs-df gnomevfs-df.o -pthread ../libgnomevfs/.libs/libgnomevfs-2.so -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib /gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib/libxml2.so -ldl -lz /gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib/liblzma.so -lm -lresolv /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib/libgconf-2.so /gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib/libdbus-glib-1.so -lgio-2.0 /gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/libdbus-1.so -lpthread /gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib/libORBit-2.so -lgmodule-2.0 -lgobject-2.0 -lgthread-2.0 -lglib-2.0 -lutil -pthread -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib libtool: link: gcc -g -O2 -o .libs/gnomevfs-ls gnomevfs-ls.o -pthread ../libgnomevfs/.libs/libgnomevfs-2.so -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib /gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib/libxml2.so -ldl -lz /gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib/liblzma.so -lm -lresolv /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib/libgconf-2.so /gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib/libdbus-glib-1.so -lgio-2.0 /gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/libdbus-1.so -lpthread /gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib/libORBit-2.so -lgmodule-2.0 -lgobject-2.0 -lgthread-2.0 -lglib-2.0 -lutil -pthread -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib libtool: link: gcc -g -O2 -o .libs/gnomevfs-info gnomevfs-info.o -pthread ../libgnomevfs/.libs/libgnomevfs-2.so -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib /gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib/libxml2.so -ldl -lz /gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib/liblzma.so -lm -lresolv /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib/libgconf-2.so /gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib/libdbus-glib-1.so -lgio-2.0 /gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/libdbus-1.so -lpthread /gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib/libORBit-2.so -lgmodule-2.0 -lgobject-2.0 -lgthread-2.0 -lglib-2.0 -lutil -pthread -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib make[2]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/programs' Making all in test make[2]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/test' gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../libgnomevfs -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DG_DISABLE_DEPRECATED -DMODULES_PATH=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/vfs/modules\" -g -O2 -MT test-acl.o -MD -MP -MF .deps/test-acl.Tpo -c -o test-acl.o test-acl.c gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../libgnomevfs -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DG_DISABLE_DEPRECATED -DMODULES_PATH=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/vfs/modules\" -g -O2 -MT test-address.o -MD -MP -MF .deps/test-address.Tpo -c -o test-address.o test-address.c gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../libgnomevfs -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DG_DISABLE_DEPRECATED -DMODULES_PATH=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/vfs/modules\" -g -O2 -MT test-async.o -MD -MP -MF .deps/test-async.Tpo -c -o test-async.o test-async.c gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../libgnomevfs -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DG_DISABLE_DEPRECATED -DMODULES_PATH=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/vfs/modules\" -g -O2 -MT test-async-cancel.o -MD -MP -MF .deps/test-async-cancel.Tpo -c -o test-async-cancel.o test-async-cancel.c gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../libgnomevfs -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DG_DISABLE_DEPRECATED -DMODULES_PATH=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/vfs/modules\" -g -O2 -MT test-async-directory.o -MD -MP -MF .deps/test-async-directory.Tpo -c -o test-async-directory.o test-async-directory.c gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../libgnomevfs -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DG_DISABLE_DEPRECATED -DMODULES_PATH=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/vfs/modules\" -g -O2 -MT test-channel.o -MD -MP -MF .deps/test-channel.Tpo -c -o test-channel.o test-channel.c gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../libgnomevfs -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DG_DISABLE_DEPRECATED -DMODULES_PATH=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/vfs/modules\" -g -O2 -MT test-directory.o -MD -MP -MF .deps/test-directory.Tpo -c -o test-directory.o test-directory.c gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../libgnomevfs -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DG_DISABLE_DEPRECATED -DMODULES_PATH=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/vfs/modules\" -g -O2 -MT test-directory-visit.o -MD -MP -MF .deps/test-directory-visit.Tpo -c -o test-directory-visit.o test-directory-visit.c gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../libgnomevfs -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DG_DISABLE_DEPRECATED -DMODULES_PATH=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/vfs/modules\" -g -O2 -MT test-dirop.o -MD -MP -MF .deps/test-dirop.Tpo -c -o test-dirop.o test-dirop.c gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../libgnomevfs -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DG_DISABLE_DEPRECATED -DMODULES_PATH=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/vfs/modules\" -g -O2 -MT test-escape.o -MD -MP -MF .deps/test-escape.Tpo -c -o test-escape.o test-escape.c gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../libgnomevfs -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DG_DISABLE_DEPRECATED -DMODULES_PATH=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/vfs/modules\" -g -O2 -MT test-find-directory.o -MD -MP -MF .deps/test-find-directory.Tpo -c -o test-find-directory.o test-find-directory.c gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../libgnomevfs -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DG_DISABLE_DEPRECATED -DMODULES_PATH=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/vfs/modules\" -g -O2 -MT test-info.o -MD -MP -MF .deps/test-info.Tpo -c -o test-info.o test-info.c gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../libgnomevfs -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DG_DISABLE_DEPRECATED -DMODULES_PATH=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/vfs/modules\" -g -O2 -MT test-long-cancel.o -MD -MP -MF .deps/test-long-cancel.Tpo -c -o test-long-cancel.o test-long-cancel.c gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../libgnomevfs -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DG_DISABLE_DEPRECATED -DMODULES_PATH=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/vfs/modules\" -g -O2 -MT test-mime.o -MD -MP -MF .deps/test-mime.Tpo -c -o test-mime.o test-mime.c gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../libgnomevfs -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DG_DISABLE_DEPRECATED -DMODULES_PATH=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/vfs/modules\" -g -O2 -MT test-mime-handlers.o -MD -MP -MF .deps/test-mime-handlers.Tpo -c -o test-mime-handlers.o test-mime-handlers.c gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../libgnomevfs -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DG_DISABLE_DEPRECATED -DMODULES_PATH=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/vfs/modules\" -g -O2 -MT test-mime-info-cache.o -MD -MP -MF .deps/test-mime-info-cache.Tpo -c -o test-mime-info-cache.o test-mime-info-cache.c test-mime-info-cache.c: In function ‘main’: test-mime-info-cache.c:54:17: warning: ‘g_thread_create’ is deprecated: Use 'g_thread_new' instead [-Wdeprecated-declarations] 54 | (void) g_thread_create ((GThreadFunc) foo, mime_type, FALSE, NULL); | ^ In file included from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:112, from ../libgnomevfs/gnome-vfs-acl.h:28, from ../libgnomevfs/gnome-vfs.h:28, from test-mime-info-cache.c:2: /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/deprecated/gthread.h:100:10: note: declared here 100 | GThread *g_thread_create (GThreadFunc func, | ^~~~~~~~~~~~~~~ test-async-directory.c: In function ‘main’: test-async-directory.c:236:2: warning: implicit declaration of function ‘g_printf’; did you mean ‘g_print’? [-Wimplicit-function-declaration] 236 | g_printf("Initializing gnome-libs..."); | ^~~~~~~~ | g_print mv -f .deps/test-mime-handlers.Tpo .deps/test-mime-handlers.Po gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../libgnomevfs -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DG_DISABLE_DEPRECATED -DMODULES_PATH=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/vfs/modules\" -g -O2 -MT test-mime-handlers-set.o -MD -MP -MF .deps/test-mime-handlers-set.Tpo -c -o test-mime-handlers-set.o test-mime-handlers-set.c mv -f .deps/test-directory-visit.Tpo .deps/test-directory-visit.Po mv -f .deps/test-mime-info-cache.Tpo .deps/test-mime-info-cache.Po gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../libgnomevfs -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DG_DISABLE_DEPRECATED -DMODULES_PATH=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/vfs/modules\" -g -O2 -MT test-monitor.o -MD -MP -MF .deps/test-monitor.Tpo -c -o test-monitor.o test-monitor.c gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../libgnomevfs -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DG_DISABLE_DEPRECATED -DMODULES_PATH=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/vfs/modules\" -g -O2 -MT test-performance.o -MD -MP -MF .deps/test-performance.Tpo -c -o test-performance.o test-performance.c mv -f .deps/test-channel.Tpo .deps/test-channel.Po mv -f .deps/test-async.Tpo .deps/test-async.Po gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../libgnomevfs -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DG_DISABLE_DEPRECATED -DMODULES_PATH=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/vfs/modules\" -g -O2 -MT test-seek.o -MD -MP -MF .deps/test-seek.Tpo -c -o test-seek.o test-seek.c mv -f .deps/test-directory.Tpo .deps/test-directory.Po gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../libgnomevfs -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DG_DISABLE_DEPRECATED -DMODULES_PATH=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/vfs/modules\" -g -O2 -MT test-shell.o -MD -MP -MF .deps/test-shell.Tpo -c -o test-shell.o test-shell.c mv -f .deps/test-long-cancel.Tpo .deps/test-long-cancel.Po mv -f .deps/test-mime.Tpo .deps/test-mime.Po mv -f .deps/test-escape.Tpo .deps/test-escape.Po gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../libgnomevfs -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DG_DISABLE_DEPRECATED -DMODULES_PATH=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/vfs/modules\" -g -O2 -MT test-ssl.o -MD -MP -MF .deps/test-ssl.Tpo -c -o test-ssl.o test-ssl.c gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../libgnomevfs -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DG_DISABLE_DEPRECATED -DMODULES_PATH=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/vfs/modules\" -g -O2 -MT test-sync.o -MD -MP -MF .deps/test-sync.Tpo -c -o test-sync.o test-sync.c gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../libgnomevfs -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DG_DISABLE_DEPRECATED -DMODULES_PATH=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/vfs/modules\" -g -O2 -MT test-sync-create.o -MD -MP -MF .deps/test-sync-create.Tpo -c -o test-sync-create.o test-sync-create.c gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../libgnomevfs -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DG_DISABLE_DEPRECATED -DMODULES_PATH=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/vfs/modules\" -g -O2 -MT test-sync-write.o -MD -MP -MF .deps/test-sync-write.Tpo -c -o test-sync-write.o test-sync-write.c mv -f .deps/test-dirop.Tpo .deps/test-dirop.Po gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../libgnomevfs -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DG_DISABLE_DEPRECATED -DMODULES_PATH=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/vfs/modules\" -g -O2 -MT test-unlink.o -MD -MP -MF .deps/test-unlink.Tpo -c -o test-unlink.o test-unlink.c mv -f .deps/test-find-directory.Tpo .deps/test-find-directory.Po mv -f .deps/test-async-directory.Tpo .deps/test-async-directory.Po gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../libgnomevfs -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DG_DISABLE_DEPRECATED -DMODULES_PATH=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/vfs/modules\" -g -O2 -MT test-uri.o -MD -MP -MF .deps/test-uri.Tpo -c -o test-uri.o test-uri.c gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../libgnomevfs -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DG_DISABLE_DEPRECATED -DMODULES_PATH=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/vfs/modules\" -g -O2 -MT test-volumes.o -MD -MP -MF .deps/test-volumes.Tpo -c -o test-volumes.o test-volumes.c mv -f .deps/test-address.Tpo .deps/test-address.Po gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../libgnomevfs -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DG_DISABLE_DEPRECATED -DMODULES_PATH=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/vfs/modules\" -g -O2 -MT test-xfer.o -MD -MP -MF .deps/test-xfer.Tpo -c -o test-xfer.o test-xfer.c mv -f .deps/test-acl.Tpo .deps/test-acl.Po mv -f .deps/test-info.Tpo .deps/test-info.Po gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../libgnomevfs -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DG_DISABLE_DEPRECATED -DMODULES_PATH=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/vfs/modules\" -g -O2 -MT test-callback.o -MD -MP -MF .deps/test-callback.Tpo -c -o test-callback.o test-callback.c gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../libgnomevfs -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DG_DISABLE_DEPRECATED -DMODULES_PATH=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/vfs/modules\" -g -O2 -MT test-module-selftest.o -MD -MP -MF .deps/test-module-selftest.Tpo -c -o test-module-selftest.o test-module-selftest.c test-performance.c: In function ‘main’: test-performance.c:14:2: warning: ‘g_type_init’ is deprecated [-Wdeprecated-declarations] 14 | g_type_init (); | ^~~~~~~~~~~ In file included from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/gobject/gobject.h:24, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/gobject/gbinding.h:29, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib-object.h:22, from test-performance.c:4: /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/gobject/gtype.h:710:23: note: declared here 710 | void g_type_init (void); | ^~~~~~~~~~~ In file included from ../libgnomevfs/gnome-vfs-ssl.h:29, from test-shell.c:35: ../libgnomevfs/gnome-vfs-socket.h:124:8: warning: ‘GTimeVal’ is deprecated: Use 'GDateTime' instead [-Wdeprecated-declarations] 124 | GTimeVal *timeout, | ^~~~~~~~ In file included from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from test-shell.c:30: /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:547:8: note: declared here 547 | struct _GTimeVal | ^~~~~~~~~ In file included from ../libgnomevfs/gnome-vfs-ssl.h:29, from test-shell.c:35: ../libgnomevfs/gnome-vfs-socket.h:163:8: warning: ‘GTimeVal’ is deprecated: Use 'GDateTime' instead [-Wdeprecated-declarations] 163 | GTimeVal *timeout, | ^~~~~~~~ In file included from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from test-shell.c:30: /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:547:8: note: declared here 547 | struct _GTimeVal | ^~~~~~~~~ In file included from test-shell.c:35: ../libgnomevfs/gnome-vfs-ssl.h:57:12: warning: ‘GTimeVal’ is deprecated: Use 'GDateTime' instead [-Wdeprecated-declarations] 57 | GTimeVal *timeout, | ^~~~~~~~ In file included from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from test-shell.c:30: /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:547:8: note: declared here 547 | struct _GTimeVal | ^~~~~~~~~ mv -f .deps/test-performance.Tpo .deps/test-performance.Po mv -f .deps/test-mime-handlers-set.Tpo .deps/test-mime-handlers-set.Po In file included from ../libgnomevfs/gnome-vfs-socket-buffer.h:32, from test-ssl.c:29: ../libgnomevfs/gnome-vfs-socket.h:124:8: warning: ‘GTimeVal’ is deprecated: Use 'GDateTime' instead [-Wdeprecated-declarations] 124 | GTimeVal *timeout, | ^~~~~~~~ In file included from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from test-ssl.c:27: /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:547:8: note: declared here 547 | struct _GTimeVal | ^~~~~~~~~ In file included from ../libgnomevfs/gnome-vfs-socket-buffer.h:32, from test-ssl.c:29: ../libgnomevfs/gnome-vfs-socket.h:163:8: warning: ‘GTimeVal’ is deprecated: Use 'GDateTime' instead [-Wdeprecated-declarations] 163 | GTimeVal *timeout, | ^~~~~~~~ In file included from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from test-ssl.c:27: /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:547:8: note: declared here 547 | struct _GTimeVal | ^~~~~~~~~ In file included from test-ssl.c:31: ../libgnomevfs/gnome-vfs-ssl.h:57:12: warning: ‘GTimeVal’ is deprecated: Use 'GDateTime' instead [-Wdeprecated-declarations] 57 | GTimeVal *timeout, | ^~~~~~~~ In file included from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/galloca.h:32, from /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib.h:30, from test-ssl.c:27: /gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0/glib/gtypes.h:547:8: note: declared here 547 | struct _GTimeVal | ^~~~~~~~~ gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../libgnomevfs -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DG_DISABLE_DEPRECATED -DMODULES_PATH=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/vfs/modules\" -g -O2 -MT test-queue.o -MD -MP -MF .deps/test-queue.Tpo -c -o test-queue.o test-queue.c gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../libgnomevfs -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DG_DISABLE_DEPRECATED -DMODULES_PATH=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/vfs/modules\" -g -O2 -MT test-dns-sd.o -MD -MP -MF .deps/test-dns-sd.Tpo -c -o test-dns-sd.o test-dns-sd.c mv -f .deps/test-async-cancel.Tpo .deps/test-async-cancel.Po mv -f .deps/test-sync-write.Tpo .deps/test-sync-write.Po mv -f .deps/test-sync.Tpo .deps/test-sync.Po mv -f .deps/test-monitor.Tpo .deps/test-monitor.Po gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../libgnomevfs -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DG_DISABLE_DEPRECATED -DMODULES_PATH=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/vfs/modules\" -g -O2 -MT test-symlinks.o -MD -MP -MF .deps/test-symlinks.Tpo -c -o test-symlinks.o test-symlinks.c gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../libgnomevfs -DORBIT2=1 -pthread -I/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/include/gconf/2 -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/libmount -I/gnu/store/x2gbx78yz9322i0in263h5ahfgkr2h2q-util-linux-2.37.2-lib/include/blkid -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/include/glib-2.0 -I/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib/glib-2.0/include -I/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/include/orbit-2.0 -DG_DISABLE_DEPRECATED -DMODULES_PATH=\"/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/vfs/modules\" -g -O2 -MT test-parse-ls-lga.o -MD -MP -MF .deps/test-parse-ls-lga.Tpo -c -o test-parse-ls-lga.o test-parse-ls-lga.c mv -f .deps/test-sync-create.Tpo .deps/test-sync-create.Po /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -o test-address test-address.o ../libgnomevfs/libgnomevfs-2.la -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgconf-2 -lgthread-2.0 -pthread -lglib-2.0 -lutil /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -o test-acl test-acl.o ../libgnomevfs/libgnomevfs-2.la -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgconf-2 -lgthread-2.0 -pthread -lglib-2.0 -lutil /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -o test-async test-async.o ../libgnomevfs/libgnomevfs-2.la -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgconf-2 -lgthread-2.0 -pthread -lglib-2.0 -lutil mv -f .deps/test-unlink.Tpo .deps/test-unlink.Po mv -f .deps/test-seek.Tpo .deps/test-seek.Po /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -o test-async-cancel test-async-cancel.o ../libgnomevfs/libgnomevfs-2.la -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgconf-2 -lgthread-2.0 -pthread -lglib-2.0 -lutil /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -o test-async-directory test-async-directory.o ../libgnomevfs/libgnomevfs-2.la -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgconf-2 -lgthread-2.0 -pthread -lglib-2.0 -lutil mv -f .deps/test-xfer.Tpo .deps/test-xfer.Po mv -f .deps/test-module-selftest.Tpo .deps/test-module-selftest.Po mv -f .deps/test-ssl.Tpo .deps/test-ssl.Po /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -o test-channel test-channel.o ../libgnomevfs/libgnomevfs-2.la -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgconf-2 -lgthread-2.0 -pthread -lglib-2.0 -lutil /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -o test-directory test-directory.o ../libgnomevfs/libgnomevfs-2.la -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgconf-2 -lgthread-2.0 -pthread -lglib-2.0 -lutil /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -o test-directory-visit test-directory-visit.o ../libgnomevfs/libgnomevfs-2.la -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgconf-2 -lgthread-2.0 -pthread -lglib-2.0 -lutil mv -f .deps/test-volumes.Tpo .deps/test-volumes.Po /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -o test-dirop test-dirop.o ../libgnomevfs/libgnomevfs-2.la -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgconf-2 -lgthread-2.0 -pthread -lglib-2.0 -lutil mv -f .deps/test-dns-sd.Tpo .deps/test-dns-sd.Po /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -o test-escape test-escape.o ../libgnomevfs/libgnomevfs-2.la -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgconf-2 -lgthread-2.0 -pthread -lglib-2.0 -lutil mv -f .deps/test-parse-ls-lga.Tpo .deps/test-parse-ls-lga.Po /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -o test-find-directory test-find-directory.o ../libgnomevfs/libgnomevfs-2.la -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgconf-2 -lgthread-2.0 -pthread -lglib-2.0 -lutil libtool: link: gcc -g -O2 -o .libs/test-async test-async.o -pthread ../libgnomevfs/.libs/libgnomevfs-2.so -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib /gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib/libxml2.so -ldl -lz /gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib/liblzma.so -lm -lresolv /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib/libgconf-2.so /gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib/libdbus-glib-1.so -lgio-2.0 /gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/libdbus-1.so -lpthread /gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib/libORBit-2.so -lgmodule-2.0 -lgobject-2.0 -lgthread-2.0 -lglib-2.0 -lutil -pthread -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib libtool: link: gcc -g -O2 -o .libs/test-acl test-acl.o -pthread ../libgnomevfs/.libs/libgnomevfs-2.so -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib /gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib/libxml2.so -ldl -lz /gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib/liblzma.so -lm -lresolv /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib/libgconf-2.so /gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib/libdbus-glib-1.so -lgio-2.0 /gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/libdbus-1.so -lpthread /gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib/libORBit-2.so -lgmodule-2.0 -lgobject-2.0 -lgthread-2.0 -lglib-2.0 -lutil -pthread -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib libtool: link: gcc -g -O2 -o .libs/test-address test-address.o -pthread ../libgnomevfs/.libs/libgnomevfs-2.so -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib /gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib/libxml2.so -ldl -lz /gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib/liblzma.so -lm -lresolv /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib/libgconf-2.so /gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib/libdbus-glib-1.so -lgio-2.0 /gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/libdbus-1.so -lpthread /gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib/libORBit-2.so -lgmodule-2.0 -lgobject-2.0 -lgthread-2.0 -lglib-2.0 -lutil -pthread -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib mv -f .deps/test-queue.Tpo .deps/test-queue.Po mv -f .deps/test-symlinks.Tpo .deps/test-symlinks.Po mv -f .deps/test-uri.Tpo .deps/test-uri.Po /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -o test-info test-info.o ../libgnomevfs/libgnomevfs-2.la -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgconf-2 -lgthread-2.0 -pthread -lglib-2.0 -lutil /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -o test-long-cancel test-long-cancel.o ../libgnomevfs/libgnomevfs-2.la -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgconf-2 -lgthread-2.0 -pthread -lglib-2.0 -lutil /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -o test-mime test-mime.o ../libgnomevfs/libgnomevfs-2.la -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgconf-2 -lgthread-2.0 -pthread -lglib-2.0 -lutil libtool: link: gcc -g -O2 -o .libs/test-async-cancel test-async-cancel.o -pthread ../libgnomevfs/.libs/libgnomevfs-2.so -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib /gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib/libxml2.so -ldl -lz /gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib/liblzma.so -lm -lresolv /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib/libgconf-2.so /gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib/libdbus-glib-1.so -lgio-2.0 /gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/libdbus-1.so -lpthread /gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib/libORBit-2.so -lgmodule-2.0 -lgobject-2.0 -lgthread-2.0 -lglib-2.0 -lutil -pthread -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib libtool: link: gcc -g -O2 -o .libs/test-async-directory test-async-directory.o -pthread ../libgnomevfs/.libs/libgnomevfs-2.so -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib /gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib/libxml2.so -ldl -lz /gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib/liblzma.so -lm -lresolv /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib/libgconf-2.so /gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib/libdbus-glib-1.so -lgio-2.0 /gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/libdbus-1.so -lpthread /gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib/libORBit-2.so -lgmodule-2.0 -lgobject-2.0 -lgthread-2.0 -lglib-2.0 -lutil -pthread -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib libtool: link: gcc -g -O2 -o .libs/test-directory-visit test-directory-visit.o -pthread ../libgnomevfs/.libs/libgnomevfs-2.so -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib /gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib/libxml2.so -ldl -lz /gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib/liblzma.so -lm -lresolv /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib/libgconf-2.so /gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib/libdbus-glib-1.so -lgio-2.0 /gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/libdbus-1.so -lpthread /gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib/libORBit-2.so -lgmodule-2.0 -lgobject-2.0 -lgthread-2.0 -lglib-2.0 -lutil -pthread -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib libtool: link: gcc -g -O2 -o .libs/test-directory test-directory.o -pthread ../libgnomevfs/.libs/libgnomevfs-2.so -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib /gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib/libxml2.so -ldl -lz /gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib/liblzma.so -lm -lresolv /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib/libgconf-2.so /gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib/libdbus-glib-1.so -lgio-2.0 /gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/libdbus-1.so -lpthread /gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib/libORBit-2.so -lgmodule-2.0 -lgobject-2.0 -lgthread-2.0 -lglib-2.0 -lutil -pthread -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib mv -f .deps/test-callback.Tpo .deps/test-callback.Po libtool: link: gcc -g -O2 -o .libs/test-channel test-channel.o -pthread ../libgnomevfs/.libs/libgnomevfs-2.so -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib /gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib/libxml2.so -ldl -lz /gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib/liblzma.so -lm -lresolv /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib/libgconf-2.so /gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib/libdbus-glib-1.so -lgio-2.0 /gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/libdbus-1.so -lpthread /gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib/libORBit-2.so -lgmodule-2.0 -lgobject-2.0 -lgthread-2.0 -lglib-2.0 -lutil -pthread -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -o test-mime-handlers test-mime-handlers.o ../libgnomevfs/libgnomevfs-2.la -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgconf-2 -lgthread-2.0 -pthread -lglib-2.0 -lutil /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -o test-mime-info-cache test-mime-info-cache.o ../libgnomevfs/libgnomevfs-2.la -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgconf-2 -lgthread-2.0 -pthread -lglib-2.0 -lutil /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -o test-mime-handlers-set test-mime-handlers-set.o ../libgnomevfs/libgnomevfs-2.la -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgconf-2 -lgthread-2.0 -pthread -lglib-2.0 -lutil libtool: link: gcc -g -O2 -o .libs/test-dirop test-dirop.o -pthread ../libgnomevfs/.libs/libgnomevfs-2.so -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib /gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib/libxml2.so -ldl -lz /gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib/liblzma.so -lm -lresolv /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib/libgconf-2.so /gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib/libdbus-glib-1.so -lgio-2.0 /gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/libdbus-1.so -lpthread /gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib/libORBit-2.so -lgmodule-2.0 -lgobject-2.0 -lgthread-2.0 -lglib-2.0 -lutil -pthread -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -o test-monitor test-monitor.o ../libgnomevfs/libgnomevfs-2.la -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgconf-2 -lgthread-2.0 -pthread -lglib-2.0 -lutil libtool: link: gcc -g -O2 -o .libs/test-escape test-escape.o -pthread ../libgnomevfs/.libs/libgnomevfs-2.so -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib /gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib/libxml2.so -ldl -lz /gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib/liblzma.so -lm -lresolv /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib/libgconf-2.so /gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib/libdbus-glib-1.so -lgio-2.0 /gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/libdbus-1.so -lpthread /gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib/libORBit-2.so -lgmodule-2.0 -lgobject-2.0 -lgthread-2.0 -lglib-2.0 -lutil -pthread -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -o test-performance test-performance.o ../libgnomevfs/libgnomevfs-2.la -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgconf-2 -lgthread-2.0 -pthread -lglib-2.0 -lutil /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -o test-seek test-seek.o ../libgnomevfs/libgnomevfs-2.la -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgconf-2 -lgthread-2.0 -pthread -lglib-2.0 -lutil libtool: link: gcc -g -O2 -o .libs/test-find-directory test-find-directory.o -pthread ../libgnomevfs/.libs/libgnomevfs-2.so -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib /gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib/libxml2.so -ldl -lz /gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib/liblzma.so -lm -lresolv /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib/libgconf-2.so /gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib/libdbus-glib-1.so -lgio-2.0 /gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/libdbus-1.so -lpthread /gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib/libORBit-2.so -lgmodule-2.0 -lgobject-2.0 -lgthread-2.0 -lglib-2.0 -lutil -pthread -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -o test-sync test-sync.o ../libgnomevfs/libgnomevfs-2.la -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgconf-2 -lgthread-2.0 -pthread -lglib-2.0 -lutil /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -o test-ssl test-ssl.o ../libgnomevfs/libgnomevfs-2.la -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgconf-2 -lgthread-2.0 -pthread -lglib-2.0 -lutil /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -o test-sync-create test-sync-create.o ../libgnomevfs/libgnomevfs-2.la -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgconf-2 -lgthread-2.0 -pthread -lglib-2.0 -lutil libtool: link: gcc -g -O2 -o .libs/test-info test-info.o -pthread ../libgnomevfs/.libs/libgnomevfs-2.so -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib /gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib/libxml2.so -ldl -lz /gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib/liblzma.so -lm -lresolv /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib/libgconf-2.so /gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib/libdbus-glib-1.so -lgio-2.0 /gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/libdbus-1.so -lpthread /gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib/libORBit-2.so -lgmodule-2.0 -lgobject-2.0 -lgthread-2.0 -lglib-2.0 -lutil -pthread -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib libtool: link: gcc -g -O2 -o .libs/test-mime test-mime.o -pthread ../libgnomevfs/.libs/libgnomevfs-2.so -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib /gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib/libxml2.so -ldl -lz /gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib/liblzma.so -lm -lresolv /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib/libgconf-2.so /gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib/libdbus-glib-1.so -lgio-2.0 /gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/libdbus-1.so -lpthread /gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib/libORBit-2.so -lgmodule-2.0 -lgobject-2.0 -lgthread-2.0 -lglib-2.0 -lutil -pthread -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib libtool: link: gcc -g -O2 -o .libs/test-long-cancel test-long-cancel.o -pthread ../libgnomevfs/.libs/libgnomevfs-2.so -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib /gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib/libxml2.so -ldl -lz /gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib/liblzma.so -lm -lresolv /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib/libgconf-2.so /gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib/libdbus-glib-1.so -lgio-2.0 /gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/libdbus-1.so -lpthread /gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib/libORBit-2.so -lgmodule-2.0 -lgobject-2.0 -lgthread-2.0 -lglib-2.0 -lutil -pthread -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -o test-sync-write test-sync-write.o ../libgnomevfs/libgnomevfs-2.la -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgconf-2 -lgthread-2.0 -pthread -lglib-2.0 -lutil /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -o test-unlink test-unlink.o ../libgnomevfs/libgnomevfs-2.la -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgconf-2 -lgthread-2.0 -pthread -lglib-2.0 -lutil libtool: link: gcc -g -O2 -o .libs/test-mime-handlers test-mime-handlers.o -pthread ../libgnomevfs/.libs/libgnomevfs-2.so -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib /gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib/libxml2.so -ldl -lz /gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib/liblzma.so -lm -lresolv /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib/libgconf-2.so /gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib/libdbus-glib-1.so -lgio-2.0 /gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/libdbus-1.so -lpthread /gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib/libORBit-2.so -lgmodule-2.0 -lgobject-2.0 -lgthread-2.0 -lglib-2.0 -lutil -pthread -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -o test-uri test-uri.o ../libgnomevfs/libgnomevfs-2.la -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgconf-2 -lgthread-2.0 -pthread -lglib-2.0 -lutil libtool: link: gcc -g -O2 -o .libs/test-mime-info-cache test-mime-info-cache.o -pthread ../libgnomevfs/.libs/libgnomevfs-2.so -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib /gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib/libxml2.so -ldl -lz /gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib/liblzma.so -lm -lresolv /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib/libgconf-2.so /gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib/libdbus-glib-1.so -lgio-2.0 /gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/libdbus-1.so -lpthread /gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib/libORBit-2.so -lgmodule-2.0 -lgobject-2.0 -lgthread-2.0 -lglib-2.0 -lutil -pthread -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib libtool: link: gcc -g -O2 -o .libs/test-mime-handlers-set test-mime-handlers-set.o -pthread ../libgnomevfs/.libs/libgnomevfs-2.so -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib /gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib/libxml2.so -ldl -lz /gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib/liblzma.so -lm -lresolv /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib/libgconf-2.so /gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib/libdbus-glib-1.so -lgio-2.0 /gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/libdbus-1.so -lpthread /gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib/libORBit-2.so -lgmodule-2.0 -lgobject-2.0 -lgthread-2.0 -lglib-2.0 -lutil -pthread -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib libtool: link: gcc -g -O2 -o .libs/test-monitor test-monitor.o -pthread ../libgnomevfs/.libs/libgnomevfs-2.so -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib /gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib/libxml2.so -ldl -lz /gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib/liblzma.so -lm -lresolv /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib/libgconf-2.so /gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib/libdbus-glib-1.so -lgio-2.0 /gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/libdbus-1.so -lpthread /gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib/libORBit-2.so -lgmodule-2.0 -lgobject-2.0 -lgthread-2.0 -lglib-2.0 -lutil -pthread -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -o test-volumes test-volumes.o ../libgnomevfs/libgnomevfs-2.la -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgconf-2 -lgthread-2.0 -pthread -lglib-2.0 -lutil /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -o test-xfer test-xfer.o ../libgnomevfs/libgnomevfs-2.la -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgconf-2 -lgthread-2.0 -pthread -lglib-2.0 -lutil libtool: link: gcc -g -O2 -o .libs/test-performance test-performance.o -pthread ../libgnomevfs/.libs/libgnomevfs-2.so -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib /gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib/libxml2.so -ldl -lz /gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib/liblzma.so -lm -lresolv /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib/libgconf-2.so /gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib/libdbus-glib-1.so -lgio-2.0 /gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/libdbus-1.so -lpthread /gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib/libORBit-2.so -lgmodule-2.0 -lgobject-2.0 -lgthread-2.0 -lglib-2.0 -lutil -pthread -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib libtool: link: gcc -g -O2 -o .libs/test-seek test-seek.o -pthread ../libgnomevfs/.libs/libgnomevfs-2.so -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib /gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib/libxml2.so -ldl -lz /gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib/liblzma.so -lm -lresolv /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib/libgconf-2.so /gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib/libdbus-glib-1.so -lgio-2.0 /gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/libdbus-1.so -lpthread /gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib/libORBit-2.so -lgmodule-2.0 -lgobject-2.0 -lgthread-2.0 -lglib-2.0 -lutil -pthread -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -o test-callback test-callback.o ../libgnomevfs/libgnomevfs-2.la -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgconf-2 -lgthread-2.0 -pthread -lglib-2.0 -lutil libtool: link: gcc -g -O2 -o .libs/test-sync test-sync.o -pthread ../libgnomevfs/.libs/libgnomevfs-2.so -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib /gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib/libxml2.so -ldl -lz /gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib/liblzma.so -lm -lresolv /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib/libgconf-2.so /gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib/libdbus-glib-1.so -lgio-2.0 /gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/libdbus-1.so -lpthread /gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib/libORBit-2.so -lgmodule-2.0 -lgobject-2.0 -lgthread-2.0 -lglib-2.0 -lutil -pthread -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib libtool: link: gcc -g -O2 -o .libs/test-ssl test-ssl.o -pthread ../libgnomevfs/.libs/libgnomevfs-2.so -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib /gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib/libxml2.so -ldl -lz /gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib/liblzma.so -lm -lresolv /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib/libgconf-2.so /gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib/libdbus-glib-1.so -lgio-2.0 /gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/libdbus-1.so -lpthread /gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib/libORBit-2.so -lgmodule-2.0 -lgobject-2.0 -lgthread-2.0 -lglib-2.0 -lutil -pthread -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib libtool: link: gcc -g -O2 -o .libs/test-sync-create test-sync-create.o -pthread ../libgnomevfs/.libs/libgnomevfs-2.so -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib /gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib/libxml2.so -ldl -lz /gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib/liblzma.so -lm -lresolv /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib/libgconf-2.so /gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib/libdbus-glib-1.so -lgio-2.0 /gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/libdbus-1.so -lpthread /gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib/libORBit-2.so -lgmodule-2.0 -lgobject-2.0 -lgthread-2.0 -lglib-2.0 -lutil -pthread -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -o test-module-selftest test-module-selftest.o ../libgnomevfs/libgnomevfs-2.la -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgconf-2 -lgthread-2.0 -pthread -lglib-2.0 -lutil /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -o test-queue test-queue.o ../libgnomevfs/libgnomevfs-2.la -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgconf-2 -lgthread-2.0 -pthread -lglib-2.0 -lutil /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -o test-dns-sd test-dns-sd.o ../libgnomevfs/libgnomevfs-2.la -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgconf-2 -lgthread-2.0 -pthread -lglib-2.0 -lutil mv -f .deps/test-shell.Tpo .deps/test-shell.Po libtool: link: gcc -g -O2 -o .libs/test-sync-write test-sync-write.o -pthread ../libgnomevfs/.libs/libgnomevfs-2.so -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib /gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib/libxml2.so -ldl -lz /gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib/liblzma.so -lm -lresolv /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib/libgconf-2.so /gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib/libdbus-glib-1.so -lgio-2.0 /gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/libdbus-1.so -lpthread /gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib/libORBit-2.so -lgmodule-2.0 -lgobject-2.0 -lgthread-2.0 -lglib-2.0 -lutil -pthread -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -o test-symlinks test-symlinks.o ../libgnomevfs/libgnomevfs-2.la -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgconf-2 -lgthread-2.0 -pthread -lglib-2.0 -lutil libtool: link: gcc -g -O2 -o .libs/test-unlink test-unlink.o -pthread ../libgnomevfs/.libs/libgnomevfs-2.so -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib /gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib/libxml2.so -ldl -lz /gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib/liblzma.so -lm -lresolv /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib/libgconf-2.so /gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib/libdbus-glib-1.so -lgio-2.0 /gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/libdbus-1.so -lpthread /gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib/libORBit-2.so -lgmodule-2.0 -lgobject-2.0 -lgthread-2.0 -lglib-2.0 -lutil -pthread -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -o test-parse-ls-lga test-parse-ls-lga.o ../libgnomevfs/libgnomevfs-2.la -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgconf-2 -lgthread-2.0 -pthread -lglib-2.0 -lutil /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -o test-shell test-shell.o ../libgnomevfs/libgnomevfs-2.la -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgconf-2 -lgthread-2.0 -pthread -lglib-2.0 -lutil libtool: link: gcc -g -O2 -o .libs/test-uri test-uri.o -pthread ../libgnomevfs/.libs/libgnomevfs-2.so -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib /gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib/libxml2.so -ldl -lz /gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib/liblzma.so -lm -lresolv /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib/libgconf-2.so /gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib/libdbus-glib-1.so -lgio-2.0 /gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/libdbus-1.so -lpthread /gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib/libORBit-2.so -lgmodule-2.0 -lgobject-2.0 -lgthread-2.0 -lglib-2.0 -lutil -pthread -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib libtool: link: gcc -g -O2 -o .libs/test-volumes test-volumes.o -pthread ../libgnomevfs/.libs/libgnomevfs-2.so -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib /gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib/libxml2.so -ldl -lz /gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib/liblzma.so -lm -lresolv /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib/libgconf-2.so /gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib/libdbus-glib-1.so -lgio-2.0 /gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/libdbus-1.so -lpthread /gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib/libORBit-2.so -lgmodule-2.0 -lgobject-2.0 -lgthread-2.0 -lglib-2.0 -lutil -pthread -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib libtool: link: gcc -g -O2 -o .libs/test-xfer test-xfer.o -pthread ../libgnomevfs/.libs/libgnomevfs-2.so -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib /gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib/libxml2.so -ldl -lz /gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib/liblzma.so -lm -lresolv /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib/libgconf-2.so /gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib/libdbus-glib-1.so -lgio-2.0 /gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/libdbus-1.so -lpthread /gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib/libORBit-2.so -lgmodule-2.0 -lgobject-2.0 -lgthread-2.0 -lglib-2.0 -lutil -pthread -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib libtool: link: gcc -g -O2 -o .libs/test-callback test-callback.o -pthread ../libgnomevfs/.libs/libgnomevfs-2.so -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib /gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib/libxml2.so -ldl -lz /gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib/liblzma.so -lm -lresolv /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib/libgconf-2.so /gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib/libdbus-glib-1.so -lgio-2.0 /gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/libdbus-1.so -lpthread /gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib/libORBit-2.so -lgmodule-2.0 -lgobject-2.0 -lgthread-2.0 -lglib-2.0 -lutil -pthread -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib libtool: link: gcc -g -O2 -o .libs/test-module-selftest test-module-selftest.o -pthread ../libgnomevfs/.libs/libgnomevfs-2.so -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib /gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib/libxml2.so -ldl -lz /gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib/liblzma.so -lm -lresolv /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib/libgconf-2.so /gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib/libdbus-glib-1.so -lgio-2.0 /gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/libdbus-1.so -lpthread /gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib/libORBit-2.so -lgmodule-2.0 -lgobject-2.0 -lgthread-2.0 -lglib-2.0 -lutil -pthread -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib libtool: link: gcc -g -O2 -o .libs/test-queue test-queue.o -pthread ../libgnomevfs/.libs/libgnomevfs-2.so -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib /gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib/libxml2.so -ldl -lz /gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib/liblzma.so -lm -lresolv /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib/libgconf-2.so /gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib/libdbus-glib-1.so -lgio-2.0 /gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/libdbus-1.so -lpthread /gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib/libORBit-2.so -lgmodule-2.0 -lgobject-2.0 -lgthread-2.0 -lglib-2.0 -lutil -pthread -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib libtool: link: gcc -g -O2 -o .libs/test-dns-sd test-dns-sd.o -pthread ../libgnomevfs/.libs/libgnomevfs-2.so -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib /gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib/libxml2.so -ldl -lz /gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib/liblzma.so -lm -lresolv /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib/libgconf-2.so /gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib/libdbus-glib-1.so -lgio-2.0 /gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/libdbus-1.so -lpthread /gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib/libORBit-2.so -lgmodule-2.0 -lgobject-2.0 -lgthread-2.0 -lglib-2.0 -lutil -pthread -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib libtool: link: gcc -g -O2 -o .libs/test-symlinks test-symlinks.o -pthread ../libgnomevfs/.libs/libgnomevfs-2.so -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib /gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib/libxml2.so -ldl -lz /gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib/liblzma.so -lm -lresolv /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib/libgconf-2.so /gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib/libdbus-glib-1.so -lgio-2.0 /gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/libdbus-1.so -lpthread /gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib/libORBit-2.so -lgmodule-2.0 -lgobject-2.0 -lgthread-2.0 -lglib-2.0 -lutil -pthread -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib libtool: link: gcc -g -O2 -o .libs/test-parse-ls-lga test-parse-ls-lga.o -pthread ../libgnomevfs/.libs/libgnomevfs-2.so -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib /gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib/libxml2.so -ldl -lz /gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib/liblzma.so -lm -lresolv /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib/libgconf-2.so /gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib/libdbus-glib-1.so -lgio-2.0 /gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/libdbus-1.so -lpthread /gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib/libORBit-2.so -lgmodule-2.0 -lgobject-2.0 -lgthread-2.0 -lglib-2.0 -lutil -pthread -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib libtool: link: gcc -g -O2 -o .libs/test-shell test-shell.o -pthread ../libgnomevfs/.libs/libgnomevfs-2.so -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib /gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib/libxml2.so -ldl -lz /gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib/liblzma.so -lm -lresolv /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib/libgconf-2.so /gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib/libdbus-glib-1.so -lgio-2.0 /gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib/libdbus-1.so -lpthread /gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib/libORBit-2.so -lgmodule-2.0 -lgobject-2.0 -lgthread-2.0 -lglib-2.0 -lutil -pthread -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib make[2]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/test' Making all in po make[2]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/po' file=`echo af | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file af.po file=`echo am | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file am.po file=`echo ar | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file ar.po file=`echo as | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file as.po file=`echo ast | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file ast.po file=`echo az | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file az.po file=`echo be | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file be.po file=`echo bg | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file bg.po file=`echo bn | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file bn.po file=`echo bn_IN | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file bn_IN.po file=`echo bs | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file bs.po file=`echo ca | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file ca.po file=`echo ca@valencia | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file ca@valencia.po file=`echo cs | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file cs.po file=`echo cy | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file cy.po file=`echo da | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file da.po file=`echo de | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file de.po file=`echo dz | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file dz.po file=`echo el | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file el.po file=`echo en_CA | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file en_CA.po file=`echo en_GB | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file en_GB.po file=`echo en@shaw | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file en@shaw.po file=`echo eo | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file eo.po file=`echo es | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file es.po file=`echo et | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file et.po file=`echo eu | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file eu.po file=`echo fa | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file fa.po file=`echo fi | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file fi.po file=`echo fr | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file fr.po file=`echo ga | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file ga.po file=`echo gl | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file gl.po file=`echo gu | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file gu.po file=`echo he | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file he.po file=`echo hi | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file hi.po file=`echo hr | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file hr.po file=`echo hu | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file hu.po file=`echo id | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file id.po file=`echo is | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file is.po file=`echo it | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file it.po file=`echo ja | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file ja.po file=`echo ka | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file ka.po file=`echo kn | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file kn.po file=`echo ko | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file ko.po file=`echo ku | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file ku.po file=`echo li | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file li.po file=`echo lt | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file lt.po file=`echo lv | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file lv.po file=`echo mai | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file mai.po file=`echo mg | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file mg.po file=`echo mk | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file mk.po file=`echo ml | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file ml.po file=`echo mn | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file mn.po file=`echo mr | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file mr.po file=`echo ms | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file ms.po file=`echo nb | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file nb.po file=`echo ne | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file ne.po file=`echo nl | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file nl.po file=`echo nn | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file nn.po file=`echo nso | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file nso.po file=`echo oc | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file oc.po file=`echo or | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file or.po file=`echo pa | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file pa.po file=`echo pl | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file pl.po file=`echo pt | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file pt.po file=`echo pt_BR | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file pt_BR.po file=`echo ro | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file ro.po file=`echo ru | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file ru.po file=`echo rw | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file rw.po file=`echo sk | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file sk.po file=`echo sl | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file sl.po file=`echo sq | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file sq.po file=`echo sr | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file sr.po file=`echo sr@latin | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file sr@latin.po file=`echo sr@ije | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file sr@ije.po file=`echo sv | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file sv.po file=`echo ta | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file ta.po file=`echo te | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file te.po file=`echo th | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file th.po file=`echo tr | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file tr.po file=`echo uk | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file uk.po file=`echo uz | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file uz.po file=`echo uz@cyrillic | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file uz@cyrillic.po file=`echo vi | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file vi.po file=`echo wa | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file wa.po file=`echo xh | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file xh.po file=`echo yi | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file yi.po file=`echo zh_CN | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file zh_CN.po file=`echo zh_HK | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file zh_HK.po file=`echo zh_TW | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file zh_TW.po file=`echo zu | sed 's,.*/,,'`.gmo \ && rm -f $file && /gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin/msgfmt -o $file zu.po make[2]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/po' make[2]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4' make[2]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4' make[1]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4' phase `build' succeeded after 15.2 seconds starting phase `check' Making check in imported make[1]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/imported' Making check in neon make[2]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/imported/neon' make[2]: Nothing to be done for 'check'. make[2]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/imported/neon' Making check in fnmatch make[2]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/imported/fnmatch' make[2]: Nothing to be done for 'check'. make[2]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/imported/fnmatch' make[2]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/imported' make[2]: Nothing to be done for 'check-am'. make[2]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/imported' make[1]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/imported' Making check in libgnomevfs make[1]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/libgnomevfs' make check-am make[2]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/libgnomevfs' make[2]: Nothing to be done for 'check-am'. make[2]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/libgnomevfs' make[1]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/libgnomevfs' Making check in modules make[1]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/modules' make[1]: Nothing to be done for 'check'. make[1]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/modules' Making check in daemon make[1]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/daemon' make[1]: Nothing to be done for 'check'. make[1]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/daemon' Making check in schemas make[1]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/schemas' make[1]: Nothing to be done for 'check'. make[1]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/schemas' Making check in devel-docs make[1]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/devel-docs' Making check in gnome-vfs-tutorial make[2]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/devel-docs/gnome-vfs-tutorial' make[2]: Nothing to be done for 'check'. make[2]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/devel-docs/gnome-vfs-tutorial' make[2]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/devel-docs' make[2]: Nothing to be done for 'check-am'. make[2]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/devel-docs' make[1]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/devel-docs' Making check in doc make[1]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/doc' make[1]: Nothing to be done for 'check'. make[1]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/doc' Making check in programs make[1]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/programs' make[1]: Nothing to be done for 'check'. make[1]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/programs' Making check in test make[1]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/test' make check-TESTS make[2]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/test' ACL auto test mode Testing ACE Object Testing ACL Object PASS: test-acl Testing GnomeVFSAddress PASS: test-address Testing get file info... Testing open, close... Testing read, close... Testing cancellation... Testing failed opens... Testing read, cancel, closes... Testing directory loads... Testing directory finds... Testing shutdown... All tests passed successfully. PASS: test-async-cancel PASS: test-escape GConf Error: Failed to contact configuration server; the most common cause is a missing or misconfigured D-Bus session bus daemon. See http://projects.gnome.org/gconf/ for information. (Details - 1: Not running within active session) PASS: test-uri Initializing gnome-vfs... Creating async context... Starting open for `./test.input'... Main loop running. Open failed: Invalid URI. Main loop finished. Test async queue efficiency ...Passed All done Test passed PASS: ./auto-test ================== All 6 tests passed ================== make[2]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/test' make[1]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/test' Making check in po make[1]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/po' INTLTOOL_EXTRACT=/gnu/store/jr3sfjid7nv7bqbddwir31a6chddmady-intltool-0.51.0/bin/intltool-extract srcdir=. /gnu/store/jr3sfjid7nv7bqbddwir31a6chddmady-intltool-0.51.0/bin/intltool-update --gettext-package gnome-vfs-2.0 --pot rm -f missing notexist srcdir=. /gnu/store/jr3sfjid7nv7bqbddwir31a6chddmady-intltool-0.51.0/bin/intltool-update -m if [ -r missing -o -r notexist ]; then \ exit 1; \ fi make[1]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/po' make[1]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4' make[1]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4' phase `check' succeeded after 2.0 seconds starting phase `install' Making install in imported make[1]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/imported' Making install in neon make[2]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/imported/neon' make[3]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/imported/neon' make[3]: Nothing to be done for 'install-exec-am'. make[3]: Nothing to be done for 'install-data-am'. make[3]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/imported/neon' make[2]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/imported/neon' Making install in fnmatch make[2]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/imported/fnmatch' make[3]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/imported/fnmatch' make[3]: Nothing to be done for 'install-exec-am'. make[3]: Nothing to be done for 'install-data-am'. make[3]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/imported/fnmatch' make[2]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/imported/fnmatch' make[2]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/imported' make[3]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/imported' make[3]: Nothing to be done for 'install-exec-am'. make[3]: Nothing to be done for 'install-data-am'. make[3]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/imported' make[2]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/imported' make[1]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/imported' Making install in libgnomevfs make[1]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/libgnomevfs' make install-am make[2]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/libgnomevfs' make[3]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/libgnomevfs' test -z "/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib" || /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/mkdir -p "/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib" /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --mode=install /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c libgnomevfs-2.la '/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib' libtool: install: /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c .libs/libgnomevfs-2.so.0.2400.4 /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/libgnomevfs-2.so.0.2400.4 libtool: install: (cd /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib && { ln -s -f libgnomevfs-2.so.0.2400.4 libgnomevfs-2.so.0 || { rm -f libgnomevfs-2.so.0 && ln -s libgnomevfs-2.so.0.2400.4 libgnomevfs-2.so.0; }; }) libtool: install: (cd /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib && { ln -s -f libgnomevfs-2.so.0.2400.4 libgnomevfs-2.so || { rm -f libgnomevfs-2.so && ln -s libgnomevfs-2.so.0.2400.4 libgnomevfs-2.so; }; }) libtool: install: /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c .libs/libgnomevfs-2.lai /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/libgnomevfs-2.la libtool: install: /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c .libs/libgnomevfs-2.a /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/libgnomevfs-2.a libtool: install: chmod 644 /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/libgnomevfs-2.a libtool: install: ranlib /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/libgnomevfs-2.a libtool: finish: PATH="/gnu/store/7sa6phqdsirzj29n59mrzjr363a837b8-glib-2.70.2-bin/bin:/gnu/store/jr3sfjid7nv7bqbddwir31a6chddmady-intltool-0.51.0/bin:/gnu/store/3nw1jhybwdbbsx8v821bm71h205462wz-pkg-config-0.29.2/bin:/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/bin:/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/bin:/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/bin:/gnu/store/99c25918hl9pihix8hparmc96q6zrpwy-tar-1.34/bin:/gnu/store/l0yga4lrwwf74rz7fb0dadglg27ajpsx-gzip-1.10/bin:/gnu/store/ihakfb51zdgjz3v9nkj0ja9zk9ng8xzl-bzip2-1.0.8/bin:/gnu/store/fk24dx8qz1b5smnc4ljfw25xn7yjps0q-xz-5.2.5/bin:/gnu/store/vl1b3nq6gijpzbl03zq92m5dwgs17nik-file-5.39/bin:/gnu/store/h0rx6y95zin61fp5wlyjly4g9j2hma18-diffutils-3.8/bin:/gnu/store/7j8j7m0kgb7kv2fc18qvrdj7gs3jc4mx-patch-2.7.6/bin:/gnu/store/x4yglk9pn2s2ixl1b4lj151bd2yvlgww-findutils-4.8.0/bin:/gnu/store/vzq0il5z2d6ksllb525m9xaqzv829g3k-gawk-5.1.0/bin:/gnu/store/cnwr7widbi6470kfyb13krx46kz5anmy-sed-4.8/bin:/gnu/store/bx47clwnxn51m7jdwfimz4lw2fh8g21v-grep-3.6/bin:/gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin:/gnu/store/dhx00nrv9r52f6xivg0xa4iihpl9awyk-make-4.3/bin:/gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin:/gnu/store/4bzvr16pyax9224v9r72rqxswj9931sb-ld-wrapper-0/bin:/gnu/store/v4a7zw8w52v64kw5781ypa8gjwd098jz-binutils-2.37/bin:/gnu/store/v5xfd4vy1lvqikdl1rzs8aklgsnqwd26-gcc-10.3.0/bin:/gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/bin:/gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/sbin:/gnu/store/zn45z8pv5dkh98hi9l1q9aldbplga3m7-perl-5.34.0/bin:/gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin:/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/bin:/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/bin:/sbin" ldconfig -n /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib ---------------------------------------------------------------------- Libraries have been installed in: /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib If you ever happen to want to link against installed libraries in a given directory, LIBDIR, you must either use libtool, and specify the full pathname of the library, or use the `-LLIBDIR' flag during linking and do at least one of the following: - add LIBDIR to the `LD_LIBRARY_PATH' environment variable during execution - add LIBDIR to the `LD_RUN_PATH' environment variable during linking - use the `-Wl,-rpath -Wl,LIBDIR' linker flag See any operating system documentation about shared libraries for more information, such as the ld(1) and ld.so(8) manual pages. ---------------------------------------------------------------------- test -z "/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/include/gnome-vfs-2.0/libgnomevfs" || /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/mkdir -p "/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/include/gnome-vfs-2.0/libgnomevfs" /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c -m 644 gnome-vfs-ace.h gnome-vfs-acl.h gnome-vfs-application-registry.h gnome-vfs-address.h gnome-vfs-async-ops.h gnome-vfs-cancellation.h gnome-vfs-context.h gnome-vfs-directory.h gnome-vfs-dns-sd.h gnome-vfs-drive.h gnome-vfs-enum-types.h gnome-vfs-file-info.h gnome-vfs-file-size.h gnome-vfs-find-directory.h gnome-vfs-handle.h gnome-vfs-init.h gnome-vfs-job-limit.h gnome-vfs-mime.h gnome-vfs-mime-deprecated.h gnome-vfs-mime-handlers.h gnome-vfs-mime-info-cache.h gnome-vfs-mime-monitor.h gnome-vfs-mime-utils.h gnome-vfs-module-callback.h gnome-vfs-monitor.h gnome-vfs-ops.h gnome-vfs-resolve.h gnome-vfs-result.h gnome-vfs-standard-callbacks.h gnome-vfs-types.h gnome-vfs-uri.h gnome-vfs-utils.h gnome-vfs-version.h gnome-vfs-volume-monitor.h gnome-vfs-volume.h gnome-vfs-xfer.h gnome-vfs.h '/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/include/gnome-vfs-2.0/libgnomevfs' test -z "/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/include/gnome-vfs-module-2.0/libgnomevfs" || /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/mkdir -p "/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/include/gnome-vfs-module-2.0/libgnomevfs" /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c -m 644 gnome-vfs-cancellable-ops.h gnome-vfs-inet-connection.h gnome-vfs-method.h gnome-vfs-mime-info.h gnome-vfs-module-callback-module-api.h gnome-vfs-module-shared.h gnome-vfs-module.h gnome-vfs-parse-ls.h gnome-vfs-ssl.h gnome-vfs-transform.h gnome-vfs-socket-buffer.h gnome-vfs-socket.h gnome-vfs-pty.h '/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/include/gnome-vfs-module-2.0/libgnomevfs' test -z "/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/include" || /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/mkdir -p "/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/include" /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c -m 644 gnome-vfs-file-size.h '/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/include' make[3]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/libgnomevfs' make[2]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/libgnomevfs' make[1]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/libgnomevfs' Making install in modules make[1]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/modules' make[2]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/modules' make[2]: Nothing to be done for 'install-exec-am'. test -z "/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules" || /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/mkdir -p "/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules" /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --mode=install /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c libfile.la libvfs-test.la libbzip2.la libgzip.la libtar.la libcomputer.la libdns-sd.la libnetwork.la libnntp.la libsftp.la libhttp.la libftp.la '/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules' libtool: install: warning: relinking `libfile.la' libtool: install: (cd /tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/modules; /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash /tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/libtool --tag CC --mode=relink gcc -g -O2 -export_dynamic -avoid-version -module -no-undefined -o libfile.la -rpath /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules file-method.lo fstype.lo file-method-acl.lo inotify-kernel.lo inotify-missing.lo inotify-path.lo inotify-sub.lo inotify-helper.lo inotify-diag.lo -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgmodule-2.0 -pthread -lgthread-2.0 -pthread -lgobject-2.0 -lgconf-2 -lglib-2.0 ../libgnomevfs/libgnomevfs-2.la -lutil ) libtool: relink: gcc -shared .libs/file-method.o .libs/fstype.o .libs/file-method-acl.o .libs/inotify-kernel.o .libs/inotify-missing.o .libs/inotify-path.o .libs/inotify-sub.o .libs/inotify-helper.o .libs/inotify-diag.o -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib -L/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -lgnomevfs-2 -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -lgconf-2 -lORBit-2 -lgmodule-2.0 -lgthread-2.0 -lxml2 -ldl -lz -llzma -lm -ldbus-glib-1 -lgio-2.0 -ldbus-1 -lpthread -lgobject-2.0 -lglib-2.0 -lresolv -lutil -pthread -pthread -pthread -Wl,-soname -Wl,libfile.so -o .libs/libfile.so libtool: install: /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c .libs/libfile.soT /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules/libfile.so libtool: install: /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c .libs/libfile.lai /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules/libfile.la libtool: install: warning: relinking `libvfs-test.la' libtool: install: (cd /tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/modules; /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash /tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/libtool --tag CC --mode=relink gcc -g -O2 -export_dynamic -avoid-version -module -no-undefined -o libvfs-test.la -rpath /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules test-method.lo -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgmodule-2.0 -pthread -lgthread-2.0 -pthread -lglib-2.0 -lxml2 ../libgnomevfs/libgnomevfs-2.la -lutil ) libtool: relink: gcc -shared .libs/test-method.o -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -lgnomevfs-2 -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib -L/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -lgconf-2 -lORBit-2 -lgmodule-2.0 -lgthread-2.0 -lxml2 -ldl -lz -llzma -lm -ldbus-glib-1 -lgio-2.0 -ldbus-1 -lpthread -lgobject-2.0 -lglib-2.0 -lresolv -lutil -pthread -pthread -pthread -Wl,-soname -Wl,libvfs-test.so -o .libs/libvfs-test.so libtool: install: /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c .libs/libvfs-test.soT /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules/libvfs-test.so libtool: install: /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c .libs/libvfs-test.lai /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules/libvfs-test.la libtool: install: warning: relinking `libbzip2.la' libtool: install: (cd /tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/modules; /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash /tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/libtool --tag CC --mode=relink gcc -g -O2 -export_dynamic -avoid-version -module -no-undefined -o libbzip2.la -rpath /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules bzip2-method.lo -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgmodule-2.0 -pthread -lgthread-2.0 -pthread -lgobject-2.0 -lglib-2.0 -lbz2 ../libgnomevfs/libgnomevfs-2.la -lutil ) libtool: relink: gcc -shared .libs/bzip2-method.o -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lbz2 -L/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -lgnomevfs-2 -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib -L/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -lgconf-2 -lORBit-2 -lgmodule-2.0 -lgthread-2.0 -lxml2 -ldl -lz -llzma -lm -ldbus-glib-1 -lgio-2.0 -ldbus-1 -lpthread -lgobject-2.0 -lglib-2.0 -lresolv -lutil -pthread -pthread -pthread -Wl,-soname -Wl,libbzip2.so -o .libs/libbzip2.so libtool: install: /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c .libs/libbzip2.soT /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules/libbzip2.so libtool: install: /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c .libs/libbzip2.lai /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules/libbzip2.la libtool: install: warning: relinking `libgzip.la' libtool: install: (cd /tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/modules; /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash /tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/libtool --tag CC --mode=relink gcc -g -O2 -export_dynamic -avoid-version -module -no-undefined -o libgzip.la -rpath /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules gzip-method.lo -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgmodule-2.0 -pthread -lgthread-2.0 -pthread -lgobject-2.0 -lglib-2.0 -lz ../libgnomevfs/libgnomevfs-2.la -lutil ) libtool: relink: gcc -shared .libs/gzip-method.o -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -lgnomevfs-2 -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib -L/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -lgconf-2 -lORBit-2 -lgmodule-2.0 -lgthread-2.0 -lxml2 -ldl -lz -llzma -lm -ldbus-glib-1 -lgio-2.0 -ldbus-1 -lpthread -lgobject-2.0 -lglib-2.0 -lresolv -lutil -pthread -pthread -pthread -Wl,-soname -Wl,libgzip.so -o .libs/libgzip.so libtool: install: /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c .libs/libgzip.soT /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules/libgzip.so libtool: install: /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c .libs/libgzip.lai /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules/libgzip.la libtool: install: warning: relinking `libtar.la' libtool: install: (cd /tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/modules; /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash /tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/libtool --tag CC --mode=relink gcc -g -O2 -export_dynamic -avoid-version -module -no-undefined -o libtar.la -rpath /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules tar-method.lo -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgmodule-2.0 -pthread -lgthread-2.0 -pthread -lgobject-2.0 -lglib-2.0 ../libgnomevfs/libgnomevfs-2.la -lutil ) libtool: relink: gcc -shared .libs/tar-method.o -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -lgnomevfs-2 -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib -L/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -lgconf-2 -lORBit-2 -lgmodule-2.0 -lgthread-2.0 -lxml2 -ldl -lz -llzma -lm -ldbus-glib-1 -lgio-2.0 -ldbus-1 -lpthread -lgobject-2.0 -lglib-2.0 -lresolv -lutil -pthread -pthread -pthread -Wl,-soname -Wl,libtar.so -o .libs/libtar.so libtool: install: /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c .libs/libtar.soT /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules/libtar.so libtool: install: /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c .libs/libtar.lai /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules/libtar.la libtool: install: warning: relinking `libcomputer.la' libtool: install: (cd /tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/modules; /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash /tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/libtool --tag CC --mode=relink gcc -g -O2 -export_dynamic -avoid-version -module -no-undefined -o libcomputer.la -rpath /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules computer-method.lo -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgmodule-2.0 -pthread -lgthread-2.0 -pthread -lgobject-2.0 -lgconf-2 -lglib-2.0 ../libgnomevfs/libgnomevfs-2.la -lutil ) libtool: relink: gcc -shared .libs/computer-method.o -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib -L/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -lgnomevfs-2 -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -lgconf-2 -lORBit-2 -lgmodule-2.0 -lgthread-2.0 -lxml2 -ldl -lz -llzma -lm -ldbus-glib-1 -lgio-2.0 -ldbus-1 -lpthread -lgobject-2.0 -lglib-2.0 -lresolv -lutil -pthread -pthread -pthread -Wl,-soname -Wl,libcomputer.so -o .libs/libcomputer.so libtool: install: /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c .libs/libcomputer.soT /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules/libcomputer.so libtool: install: /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c .libs/libcomputer.lai /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules/libcomputer.la libtool: install: warning: relinking `libdns-sd.la' libtool: install: (cd /tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/modules; /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash /tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/libtool --tag CC --mode=relink gcc -g -O2 -export_dynamic -avoid-version -module -no-undefined -o libdns-sd.la -rpath /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules dns-sd-method.lo -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgmodule-2.0 -pthread -lgthread-2.0 -pthread -lgobject-2.0 -lglib-2.0 ../libgnomevfs/libgnomevfs-2.la -lutil ) libtool: relink: gcc -shared .libs/dns-sd-method.o -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -lgnomevfs-2 -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib -L/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -lgconf-2 -lORBit-2 -lgmodule-2.0 -lgthread-2.0 -lxml2 -ldl -lz -llzma -lm -ldbus-glib-1 -lgio-2.0 -ldbus-1 -lpthread -lgobject-2.0 -lglib-2.0 -lresolv -lutil -pthread -pthread -pthread -Wl,-soname -Wl,libdns-sd.so -o .libs/libdns-sd.so libtool: install: /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c .libs/libdns-sd.soT /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules/libdns-sd.so libtool: install: /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c .libs/libdns-sd.lai /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules/libdns-sd.la libtool: install: warning: relinking `libnetwork.la' libtool: install: (cd /tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/modules; /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash /tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/libtool --tag CC --mode=relink gcc -g -O2 -export_dynamic -avoid-version -module -no-undefined -o libnetwork.la -rpath /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules network-method.lo -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgmodule-2.0 -pthread -lgthread-2.0 -pthread -lgobject-2.0 -lgconf-2 -lglib-2.0 ../libgnomevfs/libgnomevfs-2.la -lutil ) libtool: relink: gcc -shared .libs/network-method.o -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib -L/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -lgnomevfs-2 -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -lgconf-2 -lORBit-2 -lgmodule-2.0 -lgthread-2.0 -lxml2 -ldl -lz -llzma -lm -ldbus-glib-1 -lgio-2.0 -ldbus-1 -lpthread -lgobject-2.0 -lglib-2.0 -lresolv -lutil -pthread -pthread -pthread -Wl,-soname -Wl,libnetwork.so -o .libs/libnetwork.so libtool: install: /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c .libs/libnetwork.soT /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules/libnetwork.so libtool: install: /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c .libs/libnetwork.lai /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules/libnetwork.la libtool: install: warning: relinking `libnntp.la' libtool: install: (cd /tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/modules; /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash /tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/libtool --tag CC --mode=relink gcc -g -O2 -export_dynamic -avoid-version -module -no-undefined -o libnntp.la -rpath /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules nntp-method.lo -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgmodule-2.0 -pthread -lgthread-2.0 -pthread -lgobject-2.0 -lglib-2.0 ../libgnomevfs/libgnomevfs-2.la -lutil ) libtool: relink: gcc -shared .libs/nntp-method.o -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -lgnomevfs-2 -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib -L/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -lgconf-2 -lORBit-2 -lgmodule-2.0 -lgthread-2.0 -lxml2 -ldl -lz -llzma -lm -ldbus-glib-1 -lgio-2.0 -ldbus-1 -lpthread -lgobject-2.0 -lglib-2.0 -lresolv -lutil -pthread -pthread -pthread -Wl,-soname -Wl,libnntp.so -o .libs/libnntp.so libtool: install: /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c .libs/libnntp.soT /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules/libnntp.so libtool: install: /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c .libs/libnntp.lai /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules/libnntp.la libtool: install: warning: relinking `libsftp.la' libtool: install: (cd /tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/modules; /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash /tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/libtool --tag CC --mode=relink gcc -g -O2 -export_dynamic -avoid-version -module -no-undefined -o libsftp.la -rpath /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules sftp-method.lo -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgmodule-2.0 -pthread -lgthread-2.0 -pthread -lgobject-2.0 -lglib-2.0 ../libgnomevfs/libgnomevfs-2.la -lutil ) libtool: relink: gcc -shared .libs/sftp-method.o -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -lgnomevfs-2 -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib -L/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -lgconf-2 -lORBit-2 -lgmodule-2.0 -lgthread-2.0 -lxml2 -ldl -lz -llzma -lm -ldbus-glib-1 -lgio-2.0 -ldbus-1 -lpthread -lgobject-2.0 -lglib-2.0 -lresolv -lutil -pthread -pthread -pthread -Wl,-soname -Wl,libsftp.so -o .libs/libsftp.so libtool: install: /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c .libs/libsftp.soT /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules/libsftp.so libtool: install: /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c .libs/libsftp.lai /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules/libsftp.la libtool: install: warning: relinking `libhttp.la' libtool: install: (cd /tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/modules; /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash /tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/libtool --tag CC --mode=relink gcc -g -O2 -export_dynamic -avoid-version -module -no-undefined -o libhttp.la -rpath /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules http-neon-method.lo http-proxy.lo -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgmodule-2.0 -pthread -lgthread-2.0 -pthread -lgobject-2.0 -lgconf-2 -lglib-2.0 ../imported/neon/libneon.la ../libgnomevfs/libgnomevfs-2.la -lutil ) libtool: relink: gcc -shared .libs/http-neon-method.o .libs/http-proxy.o -Wl,--whole-archive ../imported/neon/.libs/libneon.a -Wl,--no-whole-archive -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -lgnomevfs-2 -L/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -lgconf-2 -lORBit-2 -lgmodule-2.0 -lgthread-2.0 -lxml2 -ldl -lz -llzma -lm -ldbus-glib-1 -lgio-2.0 -ldbus-1 -lpthread -lgobject-2.0 -lglib-2.0 -lresolv -lutil -pthread -pthread -pthread -Wl,-soname -Wl,libhttp.so -o .libs/libhttp.so libtool: install: /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c .libs/libhttp.soT /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules/libhttp.so libtool: install: /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c .libs/libhttp.lai /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules/libhttp.la libtool: install: warning: relinking `libftp.la' libtool: install: (cd /tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/modules; /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash /tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/libtool --tag CC --mode=relink gcc -g -O2 -export_dynamic -avoid-version -module -no-undefined -o libftp.la -rpath /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules ftp-method.lo -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -lgmodule-2.0 -pthread -lgthread-2.0 -pthread -lgobject-2.0 -lgconf-2 -lglib-2.0 ../libgnomevfs/libgnomevfs-2.la -lutil ) libtool: relink: gcc -shared .libs/ftp-method.o -Wl,-rpath -Wl,/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -Wl,-rpath -Wl,/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -Wl,-rpath -Wl,/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib -Wl,-rpath -Wl,/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -Wl,-rpath -Wl,/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -Wl,-rpath -Wl,/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -Wl,-rpath -Wl,/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/lib -L/gnu/store/4870ak812g1sbldw1bd7hwk3ldn39w80-glib-2.70.2/lib -L/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/lib -L/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/lib -L/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/lib -L/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib -lgnomevfs-2 -L/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/lib -L/gnu/store/anx9g8l0j8h57cg40vrp88disb5c69jd-xz-5.2.5/lib -lgconf-2 -lORBit-2 -lgmodule-2.0 -lgthread-2.0 -lxml2 -ldl -lz -llzma -lm -ldbus-glib-1 -lgio-2.0 -ldbus-1 -lpthread -lgobject-2.0 -lglib-2.0 -lresolv -lutil -pthread -pthread -pthread -Wl,-soname -Wl,libftp.so -o .libs/libftp.so libtool: install: /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c .libs/libftp.soT /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules/libftp.so libtool: install: /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c .libs/libftp.lai /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules/libftp.la libtool: install: /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c .libs/libfile.a /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules/libfile.a libtool: install: chmod 644 /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules/libfile.a libtool: install: ranlib /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules/libfile.a libtool: install: /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c .libs/libvfs-test.a /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules/libvfs-test.a libtool: install: chmod 644 /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules/libvfs-test.a libtool: install: ranlib /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules/libvfs-test.a libtool: install: /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c .libs/libbzip2.a /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules/libbzip2.a libtool: install: chmod 644 /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules/libbzip2.a libtool: install: ranlib /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules/libbzip2.a libtool: install: /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c .libs/libgzip.a /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules/libgzip.a libtool: install: chmod 644 /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules/libgzip.a libtool: install: ranlib /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules/libgzip.a libtool: install: /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c .libs/libtar.a /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules/libtar.a libtool: install: chmod 644 /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules/libtar.a libtool: install: ranlib /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules/libtar.a libtool: install: /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c .libs/libcomputer.a /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules/libcomputer.a libtool: install: chmod 644 /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules/libcomputer.a libtool: install: ranlib /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules/libcomputer.a libtool: install: /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c .libs/libdns-sd.a /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules/libdns-sd.a libtool: install: chmod 644 /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules/libdns-sd.a libtool: install: ranlib /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules/libdns-sd.a libtool: install: /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c .libs/libnetwork.a /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules/libnetwork.a libtool: install: chmod 644 /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules/libnetwork.a libtool: install: ranlib /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules/libnetwork.a libtool: install: /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c .libs/libnntp.a /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules/libnntp.a libtool: install: chmod 644 /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules/libnntp.a libtool: install: ranlib /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules/libnntp.a libtool: install: /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c .libs/libsftp.a /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules/libsftp.a libtool: install: chmod 644 /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules/libsftp.a libtool: install: ranlib /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules/libsftp.a libtool: install: /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c .libs/libhttp.a /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules/libhttp.a libtool: install: chmod 644 /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules/libhttp.a libtool: install: ranlib /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules/libhttp.a libtool: install: /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c .libs/libftp.a /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules/libftp.a libtool: install: chmod 644 /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules/libftp.a libtool: install: ranlib /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules/libftp.a libtool: finish: PATH="/gnu/store/7sa6phqdsirzj29n59mrzjr363a837b8-glib-2.70.2-bin/bin:/gnu/store/jr3sfjid7nv7bqbddwir31a6chddmady-intltool-0.51.0/bin:/gnu/store/3nw1jhybwdbbsx8v821bm71h205462wz-pkg-config-0.29.2/bin:/gnu/store/1id02vdkwlpdgzscyvzb3fh4l6pd6qlx-libxml2-2.9.12/bin:/gnu/store/qld73h44kgdfrfmfwjl7zxaibb04iwvl-dbus-glib-0.110/bin:/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/bin:/gnu/store/99c25918hl9pihix8hparmc96q6zrpwy-tar-1.34/bin:/gnu/store/l0yga4lrwwf74rz7fb0dadglg27ajpsx-gzip-1.10/bin:/gnu/store/ihakfb51zdgjz3v9nkj0ja9zk9ng8xzl-bzip2-1.0.8/bin:/gnu/store/fk24dx8qz1b5smnc4ljfw25xn7yjps0q-xz-5.2.5/bin:/gnu/store/vl1b3nq6gijpzbl03zq92m5dwgs17nik-file-5.39/bin:/gnu/store/h0rx6y95zin61fp5wlyjly4g9j2hma18-diffutils-3.8/bin:/gnu/store/7j8j7m0kgb7kv2fc18qvrdj7gs3jc4mx-patch-2.7.6/bin:/gnu/store/x4yglk9pn2s2ixl1b4lj151bd2yvlgww-findutils-4.8.0/bin:/gnu/store/vzq0il5z2d6ksllb525m9xaqzv829g3k-gawk-5.1.0/bin:/gnu/store/cnwr7widbi6470kfyb13krx46kz5anmy-sed-4.8/bin:/gnu/store/bx47clwnxn51m7jdwfimz4lw2fh8g21v-grep-3.6/bin:/gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin:/gnu/store/dhx00nrv9r52f6xivg0xa4iihpl9awyk-make-4.3/bin:/gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin:/gnu/store/4bzvr16pyax9224v9r72rqxswj9931sb-ld-wrapper-0/bin:/gnu/store/v4a7zw8w52v64kw5781ypa8gjwd098jz-binutils-2.37/bin:/gnu/store/v5xfd4vy1lvqikdl1rzs8aklgsnqwd26-gcc-10.3.0/bin:/gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/bin:/gnu/store/0iapawfss4xnxls622g23qpk4mwb9ihp-glibc-2.33/sbin:/gnu/store/zn45z8pv5dkh98hi9l1q9aldbplga3m7-perl-5.34.0/bin:/gnu/store/z5bhg65fw1h5nci5i9ikipsb225ayfga-gettext-minimal-0.21/bin:/gnu/store/nzha9x6p3hf7cd1nkn32mqs9x2zqqhfp-dbus-1.12.20/bin:/gnu/store/qjhc9l4717bzifbi74hgdrix38q7bam8-orbit2-2.14.19/bin:/sbin" ldconfig -n /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules ---------------------------------------------------------------------- Libraries have been installed in: /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/gnome-vfs-2.0/modules If you ever happen to want to link against installed libraries in a given directory, LIBDIR, you must either use libtool, and specify the full pathname of the library, or use the `-LLIBDIR' flag during linking and do at least one of the following: - add LIBDIR to the `LD_LIBRARY_PATH' environment variable during execution - add LIBDIR to the `LD_RUN_PATH' environment variable during linking - use the `-Wl,-rpath -Wl,LIBDIR' linker flag See any operating system documentation about shared libraries for more information, such as the ld(1) and ld.so(8) manual pages. ---------------------------------------------------------------------- test -z "/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc/gnome-vfs-2.0/modules" || /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/mkdir -p "/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc/gnome-vfs-2.0/modules" /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c -m 644 default-modules.conf '/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc/gnome-vfs-2.0/modules' make[2]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/modules' make[1]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/modules' Making install in daemon make[1]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/daemon' make[2]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/daemon' test -z "/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/libexec" || /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/mkdir -p "/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/libexec" /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --mode=install /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c gnome-vfs-daemon '/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/libexec' libtool: install: /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c .libs/gnome-vfs-daemon /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/libexec/gnome-vfs-daemon test -z "/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/dbus-1/services" || /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/mkdir -p "/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/dbus-1/services" /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c -m 644 gnome-vfs-daemon.service '/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/dbus-1/services' make[2]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/daemon' make[1]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/daemon' Making install in schemas make[1]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/schemas' make[2]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/schemas' make[2]: Nothing to be done for 'install-exec-am'. if test -z "" ; then \ for p in system_http_proxy.schemas system_smb.schemas system_dns_sd.schemas desktop_default_applications.schemas desktop_gnome_url_handlers.schemas ; do \ GCONF_CONFIG_SOURCE=xml:merged:/gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/etc/gconf/gconf.xml.defaults /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/bin/gconftool-2 --makefile-install-rule $p; \ done \ fi Attached schema `/schemas/system/http_proxy/use_http_proxy' to key `/system/http_proxy/use_http_proxy' WARNING: failed to install schema `/schemas/system/http_proxy/use_http_proxy', locale `mk': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `zu': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `be': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `ca@valencia': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `nb': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `ml': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `lv': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `sv': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `cs': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `nn': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `pt_BR': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `ta': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `sk': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `ru': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `uz': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `C': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `xh': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `he': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `bg': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `el': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `en@shaw': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `sl': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `bs': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `mn': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `mai': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `af': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `ar': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `hr': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `or': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `ne': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `it': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `pt': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `en_CA': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `as': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `da': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `ka': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `sr@latin': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `zh_CN': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `eo': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `te': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `zh_HK': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `hi': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `kn': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `ca': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `ja': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `nso': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `hu': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `fr': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `mr': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `tr': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `dz': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `ko': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `ro': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `mg': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `pl': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `sq': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `cy': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `pa': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `gu': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `th': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `de': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `sr': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `vi': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `ast': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `fi': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `es': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `bn': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `zh_TW': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `uk': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `en_GB': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `uz@cyrillic': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `et': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `lt': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `gl': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `bn_IN': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `nl': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `id': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `sr@ije': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `eu': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_http_proxy', locale `az': Unable to store a value at key '/schemas/system/http_proxy/use_http_proxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host' to key `/system/http_proxy/host' WARNING: failed to install schema `/schemas/system/http_proxy/host', locale `mk': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `zu': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `be': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `ca@valencia': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `nb': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `ml': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `lv': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `sv': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `cs': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `nn': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `pt_BR': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `ta': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `sk': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `ru': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `uz': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `C': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `xh': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `he': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `bg': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `el': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `en@shaw': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `sl': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `bs': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `mn': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `mai': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `af': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `ar': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `hr': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `or': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `ne': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `it': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `pt': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `en_CA': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `as': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `da': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `ka': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `sr@latin': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `zh_CN': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `te': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `zh_HK': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `hi': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `kn': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `ca': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `ja': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `nso': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `hu': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `fr': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `mr': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `tr': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `dz': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `ko': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `ro': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `mg': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `pl': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `sq': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `cy': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `pa': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `gu': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `th': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `de': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `sr': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `vi': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `ast': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `fi': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `es': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `bn': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `zh_TW': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `uk': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `en_GB': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `uz@cyrillic': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `et': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `lt': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `gl': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `bn_IN': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `nl': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `id': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `sr@ije': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `eu': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/host', locale `az': Unable to store a value at key '/schemas/system/http_proxy/host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port' to key `/system/http_proxy/port' WARNING: failed to install schema `/schemas/system/http_proxy/port', locale `mk': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `zu': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `be': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `ca@valencia': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `nb': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `ml': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `lv': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `sv': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `cs': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `nn': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `pt_BR': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `ta': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `sk': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `ru': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `uz': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `C': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `xh': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `he': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `bg': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `el': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `en@shaw': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `sl': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `bs': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `mn': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `mai': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `af': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `ar': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `hr': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `or': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `ne': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `it': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `pt': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `en_CA': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `as': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `da': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `ka': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `sr@latin': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `zh_CN': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `eo': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `te': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `zh_HK': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `hi': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `kn': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `ca': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `ja': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `nso': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `hu': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `fr': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `mr': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `tr': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `dz': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `ko': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `ro': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `mg': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `pl': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `sq': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `cy': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `pa': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `gu': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `th': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `de': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `sr': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `vi': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `ast': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `fi': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `es': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `bn': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `zh_TW': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `uk': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `en_GB': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `uz@cyrillic': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `et': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `lt': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `gl': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `bn_IN': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `nl': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `id': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `sr@ije': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `eu': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/port', locale `az': Unable to store a value at key '/schemas/system/http_proxy/port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication' to key `/system/http_proxy/use_authentication' WARNING: failed to install schema `/schemas/system/http_proxy/use_authentication', locale `mk': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `zu': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `be': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `ca@valencia': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `nb': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `ml': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `lv': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `sv': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `cs': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `nn': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `pt_BR': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `ta': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `sk': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `ru': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `C': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `xh': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `he': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `bg': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `el': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `en@shaw': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `sl': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `bs': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `mn': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `mai': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `af': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `ar': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `hr': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `or': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `ne': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `it': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `pt': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `en_CA': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `as': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `da': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `ka': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `sr@latin': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `zh_CN': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `te': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `zh_HK': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `hi': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `kn': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `ca': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `ja': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `nso': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `hu': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `fr': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `mr': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `tr': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `dz': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `ko': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `ro': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `mg': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `pl': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `sq': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `cy': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `pa': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `gu': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `th': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `de': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `sr': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `vi': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `ast': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `fi': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `es': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `bn': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `zh_TW': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `uk': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `en_GB': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `et': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `lt': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `gl': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `bn_IN': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `nl': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `id': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `sr@ije': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `eu': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/use_authentication', locale `az': Unable to store a value at key '/schemas/system/http_proxy/use_authentication', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user' to key `/system/http_proxy/authentication_user' WARNING: failed to install schema `/schemas/system/http_proxy/authentication_user', locale `mk': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `zu': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `be': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `ca@valencia': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `nb': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `ml': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `lv': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `sv': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `cs': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `nn': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `pt_BR': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `ta': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `sk': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `ru': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `uz': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `C': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `xh': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `he': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `bg': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `el': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `en@shaw': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `sl': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `bs': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `mn': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `mai': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `af': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `ar': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `hr': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `or': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `ne': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `it': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `pt': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `en_CA': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `as': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `da': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `ka': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `sr@latin': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `zh_CN': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `eo': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `te': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `zh_HK': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `hi': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `kn': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `ca': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `ja': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `nso': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `hu': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `fr': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `mr': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `tr': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `dz': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `ko': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `ro': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `mg': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `pl': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `sq': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `cy': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `pa': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `gu': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `th': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `de': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `sr': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `vi': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `ast': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `fi': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `es': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `bn': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `zh_TW': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `uk': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `en_GB': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `uz@cyrillic': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `et': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `lt': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `gl': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `bn_IN': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `nl': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `id': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `sr@ije': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `eu': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_user', locale `az': Unable to store a value at key '/schemas/system/http_proxy/authentication_user', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password' to key `/system/http_proxy/authentication_password' WARNING: failed to install schema `/schemas/system/http_proxy/authentication_password', locale `mk': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `zu': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `be': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `ca@valencia': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `nb': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `ml': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `lv': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `sv': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `cs': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `nn': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `pt_BR': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `ta': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `sk': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `ru': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `uz': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `C': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `xh': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `he': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `bg': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `el': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `en@shaw': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `sl': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `bs': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `mn': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `mai': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `af': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `ar': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `hr': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `or': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `ne': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `it': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `pt': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `en_CA': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `as': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `da': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `ka': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `sr@latin': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `zh_CN': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `eo': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `te': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `zh_HK': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `hi': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `kn': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `ca': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `ja': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `nso': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `hu': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `fr': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `mr': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `tr': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `dz': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `ko': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `ro': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `mg': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `pl': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `sq': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `cy': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `pa': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `gu': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `th': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `de': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `sr': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `vi': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `ast': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `fi': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `es': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `bn': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `zh_TW': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `uk': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `en_GB': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `uz@cyrillic': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `et': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `lt': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `gl': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `bn_IN': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `nl': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `id': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `sr@ije': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `eu': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/authentication_password', locale `az': Unable to store a value at key '/schemas/system/http_proxy/authentication_password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts' to key `/system/http_proxy/ignore_hosts' WARNING: failed to install schema `/schemas/system/http_proxy/ignore_hosts', locale `mk': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `zu': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `be': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `ca@valencia': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `nb': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `ml': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `lv': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `sv': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `cs': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `nn': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `pt_BR': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `ta': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `sk': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `ru': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `C': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `xh': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `he': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `bg': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `el': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `en@shaw': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `sl': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `bs': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `mn': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `mai': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `af': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `ar': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `hr': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `or': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `ne': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `it': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `pt': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `en_CA': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `as': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `da': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `ka': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `sr@latin': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `zh_CN': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `te': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `zh_HK': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `hi': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `kn': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `ca': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `ja': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `nso': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `hu': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `fr': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `mr': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `tr': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `dz': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `ko': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `ro': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `mg': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `pl': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `sq': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `cy': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `pa': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `gu': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `th': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `de': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `sr': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `vi': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `ast': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `fi': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `es': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `bn': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `zh_TW': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `uk': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `en_GB': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `et': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `lt': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `gl': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `bn_IN': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `nl': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `id': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `sr@ije': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `eu': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/http_proxy/ignore_hosts', locale `az': Unable to store a value at key '/schemas/system/http_proxy/ignore_hosts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode' to key `/system/proxy/mode' WARNING: failed to install schema `/schemas/system/proxy/mode', locale `mk': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `zu': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `be': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `ca@valencia': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `nb': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `ml': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `lv': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `sv': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `cs': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `nn': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `pt_BR': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `ta': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `sk': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `ru': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `uz': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `C': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `xh': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `he': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `bg': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `el': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `en@shaw': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `sl': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `bs': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `mn': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `mai': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `af': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `ar': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `hr': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `or': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `ne': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `it': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `pt': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `en_CA': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `as': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `da': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `ka': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `sr@latin': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `zh_CN': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `te': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `zh_HK': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `hi': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `kn': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `ca': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `ja': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `nso': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `hu': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `fr': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `mr': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `tr': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `dz': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `ko': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `ro': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `mg': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `pl': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `sq': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `cy': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `pa': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `gu': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `th': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `de': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `sr': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `vi': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `ast': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `fi': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `es': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `bn': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `zh_TW': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `uk': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `en_GB': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `uz@cyrillic': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `et': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `lt': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `gl': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `bn_IN': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `nl': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `id': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `sr@ije': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `eu': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/mode', locale `az': Unable to store a value at key '/schemas/system/proxy/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host' to key `/system/proxy/secure_host' WARNING: failed to install schema `/schemas/system/proxy/secure_host', locale `mk': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `zu': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `be': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `ca@valencia': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `nb': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `ml': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `lv': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `sv': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `cs': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `nn': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `pt_BR': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `ta': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `sk': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `ru': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `uz': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `C': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `xh': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `he': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `bg': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `el': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `en@shaw': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `sl': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `bs': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `mn': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `mai': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `af': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `ar': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `hr': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `or': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `ne': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `it': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `pt': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `en_CA': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `as': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `da': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `ka': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `sr@latin': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `zh_CN': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `te': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `zh_HK': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `hi': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `kn': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `ca': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `ja': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `nso': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `hu': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `fr': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `mr': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `tr': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `dz': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `ko': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `ro': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `mg': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `pl': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `sq': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `cy': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `pa': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `gu': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `th': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `de': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `sr': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `vi': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `ast': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `fi': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `es': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `bn': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `zh_TW': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `uk': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `en_GB': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `uz@cyrillic': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `et': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `lt': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `gl': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `bn_IN': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `nl': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `id': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `sr@ije': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `eu': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_host', locale `az': Unable to store a value at key '/schemas/system/proxy/secure_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port' to key `/system/proxy/secure_port' WARNING: failed to install schema `/schemas/system/proxy/secure_port', locale `mk': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `zu': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `be': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `ca@valencia': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `nb': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `ml': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `lv': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `sv': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `cs': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `nn': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `pt_BR': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `ta': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `sk': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `ru': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `uz': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `C': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `xh': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `he': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `bg': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `el': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `en@shaw': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `sl': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `bs': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `mn': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `mai': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `af': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `ar': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `hr': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `or': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `ne': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `it': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `pt': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `en_CA': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `as': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `da': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `ka': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `sr@latin': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `zh_CN': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `te': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `zh_HK': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `hi': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `kn': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `ca': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `ja': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `nso': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `hu': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `fr': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `mr': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `tr': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `dz': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `ko': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `ro': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `mg': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `pl': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `sq': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `cy': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `pa': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `gu': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `th': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `de': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `sr': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `vi': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `ast': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `fi': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `es': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `bn': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `zh_TW': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `uk': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `en_GB': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `uz@cyrillic': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `et': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `lt': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `gl': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `bn_IN': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `nl': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `id': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `sr@ije': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `eu': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/secure_port', locale `az': Unable to store a value at key '/schemas/system/proxy/secure_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host' to key `/system/proxy/ftp_host' WARNING: failed to install schema `/schemas/system/proxy/ftp_host', locale `mk': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `zu': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `be': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `ca@valencia': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `nb': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `ml': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `lv': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `sv': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `cs': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `nn': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `pt_BR': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `ta': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `sk': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `ru': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `uz': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `C': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `xh': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `he': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `bg': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `el': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `sl': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `bs': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `mn': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `mai': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `af': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `ar': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `hr': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `or': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `ne': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `it': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `pt': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `en_CA': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `as': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `da': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `ka': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `sr@latin': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `zh_CN': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `te': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `zh_HK': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `hi': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `kn': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `ca': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `ja': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `nso': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `hu': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `fr': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `mr': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `tr': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `dz': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `ko': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `ro': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `mg': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `pl': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `sq': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `cy': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `pa': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `gu': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `th': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `de': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `sr': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `vi': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `ast': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `fi': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `es': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `bn': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `zh_TW': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `uk': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `en_GB': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `uz@cyrillic': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `et': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `lt': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `gl': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `bn_IN': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `nl': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `id': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `sr@ije': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `eu': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_host', locale `az': Unable to store a value at key '/schemas/system/proxy/ftp_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port' to key `/system/proxy/ftp_port' WARNING: failed to install schema `/schemas/system/proxy/ftp_port', locale `mk': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `zu': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `be': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `ca@valencia': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `nb': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `ml': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `lv': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `sv': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `cs': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `nn': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `pt_BR': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `ta': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `sk': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `ru': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `uz': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `C': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `xh': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `he': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `bg': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `el': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `en@shaw': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `sl': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `bs': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `mn': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `mai': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `af': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `ar': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `hr': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `or': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `ne': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `it': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `pt': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `en_CA': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `as': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `da': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `ka': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `sr@latin': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `zh_CN': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `eo': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `te': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `zh_HK': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `hi': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `kn': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `ca': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `ja': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `nso': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `hu': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `fr': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `mr': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `tr': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `dz': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `ko': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `ro': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `mg': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `pl': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `sq': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `cy': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `pa': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `gu': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `th': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `de': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `sr': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `vi': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `ast': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `fi': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `es': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `bn': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `zh_TW': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `uk': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `en_GB': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `uz@cyrillic': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `et': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `lt': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `gl': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `bn_IN': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `nl': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `id': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `sr@ije': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `eu': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/ftp_port', locale `az': Unable to store a value at key '/schemas/system/proxy/ftp_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host' to key `/system/proxy/socks_host' WARNING: failed to install schema `/schemas/system/proxy/socks_host', locale `mk': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `zu': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `be': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `ca@valencia': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `nb': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `ml': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `lv': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `sv': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `cs': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `nn': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `pt_BR': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `ta': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `sk': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `ru': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `uz': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `C': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `xh': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `he': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `bg': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `el': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `en@shaw': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `sl': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `bs': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `mn': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `mai': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `af': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `ar': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `hr': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `or': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `ne': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `it': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `pt': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `en_CA': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `as': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `da': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `ka': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `sr@latin': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `zh_CN': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `te': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `zh_HK': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `hi': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `kn': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `ca': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `ja': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `nso': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `hu': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `fr': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `mr': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `tr': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `dz': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `ko': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `ro': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `mg': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `pl': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `sq': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `cy': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `pa': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `gu': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `th': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `de': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `sr': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `vi': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `ast': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `fi': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `es': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `bn': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `zh_TW': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `uk': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `en_GB': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `uz@cyrillic': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `et': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `lt': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `gl': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `bn_IN': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `nl': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `id': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `sr@ije': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `eu': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_host', locale `az': Unable to store a value at key '/schemas/system/proxy/socks_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port' to key `/system/proxy/socks_port' WARNING: failed to install schema `/schemas/system/proxy/socks_port', locale `mk': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `zu': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `be': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `ca@valencia': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `nb': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `ml': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `lv': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `sv': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `cs': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `nn': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `pt_BR': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `ta': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `sk': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `ru': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `uz': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `C': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `xh': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `he': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `bg': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `el': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `en@shaw': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `sl': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `bs': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `mn': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `mai': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `af': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `ar': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `hr': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `or': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `ne': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `it': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `pt': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `en_CA': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `as': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `da': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `ka': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `sr@latin': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `zh_CN': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `te': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `zh_HK': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `hi': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `kn': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `ca': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `ja': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `nso': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `hu': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `fr': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `mr': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `tr': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `dz': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `ko': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `ro': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `mg': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `pl': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `sq': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `cy': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `pa': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `gu': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `th': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `de': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `sr': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `vi': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `ast': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `fi': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `es': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `bn': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `zh_TW': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `uk': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `en_GB': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `uz@cyrillic': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `et': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `lt': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `gl': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `bn_IN': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `nl': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `id': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `sr@ije': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `eu': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/socks_port', locale `az': Unable to store a value at key '/schemas/system/proxy/socks_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url' to key `/system/proxy/autoconfig_url' WARNING: failed to install schema `/schemas/system/proxy/autoconfig_url', locale `mk': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `zu': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `be': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `ca@valencia': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `nb': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `ml': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `lv': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `sv': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `cs': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `nn': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `pt_BR': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `ta': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `sk': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `ru': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `uz': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `C': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `xh': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `he': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `bg': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `el': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `en@shaw': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `sl': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `bs': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `mn': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `mai': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `af': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `ar': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `hr': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `or': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `ne': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `it': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `pt': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `en_CA': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `as': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `da': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `ka': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `sr@latin': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `zh_CN': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `te': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `zh_HK': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `hi': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `kn': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `ca': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `ja': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `nso': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `hu': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `fr': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `mr': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `tr': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `dz': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `ko': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `ro': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `mg': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `pl': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `sq': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `cy': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `pa': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `gu': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `th': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `de': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `sr': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `vi': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `ast': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `fi': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `es': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `bn': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `zh_TW': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `uk': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `en_GB': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `uz@cyrillic': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `et': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `lt': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `gl': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `bn_IN': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `nl': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `id': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `sr@ije': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `eu': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/proxy/autoconfig_url', locale `az': Unable to store a value at key '/schemas/system/proxy/autoconfig_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup' to key `/system/smb/workgroup' WARNING: failed to install schema `/schemas/system/smb/workgroup', locale `mk': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `oc': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `zu': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `be': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `ca@valencia': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `nb': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `ml': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `lv': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `sv': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `cs': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `nn': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `pt_BR': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `ta': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `C': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `ru': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `uz': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `sk': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `xh': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `he': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `bg': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `el': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `en@shaw': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `sl': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `bs': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `mn': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `mai': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `af': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `ar': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `hr': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `or': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `ne': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `it': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `pt': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `en_CA': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `as': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `da': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `ka': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `sr@latin': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `zh_CN': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `te': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `zh_HK': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `hi': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `kn': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `ca': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `ja': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `nso': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `hu': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `fr': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `mr': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `tr': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `dz': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `ko': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `ro': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `mg': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `pl': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `sq': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `cy': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `pa': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `gu': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `th': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `de': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `sr': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `vi': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `ast': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `fi': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `es': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `bn': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `zh_TW': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `uk': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `en_GB': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `uz@cyrillic': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `et': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `lt': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `gl': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `bn_IN': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `nl': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `id': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `sr@ije': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `eu': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/smb/workgroup', locale `az': Unable to store a value at key '/schemas/system/smb/workgroup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local' to key `/system/dns_sd/display_local' WARNING: failed to install schema `/schemas/system/dns_sd/display_local', locale `zu': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `be': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `ca@valencia': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `nb': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `ml': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `lv': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `sv': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `cs': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `nn': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `pt_BR': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `ta': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `sk': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `ru': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `C': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `xh': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `he': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `bg': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `el': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `en@shaw': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `sl': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `bs': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `mn': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `mai': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `ar': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `hr': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `or': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `ne': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `it': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `pt': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `en_CA': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `as': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `da': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `ka': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `sr@latin': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `zh_CN': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `te': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `zh_HK': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `hi': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `kn': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `ca': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `ja': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `nso': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `hu': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `fr': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `mr': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `tr': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `dz': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `ko': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `ro': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `mg': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `pl': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `sq': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `cy': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `pa': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `gu': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `th': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `sr': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `de': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `vi': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `ast': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `fi': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `es': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `bn': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `zh_TW': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `uk': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `en_GB': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `et': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `lt': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `gl': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `bn_IN': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `nl': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `id': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `eu': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/display_local', locale `mk': Unable to store a value at key '/schemas/system/dns_sd/display_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains' to key `/system/dns_sd/extra_domains' WARNING: failed to install schema `/schemas/system/dns_sd/extra_domains', locale `be': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `ca@valencia': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `nb': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `ml': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `lv': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `sv': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `cs': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `nn': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `pt_BR': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `ta': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `C': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `ru': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `sk': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `he': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `bg': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `el': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `sl': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `mai': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `ar': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `hr': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `or': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `ne': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `it': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `pt': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `en_CA': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `as': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `sr@latin': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `ka': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `da': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `zh_CN': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `te': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `zh_HK': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `hi': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `kn': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `ca': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `ja': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `hu': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `dz': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `fr': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `mr': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `tr': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `ko': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `ro': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `mg': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `pl': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `sq': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `cy': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `pa': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `gu': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `th': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `sr': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `de': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `vi': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `ast': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `fi': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `es': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `bn': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `zh_TW': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `uk': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `en_GB': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `et': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `lt': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `gl': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `bn_IN': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `nl': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `id': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `mk': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/system/dns_sd/extra_domains', locale `eu': Unable to store a value at key '/schemas/system/dns_sd/extra_domains', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec' to key `/desktop/gnome/applications/terminal/exec' WARNING: failed to install schema `/schemas/desktop/gnome/applications/terminal/exec', locale `mk': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `oc': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `zu': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `be': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `ca@valencia': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `nb': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `ml': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `lv': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `sv': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `cs': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `nn': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `pt_BR': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `ta': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `C': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `ru': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `uz': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `sk': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `xh': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `he': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `bg': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `el': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `en@shaw': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `sl': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `bs': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `mn': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `mai': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `af': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `ar': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `hr': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `or': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `ne': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `it': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `pt': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `en_CA': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `as': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `da': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `ka': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `sr@latin': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `zh_CN': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `eo': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `te': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `zh_HK': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `hi': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `kn': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `ca': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `ja': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `nso': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `hu': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `fr': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `mr': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `tr': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `dz': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `ko': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `ro': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `mg': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `pl': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `sq': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `cy': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `pa': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `gu': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `th': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `de': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `sr': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `vi': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `ast': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `fi': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `es': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `bn': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `zh_TW': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `uk': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `en_GB': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `uz@cyrillic': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `et': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `lt': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `gl': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `bn_IN': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `nl': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `id': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `sr@ije': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `eu': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec', locale `az': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg' to key `/desktop/gnome/applications/terminal/exec_arg' WARNING: failed to install schema `/schemas/desktop/gnome/applications/terminal/exec_arg', locale `mk': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `zu': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `be': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `ca@valencia': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `nb': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `ml': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `lv': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `sv': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `cs': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `nn': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `pt_BR': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `ta': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `sk': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `ru': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `C': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `xh': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `he': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `bg': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `el': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `en@shaw': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `sl': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `bs': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `mn': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `mai': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `af': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `ar': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `hr': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `or': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `ne': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `it': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `pt': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `en_CA': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `as': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `da': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `ka': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `sr@latin': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `zh_CN': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `te': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `zh_HK': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `hi': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `kn': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `ca': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `ja': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `nso': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `hu': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `fr': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `mr': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `tr': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `dz': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `ko': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `ro': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `mg': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `pl': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `sq': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `cy': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `pa': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `gu': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `th': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `de': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `sr': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `vi': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `ast': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `fi': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `es': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `bn': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `zh_TW': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `uk': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `en_GB': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `et': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `lt': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `gl': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `bn_IN': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `nl': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `id': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `sr@ije': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `eu': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/terminal/exec_arg', locale `az': Unable to store a value at key '/schemas/desktop/gnome/applications/terminal/exec_arg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec' to key `/desktop/gnome/applications/component_viewer/exec' WARNING: failed to install schema `/schemas/desktop/gnome/applications/component_viewer/exec', locale `mk': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `zu': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `be': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `ca@valencia': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `nb': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `ml': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `lv': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `sv': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `cs': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `nn': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `pt_BR': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `ta': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `sk': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `ru': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `C': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `xh': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `he': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `bg': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `el': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `en@shaw': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `sl': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `bs': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `mn': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `mai': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `af': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `ar': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `hr': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `or': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `ne': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `it': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `pt': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `en_CA': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `as': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `da': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `ka': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `sr@latin': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `zh_CN': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `te': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `zh_HK': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `hi': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `kn': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `ca': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `ja': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `nso': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `hu': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `fr': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `mr': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `tr': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `dz': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `ko': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `ro': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `mg': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `pl': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `sq': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `cy': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `pa': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `gu': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `th': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `de': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `sr': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `vi': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `ast': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `fi': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `es': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `bn': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `zh_TW': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `uk': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `en_GB': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `et': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `lt': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `gl': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `bn_IN': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `nl': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `id': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `sr@ije': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `eu': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/applications/component_viewer/exec', locale `az': Unable to store a value at key '/schemas/desktop/gnome/applications/component_viewer/exec', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled' to key `/desktop/gnome/url-handlers/trash/enabled' WARNING: failed to install schema `/schemas/desktop/gnome/url-handlers/trash/enabled', locale `zu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `be': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `ca@valencia': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `nb': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `ml': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `lv': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `sv': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `cs': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `nn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `pt_BR': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `ta': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `sk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `ru': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `C': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `xh': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `he': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `bg': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `el': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `en@shaw': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `sl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `bs': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `mn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `mai': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `ar': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `hr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `or': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `ne': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `it': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `pt': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `en_CA': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `as': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `da': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `ka': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `sr@latin': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `zh_CN': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `te': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `zh_HK': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `hi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `kn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `ca': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `ja': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `nso': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `hu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `fr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `mr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `tr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `dz': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `ko': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `ro': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `mg': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `pl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `sq': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `cy': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `pa': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `gu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `th': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `sr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `de': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `vi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `ast': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `fi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `es': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `bn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `zh_TW': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `uk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `en_GB': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `et': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `lt': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `gl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `bn_IN': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `nl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `id': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `eu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/enabled', locale `mk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command' to key `/desktop/gnome/url-handlers/trash/command' WARNING: failed to install schema `/schemas/desktop/gnome/url-handlers/trash/command', locale `zu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `be': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `ca@valencia': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `nb': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `ml': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `lv': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `sv': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `cs': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `nn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `pt_BR': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `ta': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `sk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `ru': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `C': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `xh': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `he': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `bg': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `el': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `en@shaw': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `sl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `bs': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `mn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `mai': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `af': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `ar': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `hr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `or': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `ne': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `it': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `pt': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `en_CA': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `as': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `da': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `ka': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `sr@latin': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `zh_CN': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `te': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `zh_HK': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `hi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `kn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `ca': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `ja': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `nso': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `hu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `fr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `mr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `tr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `dz': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `ko': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `ro': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `mg': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `pl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `sq': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `cy': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `pa': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `gu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `th': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `de': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `sr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `vi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `ast': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `fi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `es': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `bn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `zh_TW': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `uk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `en_GB': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `et': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `lt': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `gl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `bn_IN': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `nl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `id': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `eu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/command', locale `mk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal' to key `/desktop/gnome/url-handlers/trash/needs_terminal' WARNING: failed to install schema `/schemas/desktop/gnome/url-handlers/trash/needs_terminal', locale `zu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `be': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `ca@valencia': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `nb': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `ml': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `lv': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `sv': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `cs': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `nn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `pt_BR': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `ta': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `sk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `ru': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `uz': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `C': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `xh': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `he': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `bg': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `el': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `en@shaw': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `sl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `bs': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `mn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `mai': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `af': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `ar': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `hr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `or': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `ne': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `it': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `pt': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `en_CA': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `as': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `da': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `ka': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `sr@latin': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `zh_CN': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `eo': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `te': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `zh_HK': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `hi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `kn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `ca': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `ja': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `nso': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `hu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `fr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `mr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `tr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `dz': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `ko': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `ro': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `mg': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `pl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `sq': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `cy': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `pa': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `gu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `th': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `de': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `sr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `vi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `ast': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `fi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `es': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `bn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `zh_TW': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `uk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `en_GB': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `uz@cyrillic': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `et': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `lt': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `gl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `bn_IN': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `nl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `id': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `eu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/trash/needs_terminal', locale `mk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/trash/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled' to key `/desktop/gnome/url-handlers/ghelp/enabled' WARNING: failed to install schema `/schemas/desktop/gnome/url-handlers/ghelp/enabled', locale `zu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `be': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `ca@valencia': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `nb': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `ml': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `lv': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `sv': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `cs': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `nn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `pt_BR': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `ta': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `sk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `ru': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `C': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `xh': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `he': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `bg': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `el': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `sl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `bs': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `mn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `mai': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `ar': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `hr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `or': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `ne': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `it': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `pt': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `en_CA': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `as': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `sr@latin': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `ka': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `da': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `zh_CN': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `te': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `zh_HK': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `hi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `kn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `ca': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `ja': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `hu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `dz': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `fr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `mr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `tr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `ko': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `ro': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `mg': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `pl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `nso': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `sq': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `pa': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `gu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `cy': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `sr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `de': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `th': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `ast': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `fi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `es': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `vi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `bn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `zh_TW': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `uk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `en_GB': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `et': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `lt': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `gl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `bn_IN': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `nl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `id': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `eu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/enabled', locale `mk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command' to key `/desktop/gnome/url-handlers/ghelp/command' WARNING: failed to install schema `/schemas/desktop/gnome/url-handlers/ghelp/command', locale `zu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `be': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `ca@valencia': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `nb': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `ml': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `lv': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `sv': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `cs': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `nn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `pt_BR': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `ta': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `sk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `ru': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `C': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `xh': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `he': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `bg': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `el': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `sl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `bs': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `mn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `mai': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `af': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `ar': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `hr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `or': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `ne': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `it': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `pt': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `en_CA': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `as': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `da': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `ka': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `sr@latin': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `zh_CN': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `te': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `zh_HK': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `hi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `kn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `ca': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `ja': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `nso': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `hu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `fr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `mr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `tr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `dz': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `ko': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `ro': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `mg': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `pl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `sq': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `cy': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `pa': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `gu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `th': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `sr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `de': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `vi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `ast': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `fi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `es': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `bn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `zh_TW': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `uk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `en_GB': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `et': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `lt': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `gl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `bn_IN': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `nl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `id': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `eu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/command', locale `mk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal' to key `/desktop/gnome/url-handlers/ghelp/needs_terminal' WARNING: failed to install schema `/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `zu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `be': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `ca@valencia': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `nb': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `ml': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `lv': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `sv': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `cs': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `nn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `pt_BR': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `ta': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `sk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `ru': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `uz': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `C': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `xh': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `he': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `bg': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `el': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `en@shaw': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `sl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `bs': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `mn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `mai': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `af': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `ar': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `hr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `or': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `ne': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `it': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `pt': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `en_CA': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `as': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `da': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `ka': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `sr@latin': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `zh_CN': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `eo': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `te': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `zh_HK': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `hi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `kn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `ca': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `ja': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `nso': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `hu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `fr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `mr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `tr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `dz': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `ko': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `ro': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `mg': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `pl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `sq': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `cy': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `pa': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `gu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `th': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `de': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `sr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `vi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `ast': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `fi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `es': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `bn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `zh_TW': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `uk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `en_GB': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `uz@cyrillic': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `et': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `lt': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `gl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `bn_IN': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `nl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `id': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `eu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/ghelp/needs_terminal', locale `mk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/ghelp/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled' to key `/desktop/gnome/url-handlers/info/enabled' WARNING: failed to install schema `/schemas/desktop/gnome/url-handlers/info/enabled', locale `zu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `be': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `ca@valencia': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `nb': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `ml': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `lv': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `sv': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `cs': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `nn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `pt_BR': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `ta': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `sk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `ru': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `C': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `xh': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `he': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `bg': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `el': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `en@shaw': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `sl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `bs': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `mn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `mai': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `ar': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `hr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `or': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `ne': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `it': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `pt': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `en_CA': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `as': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `da': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `ka': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `sr@latin': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `zh_CN': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `te': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `zh_HK': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `hi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `kn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `ca': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `ja': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `nso': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `hu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `fr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `mr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `tr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `dz': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `ko': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `ro': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `mg': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `pl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `sq': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `cy': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `pa': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `gu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `th': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `sr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `de': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `vi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `ast': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `fi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `es': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `bn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `zh_TW': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `uk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `en_GB': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `et': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `lt': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `gl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `bn_IN': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `nl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `id': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `eu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/enabled', locale `mk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command' to key `/desktop/gnome/url-handlers/info/command' WARNING: failed to install schema `/schemas/desktop/gnome/url-handlers/info/command', locale `zu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `be': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `ca@valencia': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `nb': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `ml': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `lv': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `sv': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `cs': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `nn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `pt_BR': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `ta': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `sk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `ru': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `C': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `xh': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `he': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `bg': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `el': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `en@shaw': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `sl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `bs': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `mn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `mai': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `af': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `ar': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `hr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `or': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `ne': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `it': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `pt': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `en_CA': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `as': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `da': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `ka': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `sr@latin': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `zh_CN': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `te': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `zh_HK': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `hi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `kn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `ca': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `ja': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `nso': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `hu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `fr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `mr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `tr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `dz': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `ko': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `ro': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `mg': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `pl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `sq': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `cy': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `pa': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `gu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `th': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `de': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `sr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `vi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `ast': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `fi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `es': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `bn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `zh_TW': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `uk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `en_GB': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `et': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `lt': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `gl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `bn_IN': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `nl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `id': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `eu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/command', locale `mk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal' to key `/desktop/gnome/url-handlers/info/needs_terminal' WARNING: failed to install schema `/schemas/desktop/gnome/url-handlers/info/needs_terminal', locale `zu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `be': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `ca@valencia': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `nb': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `ml': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `lv': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `sv': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `cs': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `nn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `pt_BR': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `ta': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `sk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `ru': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `uz': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `C': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `xh': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `he': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `bg': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `el': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `en@shaw': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `sl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `bs': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `mn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `mai': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `af': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `ar': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `hr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `or': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `ne': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `it': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `pt': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `en_CA': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `as': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `da': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `ka': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `sr@latin': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `zh_CN': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `eo': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `te': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `zh_HK': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `hi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `kn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `ca': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `ja': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `nso': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `hu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `fr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `mr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `tr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `dz': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `ko': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `ro': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `mg': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `pl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `sq': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `cy': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `pa': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `gu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `th': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `de': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `sr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `vi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `ast': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `fi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `es': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `bn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `zh_TW': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `uk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `en_GB': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `uz@cyrillic': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `et': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `lt': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `gl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `bn_IN': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `nl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `id': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `eu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/info/needs_terminal', locale `mk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/info/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled' to key `/desktop/gnome/url-handlers/man/enabled' WARNING: failed to install schema `/schemas/desktop/gnome/url-handlers/man/enabled', locale `zu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `be': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `ca@valencia': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `nb': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `ml': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `lv': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `sv': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `cs': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `nn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `pt_BR': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `ta': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `sk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `ru': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `C': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `xh': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `he': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `bg': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `el': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `en@shaw': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `sl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `bs': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `mn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `mai': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `ar': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `hr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `or': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `ne': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `it': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `pt': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `en_CA': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `as': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `da': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `ka': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `sr@latin': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `zh_CN': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `te': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `zh_HK': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `hi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `kn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `ca': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `ja': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `nso': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `hu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `fr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `mr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `tr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `dz': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `ko': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `ro': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `mg': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `pl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `sq': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `cy': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `pa': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `gu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `th': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `sr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `de': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `vi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `ast': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `fi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `es': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `bn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `zh_TW': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `uk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `en_GB': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `et': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `lt': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `gl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `bn_IN': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `nl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `id': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `eu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/enabled', locale `mk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command' to key `/desktop/gnome/url-handlers/man/command' WARNING: failed to install schema `/schemas/desktop/gnome/url-handlers/man/command', locale `zu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `be': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `ca@valencia': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `nb': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `ml': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `lv': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `sv': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `cs': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `nn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `pt_BR': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `ta': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `sk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `ru': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `C': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `xh': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `he': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `bg': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `el': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `en@shaw': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `sl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `bs': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `mn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `mai': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `af': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `ar': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `hr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `or': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `ne': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `it': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `pt': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `en_CA': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `as': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `da': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `ka': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `sr@latin': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `zh_CN': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `te': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `zh_HK': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `hi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `kn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `ca': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `ja': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `nso': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `hu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `fr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `mr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `tr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `dz': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `ko': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `ro': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `mg': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `pl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `sq': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `cy': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `pa': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `gu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `th': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `de': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `sr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `vi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `ast': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `fi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `es': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `bn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `zh_TW': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `uk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `en_GB': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `et': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `lt': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `gl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `bn_IN': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `nl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `id': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `eu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/command', locale `mk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal' to key `/desktop/gnome/url-handlers/man/needs_terminal' WARNING: failed to install schema `/schemas/desktop/gnome/url-handlers/man/needs_terminal', locale `zu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `be': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `ca@valencia': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `nb': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `ml': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `lv': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `sv': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `cs': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `nn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `pt_BR': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `ta': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `sk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `ru': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `uz': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `C': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `xh': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `he': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `bg': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `el': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `en@shaw': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `sl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `bs': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `mn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `mai': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `af': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `ar': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `hr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `or': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `ne': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `it': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `pt': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `en_CA': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `as': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `da': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `ka': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `sr@latin': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `zh_CN': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `eo': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `te': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `zh_HK': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `hi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `kn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `ca': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `ja': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `nso': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `hu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `fr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `mr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `tr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `dz': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `ko': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `ro': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `mg': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `pl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `sq': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `cy': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `pa': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `gu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `th': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `de': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `sr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `vi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `ast': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `fi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `es': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `bn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `zh_TW': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `uk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `en_GB': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `uz@cyrillic': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `et': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `lt': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `gl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `bn_IN': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `nl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `id': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `eu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/man/needs_terminal', locale `mk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/man/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled' to key `/desktop/gnome/url-handlers/http/enabled' WARNING: failed to install schema `/schemas/desktop/gnome/url-handlers/http/enabled', locale `zu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `be': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `ca@valencia': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `nb': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `ml': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `lv': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `sv': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `cs': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `nn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `pt_BR': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `ta': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `sk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `ru': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `C': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `xh': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `he': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `bg': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `el': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `en@shaw': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `sl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `bs': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `mai': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `ar': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `hr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `or': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `ne': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `it': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `pt': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `en_CA': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `as': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `sr@latin': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `ka': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `da': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `zh_CN': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `te': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `zh_HK': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `hi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `kn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `ca': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `ja': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `hu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `dz': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `fr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `mr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `tr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `ko': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `ro': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `mg': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `pl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `nso': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `sq': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `pa': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `gu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `cy': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `sr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `de': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `th': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `ast': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `fi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `es': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `vi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `bn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `zh_TW': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `uk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `en_GB': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `et': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `lt': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `gl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `bn_IN': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `nl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `id': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `eu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/enabled', locale `mk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command' to key `/desktop/gnome/url-handlers/http/command' WARNING: failed to install schema `/schemas/desktop/gnome/url-handlers/http/command', locale `zu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `be': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `ca@valencia': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `nb': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `ml': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `lv': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `sv': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `cs': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `nn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `pt_BR': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `ta': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `sk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `ru': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `C': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `xh': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `he': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `bg': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `el': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `en@shaw': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `sl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `bs': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `mai': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `af': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `ar': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `hr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `or': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `ne': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `it': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `pt': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `en_CA': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `as': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `da': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `ka': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `sr@latin': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `zh_CN': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `te': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `zh_HK': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `hi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `kn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `ca': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `ja': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `nso': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `hu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `fr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `mr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `tr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `dz': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `ko': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `ro': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `mg': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `pl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `sq': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `cy': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `pa': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `gu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `th': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `sr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `de': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `vi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `ast': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `fi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `es': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `bn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `zh_TW': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `uk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `en_GB': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `et': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `lt': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `gl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `bn_IN': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `nl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `id': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `eu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/command', locale `mk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal' to key `/desktop/gnome/url-handlers/http/needs_terminal' WARNING: failed to install schema `/schemas/desktop/gnome/url-handlers/http/needs_terminal', locale `zu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `be': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `ca@valencia': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `nb': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `ml': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `lv': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `sv': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `cs': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `nn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `pt_BR': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `ta': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `sk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `ru': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `uz': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `C': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `xh': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `he': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `bg': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `el': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `en@shaw': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `sl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `bs': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `mn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `mai': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `af': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `ar': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `hr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `or': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `ne': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `it': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `pt': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `en_CA': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `as': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `da': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `ka': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `sr@latin': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `zh_CN': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `eo': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `te': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `zh_HK': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `hi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `kn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `ca': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `ja': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `nso': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `hu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `fr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `mr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `tr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `dz': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `ko': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `ro': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `mg': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `pl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `sq': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `cy': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `pa': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `gu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `th': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `de': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `sr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `vi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `ast': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `fi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `es': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `bn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `zh_TW': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `uk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `en_GB': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `uz@cyrillic': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `et': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `lt': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `gl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `bn_IN': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `nl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `id': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `eu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/http/needs_terminal', locale `mk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/http/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled' to key `/desktop/gnome/url-handlers/https/enabled' WARNING: failed to install schema `/schemas/desktop/gnome/url-handlers/https/enabled', locale `zu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `be': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `ca@valencia': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `nb': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `ml': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `lv': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `sv': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `cs': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `nn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `pt_BR': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `ta': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `C': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `ru': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `sk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `xh': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `he': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `bg': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `el': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `sl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `bs': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `mai': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `ar': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `hr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `or': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `ne': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `it': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `pt': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `en_CA': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `as': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `sr@latin': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `ka': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `da': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `zh_CN': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `te': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `zh_HK': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `hi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `kn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `ca': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `ja': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `hu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `dz': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `fr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `mr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `tr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `ko': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `ro': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `mg': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `pl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `nso': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `sq': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `pa': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `gu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `cy': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `sr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `de': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `th': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `ast': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `fi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `es': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `vi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `bn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `zh_TW': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `uk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `en_GB': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `et': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `lt': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `gl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `bn_IN': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `nl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `id': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `eu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/enabled', locale `mk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command' to key `/desktop/gnome/url-handlers/https/command' WARNING: failed to install schema `/schemas/desktop/gnome/url-handlers/https/command', locale `zu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `be': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `ca@valencia': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `nb': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `ml': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `lv': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `sv': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `cs': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `nn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `pt_BR': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `ta': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `sk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `ru': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `C': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `xh': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `he': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `bg': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `el': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `sl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `bs': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `mai': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `af': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `ar': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `hr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `or': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `ne': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `it': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `pt': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `en_CA': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `as': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `sr@latin': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `ka': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `da': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `zh_CN': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `te': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `zh_HK': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `hi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `kn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `ca': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `ja': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `hu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `dz': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `fr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `mr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `tr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `ko': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `ro': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `mg': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `pl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `nso': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `sq': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `pa': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `gu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `cy': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `sr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `de': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `th': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `ast': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `fi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `es': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `vi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `bn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `zh_TW': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `uk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `en_GB': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `et': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `lt': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `gl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `bn_IN': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `nl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `id': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `eu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/command', locale `mk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal' to key `/desktop/gnome/url-handlers/https/needs_terminal' WARNING: failed to install schema `/schemas/desktop/gnome/url-handlers/https/needs_terminal', locale `zu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `be': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `ca@valencia': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `nb': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `ml': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `lv': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `sv': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `cs': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `nn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `pt_BR': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `ta': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `sk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `ru': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `uz': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `C': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `xh': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `he': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `bg': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `el': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `en@shaw': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `sl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `bs': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `mn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `mai': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `af': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `ar': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `hr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `or': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `ne': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `it': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `pt': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `en_CA': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `as': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `da': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `ka': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `sr@latin': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `zh_CN': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `eo': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `te': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `zh_HK': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `hi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `kn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `ca': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `ja': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `nso': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `hu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `fr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `mr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `tr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `dz': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `ko': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `ro': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `mg': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `pl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `sq': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `cy': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `pa': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `gu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `th': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `de': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `sr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `vi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `ast': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `fi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `es': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `bn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `zh_TW': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `uk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `en_GB': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `uz@cyrillic': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `et': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `lt': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `gl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `bn_IN': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `nl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `id': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `eu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/https/needs_terminal', locale `mk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/https/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled' to key `/desktop/gnome/url-handlers/mailto/enabled' WARNING: failed to install schema `/schemas/desktop/gnome/url-handlers/mailto/enabled', locale `zu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `be': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `ca@valencia': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `nb': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `ml': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `lv': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `sv': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `cs': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `nn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `pt_BR': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `ta': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `sk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `ru': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `C': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `xh': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `he': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `bg': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `el': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `sl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `bs': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `mn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `mai': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `ar': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `hr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `or': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `ne': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `it': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `pt': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `en_CA': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `as': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `sr@latin': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `ka': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `da': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `zh_CN': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `te': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `zh_HK': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `hi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `kn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `ca': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `ja': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `hu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `dz': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `fr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `mr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `tr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `ko': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `ro': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `mg': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `pl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `nso': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `sq': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `pa': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `gu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `cy': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `sr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `de': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `th': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `ast': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `fi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `es': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `vi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `bn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `zh_TW': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `uk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `en_GB': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `et': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `lt': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `gl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `bn_IN': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `nl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `id': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `eu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/enabled', locale `mk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command' to key `/desktop/gnome/url-handlers/mailto/command' WARNING: failed to install schema `/schemas/desktop/gnome/url-handlers/mailto/command', locale `zu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `be': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `ca@valencia': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `nb': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `ml': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `lv': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `sv': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `cs': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `nn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `pt_BR': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `ta': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `sk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `ru': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `C': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `xh': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `he': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `bg': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `el': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `sl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `bs': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `mn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `mai': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `af': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `ar': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `hr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `or': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `ne': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `it': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `pt': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `en_CA': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `as': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `da': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `ka': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `sr@latin': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `zh_CN': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `te': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `zh_HK': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `hi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `kn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `ca': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `ja': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `nso': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `hu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `fr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `mr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `tr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `dz': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `ko': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `ro': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `mg': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `pl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `sq': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `cy': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `pa': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `gu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `th': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `sr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `de': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `vi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `ast': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `fi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `es': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `bn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `zh_TW': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `uk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `en_GB': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `et': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `lt': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `gl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `bn_IN': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `nl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `id': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `eu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/command', locale `mk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal' to key `/desktop/gnome/url-handlers/mailto/needs_terminal' WARNING: failed to install schema `/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', locale `zu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `be': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `ca@valencia': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `nb': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `ml': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `lv': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `sv': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `cs': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `nn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `pt_BR': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `ta': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `sk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `ru': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `uz': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `C': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `xh': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `he': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `bg': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `el': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `en@shaw': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `sl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `bs': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `mn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `mai': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `af': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `ar': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `hr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `or': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `ne': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `it': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `pt': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `en_CA': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `as': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `da': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `ka': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `sr@latin': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `zh_CN': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `eo': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `te': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `zh_HK': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `hi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `kn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `ca': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `ja': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `nso': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `hu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `fr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `mr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `tr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `dz': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `ko': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `ro': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `mg': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `pl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `sq': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `cy': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `pa': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `gu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `th': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `de': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `sr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `vi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `ast': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `fi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `es': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `bn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `zh_TW': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `uk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `en_GB': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `uz@cyrillic': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `et': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `lt': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `gl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `bn_IN': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `nl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `id': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `eu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/mailto/needs_terminal', locale `mk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/mailto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled' to key `/desktop/gnome/url-handlers/aim/enabled' WARNING: failed to install schema `/schemas/desktop/gnome/url-handlers/aim/enabled', locale `zu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `be': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `ca@valencia': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `nb': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `ml': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `lv': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `sv': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `cs': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `nn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `pt_BR': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `ta': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `sk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `ru': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `C': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `xh': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `he': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `bg': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `el': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `en@shaw': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `sl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `bs': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `mn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `mai': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `ar': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `hr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `or': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `ne': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `it': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `pt': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `en_CA': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `as': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `da': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `ka': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `sr@latin': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `zh_CN': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `te': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `zh_HK': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `hi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `kn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `ca': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `ja': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `hu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `dz': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `fr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `mr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `tr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `ko': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `ro': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `mg': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `pl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `nso': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `sq': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `pa': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `gu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `cy': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `sr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `de': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `th': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `fi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `es': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `vi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `bn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `zh_TW': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `uk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `en_GB': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `et': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `lt': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `gl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `bn_IN': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `nl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `id': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `eu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/enabled', locale `mk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command' to key `/desktop/gnome/url-handlers/aim/command' WARNING: failed to install schema `/schemas/desktop/gnome/url-handlers/aim/command', locale `zu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `be': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `ca@valencia': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `nb': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `ml': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `lv': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `sv': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `cs': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `nn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `pt_BR': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `ta': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `sk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `ru': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `C': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `xh': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `he': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `bg': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `el': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `en@shaw': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `sl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `bs': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `mn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `mai': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `af': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `ar': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `hr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `or': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `ne': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `it': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `pt': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `en_CA': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `as': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `da': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `ka': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `sr@latin': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `zh_CN': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `te': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `zh_HK': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `hi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `kn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `ca': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `ja': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `nso': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `hu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `fr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `mr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `tr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `dz': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `ko': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `ro': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `mg': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `pl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `sq': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `cy': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `pa': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `gu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `th': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `sr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `de': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `vi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `fi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `es': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `bn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `zh_TW': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `uk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `en_GB': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `et': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `lt': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `gl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `bn_IN': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `nl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `id': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `eu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/command', locale `mk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal' to key `/desktop/gnome/url-handlers/aim/needs_terminal' WARNING: failed to install schema `/schemas/desktop/gnome/url-handlers/aim/needs_terminal', locale `zu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `be': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `ca@valencia': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `nb': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `ml': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `lv': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `sv': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `cs': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `nn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `pt_BR': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `ta': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `sk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `ru': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `uz': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `C': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `xh': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `he': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `bg': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `el': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `en@shaw': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `sl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `bs': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `mn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `mai': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `af': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `ar': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `hr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `or': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `ne': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `it': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `pt': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `en_CA': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `as': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `da': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `ka': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `sr@latin': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `zh_CN': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `eo': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `te': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `zh_HK': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `hi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `kn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `ca': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `ja': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `nso': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `hu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `fr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `mr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `tr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `dz': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `ko': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `ro': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `mg': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `pl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `sq': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `cy': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `pa': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `gu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `th': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `de': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `sr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `vi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `ast': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `fi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `es': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `bn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `zh_TW': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `uk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `en_GB': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `uz@cyrillic': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `et': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `lt': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `gl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `bn_IN': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `nl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `id': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `eu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/aim/needs_terminal', locale `mk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/aim/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled' to key `/desktop/gnome/url-handlers/callto/enabled' WARNING: failed to install schema `/schemas/desktop/gnome/url-handlers/callto/enabled', locale `zu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `be': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `ca@valencia': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `nb': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `ml': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `lv': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `sv': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `cs': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `nn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `pt_BR': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `ta': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `sk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `ru': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `C': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `xh': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `he': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `bg': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `el': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `sl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `bs': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `mn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `mai': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `ar': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `hr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `or': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `ne': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `it': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `pt': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `en_CA': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `as': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `sr@latin': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `ka': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `da': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `zh_CN': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `te': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `zh_HK': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `hi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `kn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `ca': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `ja': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `hu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `dz': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `fr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `mr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `tr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `ko': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `ro': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `mg': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `pl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `nso': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `sq': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `pa': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `gu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `cy': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `sr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `de': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `th': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `ast': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `fi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `es': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `vi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `bn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `zh_TW': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `uk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `en_GB': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `et': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `lt': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `gl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `bn_IN': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `nl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `id': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `eu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/enabled', locale `mk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command' to key `/desktop/gnome/url-handlers/callto/command' WARNING: failed to install schema `/schemas/desktop/gnome/url-handlers/callto/command', locale `zu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `be': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `ca@valencia': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `nb': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `ml': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `lv': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `sv': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `cs': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `nn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `pt_BR': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `ta': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `sk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `ru': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `C': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `xh': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `he': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `bg': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `el': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `sl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `bs': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `mn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `mai': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `af': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `ar': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `hr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `or': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `ne': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `it': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `pt': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `en_CA': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `as': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `da': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `ka': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `sr@latin': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `zh_CN': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `te': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `zh_HK': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `hi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `kn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `ca': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `ja': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `nso': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `hu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `fr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `mr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `tr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `dz': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `ko': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `ro': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `mg': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `pl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `sq': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `cy': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `pa': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `gu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `th': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `sr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `de': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `vi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `ast': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `fi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `es': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `bn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `zh_TW': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `uk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `en_GB': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `et': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `lt': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `gl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `bn_IN': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `nl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `id': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `eu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/command', locale `mk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal' to key `/desktop/gnome/url-handlers/callto/needs_terminal' WARNING: failed to install schema `/schemas/desktop/gnome/url-handlers/callto/needs_terminal', locale `zu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `be': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `ca@valencia': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `nb': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `ml': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `lv': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `sv': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `cs': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `nn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `pt_BR': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `ta': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `sk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `ru': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `uz': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `C': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `xh': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `he': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `bg': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `el': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `en@shaw': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `sl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `bs': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `mn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `mai': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `af': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `ar': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `hr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `or': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `ne': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `it': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `pt': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `en_CA': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `as': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `da': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `ka': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `sr@latin': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `zh_CN': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `eo': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `te': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `zh_HK': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `hi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `kn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `ca': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `ja': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `nso': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `hu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `fr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `mr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `tr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `dz': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `ko': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `ro': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `mg': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `pl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `sq': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `cy': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `pa': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `gu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `th': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `de': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `sr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `vi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `ast': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `fi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `es': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `bn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `zh_TW': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `uk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `en_GB': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `uz@cyrillic': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `et': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `lt': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `gl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `bn_IN': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `nl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `id': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `eu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/callto/needs_terminal', locale `mk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/callto/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled' to key `/desktop/gnome/url-handlers/h323/enabled' WARNING: failed to install schema `/schemas/desktop/gnome/url-handlers/h323/enabled', locale `zu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `be': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `ca@valencia': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `nb': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `ml': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `lv': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `sv': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `cs': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `nn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `pt_BR': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `ta': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `sk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `ru': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `C': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `xh': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `he': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `bg': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `el': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `en@shaw': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `sl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `bs': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `mai': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `ar': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `hr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `or': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `ne': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `it': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `pt': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `en_CA': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `as': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `sr@latin': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `ka': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `da': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `zh_CN': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `te': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `zh_HK': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `hi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `kn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `ca': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `ja': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `hu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `dz': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `fr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `mr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `tr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `ko': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `ro': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `mg': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `pl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `nso': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `sq': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `pa': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `gu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `cy': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `sr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `de': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `th': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `ast': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `fi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `es': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `vi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `bn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `zh_TW': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `uk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `en_GB': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `et': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `lt': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `gl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `bn_IN': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `nl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `id': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `eu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/enabled', locale `mk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command' to key `/desktop/gnome/url-handlers/h323/command' WARNING: failed to install schema `/schemas/desktop/gnome/url-handlers/h323/command', locale `zu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `be': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `ca@valencia': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `nb': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `ml': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `lv': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `sv': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `cs': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `nn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `pt_BR': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `ta': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `sk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `ru': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `C': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `xh': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `he': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `bg': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `el': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `en@shaw': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `sl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `bs': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `mai': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `af': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `ar': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `hr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `or': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `ne': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `it': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `pt': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `en_CA': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `as': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `da': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `ka': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `sr@latin': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `zh_CN': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `te': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `zh_HK': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `hi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `kn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `ca': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `ja': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `nso': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `hu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `fr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `mr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `tr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `dz': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `ko': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `ro': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `mg': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `pl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `sq': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `cy': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `pa': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `gu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `th': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `sr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `de': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `vi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `ast': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `fi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `es': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `bn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `zh_TW': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `uk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `en_GB': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `et': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `lt': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `gl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `bn_IN': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `nl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `id': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `eu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/command', locale `mk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal' to key `/desktop/gnome/url-handlers/h323/needs_terminal' WARNING: failed to install schema `/schemas/desktop/gnome/url-handlers/h323/needs_terminal', locale `zu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `be': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `ca@valencia': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `nb': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `ml': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `lv': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `sv': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `cs': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `nn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `pt_BR': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `ta': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `sk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `ru': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `uz': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `C': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `xh': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `he': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `bg': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `el': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `en@shaw': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `sl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `bs': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `mn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `mai': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `af': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `ar': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `hr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `or': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `ne': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `it': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `pt': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `en_CA': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `as': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `da': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `ka': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `sr@latin': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `zh_CN': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `eo': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `te': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `zh_HK': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `hi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `kn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `ca': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `ja': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `nso': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `hu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `fr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `mr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `tr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `dz': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `ko': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `ro': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `mg': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `pl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `sq': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `cy': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `pa': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `gu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `th': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `de': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `sr': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `vi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `ast': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `fi': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `es': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `bn': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `zh_TW': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `uk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `en_GB': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `uz@cyrillic': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `et': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `lt': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `gl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `bn_IN': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `nl': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `id': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `eu': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/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/desktop/gnome/url-handlers/h323/needs_terminal', locale `mk': Unable to store a value at key '/schemas/desktop/gnome/url-handlers/h323/needs_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /gnu/store/das27n35yv43mvd5r5xrw3drajs1krc0-gconf-3.2.6/etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf test -z "/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc/gconf/schemas" || /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/mkdir -p "/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc/gconf/schemas" /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c -m 644 system_http_proxy.schemas system_smb.schemas system_dns_sd.schemas desktop_default_applications.schemas desktop_gnome_url_handlers.schemas '/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc/gconf/schemas' make[2]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/schemas' make[1]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/schemas' Making install in devel-docs make[1]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/devel-docs' Making install in gnome-vfs-tutorial make[2]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/devel-docs/gnome-vfs-tutorial' make[3]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/devel-docs/gnome-vfs-tutorial' make[3]: Nothing to be done for 'install-exec-am'. make[3]: Nothing to be done for 'install-data-am'. make[3]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/devel-docs/gnome-vfs-tutorial' make[2]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/devel-docs/gnome-vfs-tutorial' make[2]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/devel-docs' make[3]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/devel-docs' make[3]: Nothing to be done for 'install-exec-am'. make[3]: Nothing to be done for 'install-data-am'. make[3]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/devel-docs' make[2]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/devel-docs' make[1]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/devel-docs' Making install in doc make[1]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/doc' make[2]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/doc' make[2]: Nothing to be done for 'install-exec-am'. mkdir -p -- /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/gtk-doc/html/gnome-vfs-2.0 -- Installing ./html/about.html -- Installing ./html/data-types.html -- Installing ./html/gnome-vfs-2.0.devhelp -- Installing ./html/gnome-vfs-2.0.devhelp2 -- Installing ./html/gnome-vfs-2.0-gnome-vfs-application-registry.html -- Installing ./html/gnome-vfs-2.0-gnome-vfs-async-ops.html -- Installing ./html/gnome-vfs-2.0-gnome-vfs-cancellation.html -- Installing ./html/gnome-vfs-2.0-gnome-vfs-context.html -- Installing ./html/gnome-vfs-2.0-gnome-vfs-directory-basic-ops.html -- Installing ./html/gnome-vfs-2.0-gnome-vfs-directory-find-ops.html -- Installing ./html/gnome-vfs-2.0-gnome-vfs-directory-list-ops.html -- Installing ./html/gnome-vfs-2.0-gnome-vfs-dns-sd.html -- Installing ./html/gnome-vfs-2.0-gnome-vfs-drive.html -- Installing ./html/gnome-vfs-2.0-gnome-vfs-file-advanced-ops.html -- Installing ./html/gnome-vfs-2.0-gnome-vfs-file-basic-ops.html -- Installing ./html/gnome-vfs-2.0-gnome-vfs-file-info.html -- Installing ./html/gnome-vfs-2.0-gnome-vfs-file-info-ops.html -- Installing ./html/gnome-vfs-2.0-gnome-vfs-file-rw-ops.html -- Installing ./html/gnome-vfs-2.0-gnome-vfs-file-size.html -- Installing ./html/gnome-vfs-2.0-gnome-vfs-file-trunc-ops.html -- Installing ./html/gnome-vfs-2.0-gnome-vfs-inet-connection.html -- Installing ./html/gnome-vfs-2.0-gnome-vfs-init.html -- Installing ./html/gnome-vfs-2.0-gnome-vfs-method.html -- Installing ./html/gnome-vfs-2.0-gnome-vfs-mime-database-deprecated.html -- Installing ./html/gnome-vfs-2.0-gnome-vfs-mime-database.html -- Installing ./html/gnome-vfs-2.0-gnome-vfs-mime.html -- Installing ./html/gnome-vfs-2.0-gnome-vfs-mime-monitor.html -- Installing ./html/gnome-vfs-2.0-gnome-vfs-mime-utils.html -- Installing ./html/gnome-vfs-2.0-gnome-vfs-module-callback.html -- Installing ./html/gnome-vfs-2.0-gnome-vfs-module-callback-module-api.html -- Installing ./html/gnome-vfs-2.0-gnome-vfs-module.html -- Installing ./html/gnome-vfs-2.0-gnome-vfs-module-shared.html -- Installing ./html/gnome-vfs-2.0-gnome-vfs-monitor.html -- Installing ./html/gnome-vfs-2.0-gnome-vfs-parse-ls.html -- Installing ./html/gnome-vfs-2.0-gnome-vfs-resolve.html -- Installing ./html/gnome-vfs-2.0-gnome-vfs-result.html -- Installing ./html/gnome-vfs-2.0-gnome-vfs-socket-buffer.html -- Installing ./html/gnome-vfs-2.0-gnome-vfs-socket.html -- Installing ./html/gnome-vfs-2.0-gnome-vfs-ssl.html -- Installing ./html/gnome-vfs-2.0-gnome-vfs-standard-callbacks.html -- Installing ./html/gnome-vfs-2.0-gnome-vfs-transform.html -- Installing ./html/gnome-vfs-2.0-gnome-vfs-uri.html -- Installing ./html/gnome-vfs-2.0-gnome-vfs-utils.html -- Installing ./html/gnome-vfs-2.0-gnome-vfs-volume.html -- Installing ./html/gnome-vfs-2.0-gnome-vfs-volume-monitor.html -- Installing ./html/gnome-vfs-2.0-gnome-vfs-xfer.html -- Installing ./html/gnome-vfs-basic-file-ops.html -- Installing ./html/gnome-vfs-directory-ops.html -- Installing ./html/gnome-vfs-file-and-dirs-ops.html -- Installing ./html/gnome-vfs-file-async-ops.html -- Installing ./html/gnome-vfs-first-steps.html -- Installing ./html/gnome-vfs-writing-modules.html -- Installing ./html/home.png -- Installing ./html/index.html -- Installing ./html/index.sgml -- Installing ./html/left.png -- Installing ./html/mime-registry.html -- Installing ./html/modules.html -- Installing ./html/networking.html -- Installing ./html/right.png -- Installing ./html/style.css -- Installing ./html/up.png -- Installing ./html/volumes.html make[2]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/doc' make[1]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/doc' Making install in programs make[1]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/programs' make[2]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/programs' test -z "/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin" || /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/mkdir -p "/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin" /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash ../libtool --mode=install /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c gnomevfs-cat gnomevfs-copy gnomevfs-info gnomevfs-ls gnomevfs-monitor gnomevfs-mkdir gnomevfs-mv gnomevfs-rm gnomevfs-df '/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin' libtool: install: /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c .libs/gnomevfs-cat /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin/gnomevfs-cat libtool: install: /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c .libs/gnomevfs-copy /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin/gnomevfs-copy libtool: install: /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c .libs/gnomevfs-info /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin/gnomevfs-info libtool: install: /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c .libs/gnomevfs-ls /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin/gnomevfs-ls libtool: install: /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c .libs/gnomevfs-monitor /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin/gnomevfs-monitor libtool: install: /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c .libs/gnomevfs-mkdir /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin/gnomevfs-mkdir libtool: install: /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c .libs/gnomevfs-mv /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin/gnomevfs-mv libtool: install: /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c .libs/gnomevfs-rm /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin/gnomevfs-rm libtool: install: /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c .libs/gnomevfs-df /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin/gnomevfs-df make[2]: Nothing to be done for 'install-data-am'. make[2]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/programs' make[1]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/programs' Making install in test make[1]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/test' make[2]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/test' make[2]: Nothing to be done for 'install-exec-am'. make[2]: Nothing to be done for 'install-data-am'. make[2]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/test' make[1]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/test' Making install in po make[1]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/po' linguas="af am ar as ast az be bg bn bn_IN bs ca ca@valencia cs cy da de dz el en_CA en_GB en@shaw eo es et eu fa fi fr ga gl gu he hi hr hu id is it ja ka kn ko ku li lt lv mai mg mk ml mn mr ms nb ne nl nn nso oc or pa pl pt pt_BR ro ru rw sk sl sq sr sr@latin sr@ije sv ta te th tr uk uz uz@cyrillic vi wa xh yi zh_CN zh_HK zh_TW zu "; \ for lang in $linguas; do \ dir=/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/$lang/LC_MESSAGES; \ /gnu/store/7s2zlc4r9wqvlh9x2gqmzm4lnmbsdzmn-bash-minimal-5.1.8/bin/bash /tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/install-sh -d $dir; \ if test -r $lang.gmo; then \ /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c -m 644 $lang.gmo $dir/gnome-vfs-2.0.mo; \ echo "installing $lang.gmo as $dir/gnome-vfs-2.0.mo"; \ else \ /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c -m 644 ./$lang.gmo $dir/gnome-vfs-2.0.mo; \ echo "installing ./$lang.gmo as" \ "$dir/gnome-vfs-2.0.mo"; \ fi; \ if test -r $lang.gmo.m; then \ /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c -m 644 $lang.gmo.m $dir/gnome-vfs-2.0.mo.m; \ echo "installing $lang.gmo.m as $dir/gnome-vfs-2.0.mo.m"; \ else \ if test -r ./$lang.gmo.m ; then \ /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c -m 644 ./$lang.gmo.m \ $dir/gnome-vfs-2.0.mo.m; \ echo "installing ./$lang.gmo.m as" \ "$dir/gnome-vfs-2.0.mo.m"; \ else \ true; \ fi; \ fi; \ done installing af.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/af/LC_MESSAGES/gnome-vfs-2.0.mo installing am.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/am/LC_MESSAGES/gnome-vfs-2.0.mo installing ar.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/ar/LC_MESSAGES/gnome-vfs-2.0.mo installing as.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/as/LC_MESSAGES/gnome-vfs-2.0.mo installing ast.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/ast/LC_MESSAGES/gnome-vfs-2.0.mo installing az.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/az/LC_MESSAGES/gnome-vfs-2.0.mo installing be.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/be/LC_MESSAGES/gnome-vfs-2.0.mo installing bg.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/bg/LC_MESSAGES/gnome-vfs-2.0.mo installing bn.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/bn/LC_MESSAGES/gnome-vfs-2.0.mo installing bn_IN.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/bn_IN/LC_MESSAGES/gnome-vfs-2.0.mo installing bs.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/bs/LC_MESSAGES/gnome-vfs-2.0.mo installing ca.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/ca/LC_MESSAGES/gnome-vfs-2.0.mo installing ca@valencia.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/ca@valencia/LC_MESSAGES/gnome-vfs-2.0.mo installing cs.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/cs/LC_MESSAGES/gnome-vfs-2.0.mo installing cy.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/cy/LC_MESSAGES/gnome-vfs-2.0.mo installing da.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/da/LC_MESSAGES/gnome-vfs-2.0.mo installing de.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/de/LC_MESSAGES/gnome-vfs-2.0.mo installing dz.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/dz/LC_MESSAGES/gnome-vfs-2.0.mo installing el.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/el/LC_MESSAGES/gnome-vfs-2.0.mo installing en_CA.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/en_CA/LC_MESSAGES/gnome-vfs-2.0.mo installing en_GB.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/en_GB/LC_MESSAGES/gnome-vfs-2.0.mo installing en@shaw.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/en@shaw/LC_MESSAGES/gnome-vfs-2.0.mo installing eo.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/eo/LC_MESSAGES/gnome-vfs-2.0.mo installing es.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/es/LC_MESSAGES/gnome-vfs-2.0.mo installing et.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/et/LC_MESSAGES/gnome-vfs-2.0.mo installing eu.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/eu/LC_MESSAGES/gnome-vfs-2.0.mo installing fa.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/fa/LC_MESSAGES/gnome-vfs-2.0.mo installing fi.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/fi/LC_MESSAGES/gnome-vfs-2.0.mo installing fr.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/fr/LC_MESSAGES/gnome-vfs-2.0.mo installing ga.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/ga/LC_MESSAGES/gnome-vfs-2.0.mo installing gl.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/gl/LC_MESSAGES/gnome-vfs-2.0.mo installing gu.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/gu/LC_MESSAGES/gnome-vfs-2.0.mo installing he.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/he/LC_MESSAGES/gnome-vfs-2.0.mo installing hi.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/hi/LC_MESSAGES/gnome-vfs-2.0.mo installing hr.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/hr/LC_MESSAGES/gnome-vfs-2.0.mo installing hu.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/hu/LC_MESSAGES/gnome-vfs-2.0.mo installing id.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/id/LC_MESSAGES/gnome-vfs-2.0.mo installing is.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/is/LC_MESSAGES/gnome-vfs-2.0.mo installing it.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/it/LC_MESSAGES/gnome-vfs-2.0.mo installing ja.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/ja/LC_MESSAGES/gnome-vfs-2.0.mo installing ka.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/ka/LC_MESSAGES/gnome-vfs-2.0.mo installing kn.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/kn/LC_MESSAGES/gnome-vfs-2.0.mo installing ko.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/ko/LC_MESSAGES/gnome-vfs-2.0.mo installing ku.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/ku/LC_MESSAGES/gnome-vfs-2.0.mo installing li.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/li/LC_MESSAGES/gnome-vfs-2.0.mo installing lt.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/lt/LC_MESSAGES/gnome-vfs-2.0.mo installing lv.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/lv/LC_MESSAGES/gnome-vfs-2.0.mo installing mai.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/mai/LC_MESSAGES/gnome-vfs-2.0.mo installing mg.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/mg/LC_MESSAGES/gnome-vfs-2.0.mo installing mk.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/mk/LC_MESSAGES/gnome-vfs-2.0.mo installing ml.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/ml/LC_MESSAGES/gnome-vfs-2.0.mo installing mn.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/mn/LC_MESSAGES/gnome-vfs-2.0.mo installing mr.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/mr/LC_MESSAGES/gnome-vfs-2.0.mo installing ms.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/ms/LC_MESSAGES/gnome-vfs-2.0.mo installing nb.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/nb/LC_MESSAGES/gnome-vfs-2.0.mo installing ne.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/ne/LC_MESSAGES/gnome-vfs-2.0.mo installing nl.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/nl/LC_MESSAGES/gnome-vfs-2.0.mo installing nn.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/nn/LC_MESSAGES/gnome-vfs-2.0.mo installing nso.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/nso/LC_MESSAGES/gnome-vfs-2.0.mo installing oc.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/oc/LC_MESSAGES/gnome-vfs-2.0.mo installing or.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/or/LC_MESSAGES/gnome-vfs-2.0.mo installing pa.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/pa/LC_MESSAGES/gnome-vfs-2.0.mo installing pl.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/pl/LC_MESSAGES/gnome-vfs-2.0.mo installing pt.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/pt/LC_MESSAGES/gnome-vfs-2.0.mo installing pt_BR.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/pt_BR/LC_MESSAGES/gnome-vfs-2.0.mo installing ro.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/ro/LC_MESSAGES/gnome-vfs-2.0.mo installing ru.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/ru/LC_MESSAGES/gnome-vfs-2.0.mo installing rw.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/rw/LC_MESSAGES/gnome-vfs-2.0.mo installing sk.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/sk/LC_MESSAGES/gnome-vfs-2.0.mo installing sl.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/sl/LC_MESSAGES/gnome-vfs-2.0.mo installing sq.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/sq/LC_MESSAGES/gnome-vfs-2.0.mo installing sr.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/sr/LC_MESSAGES/gnome-vfs-2.0.mo installing sr@latin.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/sr@latin/LC_MESSAGES/gnome-vfs-2.0.mo installing sr@ije.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/sr@ije/LC_MESSAGES/gnome-vfs-2.0.mo installing sv.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/sv/LC_MESSAGES/gnome-vfs-2.0.mo installing ta.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/ta/LC_MESSAGES/gnome-vfs-2.0.mo installing te.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/te/LC_MESSAGES/gnome-vfs-2.0.mo installing th.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/th/LC_MESSAGES/gnome-vfs-2.0.mo installing tr.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/tr/LC_MESSAGES/gnome-vfs-2.0.mo installing uk.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/uk/LC_MESSAGES/gnome-vfs-2.0.mo installing uz.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/uz/LC_MESSAGES/gnome-vfs-2.0.mo installing uz@cyrillic.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/uz@cyrillic/LC_MESSAGES/gnome-vfs-2.0.mo installing vi.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/vi/LC_MESSAGES/gnome-vfs-2.0.mo installing wa.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/wa/LC_MESSAGES/gnome-vfs-2.0.mo installing xh.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/xh/LC_MESSAGES/gnome-vfs-2.0.mo installing yi.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/yi/LC_MESSAGES/gnome-vfs-2.0.mo installing zh_CN.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/zh_CN/LC_MESSAGES/gnome-vfs-2.0.mo installing zh_HK.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/zh_HK/LC_MESSAGES/gnome-vfs-2.0.mo installing zh_TW.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/zh_TW/LC_MESSAGES/gnome-vfs-2.0.mo installing zu.gmo as /gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/share/locale/zu/LC_MESSAGES/gnome-vfs-2.0.mo make[1]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4/po' make[1]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4' make[2]: Entering directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4' make[2]: Nothing to be done for 'install-exec-am'. test -z "/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/pkgconfig" || /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/mkdir -p "/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/pkgconfig" /gnu/store/9a0cjh929maqvkxn3inv6jqbxn72fkx0-coreutils-8.32/bin/install -c -m 644 gnome-vfs-2.0.pc gnome-vfs-module-2.0.pc '/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib/pkgconfig' make[2]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4' make[1]: Leaving directory '/tmp/guix-build-gnome-vfs-2.24.4.drv-0/gnome-vfs-2.24.4' phase `install' succeeded after 9.9 seconds starting phase `patch-shebangs' phase `patch-shebangs' succeeded after 0.0 seconds starting phase `strip' stripping binaries in "/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib" with "strip" and flags ("--strip-unneeded" "--enable-deterministic-archives") stripping binaries in "/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/libexec" with "strip" and flags ("--strip-unneeded" "--enable-deterministic-archives") stripping binaries in "/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin" with "strip" and flags ("--strip-unneeded" "--enable-deterministic-archives") phase `strip' succeeded after 0.3 seconds starting phase `validate-runpath' validating RUNPATH of 13 binaries in "/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/lib"... validating RUNPATH of 1 binaries in "/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/libexec"... validating RUNPATH of 9 binaries in "/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/bin"... phase `validate-runpath' succeeded after 0.0 seconds starting phase `validate-documentation-location' phase `validate-documentation-location' succeeded after 0.0 seconds starting phase `delete-info-dir-file' phase `delete-info-dir-file' succeeded after 0.0 seconds starting phase `patch-dot-desktop-files' phase `patch-dot-desktop-files' succeeded after 0.0 seconds starting phase `make-dynamic-linker-cache' created '/gnu/store/h22n90wpvmkfw18as4hl9cyx7xc8k9zm-gnome-vfs-2.24.4/etc/ld.so.cache' from 14 library search path entries phase `make-dynamic-linker-cache' succeeded after 0.5 seconds starting phase `install-license-files' installing 2 license files from '.' phase `install-license-files' succeeded after 0.0 seconds starting phase `reset-gzip-timestamps' phase `reset-gzip-timestamps' succeeded after 0.0 seconds starting phase `compress-documentation' phase `compress-documentation' succeeded after 0.0 seconds