Build start: 2014. júl. 9., szerda, 16.37.27 UTC **** gnomeradio_1.8-6.17 **** Fetching ccache... done. Utolsó belépés: 2014. júl. 9., szerda, 16.37.00 UTC, pts/0 FYI: Compile snapshot nem fog készülni! ($UHUBUILD_COMPILESNAPSHOTDIR nincs beállítva) FYI: Install snapshot nem fog készülni! ($UHUBUILD_INSTALLSNAPSHOTDIR nincs beállítva) Források letöltése... Chroot rendszer felépítése... Chroot könyvtár: /var/build/chroot2 Fájlrendszerek csatolása: dev , proc 0% [Working] Get:1 ftp://172.16.1.1 ./ InRelease 0% [1 InRelease 0 B] Ign ftp://172.16.1.1 ./ InRelease 25% [Working] Get:2 ftp://172.16.1.1 ./ Release.gpg 25% [2 Release.gpg 0 B] Ign ftp://172.16.1.1 ./ Release.gpg 33% [Working] Hit ftp://172.16.1.1 ./ Release 50% [Working] Get:3 ftp://172.16.1.1 ./ Packages/DiffIndex 50% [3 Packages 0 B] Ign ftp://172.16.1.1 ./ Packages/DiffIndex 57% [Working] Get:4 ftp://172.16.1.1 ./ Translation-en 57% [4 Translation-en 0 B] Get:5 ftp://172.16.1.1 ./ Packages 57% [5 Packages 0 B] Get:6 ftp://172.16.1.1 ./ Translation-en 57% [6 Translation-en 0 B] Get:7 ftp://172.16.1.1 ./ Packages 57% [7 Packages 0 B] Get:8 ftp://172.16.1.1 ./ Translation-en 57% [8 Translation-en 0 B] Get:9 ftp://172.16.1.1 ./ Packages 57% [9 Packages 0 B] Get:10 ftp://172.16.1.1 ./ Translation-en 57% [10 Translation-en 0 B] Get:11 ftp://172.16.1.1 ./ Packages [514 KB] 0% [11 Packages 0 B/514 KB 0%] 100% [Working] 100% [11 Packages gzip 0 B] [Query] Get:12 ftp://172.16.1.1 ./ Translation-en 100% [11 Packages gzip 0 B] [12 Translation-en 0 B] Ign ftp://172.16.1.1 ./ Translation-en 100% [11 Packages gzip 0 B] 100% [Working] Fetched 514 KB in 1s (505 KB/s) Reading package lists... 0% Reading package lists... 0% Reading package lists... 2% Reading package lists... 52% Reading package lists... 100% Reading package lists... 100% Reading package lists... 100% Reading package lists... Done Reading package lists... 0% Reading package lists... 0% Reading package lists... 73% Reading package lists... Done Building dependency tree... 0% Building dependency tree... 0% Building dependency tree... 50% Building dependency tree... 50% Building dependency tree Reading state information... 0% Reading state information... 0% Reading state information... Done uhubuild-config is already the newest version. Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 0% [Working] Get:1 ftp://172.16.1.1 ./ InRelease 0% [1 InRelease 0 B] Ign ftp://172.16.1.1 ./ InRelease 25% [Working] Get:2 ftp://172.16.1.1 ./ Release.gpg 25% [2 Release.gpg 0 B] Ign ftp://172.16.1.1 ./ Release.gpg 33% [Working] Hit ftp://172.16.1.1 ./ Release 50% [Working] Get:3 ftp://172.16.1.1 ./ Packages/DiffIndex 50% [3 Packages 0 B] Ign ftp://172.16.1.1 ./ Packages/DiffIndex 57% [Working] Get:4 ftp://172.16.1.1 ./ Translation-en 57% [4 Translation-en 0 B] Get:5 ftp://172.16.1.1 ./ Packages 57% [5 Packages 0 B] Get:6 ftp://172.16.1.1 ./ Translation-en 57% [6 Translation-en 0 B] Get:7 ftp://172.16.1.1 ./ Packages 57% [7 Packages 0 B] Get:8 ftp://172.16.1.1 ./ Translation-en 57% [8 Translation-en 0 B] Get:9 ftp://172.16.1.1 ./ Packages 57% [9 Packages 0 B] Get:10 ftp://172.16.1.1 ./ Translation-en 57% [10 Translation-en 0 B] Hit ftp://172.16.1.1 ./ Packages 71% [Working] Get:11 ftp://172.16.1.1 ./ Translation-en 71% [11 Translation-en 0 B] Ign ftp://172.16.1.1 ./ Translation-en 86% [Working] Reading package lists... 0% Reading package lists... 0% Reading package lists... 2% Reading package lists... 100% Reading package lists... 100% Reading package lists... Done dpkg: warning: package not in database at line 55: dbus dpkg: warning: package not in database at line 55: dbus-glib dpkg: warning: package not in database at line 61: freetype2 dpkg: warning: package not in database at line 66: js17 dpkg: warning: package not in database at line 67: libusb dpkg: warning: package not in database at line 67: libxml2 dpkg: warning: package not in database at line 67: polkit dpkg: warning: package not in database at line 92: gc dpkg: warning: package not in database at line 98: libunistring dpkg: warning: package not in database at line 98: guile dpkg: warning: package not in database at line 98: libtasn1 dpkg: warning: package not in database at line 98: nettle dpkg: warning: package not in database at line 98: p11-kit dpkg: warning: package not in database at line 98: trousers dpkg: warning: package not in database at line 98: gnutls dpkg: warning: package not in database at line 98: libice dpkg: warning: package not in database at line 98: libjpeg dpkg: warning: package not in database at line 98: libsm dpkg: warning: package not in database at line 99: libtiff dpkg: warning: package not in database at line 110: alsa-lib dpkg: warning: package not in database at line 110: libxau dpkg: warning: package not in database at line 110: libxdmcp dpkg: warning: package not in database at line 110: libxcb dpkg: warning: package not in database at line 110: libx11 dpkg: warning: package not in database at line 110: libxext dpkg: warning: package not in database at line 110: libxi dpkg: warning: package not in database at line 110: libxtst dpkg: warning: package not in database at line 110: at-spi2-core dpkg: warning: package not in database at line 110: atk dpkg: warning: package not in database at line 110: at-spi2-atk dpkg: warning: package not in database at line 110: dbus-dev dpkg: warning: package not in database at line 110: libffi-dev dpkg: warning: package not in database at line 110: pcre-dev dpkg: warning: package not in database at line 111: glib-dev dpkg: warning: package not in database at line 111: at-spi2-core-dev dpkg: warning: package not in database at line 111: at-spi2-atk-dev dpkg: warning: package not in database at line 111: atk-dev dpkg: warning: package not in database at line 113: fontconfig dpkg: warning: package not in database at line 113: libxrender dpkg: warning: package not in database at line 113: pixman dpkg: warning: package not in database at line 113: cairo dpkg: warning: package not in database at line 113: jasper dpkg: warning: package not in database at line 113: gdk-pixbuf dpkg: warning: package not in database at line 113: lcms2 dpkg: warning: package not in database at line 113: libgusb dpkg: warning: package not in database at line 113: colord dpkg: warning: package not in database at line 113: cups dpkg: warning: package not in database at line 113: icu dpkg: warning: package not in database at line 113: harfbuzz dpkg: warning: package not in database at line 113: icon-theme-hicolor dpkg: warning: package not in database at line 113: libxcomposite dpkg: warning: package not in database at line 113: libxfixes dpkg: warning: package not in database at line 113: libxinerama dpkg: warning: package not in database at line 113: libxft dpkg: warning: package not in database at line 113: pango dpkg: warning: package not in database at line 113: shared-mime-info dpkg: warning: package not in database at line 113: gtk2 dpkg: warning: package not in database at line 113: libxcursor dpkg: warning: package not in database at line 113: libxdamage dpkg: warning: package not in database at line 113: libxrandr dpkg: warning: package not in database at line 113: gtk dpkg: warning: package not in database at line 113: libdaemon dpkg: warning: package not in database at line 113: avahi dpkg: warning: package not in database at line 115: libpng-dev dpkg: warning: package not in database at line 115: freetype2-dev dpkg: warning: package not in database at line 115: fontconfig-dev dpkg: warning: package not in database at line 115: x.org-util-macros dpkg: warning: package not in database at line 115: x.org-proto-dev dpkg: warning: package not in database at line 115: libxau-dev dpkg: warning: package not in database at line 115: libxdmcp-dev dpkg: warning: package not in database at line 115: libxcb-dev dpkg: warning: package not in database at line 115: libx11-dev dpkg: warning: package not in database at line 115: libxext-dev dpkg: warning: package not in database at line 115: libxrender-dev dpkg: warning: package not in database at line 115: pixman-dev dpkg: warning: package not in database at line 115: cairo-dev dpkg: warning: package not in database at line 115: gdk-pixbuf-dev dpkg: warning: package not in database at line 115: icu-dev dpkg: warning: package not in database at line 115: harfbuzz-dev dpkg: warning: package not in database at line 115: libxfixes-dev dpkg: warning: package not in database at line 115: libxcomposite-dev dpkg: warning: package not in database at line 115: libxcursor-dev dpkg: warning: package not in database at line 115: libxdamage-dev dpkg: warning: package not in database at line 115: libxi-dev dpkg: warning: package not in database at line 115: libxinerama-dev dpkg: warning: package not in database at line 115: libxrandr-dev dpkg: warning: package not in database at line 115: libxft-dev dpkg: warning: package not in database at line 115: pango-dev dpkg: warning: package not in database at line 115: gtk-dev dpkg: warning: package not in database at line 115: gtk2-dev dpkg: warning: package not in database at line 115: libglade2 dpkg: warning: package not in database at line 115: gtk2-sharp dpkg: warning: package not in database at line 115: avahi-dev dpkg: warning: package not in database at line 116: cdparanoia dpkg: warning: package not in database at line 116: dbus-glib-dev dpkg: warning: package not in database at line 122: gconf2 dpkg: warning: package not in database at line 122: gconf2-dev dpkg: warning: package not in database at line 122: libxslt dpkg: warning: package not in database at line 122: gnome-doc-utils dpkg: warning: package not in database at line 122: gnome2-vfs dpkg: warning: package not in database at line 122: gnome2-vfs-dev dpkg: warning: package not in database at line 122: gstreamer0.10 dpkg: warning: package not in database at line 122: libogg dpkg: warning: package not in database at line 122: libtheora dpkg: warning: package not in database at line 122: libvisual dpkg: warning: package not in database at line 122: libvorbis dpkg: warning: package not in database at line 122: libxv dpkg: warning: package not in database at line 122: gst0.10-plugins-base dpkg: warning: package not in database at line 122: libxml2-dev dpkg: warning: package not in database at line 122: gstreamer0.10-dev dpkg: warning: package not in database at line 122: gst0.10-plugins-base-dev dpkg: warning: package not in database at line 122: libgnome-media-profiles dpkg: warning: package not in database at line 122: libgnome-media-profiles-dev dpkg: warning: package not in database at line 122: lirc dpkg: warning: package not in database at line 122: lirc-dev dpkg: warning: package not in database at line 125: perl-xml-parser dpkg: warning: found unknown packages; this might mean the available database is outdated, and needs to be updated through a frontend method (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 18022 files and directories currently installed.) Removing libggz-dev (0.99.4-3.12) ... Purging configuration files for libggz-dev (0.99.4-3.12) ... Removing libggz (0.99.4-3.12) ... Purging configuration files for libggz (0.99.4-3.12) ... Removing libgcrypt-dev (1.6.1-2.2) ... Purging configuration files for libgcrypt-dev (1.6.1-2.2) ... Removing libgpg-error-dev (1.13-2.2) ... Purging configuration files for libgpg-error-dev (1.13-2.2) ... Reading package lists... 0% Reading package lists... 0% Reading package lists... 74% Reading package lists... Done Building dependency tree... 0% Building dependency tree... 0% Building dependency tree... 50% Building dependency tree... 50% Building dependency tree Reading state information... 0% Reading state information... 0% Reading state information... Done acl is already the newest version. attr is already the newest version. audit is already the newest version. autoconf is already the newest version. automake is already the newest version. bash is already the newest version. bc is already the newest version. binutils is already the newest version. bison is already the newest version. bzip2 is already the newest version. bzip2-dev is already the newest version. ccache is already the newest version. coreutils is already the newest version. cpio is already the newest version. cpp is already the newest version. cracklib is already the newest version. cryptsetup is already the newest version. curl is already the newest version. cyrus-sasl2 is already the newest version. db4 is already the newest version. desktop-file-utils is already the newest version. diffutils is already the newest version. dl is already the newest version. dosfstools is already the newest version. dpkg is already the newest version. expat is already the newest version. expat-dev is already the newest version. fbgetty is already the newest version. file is already the newest version. findutils is already the newest version. flex is already the newest version. flex-dev is already the newest version. gamin is already the newest version. gawk is already the newest version. gcc is already the newest version. gcc-lib is already the newest version. gdbm is already the newest version. gettext is already the newest version. gettext-tools is already the newest version. glib is already the newest version. glibc is already the newest version. glibc-dev is already the newest version. glibc-locales is already the newest version. gmp is already the newest version. grep is already the newest version. grub is already the newest version. gzip is already the newest version. kernel-headers is already the newest version. krb5 is already the newest version. libcap is already the newest version. libelf is already the newest version. libffi is already the newest version. libgcrypt is already the newest version. libgpg-error is already the newest version. libidn is already the newest version. libpng is already the newest version. libqrencode is already the newest version. libsigsegv is already the newest version. libstdc++ is already the newest version. libstdc++-dev is already the newest version. libtool is already the newest version. licenses is already the newest version. lvm is already the newest version. lynx is already the newest version. m4 is already the newest version. make is already the newest version. module-init-tools is already the newest version. mpc is already the newest version. mpfr is already the newest version. ncurses is already the newest version. ncurses-dev is already the newest version. nspr is already the newest version. nss is already the newest version. openldap is already the newest version. openssl is already the newest version. optipng is already the newest version. pam is already the newest version. pam-dev is already the newest version. patch is already the newest version. pbzip2 is already the newest version. pcre is already the newest version. perl is already the newest version. perl-encode-locale is already the newest version. perl-file-listing is already the newest version. perl-html-parser is already the newest version. perl-html-tagset is already the newest version. perl-http-cookies is already the newest version. perl-http-daemon is already the newest version. perl-http-date is already the newest version. perl-http-message is already the newest version. perl-http-negotiate is already the newest version. perl-io-html is already the newest version. perl-libwww is already the newest version. perl-lwp-mediatypes is already the newest version. perl-net-http is already the newest version. perl-timedate is already the newest version. perl-uri is already the newest version. perl-www-robotrules is already the newest version. pigz is already the newest version. pkgconfig is already the newest version. popt is already the newest version. pretendroot is already the newest version. python is already the newest version. readline is already the newest version. readline-dev is already the newest version. rmt is already the newest version. rpm is already the newest version. sed is already the newest version. shadow is already the newest version. sortdir is already the newest version. sqlite is already the newest version. systemd is already the newest version. tar is already the newest version. texinfo is already the newest version. timeslide is already the newest version. uhu-base is already the newest version. uhubuild-common is already the newest version. uhubuild-config is already the newest version. uhubuild-helpers is already the newest version. uhubuild-here is already the newest version. uhu-pkg is already the newest version. uhu-utils is already the newest version. unarj is already the newest version. unrar is already the newest version. unzip is already the newest version. util-linux is already the newest version. which is already the newest version. xz is already the newest version. xz-dev is already the newest version. zlib is already the newest version. zlib-dev is already the newest version. Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done The following NEW packages will be installed: alsa-lib at-spi2-atk at-spi2-atk-dev at-spi2-core at-spi2-core-dev atk atk-dev avahi avahi-dev cairo cairo-dev cdparanoia colord cups dbus dbus-dev dbus-glib dbus-glib-dev fontconfig fontconfig-dev freetype2 freetype2-dev gc gconf2 gconf2-dev gdk-pixbuf gdk-pixbuf-dev glib-dev gnome-doc-utils gnome2-vfs gnome2-vfs-dev gnutls gst0.10-plugins-base gst0.10-plugins-base-dev gstreamer0.10 gstreamer0.10-dev gtk gtk-dev gtk2 gtk2-dev gtk2-sharp guile harfbuzz harfbuzz-dev icon-theme-hicolor icu icu-dev jasper js17 lcms2 libdaemon libffi-dev libglade2 libgnome-media-profiles libgnome-media-profiles-dev libgusb libice libjpeg libogg libpng-dev libsm libtasn1 libtheora libtiff libunistring libusb libvisual libvorbis libx11 libx11-dev libxau libxau-dev libxcb libxcb-dev libxcomposite libxcomposite-dev libxcursor libxcursor-dev libxdamage libxdamage-dev libxdmcp libxdmcp-dev libxext libxext-dev libxfixes libxfixes-dev libxft libxft-dev libxi libxi-dev libxinerama libxinerama-dev libxml2 libxml2-dev libxrandr libxrandr-dev libxrender libxrender-dev libxslt libxtst libxv lirc lirc-dev nettle p11-kit pango pango-dev pcre-dev perl-xml-parser pixman pixman-dev polkit shared-mime-info trousers x.org-proto-dev x.org-util-macros 0 upgraded, 116 newly installed, 0 to remove and 0 not upgraded. Need to get 3383 KB/93.2 MB of archives. After this operation, 400 MB of additional disk space will be used. WARNING: The following packages cannot be authenticated! dbus dbus-glib freetype2 js17 libusb libxml2 polkit gc libunistring guile libtasn1 nettle p11-kit trousers gnutls libice libjpeg libsm libtiff alsa-lib libxau libxdmcp libxcb libx11 libxext libxi libxtst at-spi2-core atk at-spi2-atk dbus-dev libffi-dev pcre-dev glib-dev at-spi2-core-dev at-spi2-atk-dev atk-dev fontconfig libxrender pixman cairo jasper gdk-pixbuf lcms2 libgusb colord cups icu harfbuzz icon-theme-hicolor libxcomposite libxfixes libxinerama libxft pango shared-mime-info gtk2 libxcursor libxdamage libxrandr gtk libdaemon avahi libpng-dev freetype2-dev fontconfig-dev x.org-util-macros x.org-proto-dev libxau-dev libxdmcp-dev libxcb-dev libx11-dev libxext-dev libxrender-dev pixman-dev cairo-dev gdk-pixbuf-dev icu-dev harfbuzz-dev libxfixes-dev libxcomposite-dev libxcursor-dev libxdamage-dev libxi-dev libxinerama-dev libxrandr-dev libxft-dev pango-dev gtk-dev gtk2-dev libglade2 gtk2-sharp avahi-dev cdparanoia dbus-glib-dev gconf2 gconf2-dev libxslt gnome-doc-utils gnome2-vfs gnome2-vfs-dev gstreamer0.10 libogg libtheora libvisual libvorbis libxv gst0.10-plugins-base libxml2-dev gstreamer0.10-dev gst0.10-plugins-base-dev libgnome-media-profiles libgnome-media-profiles-dev lirc lirc-dev perl-xml-parser Authentication warning overridden. 0% [Working] Get:1 ftp://172.16.1.1/uhu/dev/packages/ ./ gnome-doc-utils 0.20.10-2.14 [475 KB] 0% [1 gnome-doc-utils 0 B/475 KB 0%] 14% [Working] Get:2 ftp://172.16.1.1/uhu/dev/packages/ ./ gnome2-vfs-dev 2.24.4-2.18 [254 KB] 14% [2 gnome2-vfs-dev 0 B/254 KB 0%] 22% [Working] Get:3 ftp://172.16.1.1/uhu/dev/packages/ ./ gstreamer0.10-dev 0.10.36-4.6 [1130 KB] 22% [3 gstreamer0.10-dev 0 B/1130 KB 0%] 55% [Working] Get:4 ftp://172.16.1.1/uhu/dev/packages/ ./ gst0.10-plugins-base-dev 0.10.36-5.6 [715 KB] 55% [4 gst0.10-plugins-base-dev 0 B/715 KB 0%] 76% [Working] Get:5 ftp://172.16.1.1/uhu/dev/packages/ ./ libgnome-media-profiles 3.0.0-3.15 [796 KB] 76% [5 libgnome-media-profiles 0 B/796 KB 0%] 100% [Working] Get:6 ftp://172.16.1.1/uhu/dev/packages/ ./ libgnome-media-profiles-dev 3.0.0-3.15 [7702 B] 100% [6 libgnome-media-profiles-dev 0 B/7702 B 0%] 100% [Working] Get:7 ftp://172.16.1.1/uhu/dev/packages/ ./ lirc-dev 0.9.0-9.7 [5856 B] 100% [7 lirc-dev 0 B/5856 B 0%] 100% [Working] Fetched 3383 KB in 0s (4376 KB/s) Selecting previously unselected package dbus. (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 17997 files and directories currently installed.) Preparing to unpack .../dbus_1.8.4-2.2_i386.uhu ... Unpacking dbus (1.8.4-2.2) ... Selecting previously unselected package dbus-glib. Preparing to unpack .../dbus-glib_0.102-2.2_i386.uhu ... Unpacking dbus-glib (0.102-2.2) ... Selecting previously unselected package freetype2. Preparing to unpack .../freetype2_2.5.3-2.6_i386.uhu ... Unpacking freetype2 (2.5.3-2.6) ... Selecting previously unselected package js17. Preparing to unpack .../js17_17.0.0-2.2_i386.uhu ... Unpacking js17 (17.0.0-2.2) ... Selecting previously unselected package libusb. Preparing to unpack .../libusb_1.0.18-2.5_i386.uhu ... Unpacking libusb (1.0.18-2.5) ... Selecting previously unselected package libxml2. Preparing to unpack .../libxml2_2.9.1-2.2_i386.uhu ... Unpacking libxml2 (2.9.1-2.2) ... Selecting previously unselected package polkit. Preparing to unpack .../polkit_0.112-4.6_i386.uhu ... Unpacking polkit (0.112-4.6) ... Selecting previously unselected package gc. Preparing to unpack .../archives/gc_7.2-2.17_i386.uhu ... Unpacking gc (7.2-2.17) ... Selecting previously unselected package libunistring. Preparing to unpack .../libunistring_0.9.3-3.2_i386.uhu ... Unpacking libunistring (0.9.3-3.2) ... Selecting previously unselected package guile. Preparing to unpack .../guile_2.0.11-4.6_i386.uhu ... Unpacking guile (2.0.11-4.6) ... Selecting previously unselected package libtasn1. Preparing to unpack .../libtasn1_3.6-2.7_i386.uhu ... Unpacking libtasn1 (3.6-2.7) ... Selecting previously unselected package nettle. Preparing to unpack .../nettle_2.7.1-2.6_i386.uhu ... Unpacking nettle (2.7.1-2.6) ... Selecting previously unselected package p11-kit. Preparing to unpack .../p11-kit_0.20.2-3.3_i386.uhu ... Unpacking p11-kit (0.20.2-3.3) ... Selecting previously unselected package trousers. Preparing to unpack .../trousers_0.3.13-3.7_i386.uhu ... Unpacking trousers (0.3.13-3.7) ... Selecting previously unselected package gnutls. Preparing to unpack .../gnutls_3.3.5-1.3_i386.uhu ... Unpacking gnutls (3.3.5-1.3) ... Selecting previously unselected package libice. Preparing to unpack .../libice_1.0.9-2.2_i386.uhu ... Unpacking libice (1.0.9-2.2) ... Selecting previously unselected package libjpeg. Preparing to unpack .../libjpeg_9a-3.2_i386.uhu ... Unpacking libjpeg (9a-3.2) ... Selecting previously unselected package libsm. Preparing to unpack .../libsm_1.2.2-2.2_i386.uhu ... Unpacking libsm (1.2.2-2.2) ... Selecting previously unselected package libtiff. Preparing to unpack .../libtiff_4.0.3-3.2_i386.uhu ... Unpacking libtiff (4.0.3-3.2) ... Selecting previously unselected package alsa-lib. Preparing to unpack .../alsa-lib_1.0.28-1.6_i386.uhu ... Unpacking alsa-lib (1.0.28-1.6) ... Selecting previously unselected package libxau. Preparing to unpack .../libxau_1.0.8-1.16_i386.uhu ... Unpacking libxau (1.0.8-1.16) ... Selecting previously unselected package libxdmcp. Preparing to unpack .../libxdmcp_1.1.1-2.16_i386.uhu ... Unpacking libxdmcp (1.1.1-2.16) ... Selecting previously unselected package libxcb. Preparing to unpack .../libxcb_1.10-1.14_i386.uhu ... Unpacking libxcb (1.10-1.14) ... Selecting previously unselected package libx11. Preparing to unpack .../libx11_1.6.2-3.2_i386.uhu ... Unpacking libx11 (1.6.2-3.2) ... Selecting previously unselected package libxext. Preparing to unpack .../libxext_1.3.2-3.2_i386.uhu ... Unpacking libxext (1.3.2-3.2) ... Selecting previously unselected package libxi. Preparing to unpack .../libxi_1.7.2-1.16_i386.uhu ... Unpacking libxi (1.7.2-1.16) ... Selecting previously unselected package libxtst. Preparing to unpack .../libxtst_1.2.2-1.16_i386.uhu ... Unpacking libxtst (1.2.2-1.16) ... Selecting previously unselected package at-spi2-core. Preparing to unpack .../at-spi2-core_2.12.0-1.12_i386.uhu ... Unpacking at-spi2-core (2.12.0-1.12) ... Selecting previously unselected package atk. Preparing to unpack .../atk_2.12.0-1.12_i386.uhu ... Unpacking atk (2.12.0-1.12) ... Selecting previously unselected package at-spi2-atk. Preparing to unpack .../at-spi2-atk_2.12.1-1.10_i386.uhu ... Unpacking at-spi2-atk (2.12.1-1.10) ... Selecting previously unselected package dbus-dev. Preparing to unpack .../dbus-dev_1.8.4-2.2_i386.uhu ... Unpacking dbus-dev (1.8.4-2.2) ... Selecting previously unselected package libffi-dev. Preparing to unpack .../libffi-dev_3.0.13-2.15_i386.uhu ... Unpacking libffi-dev (3.0.13-2.15) ... Selecting previously unselected package pcre-dev. Preparing to unpack .../pcre-dev_8.35-1.5_i386.uhu ... Unpacking pcre-dev (8.35-1.5) ... Selecting previously unselected package glib-dev. Preparing to unpack .../glib-dev_2.40.0-1.12_i386.uhu ... Unpacking glib-dev (2.40.0-1.12) ... Selecting previously unselected package at-spi2-core-dev. Preparing to unpack .../at-spi2-core-dev_2.12.0-1.12_i386.uhu ... Unpacking at-spi2-core-dev (2.12.0-1.12) ... Selecting previously unselected package at-spi2-atk-dev. Preparing to unpack .../at-spi2-atk-dev_2.12.1-1.10_i386.uhu ... Unpacking at-spi2-atk-dev (2.12.1-1.10) ... Selecting previously unselected package atk-dev. Preparing to unpack .../atk-dev_2.12.0-1.12_i386.uhu ... Unpacking atk-dev (2.12.0-1.12) ... Selecting previously unselected package fontconfig. Preparing to unpack .../fontconfig_2.11.1-1.11_i386.uhu ... Unpacking fontconfig (2.11.1-1.11) ... Selecting previously unselected package libxrender. Preparing to unpack .../libxrender_0.9.8-1.16_i386.uhu ... Unpacking libxrender (0.9.8-1.16) ... Selecting previously unselected package pixman. Preparing to unpack .../pixman_0.32.4-1.15_i386.uhu ... Unpacking pixman (0.32.4-1.15) ... Selecting previously unselected package cairo. Preparing to unpack .../cairo_1.12.16-1.21_i386.uhu ... Unpacking cairo (1.12.16-1.21) ... Selecting previously unselected package jasper. Preparing to unpack .../jasper_1.900.1-3.45_i386.uhu ... Unpacking jasper (1.900.1-3.45) ... Selecting previously unselected package gdk-pixbuf. Preparing to unpack .../gdk-pixbuf_2.30.8-1.8_i386.uhu ... Unpacking gdk-pixbuf (2.30.8-1.8) ... Selecting previously unselected package lcms2. Preparing to unpack .../lcms2_2.6-1.11_i386.uhu ... Unpacking lcms2 (2.6-1.11) ... Selecting previously unselected package libgusb. Preparing to unpack .../libgusb_0.1.6-3.20_i386.uhu ... Unpacking libgusb (0.1.6-3.20) ... Selecting previously unselected package colord. Preparing to unpack .../colord_1.2.1-2.5_i386.uhu ... Unpacking colord (1.2.1-2.5) ... Selecting previously unselected package cups. Preparing to unpack .../cups_1.7.3-1.7_i386.uhu ... Unpacking cups (1.7.3-1.7) ... Selecting previously unselected package icu. Preparing to unpack .../icu_51.2-2.14_i386.uhu ... Unpacking icu (51.2-2.14) ... Selecting previously unselected package harfbuzz. Preparing to unpack .../harfbuzz_0.9.29-1.8_i386.uhu ... Unpacking harfbuzz (0.9.29-1.8) ... Selecting previously unselected package icon-theme-hicolor. Preparing to unpack .../icon-theme-hicolor_0.13-1.6_i386.uhu ... Unpacking icon-theme-hicolor (0.13-1.6) ... Selecting previously unselected package libxcomposite. Preparing to unpack .../libxcomposite_0.4.4-2.16_i386.uhu ... Unpacking libxcomposite (0.4.4-2.16) ... Selecting previously unselected package libxfixes. Preparing to unpack .../libxfixes_5.0.1-1.16_i386.uhu ... Unpacking libxfixes (5.0.1-1.16) ... Selecting previously unselected package libxinerama. Preparing to unpack .../libxinerama_1.1.3-1.16_i386.uhu ... Unpacking libxinerama (1.1.3-1.16) ... Selecting previously unselected package libxft. Preparing to unpack .../libxft_2.3.1-4.17_i386.uhu ... Unpacking libxft (2.3.1-4.17) ... Selecting previously unselected package pango. Preparing to unpack .../pango_1.36.5-1.5_i386.uhu ... Unpacking pango (1.36.5-1.5) ... Selecting previously unselected package shared-mime-info. Preparing to unpack .../shared-mime-info_1.3-1.9_i386.uhu ... Unpacking shared-mime-info (1.3-1.9) ... Selecting previously unselected package gtk2. Preparing to unpack .../gtk2_2.24.24-1.5_i386.uhu ... Unpacking gtk2 (2.24.24-1.5) ... Selecting previously unselected package libxcursor. Preparing to unpack .../libxcursor_1.1.14-1.16_i386.uhu ... Unpacking libxcursor (1.1.14-1.16) ... Selecting previously unselected package libxdamage. Preparing to unpack .../libxdamage_1.1.4-1.16_i386.uhu ... Unpacking libxdamage (1.1.4-1.16) ... Selecting previously unselected package libxrandr. Preparing to unpack .../libxrandr_1.4.2-1.16_i386.uhu ... Unpacking libxrandr (1.4.2-1.16) ... Selecting previously unselected package gtk. Preparing to unpack .../gtk_3.12.2-1.7_i386.uhu ... Unpacking gtk (3.12.2-1.7) ... Selecting previously unselected package libdaemon. Preparing to unpack .../libdaemon_0.14-3.16_i386.uhu ... Unpacking libdaemon (0.14-3.16) ... Selecting previously unselected package avahi. Preparing to unpack .../avahi_0.6.31-7.9_i386.uhu ... Unpacking avahi (0.6.31-7.9) ... Selecting previously unselected package libpng-dev. Preparing to unpack .../libpng-dev_1.6.10-2.6_i386.uhu ... Unpacking libpng-dev (1.6.10-2.6) ... Selecting previously unselected package freetype2-dev. Preparing to unpack .../freetype2-dev_2.5.3-2.6_i386.uhu ... Unpacking freetype2-dev (2.5.3-2.6) ... Selecting previously unselected package fontconfig-dev. Preparing to unpack .../fontconfig-dev_2.11.1-1.11_i386.uhu ... Unpacking fontconfig-dev (2.11.1-1.11) ... Selecting previously unselected package x.org-util-macros. Preparing to unpack .../x.org-util-macros_1.17.1-1.17_i386.uhu ... Unpacking x.org-util-macros (1.17.1-1.17) ... Selecting previously unselected package x.org-proto-dev. Preparing to unpack .../x.org-proto-dev_7.7.1-3.14_i386.uhu ... Unpacking x.org-proto-dev (7.7.1-3.14) ... Selecting previously unselected package libxau-dev. Preparing to unpack .../libxau-dev_1.0.8-1.16_i386.uhu ... Unpacking libxau-dev (1.0.8-1.16) ... Selecting previously unselected package libxdmcp-dev. Preparing to unpack .../libxdmcp-dev_1.1.1-2.16_i386.uhu ... Unpacking libxdmcp-dev (1.1.1-2.16) ... Selecting previously unselected package libxcb-dev. Preparing to unpack .../libxcb-dev_1.10-1.14_i386.uhu ... Unpacking libxcb-dev (1.10-1.14) ... Selecting previously unselected package libx11-dev. Preparing to unpack .../libx11-dev_1.6.2-3.2_i386.uhu ... Unpacking libx11-dev (1.6.2-3.2) ... Selecting previously unselected package libxext-dev. Preparing to unpack .../libxext-dev_1.3.2-3.2_i386.uhu ... Unpacking libxext-dev (1.3.2-3.2) ... Selecting previously unselected package libxrender-dev. Preparing to unpack .../libxrender-dev_0.9.8-1.16_i386.uhu ... Unpacking libxrender-dev (0.9.8-1.16) ... Selecting previously unselected package pixman-dev. Preparing to unpack .../pixman-dev_0.32.4-1.15_i386.uhu ... Unpacking pixman-dev (0.32.4-1.15) ... Selecting previously unselected package cairo-dev. Preparing to unpack .../cairo-dev_1.12.16-1.21_i386.uhu ... Unpacking cairo-dev (1.12.16-1.21) ... Selecting previously unselected package gdk-pixbuf-dev. Preparing to unpack .../gdk-pixbuf-dev_2.30.8-1.8_i386.uhu ... Unpacking gdk-pixbuf-dev (2.30.8-1.8) ... Selecting previously unselected package icu-dev. Preparing to unpack .../icu-dev_51.2-2.14_i386.uhu ... Unpacking icu-dev (51.2-2.14) ... Selecting previously unselected package harfbuzz-dev. Preparing to unpack .../harfbuzz-dev_0.9.29-1.8_i386.uhu ... Unpacking harfbuzz-dev (0.9.29-1.8) ... Selecting previously unselected package libxfixes-dev. Preparing to unpack .../libxfixes-dev_5.0.1-1.16_i386.uhu ... Unpacking libxfixes-dev (5.0.1-1.16) ... Selecting previously unselected package libxcomposite-dev. Preparing to unpack .../libxcomposite-dev_0.4.4-2.16_i386.uhu ... Unpacking libxcomposite-dev (0.4.4-2.16) ... Selecting previously unselected package libxcursor-dev. Preparing to unpack .../libxcursor-dev_1.1.14-1.16_i386.uhu ... Unpacking libxcursor-dev (1.1.14-1.16) ... Selecting previously unselected package libxdamage-dev. Preparing to unpack .../libxdamage-dev_1.1.4-1.16_i386.uhu ... Unpacking libxdamage-dev (1.1.4-1.16) ... Selecting previously unselected package libxi-dev. Preparing to unpack .../libxi-dev_1.7.2-1.16_i386.uhu ... Unpacking libxi-dev (1.7.2-1.16) ... Selecting previously unselected package libxinerama-dev. Preparing to unpack .../libxinerama-dev_1.1.3-1.16_i386.uhu ... Unpacking libxinerama-dev (1.1.3-1.16) ... Selecting previously unselected package libxrandr-dev. Preparing to unpack .../libxrandr-dev_1.4.2-1.16_i386.uhu ... Unpacking libxrandr-dev (1.4.2-1.16) ... Selecting previously unselected package libxft-dev. Preparing to unpack .../libxft-dev_2.3.1-4.17_i386.uhu ... Unpacking libxft-dev (2.3.1-4.17) ... Selecting previously unselected package pango-dev. Preparing to unpack .../pango-dev_1.36.5-1.5_i386.uhu ... Unpacking pango-dev (1.36.5-1.5) ... Selecting previously unselected package gtk-dev. Preparing to unpack .../gtk-dev_3.12.2-1.7_i386.uhu ... Unpacking gtk-dev (3.12.2-1.7) ... Selecting previously unselected package gtk2-dev. Preparing to unpack .../gtk2-dev_2.24.24-1.5_i386.uhu ... Unpacking gtk2-dev (2.24.24-1.5) ... Selecting previously unselected package libglade2. Preparing to unpack .../libglade2_2.6.4-3.14_i386.uhu ... Unpacking libglade2 (2.6.4-3.14) ... Selecting previously unselected package gtk2-sharp. Preparing to unpack .../gtk2-sharp_2.12.11-3.14_i386.uhu ... Unpacking gtk2-sharp (2.12.11-3.14) ... Selecting previously unselected package avahi-dev. Preparing to unpack .../avahi-dev_0.6.31-7.9_i386.uhu ... Unpacking avahi-dev (0.6.31-7.9) ... Selecting previously unselected package cdparanoia. Preparing to unpack .../cdparanoia_10.2-3.11_i386.uhu ... Unpacking cdparanoia (10.2-3.11) ... Selecting previously unselected package dbus-glib-dev. Preparing to unpack .../dbus-glib-dev_0.102-2.2_i386.uhu ... Unpacking dbus-glib-dev (0.102-2.2) ... Selecting previously unselected package gconf2. Preparing to unpack .../gconf2_3.2.6-3.16_i386.uhu ... Unpacking gconf2 (3.2.6-3.16) ... Selecting previously unselected package gconf2-dev. Preparing to unpack .../gconf2-dev_3.2.6-3.16_i386.uhu ... Unpacking gconf2-dev (3.2.6-3.16) ... Selecting previously unselected package libxslt. Preparing to unpack .../libxslt_1.1.28-2.17_i386.uhu ... Unpacking libxslt (1.1.28-2.17) ... Selecting previously unselected package gnome-doc-utils. Preparing to unpack .../gnome-doc-utils_0.20.10-2.14_i386.uhu ... Unpacking gnome-doc-utils (0.20.10-2.14) ... Selecting previously unselected package gnome2-vfs. Preparing to unpack .../gnome2-vfs_2.24.4-2.18_i386.uhu ... Unpacking gnome2-vfs (2.24.4-2.18) ... Selecting previously unselected package gnome2-vfs-dev. Preparing to unpack .../gnome2-vfs-dev_2.24.4-2.18_i386.uhu ... Unpacking gnome2-vfs-dev (2.24.4-2.18) ... Selecting previously unselected package gstreamer0.10. Preparing to unpack .../gstreamer0.10_0.10.36-4.6_i386.uhu ... Unpacking gstreamer0.10 (0.10.36-4.6) ... Selecting previously unselected package libogg. Preparing to unpack .../libogg_1.3.2-1.7_i386.uhu ... Unpacking libogg (1.3.2-1.7) ... Selecting previously unselected package libtheora. Preparing to unpack .../libtheora_1.1.1-2.17_i386.uhu ... Unpacking libtheora (1.1.1-2.17) ... Selecting previously unselected package libvisual. Preparing to unpack .../libvisual_0.4.0-2.15_i386.uhu ... Unpacking libvisual (0.4.0-2.15) ... Selecting previously unselected package libvorbis. Preparing to unpack .../libvorbis_1.3.4-1.8_i386.uhu ... Unpacking libvorbis (1.3.4-1.8) ... Selecting previously unselected package libxv. Preparing to unpack .../libxv_1.0.10-1.16_i386.uhu ... Unpacking libxv (1.0.10-1.16) ... Selecting previously unselected package gst0.10-plugins-base. Preparing to unpack .../gst0.10-plugins-base_0.10.36-5.6_i386.uhu ... Unpacking gst0.10-plugins-base (0.10.36-5.6) ... Selecting previously unselected package libxml2-dev. Preparing to unpack .../libxml2-dev_2.9.1-2.2_i386.uhu ... Unpacking libxml2-dev (2.9.1-2.2) ... Selecting previously unselected package gstreamer0.10-dev. Preparing to unpack .../gstreamer0.10-dev_0.10.36-4.6_i386.uhu ... Unpacking gstreamer0.10-dev (0.10.36-4.6) ... Selecting previously unselected package gst0.10-plugins-base-dev. Preparing to unpack .../gst0.10-plugins-base-dev_0.10.36-5.6_i386.uhu ... Unpacking gst0.10-plugins-base-dev (0.10.36-5.6) ... Selecting previously unselected package libgnome-media-profiles. Preparing to unpack .../libgnome-media-profiles_3.0.0-3.15_i386.uhu ... Unpacking libgnome-media-profiles (3.0.0-3.15) ... Selecting previously unselected package libgnome-media-profiles-dev. Preparing to unpack .../libgnome-media-profiles-dev_3.0.0-3.15_i386.uhu ... Unpacking libgnome-media-profiles-dev (3.0.0-3.15) ... Selecting previously unselected package lirc. Preparing to unpack .../lirc_0.9.0-9.7_i386.uhu ... Unpacking lirc (0.9.0-9.7) ... Selecting previously unselected package lirc-dev. Preparing to unpack .../lirc-dev_0.9.0-9.7_i386.uhu ... Unpacking lirc-dev (0.9.0-9.7) ... Selecting previously unselected package perl-xml-parser. Preparing to unpack .../perl-xml-parser_2.41-2.18_i386.uhu ... Unpacking perl-xml-parser (2.41-2.18) ... Setting up dbus (1.8.4-2.2) ... Setting up dbus-glib (0.102-2.2) ... Setting up freetype2 (2.5.3-2.6) ... Setting up js17 (17.0.0-2.2) ... Setting up libusb (1.0.18-2.5) ... Setting up libxml2 (2.9.1-2.2) ... Setting up polkit (0.112-4.6) ... Setting up gc (7.2-2.17) ... Setting up libunistring (0.9.3-3.2) ... Setting up guile (2.0.11-4.6) ... Setting up libtasn1 (3.6-2.7) ... Setting up nettle (2.7.1-2.6) ... Setting up p11-kit (0.20.2-3.3) ... Setting up trousers (0.3.13-3.7) ... Setting up gnutls (3.3.5-1.3) ... Setting up libice (1.0.9-2.2) ... Setting up libjpeg (9a-3.2) ... Setting up libsm (1.2.2-2.2) ... Setting up libtiff (4.0.3-3.2) ... Setting up alsa-lib (1.0.28-1.6) ... Setting up libxau (1.0.8-1.16) ... Setting up libxdmcp (1.1.1-2.16) ... Setting up libxcb (1.10-1.14) ... Setting up libx11 (1.6.2-3.2) ... Setting up libxext (1.3.2-3.2) ... Setting up libxi (1.7.2-1.16) ... Setting up libxtst (1.2.2-1.16) ... Setting up at-spi2-core (2.12.0-1.12) ... Setting up atk (2.12.0-1.12) ... Setting up at-spi2-atk (2.12.1-1.10) ... Setting up dbus-dev (1.8.4-2.2) ... Setting up libffi-dev (3.0.13-2.15) ... Setting up pcre-dev (8.35-1.5) ... Setting up glib-dev (2.40.0-1.12) ... Setting up at-spi2-core-dev (2.12.0-1.12) ... Setting up at-spi2-atk-dev (2.12.1-1.10) ... Setting up atk-dev (2.12.0-1.12) ... Setting up fontconfig (2.11.1-1.11) ... Setting up libxrender (0.9.8-1.16) ... Setting up pixman (0.32.4-1.15) ... Setting up cairo (1.12.16-1.21) ... Setting up jasper (1.900.1-3.45) ... Setting up gdk-pixbuf (2.30.8-1.8) ... Setting up lcms2 (2.6-1.11) ... Setting up libgusb (0.1.6-3.20) ... Setting up colord (1.2.1-2.5) ... Setting up icu (51.2-2.14) ... Setting up harfbuzz (0.9.29-1.8) ... Setting up icon-theme-hicolor (0.13-1.6) ... Setting up libxcomposite (0.4.4-2.16) ... Setting up libxfixes (5.0.1-1.16) ... Setting up libxinerama (1.1.3-1.16) ... Setting up libxft (2.3.1-4.17) ... Setting up pango (1.36.5-1.5) ... Setting up shared-mime-info (1.3-1.9) ... Setting up gtk2 (2.24.24-1.5) ... Setting up libxcursor (1.1.14-1.16) ... Setting up libxdamage (1.1.4-1.16) ... Setting up libxrandr (1.4.2-1.16) ... Setting up libdaemon (0.14-3.16) ... Setting up libpng-dev (1.6.10-2.6) ... Setting up freetype2-dev (2.5.3-2.6) ... Setting up fontconfig-dev (2.11.1-1.11) ... Setting up x.org-util-macros (1.17.1-1.17) ... Setting up x.org-proto-dev (7.7.1-3.14) ... Setting up libxau-dev (1.0.8-1.16) ... Setting up libxdmcp-dev (1.1.1-2.16) ... Setting up libxcb-dev (1.10-1.14) ... Setting up libx11-dev (1.6.2-3.2) ... Setting up libxext-dev (1.3.2-3.2) ... Setting up libxrender-dev (0.9.8-1.16) ... Setting up pixman-dev (0.32.4-1.15) ... Setting up cairo-dev (1.12.16-1.21) ... Setting up gdk-pixbuf-dev (2.30.8-1.8) ... Setting up icu-dev (51.2-2.14) ... Setting up harfbuzz-dev (0.9.29-1.8) ... Setting up libxfixes-dev (5.0.1-1.16) ... Setting up libxcomposite-dev (0.4.4-2.16) ... Setting up libxcursor-dev (1.1.14-1.16) ... Setting up libxdamage-dev (1.1.4-1.16) ... Setting up libxi-dev (1.7.2-1.16) ... Setting up libxinerama-dev (1.1.3-1.16) ... Setting up libxrandr-dev (1.4.2-1.16) ... Setting up libxft-dev (2.3.1-4.17) ... Setting up pango-dev (1.36.5-1.5) ... Setting up gtk2-dev (2.24.24-1.5) ... Setting up libglade2 (2.6.4-3.14) ... Setting up gtk2-sharp (2.12.11-3.14) ... Setting up cdparanoia (10.2-3.11) ... Setting up dbus-glib-dev (0.102-2.2) ... Setting up gconf2 (3.2.6-3.16) ... Setting up gconf2-dev (3.2.6-3.16) ... Setting up libxslt (1.1.28-2.17) ... Setting up gnome-doc-utils (0.20.10-2.14) ... Setting up gstreamer0.10 (0.10.36-4.6) ... Setting up libogg (1.3.2-1.7) ... Setting up libtheora (1.1.1-2.17) ... Setting up libvisual (0.4.0-2.15) ... Setting up libvorbis (1.3.4-1.8) ... Setting up libxv (1.0.10-1.16) ... Setting up libxml2-dev (2.9.1-2.2) ... Setting up gstreamer0.10-dev (0.10.36-4.6) ... Setting up lirc (0.9.0-9.7) ... Setting up lirc-dev (0.9.0-9.7) ... Setting up perl-xml-parser (2.41-2.18) ... Setting up avahi (0.6.31-7.9) ... Setting up cups (1.7.3-1.7) ... Setting up gtk (3.12.2-1.7) ... Setting up gtk-dev (3.12.2-1.7) ... Setting up avahi-dev (0.6.31-7.9) ... Setting up gnome2-vfs (2.24.4-2.18) ... Setting up gnome2-vfs-dev (2.24.4-2.18) ... Setting up gst0.10-plugins-base (0.10.36-5.6) ... Setting up gst0.10-plugins-base-dev (0.10.36-5.6) ... Setting up libgnome-media-profiles (3.0.0-3.15) ... Setting up libgnome-media-profiles-dev (3.0.0-3.15) ... Running `/sbin/uhu-pkg postinst +' ... Generating MIME cache for desktop files ... Running fc-cache ... Installing gconf schemas ... (gconftool-2:22375): GConf-WARNING **: Client failed to connect to the D-BUS daemon: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11 (gconftool-2:22702): GConf-WARNING **: Client failed to connect to the D-BUS daemon: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11 (gconftool-2:23267): GConf-WARNING **: Client failed to connect to the D-BUS daemon: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11 (gconftool-2:23599): GConf-WARNING **: Client failed to connect to the D-BUS daemon: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11 (gconftool-2:23635): GConf-WARNING **: Client failed to connect to the D-BUS daemon: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11 (gconftool-2:23699): GConf-WARNING **: Client failed to connect to the D-BUS daemon: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11 Querying GDK pixbuf loaders ... Querying GIO modules ... Compiling Glib schemas ... Updating icon cache ... Querying GTK3 input methods ... Running ldconfig ... Generating shared MIME database ... Reload systemd unit files ...Running in chroot, ignoring request. Restart systemd-modules-load service ...Running in chroot, ignoring request. dpkg: warning: obsolete '--forget-old-unavail' option; unavailable packages are automatically cleaned up Takarítás... Chroot rendszer OK  , ccache , forrás OK  Megyünk a chroot alá, uhubuild-build indul. Building gnomeradio-1.8-6 for distribution UHU Linux dev. Target binary packages: gnomeradio. acquire... gnomeradio-1.8/ gnomeradio-1.8/po/ gnomeradio-1.8/po/ChangeLog gnomeradio-1.8/po/Makefile.in.in gnomeradio-1.8/po/POTFILES.in gnomeradio-1.8/po/ar.po gnomeradio-1.8/po/am.po gnomeradio-1.8/po/az.po gnomeradio-1.8/po/be.po gnomeradio-1.8/po/bg.po gnomeradio-1.8/po/ca.po gnomeradio-1.8/po/cs.po gnomeradio-1.8/po/da.po gnomeradio-1.8/po/de.po gnomeradio-1.8/po/dz.po gnomeradio-1.8/po/en_CA.po gnomeradio-1.8/po/en_GB.po gnomeradio-1.8/po/es.po gnomeradio-1.8/po/eu.po gnomeradio-1.8/po/fi.po gnomeradio-1.8/po/fr.po gnomeradio-1.8/po/he.po gnomeradio-1.8/po/hr.po gnomeradio-1.8/po/hu.po gnomeradio-1.8/po/it.po gnomeradio-1.8/po/ja.po gnomeradio-1.8/po/lv.po gnomeradio-1.8/po/mk.po gnomeradio-1.8/po/ml.po gnomeradio-1.8/po/mn.po gnomeradio-1.8/po/ms.po gnomeradio-1.8/po/nb.po gnomeradio-1.8/po/nl.po gnomeradio-1.8/po/oc.po gnomeradio-1.8/po/pa.po gnomeradio-1.8/po/pl.po gnomeradio-1.8/po/pt.po gnomeradio-1.8/po/pt_BR.po gnomeradio-1.8/po/ru.po gnomeradio-1.8/po/rw.po gnomeradio-1.8/po/sk.po gnomeradio-1.8/po/sr.po gnomeradio-1.8/po/sr@Latn.po gnomeradio-1.8/po/sv.po gnomeradio-1.8/po/tr.po gnomeradio-1.8/po/uk.po gnomeradio-1.8/po/vi.po gnomeradio-1.8/po/zh_CN.po gnomeradio-1.8/po/zh_TW.po gnomeradio-1.8/README gnomeradio-1.8/configure.in gnomeradio-1.8/aclocal.m4 gnomeradio-1.8/Makefile.am gnomeradio-1.8/Makefile.in gnomeradio-1.8/config.h.in gnomeradio-1.8/gnomeradio.spec.in gnomeradio-1.8/configure gnomeradio-1.8/AUTHORS gnomeradio-1.8/COPYING gnomeradio-1.8/ChangeLog gnomeradio-1.8/INSTALL gnomeradio-1.8/NEWS gnomeradio-1.8/TODO gnomeradio-1.8/config.guess gnomeradio-1.8/config.sub gnomeradio-1.8/depcomp gnomeradio-1.8/install-sh gnomeradio-1.8/ltmain.sh gnomeradio-1.8/missing gnomeradio-1.8/mkinstalldirs gnomeradio-1.8/intltool-update.in gnomeradio-1.8/intltool-merge.in gnomeradio-1.8/intltool-extract.in gnomeradio-1.8/README.lirc gnomeradio-1.8/README.recording gnomeradio-1.8/gnomeradio.spec gnomeradio-1.8/gnome-doc-utils.make gnomeradio-1.8/help/ gnomeradio-1.8/help/Makefile.am gnomeradio-1.8/help/Makefile.in gnomeradio-1.8/help/C/ gnomeradio-1.8/help/C/legal.xml gnomeradio-1.8/help/C/gnomeradio.xml gnomeradio-1.8/help/C/figures/ gnomeradio-1.8/help/C/figures/freq-controls.png gnomeradio-1.8/help/C/figures/misc-controls.png gnomeradio-1.8/help/C/figures/presets-box.png gnomeradio-1.8/help/C/figures/recording-general.png gnomeradio-1.8/help/C/figures/recording-mp3.png gnomeradio-1.8/help/C/figures/recording-wav.png gnomeradio-1.8/help/C/figures/recording_status.png gnomeradio-1.8/help/C/figures/settings-misc.png gnomeradio-1.8/help/C/figures/settings-presets.png gnomeradio-1.8/help/C/figures/status-window.png gnomeradio-1.8/help/C/figures/volume-controls.png gnomeradio-1.8/help/es/ gnomeradio-1.8/help/es/gnomeradio.xml gnomeradio-1.8/help/es/es.po gnomeradio-1.8/help/fr/ gnomeradio-1.8/help/fr/gnomeradio.xml gnomeradio-1.8/help/fr/fr.po gnomeradio-1.8/help/fr/figures/ gnomeradio-1.8/help/fr/figures/presets-box.png gnomeradio-1.8/help/fr/figures/recording_status.png gnomeradio-1.8/help/fr/figures/settings-misc.png gnomeradio-1.8/help/oc/ gnomeradio-1.8/help/oc/gnomeradio.xml gnomeradio-1.8/help/oc/oc.po gnomeradio-1.8/help/sv/ gnomeradio-1.8/help/sv/gnomeradio.xml gnomeradio-1.8/help/sv/sv.po gnomeradio-1.8/help/sv/figures/ gnomeradio-1.8/help/sv/figures/recording_status.png gnomeradio-1.8/help/gnomeradio.omf.in gnomeradio-1.8/data/ gnomeradio-1.8/data/Makefile.am gnomeradio-1.8/data/Makefile.in gnomeradio-1.8/data/gnomeradio.desktop gnomeradio-1.8/data/gnomeradio.desktop.in gnomeradio-1.8/data/gnomeradio.schemas gnomeradio-1.8/data/gnomeradio.schemas.in gnomeradio-1.8/data/example.lircrc gnomeradio-1.8/data/icons/ gnomeradio-1.8/data/icons/Makefile.am gnomeradio-1.8/data/icons/Makefile.in gnomeradio-1.8/data/icons/16x16/ gnomeradio-1.8/data/icons/16x16/Makefile.am gnomeradio-1.8/data/icons/16x16/Makefile.in gnomeradio-1.8/data/icons/16x16/gnomeradio.png gnomeradio-1.8/data/icons/22x22/ gnomeradio-1.8/data/icons/22x22/Makefile.am gnomeradio-1.8/data/icons/22x22/Makefile.in gnomeradio-1.8/data/icons/22x22/gnomeradio.png gnomeradio-1.8/data/icons/24x24/ gnomeradio-1.8/data/icons/24x24/Makefile.am gnomeradio-1.8/data/icons/24x24/Makefile.in gnomeradio-1.8/data/icons/24x24/gnomeradio.png gnomeradio-1.8/data/icons/32x32/ gnomeradio-1.8/data/icons/32x32/Makefile.am gnomeradio-1.8/data/icons/32x32/Makefile.in gnomeradio-1.8/data/icons/32x32/gnomeradio.png gnomeradio-1.8/data/icons/48x48/ gnomeradio-1.8/data/icons/48x48/Makefile.am gnomeradio-1.8/data/icons/48x48/Makefile.in gnomeradio-1.8/data/icons/48x48/gnomeradio.png gnomeradio-1.8/data/icons/scalable/ gnomeradio-1.8/data/icons/scalable/Makefile.am gnomeradio-1.8/data/icons/scalable/Makefile.in gnomeradio-1.8/data/icons/scalable/gnomeradio.svg gnomeradio-1.8/data/pixmaps/ gnomeradio-1.8/data/pixmaps/Makefile.am gnomeradio-1.8/data/pixmaps/Makefile.in gnomeradio-1.8/data/pixmaps/digits.xpm gnomeradio-1.8/data/pixmaps/freq_up.xpm gnomeradio-1.8/data/pixmaps/signal.xpm gnomeradio-1.8/data/pixmaps/vol_down.xpm gnomeradio-1.8/data/pixmaps/freq_down.xpm gnomeradio-1.8/data/pixmaps/stereo.xpm gnomeradio-1.8/data/pixmaps/vol_up.xpm gnomeradio-1.8/src/ gnomeradio-1.8/src/Makefile.am gnomeradio-1.8/src/Makefile.in gnomeradio-1.8/src/bacon-volume.h gnomeradio-1.8/src/gui.h gnomeradio-1.8/src/lirc.h gnomeradio-1.8/src/prefs.h gnomeradio-1.8/src/radio.h gnomeradio-1.8/src/rec_tech.h gnomeradio-1.8/src/record.h gnomeradio-1.8/src/tech.h gnomeradio-1.8/src/trayicon.h gnomeradio-1.8/src/v4l1.h gnomeradio-1.8/src/v4l2.h gnomeradio-1.8/src/bacon-volume.c gnomeradio-1.8/src/gui.c gnomeradio-1.8/src/lirc.c gnomeradio-1.8/src/prefs.c gnomeradio-1.8/src/radio.c gnomeradio-1.8/src/rec_tech.c gnomeradio-1.8/src/record.c gnomeradio-1.8/src/tech.c gnomeradio-1.8/src/trayicon.c gnomeradio-1.8/src/v4l1.c gnomeradio-1.8/src/v4l2.c +++ Applying patch: /var/uhubuild/work/.src/patches/10-gnomeradio-v4l2.patch patching file src/Makefile.am patching file src/Makefile.in patching file src/prefs.c patching file src/radio.c +++ Applying patch: /var/uhubuild/work/.src/patches/20-gnomeradio-ld.patch patching file src/Makefile.am patching file src/Makefile.in +++ Applying patch: /var/uhubuild/work/.src/patches/25-gnomeradio-crash.patch patching file ChangeLog patching file src/gui.c patching file src/prefs.c +++ Applying patch: /var/uhubuild/work/.src/patches/30-gnomeradio-gnome-3.0.patch patching file configure patching file src/prefs.c patching file src/rec_tech.c +++ Applying patch: /var/uhubuild/work/.src/patches/40-gnomeradio-gtk.patch patching file src/bacon-volume.c patching file src/gui.c patching file src/prefs.c patching file src/record.c patching file src/trayicon.c +++ Applying patch: /var/uhubuild/work/.src/patches/50-gnomeradio-1.8-nogtk2.patch patching file config.h.in patching file configure patching file src/bacon-volume.c patching file src/bacon-volume.h patching file src/gui.c patching file src/lirc.c patching file src/prefs.c patching file src/prefs.h patching file src/record.c patching file src/record.h patching file src/rec_tech.c patching file src/trayicon.c +++ Applying patch: /var/uhubuild/work/.src/patches/60-menu.patch patching file data/gnomeradio.desktop.in ccache-extract... compile... + ub_compile ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --build=i686-uhu-linux --host=i686-uhu-linux --disable-static CFLAGS=-O2 -march=i686 -mtune=generic --disable-schemas-install --disable-scrollkeeper checking for a BSD-compatible install... /bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether to enable maintainer-specific portions of Makefiles... no checking for style of include used by make... GNU checking for i686-uhu-linux-gcc... i686-uhu-linux-gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether i686-uhu-linux-gcc accepts -g... yes checking for i686-uhu-linux-gcc option to accept ISO C89... none needed checking dependency style of i686-uhu-linux-gcc... gcc3 checking for intltool >= 0.21... 0.37.1 found checking for xgettext... /usr/bin/xgettext checking for msgmerge... /usr/bin/msgmerge checking for msgfmt... /usr/bin/msgfmt checking for perl... /usr/bin/perl checking for XML::Parser... ok checking build system type... i686-uhu-linux-gnu checking host system type... i686-uhu-linux-gnu checking for a sed that does not truncate output... /bin/sed checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ld used by i686-uhu-linux-gcc... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for /usr/bin/ld option to reload object files... -r checking for BSD-compatible nm... /usr/bin/nm -B checking whether ln -s works... yes checking how to recognize dependent libraries... pass_all checking how to run the C preprocessor... i686-uhu-linux-gcc -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking dlfcn.h usability... yes checking dlfcn.h presence... yes checking for dlfcn.h... yes checking for i686-uhu-linux-g++... i686-uhu-linux-g++ checking whether we are using the GNU C++ compiler... yes checking whether i686-uhu-linux-g++ accepts -g... yes checking dependency style of i686-uhu-linux-g++... gcc3 checking how to run the C++ preprocessor... i686-uhu-linux-g++ -E checking for i686-uhu-linux-g77... no checking for i686-uhu-linux-xlf... no checking for i686-uhu-linux-f77... no checking for i686-uhu-linux-frt... no checking for i686-uhu-linux-pgf77... no checking for i686-uhu-linux-cf77... no checking for i686-uhu-linux-fort77... no checking for i686-uhu-linux-fl32... no checking for i686-uhu-linux-af77... no checking for i686-uhu-linux-xlf90... no checking for i686-uhu-linux-f90... no checking for i686-uhu-linux-pgf90... no checking for i686-uhu-linux-pghpf... no checking for i686-uhu-linux-epcf90... no checking for i686-uhu-linux-gfortran... no checking for i686-uhu-linux-g95... no checking for i686-uhu-linux-xlf95... no checking for i686-uhu-linux-f95... no checking for i686-uhu-linux-fort... no checking for i686-uhu-linux-ifort... no checking for i686-uhu-linux-ifc... no checking for i686-uhu-linux-efc... no checking for i686-uhu-linux-pgf95... no checking for i686-uhu-linux-lf95... no checking for i686-uhu-linux-ftn... no checking for g77... no checking for xlf... no checking for f77... no checking for frt... no checking for pgf77... no checking for cf77... no checking for fort77... no checking for fl32... no checking for af77... no checking for xlf90... no checking for f90... no checking for pgf90... no checking for pghpf... no checking for epcf90... no checking for gfortran... no checking for g95... no checking for xlf95... no checking for f95... no checking for fort... no checking for ifort... no checking for ifc... no checking for efc... no checking for pgf95... no checking for lf95... no checking for ftn... no checking whether we are using the GNU Fortran 77 compiler... no checking whether accepts -g... no checking the maximum length of command line arguments... 1572864 checking command to parse /usr/bin/nm -B output from i686-uhu-linux-gcc object... ok checking for objdir... .libs checking for i686-uhu-linux-ar... i686-uhu-linux-ar checking for i686-uhu-linux-ranlib... no checking for ranlib... ranlib checking for i686-uhu-linux-strip... no checking for strip... strip checking if i686-uhu-linux-gcc supports -fno-rtti -fno-exceptions... no checking for i686-uhu-linux-gcc option to produce PIC... -fPIC checking if i686-uhu-linux-gcc PIC flag -fPIC works... yes checking if i686-uhu-linux-gcc static flag -static works... yes checking if i686-uhu-linux-gcc supports -c -o file.o... yes checking whether the i686-uhu-linux-gcc linker (/usr/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... no configure: creating libtool appending configuration tag "CXX" to libtool checking for ld used by i686-uhu-linux-g++... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking whether the i686-uhu-linux-g++ linker (/usr/bin/ld) supports shared libraries... yes checking for i686-uhu-linux-g++ option to produce PIC... -fPIC checking if i686-uhu-linux-g++ PIC flag -fPIC works... yes checking if i686-uhu-linux-g++ static flag -static works... yes checking if i686-uhu-linux-g++ supports -c -o file.o... yes checking whether the i686-uhu-linux-g++ linker (/usr/bin/ld) supports shared libraries... yes checking dynamic linker characteristics... GNU/Linux ld.so (cached) (cached) checking how to hardcode library paths into programs... immediate appending configuration tag "F77" to libtool checking for library containing strerror... none required checking for i686-uhu-linux-gcc... (cached) i686-uhu-linux-gcc checking whether we are using the GNU C compiler... (cached) yes checking whether i686-uhu-linux-gcc accepts -g... (cached) yes checking for i686-uhu-linux-gcc option to accept ISO C89... (cached) none needed checking dependency style of i686-uhu-linux-gcc... (cached) gcc3 checking for a BSD-compatible install... /bin/install -c checking whether make sets $(MAKE)... (cached) 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) /usr/bin/msgfmt checking for dcgettext... yes checking if msgfmt accepts -c... yes checking for gmsgfmt... /usr/bin/msgfmt checking for xgettext... (cached) /usr/bin/xgettext checking for catalogs to be installed... ar am az be bg ca cs da de dz en_CA en_GB es eu fi fr he hr hu it ja lv mk ml mn ms nb nl oc pa pl pt pt_BR ru rw sk sr sr@Latn sv tr uk vi zh_CN zh_TW checking for i686-uhu-linux-pkg-config... no checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for GNOME... yes checking for GSTREAMER... yes checking for gconftool-2... /usr/bin/gconftool-2 Using config source xml:merged:/etc/gconf/gconf.xml.defaults for schema installation Using $(sysconfdir)/gconf/schemas as install directory for schema files checking for lirc_init in -llirc_client... yes configure: creating ./config.status config.status: creating gnomeradio.spec config.status: creating Makefile config.status: creating src/Makefile config.status: creating po/Makefile.in config.status: creating data/Makefile config.status: creating data/pixmaps/Makefile config.status: creating data/icons/Makefile config.status: creating data/icons/16x16/Makefile config.status: creating data/icons/22x22/Makefile config.status: creating data/icons/24x24/Makefile config.status: creating data/icons/32x32/Makefile config.status: creating data/icons/48x48/Makefile config.status: creating data/icons/scalable/Makefile config.status: creating help/Makefile config.status: creating config.h config.status: executing depfiles commands config.status: executing intltool commands config.status: executing default-1 commands config.status: executing po/stamp-it commands make -j16 MAN1EXT=1 MAN2EXT=2 MAN3EXT=3 MAN4EXT=4 MAN5EXT=5 MAN6EXT=6 MAN7EXT=7 MAN8EXT=8 make all-recursive make[1]: Entering directory `/var/uhubuild/work/compile' Making all in help make[2]: Entering directory `/var/uhubuild/work/compile/help' if ! test -d es/; then mkdir es/; fi if ! test -d fr/; then mkdir fr/; fi if ! test -d oc/; then mkdir oc/; fi if ! test -d sv/; then mkdir sv/; fi if [ -f "C/gnomeradio.xml" ]; then d="../"; else d="/var/uhubuild/work/compile/help/"; fi; \ (cd es/ && \ `which xml2po` -e -p \ "${d}es/es.po" \ "${d}C/gnomeradio.xml" > gnomeradio.xml.tmp && \ cp gnomeradio.xml.tmp gnomeradio.xml && rm -f gnomeradio.xml.tmp) if [ -f "C/gnomeradio.xml" ]; then d="../"; else d="/var/uhubuild/work/compile/help/"; fi; \ (cd fr/ && \ `which xml2po` -e -p \ "${d}fr/fr.po" \ "${d}C/gnomeradio.xml" > gnomeradio.xml.tmp && \ cp gnomeradio.xml.tmp gnomeradio.xml && rm -f gnomeradio.xml.tmp) if [ -f "C/gnomeradio.xml" ]; then d="../"; else d="/var/uhubuild/work/compile/help/"; fi; \ (cd oc/ && \ `which xml2po` -e -p \ "${d}oc/oc.po" \ "${d}C/gnomeradio.xml" > gnomeradio.xml.tmp && \ cp gnomeradio.xml.tmp gnomeradio.xml && rm -f gnomeradio.xml.tmp) if [ -f "C/gnomeradio.xml" ]; then d="../"; else d="/var/uhubuild/work/compile/help/"; fi; \ (cd sv/ && \ `which xml2po` -e -p \ "${d}sv/sv.po" \ "${d}C/gnomeradio.xml" > gnomeradio.xml.tmp && \ cp gnomeradio.xml.tmp gnomeradio.xml && rm -f gnomeradio.xml.tmp) xsltproc -o gnomeradio-C.omf --stringparam db2omf.basename gnomeradio --stringparam db2omf.format 'docbook' --stringparam db2omf.dtd "-//OASIS//DTD DocBook XML V4.4//EN" --stringparam db2omf.lang C --stringparam db2omf.omf_dir "/usr/share/omf" --stringparam db2omf.help_dir "/usr/share/gnome/help" --stringparam db2omf.omf_in "/var/uhubuild/work/compile/help/gnomeradio.omf.in" `/usr/bin/pkg-config --variable db2omf gnome-doc-utils` C/gnomeradio.xml || { rm -f "gnomeradio-C.omf"; exit 1; } error : connection refused C/gnomeradio.xml:9: warning: failed to load external entity "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" ]> ^ xsltproc -o gnomeradio-sv.omf --stringparam db2omf.basename gnomeradio --stringparam db2omf.format 'docbook' --stringparam db2omf.dtd "-//OASIS//DTD DocBook XML V4.4//EN" --stringparam db2omf.lang sv --stringparam db2omf.omf_dir "/usr/share/omf" --stringparam db2omf.help_dir "/usr/share/gnome/help" --stringparam db2omf.omf_in "/var/uhubuild/work/compile/help/gnomeradio.omf.in" `/usr/bin/pkg-config --variable db2omf gnome-doc-utils` sv/gnomeradio.xml || { rm -f "gnomeradio-sv.omf"; exit 1; } error : connection refused sv/gnomeradio.xml:8: warning: failed to load external entity "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" ]> ^ xsltproc -o gnomeradio-oc.omf --stringparam db2omf.basename gnomeradio --stringparam db2omf.format 'docbook' --stringparam db2omf.dtd "-//OASIS//DTD DocBook XML V4.4//EN" --stringparam db2omf.lang oc --stringparam db2omf.omf_dir "/usr/share/omf" --stringparam db2omf.help_dir "/usr/share/gnome/help" --stringparam db2omf.omf_in "/var/uhubuild/work/compile/help/gnomeradio.omf.in" `/usr/bin/pkg-config --variable db2omf gnome-doc-utils` oc/gnomeradio.xml || { rm -f "gnomeradio-oc.omf"; exit 1; } error : connection refused oc/gnomeradio.xml:8: warning: failed to load external entity "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" ]> ^ xsltproc -o gnomeradio-es.omf --stringparam db2omf.basename gnomeradio --stringparam db2omf.format 'docbook' --stringparam db2omf.dtd "-//OASIS//DTD DocBook XML V4.4//EN" --stringparam db2omf.lang es --stringparam db2omf.omf_dir "/usr/share/omf" --stringparam db2omf.help_dir "/usr/share/gnome/help" --stringparam db2omf.omf_in "/var/uhubuild/work/compile/help/gnomeradio.omf.in" `/usr/bin/pkg-config --variable db2omf gnome-doc-utils` es/gnomeradio.xml || { rm -f "gnomeradio-es.omf"; exit 1; } xsltproc -o gnomeradio-fr.omf --stringparam db2omf.basename gnomeradio --stringparam db2omf.format 'docbook' --stringparam db2omf.dtd "-//OASIS//DTD DocBook XML V4.4//EN" --stringparam db2omf.lang fr --stringparam db2omf.omf_dir "/usr/share/omf" --stringparam db2omf.help_dir "/usr/share/gnome/help" --stringparam db2omf.omf_in "/var/uhubuild/work/compile/help/gnomeradio.omf.in" `/usr/bin/pkg-config --variable db2omf gnome-doc-utils` fr/gnomeradio.xml || { rm -f "gnomeradio-fr.omf"; exit 1; } error : connection refused es/gnomeradio.xml:8: warning: failed to load external entity "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" ]> ^ error : connection refused fr/gnomeradio.xml:8: warning: failed to load external entity "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" ]> ^ make[2]: Leaving directory `/var/uhubuild/work/compile/help' Making all in data make[2]: Entering directory `/var/uhubuild/work/compile/data' Making all in icons make[3]: Entering directory `/var/uhubuild/work/compile/data/icons' Making all in 16x16 make[4]: Entering directory `/var/uhubuild/work/compile/data/icons/16x16' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/var/uhubuild/work/compile/data/icons/16x16' Making all in 22x22 make[4]: Entering directory `/var/uhubuild/work/compile/data/icons/22x22' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/var/uhubuild/work/compile/data/icons/22x22' Making all in 24x24 make[4]: Entering directory `/var/uhubuild/work/compile/data/icons/24x24' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/var/uhubuild/work/compile/data/icons/24x24' Making all in 32x32 make[4]: Entering directory `/var/uhubuild/work/compile/data/icons/32x32' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/var/uhubuild/work/compile/data/icons/32x32' Making all in 48x48 make[4]: Entering directory `/var/uhubuild/work/compile/data/icons/48x48' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/var/uhubuild/work/compile/data/icons/48x48' Making all in scalable make[4]: Entering directory `/var/uhubuild/work/compile/data/icons/scalable' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/var/uhubuild/work/compile/data/icons/scalable' make[4]: Entering directory `/var/uhubuild/work/compile/data/icons' make[4]: Nothing to be done for `all-am'. make[4]: Leaving directory `/var/uhubuild/work/compile/data/icons' make[3]: Leaving directory `/var/uhubuild/work/compile/data/icons' Making all in pixmaps make[3]: Entering directory `/var/uhubuild/work/compile/data/pixmaps' make[3]: Nothing to be done for `all'. make[3]: Leaving directory `/var/uhubuild/work/compile/data/pixmaps' make[3]: Entering directory `/var/uhubuild/work/compile/data' LC_ALL=C ../intltool-merge -d -u -c ../po/.intltool-merge-cache ../po gnomeradio.desktop.in gnomeradio.desktop LC_ALL=C ../intltool-merge -s -u -c ../po/.intltool-merge-cache ../po gnomeradio.schemas.in gnomeradio.schemas Generating and caching the translation database Generating and caching the translation database Merging translations into gnomeradio.schemas. Merging translations into gnomeradio.desktop. make[3]: Leaving directory `/var/uhubuild/work/compile/data' make[2]: Leaving directory `/var/uhubuild/work/compile/data' Making all in po make[2]: Entering directory `/var/uhubuild/work/compile/po' file=`echo ar | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file ar.po file=`echo am | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file am.po file=`echo az | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file az.po file=`echo be | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file be.po file=`echo bg | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file bg.po file=`echo ca | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file ca.po file=`echo cs | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file cs.po file=`echo da | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file da.po file=`echo de | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file de.po file=`echo dz | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file dz.po file=`echo en_CA | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file en_CA.po file=`echo en_GB | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file en_GB.po file=`echo es | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file es.po file=`echo eu | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file eu.po file=`echo fi | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file fi.po file=`echo fr | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file fr.po file=`echo he | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file he.po file=`echo hr | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file hr.po file=`echo hu | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file hu.po file=`echo it | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file it.po file=`echo ja | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file ja.po file=`echo lv | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file lv.po file=`echo mk | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file mk.po file=`echo ml | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file ml.po file=`echo mn | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file mn.po file=`echo ms | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file ms.po file=`echo nb | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file nb.po file=`echo nl | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file nl.po file=`echo oc | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file oc.po file=`echo pa | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file pa.po file=`echo pl | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file pl.po file=`echo pt | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file pt.po file=`echo pt_BR | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file pt_BR.po file=`echo ru | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file ru.po file=`echo rw | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file rw.po file=`echo sk | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file sk.po file=`echo sr | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file sr.po file=`echo sr@Latn | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file sr@Latn.po file=`echo sv | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file sv.po file=`echo tr | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file tr.po file=`echo uk | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file uk.po file=`echo vi | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file vi.po file=`echo zh_CN | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file zh_CN.po file=`echo zh_TW | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file zh_TW.po make[2]: Leaving directory `/var/uhubuild/work/compile/po' Making all in src make[2]: Entering directory `/var/uhubuild/work/compile/src' if i686-uhu-linux-gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I/usr/include -pthread -I/usr/include/dbus-1.0 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -I/usr/include/libgnome-media-profiles-3.0 -I/usr/include/gconf/2 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/gstreamer-0.10 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libxml2 -DG_LOG_DOMAIN=\"gnomeradio\" -DGNOMELOCALEDIR=\""/usr/share/locale"\" -DDATADIR=\""/usr/share/"\" -DPREFIX=\""/usr/"\" -DLIBDIR=\""/usr/lib/"\" -DSYSCONFDIR=\""/etc/"\" -O2 -march=i686 -mtune=generic -MT bacon-volume.o -MD -MP -MF ".deps/bacon-volume.Tpo" -c -o bacon-volume.o bacon-volume.c; \ then mv -f ".deps/bacon-volume.Tpo" ".deps/bacon-volume.Po"; else rm -f ".deps/bacon-volume.Tpo"; exit 1; fi if i686-uhu-linux-gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I/usr/include -pthread -I/usr/include/dbus-1.0 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -I/usr/include/libgnome-media-profiles-3.0 -I/usr/include/gconf/2 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/gstreamer-0.10 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libxml2 -DG_LOG_DOMAIN=\"gnomeradio\" -DGNOMELOCALEDIR=\""/usr/share/locale"\" -DDATADIR=\""/usr/share/"\" -DPREFIX=\""/usr/"\" -DLIBDIR=\""/usr/lib/"\" -DSYSCONFDIR=\""/etc/"\" -O2 -march=i686 -mtune=generic -MT gui.o -MD -MP -MF ".deps/gui.Tpo" -c -o gui.o gui.c; \ then mv -f ".deps/gui.Tpo" ".deps/gui.Po"; else rm -f ".deps/gui.Tpo"; exit 1; fi if i686-uhu-linux-gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I/usr/include -pthread -I/usr/include/dbus-1.0 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -I/usr/include/libgnome-media-profiles-3.0 -I/usr/include/gconf/2 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/gstreamer-0.10 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libxml2 -DG_LOG_DOMAIN=\"gnomeradio\" -DGNOMELOCALEDIR=\""/usr/share/locale"\" -DDATADIR=\""/usr/share/"\" -DPREFIX=\""/usr/"\" -DLIBDIR=\""/usr/lib/"\" -DSYSCONFDIR=\""/etc/"\" -O2 -march=i686 -mtune=generic -MT lirc.o -MD -MP -MF ".deps/lirc.Tpo" -c -o lirc.o lirc.c; \ then mv -f ".deps/lirc.Tpo" ".deps/lirc.Po"; else rm -f ".deps/lirc.Tpo"; exit 1; fi if i686-uhu-linux-gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I/usr/include -pthread -I/usr/include/dbus-1.0 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -I/usr/include/libgnome-media-profiles-3.0 -I/usr/include/gconf/2 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/gstreamer-0.10 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libxml2 -DG_LOG_DOMAIN=\"gnomeradio\" -DGNOMELOCALEDIR=\""/usr/share/locale"\" -DDATADIR=\""/usr/share/"\" -DPREFIX=\""/usr/"\" -DLIBDIR=\""/usr/lib/"\" -DSYSCONFDIR=\""/etc/"\" -O2 -march=i686 -mtune=generic -MT prefs.o -MD -MP -MF ".deps/prefs.Tpo" -c -o prefs.o prefs.c; \ then mv -f ".deps/prefs.Tpo" ".deps/prefs.Po"; else rm -f ".deps/prefs.Tpo"; exit 1; fi if i686-uhu-linux-gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I/usr/include -pthread -I/usr/include/dbus-1.0 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -I/usr/include/libgnome-media-profiles-3.0 -I/usr/include/gconf/2 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/gstreamer-0.10 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libxml2 -DG_LOG_DOMAIN=\"gnomeradio\" -DGNOMELOCALEDIR=\""/usr/share/locale"\" -DDATADIR=\""/usr/share/"\" -DPREFIX=\""/usr/"\" -DLIBDIR=\""/usr/lib/"\" -DSYSCONFDIR=\""/etc/"\" -O2 -march=i686 -mtune=generic -MT radio.o -MD -MP -MF ".deps/radio.Tpo" -c -o radio.o radio.c; \ then mv -f ".deps/radio.Tpo" ".deps/radio.Po"; else rm -f ".deps/radio.Tpo"; exit 1; fi if i686-uhu-linux-gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I/usr/include -pthread -I/usr/include/dbus-1.0 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -I/usr/include/libgnome-media-profiles-3.0 -I/usr/include/gconf/2 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/gstreamer-0.10 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libxml2 -DG_LOG_DOMAIN=\"gnomeradio\" -DGNOMELOCALEDIR=\""/usr/share/locale"\" -DDATADIR=\""/usr/share/"\" -DPREFIX=\""/usr/"\" -DLIBDIR=\""/usr/lib/"\" -DSYSCONFDIR=\""/etc/"\" -O2 -march=i686 -mtune=generic -MT rec_tech.o -MD -MP -MF ".deps/rec_tech.Tpo" -c -o rec_tech.o rec_tech.c; \ then mv -f ".deps/rec_tech.Tpo" ".deps/rec_tech.Po"; else rm -f ".deps/rec_tech.Tpo"; exit 1; fi if i686-uhu-linux-gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I/usr/include -pthread -I/usr/include/dbus-1.0 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -I/usr/include/libgnome-media-profiles-3.0 -I/usr/include/gconf/2 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/gstreamer-0.10 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libxml2 -DG_LOG_DOMAIN=\"gnomeradio\" -DGNOMELOCALEDIR=\""/usr/share/locale"\" -DDATADIR=\""/usr/share/"\" -DPREFIX=\""/usr/"\" -DLIBDIR=\""/usr/lib/"\" -DSYSCONFDIR=\""/etc/"\" -O2 -march=i686 -mtune=generic -MT record.o -MD -MP -MF ".deps/record.Tpo" -c -o record.o record.c; \ then mv -f ".deps/record.Tpo" ".deps/record.Po"; else rm -f ".deps/record.Tpo"; exit 1; fi if i686-uhu-linux-gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I/usr/include -pthread -I/usr/include/dbus-1.0 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -I/usr/include/libgnome-media-profiles-3.0 -I/usr/include/gconf/2 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/gstreamer-0.10 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libxml2 -DG_LOG_DOMAIN=\"gnomeradio\" -DGNOMELOCALEDIR=\""/usr/share/locale"\" -DDATADIR=\""/usr/share/"\" -DPREFIX=\""/usr/"\" -DLIBDIR=\""/usr/lib/"\" -DSYSCONFDIR=\""/etc/"\" -O2 -march=i686 -mtune=generic -MT tech.o -MD -MP -MF ".deps/tech.Tpo" -c -o tech.o tech.c; \ then mv -f ".deps/tech.Tpo" ".deps/tech.Po"; else rm -f ".deps/tech.Tpo"; exit 1; fi if i686-uhu-linux-gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I/usr/include -pthread -I/usr/include/dbus-1.0 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -I/usr/include/libgnome-media-profiles-3.0 -I/usr/include/gconf/2 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/gstreamer-0.10 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libxml2 -DG_LOG_DOMAIN=\"gnomeradio\" -DGNOMELOCALEDIR=\""/usr/share/locale"\" -DDATADIR=\""/usr/share/"\" -DPREFIX=\""/usr/"\" -DLIBDIR=\""/usr/lib/"\" -DSYSCONFDIR=\""/etc/"\" -O2 -march=i686 -mtune=generic -MT trayicon.o -MD -MP -MF ".deps/trayicon.Tpo" -c -o trayicon.o trayicon.c; \ then mv -f ".deps/trayicon.Tpo" ".deps/trayicon.Po"; else rm -f ".deps/trayicon.Tpo"; exit 1; fi if i686-uhu-linux-gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I/usr/include -pthread -I/usr/include/dbus-1.0 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -I/usr/include/libgnome-media-profiles-3.0 -I/usr/include/gconf/2 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/gstreamer-0.10 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libxml2 -DG_LOG_DOMAIN=\"gnomeradio\" -DGNOMELOCALEDIR=\""/usr/share/locale"\" -DDATADIR=\""/usr/share/"\" -DPREFIX=\""/usr/"\" -DLIBDIR=\""/usr/lib/"\" -DSYSCONFDIR=\""/etc/"\" -O2 -march=i686 -mtune=generic -MT v4l2.o -MD -MP -MF ".deps/v4l2.Tpo" -c -o v4l2.o v4l2.c; \ then mv -f ".deps/v4l2.Tpo" ".deps/v4l2.Po"; else rm -f ".deps/v4l2.Tpo"; exit 1; fi record.c: In function 'record_status_window': record.c:113:2: warning: 'gtk_vbox_new' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtkvbox.h:61): Use 'gtk_box_new' instead [-Wdeprecated-declarations] vbox = gtk_vbox_new(FALSE, 5); ^ record.c:116:2: warning: 'gtk_table_new' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtktable.h:102): Use 'GtkGrid' instead [-Wdeprecated-declarations] table = gtk_table_new(3, 2, FALSE); ^ record.c:117:2: warning: 'gtk_table_set_row_spacings' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtktable.h:142): Use 'GtkGrid' instead [-Wdeprecated-declarations] gtk_table_set_row_spacings(GTK_TABLE(table), 10); ^ record.c:117:2: warning: 'gtk_table_get_type' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtktable.h:100) [-Wdeprecated-declarations] record.c:118:2: warning: 'gtk_table_set_col_spacings' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtktable.h:147): Use 'GtkGrid' instead [-Wdeprecated-declarations] gtk_table_set_col_spacings(GTK_TABLE(table), 12); ^ record.c:118:2: warning: 'gtk_table_get_type' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtktable.h:100) [-Wdeprecated-declarations] record.c:148:2: warning: 'gtk_table_attach' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtktable.h:110): Use 'GtkGrid' instead [-Wdeprecated-declarations] gtk_table_attach(GTK_TABLE(table), title, 0, 2, 0, 1, GTK_FILL | GTK_SHRINK, GTK_FILL | GTK_EXPAND, 0, 0); ^ record.c:148:2: warning: 'gtk_table_get_type' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtktable.h:100) [-Wdeprecated-declarations] record.c:149:2: warning: 'gtk_table_attach' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtktable.h:110): Use 'GtkGrid' instead [-Wdeprecated-declarations] gtk_table_attach(GTK_TABLE(table), f_lbl, 0, 1, 1, 2, GTK_FILL | GTK_SHRINK, GTK_FILL, 0, 0); ^ record.c:149:2: warning: 'gtk_table_get_type' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtktable.h:100) [-Wdeprecated-declarations] record.c:150:2: warning: 'gtk_table_attach' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtktable.h:110): Use 'GtkGrid' instead [-Wdeprecated-declarations] gtk_table_attach(GTK_TABLE(table), s_lbl, 0, 1, 2, 3, GTK_FILL | GTK_SHRINK, GTK_FILL, 0, 0); ^ record.c:150:2: warning: 'gtk_table_get_type' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtktable.h:100) [-Wdeprecated-declarations] record.c:152:2: warning: 'gtk_table_attach' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtktable.h:110): Use 'GtkGrid' instead [-Wdeprecated-declarations] gtk_table_attach(GTK_TABLE(table), file_lbl, 1, 2, 1, 2, GTK_FILL | GTK_EXPAND, GTK_FILL, 0, 0); ^ record.c:152:2: warning: 'gtk_table_get_type' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtktable.h:100) [-Wdeprecated-declarations] record.c:153:2: warning: 'gtk_table_attach' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtktable.h:110): Use 'GtkGrid' instead [-Wdeprecated-declarations] gtk_table_attach(GTK_TABLE(table), size_lbl, 1, 2, 2, 3, GTK_FILL | GTK_EXPAND, GTK_FILL, 0, 0); ^ record.c:153:2: warning: 'gtk_table_get_type' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtktable.h:100) [-Wdeprecated-declarations] record.c:156:2: warning: 'gtk_hbox_new' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtkhbox.h:63): Use 'gtk_box_new' instead [-Wdeprecated-declarations] btn_box = gtk_hbox_new(FALSE, 0); ^ record.c:158:2: warning: 'gtk_image_new_from_stock' is deprecated (declared at /usr/include/gtk-3.0/gtk/gtkimage.h:122): Use 'gtk_image_new_from_icon_name' instead [-Wdeprecated-declarations] btn_pixmap = gtk_image_new_from_stock(GTK_STOCK_STOP, GTK_ICON_SIZE_BUTTON); ^ record.c:158:2: warning: 'GtkStock' is deprecated [-Wdeprecated-declarations] record.c:165:2: warning: 'gtk_hbox_new' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtkhbox.h:63): Use 'gtk_box_new' instead [-Wdeprecated-declarations] hbox = gtk_hbox_new(FALSE, 0); ^ trayicon.c: In function 'create_tray_menu': trayicon.c:92:2: warning: 'gtk_image_menu_item_new_from_stock' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtkimagemenuitem.h:84): Use 'gtk_menu_item_new' instead [-Wdeprecated-declarations] GtkWidget *record_menuitem = gtk_image_menu_item_new_from_stock(GTK_STOCK_MEDIA_RECORD, NULL); ^ bacon-volume.c: In function 'bacon_volume_button_new': trayicon.c:92:2: warning: 'GtkStock' is deprecated [-Wdeprecated-declarations] bacon-volume.c:183:3: warning: 'gtk_vbox_new' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtkvbox.h:61): Use 'gtk_box_new' instead [-Wdeprecated-declarations] box = gtk_vbox_new (FALSE, 0); ^ trayicon.c:106:2: warning: 'gtk_image_menu_item_new_from_stock' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtkimagemenuitem.h:84): Use 'gtk_menu_item_new' instead [-Wdeprecated-declarations] GtkWidget *quit_menuitem = gtk_image_menu_item_new_from_stock(GTK_STOCK_QUIT, NULL); ^ trayicon.c:106:2: warning: 'GtkStock' is deprecated [-Wdeprecated-declarations] trayicon.c: In function 'create_tray_icon': trayicon.c:137:2: warning: 'gdk_pixbuf_unref' is deprecated (declared at /usr/include/gdk-pixbuf-2.0/gdk-pixbuf/gdk-pixbuf-core.h:226): Use 'g_object_unref' instead [-Wdeprecated-declarations] gdk_pixbuf_unref(pixbuf); ^ bacon-volume.c: In function 'bacon_volume_button_press': bacon-volume.c:313:3: warning: 'gdk_pointer_grab' is deprecated (declared at /usr/include/gtk-3.0/gdk/gdkmain.h:86): Use 'gdk_device_grab' instead [-Wdeprecated-declarations] gdk_pointer_grab (gtk_widget_get_window(button->dock), TRUE, ^ bacon-volume.c:316:3: warning: 'gdk_keyboard_grab' is deprecated (declared at /usr/include/gtk-3.0/gdk/gdkmain.h:93): Use 'gdk_device_grab' instead [-Wdeprecated-declarations] gdk_keyboard_grab (gtk_widget_get_window(button->dock), TRUE, GDK_CURRENT_TIME); ^ bacon-volume.c: In function 'bacon_volume_release_grab': bacon-volume.c:418:3: warning: 'gdk_keyboard_ungrab' is deprecated (declared at /usr/include/gtk-3.0/gdk/gdkmain.h:104): Use 'gdk_device_ungrab' instead [-Wdeprecated-declarations] gdk_keyboard_ungrab (GDK_CURRENT_TIME); ^ bacon-volume.c:419:3: warning: 'gdk_pointer_ungrab' is deprecated (declared at /usr/include/gtk-3.0/gdk/gdkmain.h:102): Use 'gdk_device_ungrab' instead [-Wdeprecated-declarations] gdk_pointer_ungrab (GDK_CURRENT_TIME); ^ bacon-volume.c: In function 'bacon_volume_scale_get_type': bacon-volume.c:496:9: warning: 'gtk_vscale_get_type' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtkvscale.h:65) [-Wdeprecated-declarations] g_type_register_static (GTK_TYPE_VSCALE, ^ bacon-volume.c: In function 'bacon_volume_scale_class_init': bacon-volume.c:510:3: warning: 'gtk_vscale_get_type' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtkvscale.h:65) [-Wdeprecated-declarations] scale_parent_class = g_type_class_ref (GTK_TYPE_VSCALE); ^ bacon-volume.c: In function 'bacon_volume_scale_new': bacon-volume.c:525:7: warning: assignment from incompatible pointer type [enabled by default] adj = gtk_adjustment_new (min, min, max, step, 10 * step, 0); ^ prefs.c: In function 'add_button_clicked_cb': prefs.c:312:2: warning: 'gtk_tree_view_get_vadjustment' is deprecated (declared at /usr/include/gtk-3.0/gtk/gtktreeview.h:227): Use 'gtk_scrollable_get_vadjustment' instead [-Wdeprecated-declarations] v_scb = gtk_tree_view_get_vadjustment(GTK_TREE_VIEW(list_view)); ^ prefs.c: In function 'destination_button_clicked_cb': prefs.c:386:6: warning: 'GtkStock' is deprecated [-Wdeprecated-declarations] GTK_STOCK_CANCEL, GTK_RESPONSE_CANCEL, ^ prefs.c:387:6: warning: 'GtkStock' is deprecated [-Wdeprecated-declarations] GTK_STOCK_OPEN, GTK_RESPONSE_ACCEPT, ^ prefs.c: In function 'prefs_window': prefs.c:540:4: warning: 'GtkStock' is deprecated [-Wdeprecated-declarations] GTK_STOCK_CLOSE, GTK_RESPONSE_CLOSE, ^ prefs.c:541:4: warning: 'GtkStock' is deprecated [-Wdeprecated-declarations] GTK_STOCK_HELP, GTK_RESPONSE_HELP, ^ prefs.c:547:2: warning: 'gtk_vbox_new' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtkvbox.h:61): Use 'gtk_box_new' instead [-Wdeprecated-declarations] box = gtk_vbox_new(FALSE, 18); ^ prefs.c:551:2: warning: 'gtk_vbox_new' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtkvbox.h:61): Use 'gtk_box_new' instead [-Wdeprecated-declarations] settings_box = gtk_vbox_new(FALSE, 6); ^ prefs.c:561:2: warning: 'gtk_vbox_new' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtkvbox.h:61): Use 'gtk_box_new' instead [-Wdeprecated-declarations] presets_box = gtk_vbox_new(FALSE, 6); ^ prefs.c:571:2: warning: 'gtk_vbox_new' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtkvbox.h:61): Use 'gtk_box_new' instead [-Wdeprecated-declarations] record_box = gtk_vbox_new(FALSE, 6); ^ prefs.c:582:2: warning: 'gtk_hbox_new' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtkhbox.h:63): Use 'gtk_box_new' instead [-Wdeprecated-declarations] sbox = gtk_hbox_new(FALSE, 0); ^ prefs.c:587:2: warning: 'gtk_table_new' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtktable.h:102): Use 'GtkGrid' instead [-Wdeprecated-declarations] settings_table = gtk_table_new(3, 2, FALSE); ^ prefs.c:588:2: warning: 'gtk_table_set_row_spacings' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtktable.h:142): Use 'GtkGrid' instead [-Wdeprecated-declarations] gtk_table_set_row_spacings(GTK_TABLE(settings_table), 5); ^ prefs.c:588:2: warning: 'gtk_table_get_type' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtktable.h:100) [-Wdeprecated-declarations] prefs.c:589:2: warning: 'gtk_table_set_col_spacings' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtktable.h:147): Use 'GtkGrid' instead [-Wdeprecated-declarations] gtk_table_set_col_spacings(GTK_TABLE(settings_table), 15); ^ prefs.c:589:2: warning: 'gtk_table_get_type' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtktable.h:100) [-Wdeprecated-declarations] prefs.c:596:2: warning: 'gtk_table_attach_defaults' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtktable.h:121): Use 'GtkGrid' instead [-Wdeprecated-declarations] gtk_table_attach_defaults(GTK_TABLE(settings_table), device_label, 0, 1, 0, 1); ^ prefs.c:596:2: warning: 'gtk_table_get_type' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtktable.h:100) [-Wdeprecated-declarations] prefs.c:597:2: warning: 'gtk_table_attach_defaults' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtktable.h:121): Use 'GtkGrid' instead [-Wdeprecated-declarations] gtk_table_attach_defaults(GTK_TABLE(settings_table), device_entry, 1, 2, 0, 1); ^ prefs.c:597:2: warning: 'gtk_table_get_type' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtktable.h:100) [-Wdeprecated-declarations] prefs.c:613:2: warning: 'gtk_table_attach_defaults' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtktable.h:121): Use 'GtkGrid' instead [-Wdeprecated-declarations] gtk_table_attach_defaults(GTK_TABLE(settings_table), mixer_label, 0, 1, 1, 2); ^ prefs.c:613:2: warning: 'gtk_table_get_type' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtktable.h:100) [-Wdeprecated-declarations] prefs.c:614:2: warning: 'gtk_table_attach_defaults' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtktable.h:121): Use 'GtkGrid' instead [-Wdeprecated-declarations] gtk_table_attach_defaults(GTK_TABLE(settings_table), mixer_eb, 1, 2, 1, 2); ^ prefs.c:614:2: warning: 'gtk_table_get_type' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtktable.h:100) [-Wdeprecated-declarations] prefs.c:619:2: warning: 'gtk_table_attach_defaults' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtktable.h:121): Use 'GtkGrid' instead [-Wdeprecated-declarations] gtk_table_attach_defaults(GTK_TABLE(settings_table), mute_on_exit_cb, 0, 2, 2, 3); ^ prefs.c:619:2: warning: 'gtk_table_get_type' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtktable.h:100) [-Wdeprecated-declarations] prefs.c:633:2: warning: 'gtk_hbox_new' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtkhbox.h:63): Use 'gtk_box_new' instead [-Wdeprecated-declarations] pbox = gtk_hbox_new(FALSE, 0); ^ prefs.c:638:2: warning: 'gtk_vbox_new' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtkvbox.h:61): Use 'gtk_box_new' instead [-Wdeprecated-declarations] preset_box = gtk_vbox_new(FALSE, 10); ^ gui.c: In function 'initial_frequency_scan': gui.c:137:3: warning: 'GtkStock' is deprecated [-Wdeprecated-declarations] GTK_WINDOW(app), DIALOG_FLAGS, GTK_STOCK_CANCEL, GTK_RESPONSE_CANCEL, NULL); ^ prefs.c:671:2: warning: 'gtk_hbox_new' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtkhbox.h:63): Use 'gtk_box_new' instead [-Wdeprecated-declarations] button_box = gtk_hbox_new(FALSE, 12); ^ prefs.c:673:2: warning: 'gtk_button_new_from_stock' is deprecated (declared at /usr/include/gtk-3.0/gtk/gtkbutton.h:103): Use 'gtk_button_new_with_label' instead [-Wdeprecated-declarations] add_button = gtk_button_new_from_stock(GTK_STOCK_ADD); ^ prefs.c:673:2: warning: 'GtkStock' is deprecated [-Wdeprecated-declarations] prefs.c:674:2: warning: 'gtk_button_new_from_stock' is deprecated (declared at /usr/include/gtk-3.0/gtk/gtkbutton.h:103): Use 'gtk_button_new_with_label' instead [-Wdeprecated-declarations] del_button = gtk_button_new_from_stock(GTK_STOCK_DELETE); ^ prefs.c:674:2: warning: 'GtkStock' is deprecated [-Wdeprecated-declarations] prefs.c:702:2: warning: 'gtk_hbox_new' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtkhbox.h:63): Use 'gtk_box_new' instead [-Wdeprecated-declarations] rbox = gtk_hbox_new(FALSE, 0); ^ prefs.c:707:2: warning: 'gtk_table_new' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtktable.h:102): Use 'GtkGrid' instead [-Wdeprecated-declarations] record_table = gtk_table_new(2, 2, FALSE); ^ prefs.c:708:2: warning: 'gtk_table_set_col_spacings' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtktable.h:147): Use 'GtkGrid' instead [-Wdeprecated-declarations] gtk_table_set_col_spacings(GTK_TABLE(record_table), 15); ^ prefs.c:708:2: warning: 'gtk_table_get_type' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtktable.h:100) [-Wdeprecated-declarations] prefs.c:709:2: warning: 'gtk_table_set_row_spacings' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtktable.h:142): Use 'GtkGrid' instead [-Wdeprecated-declarations] gtk_table_set_row_spacings(GTK_TABLE(record_table), 5); ^ prefs.c:709:2: warning: 'gtk_table_get_type' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtktable.h:100) [-Wdeprecated-declarations] prefs.c:722:2: warning: 'gtk_table_attach_defaults' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtktable.h:121): Use 'GtkGrid' instead [-Wdeprecated-declarations] gtk_table_attach_defaults(GTK_TABLE(record_table), destination_label, 0, 1, 0, 1); ^ prefs.c:722:2: warning: 'gtk_table_get_type' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtktable.h:100) [-Wdeprecated-declarations] prefs.c:723:2: warning: 'gtk_table_attach_defaults' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtktable.h:121): Use 'GtkGrid' instead [-Wdeprecated-declarations] gtk_table_attach_defaults(GTK_TABLE(record_table), destination_button, 1, 2, 0, 1); ^ prefs.c:723:2: warning: 'gtk_table_get_type' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtktable.h:100) [-Wdeprecated-declarations] prefs.c:724:2: warning: 'gtk_table_attach_defaults' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtktable.h:121): Use 'GtkGrid' instead [-Wdeprecated-declarations] gtk_table_attach_defaults(GTK_TABLE(record_table), profile_eb, 0, 2, 1, 2); ^ prefs.c:724:2: warning: 'gtk_table_get_type' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtktable.h:100) [-Wdeprecated-declarations] gui.c: In function 'gnome_radio_gui': gui.c:887:2: warning: 'gtk_image_new_from_stock' is deprecated (declared at /usr/include/gtk-3.0/gtk/gtkimage.h:122): Use 'gtk_image_new_from_icon_name' instead [-Wdeprecated-declarations] quit_pixmap = gtk_image_new_from_stock(GTK_STOCK_QUIT, GTK_ICON_SIZE_BUTTON); ^ gui.c:887:2: warning: 'GtkStock' is deprecated [-Wdeprecated-declarations] gui.c:888:2: warning: 'gtk_image_new_from_stock' is deprecated (declared at /usr/include/gtk-3.0/gtk/gtkimage.h:122): Use 'gtk_image_new_from_icon_name' instead [-Wdeprecated-declarations] prefs_pixmap = gtk_image_new_from_stock(GTK_STOCK_PROPERTIES, GTK_ICON_SIZE_LARGE_TOOLBAR); ^ gui.c:888:2: warning: 'GtkStock' is deprecated [-Wdeprecated-declarations] gui.c:889:2: warning: 'gtk_image_new_from_stock' is deprecated (declared at /usr/include/gtk-3.0/gtk/gtkimage.h:122): Use 'gtk_image_new_from_icon_name' instead [-Wdeprecated-declarations] scfw_pixmap = gtk_image_new_from_stock(GTK_STOCK_MEDIA_FORWARD, GTK_ICON_SIZE_LARGE_TOOLBAR); ^ gui.c:889:2: warning: 'GtkStock' is deprecated [-Wdeprecated-declarations] gui.c:890:2: warning: 'gtk_image_new_from_stock' is deprecated (declared at /usr/include/gtk-3.0/gtk/gtkimage.h:122): Use 'gtk_image_new_from_icon_name' instead [-Wdeprecated-declarations] scbw_pixmap = gtk_image_new_from_stock(GTK_STOCK_MEDIA_REWIND, GTK_ICON_SIZE_LARGE_TOOLBAR); ^ gui.c:890:2: warning: 'GtkStock' is deprecated [-Wdeprecated-declarations] gui.c:891:2: warning: 'gtk_image_new_from_stock' is deprecated (declared at /usr/include/gtk-3.0/gtk/gtkimage.h:122): Use 'gtk_image_new_from_icon_name' instead [-Wdeprecated-declarations] stfw_pixmap = gtk_image_new_from_stock(GTK_STOCK_MEDIA_NEXT, GTK_ICON_SIZE_LARGE_TOOLBAR); ^ gui.c:891:2: warning: 'GtkStock' is deprecated [-Wdeprecated-declarations] gui.c:892:2: warning: 'gtk_image_new_from_stock' is deprecated (declared at /usr/include/gtk-3.0/gtk/gtkimage.h:122): Use 'gtk_image_new_from_icon_name' instead [-Wdeprecated-declarations] stbw_pixmap = gtk_image_new_from_stock(GTK_STOCK_MEDIA_PREVIOUS, GTK_ICON_SIZE_LARGE_TOOLBAR); ^ gui.c:892:2: warning: 'GtkStock' is deprecated [-Wdeprecated-declarations] gui.c:893:2: warning: 'gtk_image_new_from_stock' is deprecated (declared at /usr/include/gtk-3.0/gtk/gtkimage.h:122): Use 'gtk_image_new_from_icon_name' instead [-Wdeprecated-declarations] about_pixmap = gtk_image_new_from_stock(GTK_STOCK_ABOUT, GTK_ICON_SIZE_LARGE_TOOLBAR); ^ gui.c:893:2: warning: 'GtkStock' is deprecated [-Wdeprecated-declarations] gui.c:895:2: warning: 'gtk_image_new_from_stock' is deprecated (declared at /usr/include/gtk-3.0/gtk/gtkimage.h:122): Use 'gtk_image_new_from_icon_name' instead [-Wdeprecated-declarations] rec_pixmap = gtk_image_new_from_stock(GTK_STOCK_MEDIA_RECORD, GTK_ICON_SIZE_LARGE_TOOLBAR); ^ gui.c:895:2: warning: 'GtkStock' is deprecated [-Wdeprecated-declarations] gui.c:922:2: warning: 'gtk_vbox_new' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtkvbox.h:61): Use 'gtk_box_new' instead [-Wdeprecated-declarations] vbox = gtk_vbox_new(FALSE, 0); ^ gui.c:923:2: warning: 'gtk_hbox_new' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtkhbox.h:63): Use 'gtk_box_new' instead [-Wdeprecated-declarations] hbox1 = gtk_hbox_new(FALSE, 0); ^ gui.c:924:2: warning: 'gtk_hbox_new' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtkhbox.h:63): Use 'gtk_box_new' instead [-Wdeprecated-declarations] hbox2 = gtk_hbox_new(FALSE, 0); ^ gui.c:925:2: warning: 'gtk_vbox_new' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtkvbox.h:61): Use 'gtk_box_new' instead [-Wdeprecated-declarations] menubox = gtk_vbox_new(FALSE, 0); ^ gui.c:926:2: warning: 'gtk_hbox_new' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtkhbox.h:63): Use 'gtk_box_new' instead [-Wdeprecated-declarations] freq_vol_box = gtk_hbox_new(FALSE, 0); ^ gui.c:937:2: warning: 'gtk_hscale_new' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtkhscale.h:61): Use 'gtk_scale_new' instead [-Wdeprecated-declarations] freq_scale = gtk_hscale_new(adj); ^ gui.c:962:2: warning: 'gtk_vseparator_new' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtkvseparator.h:67): Use 'gtk_separator_new' instead [-Wdeprecated-declarations] vseparator1 = gtk_vseparator_new(); ^ gui.c:965:2: warning: 'gtk_vseparator_new' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtkvseparator.h:67): Use 'gtk_separator_new' instead [-Wdeprecated-declarations] vseparator4 = gtk_vseparator_new(); ^ gui.c: In function 'main': gui.c:1150:5: warning: 'g_thread_init' is deprecated (declared at /usr/include/glib-2.0/glib/deprecated/gthread.h:261) [-Wdeprecated-declarations] if (!g_thread_supported ()) g_thread_init(NULL); ^ /bin/sh ../libtool --tag=CC --mode=link i686-uhu-linux-gcc -O2 -march=i686 -mtune=generic -o gnomeradio bacon-volume.o gui.o lirc.o prefs.o radio.o rec_tech.o record.o tech.o trayicon.o v4l2.o -ldbus-glib-1 -ldbus-1 -lgnomevfs-2 -lgthread-2.0 -pthread -lgmodule-2.0 -pthread -lgnome-media-profiles-3.0 -lgconf-2 -lgtk-3 -lgdk-3 -lpangocairo-1.0 -lpango-1.0 -latk-1.0 -lcairo-gobject -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0 -lgstreamer-0.10 -lgobject-2.0 -lgmodule-2.0 -pthread -lgthread-2.0 -pthread -lglib-2.0 -lxml2 -llirc_client -lm mkdir .libs i686-uhu-linux-gcc -O2 -march=i686 -mtune=generic -o gnomeradio bacon-volume.o gui.o lirc.o prefs.o radio.o rec_tech.o record.o tech.o trayicon.o v4l2.o -pthread -pthread -pthread -pthread /usr/lib/libdbus-glib-1.so /usr/lib/libdbus-1.so /usr/lib/libgnomevfs-2.so /usr/lib/libgnome-media-profiles-3.0.so /usr/lib/libgconf-2.so /usr/lib/libgtk-3.so /usr/lib/libgdk-3.so /usr/lib/libpangocairo-1.0.so /usr/lib/libpango-1.0.so /usr/lib/libatk-1.0.so /usr/lib/libcairo-gobject.so /usr/lib/libcairo.so /usr/lib/libgdk_pixbuf-2.0.so /usr/lib/libgio-2.0.so /usr/lib/libgstreamer-0.10.so /usr/lib/libgobject-2.0.so /usr/lib/libgmodule-2.0.so /usr/lib/libgthread-2.0.so /usr/lib/libglib-2.0.so /usr/lib/libxml2.so /usr/lib/liblirc_client.so -lm make[2]: Leaving directory `/var/uhubuild/work/compile/src' make[2]: Entering directory `/var/uhubuild/work/compile' make[2]: Leaving directory `/var/uhubuild/work/compile' make[1]: Leaving directory `/var/uhubuild/work/compile' ccache-remove-unused... ccache-compress... compile-snapshot...  (kihagyva) install... + ub_install DESTDIR-aware Makefile found. make DESTDIR=/var/uhubuild/work/install MAN1EXT=1 MAN2EXT=2 MAN3EXT=3 MAN4EXT=4 MAN5EXT=5 MAN6EXT=6 MAN7EXT=7 MAN8EXT=8 install Making install in help make[1]: Entering directory `/var/uhubuild/work/compile/help' make[2]: Entering directory `/var/uhubuild/work/compile/help' make[2]: Nothing to be done for `install-exec-am'. /bin/sh ../mkinstalldirs /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/C mkdir -p -- /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/C /bin/sh ../mkinstalldirs /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/es mkdir -p -- /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/es /bin/sh ../mkinstalldirs /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/fr mkdir -p -- /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/fr /bin/sh ../mkinstalldirs /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/oc mkdir -p -- /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/oc /bin/sh ../mkinstalldirs /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/sv mkdir -p -- /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/sv /bin/install -c -m 644 C/legal.xml /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/C/legal.xml /bin/install -c -m 644 C/gnomeradio.xml /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/C/gnomeradio.xml /bin/install -c -m 644 es/gnomeradio.xml /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/es/gnomeradio.xml /bin/install -c -m 644 fr/gnomeradio.xml /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/fr/gnomeradio.xml /bin/install -c -m 644 oc/gnomeradio.xml /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/oc/gnomeradio.xml /bin/install -c -m 644 sv/gnomeradio.xml /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/sv/gnomeradio.xml /bin/sh ../mkinstalldirs /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/C/figures/ mkdir -p -- /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/C/figures/ /bin/install -c -m 644 C/figures/freq-controls.png /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/C/figures/freq-controls.png /bin/sh ../mkinstalldirs /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/es/figures/ mkdir -p -- /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/es/figures/ /bin/install -c -m 644 C/figures/freq-controls.png /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/es/figures/freq-controls.png /bin/sh ../mkinstalldirs /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/fr/figures/ mkdir -p -- /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/fr/figures/ /bin/install -c -m 644 C/figures/freq-controls.png /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/fr/figures/freq-controls.png /bin/sh ../mkinstalldirs /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/oc/figures/ mkdir -p -- /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/oc/figures/ /bin/install -c -m 644 C/figures/freq-controls.png /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/oc/figures/freq-controls.png /bin/sh ../mkinstalldirs /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/sv/figures/ mkdir -p -- /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/sv/figures/ /bin/install -c -m 644 C/figures/freq-controls.png /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/sv/figures/freq-controls.png /bin/install -c -m 644 C/figures/misc-controls.png /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/C/figures/misc-controls.png /bin/install -c -m 644 C/figures/misc-controls.png /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/es/figures/misc-controls.png /bin/install -c -m 644 C/figures/misc-controls.png /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/fr/figures/misc-controls.png /bin/install -c -m 644 C/figures/misc-controls.png /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/oc/figures/misc-controls.png /bin/install -c -m 644 C/figures/misc-controls.png /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/sv/figures/misc-controls.png /bin/install -c -m 644 C/figures/presets-box.png /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/C/figures/presets-box.png /bin/install -c -m 644 C/figures/presets-box.png /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/es/figures/presets-box.png /bin/install -c -m 644 fr/figures/presets-box.png /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/fr/figures/presets-box.png /bin/install -c -m 644 C/figures/presets-box.png /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/oc/figures/presets-box.png /bin/install -c -m 644 C/figures/presets-box.png /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/sv/figures/presets-box.png /bin/install -c -m 644 C/figures/recording-general.png /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/C/figures/recording-general.png /bin/install -c -m 644 C/figures/recording-general.png /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/es/figures/recording-general.png /bin/install -c -m 644 C/figures/recording-general.png /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/fr/figures/recording-general.png /bin/install -c -m 644 C/figures/recording-general.png /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/oc/figures/recording-general.png /bin/install -c -m 644 C/figures/recording-general.png /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/sv/figures/recording-general.png /bin/install -c -m 644 C/figures/recording-mp3.png /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/C/figures/recording-mp3.png /bin/install -c -m 644 C/figures/recording-mp3.png /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/es/figures/recording-mp3.png /bin/install -c -m 644 C/figures/recording-mp3.png /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/fr/figures/recording-mp3.png /bin/install -c -m 644 C/figures/recording-mp3.png /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/oc/figures/recording-mp3.png /bin/install -c -m 644 C/figures/recording-mp3.png /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/sv/figures/recording-mp3.png /bin/install -c -m 644 C/figures/recording-wav.png /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/C/figures/recording-wav.png /bin/install -c -m 644 C/figures/recording-wav.png /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/es/figures/recording-wav.png /bin/install -c -m 644 C/figures/recording-wav.png /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/fr/figures/recording-wav.png /bin/install -c -m 644 C/figures/recording-wav.png /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/oc/figures/recording-wav.png /bin/install -c -m 644 C/figures/recording-wav.png /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/sv/figures/recording-wav.png /bin/install -c -m 644 C/figures/recording_status.png /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/C/figures/recording_status.png /bin/install -c -m 644 C/figures/recording_status.png /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/es/figures/recording_status.png /bin/install -c -m 644 fr/figures/recording_status.png /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/fr/figures/recording_status.png /bin/install -c -m 644 C/figures/recording_status.png /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/oc/figures/recording_status.png /bin/install -c -m 644 sv/figures/recording_status.png /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/sv/figures/recording_status.png /bin/install -c -m 644 C/figures/settings-misc.png /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/C/figures/settings-misc.png /bin/install -c -m 644 C/figures/settings-misc.png /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/es/figures/settings-misc.png /bin/install -c -m 644 fr/figures/settings-misc.png /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/fr/figures/settings-misc.png /bin/install -c -m 644 C/figures/settings-misc.png /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/oc/figures/settings-misc.png /bin/install -c -m 644 C/figures/settings-misc.png /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/sv/figures/settings-misc.png /bin/install -c -m 644 C/figures/settings-presets.png /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/C/figures/settings-presets.png /bin/install -c -m 644 C/figures/settings-presets.png /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/es/figures/settings-presets.png /bin/install -c -m 644 C/figures/settings-presets.png /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/fr/figures/settings-presets.png /bin/install -c -m 644 C/figures/settings-presets.png /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/oc/figures/settings-presets.png /bin/install -c -m 644 C/figures/settings-presets.png /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/sv/figures/settings-presets.png /bin/install -c -m 644 C/figures/status-window.png /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/C/figures/status-window.png /bin/install -c -m 644 C/figures/status-window.png /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/es/figures/status-window.png /bin/install -c -m 644 C/figures/status-window.png /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/fr/figures/status-window.png /bin/install -c -m 644 C/figures/status-window.png /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/oc/figures/status-window.png /bin/install -c -m 644 C/figures/status-window.png /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/sv/figures/status-window.png /bin/install -c -m 644 C/figures/volume-controls.png /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/C/figures/volume-controls.png /bin/install -c -m 644 C/figures/volume-controls.png /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/es/figures/volume-controls.png /bin/install -c -m 644 C/figures/volume-controls.png /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/fr/figures/volume-controls.png /bin/install -c -m 644 C/figures/volume-controls.png /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/oc/figures/volume-controls.png /bin/install -c -m 644 C/figures/volume-controls.png /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/sv/figures/volume-controls.png /bin/sh ../mkinstalldirs /var/uhubuild/work/install/usr/share/omf/gnomeradio mkdir -p -- /var/uhubuild/work/install/usr/share/omf/gnomeradio /bin/install -c -m 644 gnomeradio-C.omf /var/uhubuild/work/install/usr/share/omf/gnomeradio/gnomeradio-C.omf /bin/install -c -m 644 gnomeradio-es.omf /var/uhubuild/work/install/usr/share/omf/gnomeradio/gnomeradio-es.omf /bin/install -c -m 644 gnomeradio-fr.omf /var/uhubuild/work/install/usr/share/omf/gnomeradio/gnomeradio-fr.omf /bin/install -c -m 644 gnomeradio-oc.omf /var/uhubuild/work/install/usr/share/omf/gnomeradio/gnomeradio-oc.omf /bin/install -c -m 644 gnomeradio-sv.omf /var/uhubuild/work/install/usr/share/omf/gnomeradio/gnomeradio-sv.omf make[2]: Leaving directory `/var/uhubuild/work/compile/help' make[1]: Leaving directory `/var/uhubuild/work/compile/help' Making install in data make[1]: Entering directory `/var/uhubuild/work/compile/data' Making install in icons make[2]: Entering directory `/var/uhubuild/work/compile/data/icons' Making install in 16x16 make[3]: Entering directory `/var/uhubuild/work/compile/data/icons/16x16' make[4]: Entering directory `/var/uhubuild/work/compile/data/icons/16x16' make[4]: Nothing to be done for `install-exec-am'. test -z "/usr/share/icons/hicolor/16x16/apps" || mkdir -p -- "/var/uhubuild/work/install/usr/share/icons/hicolor/16x16/apps" /bin/install -c -m 644 'gnomeradio.png' '/var/uhubuild/work/install/usr/share/icons/hicolor/16x16/apps/gnomeradio.png' make[4]: Leaving directory `/var/uhubuild/work/compile/data/icons/16x16' make[3]: Leaving directory `/var/uhubuild/work/compile/data/icons/16x16' Making install in 22x22 make[3]: Entering directory `/var/uhubuild/work/compile/data/icons/22x22' make[4]: Entering directory `/var/uhubuild/work/compile/data/icons/22x22' make[4]: Nothing to be done for `install-exec-am'. test -z "/usr/share/icons/hicolor/22x22/apps" || mkdir -p -- "/var/uhubuild/work/install/usr/share/icons/hicolor/22x22/apps" /bin/install -c -m 644 'gnomeradio.png' '/var/uhubuild/work/install/usr/share/icons/hicolor/22x22/apps/gnomeradio.png' make[4]: Leaving directory `/var/uhubuild/work/compile/data/icons/22x22' make[3]: Leaving directory `/var/uhubuild/work/compile/data/icons/22x22' Making install in 24x24 make[3]: Entering directory `/var/uhubuild/work/compile/data/icons/24x24' make[4]: Entering directory `/var/uhubuild/work/compile/data/icons/24x24' make[4]: Nothing to be done for `install-exec-am'. test -z "/usr/share/icons/hicolor/24x24/apps" || mkdir -p -- "/var/uhubuild/work/install/usr/share/icons/hicolor/24x24/apps" /bin/install -c -m 644 'gnomeradio.png' '/var/uhubuild/work/install/usr/share/icons/hicolor/24x24/apps/gnomeradio.png' make[4]: Leaving directory `/var/uhubuild/work/compile/data/icons/24x24' make[3]: Leaving directory `/var/uhubuild/work/compile/data/icons/24x24' Making install in 32x32 make[3]: Entering directory `/var/uhubuild/work/compile/data/icons/32x32' make[4]: Entering directory `/var/uhubuild/work/compile/data/icons/32x32' make[4]: Nothing to be done for `install-exec-am'. test -z "/usr/share/icons/hicolor/32x32/apps" || mkdir -p -- "/var/uhubuild/work/install/usr/share/icons/hicolor/32x32/apps" /bin/install -c -m 644 'gnomeradio.png' '/var/uhubuild/work/install/usr/share/icons/hicolor/32x32/apps/gnomeradio.png' make[4]: Leaving directory `/var/uhubuild/work/compile/data/icons/32x32' make[3]: Leaving directory `/var/uhubuild/work/compile/data/icons/32x32' Making install in 48x48 make[3]: Entering directory `/var/uhubuild/work/compile/data/icons/48x48' make[4]: Entering directory `/var/uhubuild/work/compile/data/icons/48x48' make[4]: Nothing to be done for `install-exec-am'. test -z "/usr/share/icons/hicolor/48x48/apps" || mkdir -p -- "/var/uhubuild/work/install/usr/share/icons/hicolor/48x48/apps" /bin/install -c -m 644 'gnomeradio.png' '/var/uhubuild/work/install/usr/share/icons/hicolor/48x48/apps/gnomeradio.png' make[4]: Leaving directory `/var/uhubuild/work/compile/data/icons/48x48' make[3]: Leaving directory `/var/uhubuild/work/compile/data/icons/48x48' Making install in scalable make[3]: Entering directory `/var/uhubuild/work/compile/data/icons/scalable' make[4]: Entering directory `/var/uhubuild/work/compile/data/icons/scalable' make[4]: Nothing to be done for `install-exec-am'. test -z "/usr/share/icons/hicolor/scalable/apps" || mkdir -p -- "/var/uhubuild/work/install/usr/share/icons/hicolor/scalable/apps" /bin/install -c -m 644 'gnomeradio.svg' '/var/uhubuild/work/install/usr/share/icons/hicolor/scalable/apps/gnomeradio.svg' make[4]: Leaving directory `/var/uhubuild/work/compile/data/icons/scalable' make[3]: Leaving directory `/var/uhubuild/work/compile/data/icons/scalable' make[3]: Entering directory `/var/uhubuild/work/compile/data/icons' make[4]: Entering directory `/var/uhubuild/work/compile/data/icons' make[4]: Nothing to be done for `install-exec-am'. make install-data-hook make[5]: Entering directory `/var/uhubuild/work/compile/data/icons' *** Icon cache not updated. After install, run this: *** gtk-update-icon-cache -f -t /usr/share/icons/hicolor make[5]: Leaving directory `/var/uhubuild/work/compile/data/icons' make[4]: Leaving directory `/var/uhubuild/work/compile/data/icons' make[3]: Leaving directory `/var/uhubuild/work/compile/data/icons' make[2]: Leaving directory `/var/uhubuild/work/compile/data/icons' Making install in pixmaps make[2]: Entering directory `/var/uhubuild/work/compile/data/pixmaps' make[3]: Entering directory `/var/uhubuild/work/compile/data/pixmaps' make[3]: Nothing to be done for `install-exec-am'. make[3]: Nothing to be done for `install-data-am'. make[3]: Leaving directory `/var/uhubuild/work/compile/data/pixmaps' make[2]: Leaving directory `/var/uhubuild/work/compile/data/pixmaps' make[2]: Entering directory `/var/uhubuild/work/compile/data' make[3]: Entering directory `/var/uhubuild/work/compile/data' make[3]: Nothing to be done for `install-exec-am'. test -z "/usr/share/applications/" || mkdir -p -- "/var/uhubuild/work/install/usr/share/applications/" /bin/install -c -m 644 'gnomeradio.desktop' '/var/uhubuild/work/install/usr/share/applications//gnomeradio.desktop' GCONF_CONFIG_SOURCE=xml:merged:/etc/gconf/gconf.xml.defaults /usr/bin/gconftool-2 --makefile-install-rule ./gnomeradio.schemas (gconftool-2:30609): GConf-WARNING **: Client failed to connect to the D-BUS daemon: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11 Attached schema `/schemas/apps/gnomeradio/mute-on-exit' to key `/apps/gnomeradio/mute-on-exit' WARNING: failed to install schema `/schemas/apps/gnomeradio/mute-on-exit', locale `he': Unable to store a value at key '/schemas/apps/gnomeradio/mute-on-exit', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mute-on-exit', locale `ja': Unable to store a value at key '/schemas/apps/gnomeradio/mute-on-exit', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mute-on-exit', locale `zh_CN': Unable to store a value at key '/schemas/apps/gnomeradio/mute-on-exit', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mute-on-exit', locale `sk': Unable to store a value at key '/schemas/apps/gnomeradio/mute-on-exit', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mute-on-exit', locale `sr@Latn': Unable to store a value at key '/schemas/apps/gnomeradio/mute-on-exit', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mute-on-exit', locale `C': Unable to store a value at key '/schemas/apps/gnomeradio/mute-on-exit', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mute-on-exit', locale `fr': Unable to store a value at key '/schemas/apps/gnomeradio/mute-on-exit', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mute-on-exit', locale `sr': Unable to store a value at key '/schemas/apps/gnomeradio/mute-on-exit', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mute-on-exit', locale `dz': Unable to store a value at key '/schemas/apps/gnomeradio/mute-on-exit', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mute-on-exit', locale `nb': Unable to store a value at key '/schemas/apps/gnomeradio/mute-on-exit', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mute-on-exit', locale `hr': Unable to store a value at key '/schemas/apps/gnomeradio/mute-on-exit', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mute-on-exit', locale `ca': Unable to store a value at key '/schemas/apps/gnomeradio/mute-on-exit', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mute-on-exit', locale `sv': Unable to store a value at key '/schemas/apps/gnomeradio/mute-on-exit', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mute-on-exit', locale `pa': Unable to store a value at key '/schemas/apps/gnomeradio/mute-on-exit', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mute-on-exit', locale `hu': Unable to store a value at key '/schemas/apps/gnomeradio/mute-on-exit', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mute-on-exit', locale `uk': Unable to store a value at key '/schemas/apps/gnomeradio/mute-on-exit', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mute-on-exit', locale `nl': Unable to store a value at key '/schemas/apps/gnomeradio/mute-on-exit', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mute-on-exit', locale `zh_TW': Unable to store a value at key '/schemas/apps/gnomeradio/mute-on-exit', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mute-on-exit', locale `ar': Unable to store a value at key '/schemas/apps/gnomeradio/mute-on-exit', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mute-on-exit', locale `lv': Unable to store a value at key '/schemas/apps/gnomeradio/mute-on-exit', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mute-on-exit', locale `pl': Unable to store a value at key '/schemas/apps/gnomeradio/mute-on-exit', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mute-on-exit', locale `cs': Unable to store a value at key '/schemas/apps/gnomeradio/mute-on-exit', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mute-on-exit', locale `pt': Unable to store a value at key '/schemas/apps/gnomeradio/mute-on-exit', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mute-on-exit', locale `es': Unable to store a value at key '/schemas/apps/gnomeradio/mute-on-exit', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mute-on-exit', locale `eu': Unable to store a value at key '/schemas/apps/gnomeradio/mute-on-exit', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mute-on-exit', locale `vi': Unable to store a value at key '/schemas/apps/gnomeradio/mute-on-exit', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mute-on-exit', locale `ru': Unable to store a value at key '/schemas/apps/gnomeradio/mute-on-exit', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mute-on-exit', locale `en_CA': Unable to store a value at key '/schemas/apps/gnomeradio/mute-on-exit', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mute-on-exit', locale `tr': Unable to store a value at key '/schemas/apps/gnomeradio/mute-on-exit', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mute-on-exit', locale `be': Unable to store a value at key '/schemas/apps/gnomeradio/mute-on-exit', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mute-on-exit', locale `da': Unable to store a value at key '/schemas/apps/gnomeradio/mute-on-exit', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mute-on-exit', locale `it': Unable to store a value at key '/schemas/apps/gnomeradio/mute-on-exit', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mute-on-exit', locale `mk': Unable to store a value at key '/schemas/apps/gnomeradio/mute-on-exit', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mute-on-exit', locale `de': Unable to store a value at key '/schemas/apps/gnomeradio/mute-on-exit', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mute-on-exit', locale `mn': Unable to store a value at key '/schemas/apps/gnomeradio/mute-on-exit', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mute-on-exit', locale `pt_BR': Unable to store a value at key '/schemas/apps/gnomeradio/mute-on-exit', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mute-on-exit', locale `en_GB': Unable to store a value at key '/schemas/apps/gnomeradio/mute-on-exit', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mute-on-exit', locale `ms': Unable to store a value at key '/schemas/apps/gnomeradio/mute-on-exit', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mute-on-exit', locale `bg': Unable to store a value at key '/schemas/apps/gnomeradio/mute-on-exit', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mute-on-exit', locale `fi': Unable to store a value at key '/schemas/apps/gnomeradio/mute-on-exit', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/gnomeradio/last-freq' to key `/apps/gnomeradio/last-freq' WARNING: failed to install schema `/schemas/apps/gnomeradio/last-freq', locale `he': Unable to store a value at key '/schemas/apps/gnomeradio/last-freq', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/last-freq', locale `ja': Unable to store a value at key '/schemas/apps/gnomeradio/last-freq', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/last-freq', locale `zh_CN': Unable to store a value at key '/schemas/apps/gnomeradio/last-freq', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/last-freq', locale `sr@Latn': Unable to store a value at key '/schemas/apps/gnomeradio/last-freq', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/last-freq', locale `C': Unable to store a value at key '/schemas/apps/gnomeradio/last-freq', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/last-freq', locale `fr': Unable to store a value at key '/schemas/apps/gnomeradio/last-freq', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/last-freq', locale `sr': Unable to store a value at key '/schemas/apps/gnomeradio/last-freq', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/last-freq', locale `dz': Unable to store a value at key '/schemas/apps/gnomeradio/last-freq', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/last-freq', locale `nb': Unable to store a value at key '/schemas/apps/gnomeradio/last-freq', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/last-freq', locale `hr': Unable to store a value at key '/schemas/apps/gnomeradio/last-freq', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/last-freq', locale `ca': Unable to store a value at key '/schemas/apps/gnomeradio/last-freq', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/last-freq', locale `sv': Unable to store a value at key '/schemas/apps/gnomeradio/last-freq', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/last-freq', locale `pa': Unable to store a value at key '/schemas/apps/gnomeradio/last-freq', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/last-freq', locale `hu': Unable to store a value at key '/schemas/apps/gnomeradio/last-freq', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/last-freq', locale `uk': Unable to store a value at key '/schemas/apps/gnomeradio/last-freq', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/last-freq', locale `nl': Unable to store a value at key '/schemas/apps/gnomeradio/last-freq', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/last-freq', locale `zh_TW': Unable to store a value at key '/schemas/apps/gnomeradio/last-freq', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/last-freq', locale `lv': Unable to store a value at key '/schemas/apps/gnomeradio/last-freq', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/last-freq', locale `pl': Unable to store a value at key '/schemas/apps/gnomeradio/last-freq', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/last-freq', locale `cs': Unable to store a value at key '/schemas/apps/gnomeradio/last-freq', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/last-freq', locale `pt': Unable to store a value at key '/schemas/apps/gnomeradio/last-freq', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/last-freq', locale `es': Unable to store a value at key '/schemas/apps/gnomeradio/last-freq', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/last-freq', locale `eu': Unable to store a value at key '/schemas/apps/gnomeradio/last-freq', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/last-freq', locale `vi': Unable to store a value at key '/schemas/apps/gnomeradio/last-freq', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/last-freq', locale `ru': Unable to store a value at key '/schemas/apps/gnomeradio/last-freq', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/last-freq', locale `en_CA': Unable to store a value at key '/schemas/apps/gnomeradio/last-freq', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/last-freq', locale `tr': Unable to store a value at key '/schemas/apps/gnomeradio/last-freq', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/last-freq', locale `be': Unable to store a value at key '/schemas/apps/gnomeradio/last-freq', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/last-freq', locale `da': Unable to store a value at key '/schemas/apps/gnomeradio/last-freq', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/last-freq', locale `it': Unable to store a value at key '/schemas/apps/gnomeradio/last-freq', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/last-freq', locale `mk': Unable to store a value at key '/schemas/apps/gnomeradio/last-freq', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/last-freq', locale `de': Unable to store a value at key '/schemas/apps/gnomeradio/last-freq', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/last-freq', locale `mn': Unable to store a value at key '/schemas/apps/gnomeradio/last-freq', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/last-freq', locale `pt_BR': Unable to store a value at key '/schemas/apps/gnomeradio/last-freq', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/last-freq', locale `en_GB': Unable to store a value at key '/schemas/apps/gnomeradio/last-freq', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/last-freq', locale `ms': Unable to store a value at key '/schemas/apps/gnomeradio/last-freq', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/last-freq', locale `bg': Unable to store a value at key '/schemas/apps/gnomeradio/last-freq', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/last-freq', locale `fi': Unable to store a value at key '/schemas/apps/gnomeradio/last-freq', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/gnomeradio/device' to key `/apps/gnomeradio/device' WARNING: failed to install schema `/schemas/apps/gnomeradio/device', locale `he': Unable to store a value at key '/schemas/apps/gnomeradio/device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/device', locale `ja': Unable to store a value at key '/schemas/apps/gnomeradio/device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/device', locale `zh_CN': Unable to store a value at key '/schemas/apps/gnomeradio/device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/device', locale `sk': Unable to store a value at key '/schemas/apps/gnomeradio/device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/device', locale `sr@Latn': Unable to store a value at key '/schemas/apps/gnomeradio/device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/device', locale `C': Unable to store a value at key '/schemas/apps/gnomeradio/device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/device', locale `fr': Unable to store a value at key '/schemas/apps/gnomeradio/device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/device', locale `sr': Unable to store a value at key '/schemas/apps/gnomeradio/device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/device', locale `dz': Unable to store a value at key '/schemas/apps/gnomeradio/device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/device', locale `nb': Unable to store a value at key '/schemas/apps/gnomeradio/device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/device', locale `hr': Unable to store a value at key '/schemas/apps/gnomeradio/device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/device', locale `ca': Unable to store a value at key '/schemas/apps/gnomeradio/device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/device', locale `sv': Unable to store a value at key '/schemas/apps/gnomeradio/device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/device', locale `pa': Unable to store a value at key '/schemas/apps/gnomeradio/device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/device', locale `hu': Unable to store a value at key '/schemas/apps/gnomeradio/device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/device', locale `uk': Unable to store a value at key '/schemas/apps/gnomeradio/device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/device', locale `nl': Unable to store a value at key '/schemas/apps/gnomeradio/device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/device', locale `zh_TW': Unable to store a value at key '/schemas/apps/gnomeradio/device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/device', locale `ar': Unable to store a value at key '/schemas/apps/gnomeradio/device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/device', locale `lv': Unable to store a value at key '/schemas/apps/gnomeradio/device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/device', locale `pl': Unable to store a value at key '/schemas/apps/gnomeradio/device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/device', locale `cs': Unable to store a value at key '/schemas/apps/gnomeradio/device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/device', locale `pt': Unable to store a value at key '/schemas/apps/gnomeradio/device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/device', locale `es': Unable to store a value at key '/schemas/apps/gnomeradio/device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/device', locale `eu': Unable to store a value at key '/schemas/apps/gnomeradio/device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/device', locale `vi': Unable to store a value at key '/schemas/apps/gnomeradio/device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/device', locale `ru': Unable to store a value at key '/schemas/apps/gnomeradio/device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/device', locale `en_CA': Unable to store a value at key '/schemas/apps/gnomeradio/device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/device', locale `tr': Unable to store a value at key '/schemas/apps/gnomeradio/device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/device', locale `be': Unable to store a value at key '/schemas/apps/gnomeradio/device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/device', locale `da': Unable to store a value at key '/schemas/apps/gnomeradio/device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/device', locale `it': Unable to store a value at key '/schemas/apps/gnomeradio/device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/device', locale `mk': Unable to store a value at key '/schemas/apps/gnomeradio/device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/device', locale `de': Unable to store a value at key '/schemas/apps/gnomeradio/device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/device', locale `mn': Unable to store a value at key '/schemas/apps/gnomeradio/device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/device', locale `pt_BR': Unable to store a value at key '/schemas/apps/gnomeradio/device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/device', locale `en_GB': Unable to store a value at key '/schemas/apps/gnomeradio/device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/device', locale `ms': Unable to store a value at key '/schemas/apps/gnomeradio/device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/device', locale `bg': Unable to store a value at key '/schemas/apps/gnomeradio/device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/device', locale `fi': Unable to store a value at key '/schemas/apps/gnomeradio/device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/gnomeradio/driver' to key `/apps/gnomeradio/driver' WARNING: failed to install schema `/schemas/apps/gnomeradio/driver', locale `cs': Unable to store a value at key '/schemas/apps/gnomeradio/driver', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/driver', locale `C': Unable to store a value at key '/schemas/apps/gnomeradio/driver', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/driver', locale `es': Unable to store a value at key '/schemas/apps/gnomeradio/driver', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/driver', locale `it': Unable to store a value at key '/schemas/apps/gnomeradio/driver', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/driver', locale `eu': Unable to store a value at key '/schemas/apps/gnomeradio/driver', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/driver', locale `sv': Unable to store a value at key '/schemas/apps/gnomeradio/driver', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/gnomeradio/mixer' to key `/apps/gnomeradio/mixer' WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer', locale `he': Unable to store a value at key '/schemas/apps/gnomeradio/mixer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer', locale `ja': Unable to store a value at key '/schemas/apps/gnomeradio/mixer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer', locale `zh_CN': Unable to store a value at key '/schemas/apps/gnomeradio/mixer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer', locale `sk': Unable to store a value at key '/schemas/apps/gnomeradio/mixer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer', locale `sr@Latn': Unable to store a value at key '/schemas/apps/gnomeradio/mixer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer', locale `C': Unable to store a value at key '/schemas/apps/gnomeradio/mixer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer', locale `fr': Unable to store a value at key '/schemas/apps/gnomeradio/mixer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer', locale `sr': Unable to store a value at key '/schemas/apps/gnomeradio/mixer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer', locale `dz': Unable to store a value at key '/schemas/apps/gnomeradio/mixer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer', locale `nb': Unable to store a value at key '/schemas/apps/gnomeradio/mixer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer', locale `hr': Unable to store a value at key '/schemas/apps/gnomeradio/mixer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer', locale `ca': Unable to store a value at key '/schemas/apps/gnomeradio/mixer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer', locale `sv': Unable to store a value at key '/schemas/apps/gnomeradio/mixer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer', locale `pa': Unable to store a value at key '/schemas/apps/gnomeradio/mixer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer', locale `hu': Unable to store a value at key '/schemas/apps/gnomeradio/mixer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer', locale `uk': Unable to store a value at key '/schemas/apps/gnomeradio/mixer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer', locale `nl': Unable to store a value at key '/schemas/apps/gnomeradio/mixer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer', locale `zh_TW': Unable to store a value at key '/schemas/apps/gnomeradio/mixer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer', locale `lv': Unable to store a value at key '/schemas/apps/gnomeradio/mixer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer', locale `pl': Unable to store a value at key '/schemas/apps/gnomeradio/mixer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer', locale `cs': Unable to store a value at key '/schemas/apps/gnomeradio/mixer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer', locale `pt': Unable to store a value at key '/schemas/apps/gnomeradio/mixer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer', locale `es': Unable to store a value at key '/schemas/apps/gnomeradio/mixer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer', locale `eu': Unable to store a value at key '/schemas/apps/gnomeradio/mixer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer', locale `vi': Unable to store a value at key '/schemas/apps/gnomeradio/mixer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer', locale `ru': Unable to store a value at key '/schemas/apps/gnomeradio/mixer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer', locale `en_CA': Unable to store a value at key '/schemas/apps/gnomeradio/mixer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer', locale `tr': Unable to store a value at key '/schemas/apps/gnomeradio/mixer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer', locale `be': Unable to store a value at key '/schemas/apps/gnomeradio/mixer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer', locale `da': Unable to store a value at key '/schemas/apps/gnomeradio/mixer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer', locale `it': Unable to store a value at key '/schemas/apps/gnomeradio/mixer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer', locale `mk': Unable to store a value at key '/schemas/apps/gnomeradio/mixer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer', locale `de': Unable to store a value at key '/schemas/apps/gnomeradio/mixer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer', locale `mn': Unable to store a value at key '/schemas/apps/gnomeradio/mixer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer', locale `pt_BR': Unable to store a value at key '/schemas/apps/gnomeradio/mixer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer', locale `en_GB': Unable to store a value at key '/schemas/apps/gnomeradio/mixer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer', locale `ms': Unable to store a value at key '/schemas/apps/gnomeradio/mixer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer', locale `bg': Unable to store a value at key '/schemas/apps/gnomeradio/mixer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer', locale `fi': Unable to store a value at key '/schemas/apps/gnomeradio/mixer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/gnomeradio/mixer-device' to key `/apps/gnomeradio/mixer-device' WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer-device', locale `he': Unable to store a value at key '/schemas/apps/gnomeradio/mixer-device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer-device', locale `ja': Unable to store a value at key '/schemas/apps/gnomeradio/mixer-device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer-device', locale `zh_CN': Unable to store a value at key '/schemas/apps/gnomeradio/mixer-device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer-device', locale `sr@Latn': Unable to store a value at key '/schemas/apps/gnomeradio/mixer-device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer-device', locale `C': Unable to store a value at key '/schemas/apps/gnomeradio/mixer-device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer-device', locale `fr': Unable to store a value at key '/schemas/apps/gnomeradio/mixer-device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer-device', locale `sr': Unable to store a value at key '/schemas/apps/gnomeradio/mixer-device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer-device', locale `dz': Unable to store a value at key '/schemas/apps/gnomeradio/mixer-device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer-device', locale `nb': Unable to store a value at key '/schemas/apps/gnomeradio/mixer-device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer-device', locale `hr': Unable to store a value at key '/schemas/apps/gnomeradio/mixer-device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer-device', locale `ca': Unable to store a value at key '/schemas/apps/gnomeradio/mixer-device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer-device', locale `sv': Unable to store a value at key '/schemas/apps/gnomeradio/mixer-device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer-device', locale `pa': Unable to store a value at key '/schemas/apps/gnomeradio/mixer-device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer-device', locale `hu': Unable to store a value at key '/schemas/apps/gnomeradio/mixer-device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer-device', locale `uk': Unable to store a value at key '/schemas/apps/gnomeradio/mixer-device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer-device', locale `nl': Unable to store a value at key '/schemas/apps/gnomeradio/mixer-device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer-device', locale `zh_TW': Unable to store a value at key '/schemas/apps/gnomeradio/mixer-device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer-device', locale `lv': Unable to store a value at key '/schemas/apps/gnomeradio/mixer-device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer-device', locale `pl': Unable to store a value at key '/schemas/apps/gnomeradio/mixer-device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer-device', locale `cs': Unable to store a value at key '/schemas/apps/gnomeradio/mixer-device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer-device', locale `pt': Unable to store a value at key '/schemas/apps/gnomeradio/mixer-device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer-device', locale `es': Unable to store a value at key '/schemas/apps/gnomeradio/mixer-device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer-device', locale `eu': Unable to store a value at key '/schemas/apps/gnomeradio/mixer-device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer-device', locale `vi': Unable to store a value at key '/schemas/apps/gnomeradio/mixer-device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer-device', locale `ru': Unable to store a value at key '/schemas/apps/gnomeradio/mixer-device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer-device', locale `en_CA': Unable to store a value at key '/schemas/apps/gnomeradio/mixer-device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer-device', locale `tr': Unable to store a value at key '/schemas/apps/gnomeradio/mixer-device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer-device', locale `be': Unable to store a value at key '/schemas/apps/gnomeradio/mixer-device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer-device', locale `da': Unable to store a value at key '/schemas/apps/gnomeradio/mixer-device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer-device', locale `it': Unable to store a value at key '/schemas/apps/gnomeradio/mixer-device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer-device', locale `mk': Unable to store a value at key '/schemas/apps/gnomeradio/mixer-device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer-device', locale `de': Unable to store a value at key '/schemas/apps/gnomeradio/mixer-device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer-device', locale `mn': Unable to store a value at key '/schemas/apps/gnomeradio/mixer-device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer-device', locale `pt_BR': Unable to store a value at key '/schemas/apps/gnomeradio/mixer-device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer-device', locale `en_GB': Unable to store a value at key '/schemas/apps/gnomeradio/mixer-device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer-device', locale `ms': Unable to store a value at key '/schemas/apps/gnomeradio/mixer-device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer-device', locale `bg': Unable to store a value at key '/schemas/apps/gnomeradio/mixer-device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/mixer-device', locale `fi': Unable to store a value at key '/schemas/apps/gnomeradio/mixer-device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/gnomeradio/presets/presets' to key `/apps/gnomeradio/presets/presets' WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/presets', locale `sr@Latn': Unable to store a value at key '/schemas/apps/gnomeradio/presets/presets', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/presets', locale `he': Unable to store a value at key '/schemas/apps/gnomeradio/presets/presets', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/presets', locale `ja': Unable to store a value at key '/schemas/apps/gnomeradio/presets/presets', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/presets', locale `zh_CN': Unable to store a value at key '/schemas/apps/gnomeradio/presets/presets', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/presets', locale `C': Unable to store a value at key '/schemas/apps/gnomeradio/presets/presets', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/presets', locale `fr': Unable to store a value at key '/schemas/apps/gnomeradio/presets/presets', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/presets', locale `sr': Unable to store a value at key '/schemas/apps/gnomeradio/presets/presets', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/presets', locale `dz': Unable to store a value at key '/schemas/apps/gnomeradio/presets/presets', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/presets', locale `nb': Unable to store a value at key '/schemas/apps/gnomeradio/presets/presets', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/presets', locale `hr': Unable to store a value at key '/schemas/apps/gnomeradio/presets/presets', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/presets', locale `ca': Unable to store a value at key '/schemas/apps/gnomeradio/presets/presets', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/presets', locale `sv': Unable to store a value at key '/schemas/apps/gnomeradio/presets/presets', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/presets', locale `hu': Unable to store a value at key '/schemas/apps/gnomeradio/presets/presets', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/presets', locale `uk': Unable to store a value at key '/schemas/apps/gnomeradio/presets/presets', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/presets', locale `nl': Unable to store a value at key '/schemas/apps/gnomeradio/presets/presets', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/presets', locale `zh_TW': Unable to store a value at key '/schemas/apps/gnomeradio/presets/presets', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/presets', locale `lv': Unable to store a value at key '/schemas/apps/gnomeradio/presets/presets', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/presets', locale `pl': Unable to store a value at key '/schemas/apps/gnomeradio/presets/presets', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/presets', locale `cs': Unable to store a value at key '/schemas/apps/gnomeradio/presets/presets', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/presets', locale `pt': Unable to store a value at key '/schemas/apps/gnomeradio/presets/presets', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/presets', locale `es': Unable to store a value at key '/schemas/apps/gnomeradio/presets/presets', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/presets', locale `eu': Unable to store a value at key '/schemas/apps/gnomeradio/presets/presets', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/presets', locale `vi': Unable to store a value at key '/schemas/apps/gnomeradio/presets/presets', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/presets', locale `ru': Unable to store a value at key '/schemas/apps/gnomeradio/presets/presets', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/presets', locale `en_CA': Unable to store a value at key '/schemas/apps/gnomeradio/presets/presets', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/presets', locale `tr': Unable to store a value at key '/schemas/apps/gnomeradio/presets/presets', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/presets', locale `be': Unable to store a value at key '/schemas/apps/gnomeradio/presets/presets', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/presets', locale `da': Unable to store a value at key '/schemas/apps/gnomeradio/presets/presets', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/presets', locale `it': Unable to store a value at key '/schemas/apps/gnomeradio/presets/presets', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/presets', locale `mk': Unable to store a value at key '/schemas/apps/gnomeradio/presets/presets', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/presets', locale `de': Unable to store a value at key '/schemas/apps/gnomeradio/presets/presets', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/presets', locale `mn': Unable to store a value at key '/schemas/apps/gnomeradio/presets/presets', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/presets', locale `pt_BR': Unable to store a value at key '/schemas/apps/gnomeradio/presets/presets', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/presets', locale `en_GB': Unable to store a value at key '/schemas/apps/gnomeradio/presets/presets', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/presets', locale `ms': Unable to store a value at key '/schemas/apps/gnomeradio/presets/presets', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/presets', locale `bg': Unable to store a value at key '/schemas/apps/gnomeradio/presets/presets', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/presets', locale `fi': Unable to store a value at key '/schemas/apps/gnomeradio/presets/presets', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/gnomeradio/presets/last' to key `/apps/gnomeradio/presets/last' WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/last', locale `sr@Latn': Unable to store a value at key '/schemas/apps/gnomeradio/presets/last', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/last', locale `he': Unable to store a value at key '/schemas/apps/gnomeradio/presets/last', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/last', locale `ja': Unable to store a value at key '/schemas/apps/gnomeradio/presets/last', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/last', locale `zh_CN': Unable to store a value at key '/schemas/apps/gnomeradio/presets/last', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/last', locale `C': Unable to store a value at key '/schemas/apps/gnomeradio/presets/last', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/last', locale `fr': Unable to store a value at key '/schemas/apps/gnomeradio/presets/last', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/last', locale `sr': Unable to store a value at key '/schemas/apps/gnomeradio/presets/last', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/last', locale `dz': Unable to store a value at key '/schemas/apps/gnomeradio/presets/last', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/last', locale `nb': Unable to store a value at key '/schemas/apps/gnomeradio/presets/last', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/last', locale `hr': Unable to store a value at key '/schemas/apps/gnomeradio/presets/last', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/last', locale `ca': Unable to store a value at key '/schemas/apps/gnomeradio/presets/last', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/last', locale `sv': Unable to store a value at key '/schemas/apps/gnomeradio/presets/last', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/last', locale `hu': Unable to store a value at key '/schemas/apps/gnomeradio/presets/last', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/last', locale `uk': Unable to store a value at key '/schemas/apps/gnomeradio/presets/last', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/last', locale `nl': Unable to store a value at key '/schemas/apps/gnomeradio/presets/last', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/last', locale `zh_TW': Unable to store a value at key '/schemas/apps/gnomeradio/presets/last', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/last', locale `lv': Unable to store a value at key '/schemas/apps/gnomeradio/presets/last', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/last', locale `pl': Unable to store a value at key '/schemas/apps/gnomeradio/presets/last', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/last', locale `cs': Unable to store a value at key '/schemas/apps/gnomeradio/presets/last', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/last', locale `pt': Unable to store a value at key '/schemas/apps/gnomeradio/presets/last', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/last', locale `es': Unable to store a value at key '/schemas/apps/gnomeradio/presets/last', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/last', locale `eu': Unable to store a value at key '/schemas/apps/gnomeradio/presets/last', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/last', locale `vi': Unable to store a value at key '/schemas/apps/gnomeradio/presets/last', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/last', locale `ru': Unable to store a value at key '/schemas/apps/gnomeradio/presets/last', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/last', locale `en_CA': Unable to store a value at key '/schemas/apps/gnomeradio/presets/last', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/last', locale `tr': Unable to store a value at key '/schemas/apps/gnomeradio/presets/last', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/last', locale `be': Unable to store a value at key '/schemas/apps/gnomeradio/presets/last', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/last', locale `da': Unable to store a value at key '/schemas/apps/gnomeradio/presets/last', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/last', locale `it': Unable to store a value at key '/schemas/apps/gnomeradio/presets/last', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/last', locale `mk': Unable to store a value at key '/schemas/apps/gnomeradio/presets/last', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/last', locale `de': Unable to store a value at key '/schemas/apps/gnomeradio/presets/last', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/last', locale `mn': Unable to store a value at key '/schemas/apps/gnomeradio/presets/last', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/last', locale `pt_BR': Unable to store a value at key '/schemas/apps/gnomeradio/presets/last', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/last', locale `en_GB': Unable to store a value at key '/schemas/apps/gnomeradio/presets/last', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/last', locale `ms': Unable to store a value at key '/schemas/apps/gnomeradio/presets/last', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/last', locale `bg': Unable to store a value at key '/schemas/apps/gnomeradio/presets/last', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/presets/last', locale `fi': Unable to store a value at key '/schemas/apps/gnomeradio/presets/last', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/gnomeradio/recording/profile' to key `/apps/gnomeradio/recording/profile' WARNING: failed to install schema `/schemas/apps/gnomeradio/recording/profile', locale `de': Unable to store a value at key '/schemas/apps/gnomeradio/recording/profile', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/recording/profile', locale `fi': Unable to store a value at key '/schemas/apps/gnomeradio/recording/profile', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/recording/profile', locale `C': Unable to store a value at key '/schemas/apps/gnomeradio/recording/profile', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/recording/profile', locale `vi': Unable to store a value at key '/schemas/apps/gnomeradio/recording/profile', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/recording/profile', locale `cs': Unable to store a value at key '/schemas/apps/gnomeradio/recording/profile', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/recording/profile', locale `ru': Unable to store a value at key '/schemas/apps/gnomeradio/recording/profile', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/recording/profile', locale `es': Unable to store a value at key '/schemas/apps/gnomeradio/recording/profile', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/recording/profile', locale `fr': Unable to store a value at key '/schemas/apps/gnomeradio/recording/profile', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/recording/profile', locale `eu': Unable to store a value at key '/schemas/apps/gnomeradio/recording/profile', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/recording/profile', locale `sv': Unable to store a value at key '/schemas/apps/gnomeradio/recording/profile', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/recording/profile', locale `dz': Unable to store a value at key '/schemas/apps/gnomeradio/recording/profile', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/recording/profile', locale `en_GB': Unable to store a value at key '/schemas/apps/gnomeradio/recording/profile', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/recording/profile', locale `hu': Unable to store a value at key '/schemas/apps/gnomeradio/recording/profile', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/recording/profile', locale `ca': Unable to store a value at key '/schemas/apps/gnomeradio/recording/profile', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/recording/profile', locale `it': Unable to store a value at key '/schemas/apps/gnomeradio/recording/profile', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/recording/profile', locale `nl': Unable to store a value at key '/schemas/apps/gnomeradio/recording/profile', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnomeradio/recording/profile', locale `bg': Unable to store a value at key '/schemas/apps/gnomeradio/recording/profile', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf test -z "/etc/gconf/schemas" || mkdir -p -- "/var/uhubuild/work/install/etc/gconf/schemas" /bin/install -c -m 644 'gnomeradio.schemas' '/var/uhubuild/work/install/etc/gconf/schemas/gnomeradio.schemas' make[3]: Leaving directory `/var/uhubuild/work/compile/data' make[2]: Leaving directory `/var/uhubuild/work/compile/data' make[1]: Leaving directory `/var/uhubuild/work/compile/data' Making install in po make[1]: Entering directory `/var/uhubuild/work/compile/po' /var/uhubuild/work/compile/install-sh -d /var/uhubuild/work/install/usr/share/locale linguas="ar am az be bg ca cs da de dz en_CA en_GB es eu fi fr he hr hu it ja lv mk ml mn ms nb nl oc pa pl pt pt_BR ru rw sk sr sr@Latn sv tr uk vi zh_CN zh_TW "; \ for lang in $linguas; do \ dir=/var/uhubuild/work/install/usr/share/locale/$lang/LC_MESSAGES; \ /var/uhubuild/work/compile/install-sh -d $dir; \ if test -r $lang.gmo; then \ /bin/install -c -m 644 $lang.gmo $dir/gnomeradio.mo; \ echo "installing $lang.gmo as $dir/gnomeradio.mo"; \ else \ /bin/install -c -m 644 ./$lang.gmo $dir/gnomeradio.mo; \ echo "installing ./$lang.gmo as" \ "$dir/gnomeradio.mo"; \ fi; \ if test -r $lang.gmo.m; then \ /bin/install -c -m 644 $lang.gmo.m $dir/gnomeradio.mo.m; \ echo "installing $lang.gmo.m as $dir/gnomeradio.mo.m"; \ else \ if test -r ./$lang.gmo.m ; then \ /bin/install -c -m 644 ./$lang.gmo.m \ $dir/gnomeradio.mo.m; \ echo "installing ./$lang.gmo.m as" \ "$dir/gnomeradio.mo.m"; \ else \ true; \ fi; \ fi; \ done installing ar.gmo as /var/uhubuild/work/install/usr/share/locale/ar/LC_MESSAGES/gnomeradio.mo installing am.gmo as /var/uhubuild/work/install/usr/share/locale/am/LC_MESSAGES/gnomeradio.mo installing az.gmo as /var/uhubuild/work/install/usr/share/locale/az/LC_MESSAGES/gnomeradio.mo installing be.gmo as /var/uhubuild/work/install/usr/share/locale/be/LC_MESSAGES/gnomeradio.mo installing bg.gmo as /var/uhubuild/work/install/usr/share/locale/bg/LC_MESSAGES/gnomeradio.mo installing ca.gmo as /var/uhubuild/work/install/usr/share/locale/ca/LC_MESSAGES/gnomeradio.mo installing cs.gmo as /var/uhubuild/work/install/usr/share/locale/cs/LC_MESSAGES/gnomeradio.mo installing da.gmo as /var/uhubuild/work/install/usr/share/locale/da/LC_MESSAGES/gnomeradio.mo installing de.gmo as /var/uhubuild/work/install/usr/share/locale/de/LC_MESSAGES/gnomeradio.mo installing dz.gmo as /var/uhubuild/work/install/usr/share/locale/dz/LC_MESSAGES/gnomeradio.mo installing en_CA.gmo as /var/uhubuild/work/install/usr/share/locale/en_CA/LC_MESSAGES/gnomeradio.mo installing en_GB.gmo as /var/uhubuild/work/install/usr/share/locale/en_GB/LC_MESSAGES/gnomeradio.mo installing es.gmo as /var/uhubuild/work/install/usr/share/locale/es/LC_MESSAGES/gnomeradio.mo installing eu.gmo as /var/uhubuild/work/install/usr/share/locale/eu/LC_MESSAGES/gnomeradio.mo installing fi.gmo as /var/uhubuild/work/install/usr/share/locale/fi/LC_MESSAGES/gnomeradio.mo installing fr.gmo as /var/uhubuild/work/install/usr/share/locale/fr/LC_MESSAGES/gnomeradio.mo installing he.gmo as /var/uhubuild/work/install/usr/share/locale/he/LC_MESSAGES/gnomeradio.mo installing hr.gmo as /var/uhubuild/work/install/usr/share/locale/hr/LC_MESSAGES/gnomeradio.mo installing hu.gmo as /var/uhubuild/work/install/usr/share/locale/hu/LC_MESSAGES/gnomeradio.mo installing it.gmo as /var/uhubuild/work/install/usr/share/locale/it/LC_MESSAGES/gnomeradio.mo installing ja.gmo as /var/uhubuild/work/install/usr/share/locale/ja/LC_MESSAGES/gnomeradio.mo installing lv.gmo as /var/uhubuild/work/install/usr/share/locale/lv/LC_MESSAGES/gnomeradio.mo installing mk.gmo as /var/uhubuild/work/install/usr/share/locale/mk/LC_MESSAGES/gnomeradio.mo installing ml.gmo as /var/uhubuild/work/install/usr/share/locale/ml/LC_MESSAGES/gnomeradio.mo installing mn.gmo as /var/uhubuild/work/install/usr/share/locale/mn/LC_MESSAGES/gnomeradio.mo installing ms.gmo as /var/uhubuild/work/install/usr/share/locale/ms/LC_MESSAGES/gnomeradio.mo installing nb.gmo as /var/uhubuild/work/install/usr/share/locale/nb/LC_MESSAGES/gnomeradio.mo installing nl.gmo as /var/uhubuild/work/install/usr/share/locale/nl/LC_MESSAGES/gnomeradio.mo installing oc.gmo as /var/uhubuild/work/install/usr/share/locale/oc/LC_MESSAGES/gnomeradio.mo installing pa.gmo as /var/uhubuild/work/install/usr/share/locale/pa/LC_MESSAGES/gnomeradio.mo installing pl.gmo as /var/uhubuild/work/install/usr/share/locale/pl/LC_MESSAGES/gnomeradio.mo installing pt.gmo as /var/uhubuild/work/install/usr/share/locale/pt/LC_MESSAGES/gnomeradio.mo installing pt_BR.gmo as /var/uhubuild/work/install/usr/share/locale/pt_BR/LC_MESSAGES/gnomeradio.mo installing ru.gmo as /var/uhubuild/work/install/usr/share/locale/ru/LC_MESSAGES/gnomeradio.mo installing rw.gmo as /var/uhubuild/work/install/usr/share/locale/rw/LC_MESSAGES/gnomeradio.mo installing sk.gmo as /var/uhubuild/work/install/usr/share/locale/sk/LC_MESSAGES/gnomeradio.mo installing sr.gmo as /var/uhubuild/work/install/usr/share/locale/sr/LC_MESSAGES/gnomeradio.mo installing sr@Latn.gmo as /var/uhubuild/work/install/usr/share/locale/sr@Latn/LC_MESSAGES/gnomeradio.mo installing sv.gmo as /var/uhubuild/work/install/usr/share/locale/sv/LC_MESSAGES/gnomeradio.mo installing tr.gmo as /var/uhubuild/work/install/usr/share/locale/tr/LC_MESSAGES/gnomeradio.mo installing uk.gmo as /var/uhubuild/work/install/usr/share/locale/uk/LC_MESSAGES/gnomeradio.mo installing vi.gmo as /var/uhubuild/work/install/usr/share/locale/vi/LC_MESSAGES/gnomeradio.mo installing zh_CN.gmo as /var/uhubuild/work/install/usr/share/locale/zh_CN/LC_MESSAGES/gnomeradio.mo installing zh_TW.gmo as /var/uhubuild/work/install/usr/share/locale/zh_TW/LC_MESSAGES/gnomeradio.mo make[1]: Leaving directory `/var/uhubuild/work/compile/po' Making install in src make[1]: Entering directory `/var/uhubuild/work/compile/src' make[2]: Entering directory `/var/uhubuild/work/compile/src' test -z "/usr/bin" || mkdir -p -- "/var/uhubuild/work/install/usr/bin" /bin/sh ../libtool --mode=install /bin/install -c 'gnomeradio' '/var/uhubuild/work/install/usr/bin/gnomeradio' /bin/install -c gnomeradio /var/uhubuild/work/install/usr/bin/gnomeradio make[2]: Nothing to be done for `install-data-am'. make[2]: Leaving directory `/var/uhubuild/work/compile/src' make[1]: Leaving directory `/var/uhubuild/work/compile/src' make[1]: Entering directory `/var/uhubuild/work/compile' make[2]: Entering directory `/var/uhubuild/work/compile' make[2]: Nothing to be done for `install-exec-am'. make[2]: Nothing to be done for `install-data-am'. make[2]: Leaving directory `/var/uhubuild/work/compile' make[1]: Leaving directory `/var/uhubuild/work/compile' strip...  ./usr/bin/gnomeradio doc... move-compile... install-snapshot...  (kihagyva) python... addons... cleanup... optipng...  /var/uhubuild/work/install/usr/share/icons/hicolor/16x16/apps/gnomeradio.png OK /var/uhubuild/work/install/usr/share/icons/hicolor/24x24/apps/gnomeradio.png OK /var/uhubuild/work/install/usr/share/icons/hicolor/22x22/apps/gnomeradio.png OK /var/uhubuild/work/install/usr/share/icons/hicolor/32x32/apps/gnomeradio.png OK /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/C/figures/misc-controls.png OK /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/C/figures/volume-controls.png OK /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/oc/figures/misc-controls.png OK /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/oc/figures/presets-box.png OK /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/C/figures/presets-box.png OK /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/C/figures/status-window.png OK /var/uhubuild/work/install/usr/share/icons/hicolor/48x48/apps/gnomeradio.png OK /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/C/figures/freq-controls.png OK /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/es/figures/misc-controls.png OK /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/oc/figures/volume-controls.png OK /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/oc/figures/freq-controls.png OK /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/oc/figures/status-window.png OK /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/C/figures/recording-wav.png OK /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/es/figures/presets-box.png OK /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/C/figures/recording-mp3.png OK /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/oc/figures/recording-wav.png OK /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/C/figures/recording_status.png OK /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/C/figures/settings-misc.png OK /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/es/figures/volume-controls.png OK /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/oc/figures/recording-mp3.png OK /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/oc/figures/recording_status.png OK /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/es/figures/recording-wav.png OK /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/oc/figures/settings-misc.png OK /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/es/figures/recording-mp3.png OK /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/C/figures/recording-general.png OK /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/sv/figures/misc-controls.png OK /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/oc/figures/recording-general.png OK /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/es/figures/settings-misc.png OK /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/sv/figures/presets-box.png OK /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/es/figures/status-window.png OK /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/sv/figures/volume-controls.png OK /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/C/figures/settings-presets.png OK /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/es/figures/recording-general.png OK /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/es/figures/freq-controls.png OK /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/sv/figures/status-window.png OK /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/fr/figures/misc-controls.png OK /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/oc/figures/settings-presets.png OK /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/sv/figures/freq-controls.png OK /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/fr/figures/volume-controls.png OK /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/fr/figures/presets-box.png OK /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/sv/figures/recording-mp3.png OK /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/sv/figures/recording-wav.png OK /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/fr/figures/freq-controls.png OK /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/fr/figures/status-window.png OK /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/es/figures/recording_status.png OK /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/es/figures/settings-presets.png OK /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/sv/figures/settings-misc.png OK /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/fr/figures/recording-mp3.png OK /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/fr/figures/recording-wav.png OK /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/sv/figures/recording-general.png OK /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/fr/figures/recording-general.png OK /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/sv/figures/settings-presets.png OK /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/fr/figures/settings-misc.png OK /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/fr/figures/settings-presets.png OK /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/sv/figures/recording_status.png OK /var/uhubuild/work/install/usr/share/gnome/help/gnomeradio/fr/figures/recording_status.png OK split... dirs... users-groups... changelog... suid_wrapper... perms... scripts... remove-misc... man... info... mo... timestamps... menu... depends... shlibs... fhs... conffiles... buildinfo... control... pack...  gnomeradio... logpack... uhubuild-build véget ért, kimásztunk a chroot alól. Fájlrendszerek leválasztása: dev , proc , ccache , forrás OK LogPack kimásolása /var/build/result/dev/gnomeradio alá... OK Elkészült csomagok kimásolása /var/build/result/dev/gnomeradio alá... OK Kész :-) Sending back ccache files... done. Build end: 2014. júl. 9., szerda, 16.42.48 UTC