RUN: /bin/echo ['echo', 'Forking build subprocess...'] Forking build subprocess... RUN: /usr/share/launchpad-buildd/slavebin/unpack-chroot ['unpack-chroot', 'a5bf95798123a7de5b0ac6630436238ddb2ef38c', '/home/buildd/filecache-default/25121a7572f17d65ba7d4c7db29be92bd6e19436'] Synching the system clock with the buildd NTP service... 10 Apr 18:32:51 ntpdate[27417]: adjust time server 10.211.37.1 offset -0.000287 sec Unpacking chroot for build a5bf95798123a7de5b0ac6630436238ddb2ef38c RUN: /usr/share/launchpad-buildd/slavebin/mount-chroot ['mount-chroot', 'a5bf95798123a7de5b0ac6630436238ddb2ef38c'] Mounting chroot for build a5bf95798123a7de5b0ac6630436238ddb2ef38c RUN: /usr/share/launchpad-buildd/slavebin/override-sources-list ['override-sources-list', 'a5bf95798123a7de5b0ac6630436238ddb2ef38c', 'deb http://ftpmaster.internal/ubuntu natty main universe'] Overriding sources.list in build-a5bf95798123a7de5b0ac6630436238ddb2ef38c RUN: /usr/share/launchpad-buildd/slavebin/update-debian-chroot ['update-debian-chroot', 'a5bf95798123a7de5b0ac6630436238ddb2ef38c', 'i386'] Updating debian chroot for build a5bf95798123a7de5b0ac6630436238ddb2ef38c Get:1 http://ftpmaster.internal natty Release.gpg [198 B] Ign http://ftpmaster.internal/ubuntu/ natty/main Translation-en Ign http://ftpmaster.internal/ubuntu/ natty/universe Translation-en Get:2 http://ftpmaster.internal natty Release [39.8 kB] Get:3 http://ftpmaster.internal natty/main i386 Packages [1558 kB] Get:4 http://ftpmaster.internal natty/universe i386 Packages [6027 kB] Fetched 7625 kB in 8s (908 kB/s) Reading package lists... Reading package lists... Building dependency tree... Reading state information... The following NEW packages will be installed: libpam-modules-bin multiarch-support The following packages will be upgraded: adduser apt apt-transport-https base-files bash binutils bsdutils busybox-initramfs bzip2 coreutils cpio cpp cpp-4.5 debconf debconf-i18n dpkg dpkg-dev e2fslibs e2fsprogs findutils g++ g++-4.5 gcc gcc-4.5 gcc-4.5-base gnupg gpgv initramfs-tools initramfs-tools-bin initscripts klibc-utils libacl1 libattr1 libblkid1 libbz2-1.0 libc-bin libc-dev-bin libc6 libc6-dev libcomerr2 libdb4.8 libdbus-1-3 libdpkg-perl libdrm-intel1 libdrm-nouveau1a libdrm-radeon1 libdrm2 libgcc1 libgcrypt11 libgdbm3 libglib2.0-0 libgmp3c2 libgmpxx4ldbl libgnutls26 libgomp1 libgpg-error0 libgssapi-krb5-2 libk5crypto3 libkeyutils1 libklibc libkrb5-3 libkrb5support0 libldap-2.4-2 libmpc2 libmpfr4 libnih-dbus1 libnih1 libpam-modules libpam-runtime libpam0g libpcre3 libplymouth2 libpng12-0 libreadline6 libselinux1 libss2 libssl0.9.8 libstdc++6 libstdc++6-4.5-dev libtasn1-3 libudev0 libusb-0.1-4 libuuid1 linux-libc-dev locales login make module-init-tools mount mountall netbase openssl passwd perl perl-base perl-modules pkg-create-dbgsym pkgbinarymangler plymouth procps python2.7-minimal readline-common sysv-rc sysvinit-utils tzdata udev upstart util-linux zlib1g 109 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. Need to get 65.0 MB of archives. After this operation, 1061 kB of additional disk space will be used. WARNING: The following packages cannot be authenticated! libnih-dbus1 libnih1 libc6-dev libc-dev-bin libc-bin libc6 multiarch-support libdbus-1-3 linux-libc-dev libgomp1 gcc-4.5-base libgcc1 cpp-4.5 libstdc++6-4.5-dev g++-4.5 gcc-4.5 libstdc++6 libgmp3c2 libgmpxx4ldbl libmpfr4 libmpc2 zlib1g binutils debconf-i18n debconf tzdata libpam0g libselinux1 libpam-modules-bin libpam-modules base-files bash coreutils dpkg e2fslibs e2fsprogs findutils login mount perl-modules bzip2 libbz2-1.0 libdb4.8 libgdbm3 perl perl-base sysvinit-utils sysv-rc passwd initscripts libudev0 libattr1 libacl1 libpcre3 libglib2.0-0 libusb-0.1-4 module-init-tools initramfs-tools initramfs-tools-bin klibc-utils libklibc busybox-initramfs cpio procps adduser util-linux udev libdrm2 libdrm-intel1 libdrm-nouveau1a libdrm-radeon1 plymouth libpng12-0 libplymouth2 mountall upstart bsdutils libuuid1 libblkid1 libcomerr2 libss2 libgpg-error0 libgcrypt11 libtasn1-3 libgnutls26 libkeyutils1 libk5crypto3 libgssapi-krb5-2 libkrb5-3 libkrb5support0 apt libpam-runtime libssl0.9.8 python2.7-minimal readline-common libreadline6 gpgv gnupg netbase locales apt-transport-https libldap-2.4-2 openssl cpp dpkg-dev libdpkg-perl make gcc g++ pkg-create-dbgsym pkgbinarymangler Authentication warning overridden. Get:1 http://ftpmaster.internal/ubuntu/ natty/main libnih-dbus1 i386 1.0.3-1ubuntu1 [13.1 kB] Get:2 http://ftpmaster.internal/ubuntu/ natty/main libnih1 i386 1.0.3-1ubuntu1 [45.8 kB] Get:3 http://ftpmaster.internal/ubuntu/ natty/main libc6-dev i386 2.13-0ubuntu12 [4827 kB] Get:4 http://ftpmaster.internal/ubuntu/ natty/main libc-dev-bin i386 2.13-0ubuntu12 [77.0 kB] Get:5 http://ftpmaster.internal/ubuntu/ natty/main libc-bin i386 2.13-0ubuntu12 [906 kB] Get:6 http://ftpmaster.internal/ubuntu/ natty/main libc6 i386 2.13-0ubuntu12 [3653 kB] Get:7 http://ftpmaster.internal/ubuntu/ natty/main multiarch-support i386 2.13-0ubuntu12 [8204 B] Get:8 http://ftpmaster.internal/ubuntu/ natty/main libdbus-1-3 i386 1.4.6-1ubuntu6 [122 kB] Get:9 http://ftpmaster.internal/ubuntu/ natty/main linux-libc-dev i386 2.6.38-8.41 [772 kB] Get:10 http://ftpmaster.internal/ubuntu/ natty/main libgomp1 i386 4.5.2-8ubuntu2 [24.1 kB] Get:11 http://ftpmaster.internal/ubuntu/ natty/main gcc-4.5-base i386 4.5.2-8ubuntu2 [14.3 kB] Get:12 http://ftpmaster.internal/ubuntu/ natty/main libgcc1 i386 1:4.5.2-8ubuntu2 [51.5 kB] Get:13 http://ftpmaster.internal/ubuntu/ natty/main cpp-4.5 i386 4.5.2-8ubuntu2 [4154 kB] Get:14 http://ftpmaster.internal/ubuntu/ natty/main libstdc++6-4.5-dev i386 4.5.2-8ubuntu2 [1567 kB] Get:15 http://ftpmaster.internal/ubuntu/ natty/main g++-4.5 i386 4.5.2-8ubuntu2 [6015 kB] Get:16 http://ftpmaster.internal/ubuntu/ natty/main gcc-4.5 i386 4.5.2-8ubuntu2 [6887 kB] Get:17 http://ftpmaster.internal/ubuntu/ natty/main libstdc++6 i386 4.5.2-8ubuntu2 [333 kB] Get:18 http://ftpmaster.internal/ubuntu/ natty/main libgmp3c2 i386 2:4.3.2+dfsg-1ubuntu3 [319 kB] Get:19 http://ftpmaster.internal/ubuntu/ natty/main libgmpxx4ldbl i386 2:4.3.2+dfsg-1ubuntu3 [10.3 kB] Get:20 http://ftpmaster.internal/ubuntu/ natty/main libmpfr4 i386 3.0.0-7 [177 kB] Get:21 http://ftpmaster.internal/ubuntu/ natty/main libmpc2 i386 0.9-1 [37.4 kB] Get:22 http://ftpmaster.internal/ubuntu/ natty/main zlib1g i386 1:1.2.3.4.dfsg-3ubuntu3 [49.3 kB] Get:23 http://ftpmaster.internal/ubuntu/ natty/main binutils i386 2.21.0.20110327-2ubuntu2 [2170 kB] Get:24 http://ftpmaster.internal/ubuntu/ natty/main debconf-i18n all 1.5.36ubuntu4 [208 kB] Get:25 http://ftpmaster.internal/ubuntu/ natty/main debconf all 1.5.36ubuntu4 [140 kB] Get:26 http://ftpmaster.internal/ubuntu/ natty/main tzdata all 2011e-1 [772 kB] Get:27 http://ftpmaster.internal/ubuntu/ natty/main libpam0g i386 1.1.2-2ubuntu7 [51.4 kB] Get:28 http://ftpmaster.internal/ubuntu/ natty/main libselinux1 i386 2.0.96-1ubuntu2 [58.5 kB] Get:29 http://ftpmaster.internal/ubuntu/ natty/main libpam-modules-bin i386 1.1.2-2ubuntu7 [35.0 kB] Get:30 http://ftpmaster.internal/ubuntu/ natty/main libpam-modules i386 1.1.2-2ubuntu7 [263 kB] Get:31 http://ftpmaster.internal/ubuntu/ natty/main base-files i386 5.0.0ubuntu27 [54.3 kB] Get:32 http://ftpmaster.internal/ubuntu/ natty/main bash i386 4.2-0ubuntu3 [544 kB] Get:33 http://ftpmaster.internal/ubuntu/ natty/main coreutils i386 8.5-1ubuntu6 [1836 kB] Get:34 http://ftpmaster.internal/ubuntu/ natty/main dpkg i386 1.16.0~ubuntu6 [1848 kB] Get:35 http://ftpmaster.internal/ubuntu/ natty/main e2fslibs i386 1.41.14-1ubuntu3 [143 kB] Get:36 http://ftpmaster.internal/ubuntu/ natty/main e2fsprogs i386 1.41.14-1ubuntu3 [813 kB] Get:37 http://ftpmaster.internal/ubuntu/ natty/main findutils i386 4.4.2-1ubuntu3 [302 kB] Get:38 http://ftpmaster.internal/ubuntu/ natty/main login i386 1:4.1.4.2+svn3283-3ubuntu1 [279 kB] Get:39 http://ftpmaster.internal/ubuntu/ natty/main mount i386 2.17.2-9.1ubuntu4 [124 kB] Get:40 http://ftpmaster.internal/ubuntu/ natty/main perl-modules all 5.10.1-17ubuntu4 [3442 kB] Get:41 http://ftpmaster.internal/ubuntu/ natty/main bzip2 i386 1.0.5-6ubuntu1 [35.7 kB] Get:42 http://ftpmaster.internal/ubuntu/ natty/main libbz2-1.0 i386 1.0.5-6ubuntu1 [32.7 kB] Get:43 http://ftpmaster.internal/ubuntu/ natty/main libdb4.8 i386 4.8.30-5ubuntu2 [657 kB] Get:44 http://ftpmaster.internal/ubuntu/ natty/main libgdbm3 i386 1.8.3-9ubuntu1 [33.8 kB] Get:45 http://ftpmaster.internal/ubuntu/ natty/main perl i386 5.10.1-17ubuntu4 [3749 kB] Get:46 http://ftpmaster.internal/ubuntu/ natty/main perl-base i386 5.10.1-17ubuntu4 [928 kB] Get:47 http://ftpmaster.internal/ubuntu/ natty/main sysvinit-utils i386 2.87dsf-4ubuntu23 [50.7 kB] Get:48 http://ftpmaster.internal/ubuntu/ natty/main sysv-rc all 2.87dsf-4ubuntu23 [36.4 kB] Get:49 http://ftpmaster.internal/ubuntu/ natty/main passwd i386 1:4.1.4.2+svn3283-3ubuntu1 [871 kB] Get:50 http://ftpmaster.internal/ubuntu/ natty/main initscripts i386 2.87dsf-4ubuntu23 [32.1 kB] Get:51 http://ftpmaster.internal/ubuntu/ natty/main libudev0 i386 167-0ubuntu3 [26.6 kB] Get:52 http://ftpmaster.internal/ubuntu/ natty/main libattr1 i386 1:2.4.44-2ubuntu2 [10.1 kB] Get:53 http://ftpmaster.internal/ubuntu/ natty/main libacl1 i386 2.2.49-4ubuntu2 [16.3 kB] Get:54 http://ftpmaster.internal/ubuntu/ natty/main libpcre3 i386 8.12-3ubuntu2 [148 kB] Get:55 http://ftpmaster.internal/ubuntu/ natty/main libglib2.0-0 i386 2.28.5-0ubuntu1 [971 kB] Get:56 http://ftpmaster.internal/ubuntu/ natty/main libusb-0.1-4 i386 2:0.1.12-17 [15.1 kB] Get:57 http://ftpmaster.internal/ubuntu/ natty/main module-init-tools i386 3.12-1ubuntu6 [80.3 kB] Get:58 http://ftpmaster.internal/ubuntu/ natty/main initramfs-tools all 0.98.8ubuntu3 [52.6 kB] Get:59 http://ftpmaster.internal/ubuntu/ natty/main initramfs-tools-bin i386 0.98.8ubuntu3 [10.9 kB] Get:60 http://ftpmaster.internal/ubuntu/ natty/main klibc-utils i386 1.5.20-1ubuntu4 [153 kB] Get:61 http://ftpmaster.internal/ubuntu/ natty/main libklibc i386 1.5.20-1ubuntu4 [41.9 kB] Get:62 http://ftpmaster.internal/ubuntu/ natty/main busybox-initramfs i386 1:1.17.1-10ubuntu1 [148 kB] Get:63 http://ftpmaster.internal/ubuntu/ natty/main cpio i386 2.11-7ubuntu1 [104 kB] Get:64 http://ftpmaster.internal/ubuntu/ natty/main procps i386 1:3.2.8-10ubuntu3 [212 kB] Get:65 http://ftpmaster.internal/ubuntu/ natty/main adduser all 3.112+nmu1ubuntu5 [99.3 kB] Get:66 http://ftpmaster.internal/ubuntu/ natty/main util-linux i386 2.17.2-9.1ubuntu4 [481 kB] Get:67 http://ftpmaster.internal/ubuntu/ natty/main udev i386 167-0ubuntu3 [365 kB] Get:68 http://ftpmaster.internal/ubuntu/ natty/main libdrm2 i386 2.4.23-1ubuntu6 [22.6 kB] Get:69 http://ftpmaster.internal/ubuntu/ natty/main libdrm-intel1 i386 2.4.23-1ubuntu6 [23.8 kB] Get:70 http://ftpmaster.internal/ubuntu/ natty/main libdrm-nouveau1a i386 2.4.23-1ubuntu6 [14.0 kB] Get:71 http://ftpmaster.internal/ubuntu/ natty/main libdrm-radeon1 i386 2.4.23-1ubuntu6 [14.5 kB] Get:72 http://ftpmaster.internal/ubuntu/ natty/main plymouth i386 0.8.2-2ubuntu21 [112 kB] Get:73 http://ftpmaster.internal/ubuntu/ natty/main libpng12-0 i386 1.2.44-1ubuntu3 [126 kB] Get:74 http://ftpmaster.internal/ubuntu/ natty/main libplymouth2 i386 0.8.2-2ubuntu21 [79.7 kB] Get:75 http://ftpmaster.internal/ubuntu/ natty/main mountall i386 2.25 [44.8 kB] Get:76 http://ftpmaster.internal/ubuntu/ natty/main upstart i386 0.9.4-1ubuntu1 [254 kB] Get:77 http://ftpmaster.internal/ubuntu/ natty/main bsdutils i386 1:2.17.2-9.1ubuntu4 [31.8 kB] Get:78 http://ftpmaster.internal/ubuntu/ natty/main libuuid1 i386 2.17.2-9.1ubuntu4 [13.1 kB] Get:79 http://ftpmaster.internal/ubuntu/ natty/main libblkid1 i386 2.17.2-9.1ubuntu4 [60.4 kB] Get:80 http://ftpmaster.internal/ubuntu/ natty/main libcomerr2 i386 1.41.14-1ubuntu3 [52.9 kB] Get:81 http://ftpmaster.internal/ubuntu/ natty/main libss2 i386 1.41.14-1ubuntu3 [57.4 kB] Get:82 http://ftpmaster.internal/ubuntu/ natty/main libgpg-error0 i386 1.10-0.2ubuntu1 [14.2 kB] Get:83 http://ftpmaster.internal/ubuntu/ natty/main libgcrypt11 i386 1.4.6-4ubuntu2 [250 kB] Get:84 http://ftpmaster.internal/ubuntu/ natty/main libtasn1-3 i386 2.7-1ubuntu1 [41.9 kB] Get:85 http://ftpmaster.internal/ubuntu/ natty/main libgnutls26 i386 2.8.6-1ubuntu2 [365 kB] Get:86 http://ftpmaster.internal/ubuntu/ natty/main libkeyutils1 i386 1.4-4ubuntu2 [6424 B] Get:87 http://ftpmaster.internal/ubuntu/ natty/main libk5crypto3 i386 1.8.3+dfsg-5ubuntu2 [76.8 kB] Get:88 http://ftpmaster.internal/ubuntu/ natty/main libgssapi-krb5-2 i386 1.8.3+dfsg-5ubuntu2 [100 kB] Get:89 http://ftpmaster.internal/ubuntu/ natty/main libkrb5-3 i386 1.8.3+dfsg-5ubuntu2 [327 kB] Get:90 http://ftpmaster.internal/ubuntu/ natty/main libkrb5support0 i386 1.8.3+dfsg-5ubuntu2 [22.2 kB] Get:91 http://ftpmaster.internal/ubuntu/ natty/main apt i386 0.8.13.2ubuntu2 [2100 kB] Get:92 http://ftpmaster.internal/ubuntu/ natty/main libpam-runtime all 1.1.2-2ubuntu7 [42.7 kB] Get:93 http://ftpmaster.internal/ubuntu/ natty/main libssl0.9.8 i386 0.9.8o-5ubuntu1 [757 kB] Get:94 http://ftpmaster.internal/ubuntu/ natty/main python2.7-minimal i386 2.7.1-5ubuntu1 [1510 kB] Get:95 http://ftpmaster.internal/ubuntu/ natty/main readline-common all 6.2-0ubuntu1 [49.8 kB] Get:96 http://ftpmaster.internal/ubuntu/ natty/main libreadline6 i386 6.2-0ubuntu1 [120 kB] Get:97 http://ftpmaster.internal/ubuntu/ natty/main gpgv i386 1.4.11-3ubuntu1 [163 kB] Get:98 http://ftpmaster.internal/ubuntu/ natty/main gnupg i386 1.4.11-3ubuntu1 [748 kB] Get:99 http://ftpmaster.internal/ubuntu/ natty/main netbase all 4.45ubuntu1 [14.8 kB] Get:100 http://ftpmaster.internal/ubuntu/ natty/main locales all 2.13+git20100825-4 [3496 kB] Get:101 http://ftpmaster.internal/ubuntu/ natty/main apt-transport-https i386 0.8.13.2ubuntu2 [19.0 kB] Get:102 http://ftpmaster.internal/ubuntu/ natty/main libldap-2.4-2 i386 2.4.23-6ubuntu6 [160 kB] Get:103 http://ftpmaster.internal/ubuntu/ natty/main openssl i386 0.9.8o-5ubuntu1 [397 kB] Get:104 http://ftpmaster.internal/ubuntu/ natty/main cpp i386 4:4.5.2-1ubuntu1 [27.6 kB] Get:105 http://ftpmaster.internal/ubuntu/ natty/main dpkg-dev all 1.16.0~ubuntu6 [476 kB] Get:106 http://ftpmaster.internal/ubuntu/ natty/main libdpkg-perl all 1.16.0~ubuntu6 [183 kB] Get:107 http://ftpmaster.internal/ubuntu/ natty/main make i386 3.81-8ubuntu1 [109 kB] Get:108 http://ftpmaster.internal/ubuntu/ natty/main gcc i386 4:4.5.2-1ubuntu1 [5068 B] Get:109 http://ftpmaster.internal/ubuntu/ natty/main g++ i386 4:4.5.2-1ubuntu1 [1442 B] Get:110 http://ftpmaster.internal/ubuntu/ natty/main pkg-create-dbgsym all 0.48 [8096 B] Get:111 http://ftpmaster.internal/ubuntu/ natty/main pkgbinarymangler all 95 [23.3 kB] debconf: delaying package configuration, since apt-utils is not installed Fetched 65.0 MB in 3s (18.4 MB/s) (Reading database ... 13677 files and directories currently installed.) Preparing to replace libnih-dbus1 1.0.3-1 (using .../libnih-dbus1_1.0.3-1ubuntu1_i386.deb) ... Unpacking replacement libnih-dbus1 ... Preparing to replace libnih1 1.0.3-1 (using .../libnih1_1.0.3-1ubuntu1_i386.deb) ... Unpacking replacement libnih1 ... Preparing to replace libc6-dev 2.12.1-0ubuntu14 (using .../libc6-dev_2.13-0ubuntu12_i386.deb) ... Unpacking replacement libc6-dev ... Preparing to replace libc-dev-bin 2.12.1-0ubuntu14 (using .../libc-dev-bin_2.13-0ubuntu12_i386.deb) ... Unpacking replacement libc-dev-bin ... Preparing to replace libc-bin 2.12.1-0ubuntu14 (using .../libc-bin_2.13-0ubuntu12_i386.deb) ... Unpacking replacement libc-bin ... Setting up libc-bin (2.13-0ubuntu12) ... (Reading database ... 13700 files and directories currently installed.) Preparing to replace libc6 2.12.1-0ubuntu14 (using .../libc6_2.13-0ubuntu12_i386.deb) ... Checking for services that may need to be restarted... Checking init scripts... Unpacking replacement libc6 ... Setting up libc6 (2.13-0ubuntu12) ... Installing new version of config file /etc/ld.so.conf.d/i686-linux-gnu.conf ... Checking for services that may need to be restarted... Checking init scripts... Nothing to restart. Processing triggers for libc-bin ... ldconfig deferred processing now taking place Selecting previously deselected package multiarch-support. (Reading database ... 13701 files and directories currently installed.) Unpacking multiarch-support (from .../multiarch-support_2.13-0ubuntu12_i386.deb) ... Setting up multiarch-support (2.13-0ubuntu12) ... (Reading database ... 13704 files and directories currently installed.) Preparing to replace libdbus-1-3 1.4.1-0ubuntu2 (using .../libdbus-1-3_1.4.6-1ubuntu6_i386.deb) ... Unpacking replacement libdbus-1-3 ... Preparing to replace linux-libc-dev 2.6.38-1.28 (using .../linux-libc-dev_2.6.38-8.41_i386.deb) ... Unpacking replacement linux-libc-dev ... Preparing to replace libgomp1 4.5.2-2ubuntu1 (using .../libgomp1_4.5.2-8ubuntu2_i386.deb) ... Unpacking replacement libgomp1 ... Preparing to replace gcc-4.5-base 4.5.2-2ubuntu1 (using .../gcc-4.5-base_4.5.2-8ubuntu2_i386.deb) ... Unpacking replacement gcc-4.5-base ... Setting up gcc-4.5-base (4.5.2-8ubuntu2) ... (Reading database ... 13712 files and directories currently installed.) Preparing to replace libgcc1 1:4.5.2-2ubuntu1 (using .../libgcc1_1%3a4.5.2-8ubuntu2_i386.deb) ... Unpacking replacement libgcc1 ... Setting up libgcc1 (1:4.5.2-8ubuntu2) ... Processing triggers for libc-bin ... ldconfig deferred processing now taking place (Reading database ... 13712 files and directories currently installed.) Preparing to replace cpp-4.5 4.5.2-2ubuntu1 (using .../cpp-4.5_4.5.2-8ubuntu2_i386.deb) ... Unpacking replacement cpp-4.5 ... Preparing to replace libstdc++6-4.5-dev 4.5.2-2ubuntu1 (using .../libstdc++6-4.5-dev_4.5.2-8ubuntu2_i386.deb) ... Unpacking replacement libstdc++6-4.5-dev ... Preparing to replace g++-4.5 4.5.2-2ubuntu1 (using .../g++-4.5_4.5.2-8ubuntu2_i386.deb) ... Unpacking replacement g++-4.5 ... Preparing to replace gcc-4.5 4.5.2-2ubuntu1 (using .../gcc-4.5_4.5.2-8ubuntu2_i386.deb) ... Unpacking replacement gcc-4.5 ... Preparing to replace libstdc++6 4.5.2-2ubuntu1 (using .../libstdc++6_4.5.2-8ubuntu2_i386.deb) ... Unpacking replacement libstdc++6 ... Setting up libstdc++6 (4.5.2-8ubuntu2) ... Processing triggers for libc-bin ... ldconfig deferred processing now taking place (Reading database ... 13709 files and directories currently installed.) Preparing to replace libgmp3c2 2:4.3.2+dfsg-1ubuntu1 (using .../libgmp3c2_2%3a4.3.2+dfsg-1ubuntu3_i386.deb) ... Unpacking replacement libgmp3c2 ... Preparing to replace libgmpxx4ldbl 2:4.3.2+dfsg-1ubuntu1 (using .../libgmpxx4ldbl_2%3a4.3.2+dfsg-1ubuntu3_i386.deb) ... Unpacking replacement libgmpxx4ldbl ... Preparing to replace libmpfr4 3.0.0-2build1 (using .../libmpfr4_3.0.0-7_i386.deb) ... Unpacking replacement libmpfr4 ... Preparing to replace libmpc2 0.8.2-1build1 (using .../libmpc2_0.9-1_i386.deb) ... Unpacking replacement libmpc2 ... Preparing to replace zlib1g 1:1.2.3.4.dfsg-3ubuntu1 (using .../zlib1g_1%3a1.2.3.4.dfsg-3ubuntu3_i386.deb) ... Unpacking replacement zlib1g ... Setting up zlib1g (1:1.2.3.4.dfsg-3ubuntu3) ... Processing triggers for libc-bin ... ldconfig deferred processing now taking place (Reading database ... 13709 files and directories currently installed.) Preparing to replace binutils 2.21-5ubuntu1 (using .../binutils_2.21.0.20110327-2ubuntu2_i386.deb) ... Unpacking replacement binutils ... Preparing to replace debconf-i18n 1.5.36ubuntu3 (using .../debconf-i18n_1.5.36ubuntu4_all.deb) ... Unpacking replacement debconf-i18n ... Setting up debconf-i18n (1.5.36ubuntu4) ... (Reading database ... 13709 files and directories currently installed.) Preparing to replace debconf 1.5.36ubuntu3 (using .../debconf_1.5.36ubuntu4_all.deb) ... Unpacking replacement debconf ... Setting up debconf (1.5.36ubuntu4) ... (Reading database ... 13709 files and directories currently installed.) Preparing to replace tzdata 2011a-1 (using .../tzdata_2011e-1_all.deb) ... Unpacking replacement tzdata ... Setting up tzdata (2011e-1) ... Current default time zone: 'Etc/UTC' Local time is now: Sun Apr 10 18:33:30 UTC 2011. Universal Time is now: Sun Apr 10 18:33:30 UTC 2011. Run 'dpkg-reconfigure tzdata' if you wish to change it. (Reading database ... 13718 files and directories currently installed.) Preparing to replace libpam0g 1.1.1-4ubuntu2 (using .../libpam0g_1.1.2-2ubuntu7_i386.deb) ... Unpacking replacement libpam0g ... Setting up libpam0g (1.1.2-2ubuntu7) ... Checking for services that may need to be restarted...Checking init scripts... Nothing to restart. Processing triggers for libc-bin ... ldconfig deferred processing now taking place (Reading database ... 13718 files and directories currently installed.) Preparing to replace libselinux1 2.0.96-1build1 (using .../libselinux1_2.0.96-1ubuntu2_i386.deb) ... Unpacking replacement libselinux1 ... Setting up libselinux1 (2.0.96-1ubuntu2) ... Processing triggers for libc-bin ... ldconfig deferred processing now taking place Selecting previously deselected package libpam-modules-bin. (Reading database ... 13718 files and directories currently installed.) Unpacking libpam-modules-bin (from .../libpam-modules-bin_1.1.2-2ubuntu7_i386.deb) ... Replacing files in old package libpam-modules ... Setting up libpam-modules-bin (1.1.2-2ubuntu7) ... (Reading database ... 13723 files and directories currently installed.) Preparing to replace libpam-modules 1.1.1-4ubuntu2 (using .../libpam-modules_1.1.2-2ubuntu7_i386.deb) ... Unpacking replacement libpam-modules ... Setting up libpam-modules (1.1.2-2ubuntu7) ... Installing new version of config file /etc/security/group.conf ... (Reading database ... 13722 files and directories currently installed.) Preparing to replace base-files 5.0.0ubuntu26 (using .../base-files_5.0.0ubuntu27_i386.deb) ... Unpacking replacement base-files ... Setting up base-files (5.0.0ubuntu27) ... Installing new version of config file /etc/lsb-release ... (Reading database ... 13722 files and directories currently installed.) Preparing to replace bash 4.1-2ubuntu5 (using .../bash_4.2-0ubuntu3_i386.deb) ... Unpacking replacement bash ... Setting up bash (4.2-0ubuntu3) ... update-alternatives: using /usr/share/man/man7/bash-builtins.7.gz to provide /usr/share/man/man7/builtins.7.gz (builtins.7.gz) in auto mode. (Reading database ... 13722 files and directories currently installed.) Preparing to replace coreutils 8.5-1ubuntu5 (using .../coreutils_8.5-1ubuntu6_i386.deb) ... Unpacking replacement coreutils ... Setting up coreutils (8.5-1ubuntu6) ... (Reading database ... 13722 files and directories currently installed.) Preparing to replace dpkg 1.15.8.7ubuntu2 (using .../dpkg_1.16.0~ubuntu6_i386.deb) ... Unpacking replacement dpkg ... Setting up dpkg (1.16.0~ubuntu6) ... (Reading database ... 13722 files and directories currently installed.) Preparing to replace e2fslibs 1.41.14-1ubuntu1 (using .../e2fslibs_1.41.14-1ubuntu3_i386.deb) ... Unpacking replacement e2fslibs ... Setting up e2fslibs (1.41.14-1ubuntu3) ... Processing triggers for libc-bin ... ldconfig deferred processing now taking place (Reading database ... 13722 files and directories currently installed.) Preparing to replace e2fsprogs 1.41.14-1ubuntu1 (using .../e2fsprogs_1.41.14-1ubuntu3_i386.deb) ... Unpacking replacement e2fsprogs ... Setting up e2fsprogs (1.41.14-1ubuntu3) ... (Reading database ... 13722 files and directories currently installed.) Preparing to replace findutils 4.4.2-1ubuntu2 (using .../findutils_4.4.2-1ubuntu3_i386.deb) ... Unpacking replacement findutils ... Setting up findutils (4.4.2-1ubuntu3) ... (Reading database ... 13722 files and directories currently installed.) Preparing to replace login 1:4.1.4.2+svn3283-2ubuntu2 (using .../login_1%3a4.1.4.2+svn3283-3ubuntu1_i386.deb) ... Unpacking replacement login ... Setting up login (1:4.1.4.2+svn3283-3ubuntu1) ... Installing new version of config file /etc/pam.d/login ... Installing new version of config file /etc/securetty ... (Reading database ... 13722 files and directories currently installed.) Preparing to replace mount 2.17.2-3.3ubuntu4 (using .../mount_2.17.2-9.1ubuntu4_i386.deb) ... Unpacking replacement mount ... Setting up mount (2.17.2-9.1ubuntu4) ... (Reading database ... 13722 files and directories currently installed.) Preparing to replace perl-modules 5.10.1-17ubuntu1 (using .../perl-modules_5.10.1-17ubuntu4_all.deb) ... Unpacking replacement perl-modules ... Preparing to replace bzip2 1.0.5-6 (using .../bzip2_1.0.5-6ubuntu1_i386.deb) ... Unpacking replacement bzip2 ... Preparing to replace libbz2-1.0 1.0.5-6 (using .../libbz2-1.0_1.0.5-6ubuntu1_i386.deb) ... Unpacking replacement libbz2-1.0 ... Setting up libbz2-1.0 (1.0.5-6ubuntu1) ... Processing triggers for libc-bin ... ldconfig deferred processing now taking place (Reading database ... 13720 files and directories currently installed.) Preparing to replace libdb4.8 4.8.30-3 (using .../libdb4.8_4.8.30-5ubuntu2_i386.deb) ... Unpacking replacement libdb4.8 ... Setting up libdb4.8 (4.8.30-5ubuntu2) ... Processing triggers for libc-bin ... ldconfig deferred processing now taking place (Reading database ... 13720 files and directories currently installed.) Preparing to replace libgdbm3 1.8.3-9 (using .../libgdbm3_1.8.3-9ubuntu1_i386.deb) ... Unpacking replacement libgdbm3 ... Preparing to replace perl 5.10.1-17ubuntu1 (using .../perl_5.10.1-17ubuntu4_i386.deb) ... Unpacking replacement perl ... Preparing to replace perl-base 5.10.1-17ubuntu1 (using .../perl-base_5.10.1-17ubuntu4_i386.deb) ... Unpacking replacement perl-base ... Setting up perl-base (5.10.1-17ubuntu4) ... (Reading database ... 13719 files and directories currently installed.) Preparing to replace sysvinit-utils 2.87dsf-4ubuntu19 (using .../sysvinit-utils_2.87dsf-4ubuntu23_i386.deb) ... Unpacking replacement sysvinit-utils ... Preparing to replace sysv-rc 2.87dsf-4ubuntu19 (using .../sysv-rc_2.87dsf-4ubuntu23_all.deb) ... Unpacking replacement sysv-rc ... Preparing to replace passwd 1:4.1.4.2+svn3283-2ubuntu2 (using .../passwd_1%3a4.1.4.2+svn3283-3ubuntu1_i386.deb) ... Unpacking replacement passwd ... Setting up passwd (1:4.1.4.2+svn3283-3ubuntu1) ... (Reading database ... 13718 files and directories currently installed.) Preparing to replace initscripts 2.87dsf-4ubuntu19 (using .../initscripts_2.87dsf-4ubuntu23_i386.deb) ... Unpacking replacement initscripts ... Preparing to replace libudev0 165-0ubuntu2 (using .../libudev0_167-0ubuntu3_i386.deb) ... Unpacking replacement libudev0 ... Preparing to replace libattr1 1:2.4.44-2 (using .../libattr1_1%3a2.4.44-2ubuntu2_i386.deb) ... Unpacking replacement libattr1 ... Setting up libattr1 (1:2.4.44-2ubuntu2) ... Processing triggers for libc-bin ... ldconfig deferred processing now taking place (Reading database ... 13718 files and directories currently installed.) Preparing to replace libacl1 2.2.49-4 (using .../libacl1_2.2.49-4ubuntu2_i386.deb) ... Unpacking replacement libacl1 ... Setting up libacl1 (2.2.49-4ubuntu2) ... Processing triggers for libc-bin ... ldconfig deferred processing now taking place (Reading database ... 13717 files and directories currently installed.) Preparing to replace libpcre3 8.12-0ubuntu2 (using .../libpcre3_8.12-3ubuntu2_i386.deb) ... Unpacking replacement libpcre3 ... Preparing to replace libglib2.0-0 2.27.92-0ubuntu1 (using .../libglib2.0-0_2.28.5-0ubuntu1_i386.deb) ... Unpacking replacement libglib2.0-0 ... Preparing to replace libusb-0.1-4 2:0.1.12-16 (using .../libusb-0.1-4_2%3a0.1.12-17_i386.deb) ... Unpacking replacement libusb-0.1-4 ... Preparing to replace module-init-tools 3.12-1ubuntu3 (using .../module-init-tools_3.12-1ubuntu6_i386.deb) ... Moving obsolete conffile /etc/modprobe.d/intel-5300-iwlagn-disable11n.conf out of the way... Unpacking replacement module-init-tools ... Preparing to replace initramfs-tools 0.98.1ubuntu9 (using .../initramfs-tools_0.98.8ubuntu3_all.deb) ... Unpacking replacement initramfs-tools ... Preparing to replace initramfs-tools-bin 0.98.1ubuntu9 (using .../initramfs-tools-bin_0.98.8ubuntu3_i386.deb) ... Unpacking replacement initramfs-tools-bin ... Preparing to replace klibc-utils 1.5.20-1 (using .../klibc-utils_1.5.20-1ubuntu4_i386.deb) ... Unpacking replacement klibc-utils ... Preparing to replace libklibc 1.5.20-1 (using .../libklibc_1.5.20-1ubuntu4_i386.deb) ... Unpacking replacement libklibc ... Preparing to replace busybox-initramfs 1:1.17.1-8ubuntu1 (using .../busybox-initramfs_1%3a1.17.1-10ubuntu1_i386.deb) ... Unpacking replacement busybox-initramfs ... Preparing to replace cpio 2.11-6ubuntu1 (using .../cpio_2.11-7ubuntu1_i386.deb) ... Unpacking replacement cpio ... Preparing to replace procps 1:3.2.8-10ubuntu1 (using .../procps_1%3a3.2.8-10ubuntu3_i386.deb) ... Unpacking replacement procps ... Preparing to replace adduser 3.112+nmu1ubuntu4 (using .../adduser_3.112+nmu1ubuntu5_all.deb) ... Unpacking replacement adduser ... Preparing to replace util-linux 2.17.2-3.3ubuntu4 (using .../util-linux_2.17.2-9.1ubuntu4_i386.deb) ... Unpacking replacement util-linux ... Setting up util-linux (2.17.2-9.1ubuntu4) ... (Reading database ... 13718 files and directories currently installed.) Preparing to replace udev 165-0ubuntu2 (using .../udev_167-0ubuntu3_i386.deb) ... Adding 'diversion of /sbin/udevadm to /sbin/udevadm.upgrade by fake-udev' Unpacking replacement udev ... Preparing to replace libdrm2 2.4.23-1ubuntu3 (using .../libdrm2_2.4.23-1ubuntu6_i386.deb) ... Unpacking replacement libdrm2 ... Preparing to replace libdrm-intel1 2.4.23-1ubuntu3 (using .../libdrm-intel1_2.4.23-1ubuntu6_i386.deb) ... Unpacking replacement libdrm-intel1 ... Preparing to replace libdrm-nouveau1a 2.4.23-1ubuntu3 (using .../libdrm-nouveau1a_2.4.23-1ubuntu6_i386.deb) ... Unpacking replacement libdrm-nouveau1a ... Preparing to replace libdrm-radeon1 2.4.23-1ubuntu3 (using .../libdrm-radeon1_2.4.23-1ubuntu6_i386.deb) ... Unpacking replacement libdrm-radeon1 ... Preparing to replace plymouth 0.8.2-2ubuntu13 (using .../plymouth_0.8.2-2ubuntu21_i386.deb) ... Unpacking replacement plymouth ... Preparing to replace libpng12-0 1.2.44-1ubuntu1 (using .../libpng12-0_1.2.44-1ubuntu3_i386.deb) ... Unpacking replacement libpng12-0 ... Preparing to replace libplymouth2 0.8.2-2ubuntu13 (using .../libplymouth2_0.8.2-2ubuntu21_i386.deb) ... Unpacking replacement libplymouth2 ... Preparing to replace mountall 2.20+nmu1 (using .../mountall_2.25_i386.deb) ... Unpacking replacement mountall ... Preparing to replace upstart 0.6.7-5 (using .../upstart_0.9.4-1ubuntu1_i386.deb) ... Unpacking replacement upstart ... Preparing to replace bsdutils 1:2.17.2-3.3ubuntu4 (using .../bsdutils_1%3a2.17.2-9.1ubuntu4_i386.deb) ... Unpacking replacement bsdutils ... Setting up bsdutils (1:2.17.2-9.1ubuntu4) ... (Reading database ... 13737 files and directories currently installed.) Preparing to replace libuuid1 2.17.2-3.3ubuntu4 (using .../libuuid1_2.17.2-9.1ubuntu4_i386.deb) ... Unpacking replacement libuuid1 ... Setting up libuuid1 (2.17.2-9.1ubuntu4) ... Processing triggers for libc-bin ... ldconfig deferred processing now taking place (Reading database ... 13737 files and directories currently installed.) Preparing to replace libblkid1 2.17.2-3.3ubuntu4 (using .../libblkid1_2.17.2-9.1ubuntu4_i386.deb) ... Unpacking replacement libblkid1 ... Setting up libblkid1 (2.17.2-9.1ubuntu4) ... Processing triggers for libc-bin ... ldconfig deferred processing now taking place (Reading database ... 13737 files and directories currently installed.) Preparing to replace libcomerr2 1.41.14-1ubuntu1 (using .../libcomerr2_1.41.14-1ubuntu3_i386.deb) ... Unpacking replacement libcomerr2 ... Setting up libcomerr2 (1.41.14-1ubuntu3) ... Processing triggers for libc-bin ... ldconfig deferred processing now taking place (Reading database ... 13737 files and directories currently installed.) Preparing to replace libss2 1.41.14-1ubuntu1 (using .../libss2_1.41.14-1ubuntu3_i386.deb) ... Unpacking replacement libss2 ... Setting up libss2 (1.41.14-1ubuntu3) ... Processing triggers for libc-bin ... ldconfig deferred processing now taking place (Reading database ... 13737 files and directories currently installed.) Preparing to replace libgpg-error0 1.10-0.2 (using .../libgpg-error0_1.10-0.2ubuntu1_i386.deb) ... Unpacking replacement libgpg-error0 ... Preparing to replace libgcrypt11 1.4.5-2ubuntu2 (using .../libgcrypt11_1.4.6-4ubuntu2_i386.deb) ... Unpacking replacement libgcrypt11 ... Preparing to replace libtasn1-3 2.7-1 (using .../libtasn1-3_2.7-1ubuntu1_i386.deb) ... Unpacking replacement libtasn1-3 ... Preparing to replace libgnutls26 2.8.6-1ubuntu1 (using .../libgnutls26_2.8.6-1ubuntu2_i386.deb) ... Unpacking replacement libgnutls26 ... Preparing to replace libkeyutils1 1.4-1 (using .../libkeyutils1_1.4-4ubuntu2_i386.deb) ... Unpacking replacement libkeyutils1 ... Preparing to replace libk5crypto3 1.8.3+dfsg-4 (using .../libk5crypto3_1.8.3+dfsg-5ubuntu2_i386.deb) ... Unpacking replacement libk5crypto3 ... Preparing to replace libgssapi-krb5-2 1.8.3+dfsg-4 (using .../libgssapi-krb5-2_1.8.3+dfsg-5ubuntu2_i386.deb) ... Unpacking replacement libgssapi-krb5-2 ... Preparing to replace libkrb5-3 1.8.3+dfsg-4 (using .../libkrb5-3_1.8.3+dfsg-5ubuntu2_i386.deb) ... Unpacking replacement libkrb5-3 ... Preparing to replace libkrb5support0 1.8.3+dfsg-4 (using .../libkrb5support0_1.8.3+dfsg-5ubuntu2_i386.deb) ... Unpacking replacement libkrb5support0 ... Preparing to replace apt 0.8.10ubuntu1 (using .../apt_0.8.13.2ubuntu2_i386.deb) ... Unpacking replacement apt ... Setting up apt (0.8.13.2ubuntu2) ... Installing new version of config file /etc/apt/apt.conf.d/01autoremove ... Installing new version of config file /etc/cron.daily/apt ... gpg: key 437D05B5: "Ubuntu Archive Automatic Signing Key " not changed gpg: key FBB75451: "Ubuntu CD Image Automatic Signing Key " not changed gpg: Total number processed: 2 gpg: unchanged: 2 Processing triggers for libc-bin ... ldconfig deferred processing now taking place (Reading database ... 13748 files and directories currently installed.) Preparing to replace libpam-runtime 1.1.1-4ubuntu2 (using .../libpam-runtime_1.1.2-2ubuntu7_all.deb) ... Unpacking replacement libpam-runtime ... Setting up libpam-runtime (1.1.2-2ubuntu7) ... (Reading database ... 13748 files and directories currently installed.) Preparing to replace libssl0.9.8 0.9.8o-4ubuntu1 (using .../libssl0.9.8_0.9.8o-5ubuntu1_i386.deb) ... Unpacking replacement libssl0.9.8 ... Setting up libssl0.9.8 (0.9.8o-5ubuntu1) ... Processing triggers for libc-bin ... ldconfig deferred processing now taking place (Reading database ... 13748 files and directories currently installed.) Preparing to replace python2.7-minimal 2.7.1-3 (using .../python2.7-minimal_2.7.1-5ubuntu1_i386.deb) ... Unpacking replacement python2.7-minimal ... Setting up python2.7-minimal (2.7.1-5ubuntu1) ... (Reading database ... 13748 files and directories currently installed.) Preparing to replace readline-common 6.1-3 (using .../readline-common_6.2-0ubuntu1_all.deb) ... Unpacking replacement readline-common ... Preparing to replace libreadline6 6.1-3 (using .../libreadline6_6.2-0ubuntu1_i386.deb) ... Unpacking replacement libreadline6 ... Preparing to replace gpgv 1.4.10-4ubuntu2 (using .../gpgv_1.4.11-3ubuntu1_i386.deb) ... Unpacking replacement gpgv ... Preparing to replace gnupg 1.4.10-4ubuntu2 (using .../gnupg_1.4.11-3ubuntu1_i386.deb) ... Unpacking replacement gnupg ... Preparing to replace netbase 4.44ubuntu1 (using .../netbase_4.45ubuntu1_all.deb) ... Unpacking replacement netbase ... Preparing to replace locales 2.13+git20100825-2 (using .../locales_2.13+git20100825-4_all.deb) ... Unpacking replacement locales ... Preparing to replace apt-transport-https 0.8.10ubuntu1 (using .../apt-transport-https_0.8.13.2ubuntu2_i386.deb) ... Unpacking replacement apt-transport-https ... Preparing to replace libldap-2.4-2 2.4.23-6ubuntu4 (using .../libldap-2.4-2_2.4.23-6ubuntu6_i386.deb) ... Unpacking replacement libldap-2.4-2 ... Preparing to replace openssl 0.9.8o-4ubuntu1 (using .../openssl_0.9.8o-5ubuntu1_i386.deb) ... Unpacking replacement openssl ... Preparing to replace cpp 4:4.5.1-1ubuntu3 (using .../cpp_4%3a4.5.2-1ubuntu1_i386.deb) ... Unpacking replacement cpp ... Preparing to replace dpkg-dev 1.15.8.7ubuntu2 (using .../dpkg-dev_1.16.0~ubuntu6_all.deb) ... Unpacking replacement dpkg-dev ... Preparing to replace libdpkg-perl 1.15.8.7ubuntu2 (using .../libdpkg-perl_1.16.0~ubuntu6_all.deb) ... Unpacking replacement libdpkg-perl ... Preparing to replace make 3.81-8 (using .../make_3.81-8ubuntu1_i386.deb) ... Unpacking replacement make ... Preparing to replace gcc 4:4.5.1-1ubuntu3 (using .../gcc_4%3a4.5.2-1ubuntu1_i386.deb) ... Removing old gcc doc directory. Unpacking replacement gcc ... Preparing to replace g++ 4:4.5.1-1ubuntu3 (using .../g++_4%3a4.5.2-1ubuntu1_i386.deb) ... Unpacking replacement g++ ... Preparing to replace pkg-create-dbgsym 0.46 (using .../pkg-create-dbgsym_0.48_all.deb) ... Unpacking replacement pkg-create-dbgsym ... Preparing to replace pkgbinarymangler 91 (using .../pkgbinarymangler_95_all.deb) ... Unpacking replacement pkgbinarymangler ... Setting up libnih1 (1.0.3-1ubuntu1) ... Setting up libdbus-1-3 (1.4.6-1ubuntu6) ... Setting up libnih-dbus1 (1.0.3-1ubuntu1) ... Setting up libc-dev-bin (2.13-0ubuntu12) ... Setting up linux-libc-dev (2.6.38-8.41) ... Setting up libc6-dev (2.13-0ubuntu12) ... Setting up libgomp1 (4.5.2-8ubuntu2) ... Setting up libgmp3c2 (2:4.3.2+dfsg-1ubuntu3) ... Setting up libgmpxx4ldbl (2:4.3.2+dfsg-1ubuntu3) ... Setting up libmpfr4 (3.0.0-7) ... Setting up libmpc2 (0.9-1) ... Setting up cpp-4.5 (4.5.2-8ubuntu2) ... Setting up binutils (2.21.0.20110327-2ubuntu2) ... Setting up gcc-4.5 (4.5.2-8ubuntu2) ... Setting up libgdbm3 (1.8.3-9ubuntu1) ... Setting up bzip2 (1.0.5-6ubuntu1) ... Setting up sysvinit-utils (2.87dsf-4ubuntu23) ... Setting up sysv-rc (2.87dsf-4ubuntu23) ... Setting up libudev0 (167-0ubuntu3) ... Setting up libpcre3 (8.12-3ubuntu2) ... Setting up libglib2.0-0 (2.28.5-0ubuntu1) ... Setting up libusb-0.1-4 (2:0.1.12-17) ... Setting up initramfs-tools-bin (0.98.8ubuntu3) ... Setting up libklibc (1.5.20-1ubuntu4) ... Setting up klibc-utils (1.5.20-1ubuntu4) ... Setting up busybox-initramfs (1:1.17.1-10ubuntu1) ... Setting up cpio (2.11-7ubuntu1) ... Setting up adduser (3.112+nmu1ubuntu5) ... Setting up libdrm2 (2.4.23-1ubuntu6) ... Setting up libdrm-intel1 (2.4.23-1ubuntu6) ... Setting up libdrm-nouveau1a (2.4.23-1ubuntu6) ... Setting up libdrm-radeon1 (2.4.23-1ubuntu6) ... Setting up libpng12-0 (1.2.44-1ubuntu3) ... Setting up libplymouth2 (0.8.2-2ubuntu21) ... Setting up libgpg-error0 (1.10-0.2ubuntu1) ... Setting up libgcrypt11 (1.4.6-4ubuntu2) ... Setting up libtasn1-3 (2.7-1ubuntu1) ... Setting up libgnutls26 (2.8.6-1ubuntu2) ... Setting up libkeyutils1 (1.4-4ubuntu2) ... Setting up libkrb5support0 (1.8.3+dfsg-5ubuntu2) ... Setting up libk5crypto3 (1.8.3+dfsg-5ubuntu2) ... Setting up libkrb5-3 (1.8.3+dfsg-5ubuntu2) ... Setting up libgssapi-krb5-2 (1.8.3+dfsg-5ubuntu2) ... Setting up readline-common (6.2-0ubuntu1) ... Setting up libreadline6 (6.2-0ubuntu1) ... Setting up gpgv (1.4.11-3ubuntu1) ... Setting up gnupg (1.4.11-3ubuntu1) ... Setting up locales (2.13+git20100825-4) ... Setting up apt-transport-https (0.8.13.2ubuntu2) ... Setting up libldap-2.4-2 (2.4.23-6ubuntu6) ... Setting up openssl (0.9.8o-5ubuntu1) ... Setting up cpp (4:4.5.2-1ubuntu1) ... Setting up make (3.81-8ubuntu1) ... Setting up gcc (4:4.5.2-1ubuntu1) ... Setting up pkg-create-dbgsym (0.48) ... Setting up pkgbinarymangler (95) ... Setting up libstdc++6-4.5-dev (4.5.2-8ubuntu2) ... Setting up perl-modules (5.10.1-17ubuntu4) ... Setting up mountall (2.25) ... Installing new version of config file /etc/init/mounted-tmp.conf ... Setting up upstart (0.9.4-1ubuntu1) ... Installing new version of config file /etc/init/rc-sysinit.conf ... Installing new version of config file /etc/init/upstart-udev-bridge.conf ... Setting up initscripts (2.87dsf-4ubuntu23) ... Installing new version of config file /etc/init.d/sendsigs ... Installing new version of config file /etc/init.d/umountnfs.sh ... Installing new version of config file /etc/init.d/umountroot ... Setting up netbase (4.45ubuntu1) ... Installing new version of config file /etc/protocols ... Installing new version of config file /etc/services ... Setting up g++-4.5 (4.5.2-8ubuntu2) ... Setting up perl (5.10.1-17ubuntu4) ... Setting up module-init-tools (3.12-1ubuntu6) ... Installing new version of config file /etc/modprobe.d/blacklist-framebuffer.conf ... Removing obsolete conffile /etc/modprobe.d/intel-5300-iwlagn-disable11n.conf ... Setting up initramfs-tools (0.98.8ubuntu3) ... update-initramfs: deferring update (trigger activated) Setting up procps (1:3.2.8-10ubuntu3) ... Setting up udev (167-0ubuntu3) ... Removing 'diversion of /sbin/udevadm to /sbin/udevadm.upgrade by fake-udev' update-initramfs: deferring update (trigger activated) Setting up plymouth (0.8.2-2ubuntu21) ... Installing new version of config file /etc/init/plymouth-splash.conf ... update-initramfs: deferring update (trigger activated) Setting up libdpkg-perl (1.16.0~ubuntu6) ... Setting up dpkg-dev (1.16.0~ubuntu6) ... Setting up g++ (4:4.5.2-1ubuntu1) ... Processing triggers for libc-bin ... ldconfig deferred processing now taking place Processing triggers for initramfs-tools ... RUN: /usr/share/launchpad-buildd/slavebin/sbuild-package ['sbuild-package', 'a5bf95798123a7de5b0ac6630436238ddb2ef38c', 'i386', 'natty', '--nolog', '--batch', '--archive=ubuntu', '--dist=natty', '-A', '--purpose=PRIMARY', '--architecture=i386', '--comp=universe', 'docky_2.1.2-1.dsc'] Initiating build a5bf95798123a7de5b0ac6630436238ddb2ef38c with 2 processor cores. Automatic build of docky_2.1.2-1 on rothera by sbuild/i386 1.170.5 Build started at 20110410-1833 ****************************************************************************** docky_2.1.2-1.dsc exists in cwd sh: gcc: not found dpkg-architecture: warning: Couldn't determine gcc system type, falling back to default (native compilation) ** Using build dependencies supplied by package: Build-Depends: debhelper (>= 7.0.50~), autotools-dev, intltool, cli-common-dev (>= 0.7) Build-Depends-Indep: mono-devel (>= 2.4.3), gtk-sharp2-gapi, libgconf2.0-cil-dev, libgnomedesktop2.0-cil-dev, libgnome-keyring1.0-cil-dev, libgtk2.0-cil-dev, libgio2.0-cil-dev (>= 2.22.2), librsvg2-2.0-cil-dev, libmono-addins-cil-dev, libmono-addins-gui-cil-dev, libdbus1.0-cil-dev (>= 0.7), libdbus-glib1.0-cil-dev (>= 0.5), libnotify-cil-dev, libwnck1.0-cil-dev, libgtk2.0-dev, libglib2.0-dev, libgconf2-dev sh: gcc: not found dpkg-architecture: warning: Couldn't determine gcc system type, falling back to default (native compilation) sh: gcc: not found dpkg-architecture: warning: Couldn't determine gcc system type, falling back to default (native compilation) sh: gcc: not found dpkg-architecture: warning: Couldn't determine gcc system type, falling back to default (native compilation) sh: gcc: not found dpkg-architecture: warning: Couldn't determine gcc system type, falling back to default (native compilation) sh: gcc: not found dpkg-architecture: warning: Couldn't determine gcc system type, falling back to default (native compilation) sh: gcc: not found dpkg-architecture: warning: Couldn't determine gcc system type, falling back to default (native compilation) sh: gcc: not found dpkg-architecture: warning: Couldn't determine gcc system type, falling back to default (native compilation) sh: gcc: not found dpkg-architecture: warning: Couldn't determine gcc system type, falling back to default (native compilation) Checking for already installed source dependencies... debhelper: missing autotools-dev: missing intltool: missing cli-common-dev: missing mono-devel: missing gtk-sharp2-gapi: missing libgconf2.0-cil-dev: missing libgnomedesktop2.0-cil-dev: missing libgnome-keyring1.0-cil-dev: missing libgtk2.0-cil-dev: missing libgio2.0-cil-dev: missing librsvg2-2.0-cil-dev: missing libmono-addins-cil-dev: missing libmono-addins-gui-cil-dev: missing libdbus1.0-cil-dev: missing libdbus-glib1.0-cil-dev: missing libnotify-cil-dev: missing libwnck1.0-cil-dev: missing libgtk2.0-dev: missing libglib2.0-dev: missing libgconf2-dev: missing Checking for source dependency conflicts... /usr/bin/sudo /usr/bin/apt-get --purge $CHROOT_OPTIONS -q -y install debhelper autotools-dev intltool cli-common-dev mono-devel gtk-sharp2-gapi libgconf2.0-cil-dev libgnomedesktop2.0-cil-dev libgnome-keyring1.0-cil-dev libgtk2.0-cil-dev libgio2.0-cil-dev librsvg2-2.0-cil-dev libmono-addins-cil-dev libmono-addins-gui-cil-dev libdbus1.0-cil-dev libdbus-glib1.0-cil-dev libnotify-cil-dev libwnck1.0-cil-dev libgtk2.0-dev libglib2.0-dev libgconf2-dev Reading package lists... Building dependency tree... Reading state information... The following extra packages will be installed: autoconf automake bsdmainutils cli-common dbus dbus-x11 file fontconfig fontconfig-config gamin gconf2 gconf2-common gettext gettext-base gnome-mime-data groff-base html2text intltool-debian libart-2.0-2 libart2.0-cil libart2.0-cil-dev libasound2 libatk1.0-0 libatk1.0-data libatk1.0-dev libavahi-client3 libavahi-common-data libavahi-common3 libavahi-glib1 libbonobo2-0 libbonobo2-common libbonoboui2-0 libbonoboui2-common libcairo-gobject2 libcairo-script-interpreter2 libcairo2 libcairo2-dev libcanberra0 libcroco3 libcups2 libdatrie1 libdbus-1-dev libdbus-glib-1-2 libdbus-glib1.0-cil libdbus1.0-cil libexif12 libexpat1 libexpat1-dev libfontconfig1 libfontconfig1-dev libfreetype6 libfreetype6-dev libgail18 libgamin0 libgconf2-4 libgconf2.0-cil libgdiplus libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-dev libgif4 libgio-cil libglade2-0 libglade2.0-cil libglib2.0-bin libglib2.0-cil libglib2.0-cil-dev libglib2.0-data libgnome-desktop-2-17 libgnome-keyring0 libgnome-keyring1.0-cil libgnome-vfs2.0-cil libgnome-vfs2.0-cil-dev libgnome2-0 libgnome2-common libgnome2.0-cil-dev libgnome2.24-cil libgnomecanvas2-0 libgnomecanvas2-common libgnomedesktop2.20-cil libgnomeui-0 libgnomeui-common libgnomevfs2-0 libgnomevfs2-common libgtk2.0-0 libgtk2.0-cil libgtk2.0-common libhtml-parser-perl libhtml-tagset-perl libhtml-tree-perl libice-dev libice6 libidl-dev libidl0 libjasper1 libjpeg62 libltdl7 libmagic1 libmono-accessibility1.0-cil libmono-accessibility2.0-cil libmono-addins-gui0.2-cil libmono-addins0.2-cil libmono-bytefx0.7.6.1-cil libmono-bytefx0.7.6.2-cil libmono-c5-1.1-cil libmono-cairo1.0-cil libmono-cairo2.0-cil libmono-cecil-private-cil libmono-cil-dev libmono-corlib1.0-cil libmono-corlib2.0-cil libmono-cscompmgd7.0-cil libmono-cscompmgd8.0-cil libmono-data-tds1.0-cil libmono-data-tds2.0-cil libmono-data1.0-cil libmono-data2.0-cil libmono-db2-1.0-cil libmono-debugger-soft0.0-cil libmono-dev libmono-getoptions1.0-cil libmono-getoptions2.0-cil libmono-i18n-west1.0-cil libmono-i18n-west2.0-cil libmono-i18n1.0-cil libmono-i18n2.0-cil libmono-ldap1.0-cil libmono-ldap2.0-cil libmono-management2.0-cil libmono-messaging-rabbitmq2.0-cil libmono-messaging2.0-cil libmono-microsoft-build2.0-cil libmono-microsoft7.0-cil libmono-microsoft8.0-cil libmono-npgsql1.0-cil libmono-npgsql2.0-cil libmono-oracle1.0-cil libmono-oracle2.0-cil libmono-peapi1.0-cil libmono-peapi2.0-cil libmono-posix1.0-cil libmono-posix2.0-cil libmono-rabbitmq2.0-cil libmono-relaxng1.0-cil libmono-relaxng2.0-cil libmono-security1.0-cil libmono-security2.0-cil libmono-sharpzip0.6-cil libmono-sharpzip0.84-cil libmono-sharpzip2.6-cil libmono-sharpzip2.84-cil libmono-simd2.0-cil libmono-sqlite1.0-cil libmono-sqlite2.0-cil libmono-system-data-linq2.0-cil libmono-system-data1.0-cil libmono-system-data2.0-cil libmono-system-ldap1.0-cil libmono-system-ldap2.0-cil libmono-system-messaging1.0-cil libmono-system-messaging2.0-cil libmono-system-runtime1.0-cil libmono-system-runtime2.0-cil libmono-system-web-mvc1.0-cil libmono-system-web-mvc2.0-cil libmono-system-web1.0-cil libmono-system-web2.0-cil libmono-system1.0-cil libmono-system2.0-cil libmono-tasklets2.0-cil libmono-wcf3.0-cil libmono-webbrowser0.5-cil libmono-windowsbase3.0-cil libmono-winforms1.0-cil libmono-winforms2.0-cil libmono0 libmono1.0-cil libmono2.0-cil libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libnotify0.4-cil libnunit-cil-dev libnunit2.4-cil libogg0 liborbit2 liborbit2-dev libpango1.0-0 libpango1.0-dev libpipeline1 libpixman-1-0 libpixman-1-dev libpng12-dev libpopt0 libpthread-stubs0 libpthread-stubs0-dev libpython2.7 librsvg2-2 librsvg2-2.18-cil libsm-dev libsm6 libsqlite0 libsqlite3-0 libstartup-notification0 libtdb1 libthai-data libthai0 libtiff4 libunistring0 liburi-perl libvorbis0a libvorbisfile3 libwnck-common libwnck2.20-cil libwnck22 libwww-perl libx11-6 libx11-data libx11-dev libxau-dev libxau6 libxcb-atom1 libxcb-aux0 libxcb-event1 libxcb-render0 libxcb-render0-dev libxcb-shm0 libxcb-shm0-dev libxcb1 libxcb1-dev libxcomposite-dev libxcomposite1 libxcursor-dev libxcursor1 libxdamage-dev libxdamage1 libxdmcp-dev libxdmcp6 libxext-dev libxext6 libxfixes-dev libxfixes3 libxft-dev libxft2 libxi-dev libxi6 libxinerama-dev libxinerama1 libxml-dom-perl libxml-libxml-perl libxml-namespacesupport-perl libxml-parser-perl libxml-perl libxml-regexp-perl libxml-sax-perl libxml2 libxml2-utils libxrandr-dev libxrandr2 libxrender-dev libxrender1 libxres1 m4 man-db mime-support mono-2.0-devel mono-2.0-gac mono-gac mono-gmcs mono-runtime mono-utils pkg-config po-debconf psmisc python python2.7 shared-mime-info ttf-dejavu-core ucf x11-common x11proto-composite-dev x11proto-core-dev x11proto-damage-dev x11proto-fixes-dev x11proto-input-dev x11proto-kb-dev x11proto-randr-dev x11proto-render-dev x11proto-xext-dev x11proto-xinerama-dev xorg-sgml-doctools xtrans-dev zlib1g-dev Suggested packages: autoconf2.13 autoconf-archive gnu-standards autoconf-doc libtool wamerican wordlist whois vacation dh-make defoma gconf-defaults-service gettext-doc groff monodoc-gtk2.0-manual libasound2-plugins libbonobo2-bin libcairo2-doc libcanberra-gtk0 libcanberra-pulse cups-common libglib2.0-doc python-subunit gnome-keyring desktop-base gnome-icon-theme libgnomevfs2-bin libgnomevfs2-extra librsvg2-common libgtk2.0-doc libdata-dump-perl libjasper-runtime libmono-firebirdsql1.7-cil libnunit-doc monodoc-nunit-manual ttf-japanese-gothic ttf-japanese-mincho ttf-thryomanes ttf-baekmuk ttf-arphic-gbsn00lp ttf-arphic-bsmi00lp ttf-arphic-gkai00mp ttf-arphic-bkai00mp libpango1.0-doc imagemagick librsvg2-bin libcrypt-ssleay-perl libio-socket-ssl-perl less www-browser libmail-box-perl python-doc python-tk python-profiler python2.7-doc python2.7-profiler Recommended packages: curl wget lynx-cur hwdata gvfs hicolor-icon-theme libgtk2.0-bin libgluezilla notification-daemon orbit2 x-ttcidfont-conf libmailtools-perl libhtml-format-perl libxml-sax-expat-perl xml-core mono-csharp-shell binfmt-support libmail-sendmail-perl The following NEW packages will be installed: autoconf automake autotools-dev bsdmainutils cli-common cli-common-dev dbus dbus-x11 debhelper file fontconfig fontconfig-config gamin gconf2 gconf2-common gettext gettext-base gnome-mime-data groff-base gtk-sharp2-gapi html2text intltool intltool-debian libart-2.0-2 libart2.0-cil libart2.0-cil-dev libasound2 libatk1.0-0 libatk1.0-data libatk1.0-dev libavahi-client3 libavahi-common-data libavahi-common3 libavahi-glib1 libbonobo2-0 libbonobo2-common libbonoboui2-0 libbonoboui2-common libcairo-gobject2 libcairo-script-interpreter2 libcairo2 libcairo2-dev libcanberra0 libcroco3 libcups2 libdatrie1 libdbus-1-dev libdbus-glib-1-2 libdbus-glib1.0-cil libdbus-glib1.0-cil-dev libdbus1.0-cil libdbus1.0-cil-dev libexif12 libexpat1 libexpat1-dev libfontconfig1 libfontconfig1-dev libfreetype6 libfreetype6-dev libgail18 libgamin0 libgconf2-4 libgconf2-dev libgconf2.0-cil libgconf2.0-cil-dev libgdiplus libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-dev libgif4 libgio-cil libgio2.0-cil-dev libglade2-0 libglade2.0-cil libglib2.0-bin libglib2.0-cil libglib2.0-cil-dev libglib2.0-data libglib2.0-dev libgnome-desktop-2-17 libgnome-keyring0 libgnome-keyring1.0-cil libgnome-keyring1.0-cil-dev libgnome-vfs2.0-cil libgnome-vfs2.0-cil-dev libgnome2-0 libgnome2-common libgnome2.0-cil-dev libgnome2.24-cil libgnomecanvas2-0 libgnomecanvas2-common libgnomedesktop2.0-cil-dev libgnomedesktop2.20-cil libgnomeui-0 libgnomeui-common libgnomevfs2-0 libgnomevfs2-common libgtk2.0-0 libgtk2.0-cil libgtk2.0-cil-dev libgtk2.0-common libgtk2.0-dev libhtml-parser-perl libhtml-tagset-perl libhtml-tree-perl libice-dev libice6 libidl-dev libidl0 libjasper1 libjpeg62 libltdl7 libmagic1 libmono-accessibility1.0-cil libmono-accessibility2.0-cil libmono-addins-cil-dev libmono-addins-gui-cil-dev libmono-addins-gui0.2-cil libmono-addins0.2-cil libmono-bytefx0.7.6.1-cil libmono-bytefx0.7.6.2-cil libmono-c5-1.1-cil libmono-cairo1.0-cil libmono-cairo2.0-cil libmono-cecil-private-cil libmono-cil-dev libmono-corlib1.0-cil libmono-corlib2.0-cil libmono-cscompmgd7.0-cil libmono-cscompmgd8.0-cil libmono-data-tds1.0-cil libmono-data-tds2.0-cil libmono-data1.0-cil libmono-data2.0-cil libmono-db2-1.0-cil libmono-debugger-soft0.0-cil libmono-dev libmono-getoptions1.0-cil libmono-getoptions2.0-cil libmono-i18n-west1.0-cil libmono-i18n-west2.0-cil libmono-i18n1.0-cil libmono-i18n2.0-cil libmono-ldap1.0-cil libmono-ldap2.0-cil libmono-management2.0-cil libmono-messaging-rabbitmq2.0-cil libmono-messaging2.0-cil libmono-microsoft-build2.0-cil libmono-microsoft7.0-cil libmono-microsoft8.0-cil libmono-npgsql1.0-cil libmono-npgsql2.0-cil libmono-oracle1.0-cil libmono-oracle2.0-cil libmono-peapi1.0-cil libmono-peapi2.0-cil libmono-posix1.0-cil libmono-posix2.0-cil libmono-rabbitmq2.0-cil libmono-relaxng1.0-cil libmono-relaxng2.0-cil libmono-security1.0-cil libmono-security2.0-cil libmono-sharpzip0.6-cil libmono-sharpzip0.84-cil libmono-sharpzip2.6-cil libmono-sharpzip2.84-cil libmono-simd2.0-cil libmono-sqlite1.0-cil libmono-sqlite2.0-cil libmono-system-data-linq2.0-cil libmono-system-data1.0-cil libmono-system-data2.0-cil libmono-system-ldap1.0-cil libmono-system-ldap2.0-cil libmono-system-messaging1.0-cil libmono-system-messaging2.0-cil libmono-system-runtime1.0-cil libmono-system-runtime2.0-cil libmono-system-web-mvc1.0-cil libmono-system-web-mvc2.0-cil libmono-system-web1.0-cil libmono-system-web2.0-cil libmono-system1.0-cil libmono-system2.0-cil libmono-tasklets2.0-cil libmono-wcf3.0-cil libmono-webbrowser0.5-cil libmono-windowsbase3.0-cil libmono-winforms1.0-cil libmono-winforms2.0-cil libmono0 libmono1.0-cil libmono2.0-cil libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libnotify-cil-dev libnotify0.4-cil libnunit-cil-dev libnunit2.4-cil libogg0 liborbit2 liborbit2-dev libpango1.0-0 libpango1.0-dev libpipeline1 libpixman-1-0 libpixman-1-dev libpng12-dev libpopt0 libpthread-stubs0 libpthread-stubs0-dev libpython2.7 librsvg2-2 librsvg2-2.0-cil-dev librsvg2-2.18-cil libsm-dev libsm6 libsqlite0 libsqlite3-0 libstartup-notification0 libtdb1 libthai-data libthai0 libtiff4 libunistring0 liburi-perl libvorbis0a libvorbisfile3 libwnck-common libwnck1.0-cil-dev libwnck2.20-cil libwnck22 libwww-perl libx11-6 libx11-data libx11-dev libxau-dev libxau6 libxcb-atom1 libxcb-aux0 libxcb-event1 libxcb-render0 libxcb-render0-dev libxcb-shm0 libxcb-shm0-dev libxcb1 libxcb1-dev libxcomposite-dev libxcomposite1 libxcursor-dev libxcursor1 libxdamage-dev libxdamage1 libxdmcp-dev libxdmcp6 libxext-dev libxext6 libxfixes-dev libxfixes3 libxft-dev libxft2 libxi-dev libxi6 libxinerama-dev libxinerama1 libxml-dom-perl libxml-libxml-perl libxml-namespacesupport-perl libxml-parser-perl libxml-perl libxml-regexp-perl libxml-sax-perl libxml2 libxml2-utils libxrandr-dev libxrandr2 libxrender-dev libxrender1 libxres1 m4 man-db mime-support mono-2.0-devel mono-2.0-gac mono-devel mono-gac mono-gmcs mono-runtime mono-utils pkg-config po-debconf psmisc python python2.7 shared-mime-info ttf-dejavu-core ucf x11-common x11proto-composite-dev x11proto-core-dev x11proto-damage-dev x11proto-fixes-dev x11proto-input-dev x11proto-kb-dev x11proto-randr-dev x11proto-render-dev x11proto-xext-dev x11proto-xinerama-dev xorg-sgml-doctools xtrans-dev zlib1g-dev 0 upgraded, 312 newly installed, 0 to remove and 0 not upgraded. Need to get 72.1 MB of archives. After this operation, 245 MB of additional disk space will be used. WARNING: The following packages cannot be authenticated! libexpat1 libsqlite3-0 libfreetype6 ucf ttf-dejavu-core fontconfig-config libfontconfig1 libxau6 libxdmcp6 libxcb1 libx11-data libx11-6 libxcb-render0 libxcb-shm0 libxext6 libxrender1 libatk1.0-data libatk1.0-0 libavahi-common-data libavahi-common3 libavahi-client3 libavahi-glib1 x11-common libice6 x11proto-core-dev libice-dev libpixman-1-0 libcairo2 libdatrie1 libthai-data libthai0 libxft2 fontconfig libpango1.0-0 libsm6 libjpeg62 libtiff4 libxcomposite1 libxfixes3 libxcursor1 libxdamage1 libxi6 libxinerama1 libxrandr2 xtrans-dev libmagic1 file libpopt0 mime-support python2.7 python bsdmainutils gettext-base groff-base libdbus-glib-1-2 liburi-perl libhtml-tagset-perl libhtml-parser-perl libhtml-tree-perl libpipeline1 libpython2.7 libwww-perl libxml-parser-perl libxml2 man-db psmisc m4 autoconf autotools-dev automake cli-common html2text libcroco3 libunistring0 gettext intltool-debian po-debconf debhelper libmono0 libmono-posix2.0-cil libmono-system2.0-cil libmono-security2.0-cil mono-2.0-gac mono-gac mono-runtime libmono-corlib2.0-cil libmono-corlib1.0-cil mono-utils libmono-cecil-private-cil libmono-getoptions2.0-cil libmono-system1.0-cil libmono-relaxng1.0-cil libmono-relaxng2.0-cil libmono-security1.0-cil libmono-data-tds2.0-cil libmono-system-data2.0-cil libmono-messaging2.0-cil libmono-system-messaging2.0-cil libsqlite0 libmono-sqlite2.0-cil libmono-sharpzip2.84-cil libmono2.0-cil libexif12 libgif4 libgdiplus libmono-system-web2.0-cil libmono-wcf3.0-cil libmono-system-data-linq2.0-cil libmono-data-tds1.0-cil libmono-system-data1.0-cil libmono-system-web1.0-cil libmono-system-runtime1.0-cil libmono-peapi2.0-cil mono-gmcs libglib2.0-data libglib2.0-bin pkg-config zlib1g-dev libglib2.0-dev libmono-dev mono-2.0-devel libmono-sharpzip0.84-cil libmono1.0-cil libmono-posix1.0-cil libmono-getoptions1.0-cil libmono-data1.0-cil libmono-data2.0-cil libmono-c5-1.1-cil libmono-webbrowser0.5-cil libmono-management2.0-cil libmono-rabbitmq2.0-cil libmono-messaging-rabbitmq2.0-cil libmono-simd2.0-cil libmono-i18n-west1.0-cil libmono-i18n1.0-cil libmono-i18n-west2.0-cil libmono-i18n2.0-cil libmono-system-messaging1.0-cil libmono-system-web-mvc1.0-cil libmono-system-web-mvc2.0-cil libmono-system-runtime2.0-cil libmono-ldap1.0-cil libmono-system-ldap1.0-cil libmono-ldap2.0-cil libmono-system-ldap2.0-cil libmono-accessibility1.0-cil libmono-winforms1.0-cil libmono-accessibility2.0-cil libmono-winforms2.0-cil libmono-cairo1.0-cil libmono-cairo2.0-cil libmono-sharpzip0.6-cil libmono-sharpzip2.6-cil libmono-npgsql1.0-cil libmono-npgsql2.0-cil libmono-bytefx0.7.6.1-cil libmono-bytefx0.7.6.2-cil libmono-db2-1.0-cil libmono-oracle1.0-cil libmono-oracle2.0-cil libmono-sqlite1.0-cil libmono-cscompmgd7.0-cil libmono-cscompmgd8.0-cil libmono-microsoft-build2.0-cil libmono-microsoft7.0-cil libmono-microsoft8.0-cil libmono-peapi1.0-cil libmono-debugger-soft0.0-cil libmono-tasklets2.0-cil libmono-windowsbase3.0-cil libnunit2.4-cil libnunit-cil-dev libmono-cil-dev mono-devel libxml-perl libxml-regexp-perl libxml-dom-perl cli-common-dev dbus dbus-x11 libgamin0 gamin libidl0 liborbit2 gconf2-common libgconf2-4 gconf2 gnome-mime-data libxml-namespacesupport-perl libxml-sax-perl libxml-libxml-perl libglib2.0-cil gtk-sharp2-gapi intltool libart-2.0-2 libart2.0-cil libart2.0-cil-dev libasound2 libatk1.0-dev libbonobo2-common libbonobo2-0 libjasper1 libgdk-pixbuf2.0-0 libgtk2.0-common libcups2 shared-mime-info libgtk2.0-0 libglade2-0 libltdl7 libtdb1 libogg0 libvorbis0a libvorbisfile3 libcanberra0 libgnomevfs2-common libgnomevfs2-0 libgnome2-common libgnome2-0 libgail18 libgnomecanvas2-common libgnomecanvas2-0 libbonoboui2-common libbonoboui2-0 libcairo-gobject2 libcairo-script-interpreter2 libexpat1-dev libfreetype6-dev libfontconfig1-dev libxau-dev libxdmcp-dev x11proto-input-dev x11proto-kb-dev libpthread-stubs0 libpthread-stubs0-dev libxcb1-dev libx11-dev x11proto-render-dev libxrender-dev libpng12-dev libsm-dev libpixman-1-dev libxcb-render0-dev libxcb-shm0-dev libcairo2-dev libdbus-1-dev libdbus1.0-cil libdbus-glib1.0-cil libdbus1.0-cil-dev libdbus-glib1.0-cil-dev libidl-dev liborbit2-dev libgconf2-dev libgconf2.0-cil libgconf2.0-cil-dev libgdk-pixbuf2.0-dev libgio-cil libgio2.0-cil-dev libgtk2.0-cil libglade2.0-cil libglib2.0-cil-dev libxcb-atom1 libxcb-aux0 libxcb-event1 libstartup-notification0 libgnome-desktop-2-17 libgnome-keyring0 libgnome-keyring1.0-cil libgnome-keyring1.0-cil-dev libgnome-vfs2.0-cil libgnome-vfs2.0-cil-dev libgnomeui-common libgnomeui-0 libgnome2.24-cil libgtk2.0-cil-dev libgnome2.0-cil-dev libgnomedesktop2.20-cil libgnomedesktop2.0-cil-dev libxft-dev libpango1.0-dev x11proto-xext-dev libxext-dev x11proto-xinerama-dev libxinerama-dev xorg-sgml-doctools libxi-dev x11proto-randr-dev libxrandr-dev x11proto-fixes-dev libxfixes-dev libxcursor-dev x11proto-composite-dev libxcomposite-dev x11proto-damage-dev libxdamage-dev libxml2-utils libgtk2.0-dev libmono-addins0.2-cil libmono-addins-cil-dev libmono-addins-gui0.2-cil libmono-addins-gui-cil-dev libndesk-dbus1.0-cil libndesk-dbus-glib1.0-cil libnotify0.4-cil libnotify-cil-dev librsvg2-2 librsvg2-2.18-cil librsvg2-2.0-cil-dev libwnck-common libxres1 libwnck22 libwnck2.20-cil libwnck1.0-cil-dev Authentication warning overridden. Get:1 http://ftpmaster.internal/ubuntu/ natty/main libexpat1 i386 2.0.1-7ubuntu3 [135 kB] Get:2 http://ftpmaster.internal/ubuntu/ natty/main libsqlite3-0 i386 3.7.4-2ubuntu5 [308 kB] Get:3 http://ftpmaster.internal/ubuntu/ natty/main libfreetype6 i386 2.4.4-1ubuntu2 [314 kB] Get:4 http://ftpmaster.internal/ubuntu/ natty/main ucf all 3.0025+nmu1ubuntu1 [54.3 kB] Get:5 http://ftpmaster.internal/ubuntu/ natty/main ttf-dejavu-core all 2.31-1 [1450 kB] Get:6 http://ftpmaster.internal/ubuntu/ natty/main fontconfig-config all 2.8.0-2.1ubuntu3 [44.5 kB] Get:7 http://ftpmaster.internal/ubuntu/ natty/main libfontconfig1 i386 2.8.0-2.1ubuntu3 [116 kB] Get:8 http://ftpmaster.internal/ubuntu/ natty/main libxau6 i386 1:1.0.6-1ubuntu1 [7864 B] Get:9 http://ftpmaster.internal/ubuntu/ natty/main libxdmcp6 i386 1:1.1.0-1ubuntu1 [11.7 kB] Get:10 http://ftpmaster.internal/ubuntu/ natty/main libxcb1 i386 1.7-2ubuntu2 [36.8 kB] Get:11 http://ftpmaster.internal/ubuntu/ natty/main libx11-data all 2:1.4.2-1ubuntu3 [169 kB] Get:12 http://ftpmaster.internal/ubuntu/ natty/main libx11-6 i386 2:1.4.2-1ubuntu3 [735 kB] Get:13 http://ftpmaster.internal/ubuntu/ natty/main libxcb-render0 i386 1.7-2ubuntu2 [12.1 kB] Get:14 http://ftpmaster.internal/ubuntu/ natty/main libxcb-shm0 i386 1.7-2ubuntu2 [6536 B] Get:15 http://ftpmaster.internal/ubuntu/ natty/main libxext6 i386 2:1.2.0-2ubuntu1 [29.5 kB] Get:16 http://ftpmaster.internal/ubuntu/ natty/main libxrender1 i386 1:0.9.6-1ubuntu1 [18.6 kB] Get:17 http://ftpmaster.internal/ubuntu/ natty/main libatk1.0-data all 2.0.0-0ubuntu1 [11.7 kB] Get:18 http://ftpmaster.internal/ubuntu/ natty/main libatk1.0-0 i386 2.0.0-0ubuntu1 [50.7 kB] Get:19 http://ftpmaster.internal/ubuntu/ natty/main libavahi-common-data i386 0.6.30-0ubuntu2 [22.6 kB] Get:20 http://ftpmaster.internal/ubuntu/ natty/main libavahi-common3 i386 0.6.30-0ubuntu2 [36.6 kB] Get:21 http://ftpmaster.internal/ubuntu/ natty/main libavahi-client3 i386 0.6.30-0ubuntu2 [41.0 kB] Get:22 http://ftpmaster.internal/ubuntu/ natty/main libavahi-glib1 i386 0.6.30-0ubuntu2 [22.4 kB] Get:23 http://ftpmaster.internal/ubuntu/ natty/main x11-common all 1:7.6+4ubuntu3 [69.2 kB] Get:24 http://ftpmaster.internal/ubuntu/ natty/main libice6 i386 2:1.0.7-1ubuntu1 [42.0 kB] Get:25 http://ftpmaster.internal/ubuntu/ natty/main x11proto-core-dev all 7.0.20-1 [294 kB] Get:26 http://ftpmaster.internal/ubuntu/ natty/main libice-dev i386 2:1.0.7-1ubuntu1 [127 kB] Get:27 http://ftpmaster.internal/ubuntu/ natty/main libpixman-1-0 i386 0.20.2-0ubuntu1 [180 kB] Get:28 http://ftpmaster.internal/ubuntu/ natty/main libcairo2 i386 1.10.2-2ubuntu2 [452 kB] Get:29 http://ftpmaster.internal/ubuntu/ natty/main libdatrie1 i386 0.2.4-1 [25.9 kB] Get:30 http://ftpmaster.internal/ubuntu/ natty/main libthai-data all 0.1.14-2ubuntu1 [175 kB] Get:31 http://ftpmaster.internal/ubuntu/ natty/main libthai0 i386 0.1.14-2ubuntu1 [17.5 kB] Get:32 http://ftpmaster.internal/ubuntu/ natty/main libxft2 i386 2.2.0-2ubuntu2 [38.3 kB] Get:33 http://ftpmaster.internal/ubuntu/ natty/main fontconfig i386 2.8.0-2.1ubuntu3 [155 kB] Get:34 http://ftpmaster.internal/ubuntu/ natty/main libpango1.0-0 i386 1.28.4-0ubuntu1 [334 kB] Get:35 http://ftpmaster.internal/ubuntu/ natty/main libsm6 i386 2:1.2.0-1ubuntu1 [16.5 kB] Get:36 http://ftpmaster.internal/ubuntu/ natty/main libjpeg62 i386 6b1-1ubuntu1 [80.3 kB] Get:37 http://ftpmaster.internal/ubuntu/ natty/main libtiff4 i386 3.9.4-5ubuntu5 [131 kB] Get:38 http://ftpmaster.internal/ubuntu/ natty/main libxcomposite1 i386 1:0.4.3-1ubuntu1 [7312 B] Get:39 http://ftpmaster.internal/ubuntu/ natty/main libxfixes3 i386 1:4.0.5-1ubuntu1 [10.8 kB] Get:40 http://ftpmaster.internal/ubuntu/ natty/main libxcursor1 i386 1:1.1.11-1ubuntu1 [20.9 kB] Get:41 http://ftpmaster.internal/ubuntu/ natty/main libxdamage1 i386 1:1.1.3-1ubuntu1 [7048 B] Get:42 http://ftpmaster.internal/ubuntu/ natty/main libxi6 i386 2:1.4.1-1ubuntu2 [29.6 kB] Get:43 http://ftpmaster.internal/ubuntu/ natty/main libxinerama1 i386 2:1.1.1-1ubuntu1 [7752 B] Get:44 http://ftpmaster.internal/ubuntu/ natty/main libxrandr2 i386 2:1.3.1-1ubuntu1 [16.4 kB] Get:45 http://ftpmaster.internal/ubuntu/ natty/main xtrans-dev all 1.2.6-1 [80.8 kB] Get:46 http://ftpmaster.internal/ubuntu/ natty/main libmagic1 i386 5.04-5ubuntu2 [204 kB] Get:47 http://ftpmaster.internal/ubuntu/ natty/main file i386 5.04-5ubuntu2 [22.1 kB] Get:48 http://ftpmaster.internal/ubuntu/ natty/main libpopt0 i386 1.16-1 [33.9 kB] Get:49 http://ftpmaster.internal/ubuntu/ natty/main mime-support all 3.51-1ubuntu1 [30.7 kB] Get:50 http://ftpmaster.internal/ubuntu/ natty/main python2.7 i386 2.7.1-5ubuntu1 [2500 kB] Get:51 http://ftpmaster.internal/ubuntu/ natty/main python all 2.7.1-0ubuntu5 [163 kB] Get:52 http://ftpmaster.internal/ubuntu/ natty/main bsdmainutils i386 8.2.2 [191 kB] Get:53 http://ftpmaster.internal/ubuntu/ natty/main gettext-base i386 0.18.1.1-3ubuntu1 [56.6 kB] Get:54 http://ftpmaster.internal/ubuntu/ natty/main groff-base i386 1.21-5 [990 kB] Get:55 http://ftpmaster.internal/ubuntu/ natty/main libdbus-glib-1-2 i386 0.92-0ubuntu1 [66.0 kB] Get:56 http://ftpmaster.internal/ubuntu/ natty/main liburi-perl all 1.56-1 [90.6 kB] Get:57 http://ftpmaster.internal/ubuntu/ natty/main libhtml-tagset-perl all 3.20-2 [13.5 kB] Get:58 http://ftpmaster.internal/ubuntu/ natty/main libhtml-parser-perl i386 3.68-1 [100 kB] Get:59 http://ftpmaster.internal/ubuntu/ natty/main libhtml-tree-perl all 4.1-1 [206 kB] Get:60 http://ftpmaster.internal/ubuntu/ natty/main libpipeline1 i386 1.2.0-1 [23.5 kB] Get:61 http://ftpmaster.internal/ubuntu/ natty/main libpython2.7 i386 2.7.1-5ubuntu1 [1076 kB] Get:62 http://ftpmaster.internal/ubuntu/ natty/main libwww-perl all 5.837-1 [363 kB] Get:63 http://ftpmaster.internal/ubuntu/ natty/main libxml-parser-perl i386 2.36-1.1build3 [323 kB] Get:64 http://ftpmaster.internal/ubuntu/ natty/main libxml2 i386 2.7.8.dfsg-2 [607 kB] Get:65 http://ftpmaster.internal/ubuntu/ natty/main man-db i386 2.5.9-4 [676 kB] Get:66 http://ftpmaster.internal/ubuntu/ natty/main psmisc i386 22.13-1 [49.0 kB] Get:67 http://ftpmaster.internal/ubuntu/ natty/main m4 i386 1.4.14-3 [276 kB] Get:68 http://ftpmaster.internal/ubuntu/ natty/main autoconf all 2.67-2ubuntu1 [569 kB] Get:69 http://ftpmaster.internal/ubuntu/ natty/main autotools-dev all 20100122.1 [70.7 kB] Get:70 http://ftpmaster.internal/ubuntu/ natty/main automake all 1:1.11.1-1ubuntu1 [544 kB] Get:71 http://ftpmaster.internal/ubuntu/ natty/main cli-common all 0.7.1 [182 kB] Get:72 http://ftpmaster.internal/ubuntu/ natty/main html2text i386 1.3.2a-15 [101 kB] Get:73 http://ftpmaster.internal/ubuntu/ natty/main libcroco3 i386 0.6.2-1 [92.5 kB] Get:74 http://ftpmaster.internal/ubuntu/ natty/main libunistring0 i386 0.9.3-3 [423 kB] Get:75 http://ftpmaster.internal/ubuntu/ natty/main gettext i386 0.18.1.1-3ubuntu1 [1180 kB] Get:76 http://ftpmaster.internal/ubuntu/ natty/main intltool-debian all 0.35.0+20060710.1 [31.6 kB] Get:77 http://ftpmaster.internal/ubuntu/ natty/main po-debconf all 1.0.16+nmu1 [212 kB] Get:78 http://ftpmaster.internal/ubuntu/ natty/main debhelper all 8.1.2ubuntu4 [482 kB] Get:79 http://ftpmaster.internal/ubuntu/ natty/main libmono0 i386 2.6.7-5ubuntu2 [1156 kB] Get:80 http://ftpmaster.internal/ubuntu/ natty/main libmono-posix2.0-cil all 2.6.7-5ubuntu2 [100 kB] Get:81 http://ftpmaster.internal/ubuntu/ natty/main libmono-system2.0-cil all 2.6.7-5ubuntu2 [1561 kB] Get:82 http://ftpmaster.internal/ubuntu/ natty/main libmono-security2.0-cil all 2.6.7-5ubuntu2 [143 kB] Get:83 http://ftpmaster.internal/ubuntu/ natty/main mono-2.0-gac all 2.6.7-5ubuntu2 [39.1 kB] Get:84 http://ftpmaster.internal/ubuntu/ natty/main mono-gac all 2.6.7-5ubuntu2 [30.8 kB] Get:85 http://ftpmaster.internal/ubuntu/ natty/main mono-runtime i386 2.6.7-5ubuntu2 [1253 kB] Get:86 http://ftpmaster.internal/ubuntu/ natty/main libmono-corlib2.0-cil all 2.6.7-5ubuntu2 [918 kB] Get:87 http://ftpmaster.internal/ubuntu/ natty/main libmono-corlib1.0-cil all 2.6.7-5ubuntu2 [754 kB] Get:88 http://ftpmaster.internal/ubuntu/ natty/main mono-utils i386 2.6.7-5ubuntu2 [822 kB] Get:89 http://ftpmaster.internal/ubuntu/ natty/main libmono-cecil-private-cil all 2.6.7-5ubuntu2 [177 kB] Get:90 http://ftpmaster.internal/ubuntu/ natty/main libmono-getoptions2.0-cil all 2.6.7-5ubuntu2 [46.0 kB] Get:91 http://ftpmaster.internal/ubuntu/ natty/main libmono-system1.0-cil all 2.6.7-5ubuntu2 [965 kB] Get:92 http://ftpmaster.internal/ubuntu/ natty/main libmono-relaxng1.0-cil all 2.6.7-5ubuntu2 [111 kB] Get:93 http://ftpmaster.internal/ubuntu/ natty/main libmono-relaxng2.0-cil all 2.6.7-5ubuntu2 [111 kB] Get:94 http://ftpmaster.internal/ubuntu/ natty/main libmono-security1.0-cil all 2.6.7-5ubuntu2 [142 kB] Get:95 http://ftpmaster.internal/ubuntu/ natty/main libmono-data-tds2.0-cil all 2.6.7-5ubuntu2 [64.0 kB] Get:96 http://ftpmaster.internal/ubuntu/ natty/main libmono-system-data2.0-cil all 2.6.7-5ubuntu2 [336 kB] Get:97 http://ftpmaster.internal/ubuntu/ natty/main libmono-messaging2.0-cil all 2.6.7-5ubuntu2 [39.0 kB] Get:98 http://ftpmaster.internal/ubuntu/ natty/main libmono-system-messaging2.0-cil all 2.6.7-5ubuntu2 [54.9 kB] Get:99 http://ftpmaster.internal/ubuntu/ natty/main libsqlite0 i386 2.8.17-6build2 [181 kB] Get:100 http://ftpmaster.internal/ubuntu/ natty/main libmono-sqlite2.0-cil all 2.6.7-5ubuntu2 [101 kB] Get:101 http://ftpmaster.internal/ubuntu/ natty/main libmono-sharpzip2.84-cil all 2.6.7-5ubuntu2 [82.6 kB] Get:102 http://ftpmaster.internal/ubuntu/ natty/main libmono2.0-cil all 2.6.7-5ubuntu2 [61.6 kB] Get:103 http://ftpmaster.internal/ubuntu/ natty/main libexif12 i386 0.6.20-0ubuntu1 [81.5 kB] Get:104 http://ftpmaster.internal/ubuntu/ natty/main libgif4 i386 4.1.6-9 [40.0 kB] Get:105 http://ftpmaster.internal/ubuntu/ natty/main libgdiplus i386 2.6.7-3ubuntu1 [152 kB] Get:106 http://ftpmaster.internal/ubuntu/ natty/main libmono-system-web2.0-cil all 2.6.7-5ubuntu2 [1329 kB] Get:107 http://ftpmaster.internal/ubuntu/ natty/main libmono-wcf3.0-cil all 2.6.7-5ubuntu2 [631 kB] Get:108 http://ftpmaster.internal/ubuntu/ natty/main libmono-system-data-linq2.0-cil all 2.6.7-5ubuntu2 [206 kB] Get:109 http://ftpmaster.internal/ubuntu/ natty/main libmono-data-tds1.0-cil all 2.6.7-5ubuntu2 [60.3 kB] Get:110 http://ftpmaster.internal/ubuntu/ natty/main libmono-system-data1.0-cil all 2.6.7-5ubuntu2 [251 kB] Get:111 http://ftpmaster.internal/ubuntu/ natty/main libmono-system-web1.0-cil all 2.6.7-5ubuntu2 [444 kB] Get:112 http://ftpmaster.internal/ubuntu/ natty/main libmono-system-runtime1.0-cil all 2.6.7-5ubuntu2 [106 kB] Get:113 http://ftpmaster.internal/ubuntu/ natty/main libmono-peapi2.0-cil all 2.6.7-5ubuntu2 [69.0 kB] Get:114 http://ftpmaster.internal/ubuntu/ natty/main mono-gmcs all 2.6.7-5ubuntu2 [425 kB] Get:115 http://ftpmaster.internal/ubuntu/ natty/main libglib2.0-data all 2.28.5-0ubuntu1 [69.6 kB] Get:116 http://ftpmaster.internal/ubuntu/ natty/main libglib2.0-bin i386 2.28.5-0ubuntu1 [27.2 kB] Get:117 http://ftpmaster.internal/ubuntu/ natty/main pkg-config i386 0.25-1.1ubuntu1 [39.2 kB] Get:118 http://ftpmaster.internal/ubuntu/ natty/main zlib1g-dev i386 1:1.2.3.4.dfsg-3ubuntu3 [160 kB] Get:119 http://ftpmaster.internal/ubuntu/ natty/main libglib2.0-dev i386 2.28.5-0ubuntu1 [1417 kB] Get:120 http://ftpmaster.internal/ubuntu/ natty/main libmono-dev i386 2.6.7-5ubuntu2 [1601 kB] Get:121 http://ftpmaster.internal/ubuntu/ natty/main mono-2.0-devel all 2.6.7-5ubuntu2 [219 kB] Get:122 http://ftpmaster.internal/ubuntu/ natty/main libmono-sharpzip0.84-cil all 2.6.7-5ubuntu2 [82.5 kB] Get:123 http://ftpmaster.internal/ubuntu/ natty/main libmono1.0-cil all 2.6.7-5ubuntu2 [55.3 kB] Get:124 http://ftpmaster.internal/ubuntu/ natty/main libmono-posix1.0-cil all 2.6.7-5ubuntu2 [99.8 kB] Get:125 http://ftpmaster.internal/ubuntu/ natty/main libmono-getoptions1.0-cil all 2.6.7-5ubuntu2 [45.9 kB] Get:126 http://ftpmaster.internal/ubuntu/ natty/main libmono-data1.0-cil all 2.6.7-5ubuntu2 [112 kB] Get:127 http://ftpmaster.internal/ubuntu/ natty/main libmono-data2.0-cil all 2.6.7-5ubuntu2 [118 kB] Get:128 http://ftpmaster.internal/ubuntu/ natty/main libmono-c5-1.1-cil all 2.6.7-5ubuntu2 [136 kB] Get:129 http://ftpmaster.internal/ubuntu/ natty/main libmono-webbrowser0.5-cil all 2.6.7-5ubuntu2 [86.4 kB] Get:130 http://ftpmaster.internal/ubuntu/ natty/main libmono-management2.0-cil all 2.6.7-5ubuntu2 [30.4 kB] Get:131 http://ftpmaster.internal/ubuntu/ natty/main libmono-rabbitmq2.0-cil all 2.6.7-5ubuntu2 [162 kB] Get:132 http://ftpmaster.internal/ubuntu/ natty/main libmono-messaging-rabbitmq2.0-cil all 2.6.7-5ubuntu2 [39.9 kB] Get:133 http://ftpmaster.internal/ubuntu/ natty/main libmono-simd2.0-cil all 2.6.7-5ubuntu2 [47.1 kB] Get:134 http://ftpmaster.internal/ubuntu/ natty/main libmono-i18n-west1.0-cil all 2.6.7-5ubuntu2 [53.5 kB] Get:135 http://ftpmaster.internal/ubuntu/ natty/main libmono-i18n1.0-cil all 2.6.7-5ubuntu2 [376 kB] Get:136 http://ftpmaster.internal/ubuntu/ natty/main libmono-i18n-west2.0-cil all 2.6.7-5ubuntu2 [55.2 kB] Get:137 http://ftpmaster.internal/ubuntu/ natty/main libmono-i18n2.0-cil all 2.6.7-5ubuntu2 [378 kB] Get:138 http://ftpmaster.internal/ubuntu/ natty/main libmono-system-messaging1.0-cil all 2.6.7-5ubuntu2 [54.8 kB] Get:139 http://ftpmaster.internal/ubuntu/ natty/main libmono-system-web-mvc1.0-cil all 2.6.7-5ubuntu2 [107 kB] Get:140 http://ftpmaster.internal/ubuntu/ natty/main libmono-system-web-mvc2.0-cil all 2.6.7-5ubuntu2 [176 kB] Get:141 http://ftpmaster.internal/ubuntu/ natty/main libmono-system-runtime2.0-cil all 2.6.7-5ubuntu2 [111 kB] Get:142 http://ftpmaster.internal/ubuntu/ natty/main libmono-ldap1.0-cil all 2.6.7-5ubuntu2 [126 kB] Get:143 http://ftpmaster.internal/ubuntu/ natty/main libmono-system-ldap1.0-cil all 2.6.7-5ubuntu2 [44.0 kB] Get:144 http://ftpmaster.internal/ubuntu/ natty/main libmono-ldap2.0-cil all 2.6.7-5ubuntu2 [126 kB] Get:145 http://ftpmaster.internal/ubuntu/ natty/main libmono-system-ldap2.0-cil all 2.6.7-5ubuntu2 [44.2 kB] Get:146 http://ftpmaster.internal/ubuntu/ natty/main libmono-accessibility1.0-cil all 2.6.7-5ubuntu2 [29.4 kB] Get:147 http://ftpmaster.internal/ubuntu/ natty/main libmono-winforms1.0-cil all 2.6.7-5ubuntu2 [847 kB] Get:148 http://ftpmaster.internal/ubuntu/ natty/main libmono-accessibility2.0-cil all 2.6.7-5ubuntu2 [29.5 kB] Get:149 http://ftpmaster.internal/ubuntu/ natty/main libmono-winforms2.0-cil all 2.6.7-5ubuntu2 [1206 kB] Get:150 http://ftpmaster.internal/ubuntu/ natty/main libmono-cairo1.0-cil all 2.6.7-5ubuntu2 [47.4 kB] Get:151 http://ftpmaster.internal/ubuntu/ natty/main libmono-cairo2.0-cil all 2.6.7-5ubuntu2 [47.5 kB] Get:152 http://ftpmaster.internal/ubuntu/ natty/main libmono-sharpzip0.6-cil all 2.6.7-5ubuntu2 [73.0 kB] Get:153 http://ftpmaster.internal/ubuntu/ natty/main libmono-sharpzip2.6-cil all 2.6.7-5ubuntu2 [73.0 kB] Get:154 http://ftpmaster.internal/ubuntu/ natty/main libmono-npgsql1.0-cil all 2.6.7-5ubuntu2 [90.9 kB] Get:155 http://ftpmaster.internal/ubuntu/ natty/main libmono-npgsql2.0-cil all 2.6.7-5ubuntu2 [91.0 kB] Get:156 http://ftpmaster.internal/ubuntu/ natty/main libmono-bytefx0.7.6.1-cil all 2.6.7-5ubuntu2 [68.5 kB] Get:157 http://ftpmaster.internal/ubuntu/ natty/main libmono-bytefx0.7.6.2-cil all 2.6.7-5ubuntu2 [68.6 kB] Get:158 http://ftpmaster.internal/ubuntu/ natty/main libmono-db2-1.0-cil all 2.6.7-5ubuntu2 [55.5 kB] Get:159 http://ftpmaster.internal/ubuntu/ natty/main libmono-oracle1.0-cil all 2.6.7-5ubuntu2 [80.8 kB] Get:160 http://ftpmaster.internal/ubuntu/ natty/main libmono-oracle2.0-cil all 2.6.7-5ubuntu2 [89.7 kB] Get:161 http://ftpmaster.internal/ubuntu/ natty/main libmono-sqlite1.0-cil all 2.6.7-5ubuntu2 [60.1 kB] Get:162 http://ftpmaster.internal/ubuntu/ natty/main libmono-cscompmgd7.0-cil all 2.6.7-5ubuntu2 [32.0 kB] Get:163 http://ftpmaster.internal/ubuntu/ natty/main libmono-cscompmgd8.0-cil all 2.6.7-5ubuntu2 [32.5 kB] Get:164 http://ftpmaster.internal/ubuntu/ natty/main libmono-microsoft-build2.0-cil all 2.6.7-5ubuntu2 [359 kB] Get:165 http://ftpmaster.internal/ubuntu/ natty/main libmono-microsoft7.0-cil all 2.6.7-5ubuntu2 [155 kB] Get:166 http://ftpmaster.internal/ubuntu/ natty/main libmono-microsoft8.0-cil all 2.6.7-5ubuntu2 [155 kB] Get:167 http://ftpmaster.internal/ubuntu/ natty/main libmono-peapi1.0-cil all 2.6.7-5ubuntu2 [68.8 kB] Get:168 http://ftpmaster.internal/ubuntu/ natty/main libmono-debugger-soft0.0-cil all 2.6.7-5ubuntu2 [72.9 kB] Get:169 http://ftpmaster.internal/ubuntu/ natty/main libmono-tasklets2.0-cil all 2.6.7-5ubuntu2 [29.1 kB] Get:170 http://ftpmaster.internal/ubuntu/ natty/main libmono-windowsbase3.0-cil all 2.6.7-5ubuntu2 [93.1 kB] Get:171 http://ftpmaster.internal/ubuntu/ natty/main libnunit2.4-cil all 2.4.7+dfsg-6 [118 kB] Get:172 http://ftpmaster.internal/ubuntu/ natty/main libnunit-cil-dev all 2.4.7+dfsg-6 [4344 B] Get:173 http://ftpmaster.internal/ubuntu/ natty/main libmono-cil-dev all 2.6.7-5ubuntu2 [27.8 kB] Get:174 http://ftpmaster.internal/ubuntu/ natty/main mono-devel all 2.6.7-5ubuntu2 [1533 kB] Get:175 http://ftpmaster.internal/ubuntu/ natty/main libxml-perl all 0.08-2 [113 kB] Get:176 http://ftpmaster.internal/ubuntu/ natty/main libxml-regexp-perl all 0.03-8 [8066 B] Get:177 http://ftpmaster.internal/ubuntu/ natty/main libxml-dom-perl all 1.44-1 [185 kB] Get:178 http://ftpmaster.internal/ubuntu/ natty/main cli-common-dev all 0.7.1 [41.8 kB] Get:179 http://ftpmaster.internal/ubuntu/ natty/main dbus i386 1.4.6-1ubuntu6 [207 kB] Get:180 http://ftpmaster.internal/ubuntu/ natty/main dbus-x11 i386 1.4.6-1ubuntu6 [29.5 kB] Get:181 http://ftpmaster.internal/ubuntu/ natty/main libgamin0 i386 0.1.10-2ubuntu1 [16.6 kB] Get:182 http://ftpmaster.internal/ubuntu/ natty/main gamin i386 0.1.10-2ubuntu1 [42.1 kB] Get:183 http://ftpmaster.internal/ubuntu/ natty/main libidl0 i386 0.8.14-0.1ubuntu1 [72.9 kB] Get:184 http://ftpmaster.internal/ubuntu/ natty/main liborbit2 i386 1:2.14.19-0ubuntu2 [163 kB] Get:185 http://ftpmaster.internal/ubuntu/ natty/main gconf2-common all 2.32.2-0ubuntu1 [19.8 kB] Get:186 http://ftpmaster.internal/ubuntu/ natty/main libgconf2-4 i386 2.32.2-0ubuntu1 [167 kB] Get:187 http://ftpmaster.internal/ubuntu/ natty/main gconf2 i386 2.32.2-0ubuntu1 [74.5 kB] Get:188 http://ftpmaster.internal/ubuntu/ natty/main gnome-mime-data all 2.18.0-1 [362 kB] Get:189 http://ftpmaster.internal/ubuntu/ natty/main libxml-namespacesupport-perl all 1.09-3 [15.3 kB] Get:190 http://ftpmaster.internal/ubuntu/ natty/main libxml-sax-perl all 0.96+dfsg-2 [85.5 kB] Get:191 http://ftpmaster.internal/ubuntu/ natty/main libxml-libxml-perl i386 1.70.ds-1 [413 kB] Get:192 http://ftpmaster.internal/ubuntu/ natty/main libglib2.0-cil i386 2.12.10-1ubuntu1 [48.9 kB] Get:193 http://ftpmaster.internal/ubuntu/ natty/main gtk-sharp2-gapi i386 2.12.10-1ubuntu1 [68.7 kB] Get:194 http://ftpmaster.internal/ubuntu/ natty/main intltool all 0.41.1-1 [103 kB] Get:195 http://ftpmaster.internal/ubuntu/ natty/main libart-2.0-2 i386 2.3.21-1 [53.3 kB] Get:196 http://ftpmaster.internal/ubuntu/ natty/main libart2.0-cil all 2.24.2-0ubuntu1 [20.8 kB] Get:197 http://ftpmaster.internal/ubuntu/ natty/main libart2.0-cil-dev all 2.24.2-0ubuntu1 [10.1 kB] Get:198 http://ftpmaster.internal/ubuntu/ natty/main libasound2 i386 1.0.24.1-0ubuntu3 [368 kB] Get:199 http://ftpmaster.internal/ubuntu/ natty/main libatk1.0-dev i386 2.0.0-0ubuntu1 [113 kB] Get:200 http://ftpmaster.internal/ubuntu/ natty/main libbonobo2-common all 2.32.1-0ubuntu1 [56.7 kB] Get:201 http://ftpmaster.internal/ubuntu/ natty/main libbonobo2-0 i386 2.32.1-0ubuntu1 [222 kB] Get:202 http://ftpmaster.internal/ubuntu/ natty/main libjasper1 i386 1.900.1-7ubuntu2 [140 kB] Get:203 http://ftpmaster.internal/ubuntu/ natty/main libgdk-pixbuf2.0-0 i386 2.23.3-0ubuntu1 [177 kB] Get:204 http://ftpmaster.internal/ubuntu/ natty/main libgtk2.0-common all 2.24.4-0ubuntu1 [115 kB] Get:205 http://ftpmaster.internal/ubuntu/ natty/main libcups2 i386 1.4.6-4 [159 kB] Get:206 http://ftpmaster.internal/ubuntu/ natty/main shared-mime-info i386 0.90-1ubuntu1 [435 kB] Get:207 http://ftpmaster.internal/ubuntu/ natty/main libgtk2.0-0 i386 2.24.4-0ubuntu1 [2013 kB] Get:208 http://ftpmaster.internal/ubuntu/ natty/main libglade2-0 i386 1:2.6.4-1build1 [51.9 kB] Get:209 http://ftpmaster.internal/ubuntu/ natty/main libltdl7 i386 2.2.6b-2ubuntu3 [34.3 kB] Get:210 http://ftpmaster.internal/ubuntu/ natty/main libtdb1 i386 1.2.9-1fakesync1 [33.5 kB] Get:211 http://ftpmaster.internal/ubuntu/ natty/main libogg0 i386 1.2.0~dfsg-1 [16.6 kB] Get:212 http://ftpmaster.internal/ubuntu/ natty/main libvorbis0a i386 1.3.2-1ubuntu1 [93.7 kB] Get:213 http://ftpmaster.internal/ubuntu/ natty/main libvorbisfile3 i386 1.3.2-1ubuntu1 [20.3 kB] Get:214 http://ftpmaster.internal/ubuntu/ natty/main libcanberra0 i386 0.28-0ubuntu3 [37.4 kB] Get:215 http://ftpmaster.internal/ubuntu/ natty/main libgnomevfs2-common all 1:2.24.4-0ubuntu4 [24.3 kB] Get:216 http://ftpmaster.internal/ubuntu/ natty/main libgnomevfs2-0 i386 1:2.24.4-0ubuntu4 [271 kB] Get:217 http://ftpmaster.internal/ubuntu/ natty/main libgnome2-common all 2.32.1-0ubuntu3 [36.2 kB] Get:218 http://ftpmaster.internal/ubuntu/ natty/main libgnome2-0 i386 2.32.1-0ubuntu3 [60.3 kB] Get:219 http://ftpmaster.internal/ubuntu/ natty/main libgail18 i386 2.24.4-0ubuntu1 [18.6 kB] Get:220 http://ftpmaster.internal/ubuntu/ natty/main libgnomecanvas2-common all 2.30.3-0ubuntu1 [8990 B] Get:221 http://ftpmaster.internal/ubuntu/ natty/main libgnomecanvas2-0 i386 2.30.3-0ubuntu1 [83.8 kB] Get:222 http://ftpmaster.internal/ubuntu/ natty/main libbonoboui2-common all 2.24.5-0ubuntu1 [11.8 kB] Get:223 http://ftpmaster.internal/ubuntu/ natty/main libbonoboui2-0 i386 2.24.5-0ubuntu1 [164 kB] Get:224 http://ftpmaster.internal/ubuntu/ natty/main libcairo-gobject2 i386 1.10.2-2ubuntu2 [111 kB] Get:225 http://ftpmaster.internal/ubuntu/ natty/main libcairo-script-interpreter2 i386 1.10.2-2ubuntu2 [148 kB] Get:226 http://ftpmaster.internal/ubuntu/ natty/main libexpat1-dev i386 2.0.1-7ubuntu3 [211 kB] Get:227 http://ftpmaster.internal/ubuntu/ natty/main libfreetype6-dev i386 2.4.4-1ubuntu2 [726 kB] Get:228 http://ftpmaster.internal/ubuntu/ natty/main libfontconfig1-dev i386 2.8.0-2.1ubuntu3 [641 kB] Get:229 http://ftpmaster.internal/ubuntu/ natty/main libxau-dev i386 1:1.0.6-1ubuntu1 [11.2 kB] Get:230 http://ftpmaster.internal/ubuntu/ natty/main libxdmcp-dev i386 1:1.1.0-1ubuntu1 [46.0 kB] Get:231 http://ftpmaster.internal/ubuntu/ natty/main x11proto-input-dev all 2.0.1-1ubuntu1 [68.5 kB] Get:232 http://ftpmaster.internal/ubuntu/ natty/main x11proto-kb-dev all 1.0.5-1 [25.4 kB] Get:233 http://ftpmaster.internal/ubuntu/ natty/main libpthread-stubs0 i386 0.3-2 [3196 B] Get:234 http://ftpmaster.internal/ubuntu/ natty/main libpthread-stubs0-dev i386 0.3-2 [2414 B] Get:235 http://ftpmaster.internal/ubuntu/ natty/main libxcb1-dev i386 1.7-2ubuntu2 [72.6 kB] Get:236 http://ftpmaster.internal/ubuntu/ natty/main libx11-dev i386 2:1.4.2-1ubuntu3 [3104 kB] Get:237 http://ftpmaster.internal/ubuntu/ natty/main x11proto-render-dev all 2:0.11.1-1 [18.5 kB] Get:238 http://ftpmaster.internal/ubuntu/ natty/main libxrender-dev i386 1:0.9.6-1ubuntu1 [27.2 kB] Get:239 http://ftpmaster.internal/ubuntu/ natty/main libpng12-dev i386 1.2.44-1ubuntu3 [208 kB] Get:240 http://ftpmaster.internal/ubuntu/ natty/main libsm-dev i386 2:1.2.0-1ubuntu1 [87.7 kB] Get:241 http://ftpmaster.internal/ubuntu/ natty/main libpixman-1-dev i386 0.20.2-0ubuntu1 [206 kB] Get:242 http://ftpmaster.internal/ubuntu/ natty/main libxcb-render0-dev i386 1.7-2ubuntu2 [19.4 kB] Get:243 http://ftpmaster.internal/ubuntu/ natty/main libxcb-shm0-dev i386 1.7-2ubuntu2 [8006 B] Get:244 http://ftpmaster.internal/ubuntu/ natty/main libcairo2-dev i386 1.10.2-2ubuntu2 [8714 kB] Get:245 http://ftpmaster.internal/ubuntu/ natty/main libdbus-1-dev i386 1.4.6-1ubuntu6 [36.9 kB] Get:246 http://ftpmaster.internal/ubuntu/ natty/universe libdbus1.0-cil all 0.7.0-2 [55.0 kB] Get:247 http://ftpmaster.internal/ubuntu/ natty/universe libdbus-glib1.0-cil all 0.5.0-2 [7410 B] Get:248 http://ftpmaster.internal/ubuntu/ natty/universe libdbus1.0-cil-dev all 0.7.0-2 [3004 B] Get:249 http://ftpmaster.internal/ubuntu/ natty/universe libdbus-glib1.0-cil-dev all 0.5.0-2 [3016 B] Get:250 http://ftpmaster.internal/ubuntu/ natty/main libidl-dev i386 0.8.14-0.1ubuntu1 [84.0 kB] Get:251 http://ftpmaster.internal/ubuntu/ natty/main liborbit2-dev i386 1:2.14.19-0ubuntu2 [377 kB] Get:252 http://ftpmaster.internal/ubuntu/ natty/main libgconf2-dev i386 2.32.2-0ubuntu1 [208 kB] Get:253 http://ftpmaster.internal/ubuntu/ natty/main libgconf2.0-cil all 2.24.2-0ubuntu1 [13.8 kB] Get:254 http://ftpmaster.internal/ubuntu/ natty/main libgconf2.0-cil-dev all 2.24.2-0ubuntu1 [9242 B] Get:255 http://ftpmaster.internal/ubuntu/ natty/main libgdk-pixbuf2.0-dev i386 2.23.3-0ubuntu1 [47.9 kB] Get:256 http://ftpmaster.internal/ubuntu/ natty/main libgio-cil all 2.22.2-2 [68.0 kB] Get:257 http://ftpmaster.internal/ubuntu/ natty/main libgio2.0-cil-dev all 2.22.2-2 [23.8 kB] Get:258 http://ftpmaster.internal/ubuntu/ natty/main libgtk2.0-cil i386 2.12.10-1ubuntu1 [608 kB] Get:259 http://ftpmaster.internal/ubuntu/ natty/main libglade2.0-cil i386 2.12.10-1ubuntu1 [22.0 kB] Get:260 http://ftpmaster.internal/ubuntu/ natty/main libglib2.0-cil-dev i386 2.12.10-1ubuntu1 [4646 B] Get:261 http://ftpmaster.internal/ubuntu/ natty/main libxcb-atom1 i386 0.3.6-1build1 [9752 B] Get:262 http://ftpmaster.internal/ubuntu/ natty/main libxcb-aux0 i386 0.3.6-1build1 [8714 B] Get:263 http://ftpmaster.internal/ubuntu/ natty/main libxcb-event1 i386 0.3.6-1build1 [8732 B] Get:264 http://ftpmaster.internal/ubuntu/ natty/main libstartup-notification0 i386 0.10-1build1 [18.3 kB] Get:265 http://ftpmaster.internal/ubuntu/ natty/main libgnome-desktop-2-17 i386 1:2.32.1-0ubuntu5 [92.4 kB] Get:266 http://ftpmaster.internal/ubuntu/ natty/main libgnome-keyring0 i386 2.32.0-1ubuntu2 [47.7 kB] Get:267 http://ftpmaster.internal/ubuntu/ natty/universe libgnome-keyring1.0-cil i386 1.0.0-3 [16.5 kB] Get:268 http://ftpmaster.internal/ubuntu/ natty/universe libgnome-keyring1.0-cil-dev i386 1.0.0-3 [5716 B] Get:269 http://ftpmaster.internal/ubuntu/ natty/main libgnome-vfs2.0-cil all 2.24.2-0ubuntu1 [51.9 kB] Get:270 http://ftpmaster.internal/ubuntu/ natty/main libgnome-vfs2.0-cil-dev all 2.24.2-0ubuntu1 [20.7 kB] Get:271 http://ftpmaster.internal/ubuntu/ natty/main libgnomeui-common all 2.24.5-0ubuntu1 [16.4 kB] Get:272 http://ftpmaster.internal/ubuntu/ natty/main libgnomeui-0 i386 2.24.5-0ubuntu1 [215 kB] Get:273 http://ftpmaster.internal/ubuntu/ natty/main libgnome2.24-cil i386 2.24.2-0ubuntu1 [95.7 kB] Get:274 http://ftpmaster.internal/ubuntu/ natty/main libgtk2.0-cil-dev i386 2.12.10-1ubuntu1 [158 kB] Get:275 http://ftpmaster.internal/ubuntu/ natty/main libgnome2.0-cil-dev i386 2.24.2-0ubuntu1 [29.8 kB] Get:276 http://ftpmaster.internal/ubuntu/ natty/universe libgnomedesktop2.20-cil all 2.26.0-3build1 [10.9 kB] Get:277 http://ftpmaster.internal/ubuntu/ natty/universe libgnomedesktop2.0-cil-dev all 2.26.0-3build1 [7076 B] Get:278 http://ftpmaster.internal/ubuntu/ natty/main libxft-dev i386 2.2.0-2ubuntu2 [49.9 kB] Get:279 http://ftpmaster.internal/ubuntu/ natty/main libpango1.0-dev i386 1.28.4-0ubuntu1 [438 kB] Get:280 http://ftpmaster.internal/ubuntu/ natty/main x11proto-xext-dev all 7.1.99.0~git20110111.9df8b776-0ubuntu2 [254 kB] Get:281 http://ftpmaster.internal/ubuntu/ natty/main libxext-dev i386 2:1.2.0-2ubuntu1 [130 kB] Get:282 http://ftpmaster.internal/ubuntu/ natty/main x11proto-xinerama-dev all 1.2.1-1 [4870 B] Get:283 http://ftpmaster.internal/ubuntu/ natty/main libxinerama-dev i386 2:1.1.1-1ubuntu1 [10.0 kB] Get:284 http://ftpmaster.internal/ubuntu/ natty/main xorg-sgml-doctools all 1:1.6-1 [5400 B] Get:285 http://ftpmaster.internal/ubuntu/ natty/main libxi-dev i386 2:1.4.1-1ubuntu2 [212 kB] Get:286 http://ftpmaster.internal/ubuntu/ natty/main x11proto-randr-dev all 1.4.0+git20101207.0d32bb07-0ubuntu1 [32.0 kB] Get:287 http://ftpmaster.internal/ubuntu/ natty/main libxrandr-dev i386 2:1.3.1-1ubuntu1 [24.1 kB] Get:288 http://ftpmaster.internal/ubuntu/ natty/main x11proto-fixes-dev all 1:4.1.2-1 [11.3 kB] Get:289 http://ftpmaster.internal/ubuntu/ natty/main libxfixes-dev i386 1:4.0.5-1ubuntu1 [13.1 kB] Get:290 http://ftpmaster.internal/ubuntu/ natty/main libxcursor-dev i386 1:1.1.11-1ubuntu1 [28.9 kB] Get:291 http://ftpmaster.internal/ubuntu/ natty/main x11proto-composite-dev all 1:0.4.2-1 [8866 B] Get:292 http://ftpmaster.internal/ubuntu/ natty/main libxcomposite-dev i386 1:0.4.3-1ubuntu1 [10.8 kB] Get:293 http://ftpmaster.internal/ubuntu/ natty/main x11proto-damage-dev all 1:1.2.1-1 [6586 B] Get:294 http://ftpmaster.internal/ubuntu/ natty/main libxdamage-dev i386 1:1.1.3-1ubuntu1 [6804 B] Get:295 http://ftpmaster.internal/ubuntu/ natty/main libxml2-utils i386 2.7.8.dfsg-2 [77.8 kB] Get:296 http://ftpmaster.internal/ubuntu/ natty/main libgtk2.0-dev i386 2.24.4-0ubuntu1 [3394 kB] Get:297 http://ftpmaster.internal/ubuntu/ natty/main libmono-addins0.2-cil all 0.4-8 [267 kB] Get:298 http://ftpmaster.internal/ubuntu/ natty/main libmono-addins-cil-dev all 0.4-8 [5710 B] Get:299 http://ftpmaster.internal/ubuntu/ natty/main libmono-addins-gui0.2-cil all 0.4-8 [45.3 kB] Get:300 http://ftpmaster.internal/ubuntu/ natty/main libmono-addins-gui-cil-dev all 0.4-8 [5644 B] Get:301 http://ftpmaster.internal/ubuntu/ natty/main libndesk-dbus1.0-cil all 0.6.0-4 [36.2 kB] Get:302 http://ftpmaster.internal/ubuntu/ natty/main libndesk-dbus-glib1.0-cil all 0.4.1-3 [7424 B] Get:303 http://ftpmaster.internal/ubuntu/ natty/main libnotify0.4-cil all 0.4.0~r3032-2ubuntu1 [10.8 kB] Get:304 http://ftpmaster.internal/ubuntu/ natty/main libnotify-cil-dev all 0.4.0~r3032-2ubuntu1 [4272 B] Get:305 http://ftpmaster.internal/ubuntu/ natty/main librsvg2-2 i386 2.32.1-0ubuntu3 [96.8 kB] Get:306 http://ftpmaster.internal/ubuntu/ natty/universe librsvg2-2.18-cil all 2.26.0-3build1 [11.2 kB] Get:307 http://ftpmaster.internal/ubuntu/ natty/universe librsvg2-2.0-cil-dev all 2.26.0-3build1 [6530 B] Get:308 http://ftpmaster.internal/ubuntu/ natty/main libwnck-common all 1:2.30.6-0ubuntu3 [16.7 kB] Get:309 http://ftpmaster.internal/ubuntu/ natty/main libxres1 i386 2:1.0.5-1 [4740 B] Get:310 http://ftpmaster.internal/ubuntu/ natty/main libwnck22 i386 1:2.30.6-0ubuntu3 [91.6 kB] Get:311 http://ftpmaster.internal/ubuntu/ natty/universe libwnck2.20-cil i386 2.26.0-3build1 [30.1 kB] Get:312 http://ftpmaster.internal/ubuntu/ natty/universe libwnck1.0-cil-dev i386 2.26.0-3build1 [11.3 kB] debconf: delaying package configuration, since apt-utils is not installed Fetched 72.1 MB in 5s (13.9 MB/s) Selecting previously deselected package libexpat1. (Reading database ... 13746 files and directories currently installed.) Unpacking libexpat1 (from .../libexpat1_2.0.1-7ubuntu3_i386.deb) ... Selecting previously deselected package libsqlite3-0. Unpacking libsqlite3-0 (from .../libsqlite3-0_3.7.4-2ubuntu5_i386.deb) ... Selecting previously deselected package libfreetype6. Unpacking libfreetype6 (from .../libfreetype6_2.4.4-1ubuntu2_i386.deb) ... Selecting previously deselected package ucf. Unpacking ucf (from .../ucf_3.0025+nmu1ubuntu1_all.deb) ... Moving old data out of the way Selecting previously deselected package ttf-dejavu-core. Unpacking ttf-dejavu-core (from .../ttf-dejavu-core_2.31-1_all.deb) ... Selecting previously deselected package fontconfig-config. Unpacking fontconfig-config (from .../fontconfig-config_2.8.0-2.1ubuntu3_all.deb) ... Selecting previously deselected package libfontconfig1. Unpacking libfontconfig1 (from .../libfontconfig1_2.8.0-2.1ubuntu3_i386.deb) ... Selecting previously deselected package libxau6. Unpacking libxau6 (from .../libxau6_1%3a1.0.6-1ubuntu1_i386.deb) ... Selecting previously deselected package libxdmcp6. Unpacking libxdmcp6 (from .../libxdmcp6_1%3a1.1.0-1ubuntu1_i386.deb) ... Selecting previously deselected package libxcb1. Unpacking libxcb1 (from .../libxcb1_1.7-2ubuntu2_i386.deb) ... Selecting previously deselected package libx11-data. Unpacking libx11-data (from .../libx11-data_2%3a1.4.2-1ubuntu3_all.deb) ... Selecting previously deselected package libx11-6. Unpacking libx11-6 (from .../libx11-6_2%3a1.4.2-1ubuntu3_i386.deb) ... Selecting previously deselected package libxcb-render0. Unpacking libxcb-render0 (from .../libxcb-render0_1.7-2ubuntu2_i386.deb) ... Selecting previously deselected package libxcb-shm0. Unpacking libxcb-shm0 (from .../libxcb-shm0_1.7-2ubuntu2_i386.deb) ... Selecting previously deselected package libxext6. Unpacking libxext6 (from .../libxext6_2%3a1.2.0-2ubuntu1_i386.deb) ... Selecting previously deselected package libxrender1. Unpacking libxrender1 (from .../libxrender1_1%3a0.9.6-1ubuntu1_i386.deb) ... Selecting previously deselected package libatk1.0-data. Unpacking libatk1.0-data (from .../libatk1.0-data_2.0.0-0ubuntu1_all.deb) ... Selecting previously deselected package libatk1.0-0. Unpacking libatk1.0-0 (from .../libatk1.0-0_2.0.0-0ubuntu1_i386.deb) ... Selecting previously deselected package libavahi-common-data. Unpacking libavahi-common-data (from .../libavahi-common-data_0.6.30-0ubuntu2_i386.deb) ... Selecting previously deselected package libavahi-common3. Unpacking libavahi-common3 (from .../libavahi-common3_0.6.30-0ubuntu2_i386.deb) ... Selecting previously deselected package libavahi-client3. Unpacking libavahi-client3 (from .../libavahi-client3_0.6.30-0ubuntu2_i386.deb) ... Selecting previously deselected package libavahi-glib1. Unpacking libavahi-glib1 (from .../libavahi-glib1_0.6.30-0ubuntu2_i386.deb) ... Selecting previously deselected package x11-common. Unpacking x11-common (from .../x11-common_1%3a7.6+4ubuntu3_all.deb) ... Selecting previously deselected package libice6. Unpacking libice6 (from .../libice6_2%3a1.0.7-1ubuntu1_i386.deb) ... Selecting previously deselected package x11proto-core-dev. Unpacking x11proto-core-dev (from .../x11proto-core-dev_7.0.20-1_all.deb) ... Setting up x11-common (1:7.6+4ubuntu3) ... Selecting previously deselected package libice-dev. (Reading database ... 14350 files and directories currently installed.) Unpacking libice-dev (from .../libice-dev_2%3a1.0.7-1ubuntu1_i386.deb) ... Selecting previously deselected package libpixman-1-0. Unpacking libpixman-1-0 (from .../libpixman-1-0_0.20.2-0ubuntu1_i386.deb) ... Selecting previously deselected package libcairo2. Unpacking libcairo2 (from .../libcairo2_1.10.2-2ubuntu2_i386.deb) ... Selecting previously deselected package libdatrie1. Unpacking libdatrie1 (from .../libdatrie1_0.2.4-1_i386.deb) ... Selecting previously deselected package libthai-data. Unpacking libthai-data (from .../libthai-data_0.1.14-2ubuntu1_all.deb) ... Selecting previously deselected package libthai0. Unpacking libthai0 (from .../libthai0_0.1.14-2ubuntu1_i386.deb) ... Selecting previously deselected package libxft2. Unpacking libxft2 (from .../libxft2_2.2.0-2ubuntu2_i386.deb) ... Selecting previously deselected package fontconfig. Unpacking fontconfig (from .../fontconfig_2.8.0-2.1ubuntu3_i386.deb) ... Selecting previously deselected package libpango1.0-0. Unpacking libpango1.0-0 (from .../libpango1.0-0_1.28.4-0ubuntu1_i386.deb) ... Selecting previously deselected package libsm6. Unpacking libsm6 (from .../libsm6_2%3a1.2.0-1ubuntu1_i386.deb) ... Selecting previously deselected package libjpeg62. Unpacking libjpeg62 (from .../libjpeg62_6b1-1ubuntu1_i386.deb) ... Selecting previously deselected package libtiff4. Unpacking libtiff4 (from .../libtiff4_3.9.4-5ubuntu5_i386.deb) ... Selecting previously deselected package libxcomposite1. Unpacking libxcomposite1 (from .../libxcomposite1_1%3a0.4.3-1ubuntu1_i386.deb) ... Selecting previously deselected package libxfixes3. Unpacking libxfixes3 (from .../libxfixes3_1%3a4.0.5-1ubuntu1_i386.deb) ... Selecting previously deselected package libxcursor1. Unpacking libxcursor1 (from .../libxcursor1_1%3a1.1.11-1ubuntu1_i386.deb) ... Selecting previously deselected package libxdamage1. Unpacking libxdamage1 (from .../libxdamage1_1%3a1.1.3-1ubuntu1_i386.deb) ... Selecting previously deselected package libxi6. Unpacking libxi6 (from .../libxi6_2%3a1.4.1-1ubuntu2_i386.deb) ... Selecting previously deselected package libxinerama1. Unpacking libxinerama1 (from .../libxinerama1_2%3a1.1.1-1ubuntu1_i386.deb) ... Selecting previously deselected package libxrandr2. Unpacking libxrandr2 (from .../libxrandr2_2%3a1.3.1-1ubuntu1_i386.deb) ... Selecting previously deselected package xtrans-dev. Unpacking xtrans-dev (from .../xtrans-dev_1.2.6-1_all.deb) ... Selecting previously deselected package libmagic1. Unpacking libmagic1 (from .../libmagic1_5.04-5ubuntu2_i386.deb) ... Selecting previously deselected package file. Unpacking file (from .../file_5.04-5ubuntu2_i386.deb) ... Selecting previously deselected package libpopt0. Unpacking libpopt0 (from .../libpopt0_1.16-1_i386.deb) ... Selecting previously deselected package mime-support. Unpacking mime-support (from .../mime-support_3.51-1ubuntu1_all.deb) ... Selecting previously deselected package python2.7. Unpacking python2.7 (from .../python2.7_2.7.1-5ubuntu1_i386.deb) ... Selecting previously deselected package python. Unpacking python (from .../python_2.7.1-0ubuntu5_all.deb) ... Selecting previously deselected package bsdmainutils. Unpacking bsdmainutils (from .../bsdmainutils_8.2.2_i386.deb) ... Selecting previously deselected package gettext-base. Unpacking gettext-base (from .../gettext-base_0.18.1.1-3ubuntu1_i386.deb) ... Selecting previously deselected package groff-base. Unpacking groff-base (from .../groff-base_1.21-5_i386.deb) ... Selecting previously deselected package libdbus-glib-1-2. Unpacking libdbus-glib-1-2 (from .../libdbus-glib-1-2_0.92-0ubuntu1_i386.deb) ... Selecting previously deselected package liburi-perl. Unpacking liburi-perl (from .../liburi-perl_1.56-1_all.deb) ... Selecting previously deselected package libhtml-tagset-perl. Unpacking libhtml-tagset-perl (from .../libhtml-tagset-perl_3.20-2_all.deb) ... Selecting previously deselected package libhtml-parser-perl. Unpacking libhtml-parser-perl (from .../libhtml-parser-perl_3.68-1_i386.deb) ... Selecting previously deselected package libhtml-tree-perl. Unpacking libhtml-tree-perl (from .../libhtml-tree-perl_4.1-1_all.deb) ... Selecting previously deselected package libpipeline1. Unpacking libpipeline1 (from .../libpipeline1_1.2.0-1_i386.deb) ... Selecting previously deselected package libpython2.7. Unpacking libpython2.7 (from .../libpython2.7_2.7.1-5ubuntu1_i386.deb) ... Selecting previously deselected package libwww-perl. Unpacking libwww-perl (from .../libwww-perl_5.837-1_all.deb) ... Selecting previously deselected package libxml-parser-perl. Unpacking libxml-parser-perl (from .../libxml-parser-perl_2.36-1.1build3_i386.deb) ... Selecting previously deselected package libxml2. Unpacking libxml2 (from .../libxml2_2.7.8.dfsg-2_i386.deb) ... Selecting previously deselected package man-db. Unpacking man-db (from .../man-db_2.5.9-4_i386.deb) ... Selecting previously deselected package psmisc. Unpacking psmisc (from .../psmisc_22.13-1_i386.deb) ... Selecting previously deselected package m4. Unpacking m4 (from .../archives/m4_1.4.14-3_i386.deb) ... Selecting previously deselected package autoconf. Unpacking autoconf (from .../autoconf_2.67-2ubuntu1_all.deb) ... Selecting previously deselected package autotools-dev. Unpacking autotools-dev (from .../autotools-dev_20100122.1_all.deb) ... Selecting previously deselected package automake. Unpacking automake (from .../automake_1%3a1.11.1-1ubuntu1_all.deb) ... Selecting previously deselected package cli-common. Unpacking cli-common (from .../cli-common_0.7.1_all.deb) ... Selecting previously deselected package html2text. Unpacking html2text (from .../html2text_1.3.2a-15_i386.deb) ... Selecting previously deselected package libcroco3. Unpacking libcroco3 (from .../libcroco3_0.6.2-1_i386.deb) ... Selecting previously deselected package libunistring0. Unpacking libunistring0 (from .../libunistring0_0.9.3-3_i386.deb) ... Selecting previously deselected package gettext. Unpacking gettext (from .../gettext_0.18.1.1-3ubuntu1_i386.deb) ... Selecting previously deselected package intltool-debian. Unpacking intltool-debian (from .../intltool-debian_0.35.0+20060710.1_all.deb) ... Selecting previously deselected package po-debconf. Unpacking po-debconf (from .../po-debconf_1.0.16+nmu1_all.deb) ... Selecting previously deselected package debhelper. Unpacking debhelper (from .../debhelper_8.1.2ubuntu4_all.deb) ... Selecting previously deselected package libmono0. Unpacking libmono0 (from .../libmono0_2.6.7-5ubuntu2_i386.deb) ... Selecting previously deselected package libmono-posix2.0-cil. Unpacking libmono-posix2.0-cil (from .../libmono-posix2.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-system2.0-cil. Unpacking libmono-system2.0-cil (from .../libmono-system2.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-security2.0-cil. Unpacking libmono-security2.0-cil (from .../libmono-security2.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package mono-2.0-gac. Unpacking mono-2.0-gac (from .../mono-2.0-gac_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package mono-gac. Unpacking mono-gac (from .../mono-gac_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package mono-runtime. Unpacking mono-runtime (from .../mono-runtime_2.6.7-5ubuntu2_i386.deb) ... Selecting previously deselected package libmono-corlib2.0-cil. Unpacking libmono-corlib2.0-cil (from .../libmono-corlib2.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-corlib1.0-cil. Unpacking libmono-corlib1.0-cil (from .../libmono-corlib1.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package mono-utils. Unpacking mono-utils (from .../mono-utils_2.6.7-5ubuntu2_i386.deb) ... Selecting previously deselected package libmono-cecil-private-cil. Unpacking libmono-cecil-private-cil (from .../libmono-cecil-private-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-getoptions2.0-cil. Unpacking libmono-getoptions2.0-cil (from .../libmono-getoptions2.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-system1.0-cil. Unpacking libmono-system1.0-cil (from .../libmono-system1.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-relaxng1.0-cil. Unpacking libmono-relaxng1.0-cil (from .../libmono-relaxng1.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-relaxng2.0-cil. Unpacking libmono-relaxng2.0-cil (from .../libmono-relaxng2.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-security1.0-cil. Unpacking libmono-security1.0-cil (from .../libmono-security1.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-data-tds2.0-cil. Unpacking libmono-data-tds2.0-cil (from .../libmono-data-tds2.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-system-data2.0-cil. Unpacking libmono-system-data2.0-cil (from .../libmono-system-data2.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-messaging2.0-cil. Unpacking libmono-messaging2.0-cil (from .../libmono-messaging2.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-system-messaging2.0-cil. Unpacking libmono-system-messaging2.0-cil (from .../libmono-system-messaging2.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libsqlite0. Unpacking libsqlite0 (from .../libsqlite0_2.8.17-6build2_i386.deb) ... Selecting previously deselected package libmono-sqlite2.0-cil. Unpacking libmono-sqlite2.0-cil (from .../libmono-sqlite2.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-sharpzip2.84-cil. Unpacking libmono-sharpzip2.84-cil (from .../libmono-sharpzip2.84-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono2.0-cil. Unpacking libmono2.0-cil (from .../libmono2.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libexif12. Unpacking libexif12 (from .../libexif12_0.6.20-0ubuntu1_i386.deb) ... Selecting previously deselected package libgif4. Unpacking libgif4 (from .../libgif4_4.1.6-9_i386.deb) ... Selecting previously deselected package libgdiplus. Unpacking libgdiplus (from .../libgdiplus_2.6.7-3ubuntu1_i386.deb) ... Selecting previously deselected package libmono-system-web2.0-cil. Unpacking libmono-system-web2.0-cil (from .../libmono-system-web2.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-wcf3.0-cil. Unpacking libmono-wcf3.0-cil (from .../libmono-wcf3.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-system-data-linq2.0-cil. Unpacking libmono-system-data-linq2.0-cil (from .../libmono-system-data-linq2.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-data-tds1.0-cil. Unpacking libmono-data-tds1.0-cil (from .../libmono-data-tds1.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-system-data1.0-cil. Unpacking libmono-system-data1.0-cil (from .../libmono-system-data1.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-system-web1.0-cil. Unpacking libmono-system-web1.0-cil (from .../libmono-system-web1.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-system-runtime1.0-cil. Unpacking libmono-system-runtime1.0-cil (from .../libmono-system-runtime1.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-peapi2.0-cil. Unpacking libmono-peapi2.0-cil (from .../libmono-peapi2.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package mono-gmcs. Unpacking mono-gmcs (from .../mono-gmcs_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libglib2.0-data. Unpacking libglib2.0-data (from .../libglib2.0-data_2.28.5-0ubuntu1_all.deb) ... Selecting previously deselected package libglib2.0-bin. Unpacking libglib2.0-bin (from .../libglib2.0-bin_2.28.5-0ubuntu1_i386.deb) ... Selecting previously deselected package pkg-config. Unpacking pkg-config (from .../pkg-config_0.25-1.1ubuntu1_i386.deb) ... Selecting previously deselected package zlib1g-dev. Unpacking zlib1g-dev (from .../zlib1g-dev_1%3a1.2.3.4.dfsg-3ubuntu3_i386.deb) ... Selecting previously deselected package libglib2.0-dev. Unpacking libglib2.0-dev (from .../libglib2.0-dev_2.28.5-0ubuntu1_i386.deb) ... Selecting previously deselected package libmono-dev. Unpacking libmono-dev (from .../libmono-dev_2.6.7-5ubuntu2_i386.deb) ... Selecting previously deselected package mono-2.0-devel. Unpacking mono-2.0-devel (from .../mono-2.0-devel_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-sharpzip0.84-cil. Unpacking libmono-sharpzip0.84-cil (from .../libmono-sharpzip0.84-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono1.0-cil. Unpacking libmono1.0-cil (from .../libmono1.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-posix1.0-cil. Unpacking libmono-posix1.0-cil (from .../libmono-posix1.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-getoptions1.0-cil. Unpacking libmono-getoptions1.0-cil (from .../libmono-getoptions1.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-data1.0-cil. Unpacking libmono-data1.0-cil (from .../libmono-data1.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-data2.0-cil. Unpacking libmono-data2.0-cil (from .../libmono-data2.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-c5-1.1-cil. Unpacking libmono-c5-1.1-cil (from .../libmono-c5-1.1-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-webbrowser0.5-cil. Unpacking libmono-webbrowser0.5-cil (from .../libmono-webbrowser0.5-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-management2.0-cil. Unpacking libmono-management2.0-cil (from .../libmono-management2.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-rabbitmq2.0-cil. Unpacking libmono-rabbitmq2.0-cil (from .../libmono-rabbitmq2.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-messaging-rabbitmq2.0-cil. Unpacking libmono-messaging-rabbitmq2.0-cil (from .../libmono-messaging-rabbitmq2.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-simd2.0-cil. Unpacking libmono-simd2.0-cil (from .../libmono-simd2.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-i18n-west1.0-cil. Unpacking libmono-i18n-west1.0-cil (from .../libmono-i18n-west1.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-i18n1.0-cil. Unpacking libmono-i18n1.0-cil (from .../libmono-i18n1.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-i18n-west2.0-cil. Unpacking libmono-i18n-west2.0-cil (from .../libmono-i18n-west2.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-i18n2.0-cil. Unpacking libmono-i18n2.0-cil (from .../libmono-i18n2.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-system-messaging1.0-cil. Unpacking libmono-system-messaging1.0-cil (from .../libmono-system-messaging1.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-system-web-mvc1.0-cil. Unpacking libmono-system-web-mvc1.0-cil (from .../libmono-system-web-mvc1.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-system-web-mvc2.0-cil. Unpacking libmono-system-web-mvc2.0-cil (from .../libmono-system-web-mvc2.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-system-runtime2.0-cil. Unpacking libmono-system-runtime2.0-cil (from .../libmono-system-runtime2.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-ldap1.0-cil. Unpacking libmono-ldap1.0-cil (from .../libmono-ldap1.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-system-ldap1.0-cil. Unpacking libmono-system-ldap1.0-cil (from .../libmono-system-ldap1.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-ldap2.0-cil. Unpacking libmono-ldap2.0-cil (from .../libmono-ldap2.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-system-ldap2.0-cil. Unpacking libmono-system-ldap2.0-cil (from .../libmono-system-ldap2.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-accessibility1.0-cil. Unpacking libmono-accessibility1.0-cil (from .../libmono-accessibility1.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-winforms1.0-cil. Unpacking libmono-winforms1.0-cil (from .../libmono-winforms1.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-accessibility2.0-cil. Unpacking libmono-accessibility2.0-cil (from .../libmono-accessibility2.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-winforms2.0-cil. Unpacking libmono-winforms2.0-cil (from .../libmono-winforms2.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-cairo1.0-cil. Unpacking libmono-cairo1.0-cil (from .../libmono-cairo1.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-cairo2.0-cil. Unpacking libmono-cairo2.0-cil (from .../libmono-cairo2.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-sharpzip0.6-cil. Unpacking libmono-sharpzip0.6-cil (from .../libmono-sharpzip0.6-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-sharpzip2.6-cil. Unpacking libmono-sharpzip2.6-cil (from .../libmono-sharpzip2.6-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-npgsql1.0-cil. Unpacking libmono-npgsql1.0-cil (from .../libmono-npgsql1.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-npgsql2.0-cil. Unpacking libmono-npgsql2.0-cil (from .../libmono-npgsql2.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-bytefx0.7.6.1-cil. Unpacking libmono-bytefx0.7.6.1-cil (from .../libmono-bytefx0.7.6.1-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-bytefx0.7.6.2-cil. Unpacking libmono-bytefx0.7.6.2-cil (from .../libmono-bytefx0.7.6.2-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-db2-1.0-cil. Unpacking libmono-db2-1.0-cil (from .../libmono-db2-1.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-oracle1.0-cil. Unpacking libmono-oracle1.0-cil (from .../libmono-oracle1.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-oracle2.0-cil. Unpacking libmono-oracle2.0-cil (from .../libmono-oracle2.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-sqlite1.0-cil. Unpacking libmono-sqlite1.0-cil (from .../libmono-sqlite1.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-cscompmgd7.0-cil. Unpacking libmono-cscompmgd7.0-cil (from .../libmono-cscompmgd7.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-cscompmgd8.0-cil. Unpacking libmono-cscompmgd8.0-cil (from .../libmono-cscompmgd8.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-microsoft-build2.0-cil. Unpacking libmono-microsoft-build2.0-cil (from .../libmono-microsoft-build2.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-microsoft7.0-cil. Unpacking libmono-microsoft7.0-cil (from .../libmono-microsoft7.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-microsoft8.0-cil. Unpacking libmono-microsoft8.0-cil (from .../libmono-microsoft8.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-peapi1.0-cil. Unpacking libmono-peapi1.0-cil (from .../libmono-peapi1.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-debugger-soft0.0-cil. Unpacking libmono-debugger-soft0.0-cil (from .../libmono-debugger-soft0.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-tasklets2.0-cil. Unpacking libmono-tasklets2.0-cil (from .../libmono-tasklets2.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libmono-windowsbase3.0-cil. Unpacking libmono-windowsbase3.0-cil (from .../libmono-windowsbase3.0-cil_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libnunit2.4-cil. Unpacking libnunit2.4-cil (from .../libnunit2.4-cil_2.4.7+dfsg-6_all.deb) ... Selecting previously deselected package libnunit-cil-dev. Unpacking libnunit-cil-dev (from .../libnunit-cil-dev_2.4.7+dfsg-6_all.deb) ... Selecting previously deselected package libmono-cil-dev. Unpacking libmono-cil-dev (from .../libmono-cil-dev_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package mono-devel. Unpacking mono-devel (from .../mono-devel_2.6.7-5ubuntu2_all.deb) ... Selecting previously deselected package libxml-perl. Unpacking libxml-perl (from .../libxml-perl_0.08-2_all.deb) ... Selecting previously deselected package libxml-regexp-perl. Unpacking libxml-regexp-perl (from .../libxml-regexp-perl_0.03-8_all.deb) ... Selecting previously deselected package libxml-dom-perl. Unpacking libxml-dom-perl (from .../libxml-dom-perl_1.44-1_all.deb) ... Selecting previously deselected package cli-common-dev. Unpacking cli-common-dev (from .../cli-common-dev_0.7.1_all.deb) ... Selecting previously deselected package dbus. Unpacking dbus (from .../dbus_1.4.6-1ubuntu6_i386.deb) ... Selecting previously deselected package dbus-x11. Unpacking dbus-x11 (from .../dbus-x11_1.4.6-1ubuntu6_i386.deb) ... Selecting previously deselected package libgamin0. Unpacking libgamin0 (from .../libgamin0_0.1.10-2ubuntu1_i386.deb) ... Selecting previously deselected package gamin. Unpacking gamin (from .../gamin_0.1.10-2ubuntu1_i386.deb) ... Selecting previously deselected package libidl0. Unpacking libidl0 (from .../libidl0_0.8.14-0.1ubuntu1_i386.deb) ... Selecting previously deselected package liborbit2. Unpacking liborbit2 (from .../liborbit2_1%3a2.14.19-0ubuntu2_i386.deb) ... Selecting previously deselected package gconf2-common. Unpacking gconf2-common (from .../gconf2-common_2.32.2-0ubuntu1_all.deb) ... Selecting previously deselected package libgconf2-4. Unpacking libgconf2-4 (from .../libgconf2-4_2.32.2-0ubuntu1_i386.deb) ... Selecting previously deselected package gconf2. Unpacking gconf2 (from .../gconf2_2.32.2-0ubuntu1_i386.deb) ... Selecting previously deselected package gnome-mime-data. Unpacking gnome-mime-data (from .../gnome-mime-data_2.18.0-1_all.deb) ... Selecting previously deselected package libxml-namespacesupport-perl. Unpacking libxml-namespacesupport-perl (from .../libxml-namespacesupport-perl_1.09-3_all.deb) ... Selecting previously deselected package libxml-sax-perl. Unpacking libxml-sax-perl (from .../libxml-sax-perl_0.96+dfsg-2_all.deb) ... Selecting previously deselected package libxml-libxml-perl. Unpacking libxml-libxml-perl (from .../libxml-libxml-perl_1.70.ds-1_i386.deb) ... Selecting previously deselected package libglib2.0-cil. Unpacking libglib2.0-cil (from .../libglib2.0-cil_2.12.10-1ubuntu1_i386.deb) ... Selecting previously deselected package gtk-sharp2-gapi. Unpacking gtk-sharp2-gapi (from .../gtk-sharp2-gapi_2.12.10-1ubuntu1_i386.deb) ... Selecting previously deselected package intltool. Unpacking intltool (from .../intltool_0.41.1-1_all.deb) ... Selecting previously deselected package libart-2.0-2. Unpacking libart-2.0-2 (from .../libart-2.0-2_2.3.21-1_i386.deb) ... Selecting previously deselected package libart2.0-cil. Unpacking libart2.0-cil (from .../libart2.0-cil_2.24.2-0ubuntu1_all.deb) ... Selecting previously deselected package libart2.0-cil-dev. Unpacking libart2.0-cil-dev (from .../libart2.0-cil-dev_2.24.2-0ubuntu1_all.deb) ... Selecting previously deselected package libasound2. Unpacking libasound2 (from .../libasound2_1.0.24.1-0ubuntu3_i386.deb) ... Selecting previously deselected package libatk1.0-dev. Unpacking libatk1.0-dev (from .../libatk1.0-dev_2.0.0-0ubuntu1_i386.deb) ... Selecting previously deselected package libbonobo2-common. Unpacking libbonobo2-common (from .../libbonobo2-common_2.32.1-0ubuntu1_all.deb) ... Selecting previously deselected package libbonobo2-0. Unpacking libbonobo2-0 (from .../libbonobo2-0_2.32.1-0ubuntu1_i386.deb) ... Selecting previously deselected package libjasper1. Unpacking libjasper1 (from .../libjasper1_1.900.1-7ubuntu2_i386.deb) ... Selecting previously deselected package libgdk-pixbuf2.0-0. Unpacking libgdk-pixbuf2.0-0 (from .../libgdk-pixbuf2.0-0_2.23.3-0ubuntu1_i386.deb) ... Selecting previously deselected package libgtk2.0-common. Unpacking libgtk2.0-common (from .../libgtk2.0-common_2.24.4-0ubuntu1_all.deb) ... Selecting previously deselected package libcups2. Unpacking libcups2 (from .../libcups2_1.4.6-4_i386.deb) ... Selecting previously deselected package shared-mime-info. Unpacking shared-mime-info (from .../shared-mime-info_0.90-1ubuntu1_i386.deb) ... Selecting previously deselected package libgtk2.0-0. Unpacking libgtk2.0-0 (from .../libgtk2.0-0_2.24.4-0ubuntu1_i386.deb) ... Selecting previously deselected package libglade2-0. Unpacking libglade2-0 (from .../libglade2-0_1%3a2.6.4-1build1_i386.deb) ... Selecting previously deselected package libltdl7. Unpacking libltdl7 (from .../libltdl7_2.2.6b-2ubuntu3_i386.deb) ... Selecting previously deselected package libtdb1. Unpacking libtdb1 (from .../libtdb1_1.2.9-1fakesync1_i386.deb) ... Selecting previously deselected package libogg0. Unpacking libogg0 (from .../libogg0_1.2.0~dfsg-1_i386.deb) ... Selecting previously deselected package libvorbis0a. Unpacking libvorbis0a (from .../libvorbis0a_1.3.2-1ubuntu1_i386.deb) ... Selecting previously deselected package libvorbisfile3. Unpacking libvorbisfile3 (from .../libvorbisfile3_1.3.2-1ubuntu1_i386.deb) ... Selecting previously deselected package libcanberra0. Unpacking libcanberra0 (from .../libcanberra0_0.28-0ubuntu3_i386.deb) ... Selecting previously deselected package libgnomevfs2-common. Unpacking libgnomevfs2-common (from .../libgnomevfs2-common_1%3a2.24.4-0ubuntu4_all.deb) ... Selecting previously deselected package libgnomevfs2-0. Unpacking libgnomevfs2-0 (from .../libgnomevfs2-0_1%3a2.24.4-0ubuntu4_i386.deb) ... Selecting previously deselected package libgnome2-common. Unpacking libgnome2-common (from .../libgnome2-common_2.32.1-0ubuntu3_all.deb) ... Selecting previously deselected package libgnome2-0. Unpacking libgnome2-0 (from .../libgnome2-0_2.32.1-0ubuntu3_i386.deb) ... Selecting previously deselected package libgail18. Unpacking libgail18 (from .../libgail18_2.24.4-0ubuntu1_i386.deb) ... Selecting previously deselected package libgnomecanvas2-common. Unpacking libgnomecanvas2-common (from .../libgnomecanvas2-common_2.30.3-0ubuntu1_all.deb) ... Selecting previously deselected package libgnomecanvas2-0. Unpacking libgnomecanvas2-0 (from .../libgnomecanvas2-0_2.30.3-0ubuntu1_i386.deb) ... Selecting previously deselected package libbonoboui2-common. Unpacking libbonoboui2-common (from .../libbonoboui2-common_2.24.5-0ubuntu1_all.deb) ... Selecting previously deselected package libbonoboui2-0. Unpacking libbonoboui2-0 (from .../libbonoboui2-0_2.24.5-0ubuntu1_i386.deb) ... Selecting previously deselected package libcairo-gobject2. Unpacking libcairo-gobject2 (from .../libcairo-gobject2_1.10.2-2ubuntu2_i386.deb) ... Selecting previously deselected package libcairo-script-interpreter2. Unpacking libcairo-script-interpreter2 (from .../libcairo-script-interpreter2_1.10.2-2ubuntu2_i386.deb) ... Selecting previously deselected package libexpat1-dev. Unpacking libexpat1-dev (from .../libexpat1-dev_2.0.1-7ubuntu3_i386.deb) ... Selecting previously deselected package libfreetype6-dev. Unpacking libfreetype6-dev (from .../libfreetype6-dev_2.4.4-1ubuntu2_i386.deb) ... Selecting previously deselected package libfontconfig1-dev. Unpacking libfontconfig1-dev (from .../libfontconfig1-dev_2.8.0-2.1ubuntu3_i386.deb) ... Selecting previously deselected package libxau-dev. Unpacking libxau-dev (from .../libxau-dev_1%3a1.0.6-1ubuntu1_i386.deb) ... Selecting previously deselected package libxdmcp-dev. Unpacking libxdmcp-dev (from .../libxdmcp-dev_1%3a1.1.0-1ubuntu1_i386.deb) ... Selecting previously deselected package x11proto-input-dev. Unpacking x11proto-input-dev (from .../x11proto-input-dev_2.0.1-1ubuntu1_all.deb) ... Selecting previously deselected package x11proto-kb-dev. Unpacking x11proto-kb-dev (from .../x11proto-kb-dev_1.0.5-1_all.deb) ... Selecting previously deselected package libpthread-stubs0. Unpacking libpthread-stubs0 (from .../libpthread-stubs0_0.3-2_i386.deb) ... Selecting previously deselected package libpthread-stubs0-dev. Unpacking libpthread-stubs0-dev (from .../libpthread-stubs0-dev_0.3-2_i386.deb) ... Selecting previously deselected package libxcb1-dev. Unpacking libxcb1-dev (from .../libxcb1-dev_1.7-2ubuntu2_i386.deb) ... Selecting previously deselected package libx11-dev. Unpacking libx11-dev (from .../libx11-dev_2%3a1.4.2-1ubuntu3_i386.deb) ... Selecting previously deselected package x11proto-render-dev. Unpacking x11proto-render-dev (from .../x11proto-render-dev_2%3a0.11.1-1_all.deb) ... Selecting previously deselected package libxrender-dev. Unpacking libxrender-dev (from .../libxrender-dev_1%3a0.9.6-1ubuntu1_i386.deb) ... Selecting previously deselected package libpng12-dev. Unpacking libpng12-dev (from .../libpng12-dev_1.2.44-1ubuntu3_i386.deb) ... Selecting previously deselected package libsm-dev. Unpacking libsm-dev (from .../libsm-dev_2%3a1.2.0-1ubuntu1_i386.deb) ... Selecting previously deselected package libpixman-1-dev. Unpacking libpixman-1-dev (from .../libpixman-1-dev_0.20.2-0ubuntu1_i386.deb) ... Selecting previously deselected package libxcb-render0-dev. Unpacking libxcb-render0-dev (from .../libxcb-render0-dev_1.7-2ubuntu2_i386.deb) ... Selecting previously deselected package libxcb-shm0-dev. Unpacking libxcb-shm0-dev (from .../libxcb-shm0-dev_1.7-2ubuntu2_i386.deb) ... Selecting previously deselected package libcairo2-dev. Unpacking libcairo2-dev (from .../libcairo2-dev_1.10.2-2ubuntu2_i386.deb) ... Selecting previously deselected package libdbus-1-dev. Unpacking libdbus-1-dev (from .../libdbus-1-dev_1.4.6-1ubuntu6_i386.deb) ... Selecting previously deselected package libdbus1.0-cil. Unpacking libdbus1.0-cil (from .../libdbus1.0-cil_0.7.0-2_all.deb) ... Selecting previously deselected package libdbus-glib1.0-cil. Unpacking libdbus-glib1.0-cil (from .../libdbus-glib1.0-cil_0.5.0-2_all.deb) ... Selecting previously deselected package libdbus1.0-cil-dev. Unpacking libdbus1.0-cil-dev (from .../libdbus1.0-cil-dev_0.7.0-2_all.deb) ... Selecting previously deselected package libdbus-glib1.0-cil-dev. Unpacking libdbus-glib1.0-cil-dev (from .../libdbus-glib1.0-cil-dev_0.5.0-2_all.deb) ... Selecting previously deselected package libidl-dev. Unpacking libidl-dev (from .../libidl-dev_0.8.14-0.1ubuntu1_i386.deb) ... Selecting previously deselected package liborbit2-dev. Unpacking liborbit2-dev (from .../liborbit2-dev_1%3a2.14.19-0ubuntu2_i386.deb) ... Selecting previously deselected package libgconf2-dev. Unpacking libgconf2-dev (from .../libgconf2-dev_2.32.2-0ubuntu1_i386.deb) ... Selecting previously deselected package libgconf2.0-cil. Unpacking libgconf2.0-cil (from .../libgconf2.0-cil_2.24.2-0ubuntu1_all.deb) ... Selecting previously deselected package libgconf2.0-cil-dev. Unpacking libgconf2.0-cil-dev (from .../libgconf2.0-cil-dev_2.24.2-0ubuntu1_all.deb) ... Selecting previously deselected package libgdk-pixbuf2.0-dev. Unpacking libgdk-pixbuf2.0-dev (from .../libgdk-pixbuf2.0-dev_2.23.3-0ubuntu1_i386.deb) ... Selecting previously deselected package libgio-cil. Unpacking libgio-cil (from .../libgio-cil_2.22.2-2_all.deb) ... Selecting previously deselected package libgio2.0-cil-dev. Unpacking libgio2.0-cil-dev (from .../libgio2.0-cil-dev_2.22.2-2_all.deb) ... Selecting previously deselected package libgtk2.0-cil. Unpacking libgtk2.0-cil (from .../libgtk2.0-cil_2.12.10-1ubuntu1_i386.deb) ... Selecting previously deselected package libglade2.0-cil. Unpacking libglade2.0-cil (from .../libglade2.0-cil_2.12.10-1ubuntu1_i386.deb) ... Selecting previously deselected package libglib2.0-cil-dev. Unpacking libglib2.0-cil-dev (from .../libglib2.0-cil-dev_2.12.10-1ubuntu1_i386.deb) ... Selecting previously deselected package libxcb-atom1. Unpacking libxcb-atom1 (from .../libxcb-atom1_0.3.6-1build1_i386.deb) ... Selecting previously deselected package libxcb-aux0. Unpacking libxcb-aux0 (from .../libxcb-aux0_0.3.6-1build1_i386.deb) ... Selecting previously deselected package libxcb-event1. Unpacking libxcb-event1 (from .../libxcb-event1_0.3.6-1build1_i386.deb) ... Selecting previously deselected package libstartup-notification0. Unpacking libstartup-notification0 (from .../libstartup-notification0_0.10-1build1_i386.deb) ... Selecting previously deselected package libgnome-desktop-2-17. Unpacking libgnome-desktop-2-17 (from .../libgnome-desktop-2-17_1%3a2.32.1-0ubuntu5_i386.deb) ... Selecting previously deselected package libgnome-keyring0. Unpacking libgnome-keyring0 (from .../libgnome-keyring0_2.32.0-1ubuntu2_i386.deb) ... Selecting previously deselected package libgnome-keyring1.0-cil. Unpacking libgnome-keyring1.0-cil (from .../libgnome-keyring1.0-cil_1.0.0-3_i386.deb) ... Selecting previously deselected package libgnome-keyring1.0-cil-dev. Unpacking libgnome-keyring1.0-cil-dev (from .../libgnome-keyring1.0-cil-dev_1.0.0-3_i386.deb) ... Selecting previously deselected package libgnome-vfs2.0-cil. Unpacking libgnome-vfs2.0-cil (from .../libgnome-vfs2.0-cil_2.24.2-0ubuntu1_all.deb) ... Selecting previously deselected package libgnome-vfs2.0-cil-dev. Unpacking libgnome-vfs2.0-cil-dev (from .../libgnome-vfs2.0-cil-dev_2.24.2-0ubuntu1_all.deb) ... Selecting previously deselected package libgnomeui-common. Unpacking libgnomeui-common (from .../libgnomeui-common_2.24.5-0ubuntu1_all.deb) ... Selecting previously deselected package libgnomeui-0. Unpacking libgnomeui-0 (from .../libgnomeui-0_2.24.5-0ubuntu1_i386.deb) ... Selecting previously deselected package libgnome2.24-cil. Unpacking libgnome2.24-cil (from .../libgnome2.24-cil_2.24.2-0ubuntu1_i386.deb) ... Selecting previously deselected package libgtk2.0-cil-dev. Unpacking libgtk2.0-cil-dev (from .../libgtk2.0-cil-dev_2.12.10-1ubuntu1_i386.deb) ... Selecting previously deselected package libgnome2.0-cil-dev. Unpacking libgnome2.0-cil-dev (from .../libgnome2.0-cil-dev_2.24.2-0ubuntu1_i386.deb) ... Selecting previously deselected package libgnomedesktop2.20-cil. Unpacking libgnomedesktop2.20-cil (from .../libgnomedesktop2.20-cil_2.26.0-3build1_all.deb) ... Selecting previously deselected package libgnomedesktop2.0-cil-dev. Unpacking libgnomedesktop2.0-cil-dev (from .../libgnomedesktop2.0-cil-dev_2.26.0-3build1_all.deb) ... Selecting previously deselected package libxft-dev. Unpacking libxft-dev (from .../libxft-dev_2.2.0-2ubuntu2_i386.deb) ... Selecting previously deselected package libpango1.0-dev. Unpacking libpango1.0-dev (from .../libpango1.0-dev_1.28.4-0ubuntu1_i386.deb) ... Selecting previously deselected package x11proto-xext-dev. Unpacking x11proto-xext-dev (from .../x11proto-xext-dev_7.1.99.0~git20110111.9df8b776-0ubuntu2_all.deb) ... Selecting previously deselected package libxext-dev. Unpacking libxext-dev (from .../libxext-dev_2%3a1.2.0-2ubuntu1_i386.deb) ... Selecting previously deselected package x11proto-xinerama-dev. Unpacking x11proto-xinerama-dev (from .../x11proto-xinerama-dev_1.2.1-1_all.deb) ... Selecting previously deselected package libxinerama-dev. Unpacking libxinerama-dev (from .../libxinerama-dev_2%3a1.1.1-1ubuntu1_i386.deb) ... Selecting previously deselected package xorg-sgml-doctools. Unpacking xorg-sgml-doctools (from .../xorg-sgml-doctools_1%3a1.6-1_all.deb) ... Selecting previously deselected package libxi-dev. Unpacking libxi-dev (from .../libxi-dev_2%3a1.4.1-1ubuntu2_i386.deb) ... Selecting previously deselected package x11proto-randr-dev. Unpacking x11proto-randr-dev (from .../x11proto-randr-dev_1.4.0+git20101207.0d32bb07-0ubuntu1_all.deb) ... Selecting previously deselected package libxrandr-dev. Unpacking libxrandr-dev (from .../libxrandr-dev_2%3a1.3.1-1ubuntu1_i386.deb) ... Selecting previously deselected package x11proto-fixes-dev. Unpacking x11proto-fixes-dev (from .../x11proto-fixes-dev_1%3a4.1.2-1_all.deb) ... Selecting previously deselected package libxfixes-dev. Unpacking libxfixes-dev (from .../libxfixes-dev_1%3a4.0.5-1ubuntu1_i386.deb) ... Selecting previously deselected package libxcursor-dev. Unpacking libxcursor-dev (from .../libxcursor-dev_1%3a1.1.11-1ubuntu1_i386.deb) ... Selecting previously deselected package x11proto-composite-dev. Unpacking x11proto-composite-dev (from .../x11proto-composite-dev_1%3a0.4.2-1_all.deb) ... Selecting previously deselected package libxcomposite-dev. Unpacking libxcomposite-dev (from .../libxcomposite-dev_1%3a0.4.3-1ubuntu1_i386.deb) ... Selecting previously deselected package x11proto-damage-dev. Unpacking x11proto-damage-dev (from .../x11proto-damage-dev_1%3a1.2.1-1_all.deb) ... Selecting previously deselected package libxdamage-dev. Unpacking libxdamage-dev (from .../libxdamage-dev_1%3a1.1.3-1ubuntu1_i386.deb) ... Selecting previously deselected package libxml2-utils. Unpacking libxml2-utils (from .../libxml2-utils_2.7.8.dfsg-2_i386.deb) ... Selecting previously deselected package libgtk2.0-dev. Unpacking libgtk2.0-dev (from .../libgtk2.0-dev_2.24.4-0ubuntu1_i386.deb) ... Selecting previously deselected package libmono-addins0.2-cil. Unpacking libmono-addins0.2-cil (from .../libmono-addins0.2-cil_0.4-8_all.deb) ... Selecting previously deselected package libmono-addins-cil-dev. Unpacking libmono-addins-cil-dev (from .../libmono-addins-cil-dev_0.4-8_all.deb) ... Selecting previously deselected package libmono-addins-gui0.2-cil. Unpacking libmono-addins-gui0.2-cil (from .../libmono-addins-gui0.2-cil_0.4-8_all.deb) ... Selecting previously deselected package libmono-addins-gui-cil-dev. Unpacking libmono-addins-gui-cil-dev (from .../libmono-addins-gui-cil-dev_0.4-8_all.deb) ... Selecting previously deselected package libndesk-dbus1.0-cil. Unpacking libndesk-dbus1.0-cil (from .../libndesk-dbus1.0-cil_0.6.0-4_all.deb) ... Selecting previously deselected package libndesk-dbus-glib1.0-cil. Unpacking libndesk-dbus-glib1.0-cil (from .../libndesk-dbus-glib1.0-cil_0.4.1-3_all.deb) ... Selecting previously deselected package libnotify0.4-cil. Unpacking libnotify0.4-cil (from .../libnotify0.4-cil_0.4.0~r3032-2ubuntu1_all.deb) ... Selecting previously deselected package libnotify-cil-dev. Unpacking libnotify-cil-dev (from .../libnotify-cil-dev_0.4.0~r3032-2ubuntu1_all.deb) ... Selecting previously deselected package librsvg2-2. Unpacking librsvg2-2 (from .../librsvg2-2_2.32.1-0ubuntu3_i386.deb) ... Selecting previously deselected package librsvg2-2.18-cil. Unpacking librsvg2-2.18-cil (from .../librsvg2-2.18-cil_2.26.0-3build1_all.deb) ... Selecting previously deselected package librsvg2-2.0-cil-dev. Unpacking librsvg2-2.0-cil-dev (from .../librsvg2-2.0-cil-dev_2.26.0-3build1_all.deb) ... Selecting previously deselected package libwnck-common. Unpacking libwnck-common (from .../libwnck-common_1%3a2.30.6-0ubuntu3_all.deb) ... Selecting previously deselected package libxres1. Unpacking libxres1 (from .../libxres1_2%3a1.0.5-1_i386.deb) ... Selecting previously deselected package libwnck22. Unpacking libwnck22 (from .../libwnck22_1%3a2.30.6-0ubuntu3_i386.deb) ... Selecting previously deselected package libwnck2.20-cil. Unpacking libwnck2.20-cil (from .../libwnck2.20-cil_2.26.0-3build1_i386.deb) ... Selecting previously deselected package libwnck1.0-cil-dev. Unpacking libwnck1.0-cil-dev (from .../libwnck1.0-cil-dev_2.26.0-3build1_i386.deb) ... Processing triggers for libglib2.0-0 ... No schema files found: doing nothing. Setting up libexpat1 (2.0.1-7ubuntu3) ... Setting up libsqlite3-0 (3.7.4-2ubuntu5) ... Setting up libfreetype6 (2.4.4-1ubuntu2) ... Setting up ucf (3.0025+nmu1ubuntu1) ... Setting up ttf-dejavu-core (2.31-1) ... Setting up fontconfig-config (2.8.0-2.1ubuntu3) ... Setting up libfontconfig1 (2.8.0-2.1ubuntu3) ... Setting up libxau6 (1:1.0.6-1ubuntu1) ... Setting up libxdmcp6 (1:1.1.0-1ubuntu1) ... Setting up libxcb1 (1.7-2ubuntu2) ... Setting up libx11-data (2:1.4.2-1ubuntu3) ... Setting up libx11-6 (2:1.4.2-1ubuntu3) ... Setting up libxcb-render0 (1.7-2ubuntu2) ... Setting up libxcb-shm0 (1.7-2ubuntu2) ... Setting up libxext6 (2:1.2.0-2ubuntu1) ... Setting up libxrender1 (1:0.9.6-1ubuntu1) ... Setting up libatk1.0-data (2.0.0-0ubuntu1) ... Setting up libatk1.0-0 (2.0.0-0ubuntu1) ... Setting up libavahi-common-data (0.6.30-0ubuntu2) ... Setting up libavahi-common3 (0.6.30-0ubuntu2) ... Setting up libavahi-client3 (0.6.30-0ubuntu2) ... Setting up libavahi-glib1 (0.6.30-0ubuntu2) ... Setting up libice6 (2:1.0.7-1ubuntu1) ... Setting up x11proto-core-dev (7.0.20-1) ... Setting up libice-dev (2:1.0.7-1ubuntu1) ... Setting up libpixman-1-0 (0.20.2-0ubuntu1) ... Setting up libcairo2 (1.10.2-2ubuntu2) ... Setting up libdatrie1 (0.2.4-1) ... Setting up libthai-data (0.1.14-2ubuntu1) ... Setting up libthai0 (0.1.14-2ubuntu1) ... Setting up libxft2 (2.2.0-2ubuntu2) ... Setting up fontconfig (2.8.0-2.1ubuntu3) ... Cleaning up old fontconfig caches... done. Regenerating fonts cache... done. Setting up libpango1.0-0 (1.28.4-0ubuntu1) ... Setting up libsm6 (2:1.2.0-1ubuntu1) ... Setting up libjpeg62 (6b1-1ubuntu1) ... Setting up libtiff4 (3.9.4-5ubuntu5) ... Setting up libxcomposite1 (1:0.4.3-1ubuntu1) ... Setting up libxfixes3 (1:4.0.5-1ubuntu1) ... Setting up libxcursor1 (1:1.1.11-1ubuntu1) ... Setting up libxdamage1 (1:1.1.3-1ubuntu1) ... Setting up libxi6 (2:1.4.1-1ubuntu2) ... Setting up libxinerama1 (2:1.1.1-1ubuntu1) ... Setting up libxrandr2 (2:1.3.1-1ubuntu1) ... Setting up xtrans-dev (1.2.6-1) ... Setting up libmagic1 (5.04-5ubuntu2) ... Setting up file (5.04-5ubuntu2) ... Setting up libpopt0 (1.16-1) ... Setting up mime-support (3.51-1ubuntu1) ... update-alternatives: using /usr/bin/see to provide /usr/bin/view (view) in auto mode. Setting up python2.7 (2.7.1-5ubuntu1) ... Setting up python (2.7.1-0ubuntu5) ... Setting up bsdmainutils (8.2.2) ... update-alternatives: using /usr/bin/bsd-write to provide /usr/bin/write (write) in auto mode. update-alternatives: using /usr/bin/bsd-from to provide /usr/bin/from (from) in auto mode. Setting up gettext-base (0.18.1.1-3ubuntu1) ... Setting up groff-base (1.21-5) ... Setting up libdbus-glib-1-2 (0.92-0ubuntu1) ... Setting up liburi-perl (1.56-1) ... Setting up libhtml-tagset-perl (3.20-2) ... Setting up libhtml-parser-perl (3.68-1) ... Setting up libhtml-tree-perl (4.1-1) ... Setting up libpipeline1 (1.2.0-1) ... Setting up libpython2.7 (2.7.1-5ubuntu1) ... Setting up libwww-perl (5.837-1) ... Setting up libxml-parser-perl (2.36-1.1build3) ... Setting up libxml2 (2.7.8.dfsg-2) ... Setting up man-db (2.5.9-4) ... Building database of manual pages ... Setting up psmisc (22.13-1) ... Setting up m4 (1.4.14-3) ... Setting up autoconf (2.67-2ubuntu1) ... Setting up autotools-dev (20100122.1) ... Setting up automake (1:1.11.1-1ubuntu1) ... update-alternatives: using /usr/bin/automake-1.11 to provide /usr/bin/automake (automake) in auto mode. Setting up cli-common (0.7.1) ... Setting up html2text (1.3.2a-15) ... Setting up libcroco3 (0.6.2-1) ... Setting up libunistring0 (0.9.3-3) ... Setting up gettext (0.18.1.1-3ubuntu1) ... Setting up intltool-debian (0.35.0+20060710.1) ... Setting up po-debconf (1.0.16+nmu1) ... Setting up debhelper (8.1.2ubuntu4) ... Setting up libmono0 (2.6.7-5ubuntu2) ... Setting up libsqlite0 (2.8.17-6build2) ... Setting up libexif12 (0.6.20-0ubuntu1) ... Setting up libgif4 (4.1.6-9) ... Setting up libgdiplus (2.6.7-3ubuntu1) ... Setting up libglib2.0-data (2.28.5-0ubuntu1) ... Setting up libglib2.0-bin (2.28.5-0ubuntu1) ... Setting up pkg-config (0.25-1.1ubuntu1) ... Setting up zlib1g-dev (1:1.2.3.4.dfsg-3ubuntu3) ... Setting up libglib2.0-dev (2.28.5-0ubuntu1) ... Setting up libmono-dev (2.6.7-5ubuntu2) ... Setting up libxml-perl (0.08-2) ... Setting up libxml-regexp-perl (0.03-8) ... Setting up libxml-dom-perl (1.44-1) ... Setting up dbus (1.4.6-1ubuntu6) ... Setting up dbus-x11 (1.4.6-1ubuntu6) ... Setting up libidl0 (0.8.14-0.1ubuntu1) ... Setting up liborbit2 (1:2.14.19-0ubuntu2) ... Setting up gconf2-common (2.32.2-0ubuntu1) ... Creating config file /etc/gconf/2/path with new version Setting up libgconf2-4 (2.32.2-0ubuntu1) ... Setting up gconf2 (2.32.2-0ubuntu1) ... update-alternatives: using /usr/bin/gconftool-2 to provide /usr/bin/gconftool (gconftool) in auto mode. Setting up gnome-mime-data (2.18.0-1) ... Setting up libxml-namespacesupport-perl (1.09-3) ... Setting up libxml-sax-perl (0.96+dfsg-2) ... update-perl-sax-parsers: Registering Perl SAX parser XML::SAX::PurePerl with priority 10... update-perl-sax-parsers: Updating overall Perl SAX parser modules info file... Creating config file /etc/perl/XML/SAX/ParserDetails.ini with new version Setting up libxml-libxml-perl (1.70.ds-1) ... update-perl-sax-parsers: Registering Perl SAX parser XML::LibXML::SAX::Parser with priority 50... update-perl-sax-parsers: Registering Perl SAX parser XML::LibXML::SAX with priority 50... update-perl-sax-parsers: Updating overall Perl SAX parser modules info file... Replacing config file /etc/perl/XML/SAX/ParserDetails.ini with new version Setting up intltool (0.41.1-1) ... Setting up libart-2.0-2 (2.3.21-1) ... Setting up libasound2 (1.0.24.1-0ubuntu3) ... Setting up libatk1.0-dev (2.0.0-0ubuntu1) ... Setting up libbonobo2-common (2.32.1-0ubuntu1) ... Setting up libbonobo2-0 (2.32.1-0ubuntu1) ... Setting up libjasper1 (1.900.1-7ubuntu2) ... Setting up libgdk-pixbuf2.0-0 (2.23.3-0ubuntu1) ... Setting up libgtk2.0-common (2.24.4-0ubuntu1) ... Setting up libcups2 (1.4.6-4) ... Setting up shared-mime-info (0.90-1ubuntu1) ... Setting up libgtk2.0-0 (2.24.4-0ubuntu1) ... Setting up libglade2-0 (1:2.6.4-1build1) ... Setting up libltdl7 (2.2.6b-2ubuntu3) ... Setting up libtdb1 (1.2.9-1fakesync1) ... Setting up libogg0 (1.2.0~dfsg-1) ... Setting up libvorbis0a (1.3.2-1ubuntu1) ... Setting up libvorbisfile3 (1.3.2-1ubuntu1) ... Setting up libcanberra0 (0.28-0ubuntu3) ... Setting up libgnomevfs2-common (1:2.24.4-0ubuntu4) ... Setting up libgnome2-common (2.32.1-0ubuntu3) ... Setting up libgail18 (2.24.4-0ubuntu1) ... Setting up libgnomecanvas2-common (2.30.3-0ubuntu1) ... Setting up libgnomecanvas2-0 (2.30.3-0ubuntu1) ... Setting up libbonoboui2-common (2.24.5-0ubuntu1) ... Setting up libcairo-gobject2 (1.10.2-2ubuntu2) ... Setting up libcairo-script-interpreter2 (1.10.2-2ubuntu2) ... Setting up libexpat1-dev (2.0.1-7ubuntu3) ... Setting up libfreetype6-dev (2.4.4-1ubuntu2) ... Setting up libfontconfig1-dev (2.8.0-2.1ubuntu3) ... Setting up libxau-dev (1:1.0.6-1ubuntu1) ... Setting up libxdmcp-dev (1:1.1.0-1ubuntu1) ... Setting up x11proto-input-dev (2.0.1-1ubuntu1) ... Setting up x11proto-kb-dev (1.0.5-1) ... Setting up libpthread-stubs0 (0.3-2) ... Setting up libpthread-stubs0-dev (0.3-2) ... Setting up libxcb1-dev (1.7-2ubuntu2) ... Setting up libx11-dev (2:1.4.2-1ubuntu3) ... Setting up x11proto-render-dev (2:0.11.1-1) ... Setting up libxrender-dev (1:0.9.6-1ubuntu1) ... Setting up libpng12-dev (1.2.44-1ubuntu3) ... Setting up libsm-dev (2:1.2.0-1ubuntu1) ... Setting up libpixman-1-dev (0.20.2-0ubuntu1) ... Setting up libxcb-render0-dev (1.7-2ubuntu2) ... Setting up libxcb-shm0-dev (1.7-2ubuntu2) ... Setting up libcairo2-dev (1.10.2-2ubuntu2) ... Setting up libdbus-1-dev (1.4.6-1ubuntu6) ... Setting up libidl-dev (0.8.14-0.1ubuntu1) ... Setting up liborbit2-dev (1:2.14.19-0ubuntu2) ... Setting up libgconf2-dev (2.32.2-0ubuntu1) ... Setting up libgdk-pixbuf2.0-dev (2.23.3-0ubuntu1) ... Setting up libxcb-atom1 (0.3.6-1build1) ... Setting up libxcb-aux0 (0.3.6-1build1) ... Setting up libxcb-event1 (0.3.6-1build1) ... Setting up libstartup-notification0 (0.10-1build1) ... Setting up libgnome-desktop-2-17 (1:2.32.1-0ubuntu5) ... Setting up libgnome-keyring0 (2.32.0-1ubuntu2) ... Setting up libgnomeui-common (2.24.5-0ubuntu1) ... Setting up libxft-dev (2.2.0-2ubuntu2) ... Setting up libpango1.0-dev (1.28.4-0ubuntu1) ... Setting up x11proto-xext-dev (7.1.99.0~git20110111.9df8b776-0ubuntu2) ... Setting up libxext-dev (2:1.2.0-2ubuntu1) ... Setting up x11proto-xinerama-dev (1.2.1-1) ... Setting up libxinerama-dev (2:1.1.1-1ubuntu1) ... Setting up xorg-sgml-doctools (1:1.6-1) ... Setting up libxi-dev (2:1.4.1-1ubuntu2) ... Setting up x11proto-randr-dev (1.4.0+git20101207.0d32bb07-0ubuntu1) ... Setting up libxrandr-dev (2:1.3.1-1ubuntu1) ... Setting up x11proto-fixes-dev (1:4.1.2-1) ... Setting up libxfixes-dev (1:4.0.5-1ubuntu1) ... Setting up libxcursor-dev (1:1.1.11-1ubuntu1) ... Setting up x11proto-composite-dev (1:0.4.2-1) ... Setting up libxcomposite-dev (1:0.4.3-1ubuntu1) ... Setting up x11proto-damage-dev (1:1.2.1-1) ... Setting up libxdamage-dev (1:1.1.3-1ubuntu1) ... Setting up libxml2-utils (2.7.8.dfsg-2) ... Setting up libgtk2.0-dev (2.24.4-0ubuntu1) ... Setting up librsvg2-2 (2.32.1-0ubuntu3) ... Setting up libwnck-common (1:2.30.6-0ubuntu3) ... Setting up libxres1 (2:1.0.5-1) ... Setting up libwnck22 (1:2.30.6-0ubuntu3) ... Setting up gamin (0.1.10-2ubuntu1) ... Setting up libgamin0 (0.1.10-2ubuntu1) ... Setting up libgnomevfs2-0 (1:2.24.4-0ubuntu4) ... Setting up libgnome2-0 (2.32.1-0ubuntu3) ... Setting up libbonoboui2-0 (2.24.5-0ubuntu1) ... Setting up libgnomeui-0 (2.24.5-0ubuntu1) ... Setting up mono-2.0-gac (2.6.7-5ubuntu2) ... Setting up mono-gac (2.6.7-5ubuntu2) ... * Installing 6 assemblies from libart2.0-cil into Mono * Installing 1 assembly from libdbus-glib1.0-cil into Mono * Installing 1 assembly from libdbus1.0-cil into Mono * Installing 6 assemblies from libgconf2.0-cil into Mono * Installing 1 assembly from libglade2.0-cil into Mono * Installing 1 assembly from libglib2.0-cil into Mono * Installing 1 assembly from libgnome-keyring1.0-cil into Mono * Installing 6 assemblies from libgnome-vfs2.0-cil into Mono * Installing 2 assemblies from libgnome2.24-cil into Mono * Installing 1 assembly from libgnomedesktop2.20-cil into Mono * Installing 5 assemblies from libgtk2.0-cil into Mono * Installing 3 assemblies from libmono-addins-gui0.2-cil into Mono * Installing 7 assemblies from libmono-addins0.2-cil into Mono * Installing 1 assembly from libndesk-dbus-glib1.0-cil into Mono * Installing 1 assembly from libndesk-dbus1.0-cil into Mono * Installing 1 assembly from libnotify0.4-cil into Mono * Installing 6 assemblies from libnunit2.4-cil into Mono * Installing 1 assembly from librsvg2-2.18-cil into Mono * Installing 1 assembly from libwnck2.20-cil into Mono update-alternatives: using /usr/bin/gacutil to provide /usr/bin/cli-gacutil (global-assembly-cache-tool) in auto mode. Setting up mono-runtime (2.6.7-5ubuntu2) ... update-alternatives: using /usr/bin/mono to provide /usr/bin/cli (cli) in auto mode. Setting up libmono-corlib2.0-cil (2.6.7-5ubuntu2) ... Setting up libmono-posix2.0-cil (2.6.7-5ubuntu2) ... Setting up libmono-corlib1.0-cil (2.6.7-5ubuntu2) ... Setting up mono-utils (2.6.7-5ubuntu2) ... update-alternatives: using /usr/bin/monodis to provide /usr/bin/cli-ildasm (cil-disassembler) in auto mode. Setting up libmono-system1.0-cil (2.6.7-5ubuntu2) ... Setting up libmono-relaxng1.0-cil (2.6.7-5ubuntu2) ... Setting up libmono-security1.0-cil (2.6.7-5ubuntu2) ... Setting up libmono-data-tds1.0-cil (2.6.7-5ubuntu2) ... Setting up libmono-system-data1.0-cil (2.6.7-5ubuntu2) ... Setting up libmono-system-web1.0-cil (2.6.7-5ubuntu2) ... Setting up libmono-system-runtime1.0-cil (2.6.7-5ubuntu2) ... Setting up libmono-peapi2.0-cil (2.6.7-5ubuntu2) ... Setting up libmono-sharpzip0.84-cil (2.6.7-5ubuntu2) ... Setting up libmono1.0-cil (2.6.7-5ubuntu2) ... Setting up libmono-posix1.0-cil (2.6.7-5ubuntu2) ... Setting up libmono-getoptions1.0-cil (2.6.7-5ubuntu2) ... Setting up libmono-data1.0-cil (2.6.7-5ubuntu2) ... Setting up libmono-c5-1.1-cil (2.6.7-5ubuntu2) ... Setting up libmono-i18n-west1.0-cil (2.6.7-5ubuntu2) ... Setting up libmono-i18n1.0-cil (2.6.7-5ubuntu2) ... Setting up libmono-i18n-west2.0-cil (2.6.7-5ubuntu2) ... Setting up libmono-i18n2.0-cil (2.6.7-5ubuntu2) ... Setting up libmono-system-messaging1.0-cil (2.6.7-5ubuntu2) ... Setting up libmono-ldap1.0-cil (2.6.7-5ubuntu2) ... Setting up libmono-system-ldap1.0-cil (2.6.7-5ubuntu2) ... Setting up libmono-accessibility1.0-cil (2.6.7-5ubuntu2) ... Setting up libmono-winforms1.0-cil (2.6.7-5ubuntu2) ... Setting up libmono-accessibility2.0-cil (2.6.7-5ubuntu2) ... Setting up libmono-cairo1.0-cil (2.6.7-5ubuntu2) ... Setting up libmono-cairo2.0-cil (2.6.7-5ubuntu2) ... Setting up libmono-sharpzip0.6-cil (2.6.7-5ubuntu2) ... Setting up libmono-sharpzip2.6-cil (2.6.7-5ubuntu2) ... Setting up libmono-npgsql1.0-cil (2.6.7-5ubuntu2) ... Setting up libmono-bytefx0.7.6.1-cil (2.6.7-5ubuntu2) ... Setting up libmono-oracle1.0-cil (2.6.7-5ubuntu2) ... Setting up libmono-sqlite1.0-cil (2.6.7-5ubuntu2) ... Setting up libmono-cscompmgd7.0-cil (2.6.7-5ubuntu2) ... Setting up libmono-microsoft7.0-cil (2.6.7-5ubuntu2) ... Setting up libmono-peapi1.0-cil (2.6.7-5ubuntu2) ... Setting up libmono-tasklets2.0-cil (2.6.7-5ubuntu2) ... Setting up libmono-system2.0-cil (2.6.7-5ubuntu2) ... Setting up libmono-security2.0-cil (2.6.7-5ubuntu2) ... Setting up libmono-cecil-private-cil (2.6.7-5ubuntu2) ... Setting up libmono-getoptions2.0-cil (2.6.7-5ubuntu2) ... Setting up libmono-relaxng2.0-cil (2.6.7-5ubuntu2) ... Setting up libmono-data-tds2.0-cil (2.6.7-5ubuntu2) ... Setting up libmono-system-data2.0-cil (2.6.7-5ubuntu2) ... Setting up libmono-messaging2.0-cil (2.6.7-5ubuntu2) ... Setting up libmono-system-messaging2.0-cil (2.6.7-5ubuntu2) ... Setting up libmono-sqlite2.0-cil (2.6.7-5ubuntu2) ... Setting up libmono-sharpzip2.84-cil (2.6.7-5ubuntu2) ... Setting up libmono-system-data-linq2.0-cil (2.6.7-5ubuntu2) ... Setting up libmono2.0-cil (2.6.7-5ubuntu2) ... Setting up mono-gmcs (2.6.7-5ubuntu2) ... Setting up libmono-data2.0-cil (2.6.7-5ubuntu2) ... Setting up libmono-webbrowser0.5-cil (2.6.7-5ubuntu2) ... Setting up libmono-management2.0-cil (2.6.7-5ubuntu2) ... Setting up libmono-rabbitmq2.0-cil (2.6.7-5ubuntu2) ... Setting up libmono-messaging-rabbitmq2.0-cil (2.6.7-5ubuntu2) ... Setting up libmono-simd2.0-cil (2.6.7-5ubuntu2) ... Setting up libmono-ldap2.0-cil (2.6.7-5ubuntu2) ... Setting up libmono-system-ldap2.0-cil (2.6.7-5ubuntu2) ... Setting up libmono-npgsql2.0-cil (2.6.7-5ubuntu2) ... Setting up libmono-bytefx0.7.6.2-cil (2.6.7-5ubuntu2) ... Setting up libmono-db2-1.0-cil (2.6.7-5ubuntu2) ... Setting up libmono-oracle2.0-cil (2.6.7-5ubuntu2) ... Setting up libmono-cscompmgd8.0-cil (2.6.7-5ubuntu2) ... Setting up libmono-microsoft-build2.0-cil (2.6.7-5ubuntu2) ... Setting up libmono-microsoft8.0-cil (2.6.7-5ubuntu2) ... Setting up libmono-debugger-soft0.0-cil (2.6.7-5ubuntu2) ... Setting up libmono-windowsbase3.0-cil (2.6.7-5ubuntu2) ... Setting up libglib2.0-cil (2.12.10-1ubuntu1) ... * Installing 1 assembly from libglib2.0-cil into Mono Setting up gtk-sharp2-gapi (2.12.10-1ubuntu1) ... Setting up libart2.0-cil (2.24.2-0ubuntu1) ... * Installing 6 assemblies from libart2.0-cil into Mono Setting up libart2.0-cil-dev (2.24.2-0ubuntu1) ... Setting up libdbus1.0-cil (0.7.0-2) ... * Installing 1 assembly from libdbus1.0-cil into Mono Setting up libdbus-glib1.0-cil (0.5.0-2) ... * Installing 1 assembly from libdbus-glib1.0-cil into Mono Setting up libdbus1.0-cil-dev (0.7.0-2) ... Setting up libdbus-glib1.0-cil-dev (0.5.0-2) ... Setting up libgconf2.0-cil (2.24.2-0ubuntu1) ... * Installing 6 assemblies from libgconf2.0-cil into Mono Setting up libgconf2.0-cil-dev (2.24.2-0ubuntu1) ... Setting up libgio-cil (2.22.2-2) ... Setting up libgio2.0-cil-dev (2.22.2-2) ... Setting up libgtk2.0-cil (2.12.10-1ubuntu1) ... * Installing 5 assemblies from libgtk2.0-cil into Mono Setting up libglade2.0-cil (2.12.10-1ubuntu1) ... * Installing 1 assembly from libglade2.0-cil into Mono Setting up libglib2.0-cil-dev (2.12.10-1ubuntu1) ... Setting up libgnome-keyring1.0-cil (1.0.0-3) ... * Installing 1 assembly from libgnome-keyring1.0-cil into Mono Setting up libgnome-keyring1.0-cil-dev (1.0.0-3) ... Setting up libgnome-vfs2.0-cil (2.24.2-0ubuntu1) ... * Installing 6 assemblies from libgnome-vfs2.0-cil into Mono Setting up libgnome-vfs2.0-cil-dev (2.24.2-0ubuntu1) ... Setting up libgnome2.24-cil (2.24.2-0ubuntu1) ... * Installing 2 assemblies from libgnome2.24-cil into Mono Setting up libgtk2.0-cil-dev (2.12.10-1ubuntu1) ... Setting up libgnome2.0-cil-dev (2.24.2-0ubuntu1) ... Setting up libgnomedesktop2.20-cil (2.26.0-3build1) ... * Installing 1 assembly from libgnomedesktop2.20-cil into Mono Setting up libgnomedesktop2.0-cil-dev (2.26.0-3build1) ... Setting up libmono-addins0.2-cil (0.4-8) ... * Installing 7 assemblies from libmono-addins0.2-cil into Mono Setting up libmono-addins-cil-dev (0.4-8) ... Setting up libmono-addins-gui0.2-cil (0.4-8) ... * Installing 3 assemblies from libmono-addins-gui0.2-cil into Mono Setting up libmono-addins-gui-cil-dev (0.4-8) ... Setting up libndesk-dbus1.0-cil (0.6.0-4) ... * Installing 1 assembly from libndesk-dbus1.0-cil into Mono Setting up libndesk-dbus-glib1.0-cil (0.4.1-3) ... * Installing 1 assembly from libndesk-dbus-glib1.0-cil into Mono Setting up libnotify0.4-cil (0.4.0~r3032-2ubuntu1) ... * Installing 1 assembly from libnotify0.4-cil into Mono Setting up libnotify-cil-dev (0.4.0~r3032-2ubuntu1) ... Setting up librsvg2-2.18-cil (2.26.0-3build1) ... * Installing 1 assembly from librsvg2-2.18-cil into Mono Setting up librsvg2-2.0-cil-dev (2.26.0-3build1) ... Setting up libwnck2.20-cil (2.26.0-3build1) ... * Installing 1 assembly from libwnck2.20-cil into Mono Setting up libwnck1.0-cil-dev (2.26.0-3build1) ... Setting up libmono-system-web2.0-cil (2.6.7-5ubuntu2) ... Setting up mono-2.0-devel (2.6.7-5ubuntu2) ... Setting up libmono-system-web-mvc1.0-cil (2.6.7-5ubuntu2) ... Setting up libmono-system-web-mvc2.0-cil (2.6.7-5ubuntu2) ... Setting up libmono-system-runtime2.0-cil (2.6.7-5ubuntu2) ... Setting up libmono-winforms2.0-cil (2.6.7-5ubuntu2) ... Setting up libnunit2.4-cil (2.4.7+dfsg-6) ... * Installing 6 assemblies from libnunit2.4-cil into Mono Setting up libnunit-cil-dev (2.4.7+dfsg-6) ... Setting up libmono-wcf3.0-cil (2.6.7-5ubuntu2) ... Setting up libmono-cil-dev (2.6.7-5ubuntu2) ... Setting up mono-devel (2.6.7-5ubuntu2) ... update-alternatives: using /usr/bin/mono-csc to provide /usr/bin/cli-csc (c-sharp-compiler) in auto mode. update-alternatives: warning: skip creation of /usr/share/man/man1/cli-csc.1.gz because associated file /usr/share/man/man1/csc.1.gz (of link group c-sharp-compiler) doesn't exist. update-alternatives: using /usr/bin/resgen to provide /usr/bin/cli-resgen (resource-file-generator) in auto mode. update-alternatives: using /usr/bin/al to provide /usr/bin/cli-al (assembly-linker) in auto mode. update-alternatives: using /usr/bin/sn to provide /usr/bin/cli-sn (strong-name-tool) in auto mode. Setting up cli-common-dev (0.7.1) ... Processing triggers for libc-bin ... ldconfig deferred processing now taking place Checking correctness of source dependencies... Toolchain package versions: libc6-dev_2.13-0ubuntu12 make_3.81-8ubuntu1 dpkg-dev_1.16.0~ubuntu6 gcc-4.5_4.5.2-8ubuntu2 g++-4.5_4.5.2-8ubuntu2 binutils_2.21.0.20110327-2ubuntu2 libstdc++6-4.5-dev_4.5.2-8ubuntu2 libstdc++6_4.5.2-8ubuntu2 ------------------------------------------------------------------------------ dpkg-source: warning: -sn is not a valid option for Dpkg::Source::Package::V3::quilt gpgv: Signature made Sat Apr 9 10:04:52 2011 UTC using RSA key ID 0E1FAD0C gpgv: Can't check signature: public key not found dpkg-source: warning: failed to verify signature on ./docky_2.1.2-1.dsc dpkg-source: info: extracting docky in docky-2.1.2 dpkg-source: info: unpacking docky_2.1.2.orig.tar.gz dpkg-source: info: unpacking docky_2.1.2-1.debian.tar.gz dpkg-buildpackage: export CFLAGS from dpkg-buildflags (origin: vendor): -g -O2 dpkg-buildpackage: export CPPFLAGS from dpkg-buildflags (origin: vendor): dpkg-buildpackage: export CXXFLAGS from dpkg-buildflags (origin: vendor): -g -O2 dpkg-buildpackage: export FFLAGS from dpkg-buildflags (origin: vendor): -g -O2 dpkg-buildpackage: export LDFLAGS from dpkg-buildflags (origin: vendor): -Wl,-Bsymbolic-functions dpkg-buildpackage: source package docky dpkg-buildpackage: source version 2.1.2-1 dpkg-source --before-build docky-2.1.2 dpkg-buildpackage: host architecture i386 /usr/bin/fakeroot debian/rules clean dh clean dh_testdir Unknown option: with dh_testdir: warning: ignored unknown options in DH_OPTIONS dh_auto_clean Unknown option: with dh_auto_clean: warning: ignored unknown options in DH_OPTIONS dh_clean Unknown option: with dh_clean: warning: ignored unknown options in DH_OPTIONS debian/rules build dh build dh_testdir Unknown option: with dh_testdir: warning: ignored unknown options in DH_OPTIONS debian/rules override_dh_auto_configure make[1]: Entering directory `/build/buildd/docky-2.1.2' dh_auto_configure -- MCS=/usr/bin/mono-csc Unknown option: with Unknown option: with dh_auto_configure: warning: ignored unknown options in DH_OPTIONS configure: WARNING: unrecognized options: --disable-maintainer-mode checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... no checking for mawk... mawk checking whether make sets $(MAKE)... yes checking how to create a pax tar archive... gnutar checking whether NLS is requested... yes checking for style of include used by make... GNU checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking dependency style of gcc... none checking for intltool >= 0.35.0... 0.41.1 found checking for intltool-update... /usr/bin/intltool-update checking for intltool-merge... /usr/bin/intltool-merge checking for intltool-extract... /usr/bin/intltool-extract checking for xgettext... /usr/bin/xgettext checking for msgmerge... /usr/bin/msgmerge checking for msgfmt... /usr/bin/msgfmt checking for gmsgfmt... /usr/bin/msgfmt checking for perl... /usr/bin/perl checking for perl >= 5.8.1... 5.10.1 checking for XML::Parser... ok checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking 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... (cached) /usr/bin/msgfmt checking for xgettext... (cached) /usr/bin/xgettext checking for catalogs to be installed... ast bg bn ca cs da de el en_GB es et eu fi fil fo fr gl he hi hr hu id is it ja kk ko lt nb nl nn pl pt pt_BR ro ru sk sl sr sv tr uk vi zh_CN zh_HK zh_TW checking for pkg-config... /usr/bin/pkg-config checking for gcc... (cached) gcc checking whether we are using the GNU C compiler... (cached) yes checking whether gcc accepts -g... (cached) yes checking for gcc option to accept ISO C89... (cached) none needed checking dependency style of gcc... (cached) none checking for ANSI C header files... (cached) yes checking for mono... /usr/bin/mono checking for gmcs... /usr/bin/mono-csc checking pkg-config is at least version 0.9.0... yes checking for GCONF... 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 GCONF_SHARP_20... yes checking for GLIB_SHARP_20... yes checking for GIO_SHARP... yes `/usr/lib/pkgconfig/../../lib/gio-sharp/gio-sharp.dll' -> `/build/buildd/docky-2.1.2//build/gio-sharp.dll' `/usr/lib/pkgconfig/../../lib/gio-sharp/gio-sharp.dll.config' -> `/build/buildd/docky-2.1.2//build/gio-sharp.dll.config' checking for GNOME_DESKTOP_SHARP_20... yes checking for GNOME_KEYRING_SHARP... yes checking for GTK_SHARP_20... yes checking for LIBRSVG_SHARP... yes checking for MONO_ADDINS... yes checking for MONO_ADDINS_GUI... yes checking for MONO_ADDINS_SETUP... yes checking for MONO_CAIRO... yes checking for DBUS_SHARP_10... yes checking for DBUS_SHARP_GLIB_10... yes checking for NOTIFY_SHARP... yes checking for WNCK_SHARP_10... yes checking for GIO... yes checking for GTK... yes checking for GLIB... yes configure: creating ./config.status config.status: creating Docky/Makefile config.status: creating Docky.CairoHelper/Makefile config.status: creating Docky.DBus/Makefile config.status: creating Docky.Items/Makefile config.status: creating Docky.Widgets/Makefile config.status: creating Docky.Services/Makefile config.status: creating Docky.Services/AssemblyInfo.cs config.status: creating Docky/docky config.status: creating Docky/AssemblyInfo.cs config.status: creating StandardPlugins/Makefile config.status: creating StandardPlugins/BatteryMonitor/Makefile config.status: creating StandardPlugins/BatteryMonitor/Resources/BatteryMonitor.addin.xml config.status: creating StandardPlugins/Bookmarks/Makefile config.status: creating StandardPlugins/Bookmarks/Resources/Bookmarks.addin.xml config.status: creating StandardPlugins/Clippy/Makefile config.status: creating StandardPlugins/Clippy/Resources/Clippy.addin.xml config.status: creating StandardPlugins/Clock/Makefile config.status: creating StandardPlugins/Clock/Resources/Clock.addin.xml config.status: creating StandardPlugins/Clock/Themes/Makefile config.status: creating StandardPlugins/Clock/Themes/Default/Makefile config.status: creating StandardPlugins/Clock/Themes/Default24/Makefile config.status: creating StandardPlugins/CPUMonitor/Makefile config.status: creating StandardPlugins/CPUMonitor/Resources/CPUMonitor.addin.xml config.status: creating StandardPlugins/Desktop/Makefile config.status: creating StandardPlugins/Desktop/Resources/Desktop.addin.xml config.status: creating StandardPlugins/GMail/Makefile config.status: creating StandardPlugins/GMail/Resources/GMail.addin.xml config.status: creating StandardPlugins/Mounter/Makefile config.status: creating StandardPlugins/Mounter/Resources/Mounter.addin.xml config.status: creating StandardPlugins/NetworkManager/Makefile config.status: creating StandardPlugins/NetworkManager/Resources/NetworkManager.addin.xml config.status: creating StandardPlugins/NPR/Makefile config.status: creating StandardPlugins/NPR/Resources/NPR.addin.xml config.status: creating StandardPlugins/RecentDocuments/Makefile config.status: creating StandardPlugins/RecentDocuments/Resources/RecentDocuments.addin.xml config.status: creating StandardPlugins/SessionManager/Makefile config.status: creating StandardPlugins/SessionManager/Resources/SessionManager.addin.xml config.status: creating StandardPlugins/Timer/Makefile config.status: creating StandardPlugins/Timer/Resources/Timer.addin.xml config.status: creating StandardPlugins/Trash/Makefile config.status: creating StandardPlugins/Trash/Resources/Trash.addin.xml config.status: creating StandardPlugins/Weather/Makefile config.status: creating StandardPlugins/Weather/Resources/Weather.addin.xml config.status: creating StandardPlugins/WorkspaceSwitcher/Makefile config.status: creating StandardPlugins/WorkspaceSwitcher/Resources/WorkspaceSwitcher.addin.xml config.status: creating Makefile config.status: creating data/Makefile config.status: creating data/icons/Makefile config.status: creating data/icons/hicolor/16x16/Makefile config.status: creating data/icons/hicolor/16x16/apps/Makefile config.status: creating data/icons/hicolor/22x22/Makefile config.status: creating data/icons/hicolor/22x22/apps/Makefile config.status: creating data/icons/hicolor/24x24/Makefile config.status: creating data/icons/hicolor/24x24/apps/Makefile config.status: creating data/icons/hicolor/32x32/Makefile config.status: creating data/icons/hicolor/32x32/apps/Makefile config.status: creating data/icons/hicolor/48x48/Makefile config.status: creating data/icons/hicolor/48x48/apps/Makefile config.status: creating data/icons/hicolor/48x48/mimetypes/Makefile config.status: creating data/icons/hicolor/64x64/Makefile config.status: creating data/icons/hicolor/64x64/apps/Makefile config.status: creating data/icons/hicolor/128x128/Makefile config.status: creating data/icons/hicolor/128x128/apps/Makefile config.status: creating data/icons/hicolor/Makefile config.status: creating data/themes/Makefile config.status: creating data/themes/Air/Makefile config.status: creating data/themes/Glass/Makefile config.status: creating data/themes/Grayscale/Makefile config.status: creating data/themes/HUD/Makefile config.status: creating data/themes/Matte/Makefile config.status: creating data/themes/Smoke/Makefile config.status: creating data/themes/Transparent/Makefile config.status: creating m4/Makefile config.status: creating man/Makefile config.status: creating po/Makefile.in config.status: executing depfiles commands config.status: executing default-1 commands config.status: executing po/stamp-it commands configure: WARNING: unrecognized options: --disable-maintainer-mode docky-2.1.2 Build Environment Install Prefix: /usr Mono C# Compiler: /usr/bin/mono-csc -noconfig -codepage:utf8 -warn:4 Mono Runtime: /usr/bin/mono Build/Development Release Build: no Debug Build: no Use HeapShot: no make[1]: Leaving directory `/build/buildd/docky-2.1.2' dh_auto_build Unknown option: with dh_auto_build: warning: ignored unknown options in DH_OPTIONS make[1]: Entering directory `/build/buildd/docky-2.1.2' Making all in . make[2]: Entering directory `/build/buildd/docky-2.1.2' make[2]: Nothing to be done for `all-am'. make[2]: Leaving directory `/build/buildd/docky-2.1.2' Making all in data make[2]: Entering directory `/build/buildd/docky-2.1.2/data' Making all in icons make[3]: Entering directory `/build/buildd/docky-2.1.2/data/icons' Making all in hicolor make[4]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor' Making all in 16x16 make[5]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/16x16' Making all in apps make[6]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/16x16/apps' make[6]: Nothing to be done for `all'. make[6]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/16x16/apps' make[6]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/16x16' make[6]: Nothing to be done for `all-am'. make[6]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/16x16' make[5]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/16x16' Making all in 22x22 make[5]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/22x22' Making all in apps make[6]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/22x22/apps' make[6]: Nothing to be done for `all'. make[6]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/22x22/apps' make[6]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/22x22' make[6]: Nothing to be done for `all-am'. make[6]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/22x22' make[5]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/22x22' Making all in 24x24 make[5]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/24x24' Making all in apps make[6]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/24x24/apps' make[6]: Nothing to be done for `all'. make[6]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/24x24/apps' make[6]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/24x24' make[6]: Nothing to be done for `all-am'. make[6]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/24x24' make[5]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/24x24' Making all in 32x32 make[5]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/32x32' Making all in apps make[6]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/32x32/apps' make[6]: Nothing to be done for `all'. make[6]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/32x32/apps' make[6]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/32x32' make[6]: Nothing to be done for `all-am'. make[6]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/32x32' make[5]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/32x32' Making all in 48x48 make[5]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/48x48' Making all in apps make[6]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/48x48/apps' make[6]: Nothing to be done for `all'. make[6]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/48x48/apps' Making all in mimetypes make[6]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/48x48/mimetypes' make[6]: Nothing to be done for `all'. make[6]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/48x48/mimetypes' make[6]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/48x48' make[6]: Nothing to be done for `all-am'. make[6]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/48x48' make[5]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/48x48' Making all in 64x64 make[5]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/64x64' Making all in apps make[6]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/64x64/apps' make[6]: Nothing to be done for `all'. make[6]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/64x64/apps' make[6]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/64x64' make[6]: Nothing to be done for `all-am'. make[6]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/64x64' make[5]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/64x64' Making all in 128x128 make[5]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/128x128' Making all in apps make[6]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/128x128/apps' make[6]: Nothing to be done for `all'. make[6]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/128x128/apps' make[6]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/128x128' make[6]: Nothing to be done for `all-am'. make[6]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/128x128' make[5]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/128x128' make[5]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor' make[5]: Nothing to be done for `all-am'. make[5]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor' make[4]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor' make[4]: Entering directory `/build/buildd/docky-2.1.2/data/icons' make[4]: Nothing to be done for `all-am'. make[4]: Leaving directory `/build/buildd/docky-2.1.2/data/icons' make[3]: Leaving directory `/build/buildd/docky-2.1.2/data/icons' Making all in themes make[3]: Entering directory `/build/buildd/docky-2.1.2/data/themes' Making all in Grayscale make[4]: Entering directory `/build/buildd/docky-2.1.2/data/themes/Grayscale' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/build/buildd/docky-2.1.2/data/themes/Grayscale' Making all in Air make[4]: Entering directory `/build/buildd/docky-2.1.2/data/themes/Air' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/build/buildd/docky-2.1.2/data/themes/Air' Making all in Glass make[4]: Entering directory `/build/buildd/docky-2.1.2/data/themes/Glass' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/build/buildd/docky-2.1.2/data/themes/Glass' Making all in HUD make[4]: Entering directory `/build/buildd/docky-2.1.2/data/themes/HUD' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/build/buildd/docky-2.1.2/data/themes/HUD' Making all in Matte make[4]: Entering directory `/build/buildd/docky-2.1.2/data/themes/Matte' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/build/buildd/docky-2.1.2/data/themes/Matte' Making all in Smoke make[4]: Entering directory `/build/buildd/docky-2.1.2/data/themes/Smoke' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/build/buildd/docky-2.1.2/data/themes/Smoke' Making all in Transparent make[4]: Entering directory `/build/buildd/docky-2.1.2/data/themes/Transparent' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/build/buildd/docky-2.1.2/data/themes/Transparent' make[4]: Entering directory `/build/buildd/docky-2.1.2/data/themes' make[4]: Nothing to be done for `all-am'. make[4]: Leaving directory `/build/buildd/docky-2.1.2/data/themes' make[3]: Leaving directory `/build/buildd/docky-2.1.2/data/themes' make[3]: Entering directory `/build/buildd/docky-2.1.2/data' LC_ALL=C /usr/bin/intltool-merge -d -u -c ../po/.intltool-merge-cache ../po docky.desktop.in docky.desktop Generating and caching the translation database Merging translations into docky.desktop. LC_ALL=C /usr/bin/intltool-merge -s -u -c ../po/.intltool-merge-cache ../po docky.schemas.in docky.schemas Found cached translation database Merging translations into docky.schemas. make[3]: Leaving directory `/build/buildd/docky-2.1.2/data' make[2]: Leaving directory `/build/buildd/docky-2.1.2/data' Making all in po make[2]: Entering directory `/build/buildd/docky-2.1.2/po' file=`echo ast | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file ast.po file=`echo bg | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file bg.po file=`echo bn | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file bn.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 el | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file el.po file=`echo en_GB | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file en_GB.po file=`echo es | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file es.po file=`echo et | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file et.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 fil | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file fil.po file=`echo fo | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file fo.po file=`echo fr | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file fr.po file=`echo gl | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file gl.po file=`echo he | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file he.po file=`echo hi | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file hi.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 id | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file id.po file=`echo is | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file is.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 kk | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file kk.po file=`echo ko | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file ko.po file=`echo lt | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file lt.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 nn | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file nn.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 ro | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file ro.po file=`echo ru | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file ru.po file=`echo sk | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file sk.po file=`echo sl | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file sl.po file=`echo sr | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file sr.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_HK | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file zh_HK.po file=`echo zh_TW | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file zh_TW.po make[2]: Leaving directory `/build/buildd/docky-2.1.2/po' Making all in Docky.CairoHelper make[2]: Entering directory `/build/buildd/docky-2.1.2/Docky.CairoHelper' Compiling Docky.CairoHelper.dll... Generating docky.cairohelper.pc... make[2]: Leaving directory `/build/buildd/docky-2.1.2/Docky.CairoHelper' Making all in Docky.Services make[2]: Entering directory `/build/buildd/docky-2.1.2/Docky.Services' Compiling Docky.Services.dll... Generating docky.services.pc... make[2]: Leaving directory `/build/buildd/docky-2.1.2/Docky.Services' Making all in Docky.Widgets make[2]: Entering directory `/build/buildd/docky-2.1.2/Docky.Widgets' Compiling Docky.Widgets.dll... Generating docky.widgets.pc... make[2]: Leaving directory `/build/buildd/docky-2.1.2/Docky.Widgets' Making all in Docky.Items make[2]: Entering directory `/build/buildd/docky-2.1.2/Docky.Items' Compiling Docky.Items.dll... Generating docky.items.pc... make[2]: Leaving directory `/build/buildd/docky-2.1.2/Docky.Items' Making all in Docky.DBus make[2]: Entering directory `/build/buildd/docky-2.1.2/Docky.DBus' Compiling Docky.DBus.dll... make[2]: Leaving directory `/build/buildd/docky-2.1.2/Docky.DBus' Making all in StandardPlugins make[2]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins' Making all in BatteryMonitor make[3]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/BatteryMonitor' Compiling BatteryMonitor.dll... make[3]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/BatteryMonitor' Making all in Bookmarks make[3]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/Bookmarks' Compiling Bookmarks.dll... make[3]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/Bookmarks' Making all in Clippy make[3]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/Clippy' Compiling Clippy.dll... make[3]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/Clippy' Making all in Clock make[3]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/Clock' Making all in Themes make[4]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/Clock/Themes' Making all in Default make[5]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/Clock/Themes/Default' make[5]: Nothing to be done for `all'. make[5]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/Clock/Themes/Default' Making all in Default24 make[5]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/Clock/Themes/Default24' make[5]: Nothing to be done for `all'. make[5]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/Clock/Themes/Default24' make[5]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/Clock/Themes' make[5]: Nothing to be done for `all-am'. make[5]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/Clock/Themes' make[4]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/Clock/Themes' make[4]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/Clock' Compiling Clock.dll... make[4]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/Clock' make[3]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/Clock' Making all in Desktop make[3]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/Desktop' Compiling Desktop.dll... make[3]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/Desktop' Making all in CPUMonitor make[3]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/CPUMonitor' Compiling CPUMonitor.dll... make[3]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/CPUMonitor' Making all in GMail make[3]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/GMail' Compiling GMail.dll... make[3]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/GMail' Making all in Mounter make[3]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/Mounter' Compiling Mounter.dll... make[3]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/Mounter' Making all in NetworkManager make[3]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/NetworkManager' Compiling NetworkManager.dll... make[3]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/NetworkManager' Making all in NPR make[3]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/NPR' Compiling NPR.dll... make[3]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/NPR' Making all in RecentDocuments make[3]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/RecentDocuments' Compiling RecentDocuments.dll... make[3]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/RecentDocuments' Making all in SessionManager make[3]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/SessionManager' Compiling SessionManager.dll... make[3]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/SessionManager' Making all in Timer make[3]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/Timer' Compiling Timer.dll... make[3]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/Timer' Making all in Trash make[3]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/Trash' Compiling Trash.dll... make[3]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/Trash' Making all in Weather make[3]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/Weather' Compiling Weather.dll... make[3]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/Weather' Making all in WorkspaceSwitcher make[3]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/WorkspaceSwitcher' Compiling WorkspaceSwitcher.dll... make[3]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/WorkspaceSwitcher' make[3]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins' make[3]: Nothing to be done for `all-am'. make[3]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins' make[2]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins' Making all in Docky make[2]: Entering directory `/build/buildd/docky-2.1.2/Docky' Compiling Docky.exe... make[2]: Leaving directory `/build/buildd/docky-2.1.2/Docky' Making all in man make[2]: Entering directory `/build/buildd/docky-2.1.2/man' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/build/buildd/docky-2.1.2/man' Making all in m4 make[2]: Entering directory `/build/buildd/docky-2.1.2/m4' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/build/buildd/docky-2.1.2/m4' make[1]: Leaving directory `/build/buildd/docky-2.1.2' dh_auto_test Unknown option: with dh_auto_test: warning: ignored unknown options in DH_OPTIONS make[1]: Entering directory `/build/buildd/docky-2.1.2' Making check in . make[2]: Entering directory `/build/buildd/docky-2.1.2' make[2]: Nothing to be done for `check-am'. make[2]: Leaving directory `/build/buildd/docky-2.1.2' Making check in data make[2]: Entering directory `/build/buildd/docky-2.1.2/data' Making check in icons make[3]: Entering directory `/build/buildd/docky-2.1.2/data/icons' Making check in hicolor make[4]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor' Making check in 16x16 make[5]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/16x16' Making check in apps make[6]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/16x16/apps' make[6]: Nothing to be done for `check'. make[6]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/16x16/apps' make[6]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/16x16' make[6]: Nothing to be done for `check-am'. make[6]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/16x16' make[5]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/16x16' Making check in 22x22 make[5]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/22x22' Making check in apps make[6]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/22x22/apps' make[6]: Nothing to be done for `check'. make[6]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/22x22/apps' make[6]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/22x22' make[6]: Nothing to be done for `check-am'. make[6]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/22x22' make[5]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/22x22' Making check in 24x24 make[5]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/24x24' Making check in apps make[6]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/24x24/apps' make[6]: Nothing to be done for `check'. make[6]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/24x24/apps' make[6]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/24x24' make[6]: Nothing to be done for `check-am'. make[6]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/24x24' make[5]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/24x24' Making check in 32x32 make[5]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/32x32' Making check in apps make[6]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/32x32/apps' make[6]: Nothing to be done for `check'. make[6]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/32x32/apps' make[6]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/32x32' make[6]: Nothing to be done for `check-am'. make[6]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/32x32' make[5]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/32x32' Making check in 48x48 make[5]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/48x48' Making check in apps make[6]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/48x48/apps' make[6]: Nothing to be done for `check'. make[6]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/48x48/apps' Making check in mimetypes make[6]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/48x48/mimetypes' make[6]: Nothing to be done for `check'. make[6]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/48x48/mimetypes' make[6]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/48x48' make[6]: Nothing to be done for `check-am'. make[6]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/48x48' make[5]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/48x48' Making check in 64x64 make[5]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/64x64' Making check in apps make[6]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/64x64/apps' make[6]: Nothing to be done for `check'. make[6]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/64x64/apps' make[6]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/64x64' make[6]: Nothing to be done for `check-am'. make[6]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/64x64' make[5]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/64x64' Making check in 128x128 make[5]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/128x128' Making check in apps make[6]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/128x128/apps' make[6]: Nothing to be done for `check'. make[6]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/128x128/apps' make[6]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/128x128' make[6]: Nothing to be done for `check-am'. make[6]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/128x128' make[5]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/128x128' make[5]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor' make[5]: Nothing to be done for `check-am'. make[5]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor' make[4]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor' make[4]: Entering directory `/build/buildd/docky-2.1.2/data/icons' make[4]: Nothing to be done for `check-am'. make[4]: Leaving directory `/build/buildd/docky-2.1.2/data/icons' make[3]: Leaving directory `/build/buildd/docky-2.1.2/data/icons' Making check in themes make[3]: Entering directory `/build/buildd/docky-2.1.2/data/themes' Making check in Grayscale make[4]: Entering directory `/build/buildd/docky-2.1.2/data/themes/Grayscale' make[4]: Nothing to be done for `check'. make[4]: Leaving directory `/build/buildd/docky-2.1.2/data/themes/Grayscale' Making check in Air make[4]: Entering directory `/build/buildd/docky-2.1.2/data/themes/Air' make[4]: Nothing to be done for `check'. make[4]: Leaving directory `/build/buildd/docky-2.1.2/data/themes/Air' Making check in Glass make[4]: Entering directory `/build/buildd/docky-2.1.2/data/themes/Glass' make[4]: Nothing to be done for `check'. make[4]: Leaving directory `/build/buildd/docky-2.1.2/data/themes/Glass' Making check in HUD make[4]: Entering directory `/build/buildd/docky-2.1.2/data/themes/HUD' make[4]: Nothing to be done for `check'. make[4]: Leaving directory `/build/buildd/docky-2.1.2/data/themes/HUD' Making check in Matte make[4]: Entering directory `/build/buildd/docky-2.1.2/data/themes/Matte' make[4]: Nothing to be done for `check'. make[4]: Leaving directory `/build/buildd/docky-2.1.2/data/themes/Matte' Making check in Smoke make[4]: Entering directory `/build/buildd/docky-2.1.2/data/themes/Smoke' make[4]: Nothing to be done for `check'. make[4]: Leaving directory `/build/buildd/docky-2.1.2/data/themes/Smoke' Making check in Transparent make[4]: Entering directory `/build/buildd/docky-2.1.2/data/themes/Transparent' make[4]: Nothing to be done for `check'. make[4]: Leaving directory `/build/buildd/docky-2.1.2/data/themes/Transparent' make[4]: Entering directory `/build/buildd/docky-2.1.2/data/themes' make[4]: Nothing to be done for `check-am'. make[4]: Leaving directory `/build/buildd/docky-2.1.2/data/themes' make[3]: Leaving directory `/build/buildd/docky-2.1.2/data/themes' make[3]: Entering directory `/build/buildd/docky-2.1.2/data' make[3]: Nothing to be done for `check-am'. make[3]: Leaving directory `/build/buildd/docky-2.1.2/data' make[2]: Leaving directory `/build/buildd/docky-2.1.2/data' Making check in po make[2]: Entering directory `/build/buildd/docky-2.1.2/po' INTLTOOL_EXTRACT=/usr/bin/intltool-extract srcdir=. /usr/bin/intltool-update --gettext-package docky --pot rm -f missing notexist srcdir=. /usr/bin/intltool-update -m mismatched quotes at line 245 in ../Docky.Services/Docky.Services/WindowMatcherService.cs if [ -r missing -o -r notexist ]; then \ exit 1; \ fi make[2]: Leaving directory `/build/buildd/docky-2.1.2/po' Making check in Docky.CairoHelper make[2]: Entering directory `/build/buildd/docky-2.1.2/Docky.CairoHelper' make[2]: Nothing to be done for `check'. make[2]: Leaving directory `/build/buildd/docky-2.1.2/Docky.CairoHelper' Making check in Docky.Services make[2]: Entering directory `/build/buildd/docky-2.1.2/Docky.Services' make[2]: Nothing to be done for `check'. make[2]: Leaving directory `/build/buildd/docky-2.1.2/Docky.Services' Making check in Docky.Widgets make[2]: Entering directory `/build/buildd/docky-2.1.2/Docky.Widgets' make[2]: Nothing to be done for `check'. make[2]: Leaving directory `/build/buildd/docky-2.1.2/Docky.Widgets' Making check in Docky.Items make[2]: Entering directory `/build/buildd/docky-2.1.2/Docky.Items' make[2]: Nothing to be done for `check'. make[2]: Leaving directory `/build/buildd/docky-2.1.2/Docky.Items' Making check in Docky.DBus make[2]: Entering directory `/build/buildd/docky-2.1.2/Docky.DBus' make[2]: Nothing to be done for `check'. make[2]: Leaving directory `/build/buildd/docky-2.1.2/Docky.DBus' Making check in StandardPlugins make[2]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins' Making check in BatteryMonitor make[3]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/BatteryMonitor' make[3]: Nothing to be done for `check'. make[3]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/BatteryMonitor' Making check in Bookmarks make[3]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/Bookmarks' make[3]: Nothing to be done for `check'. make[3]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/Bookmarks' Making check in Clippy make[3]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/Clippy' make[3]: Nothing to be done for `check'. make[3]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/Clippy' Making check in Clock make[3]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/Clock' Making check in Themes make[4]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/Clock/Themes' Making check in Default make[5]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/Clock/Themes/Default' make[5]: Nothing to be done for `check'. make[5]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/Clock/Themes/Default' Making check in Default24 make[5]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/Clock/Themes/Default24' make[5]: Nothing to be done for `check'. make[5]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/Clock/Themes/Default24' make[5]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/Clock/Themes' make[5]: Nothing to be done for `check-am'. make[5]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/Clock/Themes' make[4]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/Clock/Themes' make[4]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/Clock' make[4]: Nothing to be done for `check-am'. make[4]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/Clock' make[3]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/Clock' Making check in Desktop make[3]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/Desktop' make[3]: Nothing to be done for `check'. make[3]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/Desktop' Making check in CPUMonitor make[3]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/CPUMonitor' make[3]: Nothing to be done for `check'. make[3]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/CPUMonitor' Making check in GMail make[3]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/GMail' make[3]: Nothing to be done for `check'. make[3]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/GMail' Making check in Mounter make[3]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/Mounter' make[3]: Nothing to be done for `check'. make[3]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/Mounter' Making check in NetworkManager make[3]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/NetworkManager' make[3]: Nothing to be done for `check'. make[3]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/NetworkManager' Making check in NPR make[3]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/NPR' make[3]: Nothing to be done for `check'. make[3]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/NPR' Making check in RecentDocuments make[3]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/RecentDocuments' make[3]: Nothing to be done for `check'. make[3]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/RecentDocuments' Making check in SessionManager make[3]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/SessionManager' make[3]: Nothing to be done for `check'. make[3]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/SessionManager' Making check in Timer make[3]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/Timer' make[3]: Nothing to be done for `check'. make[3]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/Timer' Making check in Trash make[3]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/Trash' make[3]: Nothing to be done for `check'. make[3]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/Trash' Making check in Weather make[3]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/Weather' make[3]: Nothing to be done for `check'. make[3]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/Weather' Making check in WorkspaceSwitcher make[3]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/WorkspaceSwitcher' make[3]: Nothing to be done for `check'. make[3]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/WorkspaceSwitcher' make[3]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins' make[3]: Nothing to be done for `check-am'. make[3]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins' make[2]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins' Making check in Docky make[2]: Entering directory `/build/buildd/docky-2.1.2/Docky' make[2]: Nothing to be done for `check'. make[2]: Leaving directory `/build/buildd/docky-2.1.2/Docky' Making check in man make[2]: Entering directory `/build/buildd/docky-2.1.2/man' make[2]: Nothing to be done for `check'. make[2]: Leaving directory `/build/buildd/docky-2.1.2/man' Making check in m4 make[2]: Entering directory `/build/buildd/docky-2.1.2/m4' make[2]: Nothing to be done for `check'. make[2]: Leaving directory `/build/buildd/docky-2.1.2/m4' make[1]: Leaving directory `/build/buildd/docky-2.1.2' /usr/bin/fakeroot debian/rules binary dh binary dh_testroot dh_prep Unknown option: with dh_prep: warning: ignored unknown options in DH_OPTIONS dh_installdirs Unknown option: with dh_installdirs: warning: ignored unknown options in DH_OPTIONS dh_auto_install Unknown option: with dh_auto_install: warning: ignored unknown options in DH_OPTIONS make[1]: Entering directory `/build/buildd/docky-2.1.2' Making install in . make[2]: Entering directory `/build/buildd/docky-2.1.2' make[3]: Entering directory `/build/buildd/docky-2.1.2' make[3]: Nothing to be done for `install-exec-am'. test -z "/usr/lib/docky" || /bin/mkdir -p "/build/buildd/docky-2.1.2/debian/docky/usr/lib/docky" /usr/bin/install -c -m 644 /build/buildd/docky-2.1.2//build/gio-sharp.dll /build/buildd/docky-2.1.2//build/gio-sharp.dll.config '/build/buildd/docky-2.1.2/debian/docky/usr/lib/docky' make[3]: Leaving directory `/build/buildd/docky-2.1.2' make[2]: Leaving directory `/build/buildd/docky-2.1.2' Making install in data make[2]: Entering directory `/build/buildd/docky-2.1.2/data' Making install in icons make[3]: Entering directory `/build/buildd/docky-2.1.2/data/icons' Making install in hicolor make[4]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor' Making install in 16x16 make[5]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/16x16' Making install in apps make[6]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/16x16/apps' make[7]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/16x16/apps' make[7]: Nothing to be done for `install-exec-am'. test -z "/usr/share/icons/hicolor/16x16/apps" || /bin/mkdir -p "/build/buildd/docky-2.1.2/debian/docky/usr/share/icons/hicolor/16x16/apps" /usr/bin/install -c -m 644 docky.svg '/build/buildd/docky-2.1.2/debian/docky/usr/share/icons/hicolor/16x16/apps' make[7]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/16x16/apps' make[6]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/16x16/apps' make[6]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/16x16' make[7]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/16x16' make[7]: Nothing to be done for `install-exec-am'. make[7]: Nothing to be done for `install-data-am'. make[7]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/16x16' make[6]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/16x16' make[5]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/16x16' Making install in 22x22 make[5]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/22x22' Making install in apps make[6]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/22x22/apps' make[7]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/22x22/apps' make[7]: Nothing to be done for `install-exec-am'. test -z "/usr/share/icons/hicolor/22x22/apps" || /bin/mkdir -p "/build/buildd/docky-2.1.2/debian/docky/usr/share/icons/hicolor/22x22/apps" /usr/bin/install -c -m 644 docky.svg '/build/buildd/docky-2.1.2/debian/docky/usr/share/icons/hicolor/22x22/apps' make[7]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/22x22/apps' make[6]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/22x22/apps' make[6]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/22x22' make[7]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/22x22' make[7]: Nothing to be done for `install-exec-am'. make[7]: Nothing to be done for `install-data-am'. make[7]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/22x22' make[6]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/22x22' make[5]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/22x22' Making install in 24x24 make[5]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/24x24' Making install in apps make[6]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/24x24/apps' make[7]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/24x24/apps' make[7]: Nothing to be done for `install-exec-am'. test -z "/usr/share/icons/hicolor/24x24/apps" || /bin/mkdir -p "/build/buildd/docky-2.1.2/debian/docky/usr/share/icons/hicolor/24x24/apps" /usr/bin/install -c -m 644 docky.svg '/build/buildd/docky-2.1.2/debian/docky/usr/share/icons/hicolor/24x24/apps' make[7]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/24x24/apps' make[6]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/24x24/apps' make[6]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/24x24' make[7]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/24x24' make[7]: Nothing to be done for `install-exec-am'. make[7]: Nothing to be done for `install-data-am'. make[7]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/24x24' make[6]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/24x24' make[5]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/24x24' Making install in 32x32 make[5]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/32x32' Making install in apps make[6]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/32x32/apps' make[7]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/32x32/apps' make[7]: Nothing to be done for `install-exec-am'. test -z "/usr/share/icons/hicolor/32x32/apps" || /bin/mkdir -p "/build/buildd/docky-2.1.2/debian/docky/usr/share/icons/hicolor/32x32/apps" /usr/bin/install -c -m 644 docky.svg '/build/buildd/docky-2.1.2/debian/docky/usr/share/icons/hicolor/32x32/apps' make[7]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/32x32/apps' make[6]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/32x32/apps' make[6]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/32x32' make[7]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/32x32' make[7]: Nothing to be done for `install-exec-am'. make[7]: Nothing to be done for `install-data-am'. make[7]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/32x32' make[6]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/32x32' make[5]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/32x32' Making install in 48x48 make[5]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/48x48' Making install in apps make[6]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/48x48/apps' make[7]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/48x48/apps' make[7]: Nothing to be done for `install-exec-am'. test -z "/usr/share/icons/hicolor/48x48/apps" || /bin/mkdir -p "/build/buildd/docky-2.1.2/debian/docky/usr/share/icons/hicolor/48x48/apps" /usr/bin/install -c -m 644 docky.svg '/build/buildd/docky-2.1.2/debian/docky/usr/share/icons/hicolor/48x48/apps' make[7]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/48x48/apps' make[6]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/48x48/apps' Making install in mimetypes make[6]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/48x48/mimetypes' make[7]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/48x48/mimetypes' make[7]: Nothing to be done for `install-exec-am'. test -z "/usr/share/icons/hicolor/48x48/mimetypes" || /bin/mkdir -p "/build/buildd/docky-2.1.2/debian/docky/usr/share/icons/hicolor/48x48/mimetypes" /usr/bin/install -c -m 644 extension.svg '/build/buildd/docky-2.1.2/debian/docky/usr/share/icons/hicolor/48x48/mimetypes' make[7]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/48x48/mimetypes' make[6]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/48x48/mimetypes' make[6]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/48x48' make[7]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/48x48' make[7]: Nothing to be done for `install-exec-am'. make[7]: Nothing to be done for `install-data-am'. make[7]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/48x48' make[6]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/48x48' make[5]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/48x48' Making install in 64x64 make[5]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/64x64' Making install in apps make[6]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/64x64/apps' make[7]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/64x64/apps' make[7]: Nothing to be done for `install-exec-am'. test -z "/usr/share/icons/hicolor/64x64/apps" || /bin/mkdir -p "/build/buildd/docky-2.1.2/debian/docky/usr/share/icons/hicolor/64x64/apps" /usr/bin/install -c -m 644 docky.svg '/build/buildd/docky-2.1.2/debian/docky/usr/share/icons/hicolor/64x64/apps' make[7]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/64x64/apps' make[6]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/64x64/apps' make[6]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/64x64' make[7]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/64x64' make[7]: Nothing to be done for `install-exec-am'. make[7]: Nothing to be done for `install-data-am'. make[7]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/64x64' make[6]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/64x64' make[5]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/64x64' Making install in 128x128 make[5]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/128x128' Making install in apps make[6]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/128x128/apps' make[7]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/128x128/apps' make[7]: Nothing to be done for `install-exec-am'. test -z "/usr/share/icons/hicolor/128x128/apps" || /bin/mkdir -p "/build/buildd/docky-2.1.2/debian/docky/usr/share/icons/hicolor/128x128/apps" /usr/bin/install -c -m 644 docky.svg gmail.png '/build/buildd/docky-2.1.2/debian/docky/usr/share/icons/hicolor/128x128/apps' make[7]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/128x128/apps' make[6]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/128x128/apps' make[6]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/128x128' make[7]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor/128x128' make[7]: Nothing to be done for `install-exec-am'. make[7]: Nothing to be done for `install-data-am'. make[7]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/128x128' make[6]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/128x128' make[5]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor/128x128' make[5]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor' make[6]: Entering directory `/build/buildd/docky-2.1.2/data/icons/hicolor' make[6]: Nothing to be done for `install-exec-am'. make[6]: Nothing to be done for `install-data-am'. make[6]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor' make[5]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor' make[4]: Leaving directory `/build/buildd/docky-2.1.2/data/icons/hicolor' make[4]: Entering directory `/build/buildd/docky-2.1.2/data/icons' make[5]: Entering directory `/build/buildd/docky-2.1.2/data/icons' make[5]: Nothing to be done for `install-exec-am'. make[5]: Nothing to be done for `install-data-am'. make[5]: Leaving directory `/build/buildd/docky-2.1.2/data/icons' make[4]: Leaving directory `/build/buildd/docky-2.1.2/data/icons' make[3]: Leaving directory `/build/buildd/docky-2.1.2/data/icons' Making install in themes make[3]: Entering directory `/build/buildd/docky-2.1.2/data/themes' Making install in Grayscale make[4]: Entering directory `/build/buildd/docky-2.1.2/data/themes/Grayscale' make[5]: Entering directory `/build/buildd/docky-2.1.2/data/themes/Grayscale' make[5]: Nothing to be done for `install-exec-am'. test -z "/usr/share/docky/themes/Grayscale" || /bin/mkdir -p "/build/buildd/docky-2.1.2/debian/docky/usr/share/docky/themes/Grayscale" /usr/bin/install -c -m 644 background.svg badge.svg menu.svg tooltip.svg '/build/buildd/docky-2.1.2/debian/docky/usr/share/docky/themes/Grayscale' make[5]: Leaving directory `/build/buildd/docky-2.1.2/data/themes/Grayscale' make[4]: Leaving directory `/build/buildd/docky-2.1.2/data/themes/Grayscale' Making install in Air make[4]: Entering directory `/build/buildd/docky-2.1.2/data/themes/Air' make[5]: Entering directory `/build/buildd/docky-2.1.2/data/themes/Air' make[5]: Nothing to be done for `install-exec-am'. test -z "/usr/share/docky/themes/Air" || /bin/mkdir -p "/build/buildd/docky-2.1.2/debian/docky/usr/share/docky/themes/Air" /usr/bin/install -c -m 644 background.svg badge.svg menu.svg stretch_separator.svg tooltip.svg '/build/buildd/docky-2.1.2/debian/docky/usr/share/docky/themes/Air' make[5]: Leaving directory `/build/buildd/docky-2.1.2/data/themes/Air' make[4]: Leaving directory `/build/buildd/docky-2.1.2/data/themes/Air' Making install in Glass make[4]: Entering directory `/build/buildd/docky-2.1.2/data/themes/Glass' make[5]: Entering directory `/build/buildd/docky-2.1.2/data/themes/Glass' make[5]: Nothing to be done for `install-exec-am'. test -z "/usr/share/docky/themes/Glass" || /bin/mkdir -p "/build/buildd/docky-2.1.2/debian/docky/usr/share/docky/themes/Glass" /usr/bin/install -c -m 644 background.svg badge.svg menu.svg stretch_separator.svg tooltip.svg '/build/buildd/docky-2.1.2/debian/docky/usr/share/docky/themes/Glass' make[5]: Leaving directory `/build/buildd/docky-2.1.2/data/themes/Glass' make[4]: Leaving directory `/build/buildd/docky-2.1.2/data/themes/Glass' Making install in HUD make[4]: Entering directory `/build/buildd/docky-2.1.2/data/themes/HUD' make[5]: Entering directory `/build/buildd/docky-2.1.2/data/themes/HUD' make[5]: Nothing to be done for `install-exec-am'. test -z "/usr/share/docky/themes/HUD" || /bin/mkdir -p "/build/buildd/docky-2.1.2/debian/docky/usr/share/docky/themes/HUD" /usr/bin/install -c -m 644 background.svg badge.svg menu.svg tooltip.svg '/build/buildd/docky-2.1.2/debian/docky/usr/share/docky/themes/HUD' make[5]: Leaving directory `/build/buildd/docky-2.1.2/data/themes/HUD' make[4]: Leaving directory `/build/buildd/docky-2.1.2/data/themes/HUD' Making install in Matte make[4]: Entering directory `/build/buildd/docky-2.1.2/data/themes/Matte' make[5]: Entering directory `/build/buildd/docky-2.1.2/data/themes/Matte' make[5]: Nothing to be done for `install-exec-am'. test -z "/usr/share/docky/themes/Matte" || /bin/mkdir -p "/build/buildd/docky-2.1.2/debian/docky/usr/share/docky/themes/Matte" /usr/bin/install -c -m 644 background.svg menu.svg tooltip.svg '/build/buildd/docky-2.1.2/debian/docky/usr/share/docky/themes/Matte' make[5]: Leaving directory `/build/buildd/docky-2.1.2/data/themes/Matte' make[4]: Leaving directory `/build/buildd/docky-2.1.2/data/themes/Matte' Making install in Smoke make[4]: Entering directory `/build/buildd/docky-2.1.2/data/themes/Smoke' make[5]: Entering directory `/build/buildd/docky-2.1.2/data/themes/Smoke' make[5]: Nothing to be done for `install-exec-am'. test -z "/usr/share/docky/themes/Smoke" || /bin/mkdir -p "/build/buildd/docky-2.1.2/debian/docky/usr/share/docky/themes/Smoke" /usr/bin/install -c -m 644 background.svg badge.svg menu.svg stretch_separator.svg tooltip.svg '/build/buildd/docky-2.1.2/debian/docky/usr/share/docky/themes/Smoke' make[5]: Leaving directory `/build/buildd/docky-2.1.2/data/themes/Smoke' make[4]: Leaving directory `/build/buildd/docky-2.1.2/data/themes/Smoke' Making install in Transparent make[4]: Entering directory `/build/buildd/docky-2.1.2/data/themes/Transparent' make[5]: Entering directory `/build/buildd/docky-2.1.2/data/themes/Transparent' make[5]: Nothing to be done for `install-exec-am'. test -z "/usr/share/docky/themes/Transparent" || /bin/mkdir -p "/build/buildd/docky-2.1.2/debian/docky/usr/share/docky/themes/Transparent" /usr/bin/install -c -m 644 background.svg '/build/buildd/docky-2.1.2/debian/docky/usr/share/docky/themes/Transparent' make[5]: Leaving directory `/build/buildd/docky-2.1.2/data/themes/Transparent' make[4]: Leaving directory `/build/buildd/docky-2.1.2/data/themes/Transparent' make[4]: Entering directory `/build/buildd/docky-2.1.2/data/themes' make[5]: Entering directory `/build/buildd/docky-2.1.2/data/themes' make[5]: Nothing to be done for `install-exec-am'. make[5]: Nothing to be done for `install-data-am'. make[5]: Leaving directory `/build/buildd/docky-2.1.2/data/themes' make[4]: Leaving directory `/build/buildd/docky-2.1.2/data/themes' make[3]: Leaving directory `/build/buildd/docky-2.1.2/data/themes' make[3]: Entering directory `/build/buildd/docky-2.1.2/data' make[4]: Entering directory `/build/buildd/docky-2.1.2/data' make[4]: Nothing to be done for `install-exec-am'. test -z "/usr/share/applications" || /bin/mkdir -p "/build/buildd/docky-2.1.2/debian/docky/usr/share/applications" /usr/bin/install -c -m 644 docky.desktop '/build/buildd/docky-2.1.2/debian/docky/usr/share/applications' GCONF_CONFIG_SOURCE=xml:merged:/etc/gconf/gconf.xml.defaults \ /usr/bin/gconftool-2 --makefile-install-rule docky.schemas (gconftool-2:21544): GConf-WARNING **: None of the resolved addresses are writable; saving configuration settings will not be possible Attached schema `/schemas/apps/docky-2/Clippy/ClippyItem/MaxEntries' to key `/apps/docky-2/Clippy/ClippyItem/MaxEntries' WARNING: failed to install schema `/schemas/apps/docky-2/Clippy/ClippyItem/MaxEntries', locale `lt': Unable to store a value at key '/schemas/apps/docky-2/Clippy/ClippyItem/MaxEntries', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clippy/ClippyItem/MaxEntries', locale `de': Unable to store a value at key '/schemas/apps/docky-2/Clippy/ClippyItem/MaxEntries', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clippy/ClippyItem/MaxEntries', locale `ro': Unable to store a value at key '/schemas/apps/docky-2/Clippy/ClippyItem/MaxEntries', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clippy/ClippyItem/MaxEntries', locale `pt': Unable to store a value at key '/schemas/apps/docky-2/Clippy/ClippyItem/MaxEntries', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clippy/ClippyItem/MaxEntries', locale `C': Unable to store a value at key '/schemas/apps/docky-2/Clippy/ClippyItem/MaxEntries', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clippy/ClippyItem/MaxEntries', locale `fi': Unable to store a value at key '/schemas/apps/docky-2/Clippy/ClippyItem/MaxEntries', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clippy/ClippyItem/MaxEntries', locale `sr': Unable to store a value at key '/schemas/apps/docky-2/Clippy/ClippyItem/MaxEntries', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clippy/ClippyItem/MaxEntries', locale `ru': Unable to store a value at key '/schemas/apps/docky-2/Clippy/ClippyItem/MaxEntries', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clippy/ClippyItem/MaxEntries', locale `tr': Unable to store a value at key '/schemas/apps/docky-2/Clippy/ClippyItem/MaxEntries', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clippy/ClippyItem/MaxEntries', locale `es': Unable to store a value at key '/schemas/apps/docky-2/Clippy/ClippyItem/MaxEntries', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clippy/ClippyItem/MaxEntries', locale `fr': Unable to store a value at key '/schemas/apps/docky-2/Clippy/ClippyItem/MaxEntries', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clippy/ClippyItem/MaxEntries', locale `nl': Unable to store a value at key '/schemas/apps/docky-2/Clippy/ClippyItem/MaxEntries', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only 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/docky-2/Clippy/ClippyItem/TimerDelay' to key `/apps/docky-2/Clippy/ClippyItem/TimerDelay' WARNING: failed to install schema `/schemas/apps/docky-2/Clippy/ClippyItem/TimerDelay', locale `lt': Unable to store a value at key '/schemas/apps/docky-2/Clippy/ClippyItem/TimerDelay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clippy/ClippyItem/TimerDelay', locale `de': Unable to store a value at key '/schemas/apps/docky-2/Clippy/ClippyItem/TimerDelay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clippy/ClippyItem/TimerDelay', locale `sl': Unable to store a value at key '/schemas/apps/docky-2/Clippy/ClippyItem/TimerDelay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clippy/ClippyItem/TimerDelay', locale `ro': Unable to store a value at key '/schemas/apps/docky-2/Clippy/ClippyItem/TimerDelay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clippy/ClippyItem/TimerDelay', locale `pt': Unable to store a value at key '/schemas/apps/docky-2/Clippy/ClippyItem/TimerDelay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clippy/ClippyItem/TimerDelay', locale `C': Unable to store a value at key '/schemas/apps/docky-2/Clippy/ClippyItem/TimerDelay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clippy/ClippyItem/TimerDelay', locale `fi': Unable to store a value at key '/schemas/apps/docky-2/Clippy/ClippyItem/TimerDelay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clippy/ClippyItem/TimerDelay', locale `sr': Unable to store a value at key '/schemas/apps/docky-2/Clippy/ClippyItem/TimerDelay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clippy/ClippyItem/TimerDelay', locale `ru': Unable to store a value at key '/schemas/apps/docky-2/Clippy/ClippyItem/TimerDelay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clippy/ClippyItem/TimerDelay', locale `tr': Unable to store a value at key '/schemas/apps/docky-2/Clippy/ClippyItem/TimerDelay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clippy/ClippyItem/TimerDelay', locale `es': Unable to store a value at key '/schemas/apps/docky-2/Clippy/ClippyItem/TimerDelay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clippy/ClippyItem/TimerDelay', locale `fr': Unable to store a value at key '/schemas/apps/docky-2/Clippy/ClippyItem/TimerDelay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only 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/docky-2/Clippy/ClippyItem/TrackMouseSelections' to key `/apps/docky-2/Clippy/ClippyItem/TrackMouseSelections' WARNING: failed to install schema `/schemas/apps/docky-2/Clippy/ClippyItem/TrackMouseSelections', locale `lt': Unable to store a value at key '/schemas/apps/docky-2/Clippy/ClippyItem/TrackMouseSelections', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clippy/ClippyItem/TrackMouseSelections', locale `de': Unable to store a value at key '/schemas/apps/docky-2/Clippy/ClippyItem/TrackMouseSelections', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clippy/ClippyItem/TrackMouseSelections', locale `ro': Unable to store a value at key '/schemas/apps/docky-2/Clippy/ClippyItem/TrackMouseSelections', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clippy/ClippyItem/TrackMouseSelections', locale `pt': Unable to store a value at key '/schemas/apps/docky-2/Clippy/ClippyItem/TrackMouseSelections', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clippy/ClippyItem/TrackMouseSelections', locale `C': Unable to store a value at key '/schemas/apps/docky-2/Clippy/ClippyItem/TrackMouseSelections', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clippy/ClippyItem/TrackMouseSelections', locale `cs': Unable to store a value at key '/schemas/apps/docky-2/Clippy/ClippyItem/TrackMouseSelections', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clippy/ClippyItem/TrackMouseSelections', locale `sr': Unable to store a value at key '/schemas/apps/docky-2/Clippy/ClippyItem/TrackMouseSelections', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clippy/ClippyItem/TrackMouseSelections', locale `tr': Unable to store a value at key '/schemas/apps/docky-2/Clippy/ClippyItem/TrackMouseSelections', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clippy/ClippyItem/TrackMouseSelections', locale `es': Unable to store a value at key '/schemas/apps/docky-2/Clippy/ClippyItem/TrackMouseSelections', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only 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/docky-2/Clock/ClockDockItem/ClockTheme' to key `/apps/docky-2/Clock/ClockDockItem/ClockTheme' WARNING: failed to install schema `/schemas/apps/docky-2/Clock/ClockDockItem/ClockTheme', locale `de': Unable to store a value at key '/schemas/apps/docky-2/Clock/ClockDockItem/ClockTheme', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clock/ClockDockItem/ClockTheme', locale `lt': Unable to store a value at key '/schemas/apps/docky-2/Clock/ClockDockItem/ClockTheme', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clock/ClockDockItem/ClockTheme', locale `sl': Unable to store a value at key '/schemas/apps/docky-2/Clock/ClockDockItem/ClockTheme', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clock/ClockDockItem/ClockTheme', locale `ro': Unable to store a value at key '/schemas/apps/docky-2/Clock/ClockDockItem/ClockTheme', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clock/ClockDockItem/ClockTheme', locale `fi': Unable to store a value at key '/schemas/apps/docky-2/Clock/ClockDockItem/ClockTheme', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clock/ClockDockItem/ClockTheme', locale `C': Unable to store a value at key '/schemas/apps/docky-2/Clock/ClockDockItem/ClockTheme', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clock/ClockDockItem/ClockTheme', locale `uk': Unable to store a value at key '/schemas/apps/docky-2/Clock/ClockDockItem/ClockTheme', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clock/ClockDockItem/ClockTheme', locale `pt': Unable to store a value at key '/schemas/apps/docky-2/Clock/ClockDockItem/ClockTheme', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clock/ClockDockItem/ClockTheme', locale `cs': Unable to store a value at key '/schemas/apps/docky-2/Clock/ClockDockItem/ClockTheme', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clock/ClockDockItem/ClockTheme', locale `ru': Unable to store a value at key '/schemas/apps/docky-2/Clock/ClockDockItem/ClockTheme', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clock/ClockDockItem/ClockTheme', locale `tr': Unable to store a value at key '/schemas/apps/docky-2/Clock/ClockDockItem/ClockTheme', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clock/ClockDockItem/ClockTheme', locale `sr': Unable to store a value at key '/schemas/apps/docky-2/Clock/ClockDockItem/ClockTheme', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clock/ClockDockItem/ClockTheme', locale `es': Unable to store a value at key '/schemas/apps/docky-2/Clock/ClockDockItem/ClockTheme', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clock/ClockDockItem/ClockTheme', locale `fr': Unable to store a value at key '/schemas/apps/docky-2/Clock/ClockDockItem/ClockTheme', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clock/ClockDockItem/ClockTheme', locale `eu': Unable to store a value at key '/schemas/apps/docky-2/Clock/ClockDockItem/ClockTheme', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clock/ClockDockItem/ClockTheme', locale `zh_TW': Unable to store a value at key '/schemas/apps/docky-2/Clock/ClockDockItem/ClockTheme', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clock/ClockDockItem/ClockTheme', locale `ko': Unable to store a value at key '/schemas/apps/docky-2/Clock/ClockDockItem/ClockTheme', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only 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/docky-2/Clock/ClockDockItem/ShowDate' to key `/apps/docky-2/Clock/ClockDockItem/ShowDate' WARNING: failed to install schema `/schemas/apps/docky-2/Clock/ClockDockItem/ShowDate', locale `lt': Unable to store a value at key '/schemas/apps/docky-2/Clock/ClockDockItem/ShowDate', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clock/ClockDockItem/ShowDate', locale `de': Unable to store a value at key '/schemas/apps/docky-2/Clock/ClockDockItem/ShowDate', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clock/ClockDockItem/ShowDate', locale `ro': Unable to store a value at key '/schemas/apps/docky-2/Clock/ClockDockItem/ShowDate', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clock/ClockDockItem/ShowDate', locale `pt': Unable to store a value at key '/schemas/apps/docky-2/Clock/ClockDockItem/ShowDate', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clock/ClockDockItem/ShowDate', locale `C': Unable to store a value at key '/schemas/apps/docky-2/Clock/ClockDockItem/ShowDate', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clock/ClockDockItem/ShowDate', locale `fi': Unable to store a value at key '/schemas/apps/docky-2/Clock/ClockDockItem/ShowDate', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clock/ClockDockItem/ShowDate', locale `sr': Unable to store a value at key '/schemas/apps/docky-2/Clock/ClockDockItem/ShowDate', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clock/ClockDockItem/ShowDate', locale `ru': Unable to store a value at key '/schemas/apps/docky-2/Clock/ClockDockItem/ShowDate', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clock/ClockDockItem/ShowDate', locale `tr': Unable to store a value at key '/schemas/apps/docky-2/Clock/ClockDockItem/ShowDate', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clock/ClockDockItem/ShowDate', locale `es': Unable to store a value at key '/schemas/apps/docky-2/Clock/ClockDockItem/ShowDate', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clock/ClockDockItem/ShowDate', locale `fr': Unable to store a value at key '/schemas/apps/docky-2/Clock/ClockDockItem/ShowDate', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only 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/docky-2/Clock/ClockDockItem/ShowDigital' to key `/apps/docky-2/Clock/ClockDockItem/ShowDigital' WARNING: failed to install schema `/schemas/apps/docky-2/Clock/ClockDockItem/ShowDigital', locale `lt': Unable to store a value at key '/schemas/apps/docky-2/Clock/ClockDockItem/ShowDigital', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clock/ClockDockItem/ShowDigital', locale `de': Unable to store a value at key '/schemas/apps/docky-2/Clock/ClockDockItem/ShowDigital', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clock/ClockDockItem/ShowDigital', locale `ro': Unable to store a value at key '/schemas/apps/docky-2/Clock/ClockDockItem/ShowDigital', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clock/ClockDockItem/ShowDigital', locale `fi': Unable to store a value at key '/schemas/apps/docky-2/Clock/ClockDockItem/ShowDigital', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clock/ClockDockItem/ShowDigital', locale `C': Unable to store a value at key '/schemas/apps/docky-2/Clock/ClockDockItem/ShowDigital', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clock/ClockDockItem/ShowDigital', locale `pt': Unable to store a value at key '/schemas/apps/docky-2/Clock/ClockDockItem/ShowDigital', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clock/ClockDockItem/ShowDigital', locale `cs': Unable to store a value at key '/schemas/apps/docky-2/Clock/ClockDockItem/ShowDigital', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clock/ClockDockItem/ShowDigital', locale `ru': Unable to store a value at key '/schemas/apps/docky-2/Clock/ClockDockItem/ShowDigital', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clock/ClockDockItem/ShowDigital', locale `tr': Unable to store a value at key '/schemas/apps/docky-2/Clock/ClockDockItem/ShowDigital', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clock/ClockDockItem/ShowDigital', locale `sr': Unable to store a value at key '/schemas/apps/docky-2/Clock/ClockDockItem/ShowDigital', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clock/ClockDockItem/ShowDigital', locale `es': Unable to store a value at key '/schemas/apps/docky-2/Clock/ClockDockItem/ShowDigital', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clock/ClockDockItem/ShowDigital', locale `fr': Unable to store a value at key '/schemas/apps/docky-2/Clock/ClockDockItem/ShowDigital', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only 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/docky-2/Clock/ClockDockItem/ShowMilitary' to key `/apps/docky-2/Clock/ClockDockItem/ShowMilitary' WARNING: failed to install schema `/schemas/apps/docky-2/Clock/ClockDockItem/ShowMilitary', locale `lt': Unable to store a value at key '/schemas/apps/docky-2/Clock/ClockDockItem/ShowMilitary', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clock/ClockDockItem/ShowMilitary', locale `de': Unable to store a value at key '/schemas/apps/docky-2/Clock/ClockDockItem/ShowMilitary', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clock/ClockDockItem/ShowMilitary', locale `ro': Unable to store a value at key '/schemas/apps/docky-2/Clock/ClockDockItem/ShowMilitary', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clock/ClockDockItem/ShowMilitary', locale `fi': Unable to store a value at key '/schemas/apps/docky-2/Clock/ClockDockItem/ShowMilitary', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clock/ClockDockItem/ShowMilitary', locale `C': Unable to store a value at key '/schemas/apps/docky-2/Clock/ClockDockItem/ShowMilitary', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clock/ClockDockItem/ShowMilitary', locale `pt': Unable to store a value at key '/schemas/apps/docky-2/Clock/ClockDockItem/ShowMilitary', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clock/ClockDockItem/ShowMilitary', locale `cs': Unable to store a value at key '/schemas/apps/docky-2/Clock/ClockDockItem/ShowMilitary', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clock/ClockDockItem/ShowMilitary', locale `ru': Unable to store a value at key '/schemas/apps/docky-2/Clock/ClockDockItem/ShowMilitary', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clock/ClockDockItem/ShowMilitary', locale `tr': Unable to store a value at key '/schemas/apps/docky-2/Clock/ClockDockItem/ShowMilitary', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clock/ClockDockItem/ShowMilitary', locale `sr': Unable to store a value at key '/schemas/apps/docky-2/Clock/ClockDockItem/ShowMilitary', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clock/ClockDockItem/ShowMilitary', locale `es': Unable to store a value at key '/schemas/apps/docky-2/Clock/ClockDockItem/ShowMilitary', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Clock/ClockDockItem/ShowMilitary', locale `fr': Unable to store a value at key '/schemas/apps/docky-2/Clock/ClockDockItem/ShowMilitary', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only 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/docky-2/Docky/DockController/ActiveDocks' to key `/apps/docky-2/Docky/DockController/ActiveDocks' WARNING: failed to install schema `/schemas/apps/docky-2/Docky/DockController/ActiveDocks', locale `lt': Unable to store a value at key '/schemas/apps/docky-2/Docky/DockController/ActiveDocks', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/DockController/ActiveDocks', locale `de': Unable to store a value at key '/schemas/apps/docky-2/Docky/DockController/ActiveDocks', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/DockController/ActiveDocks', locale `ro': Unable to store a value at key '/schemas/apps/docky-2/Docky/DockController/ActiveDocks', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/DockController/ActiveDocks', locale `C': Unable to store a value at key '/schemas/apps/docky-2/Docky/DockController/ActiveDocks', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/DockController/ActiveDocks', locale `cs': Unable to store a value at key '/schemas/apps/docky-2/Docky/DockController/ActiveDocks', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/DockController/ActiveDocks', locale `ru': Unable to store a value at key '/schemas/apps/docky-2/Docky/DockController/ActiveDocks', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/DockController/ActiveDocks', locale `tr': Unable to store a value at key '/schemas/apps/docky-2/Docky/DockController/ActiveDocks', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/DockController/ActiveDocks', locale `sr': Unable to store a value at key '/schemas/apps/docky-2/Docky/DockController/ActiveDocks', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/DockController/ActiveDocks', locale `es': Unable to store a value at key '/schemas/apps/docky-2/Docky/DockController/ActiveDocks', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/DockController/ActiveDocks', locale `fr': Unable to store a value at key '/schemas/apps/docky-2/Docky/DockController/ActiveDocks', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only 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/docky-2/Docky/Interface/AutohideManager/UnhideDelay' to key `/apps/docky-2/Docky/Interface/AutohideManager/UnhideDelay' WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/AutohideManager/UnhideDelay', locale `lt': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/AutohideManager/UnhideDelay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/AutohideManager/UnhideDelay', locale `de': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/AutohideManager/UnhideDelay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/AutohideManager/UnhideDelay', locale `ro': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/AutohideManager/UnhideDelay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/AutohideManager/UnhideDelay', locale `pt': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/AutohideManager/UnhideDelay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/AutohideManager/UnhideDelay', locale `C': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/AutohideManager/UnhideDelay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/AutohideManager/UnhideDelay', locale `uk': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/AutohideManager/UnhideDelay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/AutohideManager/UnhideDelay', locale `cs': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/AutohideManager/UnhideDelay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/AutohideManager/UnhideDelay', locale `ru': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/AutohideManager/UnhideDelay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/AutohideManager/UnhideDelay', locale `tr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/AutohideManager/UnhideDelay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/AutohideManager/UnhideDelay', locale `sr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/AutohideManager/UnhideDelay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/AutohideManager/UnhideDelay', locale `es': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/AutohideManager/UnhideDelay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/AutohideManager/UnhideDelay', locale `fr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/AutohideManager/UnhideDelay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/AutohideManager/UnhideDelay', locale `ko': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/AutohideManager/UnhideDelay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only 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/docky-2/Docky/Interface/AutohideManager/UpdateDelay' to key `/apps/docky-2/Docky/Interface/AutohideManager/UpdateDelay' WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/AutohideManager/UpdateDelay', locale `de': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/AutohideManager/UpdateDelay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/AutohideManager/UpdateDelay', locale `ro': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/AutohideManager/UpdateDelay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/AutohideManager/UpdateDelay', locale `pt': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/AutohideManager/UpdateDelay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/AutohideManager/UpdateDelay', locale `C': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/AutohideManager/UpdateDelay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/AutohideManager/UpdateDelay', locale `sr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/AutohideManager/UpdateDelay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/AutohideManager/UpdateDelay', locale `ru': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/AutohideManager/UpdateDelay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/AutohideManager/UpdateDelay', locale `tr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/AutohideManager/UpdateDelay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/AutohideManager/UpdateDelay', locale `es': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/AutohideManager/UpdateDelay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/AutohideManager/UpdateDelay', locale `fr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/AutohideManager/UpdateDelay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only 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/docky-2/Docky/Interface/DockDragTracker/LockDrags' to key `/apps/docky-2/Docky/Interface/DockDragTracker/LockDrags' WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockDragTracker/LockDrags', locale `lt': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockDragTracker/LockDrags', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockDragTracker/LockDrags', locale `de': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockDragTracker/LockDrags', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockDragTracker/LockDrags', locale `ro': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockDragTracker/LockDrags', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockDragTracker/LockDrags', locale `pt': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockDragTracker/LockDrags', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockDragTracker/LockDrags', locale `C': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockDragTracker/LockDrags', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockDragTracker/LockDrags', locale `cs': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockDragTracker/LockDrags', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockDragTracker/LockDrags', locale `ru': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockDragTracker/LockDrags', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockDragTracker/LockDrags', locale `tr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockDragTracker/LockDrags', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockDragTracker/LockDrags', locale `sr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockDragTracker/LockDrags', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockDragTracker/LockDrags', locale `es': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockDragTracker/LockDrags', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only 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/docky-2/Docky/Interface/DockDragTracker/ProvidersAcceptDrops' to key `/apps/docky-2/Docky/Interface/DockDragTracker/ProvidersAcceptDrops' WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockDragTracker/ProvidersAcceptDrops', locale `ru': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockDragTracker/ProvidersAcceptDrops', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockDragTracker/ProvidersAcceptDrops', locale `C': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockDragTracker/ProvidersAcceptDrops', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockDragTracker/ProvidersAcceptDrops', locale `ro': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockDragTracker/ProvidersAcceptDrops', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockDragTracker/ProvidersAcceptDrops', locale `es': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockDragTracker/ProvidersAcceptDrops', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockDragTracker/ProvidersAcceptDrops', locale `pt': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockDragTracker/ProvidersAcceptDrops', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockDragTracker/ProvidersAcceptDrops', locale `de': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockDragTracker/ProvidersAcceptDrops', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockDragTracker/ProvidersAcceptDrops', locale `sr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockDragTracker/ProvidersAcceptDrops', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only 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/docky-2/Docky/Interface/DockPreferences/FirstRun' to key `/apps/docky-2/Docky/Interface/DockPreferences/FirstRun' WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/FirstRun', locale `de': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/FirstRun', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/FirstRun', locale `lt': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/FirstRun', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/FirstRun', locale `sl': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/FirstRun', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/FirstRun', locale `ro': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/FirstRun', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/FirstRun', locale `fi': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/FirstRun', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/FirstRun', locale `C': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/FirstRun', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/FirstRun', locale `ast': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/FirstRun', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/FirstRun', locale `pt': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/FirstRun', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/FirstRun', locale `cs': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/FirstRun', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/FirstRun', locale `ru': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/FirstRun', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/FirstRun', locale `tr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/FirstRun', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/FirstRun', locale `sr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/FirstRun', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/FirstRun', locale `es': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/FirstRun', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/FirstRun', locale `fr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/FirstRun', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/FirstRun', locale `eu': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/FirstRun', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/FirstRun', locale `uk': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/FirstRun', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/FirstRun', locale `kk': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/FirstRun', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/FirstRun', locale `zh_TW': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/FirstRun', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/FirstRun', locale `ko': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/FirstRun', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/FirstRun', locale `nl': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/FirstRun', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only 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/docky-2/Docky/Interface/DockPreferences/DockN/Autohide' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock6/Autohide' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Autohide' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock5/Autohide' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Autohide' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock4/Autohide' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Autohide' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock3/Autohide' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Autohide' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock2/Autohide' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Autohide' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock1/Autohide' WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Autohide', locale `de': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Autohide', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Autohide', locale `lt': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Autohide', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Autohide', locale `sl': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Autohide', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Autohide', locale `ro': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Autohide', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Autohide', locale `fi': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Autohide', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Autohide', locale `C': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Autohide', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Autohide', locale `uk': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Autohide', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Autohide', locale `pt': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Autohide', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Autohide', locale `cs': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Autohide', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Autohide', locale `ru': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Autohide', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Autohide', locale `tr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Autohide', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Autohide', locale `sr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Autohide', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Autohide', locale `es': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Autohide', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Autohide', locale `fr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Autohide', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Autohide', locale `eu': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Autohide', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Autohide', locale `zh_TW': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Autohide', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Autohide', locale `ko': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Autohide', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only 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/docky-2/Docky/Interface/DockPreferences/DockN/FadeOnHide' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock6/FadeOnHide' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/FadeOnHide' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock5/FadeOnHide' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/FadeOnHide' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock4/FadeOnHide' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/FadeOnHide' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock3/FadeOnHide' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/FadeOnHide' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock2/FadeOnHide' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/FadeOnHide' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock1/FadeOnHide' WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/FadeOnHide', locale `de': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/FadeOnHide', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/FadeOnHide', locale `lt': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/FadeOnHide', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/FadeOnHide', locale `ro': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/FadeOnHide', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/FadeOnHide', locale `fi': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/FadeOnHide', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/FadeOnHide', locale `C': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/FadeOnHide', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/FadeOnHide', locale `uk': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/FadeOnHide', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/FadeOnHide', locale `pt': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/FadeOnHide', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/FadeOnHide', locale `cs': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/FadeOnHide', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/FadeOnHide', locale `ru': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/FadeOnHide', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/FadeOnHide', locale `tr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/FadeOnHide', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/FadeOnHide', locale `sr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/FadeOnHide', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/FadeOnHide', locale `es': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/FadeOnHide', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/FadeOnHide', locale `fr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/FadeOnHide', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/FadeOnHide', locale `eu': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/FadeOnHide', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/FadeOnHide', locale `zh_TW': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/FadeOnHide', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/FadeOnHide', locale `kk': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/FadeOnHide', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/FadeOnHide', locale `ko': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/FadeOnHide', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only 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/docky-2/Docky/Interface/DockPreferences/DockN/FadeOpacity' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock6/FadeOpacity' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/FadeOpacity' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock5/FadeOpacity' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/FadeOpacity' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock4/FadeOpacity' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/FadeOpacity' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock3/FadeOpacity' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/FadeOpacity' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock2/FadeOpacity' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/FadeOpacity' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock1/FadeOpacity' WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/FadeOpacity', locale `lt': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/FadeOpacity', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/FadeOpacity', locale `de': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/FadeOpacity', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/FadeOpacity', locale `ro': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/FadeOpacity', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/FadeOpacity', locale `pt': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/FadeOpacity', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/FadeOpacity', locale `C': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/FadeOpacity', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/FadeOpacity', locale `sr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/FadeOpacity', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/FadeOpacity', locale `ru': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/FadeOpacity', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/FadeOpacity', locale `es': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/FadeOpacity', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only 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/docky-2/Docky/Interface/DockPreferences/DockN/IconSize' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock6/IconSize' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IconSize' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock5/IconSize' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IconSize' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock4/IconSize' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IconSize' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock3/IconSize' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IconSize' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock2/IconSize' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IconSize' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock1/IconSize' WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IconSize', locale `de': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IconSize', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IconSize', locale `lt': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IconSize', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IconSize', locale `sl': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IconSize', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IconSize', locale `ro': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IconSize', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IconSize', locale `fi': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IconSize', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IconSize', locale `C': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IconSize', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IconSize', locale `uk': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IconSize', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IconSize', locale `pt': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IconSize', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IconSize', locale `cs': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IconSize', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IconSize', locale `ru': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IconSize', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IconSize', locale `tr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IconSize', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IconSize', locale `sr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IconSize', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IconSize', locale `es': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IconSize', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IconSize', locale `fr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IconSize', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IconSize', locale `eu': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IconSize', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IconSize', locale `zh_TW': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IconSize', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IconSize', locale `kk': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IconSize', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IconSize', locale `ko': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IconSize', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IconSize', locale `nl': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IconSize', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only 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/docky-2/Docky/Interface/DockPreferences/DockN/IndicateMultipleWindows' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock6/IndicateMultipleWindows' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IndicateMultipleWindows' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock5/IndicateMultipleWindows' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IndicateMultipleWindows' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock4/IndicateMultipleWindows' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IndicateMultipleWindows' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock3/IndicateMultipleWindows' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IndicateMultipleWindows' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock2/IndicateMultipleWindows' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IndicateMultipleWindows' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock1/IndicateMultipleWindows' WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IndicateMultipleWindows', locale `de': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IndicateMultipleWindows', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IndicateMultipleWindows', locale `sl': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IndicateMultipleWindows', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IndicateMultipleWindows', locale `ro': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IndicateMultipleWindows', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IndicateMultipleWindows', locale `pt': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IndicateMultipleWindows', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IndicateMultipleWindows', locale `C': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IndicateMultipleWindows', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IndicateMultipleWindows', locale `cs': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IndicateMultipleWindows', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IndicateMultipleWindows', locale `ru': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IndicateMultipleWindows', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IndicateMultipleWindows', locale `sr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IndicateMultipleWindows', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IndicateMultipleWindows', locale `es': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IndicateMultipleWindows', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IndicateMultipleWindows', locale `fr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/IndicateMultipleWindows', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only 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/docky-2/Docky/Interface/DockPreferences/DockN/Launchers' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock6/Launchers' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Launchers' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock5/Launchers' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Launchers' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock4/Launchers' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Launchers' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock3/Launchers' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Launchers' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock2/Launchers' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Launchers' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock1/Launchers' WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Launchers', locale `lt': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Launchers', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Launchers', locale `de': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Launchers', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Launchers', locale `ro': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Launchers', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Launchers', locale `pt': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Launchers', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Launchers', locale `C': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Launchers', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Launchers', locale `cs': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Launchers', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Launchers', locale `ru': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Launchers', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Launchers', locale `tr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Launchers', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Launchers', locale `sr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Launchers', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Launchers', locale `es': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Launchers', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Launchers', locale `fr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Launchers', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only 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/docky-2/Docky/Interface/DockPreferences/DockN/MonitorNumber' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock6/MonitorNumber' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/MonitorNumber' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock5/MonitorNumber' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/MonitorNumber' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock4/MonitorNumber' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/MonitorNumber' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock3/MonitorNumber' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/MonitorNumber' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock2/MonitorNumber' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/MonitorNumber' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock1/MonitorNumber' WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/MonitorNumber', locale `de': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/MonitorNumber', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/MonitorNumber', locale `ro': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/MonitorNumber', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/MonitorNumber', locale `fi': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/MonitorNumber', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/MonitorNumber', locale `C': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/MonitorNumber', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/MonitorNumber', locale `sr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/MonitorNumber', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/MonitorNumber', locale `ru': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/MonitorNumber', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/MonitorNumber', locale `tr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/MonitorNumber', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/MonitorNumber', locale `es': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/MonitorNumber', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only 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/docky-2/Docky/Interface/DockPreferences/DockN/PanelMode' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock6/PanelMode' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/PanelMode' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock5/PanelMode' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/PanelMode' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock4/PanelMode' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/PanelMode' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock3/PanelMode' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/PanelMode' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock2/PanelMode' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/PanelMode' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock1/PanelMode' WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/PanelMode', locale `lt': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/PanelMode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/PanelMode', locale `de': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/PanelMode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/PanelMode', locale `sl': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/PanelMode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/PanelMode', locale `ro': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/PanelMode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/PanelMode', locale `pt': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/PanelMode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/PanelMode', locale `C': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/PanelMode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/PanelMode', locale `cs': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/PanelMode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/PanelMode', locale `ru': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/PanelMode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/PanelMode', locale `sr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/PanelMode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/PanelMode', locale `es': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/PanelMode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/PanelMode', locale `fr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/PanelMode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only 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/docky-2/Docky/Interface/DockPreferences/DockN/Plugins' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock6/Plugins' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Plugins' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock5/Plugins' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Plugins' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock4/Plugins' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Plugins' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock3/Plugins' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Plugins' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock2/Plugins' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Plugins' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock1/Plugins' WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Plugins', locale `de': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Plugins', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Plugins', locale `lt': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Plugins', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Plugins', locale `sl': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Plugins', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Plugins', locale `ro': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Plugins', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Plugins', locale `fi': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Plugins', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Plugins', locale `C': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Plugins', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Plugins', locale `uk': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Plugins', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Plugins', locale `pt': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Plugins', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Plugins', locale `cs': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Plugins', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Plugins', locale `ru': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Plugins', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Plugins', locale `tr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Plugins', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Plugins', locale `sr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Plugins', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Plugins', locale `es': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Plugins', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Plugins', locale `fr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Plugins', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Plugins', locale `eu': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Plugins', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Plugins', locale `zh_TW': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Plugins', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Plugins', locale `hu': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Plugins', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Plugins', locale `ko': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Plugins', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Plugins', locale `nl': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Plugins', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only 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/docky-2/Docky/Interface/DockPreferences/DockN/Position' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock6/Position' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Position' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock5/Position' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Position' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock4/Position' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Position' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock3/Position' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Position' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock2/Position' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Position' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock1/Position' WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Position', locale `lt': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Position', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Position', locale `de': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Position', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Position', locale `ro': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Position', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Position', locale `fi': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Position', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Position', locale `C': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Position', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Position', locale `cs': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Position', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Position', locale `ru': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Position', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Position', locale `tr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Position', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Position', locale `sr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Position', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Position', locale `es': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Position', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Position', locale `fr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/Position', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only 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/docky-2/Docky/Interface/DockPreferences/DockN/SortList' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock6/SortList' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/SortList' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock5/SortList' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/SortList' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock4/SortList' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/SortList' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock3/SortList' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/SortList' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock2/SortList' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/SortList' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock1/SortList' WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/SortList', locale `lt': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/SortList', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/SortList', locale `de': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/SortList', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/SortList', locale `ro': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/SortList', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/SortList', locale `C': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/SortList', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/SortList', locale `cs': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/SortList', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/SortList', locale `ru': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/SortList', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/SortList', locale `tr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/SortList', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/SortList', locale `sr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/SortList', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/SortList', locale `es': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/SortList', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/SortList', locale `fr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/SortList', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only 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/docky-2/Docky/Interface/DockPreferences/DockN/ThreeDimensional' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock6/ThreeDimensional' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ThreeDimensional' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock5/ThreeDimensional' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ThreeDimensional' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock4/ThreeDimensional' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ThreeDimensional' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock3/ThreeDimensional' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ThreeDimensional' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock2/ThreeDimensional' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ThreeDimensional' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock1/ThreeDimensional' WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ThreeDimensional', locale `de': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ThreeDimensional', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ThreeDimensional', locale `lt': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ThreeDimensional', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ThreeDimensional', locale `sl': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ThreeDimensional', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ThreeDimensional', locale `ro': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ThreeDimensional', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ThreeDimensional', locale `fi': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ThreeDimensional', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ThreeDimensional', locale `C': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ThreeDimensional', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ThreeDimensional', locale `uk': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ThreeDimensional', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ThreeDimensional', locale `pt': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ThreeDimensional', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ThreeDimensional', locale `cs': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ThreeDimensional', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ThreeDimensional', locale `ru': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ThreeDimensional', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ThreeDimensional', locale `tr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ThreeDimensional', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ThreeDimensional', locale `sr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ThreeDimensional', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ThreeDimensional', locale `es': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ThreeDimensional', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ThreeDimensional', locale `fr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ThreeDimensional', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ThreeDimensional', locale `eu': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ThreeDimensional', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ThreeDimensional', locale `zh_TW': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ThreeDimensional', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ThreeDimensional', locale `kk': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ThreeDimensional', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ThreeDimensional', locale `nb': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ThreeDimensional', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ThreeDimensional', locale `ko': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ThreeDimensional', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only 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/docky-2/Docky/Interface/DockPreferences/DockN/WindowManager' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock6/WindowManager' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/WindowManager' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock5/WindowManager' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/WindowManager' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock4/WindowManager' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/WindowManager' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock3/WindowManager' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/WindowManager' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock2/WindowManager' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/WindowManager' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock1/WindowManager' WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/WindowManager', locale `de': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/WindowManager', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/WindowManager', locale `lt': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/WindowManager', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/WindowManager', locale `sl': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/WindowManager', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/WindowManager', locale `ro': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/WindowManager', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/WindowManager', locale `fi': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/WindowManager', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/WindowManager', locale `C': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/WindowManager', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/WindowManager', locale `uk': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/WindowManager', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/WindowManager', locale `pt': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/WindowManager', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/WindowManager', locale `cs': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/WindowManager', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/WindowManager', locale `ru': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/WindowManager', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/WindowManager', locale `tr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/WindowManager', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/WindowManager', locale `sr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/WindowManager', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/WindowManager', locale `es': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/WindowManager', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/WindowManager', locale `fr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/WindowManager', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/WindowManager', locale `eu': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/WindowManager', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/WindowManager', locale `zh_TW': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/WindowManager', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/WindowManager', locale `kk': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/WindowManager', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/WindowManager', locale `nb': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/WindowManager', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/WindowManager', locale `ko': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/WindowManager', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only 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/docky-2/Docky/Interface/DockPreferences/DockN/ZoomEnabled' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock6/ZoomEnabled' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ZoomEnabled' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock5/ZoomEnabled' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ZoomEnabled' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock4/ZoomEnabled' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ZoomEnabled' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock3/ZoomEnabled' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ZoomEnabled' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock2/ZoomEnabled' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ZoomEnabled' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock1/ZoomEnabled' WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ZoomEnabled', locale `de': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ZoomEnabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ZoomEnabled', locale `lt': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ZoomEnabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ZoomEnabled', locale `ro': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ZoomEnabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ZoomEnabled', locale `pt': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ZoomEnabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ZoomEnabled', locale `C': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ZoomEnabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ZoomEnabled', locale `uk': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ZoomEnabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ZoomEnabled', locale `cs': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ZoomEnabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ZoomEnabled', locale `ru': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ZoomEnabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ZoomEnabled', locale `tr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ZoomEnabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ZoomEnabled', locale `sr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ZoomEnabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ZoomEnabled', locale `es': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ZoomEnabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ZoomEnabled', locale `fr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ZoomEnabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ZoomEnabled', locale `eu': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ZoomEnabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ZoomEnabled', locale `zh_TW': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ZoomEnabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ZoomEnabled', locale `ko': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ZoomEnabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only 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/docky-2/Docky/Interface/DockPreferences/DockN/ZoomPercent' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock6/ZoomPercent' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ZoomPercent' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock5/ZoomPercent' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ZoomPercent' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock4/ZoomPercent' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ZoomPercent' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock3/ZoomPercent' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ZoomPercent' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock2/ZoomPercent' Attached schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ZoomPercent' to key `/apps/docky-2/Docky/Interface/DockPreferences/Dock1/ZoomPercent' WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ZoomPercent', locale `lt': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ZoomPercent', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ZoomPercent', locale `de': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ZoomPercent', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ZoomPercent', locale `ro': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ZoomPercent', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ZoomPercent', locale `pt': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ZoomPercent', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ZoomPercent', locale `C': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ZoomPercent', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ZoomPercent', locale `cs': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ZoomPercent', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ZoomPercent', locale `ru': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ZoomPercent', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ZoomPercent', locale `tr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ZoomPercent', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ZoomPercent', locale `sr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ZoomPercent', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ZoomPercent', locale `es': Unable to store a value at key '/schemas/apps/docky-2/Docky/Interface/DockPreferences/DockN/ZoomPercent', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only 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/docky-2/Docky/Items/DockyItem/DockyItemCommand' to key `/apps/docky-2/Docky/Items/DockyItem/DockyItemCommand' WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/DockyItemCommand', locale `de': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/DockyItemCommand', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/DockyItemCommand', locale `sl': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/DockyItemCommand', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/DockyItemCommand', locale `ro': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/DockyItemCommand', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/DockyItemCommand', locale `pt': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/DockyItemCommand', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/DockyItemCommand', locale `C': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/DockyItemCommand', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/DockyItemCommand', locale `uk': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/DockyItemCommand', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/DockyItemCommand', locale `sr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/DockyItemCommand', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/DockyItemCommand', locale `ru': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/DockyItemCommand', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/DockyItemCommand', locale `tr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/DockyItemCommand', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/DockyItemCommand', locale `es': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/DockyItemCommand', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/DockyItemCommand', locale `fr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/DockyItemCommand', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/DockyItemCommand', locale `eu': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/DockyItemCommand', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/DockyItemCommand', locale `zh_TW': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/DockyItemCommand', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only 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/docky-2/Docky/Items/DockyItem/HoverText' to key `/apps/docky-2/Docky/Items/DockyItem/HoverText' WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/HoverText', locale `lt': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/HoverText', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/HoverText', locale `de': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/HoverText', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/HoverText', locale `ro': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/HoverText', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/HoverText', locale `pt': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/HoverText', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/HoverText', locale `C': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/HoverText', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/HoverText', locale `sr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/HoverText', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/HoverText', locale `ru': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/HoverText', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/HoverText', locale `tr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/HoverText', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/HoverText', locale `es': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/HoverText', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/HoverText', locale `fr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/HoverText', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/HoverText', locale `zh_TW': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/HoverText', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only 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/docky-2/Docky/Items/DockyItem/Hue' to key `/apps/docky-2/Docky/Items/DockyItem/Hue' WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/Hue', locale `lt': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/Hue', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/Hue', locale `de': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/Hue', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/Hue', locale `ro': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/Hue', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/Hue', locale `pt': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/Hue', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/Hue', locale `C': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/Hue', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/Hue', locale `uk': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/Hue', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/Hue', locale `sr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/Hue', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/Hue', locale `ru': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/Hue', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/Hue', locale `tr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/Hue', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/Hue', locale `es': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/Hue', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/Hue', locale `fr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/Hue', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/Hue', locale `zh_TW': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/Hue', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/Hue', locale `ko': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/Hue', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only 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/docky-2/Docky/Items/DockyItem/ShowDockyItem' to key `/apps/docky-2/Docky/Items/DockyItem/ShowDockyItem' WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/ShowDockyItem', locale `lt': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/ShowDockyItem', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/ShowDockyItem', locale `de': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/ShowDockyItem', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/ShowDockyItem', locale `ro': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/ShowDockyItem', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/ShowDockyItem', locale `pt': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/ShowDockyItem', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/ShowDockyItem', locale `C': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/ShowDockyItem', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/ShowDockyItem', locale `fi': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/ShowDockyItem', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/ShowDockyItem', locale `sr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/ShowDockyItem', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/ShowDockyItem', locale `ru': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/ShowDockyItem', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/ShowDockyItem', locale `tr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/ShowDockyItem', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/ShowDockyItem', locale `es': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/ShowDockyItem', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/ShowDockyItem', locale `fr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/ShowDockyItem', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only 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/docky-2/Docky/Items/DockyItem/ShowQuit' to key `/apps/docky-2/Docky/Items/DockyItem/ShowQuit' WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/ShowQuit', locale `de': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/ShowQuit', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/ShowQuit', locale `ro': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/ShowQuit', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/ShowQuit', locale `pt': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/ShowQuit', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/ShowQuit', locale `C': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/ShowQuit', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/ShowQuit', locale `sr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/ShowQuit', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/ShowQuit', locale `ru': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/ShowQuit', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/ShowQuit', locale `tr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/ShowQuit', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/ShowQuit', locale `es': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/ShowQuit', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/ShowQuit', locale `fr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/ShowQuit', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only 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/docky-2/Docky/Items/DockyItem/ShowSettings' to key `/apps/docky-2/Docky/Items/DockyItem/ShowSettings' WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/ShowSettings', locale `de': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/ShowSettings', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/ShowSettings', locale `ro': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/ShowSettings', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/ShowSettings', locale `pt': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/ShowSettings', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/ShowSettings', locale `C': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/ShowSettings', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/ShowSettings', locale `sr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/ShowSettings', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/ShowSettings', locale `ru': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/ShowSettings', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/ShowSettings', locale `tr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/ShowSettings', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/ShowSettings', locale `es': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/ShowSettings', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/DockyItem/ShowSettings', locale `fr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/DockyItem/ShowSettings', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only 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/docky-2/Docky/Items/FileApplicationProvider/AllowPinToDock' to key `/apps/docky-2/Docky/Items/FileApplicationProvider/AllowPinToDock' WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/FileApplicationProvider/AllowPinToDock', locale `de': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/FileApplicationProvider/AllowPinToDock', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/FileApplicationProvider/AllowPinToDock', locale `ro': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/FileApplicationProvider/AllowPinToDock', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/FileApplicationProvider/AllowPinToDock', locale `pt': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/FileApplicationProvider/AllowPinToDock', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/FileApplicationProvider/AllowPinToDock', locale `C': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/FileApplicationProvider/AllowPinToDock', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/FileApplicationProvider/AllowPinToDock', locale `fi': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/FileApplicationProvider/AllowPinToDock', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/FileApplicationProvider/AllowPinToDock', locale `cs': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/FileApplicationProvider/AllowPinToDock', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/FileApplicationProvider/AllowPinToDock', locale `ru': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/FileApplicationProvider/AllowPinToDock', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/FileApplicationProvider/AllowPinToDock', locale `tr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/FileApplicationProvider/AllowPinToDock', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/FileApplicationProvider/AllowPinToDock', locale `sr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/FileApplicationProvider/AllowPinToDock', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/FileApplicationProvider/AllowPinToDock', locale `es': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/FileApplicationProvider/AllowPinToDock', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only 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/docky-2/Docky/Items/WnckDockItem/CurrentDesktopOnly' to key `/apps/docky-2/Docky/Items/WnckDockItem/CurrentDesktopOnly' WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/WnckDockItem/CurrentDesktopOnly', locale `de': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/WnckDockItem/CurrentDesktopOnly', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/WnckDockItem/CurrentDesktopOnly', locale `sl': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/WnckDockItem/CurrentDesktopOnly', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/WnckDockItem/CurrentDesktopOnly', locale `ro': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/WnckDockItem/CurrentDesktopOnly', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/WnckDockItem/CurrentDesktopOnly', locale `pt': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/WnckDockItem/CurrentDesktopOnly', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/WnckDockItem/CurrentDesktopOnly', locale `C': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/WnckDockItem/CurrentDesktopOnly', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/WnckDockItem/CurrentDesktopOnly', locale `fi': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/WnckDockItem/CurrentDesktopOnly', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/WnckDockItem/CurrentDesktopOnly', locale `cs': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/WnckDockItem/CurrentDesktopOnly', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/WnckDockItem/CurrentDesktopOnly', locale `ru': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/WnckDockItem/CurrentDesktopOnly', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/WnckDockItem/CurrentDesktopOnly', locale `tr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/WnckDockItem/CurrentDesktopOnly', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/WnckDockItem/CurrentDesktopOnly', locale `sr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/WnckDockItem/CurrentDesktopOnly', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/WnckDockItem/CurrentDesktopOnly', locale `es': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/WnckDockItem/CurrentDesktopOnly', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/WnckDockItem/CurrentDesktopOnly', locale `fr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/WnckDockItem/CurrentDesktopOnly', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only 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/docky-2/Docky/Items/WnckDockItem/ShowHovers' to key `/apps/docky-2/Docky/Items/WnckDockItem/ShowHovers' WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/WnckDockItem/ShowHovers', locale `de': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/WnckDockItem/ShowHovers', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/WnckDockItem/ShowHovers', locale `ro': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/WnckDockItem/ShowHovers', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/WnckDockItem/ShowHovers', locale `pt': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/WnckDockItem/ShowHovers', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/WnckDockItem/ShowHovers', locale `C': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/WnckDockItem/ShowHovers', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/WnckDockItem/ShowHovers', locale `sr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/WnckDockItem/ShowHovers', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/WnckDockItem/ShowHovers', locale `ru': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/WnckDockItem/ShowHovers', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/WnckDockItem/ShowHovers', locale `tr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/WnckDockItem/ShowHovers', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/WnckDockItem/ShowHovers', locale `es': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/WnckDockItem/ShowHovers', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/WnckDockItem/ShowHovers', locale `fr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/WnckDockItem/ShowHovers', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Items/WnckDockItem/ShowHovers', locale `zh_TW': Unable to store a value at key '/schemas/apps/docky-2/Docky/Items/WnckDockItem/ShowHovers', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only 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/docky-2/Docky/Services/HelperService/ShowOutput' to key `/apps/docky-2/Docky/Services/HelperService/ShowOutput' WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Services/HelperService/ShowOutput', locale `sr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Services/HelperService/ShowOutput', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Services/HelperService/ShowOutput', locale `C': Unable to store a value at key '/schemas/apps/docky-2/Docky/Services/HelperService/ShowOutput', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Services/HelperService/ShowOutput', locale `ro': Unable to store a value at key '/schemas/apps/docky-2/Docky/Services/HelperService/ShowOutput', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Services/HelperService/ShowOutput', locale `es': Unable to store a value at key '/schemas/apps/docky-2/Docky/Services/HelperService/ShowOutput', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Services/HelperService/ShowOutput', locale `pt': Unable to store a value at key '/schemas/apps/docky-2/Docky/Services/HelperService/ShowOutput', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Services/HelperService/ShowOutput', locale `de': Unable to store a value at key '/schemas/apps/docky-2/Docky/Services/HelperService/ShowOutput', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only 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/docky-2/Docky/Services/ThemeService/GlowTime' to key `/apps/docky-2/Docky/Services/ThemeService/GlowTime' WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Services/ThemeService/GlowTime', locale `de': Unable to store a value at key '/schemas/apps/docky-2/Docky/Services/ThemeService/GlowTime', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Services/ThemeService/GlowTime', locale `ro': Unable to store a value at key '/schemas/apps/docky-2/Docky/Services/ThemeService/GlowTime', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Services/ThemeService/GlowTime', locale `pt': Unable to store a value at key '/schemas/apps/docky-2/Docky/Services/ThemeService/GlowTime', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Services/ThemeService/GlowTime', locale `C': Unable to store a value at key '/schemas/apps/docky-2/Docky/Services/ThemeService/GlowTime', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Services/ThemeService/GlowTime', locale `uk': Unable to store a value at key '/schemas/apps/docky-2/Docky/Services/ThemeService/GlowTime', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Services/ThemeService/GlowTime', locale `sr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Services/ThemeService/GlowTime', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Services/ThemeService/GlowTime', locale `ru': Unable to store a value at key '/schemas/apps/docky-2/Docky/Services/ThemeService/GlowTime', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Services/ThemeService/GlowTime', locale `tr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Services/ThemeService/GlowTime', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Services/ThemeService/GlowTime', locale `es': Unable to store a value at key '/schemas/apps/docky-2/Docky/Services/ThemeService/GlowTime', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Services/ThemeService/GlowTime', locale `fr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Services/ThemeService/GlowTime', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Services/ThemeService/GlowTime', locale `ko': Unable to store a value at key '/schemas/apps/docky-2/Docky/Services/ThemeService/GlowTime', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only 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/docky-2/Docky/Services/ThemeService/Theme' to key `/apps/docky-2/Docky/Services/ThemeService/Theme' WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Services/ThemeService/Theme', locale `lt': Unable to store a value at key '/schemas/apps/docky-2/Docky/Services/ThemeService/Theme', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Services/ThemeService/Theme', locale `de': Unable to store a value at key '/schemas/apps/docky-2/Docky/Services/ThemeService/Theme', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Services/ThemeService/Theme', locale `ro': Unable to store a value at key '/schemas/apps/docky-2/Docky/Services/ThemeService/Theme', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Services/ThemeService/Theme', locale `fi': Unable to store a value at key '/schemas/apps/docky-2/Docky/Services/ThemeService/Theme', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Services/ThemeService/Theme', locale `C': Unable to store a value at key '/schemas/apps/docky-2/Docky/Services/ThemeService/Theme', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Services/ThemeService/Theme', locale `cs': Unable to store a value at key '/schemas/apps/docky-2/Docky/Services/ThemeService/Theme', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Services/ThemeService/Theme', locale `ru': Unable to store a value at key '/schemas/apps/docky-2/Docky/Services/ThemeService/Theme', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Services/ThemeService/Theme', locale `tr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Services/ThemeService/Theme', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Services/ThemeService/Theme', locale `sr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Services/ThemeService/Theme', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Services/ThemeService/Theme', locale `es': Unable to store a value at key '/schemas/apps/docky-2/Docky/Services/ThemeService/Theme', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Services/ThemeService/Theme', locale `fr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Services/ThemeService/Theme', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only 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/docky-2/Docky/Services/ThemeService/UrgentHue' to key `/apps/docky-2/Docky/Services/ThemeService/UrgentHue' WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Services/ThemeService/UrgentHue', locale `de': Unable to store a value at key '/schemas/apps/docky-2/Docky/Services/ThemeService/UrgentHue', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Services/ThemeService/UrgentHue', locale `ro': Unable to store a value at key '/schemas/apps/docky-2/Docky/Services/ThemeService/UrgentHue', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Services/ThemeService/UrgentHue', locale `pt': Unable to store a value at key '/schemas/apps/docky-2/Docky/Services/ThemeService/UrgentHue', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Services/ThemeService/UrgentHue', locale `C': Unable to store a value at key '/schemas/apps/docky-2/Docky/Services/ThemeService/UrgentHue', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Services/ThemeService/UrgentHue', locale `sr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Services/ThemeService/UrgentHue', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Services/ThemeService/UrgentHue', locale `ru': Unable to store a value at key '/schemas/apps/docky-2/Docky/Services/ThemeService/UrgentHue', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Services/ThemeService/UrgentHue', locale `tr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Services/ThemeService/UrgentHue', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Services/ThemeService/UrgentHue', locale `es': Unable to store a value at key '/schemas/apps/docky-2/Docky/Services/ThemeService/UrgentHue', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Docky/Services/ThemeService/UrgentHue', locale `fr': Unable to store a value at key '/schemas/apps/docky-2/Docky/Services/ThemeService/UrgentHue', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only 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/docky-2/GMail/GMailPreferences/Labels' to key `/apps/docky-2/GMail/GMailPreferences/Labels' WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/Labels', locale `lt': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/Labels', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/Labels', locale `de': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/Labels', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/Labels', locale `ro': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/Labels', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/Labels', locale `C': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/Labels', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/Labels', locale `uk': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/Labels', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/Labels', locale `cs': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/Labels', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/Labels', locale `ru': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/Labels', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/Labels', locale `tr': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/Labels', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/Labels', locale `sr': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/Labels', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/Labels', locale `es': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/Labels', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/Labels', locale `fr': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/Labels', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/Labels', locale `eu': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/Labels', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/Labels', locale `zh_TW': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/Labels', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/Labels', locale `nl': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/Labels', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only 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/docky-2/GMail/GMailPreferences/LastChecked' to key `/apps/docky-2/GMail/GMailPreferences/LastChecked' WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/LastChecked', locale `lt': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/LastChecked', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/LastChecked', locale `de': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/LastChecked', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/LastChecked', locale `ro': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/LastChecked', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/LastChecked', locale `fi': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/LastChecked', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/LastChecked', locale `C': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/LastChecked', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/LastChecked', locale `pt': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/LastChecked', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/LastChecked', locale `cs': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/LastChecked', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/LastChecked', locale `ru': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/LastChecked', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/LastChecked', locale `tr': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/LastChecked', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/LastChecked', locale `sr': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/LastChecked', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/LastChecked', locale `es': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/LastChecked', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/LastChecked', locale `fr': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/LastChecked', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only 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/docky-2/GMail/GMailPreferences/NeedsAttention' to key `/apps/docky-2/GMail/GMailPreferences/NeedsAttention' WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/NeedsAttention', locale `de': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/NeedsAttention', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/NeedsAttention', locale `ro': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/NeedsAttention', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/NeedsAttention', locale `pt': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/NeedsAttention', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/NeedsAttention', locale `C': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/NeedsAttention', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/NeedsAttention', locale `sr': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/NeedsAttention', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/NeedsAttention', locale `ru': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/NeedsAttention', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/NeedsAttention', locale `tr': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/NeedsAttention', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/NeedsAttention', locale `es': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/NeedsAttention', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/NeedsAttention', locale `fr': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/NeedsAttention', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only 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/docky-2/GMail/GMailPreferences/Notify' to key `/apps/docky-2/GMail/GMailPreferences/Notify' WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/Notify', locale `lt': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/Notify', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/Notify', locale `de': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/Notify', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/Notify', locale `ro': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/Notify', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/Notify', locale `fi': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/Notify', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/Notify', locale `C': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/Notify', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/Notify', locale `pt': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/Notify', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/Notify', locale `cs': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/Notify', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/Notify', locale `ru': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/Notify', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/Notify', locale `tr': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/Notify', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/Notify', locale `sr': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/Notify', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/Notify', locale `es': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/Notify', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/Notify', locale `fr': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/Notify', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only 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/docky-2/GMail/GMailPreferences/RefreshRate' to key `/apps/docky-2/GMail/GMailPreferences/RefreshRate' WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/RefreshRate', locale `lt': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/RefreshRate', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/RefreshRate', locale `de': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/RefreshRate', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/RefreshRate', locale `sl': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/RefreshRate', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/RefreshRate', locale `ro': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/RefreshRate', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/RefreshRate', locale `fi': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/RefreshRate', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/RefreshRate', locale `C': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/RefreshRate', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/RefreshRate', locale `pt': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/RefreshRate', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/RefreshRate', locale `cs': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/RefreshRate', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/RefreshRate', locale `ru': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/RefreshRate', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/RefreshRate', locale `tr': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/RefreshRate', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/RefreshRate', locale `sr': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/RefreshRate', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/RefreshRate', locale `es': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/RefreshRate', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/RefreshRate', locale `fr': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/RefreshRate', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only 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/docky-2/GMail/GMailPreferences/User' to key `/apps/docky-2/GMail/GMailPreferences/User' WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/User', locale `de': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/User', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/User', locale `lt': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/User', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/User', locale `zh_CN': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/User', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/User', locale `sl': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/User', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/User', locale `ro': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/User', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/User', locale `fi': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/User', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/User', locale `C': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/User', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/User', locale `uk': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/User', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/User', locale `pt': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/User', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/User', locale `cs': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/User', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/User', locale `ru': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/User', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/User', locale `tr': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/User', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/User', locale `sr': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/User', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/User', locale `es': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/User', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/User', locale `fr': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/User', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/User', locale `eu': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/User', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/User', locale `zh_TW': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/User', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/User', locale `hu': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/User', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/GMail/GMailPreferences/User', locale `nl': Unable to store a value at key '/schemas/apps/docky-2/GMail/GMailPreferences/User', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only 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/docky-2/NPR/NPR/MyStations' to key `/apps/docky-2/NPR/NPR/MyStations' WARNING: failed to install schema `/schemas/apps/docky-2/NPR/NPR/MyStations', locale `lt': Unable to store a value at key '/schemas/apps/docky-2/NPR/NPR/MyStations', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/NPR/NPR/MyStations', locale `de': Unable to store a value at key '/schemas/apps/docky-2/NPR/NPR/MyStations', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/NPR/NPR/MyStations', locale `ro': Unable to store a value at key '/schemas/apps/docky-2/NPR/NPR/MyStations', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/NPR/NPR/MyStations', locale `fi': Unable to store a value at key '/schemas/apps/docky-2/NPR/NPR/MyStations', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/NPR/NPR/MyStations', locale `C': Unable to store a value at key '/schemas/apps/docky-2/NPR/NPR/MyStations', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/NPR/NPR/MyStations', locale `sr': Unable to store a value at key '/schemas/apps/docky-2/NPR/NPR/MyStations', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/NPR/NPR/MyStations', locale `ru': Unable to store a value at key '/schemas/apps/docky-2/NPR/NPR/MyStations', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/NPR/NPR/MyStations', locale `tr': Unable to store a value at key '/schemas/apps/docky-2/NPR/NPR/MyStations', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/NPR/NPR/MyStations', locale `es': Unable to store a value at key '/schemas/apps/docky-2/NPR/NPR/MyStations', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/NPR/NPR/MyStations', locale `fr': Unable to store a value at key '/schemas/apps/docky-2/NPR/NPR/MyStations', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only 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/docky-2/RecentDocuments/RecentDocumentsItem/AlwaysShowRecent' to key `/apps/docky-2/RecentDocuments/RecentDocumentsItem/AlwaysShowRecent' WARNING: failed to install schema `/schemas/apps/docky-2/RecentDocuments/RecentDocumentsItem/AlwaysShowRecent', locale `lt': Unable to store a value at key '/schemas/apps/docky-2/RecentDocuments/RecentDocumentsItem/AlwaysShowRecent', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/RecentDocuments/RecentDocumentsItem/AlwaysShowRecent', locale `de': Unable to store a value at key '/schemas/apps/docky-2/RecentDocuments/RecentDocumentsItem/AlwaysShowRecent', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/RecentDocuments/RecentDocumentsItem/AlwaysShowRecent', locale `ro': Unable to store a value at key '/schemas/apps/docky-2/RecentDocuments/RecentDocumentsItem/AlwaysShowRecent', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/RecentDocuments/RecentDocumentsItem/AlwaysShowRecent', locale `C': Unable to store a value at key '/schemas/apps/docky-2/RecentDocuments/RecentDocumentsItem/AlwaysShowRecent', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/RecentDocuments/RecentDocumentsItem/AlwaysShowRecent', locale `cs': Unable to store a value at key '/schemas/apps/docky-2/RecentDocuments/RecentDocumentsItem/AlwaysShowRecent', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/RecentDocuments/RecentDocumentsItem/AlwaysShowRecent', locale `ru': Unable to store a value at key '/schemas/apps/docky-2/RecentDocuments/RecentDocumentsItem/AlwaysShowRecent', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/RecentDocuments/RecentDocumentsItem/AlwaysShowRecent', locale `tr': Unable to store a value at key '/schemas/apps/docky-2/RecentDocuments/RecentDocumentsItem/AlwaysShowRecent', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/RecentDocuments/RecentDocumentsItem/AlwaysShowRecent', locale `sr': Unable to store a value at key '/schemas/apps/docky-2/RecentDocuments/RecentDocumentsItem/AlwaysShowRecent', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/RecentDocuments/RecentDocumentsItem/AlwaysShowRecent', locale `es': Unable to store a value at key '/schemas/apps/docky-2/RecentDocuments/RecentDocumentsItem/AlwaysShowRecent', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/RecentDocuments/RecentDocumentsItem/AlwaysShowRecent', locale `fr': Unable to store a value at key '/schemas/apps/docky-2/RecentDocuments/RecentDocumentsItem/AlwaysShowRecent', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only 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/docky-2/RecentDocuments/RecentDocumentsItem/NumRecentDocs' to key `/apps/docky-2/RecentDocuments/RecentDocumentsItem/NumRecentDocs' WARNING: failed to install schema `/schemas/apps/docky-2/RecentDocuments/RecentDocumentsItem/NumRecentDocs', locale `lt': Unable to store a value at key '/schemas/apps/docky-2/RecentDocuments/RecentDocumentsItem/NumRecentDocs', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/RecentDocuments/RecentDocumentsItem/NumRecentDocs', locale `de': Unable to store a value at key '/schemas/apps/docky-2/RecentDocuments/RecentDocumentsItem/NumRecentDocs', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/RecentDocuments/RecentDocumentsItem/NumRecentDocs', locale `ro': Unable to store a value at key '/schemas/apps/docky-2/RecentDocuments/RecentDocumentsItem/NumRecentDocs', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/RecentDocuments/RecentDocumentsItem/NumRecentDocs', locale `pt': Unable to store a value at key '/schemas/apps/docky-2/RecentDocuments/RecentDocumentsItem/NumRecentDocs', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/RecentDocuments/RecentDocumentsItem/NumRecentDocs', locale `C': Unable to store a value at key '/schemas/apps/docky-2/RecentDocuments/RecentDocumentsItem/NumRecentDocs', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/RecentDocuments/RecentDocumentsItem/NumRecentDocs', locale `cs': Unable to store a value at key '/schemas/apps/docky-2/RecentDocuments/RecentDocumentsItem/NumRecentDocs', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/RecentDocuments/RecentDocumentsItem/NumRecentDocs', locale `ru': Unable to store a value at key '/schemas/apps/docky-2/RecentDocuments/RecentDocumentsItem/NumRecentDocs', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/RecentDocuments/RecentDocumentsItem/NumRecentDocs', locale `tr': Unable to store a value at key '/schemas/apps/docky-2/RecentDocuments/RecentDocumentsItem/NumRecentDocs', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/RecentDocuments/RecentDocumentsItem/NumRecentDocs', locale `sr': Unable to store a value at key '/schemas/apps/docky-2/RecentDocuments/RecentDocumentsItem/NumRecentDocs', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/RecentDocuments/RecentDocumentsItem/NumRecentDocs', locale `es': Unable to store a value at key '/schemas/apps/docky-2/RecentDocuments/RecentDocumentsItem/NumRecentDocs', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/RecentDocuments/RecentDocumentsItem/NumRecentDocs', locale `fr': Unable to store a value at key '/schemas/apps/docky-2/RecentDocuments/RecentDocumentsItem/NumRecentDocs', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only 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/docky-2/SessionManager/SessionManagerItem/CurrentIndex' to key `/apps/docky-2/SessionManager/SessionManagerItem/CurrentIndex' WARNING: failed to install schema `/schemas/apps/docky-2/SessionManager/SessionManagerItem/CurrentIndex', locale `de': Unable to store a value at key '/schemas/apps/docky-2/SessionManager/SessionManagerItem/CurrentIndex', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/SessionManager/SessionManagerItem/CurrentIndex', locale `lt': Unable to store a value at key '/schemas/apps/docky-2/SessionManager/SessionManagerItem/CurrentIndex', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/SessionManager/SessionManagerItem/CurrentIndex', locale `sl': Unable to store a value at key '/schemas/apps/docky-2/SessionManager/SessionManagerItem/CurrentIndex', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/SessionManager/SessionManagerItem/CurrentIndex', locale `ro': Unable to store a value at key '/schemas/apps/docky-2/SessionManager/SessionManagerItem/CurrentIndex', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/SessionManager/SessionManagerItem/CurrentIndex', locale `pt': Unable to store a value at key '/schemas/apps/docky-2/SessionManager/SessionManagerItem/CurrentIndex', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/SessionManager/SessionManagerItem/CurrentIndex', locale `C': Unable to store a value at key '/schemas/apps/docky-2/SessionManager/SessionManagerItem/CurrentIndex', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/SessionManager/SessionManagerItem/CurrentIndex', locale `uk': Unable to store a value at key '/schemas/apps/docky-2/SessionManager/SessionManagerItem/CurrentIndex', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/SessionManager/SessionManagerItem/CurrentIndex', locale `cs': Unable to store a value at key '/schemas/apps/docky-2/SessionManager/SessionManagerItem/CurrentIndex', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/SessionManager/SessionManagerItem/CurrentIndex', locale `ru': Unable to store a value at key '/schemas/apps/docky-2/SessionManager/SessionManagerItem/CurrentIndex', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/SessionManager/SessionManagerItem/CurrentIndex', locale `tr': Unable to store a value at key '/schemas/apps/docky-2/SessionManager/SessionManagerItem/CurrentIndex', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/SessionManager/SessionManagerItem/CurrentIndex', locale `sr': Unable to store a value at key '/schemas/apps/docky-2/SessionManager/SessionManagerItem/CurrentIndex', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/SessionManager/SessionManagerItem/CurrentIndex', locale `es': Unable to store a value at key '/schemas/apps/docky-2/SessionManager/SessionManagerItem/CurrentIndex', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/SessionManager/SessionManagerItem/CurrentIndex', locale `fr': Unable to store a value at key '/schemas/apps/docky-2/SessionManager/SessionManagerItem/CurrentIndex', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/SessionManager/SessionManagerItem/CurrentIndex', locale `eu': Unable to store a value at key '/schemas/apps/docky-2/SessionManager/SessionManagerItem/CurrentIndex', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/SessionManager/SessionManagerItem/CurrentIndex', locale `zh_TW': Unable to store a value at key '/schemas/apps/docky-2/SessionManager/SessionManagerItem/CurrentIndex', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/SessionManager/SessionManagerItem/CurrentIndex', locale `ko': Unable to store a value at key '/schemas/apps/docky-2/SessionManager/SessionManagerItem/CurrentIndex', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/SessionManager/SessionManagerItem/CurrentIndex', locale `hu': Unable to store a value at key '/schemas/apps/docky-2/SessionManager/SessionManagerItem/CurrentIndex', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only 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/docky-2/Timer/TimerMainDockItem/AutoDismissTimers' to key `/apps/docky-2/Timer/TimerMainDockItem/AutoDismissTimers' WARNING: failed to install schema `/schemas/apps/docky-2/Timer/TimerMainDockItem/AutoDismissTimers', locale `de': Unable to store a value at key '/schemas/apps/docky-2/Timer/TimerMainDockItem/AutoDismissTimers', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Timer/TimerMainDockItem/AutoDismissTimers', locale `lt': Unable to store a value at key '/schemas/apps/docky-2/Timer/TimerMainDockItem/AutoDismissTimers', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Timer/TimerMainDockItem/AutoDismissTimers', locale `sl': Unable to store a value at key '/schemas/apps/docky-2/Timer/TimerMainDockItem/AutoDismissTimers', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Timer/TimerMainDockItem/AutoDismissTimers', locale `ro': Unable to store a value at key '/schemas/apps/docky-2/Timer/TimerMainDockItem/AutoDismissTimers', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Timer/TimerMainDockItem/AutoDismissTimers', locale `fi': Unable to store a value at key '/schemas/apps/docky-2/Timer/TimerMainDockItem/AutoDismissTimers', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Timer/TimerMainDockItem/AutoDismissTimers', locale `C': Unable to store a value at key '/schemas/apps/docky-2/Timer/TimerMainDockItem/AutoDismissTimers', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Timer/TimerMainDockItem/AutoDismissTimers', locale `uk': Unable to store a value at key '/schemas/apps/docky-2/Timer/TimerMainDockItem/AutoDismissTimers', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Timer/TimerMainDockItem/AutoDismissTimers', locale `pt': Unable to store a value at key '/schemas/apps/docky-2/Timer/TimerMainDockItem/AutoDismissTimers', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Timer/TimerMainDockItem/AutoDismissTimers', locale `cs': Unable to store a value at key '/schemas/apps/docky-2/Timer/TimerMainDockItem/AutoDismissTimers', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Timer/TimerMainDockItem/AutoDismissTimers', locale `ru': Unable to store a value at key '/schemas/apps/docky-2/Timer/TimerMainDockItem/AutoDismissTimers', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Timer/TimerMainDockItem/AutoDismissTimers', locale `tr': Unable to store a value at key '/schemas/apps/docky-2/Timer/TimerMainDockItem/AutoDismissTimers', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Timer/TimerMainDockItem/AutoDismissTimers', locale `sr': Unable to store a value at key '/schemas/apps/docky-2/Timer/TimerMainDockItem/AutoDismissTimers', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Timer/TimerMainDockItem/AutoDismissTimers', locale `es': Unable to store a value at key '/schemas/apps/docky-2/Timer/TimerMainDockItem/AutoDismissTimers', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Timer/TimerMainDockItem/AutoDismissTimers', locale `fr': Unable to store a value at key '/schemas/apps/docky-2/Timer/TimerMainDockItem/AutoDismissTimers', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Timer/TimerMainDockItem/AutoDismissTimers', locale `eu': Unable to store a value at key '/schemas/apps/docky-2/Timer/TimerMainDockItem/AutoDismissTimers', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Timer/TimerMainDockItem/AutoDismissTimers', locale `zh_TW': Unable to store a value at key '/schemas/apps/docky-2/Timer/TimerMainDockItem/AutoDismissTimers', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Timer/TimerMainDockItem/AutoDismissTimers', locale `ko': Unable to store a value at key '/schemas/apps/docky-2/Timer/TimerMainDockItem/AutoDismissTimers', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only 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/docky-2/Timer/TimerMainDockItem/AutoStartTimers' to key `/apps/docky-2/Timer/TimerMainDockItem/AutoStartTimers' WARNING: failed to install schema `/schemas/apps/docky-2/Timer/TimerMainDockItem/AutoStartTimers', locale `lt': Unable to store a value at key '/schemas/apps/docky-2/Timer/TimerMainDockItem/AutoStartTimers', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Timer/TimerMainDockItem/AutoStartTimers', locale `de': Unable to store a value at key '/schemas/apps/docky-2/Timer/TimerMainDockItem/AutoStartTimers', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Timer/TimerMainDockItem/AutoStartTimers', locale `ro': Unable to store a value at key '/schemas/apps/docky-2/Timer/TimerMainDockItem/AutoStartTimers', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Timer/TimerMainDockItem/AutoStartTimers', locale `fi': Unable to store a value at key '/schemas/apps/docky-2/Timer/TimerMainDockItem/AutoStartTimers', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Timer/TimerMainDockItem/AutoStartTimers', locale `C': Unable to store a value at key '/schemas/apps/docky-2/Timer/TimerMainDockItem/AutoStartTimers', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Timer/TimerMainDockItem/AutoStartTimers', locale `pt': Unable to store a value at key '/schemas/apps/docky-2/Timer/TimerMainDockItem/AutoStartTimers', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Timer/TimerMainDockItem/AutoStartTimers', locale `cs': Unable to store a value at key '/schemas/apps/docky-2/Timer/TimerMainDockItem/AutoStartTimers', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Timer/TimerMainDockItem/AutoStartTimers', locale `ru': Unable to store a value at key '/schemas/apps/docky-2/Timer/TimerMainDockItem/AutoStartTimers', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Timer/TimerMainDockItem/AutoStartTimers', locale `tr': Unable to store a value at key '/schemas/apps/docky-2/Timer/TimerMainDockItem/AutoStartTimers', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Timer/TimerMainDockItem/AutoStartTimers', locale `sr': Unable to store a value at key '/schemas/apps/docky-2/Timer/TimerMainDockItem/AutoStartTimers', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Timer/TimerMainDockItem/AutoStartTimers', locale `es': Unable to store a value at key '/schemas/apps/docky-2/Timer/TimerMainDockItem/AutoStartTimers', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Timer/TimerMainDockItem/AutoStartTimers', locale `fr': Unable to store a value at key '/schemas/apps/docky-2/Timer/TimerMainDockItem/AutoStartTimers', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only 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/docky-2/Timer/TimerMainDockItem/DefaultTimer' to key `/apps/docky-2/Timer/TimerMainDockItem/DefaultTimer' WARNING: failed to install schema `/schemas/apps/docky-2/Timer/TimerMainDockItem/DefaultTimer', locale `lt': Unable to store a value at key '/schemas/apps/docky-2/Timer/TimerMainDockItem/DefaultTimer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Timer/TimerMainDockItem/DefaultTimer', locale `de': Unable to store a value at key '/schemas/apps/docky-2/Timer/TimerMainDockItem/DefaultTimer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Timer/TimerMainDockItem/DefaultTimer', locale `ro': Unable to store a value at key '/schemas/apps/docky-2/Timer/TimerMainDockItem/DefaultTimer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Timer/TimerMainDockItem/DefaultTimer', locale `fi': Unable to store a value at key '/schemas/apps/docky-2/Timer/TimerMainDockItem/DefaultTimer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Timer/TimerMainDockItem/DefaultTimer', locale `C': Unable to store a value at key '/schemas/apps/docky-2/Timer/TimerMainDockItem/DefaultTimer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Timer/TimerMainDockItem/DefaultTimer', locale `cs': Unable to store a value at key '/schemas/apps/docky-2/Timer/TimerMainDockItem/DefaultTimer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Timer/TimerMainDockItem/DefaultTimer', locale `ru': Unable to store a value at key '/schemas/apps/docky-2/Timer/TimerMainDockItem/DefaultTimer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Timer/TimerMainDockItem/DefaultTimer', locale `tr': Unable to store a value at key '/schemas/apps/docky-2/Timer/TimerMainDockItem/DefaultTimer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Timer/TimerMainDockItem/DefaultTimer', locale `sr': Unable to store a value at key '/schemas/apps/docky-2/Timer/TimerMainDockItem/DefaultTimer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Timer/TimerMainDockItem/DefaultTimer', locale `es': Unable to store a value at key '/schemas/apps/docky-2/Timer/TimerMainDockItem/DefaultTimer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only 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/docky-2/Timer/TimerMainDockItem/DismissOnClick' to key `/apps/docky-2/Timer/TimerMainDockItem/DismissOnClick' WARNING: failed to install schema `/schemas/apps/docky-2/Timer/TimerMainDockItem/DismissOnClick', locale `de': Unable to store a value at key '/schemas/apps/docky-2/Timer/TimerMainDockItem/DismissOnClick', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Timer/TimerMainDockItem/DismissOnClick', locale `ro': Unable to store a value at key '/schemas/apps/docky-2/Timer/TimerMainDockItem/DismissOnClick', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Timer/TimerMainDockItem/DismissOnClick', locale `pt': Unable to store a value at key '/schemas/apps/docky-2/Timer/TimerMainDockItem/DismissOnClick', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Timer/TimerMainDockItem/DismissOnClick', locale `C': Unable to store a value at key '/schemas/apps/docky-2/Timer/TimerMainDockItem/DismissOnClick', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Timer/TimerMainDockItem/DismissOnClick', locale `uk': Unable to store a value at key '/schemas/apps/docky-2/Timer/TimerMainDockItem/DismissOnClick', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Timer/TimerMainDockItem/DismissOnClick', locale `sr': Unable to store a value at key '/schemas/apps/docky-2/Timer/TimerMainDockItem/DismissOnClick', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Timer/TimerMainDockItem/DismissOnClick', locale `ru': Unable to store a value at key '/schemas/apps/docky-2/Timer/TimerMainDockItem/DismissOnClick', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Timer/TimerMainDockItem/DismissOnClick', locale `tr': Unable to store a value at key '/schemas/apps/docky-2/Timer/TimerMainDockItem/DismissOnClick', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Timer/TimerMainDockItem/DismissOnClick', locale `es': Unable to store a value at key '/schemas/apps/docky-2/Timer/TimerMainDockItem/DismissOnClick', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Timer/TimerMainDockItem/DismissOnClick', locale `fr': Unable to store a value at key '/schemas/apps/docky-2/Timer/TimerMainDockItem/DismissOnClick', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Timer/TimerMainDockItem/DismissOnClick', locale `eu': Unable to store a value at key '/schemas/apps/docky-2/Timer/TimerMainDockItem/DismissOnClick', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Timer/TimerMainDockItem/DismissOnClick', locale `zh_TW': Unable to store a value at key '/schemas/apps/docky-2/Timer/TimerMainDockItem/DismissOnClick', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/Timer/TimerMainDockItem/DismissOnClick', locale `ko': Unable to store a value at key '/schemas/apps/docky-2/Timer/TimerMainDockItem/DismissOnClick', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only 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/docky-2/WeatherDocklet/WeatherPreferences/Location' to key `/apps/docky-2/WeatherDocklet/WeatherPreferences/Location' WARNING: failed to install schema `/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Location', locale `lt': Unable to store a value at key '/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Location', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Location', locale `de': Unable to store a value at key '/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Location', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Location', locale `ro': Unable to store a value at key '/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Location', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Location', locale `pt': Unable to store a value at key '/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Location', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Location', locale `C': Unable to store a value at key '/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Location', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Location', locale `cs': Unable to store a value at key '/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Location', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Location', locale `ru': Unable to store a value at key '/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Location', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Location', locale `tr': Unable to store a value at key '/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Location', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Location', locale `sr': Unable to store a value at key '/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Location', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Location', locale `es': Unable to store a value at key '/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Location', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only 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/docky-2/WeatherDocklet/WeatherPreferences/Metric' to key `/apps/docky-2/WeatherDocklet/WeatherPreferences/Metric' WARNING: failed to install schema `/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Metric', locale `lt': Unable to store a value at key '/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Metric', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Metric', locale `de': Unable to store a value at key '/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Metric', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Metric', locale `ro': Unable to store a value at key '/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Metric', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Metric', locale `fi': Unable to store a value at key '/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Metric', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Metric', locale `C': Unable to store a value at key '/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Metric', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Metric', locale `pt': Unable to store a value at key '/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Metric', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Metric', locale `cs': Unable to store a value at key '/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Metric', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Metric', locale `ru': Unable to store a value at key '/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Metric', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Metric', locale `tr': Unable to store a value at key '/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Metric', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Metric', locale `sr': Unable to store a value at key '/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Metric', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Metric', locale `es': Unable to store a value at key '/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Metric', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Metric', locale `fr': Unable to store a value at key '/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Metric', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only 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/docky-2/WeatherDocklet/WeatherPreferences/Source' to key `/apps/docky-2/WeatherDocklet/WeatherPreferences/Source' WARNING: failed to install schema `/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Source', locale `lt': Unable to store a value at key '/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Source', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Source', locale `de': Unable to store a value at key '/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Source', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Source', locale `ro': Unable to store a value at key '/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Source', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Source', locale `fi': Unable to store a value at key '/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Source', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Source', locale `C': Unable to store a value at key '/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Source', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Source', locale `cs': Unable to store a value at key '/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Source', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Source', locale `ru': Unable to store a value at key '/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Source', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Source', locale `tr': Unable to store a value at key '/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Source', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Source', locale `sr': Unable to store a value at key '/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Source', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Source', locale `es': Unable to store a value at key '/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Source', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only 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/docky-2/WeatherDocklet/WeatherPreferences/Timeout' to key `/apps/docky-2/WeatherDocklet/WeatherPreferences/Timeout' WARNING: failed to install schema `/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Timeout', locale `lt': Unable to store a value at key '/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Timeout', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Timeout', locale `de': Unable to store a value at key '/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Timeout', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Timeout', locale `sl': Unable to store a value at key '/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Timeout', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Timeout', locale `ro': Unable to store a value at key '/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Timeout', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Timeout', locale `fi': Unable to store a value at key '/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Timeout', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Timeout', locale `C': Unable to store a value at key '/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Timeout', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Timeout', locale `pt': Unable to store a value at key '/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Timeout', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Timeout', locale `cs': Unable to store a value at key '/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Timeout', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Timeout', locale `ru': Unable to store a value at key '/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Timeout', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Timeout', locale `tr': Unable to store a value at key '/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Timeout', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Timeout', locale `sr': Unable to store a value at key '/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Timeout', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Timeout', locale `es': Unable to store a value at key '/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Timeout', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Timeout', locale `fr': Unable to store a value at key '/schemas/apps/docky-2/WeatherDocklet/WeatherPreferences/Timeout', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf test -z "/usr/share/docky" || /bin/mkdir -p "/build/buildd/docky-2.1.2/debian/docky/usr/share/docky" /usr/bin/install -c -m 644 poof.png sun.svg wind.svg temp.svg '/build/buildd/docky-2.1.2/debian/docky/usr/share/docky' test -z "/usr/share/docky" || /bin/mkdir -p "/build/buildd/docky-2.1.2/debian/docky/usr/share/docky" /usr/bin/install -c -m 644 remaps.ini '/build/buildd/docky-2.1.2/debian/docky/usr/share/docky' test -z "/etc/gconf/schemas" || /bin/mkdir -p "/build/buildd/docky-2.1.2/debian/docky/etc/gconf/schemas" /usr/bin/install -c -m 644 docky.schemas '/build/buildd/docky-2.1.2/debian/docky/etc/gconf/schemas' make[4]: Leaving directory `/build/buildd/docky-2.1.2/data' make[3]: Leaving directory `/build/buildd/docky-2.1.2/data' make[2]: Leaving directory `/build/buildd/docky-2.1.2/data' Making install in po make[2]: Entering directory `/build/buildd/docky-2.1.2/po' linguas="ast bg bn ca cs da de el en_GB es et eu fi fil fo fr gl he hi hr hu id is it ja kk ko lt nb nl nn pl pt pt_BR ro ru sk sl sr sv tr uk vi zh_CN zh_HK zh_TW "; \ for lang in $linguas; do \ dir=/build/buildd/docky-2.1.2/debian/docky/usr/share/locale/$lang/LC_MESSAGES; \ /bin/bash /build/buildd/docky-2.1.2/install-sh -d $dir; \ if test -r $lang.gmo; then \ /usr/bin/install -c -m 644 $lang.gmo $dir/docky.mo; \ echo "installing $lang.gmo as $dir/docky.mo"; \ else \ /usr/bin/install -c -m 644 ./$lang.gmo $dir/docky.mo; \ echo "installing ./$lang.gmo as" \ "$dir/docky.mo"; \ fi; \ if test -r $lang.gmo.m; then \ /usr/bin/install -c -m 644 $lang.gmo.m $dir/docky.mo.m; \ echo "installing $lang.gmo.m as $dir/docky.mo.m"; \ else \ if test -r ./$lang.gmo.m ; then \ /usr/bin/install -c -m 644 ./$lang.gmo.m \ $dir/docky.mo.m; \ echo "installing ./$lang.gmo.m as" \ "$dir/docky.mo.m"; \ else \ true; \ fi; \ fi; \ done installing ast.gmo as /build/buildd/docky-2.1.2/debian/docky/usr/share/locale/ast/LC_MESSAGES/docky.mo installing bg.gmo as /build/buildd/docky-2.1.2/debian/docky/usr/share/locale/bg/LC_MESSAGES/docky.mo installing bn.gmo as /build/buildd/docky-2.1.2/debian/docky/usr/share/locale/bn/LC_MESSAGES/docky.mo installing ca.gmo as /build/buildd/docky-2.1.2/debian/docky/usr/share/locale/ca/LC_MESSAGES/docky.mo installing cs.gmo as /build/buildd/docky-2.1.2/debian/docky/usr/share/locale/cs/LC_MESSAGES/docky.mo installing da.gmo as /build/buildd/docky-2.1.2/debian/docky/usr/share/locale/da/LC_MESSAGES/docky.mo installing de.gmo as /build/buildd/docky-2.1.2/debian/docky/usr/share/locale/de/LC_MESSAGES/docky.mo installing el.gmo as /build/buildd/docky-2.1.2/debian/docky/usr/share/locale/el/LC_MESSAGES/docky.mo installing en_GB.gmo as /build/buildd/docky-2.1.2/debian/docky/usr/share/locale/en_GB/LC_MESSAGES/docky.mo installing es.gmo as /build/buildd/docky-2.1.2/debian/docky/usr/share/locale/es/LC_MESSAGES/docky.mo installing et.gmo as /build/buildd/docky-2.1.2/debian/docky/usr/share/locale/et/LC_MESSAGES/docky.mo installing eu.gmo as /build/buildd/docky-2.1.2/debian/docky/usr/share/locale/eu/LC_MESSAGES/docky.mo installing fi.gmo as /build/buildd/docky-2.1.2/debian/docky/usr/share/locale/fi/LC_MESSAGES/docky.mo installing fil.gmo as /build/buildd/docky-2.1.2/debian/docky/usr/share/locale/fil/LC_MESSAGES/docky.mo installing fo.gmo as /build/buildd/docky-2.1.2/debian/docky/usr/share/locale/fo/LC_MESSAGES/docky.mo installing fr.gmo as /build/buildd/docky-2.1.2/debian/docky/usr/share/locale/fr/LC_MESSAGES/docky.mo installing gl.gmo as /build/buildd/docky-2.1.2/debian/docky/usr/share/locale/gl/LC_MESSAGES/docky.mo installing he.gmo as /build/buildd/docky-2.1.2/debian/docky/usr/share/locale/he/LC_MESSAGES/docky.mo installing hi.gmo as /build/buildd/docky-2.1.2/debian/docky/usr/share/locale/hi/LC_MESSAGES/docky.mo installing hr.gmo as /build/buildd/docky-2.1.2/debian/docky/usr/share/locale/hr/LC_MESSAGES/docky.mo installing hu.gmo as /build/buildd/docky-2.1.2/debian/docky/usr/share/locale/hu/LC_MESSAGES/docky.mo installing id.gmo as /build/buildd/docky-2.1.2/debian/docky/usr/share/locale/id/LC_MESSAGES/docky.mo installing is.gmo as /build/buildd/docky-2.1.2/debian/docky/usr/share/locale/is/LC_MESSAGES/docky.mo installing it.gmo as /build/buildd/docky-2.1.2/debian/docky/usr/share/locale/it/LC_MESSAGES/docky.mo installing ja.gmo as /build/buildd/docky-2.1.2/debian/docky/usr/share/locale/ja/LC_MESSAGES/docky.mo installing kk.gmo as /build/buildd/docky-2.1.2/debian/docky/usr/share/locale/kk/LC_MESSAGES/docky.mo installing ko.gmo as /build/buildd/docky-2.1.2/debian/docky/usr/share/locale/ko/LC_MESSAGES/docky.mo installing lt.gmo as /build/buildd/docky-2.1.2/debian/docky/usr/share/locale/lt/LC_MESSAGES/docky.mo installing nb.gmo as /build/buildd/docky-2.1.2/debian/docky/usr/share/locale/nb/LC_MESSAGES/docky.mo installing nl.gmo as /build/buildd/docky-2.1.2/debian/docky/usr/share/locale/nl/LC_MESSAGES/docky.mo installing nn.gmo as /build/buildd/docky-2.1.2/debian/docky/usr/share/locale/nn/LC_MESSAGES/docky.mo installing pl.gmo as /build/buildd/docky-2.1.2/debian/docky/usr/share/locale/pl/LC_MESSAGES/docky.mo installing pt.gmo as /build/buildd/docky-2.1.2/debian/docky/usr/share/locale/pt/LC_MESSAGES/docky.mo installing pt_BR.gmo as /build/buildd/docky-2.1.2/debian/docky/usr/share/locale/pt_BR/LC_MESSAGES/docky.mo installing ro.gmo as /build/buildd/docky-2.1.2/debian/docky/usr/share/locale/ro/LC_MESSAGES/docky.mo installing ru.gmo as /build/buildd/docky-2.1.2/debian/docky/usr/share/locale/ru/LC_MESSAGES/docky.mo installing sk.gmo as /build/buildd/docky-2.1.2/debian/docky/usr/share/locale/sk/LC_MESSAGES/docky.mo installing sl.gmo as /build/buildd/docky-2.1.2/debian/docky/usr/share/locale/sl/LC_MESSAGES/docky.mo installing sr.gmo as /build/buildd/docky-2.1.2/debian/docky/usr/share/locale/sr/LC_MESSAGES/docky.mo installing sv.gmo as /build/buildd/docky-2.1.2/debian/docky/usr/share/locale/sv/LC_MESSAGES/docky.mo installing tr.gmo as /build/buildd/docky-2.1.2/debian/docky/usr/share/locale/tr/LC_MESSAGES/docky.mo installing uk.gmo as /build/buildd/docky-2.1.2/debian/docky/usr/share/locale/uk/LC_MESSAGES/docky.mo installing vi.gmo as /build/buildd/docky-2.1.2/debian/docky/usr/share/locale/vi/LC_MESSAGES/docky.mo installing zh_CN.gmo as /build/buildd/docky-2.1.2/debian/docky/usr/share/locale/zh_CN/LC_MESSAGES/docky.mo installing zh_HK.gmo as /build/buildd/docky-2.1.2/debian/docky/usr/share/locale/zh_HK/LC_MESSAGES/docky.mo installing zh_TW.gmo as /build/buildd/docky-2.1.2/debian/docky/usr/share/locale/zh_TW/LC_MESSAGES/docky.mo make[2]: Leaving directory `/build/buildd/docky-2.1.2/po' Making install in Docky.CairoHelper make[2]: Entering directory `/build/buildd/docky-2.1.2/Docky.CairoHelper' make[3]: Entering directory `/build/buildd/docky-2.1.2/Docky.CairoHelper' make[3]: Nothing to be done for `install-exec-am'. test -z "/usr/lib/docky" || /bin/mkdir -p "/build/buildd/docky-2.1.2/debian/docky/usr/lib/docky" /usr/bin/install -c -m 644 ../build/Docky.CairoHelper.dll '/build/buildd/docky-2.1.2/debian/docky/usr/lib/docky' test -z "/usr/lib/docky" || /bin/mkdir -p "/build/buildd/docky-2.1.2/debian/docky/usr/lib/docky" test -z "/usr/lib/pkgconfig" || /bin/mkdir -p "/build/buildd/docky-2.1.2/debian/docky/usr/lib/pkgconfig" /usr/bin/install -c -m 644 docky.cairohelper.pc '/build/buildd/docky-2.1.2/debian/docky/usr/lib/pkgconfig' make[3]: Leaving directory `/build/buildd/docky-2.1.2/Docky.CairoHelper' make[2]: Leaving directory `/build/buildd/docky-2.1.2/Docky.CairoHelper' Making install in Docky.Services make[2]: Entering directory `/build/buildd/docky-2.1.2/Docky.Services' make[3]: Entering directory `/build/buildd/docky-2.1.2/Docky.Services' make[3]: Nothing to be done for `install-exec-am'. test -z "/usr/lib/docky" || /bin/mkdir -p "/build/buildd/docky-2.1.2/debian/docky/usr/lib/docky" /usr/bin/install -c -m 644 ../build/Docky.Services.dll Docky.Services.dll.config '/build/buildd/docky-2.1.2/debian/docky/usr/lib/docky' test -z "/usr/lib/docky" || /bin/mkdir -p "/build/buildd/docky-2.1.2/debian/docky/usr/lib/docky" test -z "/usr/lib/pkgconfig" || /bin/mkdir -p "/build/buildd/docky-2.1.2/debian/docky/usr/lib/pkgconfig" /usr/bin/install -c -m 644 docky.services.pc '/build/buildd/docky-2.1.2/debian/docky/usr/lib/pkgconfig' make[3]: Leaving directory `/build/buildd/docky-2.1.2/Docky.Services' make[2]: Leaving directory `/build/buildd/docky-2.1.2/Docky.Services' Making install in Docky.Widgets make[2]: Entering directory `/build/buildd/docky-2.1.2/Docky.Widgets' make[3]: Entering directory `/build/buildd/docky-2.1.2/Docky.Widgets' make[3]: Nothing to be done for `install-exec-am'. test -z "/usr/lib/docky" || /bin/mkdir -p "/build/buildd/docky-2.1.2/debian/docky/usr/lib/docky" /usr/bin/install -c -m 644 ../build/Docky.Widgets.dll Docky.Widgets.dll.config '/build/buildd/docky-2.1.2/debian/docky/usr/lib/docky' test -z "/usr/lib/docky" || /bin/mkdir -p "/build/buildd/docky-2.1.2/debian/docky/usr/lib/docky" test -z "/usr/lib/pkgconfig" || /bin/mkdir -p "/build/buildd/docky-2.1.2/debian/docky/usr/lib/pkgconfig" /usr/bin/install -c -m 644 docky.widgets.pc '/build/buildd/docky-2.1.2/debian/docky/usr/lib/pkgconfig' make[3]: Leaving directory `/build/buildd/docky-2.1.2/Docky.Widgets' make[2]: Leaving directory `/build/buildd/docky-2.1.2/Docky.Widgets' Making install in Docky.Items make[2]: Entering directory `/build/buildd/docky-2.1.2/Docky.Items' make[3]: Entering directory `/build/buildd/docky-2.1.2/Docky.Items' make[3]: Nothing to be done for `install-exec-am'. test -z "/usr/lib/docky" || /bin/mkdir -p "/build/buildd/docky-2.1.2/debian/docky/usr/lib/docky" /usr/bin/install -c -m 644 ../build/Docky.Items.dll '/build/buildd/docky-2.1.2/debian/docky/usr/lib/docky' test -z "/usr/lib/docky" || /bin/mkdir -p "/build/buildd/docky-2.1.2/debian/docky/usr/lib/docky" test -z "/usr/lib/pkgconfig" || /bin/mkdir -p "/build/buildd/docky-2.1.2/debian/docky/usr/lib/pkgconfig" /usr/bin/install -c -m 644 docky.items.pc '/build/buildd/docky-2.1.2/debian/docky/usr/lib/pkgconfig' make[3]: Leaving directory `/build/buildd/docky-2.1.2/Docky.Items' make[2]: Leaving directory `/build/buildd/docky-2.1.2/Docky.Items' Making install in Docky.DBus make[2]: Entering directory `/build/buildd/docky-2.1.2/Docky.DBus' make[3]: Entering directory `/build/buildd/docky-2.1.2/Docky.DBus' make[3]: Nothing to be done for `install-exec-am'. test -z "/usr/lib/docky" || /bin/mkdir -p "/build/buildd/docky-2.1.2/debian/docky/usr/lib/docky" /usr/bin/install -c -m 644 ../build/Docky.DBus.dll '/build/buildd/docky-2.1.2/debian/docky/usr/lib/docky' test -z "/usr/lib/docky" || /bin/mkdir -p "/build/buildd/docky-2.1.2/debian/docky/usr/lib/docky" test -z "/usr/lib/pkgconfig" || /bin/mkdir -p "/build/buildd/docky-2.1.2/debian/docky/usr/lib/pkgconfig" make[3]: Leaving directory `/build/buildd/docky-2.1.2/Docky.DBus' make[2]: Leaving directory `/build/buildd/docky-2.1.2/Docky.DBus' Making install in StandardPlugins make[2]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins' Making install in BatteryMonitor make[3]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/BatteryMonitor' make[4]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/BatteryMonitor' make[4]: Nothing to be done for `install-exec-am'. test -z "/usr/lib/docky/plugins" || /bin/mkdir -p "/build/buildd/docky-2.1.2/debian/docky/usr/lib/docky/plugins" /usr/bin/install -c -m 644 ../../build/BatteryMonitor.dll '/build/buildd/docky-2.1.2/debian/docky/usr/lib/docky/plugins' make[4]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/BatteryMonitor' make[3]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/BatteryMonitor' Making install in Bookmarks make[3]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/Bookmarks' make[4]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/Bookmarks' make[4]: Nothing to be done for `install-exec-am'. test -z "/usr/lib/docky/plugins" || /bin/mkdir -p "/build/buildd/docky-2.1.2/debian/docky/usr/lib/docky/plugins" /usr/bin/install -c -m 644 ../../build/Bookmarks.dll '/build/buildd/docky-2.1.2/debian/docky/usr/lib/docky/plugins' make[4]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/Bookmarks' make[3]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/Bookmarks' Making install in Clippy make[3]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/Clippy' make[4]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/Clippy' make[4]: Nothing to be done for `install-exec-am'. test -z "/usr/lib/docky/plugins" || /bin/mkdir -p "/build/buildd/docky-2.1.2/debian/docky/usr/lib/docky/plugins" /usr/bin/install -c -m 644 ../../build/Clippy.dll '/build/buildd/docky-2.1.2/debian/docky/usr/lib/docky/plugins' make[4]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/Clippy' make[3]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/Clippy' Making install in Clock make[3]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/Clock' Making install in Themes make[4]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/Clock/Themes' Making install in Default make[5]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/Clock/Themes/Default' make[6]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/Clock/Themes/Default' make[6]: Nothing to be done for `install-exec-am'. test -z "/usr/share/docky/ClockTheme/default" || /bin/mkdir -p "/build/buildd/docky-2.1.2/debian/docky/usr/share/docky/ClockTheme/default" /usr/bin/install -c -m 644 clock-drop-shadow.svg clock-face.svg clock-glass.svg clock-face-shadow.svg clock-frame.svg clock-marks.svg '/build/buildd/docky-2.1.2/debian/docky/usr/share/docky/ClockTheme/default' make[6]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/Clock/Themes/Default' make[5]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/Clock/Themes/Default' Making install in Default24 make[5]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/Clock/Themes/Default24' make[6]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/Clock/Themes/Default24' make[6]: Nothing to be done for `install-exec-am'. test -z "/usr/share/docky/ClockTheme/default-24" || /bin/mkdir -p "/build/buildd/docky-2.1.2/debian/docky/usr/share/docky/ClockTheme/default-24" /usr/bin/install -c -m 644 clock-drop-shadow.svg clock-face.svg clock-glass.svg clock-face-shadow.svg clock-frame.svg clock-marks.svg '/build/buildd/docky-2.1.2/debian/docky/usr/share/docky/ClockTheme/default-24' make[6]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/Clock/Themes/Default24' make[5]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/Clock/Themes/Default24' make[5]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/Clock/Themes' make[6]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/Clock/Themes' make[6]: Nothing to be done for `install-exec-am'. make[6]: Nothing to be done for `install-data-am'. make[6]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/Clock/Themes' make[5]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/Clock/Themes' make[4]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/Clock/Themes' make[4]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/Clock' make[5]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/Clock' make[5]: Nothing to be done for `install-exec-am'. test -z "/usr/lib/docky/plugins" || /bin/mkdir -p "/build/buildd/docky-2.1.2/debian/docky/usr/lib/docky/plugins" /usr/bin/install -c -m 644 ../../build/Clock.dll '/build/buildd/docky-2.1.2/debian/docky/usr/lib/docky/plugins' make[5]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/Clock' make[4]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/Clock' make[3]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/Clock' Making install in Desktop make[3]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/Desktop' make[4]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/Desktop' make[4]: Nothing to be done for `install-exec-am'. test -z "/usr/lib/docky/plugins" || /bin/mkdir -p "/build/buildd/docky-2.1.2/debian/docky/usr/lib/docky/plugins" /usr/bin/install -c -m 644 ../../build/Desktop.dll '/build/buildd/docky-2.1.2/debian/docky/usr/lib/docky/plugins' make[4]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/Desktop' make[3]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/Desktop' Making install in CPUMonitor make[3]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/CPUMonitor' make[4]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/CPUMonitor' make[4]: Nothing to be done for `install-exec-am'. test -z "/usr/lib/docky/plugins" || /bin/mkdir -p "/build/buildd/docky-2.1.2/debian/docky/usr/lib/docky/plugins" /usr/bin/install -c -m 644 ../../build/CPUMonitor.dll '/build/buildd/docky-2.1.2/debian/docky/usr/lib/docky/plugins' make[4]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/CPUMonitor' make[3]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/CPUMonitor' Making install in GMail make[3]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/GMail' make[4]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/GMail' make[4]: Nothing to be done for `install-exec-am'. test -z "/usr/lib/docky/plugins" || /bin/mkdir -p "/build/buildd/docky-2.1.2/debian/docky/usr/lib/docky/plugins" /usr/bin/install -c -m 644 ../../build/GMail.dll '/build/buildd/docky-2.1.2/debian/docky/usr/lib/docky/plugins' make[4]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/GMail' make[3]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/GMail' Making install in Mounter make[3]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/Mounter' make[4]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/Mounter' make[4]: Nothing to be done for `install-exec-am'. test -z "/usr/lib/docky/plugins" || /bin/mkdir -p "/build/buildd/docky-2.1.2/debian/docky/usr/lib/docky/plugins" /usr/bin/install -c -m 644 ../../build/Mounter.dll '/build/buildd/docky-2.1.2/debian/docky/usr/lib/docky/plugins' make[4]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/Mounter' make[3]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/Mounter' Making install in NetworkManager make[3]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/NetworkManager' make[4]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/NetworkManager' make[4]: Nothing to be done for `install-exec-am'. test -z "/usr/lib/docky/plugins" || /bin/mkdir -p "/build/buildd/docky-2.1.2/debian/docky/usr/lib/docky/plugins" /usr/bin/install -c -m 644 ../../build/NetworkManager.dll '/build/buildd/docky-2.1.2/debian/docky/usr/lib/docky/plugins' make[4]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/NetworkManager' make[3]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/NetworkManager' Making install in NPR make[3]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/NPR' make[4]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/NPR' make[4]: Nothing to be done for `install-exec-am'. test -z "/usr/lib/docky/plugins" || /bin/mkdir -p "/build/buildd/docky-2.1.2/debian/docky/usr/lib/docky/plugins" /usr/bin/install -c -m 644 ../../build/NPR.dll '/build/buildd/docky-2.1.2/debian/docky/usr/lib/docky/plugins' make[4]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/NPR' make[3]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/NPR' Making install in RecentDocuments make[3]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/RecentDocuments' make[4]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/RecentDocuments' make[4]: Nothing to be done for `install-exec-am'. test -z "/usr/lib/docky/plugins" || /bin/mkdir -p "/build/buildd/docky-2.1.2/debian/docky/usr/lib/docky/plugins" /usr/bin/install -c -m 644 ../../build/RecentDocuments.dll '/build/buildd/docky-2.1.2/debian/docky/usr/lib/docky/plugins' make[4]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/RecentDocuments' make[3]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/RecentDocuments' Making install in SessionManager make[3]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/SessionManager' make[4]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/SessionManager' make[4]: Nothing to be done for `install-exec-am'. test -z "/usr/lib/docky/plugins" || /bin/mkdir -p "/build/buildd/docky-2.1.2/debian/docky/usr/lib/docky/plugins" /usr/bin/install -c -m 644 ../../build/SessionManager.dll '/build/buildd/docky-2.1.2/debian/docky/usr/lib/docky/plugins' make[4]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/SessionManager' make[3]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/SessionManager' Making install in Timer make[3]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/Timer' make[4]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/Timer' make[4]: Nothing to be done for `install-exec-am'. test -z "/usr/lib/docky/plugins" || /bin/mkdir -p "/build/buildd/docky-2.1.2/debian/docky/usr/lib/docky/plugins" /usr/bin/install -c -m 644 ../../build/Timer.dll '/build/buildd/docky-2.1.2/debian/docky/usr/lib/docky/plugins' make[4]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/Timer' make[3]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/Timer' Making install in Trash make[3]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/Trash' make[4]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/Trash' make[4]: Nothing to be done for `install-exec-am'. test -z "/usr/lib/docky/plugins" || /bin/mkdir -p "/build/buildd/docky-2.1.2/debian/docky/usr/lib/docky/plugins" /usr/bin/install -c -m 644 ../../build/Trash.dll '/build/buildd/docky-2.1.2/debian/docky/usr/lib/docky/plugins' make[4]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/Trash' make[3]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/Trash' Making install in Weather make[3]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/Weather' make[4]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/Weather' make[4]: Nothing to be done for `install-exec-am'. test -z "/usr/lib/docky/plugins" || /bin/mkdir -p "/build/buildd/docky-2.1.2/debian/docky/usr/lib/docky/plugins" /usr/bin/install -c -m 644 ../../build/Weather.dll '/build/buildd/docky-2.1.2/debian/docky/usr/lib/docky/plugins' make[4]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/Weather' make[3]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/Weather' Making install in WorkspaceSwitcher make[3]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/WorkspaceSwitcher' make[4]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins/WorkspaceSwitcher' make[4]: Nothing to be done for `install-exec-am'. test -z "/usr/lib/docky/plugins" || /bin/mkdir -p "/build/buildd/docky-2.1.2/debian/docky/usr/lib/docky/plugins" /usr/bin/install -c -m 644 ../../build/WorkspaceSwitcher.dll '/build/buildd/docky-2.1.2/debian/docky/usr/lib/docky/plugins' make[4]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/WorkspaceSwitcher' make[3]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins/WorkspaceSwitcher' make[3]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins' make[4]: Entering directory `/build/buildd/docky-2.1.2/StandardPlugins' make[4]: Nothing to be done for `install-exec-am'. make[4]: Nothing to be done for `install-data-am'. make[4]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins' make[3]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins' make[2]: Leaving directory `/build/buildd/docky-2.1.2/StandardPlugins' Making install in Docky make[2]: Entering directory `/build/buildd/docky-2.1.2/Docky' make[3]: Entering directory `/build/buildd/docky-2.1.2/Docky' test -z "/usr/bin" || /bin/mkdir -p "/build/buildd/docky-2.1.2/debian/docky/usr/bin" /usr/bin/install -c docky '/build/buildd/docky-2.1.2/debian/docky/usr/bin' test -z "/usr/lib/docky" || /bin/mkdir -p "/build/buildd/docky-2.1.2/debian/docky/usr/lib/docky" /usr/bin/install -c -m 644 Docky.addins '/build/buildd/docky-2.1.2/debian/docky/usr/lib/docky' test -z "/usr/lib/docky" || /bin/mkdir -p "/build/buildd/docky-2.1.2/debian/docky/usr/lib/docky" /usr/bin/install -c ../build/Docky.exe '/build/buildd/docky-2.1.2/debian/docky/usr/lib/docky' test -z "/usr/lib/pkgconfig" || /bin/mkdir -p "/build/buildd/docky-2.1.2/debian/docky/usr/lib/pkgconfig" make[3]: Leaving directory `/build/buildd/docky-2.1.2/Docky' make[2]: Leaving directory `/build/buildd/docky-2.1.2/Docky' Making install in man make[2]: Entering directory `/build/buildd/docky-2.1.2/man' make[3]: Entering directory `/build/buildd/docky-2.1.2/man' make[3]: Nothing to be done for `install-exec-am'. test -z "/usr/share/man/man1" || /bin/mkdir -p "/build/buildd/docky-2.1.2/debian/docky/usr/share/man/man1" /usr/bin/install -c -m 644 docky.1 '/build/buildd/docky-2.1.2/debian/docky/usr/share/man/man1' make[3]: Leaving directory `/build/buildd/docky-2.1.2/man' make[2]: Leaving directory `/build/buildd/docky-2.1.2/man' Making install in m4 make[2]: Entering directory `/build/buildd/docky-2.1.2/m4' make[3]: Entering directory `/build/buildd/docky-2.1.2/m4' make[3]: Nothing to be done for `install-exec-am'. make[3]: Nothing to be done for `install-data-am'. make[3]: Leaving directory `/build/buildd/docky-2.1.2/m4' make[2]: Leaving directory `/build/buildd/docky-2.1.2/m4' make[1]: Leaving directory `/build/buildd/docky-2.1.2' dh_install Unknown option: with dh_install: warning: ignored unknown options in DH_OPTIONS dh_installdocs Unknown option: with dh_installdocs: warning: ignored unknown options in DH_OPTIONS dh_installchangelogs Unknown option: with dh_installchangelogs: warning: ignored unknown options in DH_OPTIONS dh_installexamples Unknown option: with dh_installexamples: warning: ignored unknown options in DH_OPTIONS dh_installman Unknown option: with dh_installman: warning: ignored unknown options in DH_OPTIONS dh_installcatalogs Unknown option: with dh_installcatalogs: warning: ignored unknown options in DH_OPTIONS dh_installcron Unknown option: with dh_installcron: warning: ignored unknown options in DH_OPTIONS dh_installdebconf Unknown option: with dh_installdebconf: warning: ignored unknown options in DH_OPTIONS dh_installemacsen Unknown option: with dh_installemacsen: warning: ignored unknown options in DH_OPTIONS dh_installifupdown Unknown option: with dh_installifupdown: warning: ignored unknown options in DH_OPTIONS dh_installinfo Unknown option: with dh_installinfo: warning: ignored unknown options in DH_OPTIONS dh_installinit Duplicate specification "O=s" for option "O" Unknown option: with dh_installinit: warning: ignored unknown options in DH_OPTIONS Duplicate specification "O=s" for option "O" dh_installmenu Unknown option: with dh_installmenu: warning: ignored unknown options in DH_OPTIONS dh_installmime Unknown option: with dh_installmime: warning: ignored unknown options in DH_OPTIONS dh_installmodules Unknown option: with dh_installmodules: warning: ignored unknown options in DH_OPTIONS dh_installlogcheck Unknown option: with dh_installlogcheck: warning: ignored unknown options in DH_OPTIONS dh_installlogrotate Unknown option: with dh_installlogrotate: warning: ignored unknown options in DH_OPTIONS dh_installpam Unknown option: with dh_installpam: warning: ignored unknown options in DH_OPTIONS dh_installppp Unknown option: with dh_installppp: warning: ignored unknown options in DH_OPTIONS dh_installudev Unknown option: with dh_installudev: warning: ignored unknown options in DH_OPTIONS dh_installwm Unknown option: with dh_installwm: warning: ignored unknown options in DH_OPTIONS dh_installxfonts Unknown option: with dh_installxfonts: warning: ignored unknown options in DH_OPTIONS dh_bugfiles Unknown option: with dh_bugfiles: warning: ignored unknown options in DH_OPTIONS dh_lintian Unknown option: with dh_lintian: warning: ignored unknown options in DH_OPTIONS dh_gconf Unknown option: with dh_gconf: warning: ignored unknown options in DH_OPTIONS dh_icons Unknown option: with dh_icons: warning: ignored unknown options in DH_OPTIONS dh_perl Unknown option: with dh_perl: warning: ignored unknown options in DH_OPTIONS dh_usrlocal Unknown option: with dh_usrlocal: warning: ignored unknown options in DH_OPTIONS dh_link Unknown option: with dh_link: warning: ignored unknown options in DH_OPTIONS dh_compress Unknown option: with dh_compress: warning: ignored unknown options in DH_OPTIONS dh_fixperms Unknown option: with dh_fixperms: warning: ignored unknown options in DH_OPTIONS dh_clifixperms Unknown option: with dh_clifixperms: warning: ignored unknown options in DH_OPTIONS dh_strip dh_strip debug symbol extraction: all non-arch-all packages for this build platform i386: dh_strip debug symbol extraction: packages to act on: dh_strip debug symbol extraction: ignored packages: Unknown option: with dh_strip.pkg-create-dbgsym: warning: ignored unknown options in DH_OPTIONS dh_makeshlibs Unknown option: with dh_makeshlibs: warning: ignored unknown options in DH_OPTIONS dh_shlibdeps Unknown option: with dh_shlibdeps: warning: ignored unknown options in DH_OPTIONS dh_clistrip Unknown option: with dh_clistrip: warning: ignored unknown options in DH_OPTIONS dh_cligacpolicy Unknown option: with dh_cligacpolicy: warning: ignored unknown options in DH_OPTIONS dh_cligacpolicy: Warning! No Build-Depends(-Indep) on cli-common-dev (>= 0.5.7)! debian/rules override_dh_makeclilibs make[1]: Entering directory `/build/buildd/docky-2.1.2' dh_makeclilibs -X usr/lib/docky/* Unknown option: with Unknown option: with dh_makeclilibs: warning: ignored unknown options in DH_OPTIONS make[1]: Leaving directory `/build/buildd/docky-2.1.2' dh_installcligac Unknown option: with dh_installcligac: warning: ignored unknown options in DH_OPTIONS dh_clideps Unknown option: with dh_clideps: warning: ignored unknown options in DH_OPTIONS dh_clideps: Warning: Could not resolve moduleref: libgio-2.0 for: Docky.Services.dll! dh_installdeb Unknown option: with dh_installdeb: warning: ignored unknown options in DH_OPTIONS dh_gencontrol Unknown option: with dh_gencontrol: warning: ignored unknown options in DH_OPTIONS dpkg-gencontrol: warning: Depends field of package docky: unknown substitution variable ${shlibs:Depends} dh_md5sums Unknown option: with dh_md5sums: warning: ignored unknown options in DH_OPTIONS dh_builddeb Unknown option: with dh_builddeb: warning: ignored unknown options in DH_OPTIONS INFO: pkgstriptranslations version 95 pkgstriptranslations: processing control file: ./debian/docky/DEBIAN/control, package docky, directory ./debian/docky ./debian/docky/usr/share/applications/docky.desktop: does not have gettext domain, not stripping pkgstriptranslations: preparing translation tarball docky_2.1.2-1_i386_translations.tar.gz...done (93 files) pkgmaintainermangler: Maintainer field overridden to "Ubuntu Developers " pkgstripfiles: processing control file: debian/docky/DEBIAN/control, package docky, directory debian/docky pkgstripfiles: Truncating changelog to topmost ten records OptiPNG 0.6.4: Advanced PNG optimizer. Copyright (C) 2001-2010 Cosmin Truta. ** Processing: ./usr/share/icons/hicolor/128x128/apps/gmail.png 128x128 pixels, 4x8 bits/pixel, RGB+alpha Input IDAT size = 16601 bytes Input file size = 16735 bytes Trying: zc = 9 zm = 8 zs = 0 f = 0 zc = 9 zm = 8 zs = 1 f = 0 zc = 1 zm = 8 zs = 2 f = 0 zc = 9 zm = 8 zs = 3 f = 0 zc = 9 zm = 8 zs = 0 f = 1 zc = 9 zm = 8 zs = 1 f = 1 zc = 1 zm = 8 zs = 2 f = 1 zc = 9 zm = 8 zs = 3 f = 1 zc = 9 zm = 8 zs = 0 f = 2 zc = 9 zm = 8 zs = 1 f = 2 zc = 1 zm = 8 zs = 2 f = 2 zc = 9 zm = 8 zs = 3 f = 2 zc = 9 zm = 8 zs = 0 f = 3 zc = 9 zm = 8 zs = 1 f = 3 zc = 1 zm = 8 zs = 2 f = 3 zc = 9 zm = 8 zs = 3 f = 3 zc = 9 zm = 8 zs = 0 f = 4 zc = 9 zm = 8 zs = 1 f = 4 IDAT size = 16431 zc = 1 zm = 8 zs = 2 f = 4 zc = 9 zm = 8 zs = 3 f = 4 zc = 9 zm = 8 zs = 0 f = 5 zc = 9 zm = 8 zs = 1 f = 5 IDAT size = 16345 zc = 1 zm = 8 zs = 2 f = 5 zc = 9 zm = 8 zs = 3 f = 5 Selecting parameters: zc = 9 zm = 8 zs = 1 f = 5 IDAT size = 16345 Output IDAT size = 16345 bytes (256 bytes decrease) Output file size = 16455 bytes (280 bytes = 1.67% decrease) 16455 16455 100% ./usr/share/icons/hicolor/128x128/apps/gmail.png (Bigger 18687) 16455 16455 100% OptiPNG 0.6.4: Advanced PNG optimizer. Copyright (C) 2001-2010 Cosmin Truta. ** Processing: ./usr/share/docky/poof.png 128x640 pixels, 4x8 bits/pixel, RGB+alpha Input IDAT size = 29276 bytes Input file size = 29443 bytes Trying: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 23917 zc = 9 zm = 8 zs = 1 f = 0 zc = 1 zm = 8 zs = 2 f = 0 zc = 9 zm = 8 zs = 3 f = 0 zc = 9 zm = 8 zs = 0 f = 1 zc = 9 zm = 8 zs = 1 f = 1 zc = 1 zm = 8 zs = 2 f = 1 zc = 9 zm = 8 zs = 3 f = 1 zc = 9 zm = 8 zs = 0 f = 2 zc = 9 zm = 8 zs = 1 f = 2 zc = 1 zm = 8 zs = 2 f = 2 zc = 9 zm = 8 zs = 3 f = 2 zc = 9 zm = 8 zs = 0 f = 3 zc = 9 zm = 8 zs = 1 f = 3 zc = 1 zm = 8 zs = 2 f = 3 zc = 9 zm = 8 zs = 3 f = 3 zc = 9 zm = 8 zs = 0 f = 4 zc = 9 zm = 8 zs = 1 f = 4 zc = 1 zm = 8 zs = 2 f = 4 zc = 9 zm = 8 zs = 3 f = 4 zc = 9 zm = 8 zs = 0 f = 5 zc = 9 zm = 8 zs = 1 f = 5 zc = 1 zm = 8 zs = 2 f = 5 zc = 9 zm = 8 zs = 3 f = 5 Selecting parameters: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 23917 Output IDAT size = 23917 bytes (5359 bytes decrease) Output file size = 24048 bytes (5395 bytes = 18.32% decrease) 24048 23278 96% ./usr/share/docky/poof.png 24048 23278 96% dpkg-deb: warning: 'debian/docky/DEBIAN/control' contains user-defined field 'Original-Maintainer' dpkg-deb: warning: ignoring 1 warning about the control file(s) dpkg-deb: building package `docky' in `../docky_2.1.2-1_all.deb'. dpkg-genchanges -b -mUbuntu/i386 Build Daemon >../docky_2.1.2-1_i386.changes dpkg-genchanges: binary-only upload - not including any source code dpkg-source --after-build docky-2.1.2 dpkg-buildpackage: binary only upload (no source included) ****************************************************************************** Build finished at 20110410-1837 Publishing chroot-autobuild/build/buildd/docky_2.1.2-1_i386_translations.tar.gz for rosetta. chroot-autobuild/build/buildd/docky_2.1.2-1_all.deb: new debian package, version 2.0. size 807232 bytes: control archive= 4884 bytes. 1994 bytes, 29 lines control 10117 bytes, 136 lines md5sums Package: docky Version: 2.1.2-1 Architecture: all Maintainer: Ubuntu Developers Original-Maintainer: Debian CLI Applications Team Installed-Size: 3496 Depends: mono-runtime (>= 1.1.8.1), libc6 (>= 2.12) | libc6.1 (>= 2.12) | libc0.1 (>= 2.12), libdbus-glib1.0-cil (>= 0.5), libdbus1.0-cil (>= 0.7), libgconf2.0-cil (>= 2.24.0), libgio-cil, libglib2.0-0 (>= 2.28.5), libglib2.0-cil (>= 2.12.10-1ubuntu1), libgnome-keyring1.0-cil (>= 1.0.0), libgnomedesktop2.20-cil (>= 2.26.0), libgtk2.0-0 (>= 2.23.90), libgtk2.0-cil (>= 2.12.10-1ubuntu1), libmono-addins0.2-cil (>= 0.4), libmono-cairo2.0-cil (>= 2.4), libmono-corlib2.0-cil (>= 2.6.3), libmono-posix2.0-cil (>= 2.4), libmono-sharpzip2.84-cil (>= 1.0), libmono-system-web2.0-cil (>= 1.9.1), libmono-system2.0-cil (>= 2.6.3), libnotify0.4-cil (>= 0.4.0~r2998), librsvg2-2.18-cil (>= 2.26.0), libwnck2.20-cil (>= 2.26.0), libx11-6, gconf2 (>= 2.28.1-2), librsvg2-common Recommends: dockmanager Conflicts: python-docky (<< 2.0.99) Replaces: python-docky (<< 2.0.99) Section: x11 Priority: optional Homepage: https://launchpad.net/docky Description: Elegant, powerful, clean dock A full fledged dock application that makes opening common applications and managing windows easier and quicker. Docky is fully integrated into the GNOME Desktop and features a no non-sense approach to configuration and usage. It just works. . Docky provides an application launcher, running application management, and various "docklets" including a CPU monitor, weather report and clock. It is similar to other docks such as AWN and cairo-dock. . Applications can integrate with Docky to add extra items to their context menus or modify their icons to display more information. This package includes integration helpers for a number of applications, including Banshee, Rhythmbox, Deluge, Tomboy and Zeitgeist. . Docky is derived from the GNOME Do "docky" interface. chroot-autobuild/build/buildd/docky_2.1.2-1_all.deb: drwxr-xr-x root/root 0 2011-04-10 18:37 ./ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/lib/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/lib/docky/ -rw-r--r-- root/root 223744 2011-04-10 18:37 ./usr/lib/docky/gio-sharp.dll -rw-r--r-- root/root 291 2011-04-10 18:37 ./usr/lib/docky/gio-sharp.dll.config -rw-r--r-- root/root 14336 2011-04-10 18:37 ./usr/lib/docky/Docky.CairoHelper.dll -rw-r--r-- root/root 154112 2011-04-10 18:37 ./usr/lib/docky/Docky.Services.dll -rw-r--r-- root/root 315 2011-04-10 18:37 ./usr/lib/docky/Docky.Services.dll.config -rw-r--r-- root/root 41472 2011-04-10 18:37 ./usr/lib/docky/Docky.Widgets.dll -rw-r--r-- root/root 204 2011-04-10 18:37 ./usr/lib/docky/Docky.Widgets.dll.config -rw-r--r-- root/root 102912 2011-04-10 18:37 ./usr/lib/docky/Docky.Items.dll -rw-r--r-- root/root 22528 2011-04-10 18:37 ./usr/lib/docky/Docky.DBus.dll drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/lib/docky/plugins/ -rw-r--r-- root/root 96768 2011-04-10 18:37 ./usr/lib/docky/plugins/BatteryMonitor.dll -rw-r--r-- root/root 10752 2011-04-10 18:37 ./usr/lib/docky/plugins/Bookmarks.dll -rw-r--r-- root/root 7168 2011-04-10 18:37 ./usr/lib/docky/plugins/Clippy.dll -rw-r--r-- root/root 20992 2011-04-10 18:37 ./usr/lib/docky/plugins/Clock.dll -rw-r--r-- root/root 89088 2011-04-10 18:37 ./usr/lib/docky/plugins/Desktop.dll -rw-r--r-- root/root 8704 2011-04-10 18:37 ./usr/lib/docky/plugins/CPUMonitor.dll -rw-r--r-- root/root 35840 2011-04-10 18:37 ./usr/lib/docky/plugins/GMail.dll -rw-r--r-- root/root 9728 2011-04-10 18:37 ./usr/lib/docky/plugins/Mounter.dll -rw-r--r-- root/root 32768 2011-04-10 18:37 ./usr/lib/docky/plugins/NetworkManager.dll -rw-r--r-- root/root 30208 2011-04-10 18:37 ./usr/lib/docky/plugins/NPR.dll -rw-r--r-- root/root 10752 2011-04-10 18:37 ./usr/lib/docky/plugins/RecentDocuments.dll -rw-r--r-- root/root 16384 2011-04-10 18:37 ./usr/lib/docky/plugins/SessionManager.dll -rw-r--r-- root/root 48640 2011-04-10 18:37 ./usr/lib/docky/plugins/Timer.dll -rw-r--r-- root/root 11264 2011-04-10 18:37 ./usr/lib/docky/plugins/Trash.dll -rw-r--r-- root/root 70656 2011-04-10 18:37 ./usr/lib/docky/plugins/Weather.dll -rw-r--r-- root/root 17408 2011-04-10 18:37 ./usr/lib/docky/plugins/WorkspaceSwitcher.dll -rw-r--r-- root/root 77 2011-04-10 18:37 ./usr/lib/docky/Docky.addins -rwxr-xr-x root/root 264704 2011-04-10 18:37 ./usr/lib/docky/Docky.exe drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/lib/pkgconfig/ -rw-r--r-- root/root 117 2011-04-10 18:37 ./usr/lib/pkgconfig/docky.cairohelper.pc -rw-r--r-- root/root 107 2011-04-10 18:37 ./usr/lib/pkgconfig/docky.services.pc -rw-r--r-- root/root 104 2011-04-10 18:37 ./usr/lib/pkgconfig/docky.widgets.pc -rw-r--r-- root/root 98 2011-04-10 18:37 ./usr/lib/pkgconfig/docky.items.pc drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/icons/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/icons/hicolor/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/icons/hicolor/16x16/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/icons/hicolor/16x16/apps/ -rw-r--r-- root/root 7203 2011-04-10 18:37 ./usr/share/icons/hicolor/16x16/apps/docky.svg drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/icons/hicolor/22x22/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/icons/hicolor/22x22/apps/ -rw-r--r-- root/root 14907 2011-04-10 18:37 ./usr/share/icons/hicolor/22x22/apps/docky.svg drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/icons/hicolor/24x24/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/icons/hicolor/24x24/apps/ -rw-r--r-- root/root 17892 2011-04-10 18:37 ./usr/share/icons/hicolor/24x24/apps/docky.svg drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/icons/hicolor/32x32/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/icons/hicolor/32x32/apps/ -rw-r--r-- root/root 21894 2011-04-10 18:37 ./usr/share/icons/hicolor/32x32/apps/docky.svg drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/icons/hicolor/48x48/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/icons/hicolor/48x48/apps/ -rw-r--r-- root/root 22112 2011-04-10 18:37 ./usr/share/icons/hicolor/48x48/apps/docky.svg drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/icons/hicolor/48x48/mimetypes/ -rw-r--r-- root/root 9379 2011-04-10 18:37 ./usr/share/icons/hicolor/48x48/mimetypes/extension.svg drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/icons/hicolor/64x64/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/icons/hicolor/64x64/apps/ -rw-r--r-- root/root 21866 2011-04-10 18:37 ./usr/share/icons/hicolor/64x64/apps/docky.svg drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/icons/hicolor/128x128/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/icons/hicolor/128x128/apps/ -rw-r--r-- root/root 32419 2011-04-10 18:37 ./usr/share/icons/hicolor/128x128/apps/docky.svg -rw-r--r-- root/root 16455 2011-04-10 18:37 ./usr/share/icons/hicolor/128x128/apps/gmail.png drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/docky/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/docky/themes/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/docky/themes/Grayscale/ -rw-r--r-- root/root 3501 2011-04-10 18:37 ./usr/share/docky/themes/Grayscale/background.svg -rw-r--r-- root/root 4373 2011-04-10 18:37 ./usr/share/docky/themes/Grayscale/badge.svg -rw-r--r-- root/root 4134 2011-04-10 18:37 ./usr/share/docky/themes/Grayscale/menu.svg -rw-r--r-- root/root 2765 2011-04-10 18:37 ./usr/share/docky/themes/Grayscale/tooltip.svg drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/docky/themes/Air/ -rw-r--r-- root/root 3305 2011-04-10 18:37 ./usr/share/docky/themes/Air/background.svg -rw-r--r-- root/root 2308 2011-04-10 18:37 ./usr/share/docky/themes/Air/badge.svg -rw-r--r-- root/root 4051 2011-04-10 18:37 ./usr/share/docky/themes/Air/menu.svg -rw-r--r-- root/root 1965 2011-04-10 18:37 ./usr/share/docky/themes/Air/stretch_separator.svg -rw-r--r-- root/root 2039 2011-04-10 18:37 ./usr/share/docky/themes/Air/tooltip.svg drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/docky/themes/Glass/ -rw-r--r-- root/root 2036 2011-04-10 18:37 ./usr/share/docky/themes/Glass/background.svg -rw-r--r-- root/root 2302 2011-04-10 18:37 ./usr/share/docky/themes/Glass/badge.svg -rw-r--r-- root/root 4047 2011-04-10 18:37 ./usr/share/docky/themes/Glass/menu.svg -rw-r--r-- root/root 1965 2011-04-10 18:37 ./usr/share/docky/themes/Glass/stretch_separator.svg -rw-r--r-- root/root 2765 2011-04-10 18:37 ./usr/share/docky/themes/Glass/tooltip.svg drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/docky/themes/HUD/ -rw-r--r-- root/root 2811 2011-04-10 18:37 ./usr/share/docky/themes/HUD/background.svg -rw-r--r-- root/root 3180 2011-04-10 18:37 ./usr/share/docky/themes/HUD/badge.svg -rw-r--r-- root/root 4047 2011-04-10 18:37 ./usr/share/docky/themes/HUD/menu.svg -rw-r--r-- root/root 3073 2011-04-10 18:37 ./usr/share/docky/themes/HUD/tooltip.svg drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/docky/themes/Matte/ -rw-r--r-- root/root 4287 2011-04-10 18:37 ./usr/share/docky/themes/Matte/background.svg -rw-r--r-- root/root 7201 2011-04-10 18:37 ./usr/share/docky/themes/Matte/menu.svg -rw-r--r-- root/root 9164 2011-04-10 18:37 ./usr/share/docky/themes/Matte/tooltip.svg drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/docky/themes/Smoke/ -rw-r--r-- root/root 3632 2011-04-10 18:37 ./usr/share/docky/themes/Smoke/background.svg -rw-r--r-- root/root 2972 2011-04-10 18:37 ./usr/share/docky/themes/Smoke/badge.svg -rw-r--r-- root/root 3469 2011-04-10 18:37 ./usr/share/docky/themes/Smoke/menu.svg -rw-r--r-- root/root 815 2011-04-10 18:37 ./usr/share/docky/themes/Smoke/stretch_separator.svg -rw-r--r-- root/root 2781 2011-04-10 18:37 ./usr/share/docky/themes/Smoke/tooltip.svg drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/docky/themes/Transparent/ -rw-r--r-- root/root 3006 2011-04-10 18:37 ./usr/share/docky/themes/Transparent/background.svg -rw-r--r-- root/root 23278 2011-04-10 18:37 ./usr/share/docky/poof.png -rw-r--r-- root/root 8285 2011-04-10 18:37 ./usr/share/docky/sun.svg -rw-r--r-- root/root 35181 2011-04-10 18:37 ./usr/share/docky/wind.svg -rw-r--r-- root/root 12753 2011-04-10 18:37 ./usr/share/docky/temp.svg -rw-r--r-- root/root 358 2011-04-10 18:37 ./usr/share/docky/remaps.ini drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/docky/ClockTheme/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/docky/ClockTheme/default/ -rw-r--r-- root/root 4434 2011-04-10 18:37 ./usr/share/docky/ClockTheme/default/clock-drop-shadow.svg -rw-r--r-- root/root 3840 2011-04-10 18:37 ./usr/share/docky/ClockTheme/default/clock-face.svg -rw-r--r-- root/root 3962 2011-04-10 18:37 ./usr/share/docky/ClockTheme/default/clock-glass.svg -rw-r--r-- root/root 4195 2011-04-10 18:37 ./usr/share/docky/ClockTheme/default/clock-face-shadow.svg -rw-r--r-- root/root 6819 2011-04-10 18:37 ./usr/share/docky/ClockTheme/default/clock-frame.svg -rw-r--r-- root/root 49924 2011-04-10 18:37 ./usr/share/docky/ClockTheme/default/clock-marks.svg drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/docky/ClockTheme/default-24/ -rw-r--r-- root/root 4080 2011-04-10 18:37 ./usr/share/docky/ClockTheme/default-24/clock-drop-shadow.svg -rw-r--r-- root/root 3840 2011-04-10 18:37 ./usr/share/docky/ClockTheme/default-24/clock-face.svg -rw-r--r-- root/root 3962 2011-04-10 18:37 ./usr/share/docky/ClockTheme/default-24/clock-glass.svg -rw-r--r-- root/root 4195 2011-04-10 18:37 ./usr/share/docky/ClockTheme/default-24/clock-face-shadow.svg -rw-r--r-- root/root 6819 2011-04-10 18:37 ./usr/share/docky/ClockTheme/default-24/clock-frame.svg -rw-r--r-- root/root 51016 2011-04-10 18:37 ./usr/share/docky/ClockTheme/default-24/clock-marks.svg drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/applications/ -rw-r--r-- root/root 1739 2011-04-10 18:37 ./usr/share/applications/docky.desktop drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/ast/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/ast/LC_MESSAGES/ -rw-r--r-- root/root 11051 2011-04-10 18:37 ./usr/share/locale/ast/LC_MESSAGES/docky.mo drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/bg/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/bg/LC_MESSAGES/ -rw-r--r-- root/root 16430 2011-04-10 18:37 ./usr/share/locale/bg/LC_MESSAGES/docky.mo drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/bn/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/bn/LC_MESSAGES/ -rw-r--r-- root/root 5914 2011-04-10 18:37 ./usr/share/locale/bn/LC_MESSAGES/docky.mo drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/ca/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/ca/LC_MESSAGES/ -rw-r--r-- root/root 8931 2011-04-10 18:37 ./usr/share/locale/ca/LC_MESSAGES/docky.mo drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/cs/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/cs/LC_MESSAGES/ -rw-r--r-- root/root 20624 2011-04-10 18:37 ./usr/share/locale/cs/LC_MESSAGES/docky.mo drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/da/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/da/LC_MESSAGES/ -rw-r--r-- root/root 11684 2011-04-10 18:37 ./usr/share/locale/da/LC_MESSAGES/docky.mo drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/de/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/de/LC_MESSAGES/ -rw-r--r-- root/root 29953 2011-04-10 18:37 ./usr/share/locale/de/LC_MESSAGES/docky.mo drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/el/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/el/LC_MESSAGES/ -rw-r--r-- root/root 10776 2011-04-10 18:37 ./usr/share/locale/el/LC_MESSAGES/docky.mo drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/en_GB/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/en_GB/LC_MESSAGES/ -rw-r--r-- root/root 13940 2011-04-10 18:37 ./usr/share/locale/en_GB/LC_MESSAGES/docky.mo drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/es/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/es/LC_MESSAGES/ -rw-r--r-- root/root 30006 2011-04-10 18:37 ./usr/share/locale/es/LC_MESSAGES/docky.mo drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/et/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/et/LC_MESSAGES/ -rw-r--r-- root/root 11426 2011-04-10 18:37 ./usr/share/locale/et/LC_MESSAGES/docky.mo drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/eu/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/eu/LC_MESSAGES/ -rw-r--r-- root/root 16477 2011-04-10 18:37 ./usr/share/locale/eu/LC_MESSAGES/docky.mo drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/fi/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/fi/LC_MESSAGES/ -rw-r--r-- root/root 19306 2011-04-10 18:37 ./usr/share/locale/fi/LC_MESSAGES/docky.mo drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/fil/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/fil/LC_MESSAGES/ -rw-r--r-- root/root 2146 2011-04-10 18:37 ./usr/share/locale/fil/LC_MESSAGES/docky.mo drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/fo/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/fo/LC_MESSAGES/ -rw-r--r-- root/root 4980 2011-04-10 18:37 ./usr/share/locale/fo/LC_MESSAGES/docky.mo drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/fr/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/fr/LC_MESSAGES/ -rw-r--r-- root/root 23447 2011-04-10 18:37 ./usr/share/locale/fr/LC_MESSAGES/docky.mo drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/gl/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/gl/LC_MESSAGES/ -rw-r--r-- root/root 15076 2011-04-10 18:37 ./usr/share/locale/gl/LC_MESSAGES/docky.mo drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/he/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/he/LC_MESSAGES/ -rw-r--r-- root/root 14944 2011-04-10 18:37 ./usr/share/locale/he/LC_MESSAGES/docky.mo drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/hi/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/hi/LC_MESSAGES/ -rw-r--r-- root/root 1259 2011-04-10 18:37 ./usr/share/locale/hi/LC_MESSAGES/docky.mo drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/hr/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/hr/LC_MESSAGES/ -rw-r--r-- root/root 12738 2011-04-10 18:37 ./usr/share/locale/hr/LC_MESSAGES/docky.mo drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/hu/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/hu/LC_MESSAGES/ -rw-r--r-- root/root 15541 2011-04-10 18:37 ./usr/share/locale/hu/LC_MESSAGES/docky.mo drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/id/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/id/LC_MESSAGES/ -rw-r--r-- root/root 5818 2011-04-10 18:37 ./usr/share/locale/id/LC_MESSAGES/docky.mo drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/is/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/is/LC_MESSAGES/ -rw-r--r-- root/root 7187 2011-04-10 18:37 ./usr/share/locale/is/LC_MESSAGES/docky.mo drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/it/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/it/LC_MESSAGES/ -rw-r--r-- root/root 15027 2011-04-10 18:37 ./usr/share/locale/it/LC_MESSAGES/docky.mo drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/ja/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/ja/LC_MESSAGES/ -rw-r--r-- root/root 17240 2011-04-10 18:37 ./usr/share/locale/ja/LC_MESSAGES/docky.mo drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/kk/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/kk/LC_MESSAGES/ -rw-r--r-- root/root 2689 2011-04-10 18:37 ./usr/share/locale/kk/LC_MESSAGES/docky.mo drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/ko/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/ko/LC_MESSAGES/ -rw-r--r-- root/root 15513 2011-04-10 18:37 ./usr/share/locale/ko/LC_MESSAGES/docky.mo drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/lt/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/lt/LC_MESSAGES/ -rw-r--r-- root/root 19469 2011-04-10 18:37 ./usr/share/locale/lt/LC_MESSAGES/docky.mo drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/nb/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/nb/LC_MESSAGES/ -rw-r--r-- root/root 14445 2011-04-10 18:37 ./usr/share/locale/nb/LC_MESSAGES/docky.mo drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/nl/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/nl/LC_MESSAGES/ -rw-r--r-- root/root 15406 2011-04-10 18:37 ./usr/share/locale/nl/LC_MESSAGES/docky.mo drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/nn/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/nn/LC_MESSAGES/ -rw-r--r-- root/root 14214 2011-04-10 18:37 ./usr/share/locale/nn/LC_MESSAGES/docky.mo drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/pl/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/pl/LC_MESSAGES/ -rw-r--r-- root/root 14817 2011-04-10 18:37 ./usr/share/locale/pl/LC_MESSAGES/docky.mo drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/pt/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/pt/LC_MESSAGES/ -rw-r--r-- root/root 23297 2011-04-10 18:37 ./usr/share/locale/pt/LC_MESSAGES/docky.mo drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/pt_BR/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/pt_BR/LC_MESSAGES/ -rw-r--r-- root/root 14842 2011-04-10 18:37 ./usr/share/locale/pt_BR/LC_MESSAGES/docky.mo drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/ro/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/ro/LC_MESSAGES/ -rw-r--r-- root/root 29961 2011-04-10 18:37 ./usr/share/locale/ro/LC_MESSAGES/docky.mo drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/ru/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/ru/LC_MESSAGES/ -rw-r--r-- root/root 34951 2011-04-10 18:37 ./usr/share/locale/ru/LC_MESSAGES/docky.mo drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/sk/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/sk/LC_MESSAGES/ -rw-r--r-- root/root 14782 2011-04-10 18:37 ./usr/share/locale/sk/LC_MESSAGES/docky.mo drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/sl/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/sl/LC_MESSAGES/ -rw-r--r-- root/root 15071 2011-04-10 18:37 ./usr/share/locale/sl/LC_MESSAGES/docky.mo drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/sr/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/sr/LC_MESSAGES/ -rw-r--r-- root/root 37599 2011-04-10 18:37 ./usr/share/locale/sr/LC_MESSAGES/docky.mo drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/sv/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/sv/LC_MESSAGES/ -rw-r--r-- root/root 14752 2011-04-10 18:37 ./usr/share/locale/sv/LC_MESSAGES/docky.mo drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/tr/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/tr/LC_MESSAGES/ -rw-r--r-- root/root 23516 2011-04-10 18:37 ./usr/share/locale/tr/LC_MESSAGES/docky.mo drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/uk/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/uk/LC_MESSAGES/ -rw-r--r-- root/root 21508 2011-04-10 18:37 ./usr/share/locale/uk/LC_MESSAGES/docky.mo drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/vi/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/vi/LC_MESSAGES/ -rw-r--r-- root/root 1319 2011-04-10 18:37 ./usr/share/locale/vi/LC_MESSAGES/docky.mo drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/zh_CN/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/zh_CN/LC_MESSAGES/ -rw-r--r-- root/root 14069 2011-04-10 18:37 ./usr/share/locale/zh_CN/LC_MESSAGES/docky.mo drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/zh_HK/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/zh_HK/LC_MESSAGES/ -rw-r--r-- root/root 12318 2011-04-10 18:37 ./usr/share/locale/zh_HK/LC_MESSAGES/docky.mo drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/zh_TW/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/locale/zh_TW/LC_MESSAGES/ -rw-r--r-- root/root 15746 2011-04-10 18:37 ./usr/share/locale/zh_TW/LC_MESSAGES/docky.mo drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/man/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/man/man1/ -rw-r--r-- root/root 642 2011-04-10 18:37 ./usr/share/man/man1/docky.1.gz drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/doc/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/doc/docky/ -rw-r--r-- root/root 2861 2011-04-09 10:00 ./usr/share/doc/docky/copyright -rw-r--r-- root/root 2767 2011-04-10 18:37 ./usr/share/doc/docky/changelog.Debian.gz drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/gconf/ drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/share/gconf/schemas/ -rw-r--r-- root/root 133296 2011-04-10 18:37 ./usr/share/gconf/schemas/docky.schemas drwxr-xr-x root/root 0 2011-04-10 18:37 ./usr/bin/ -rwxr-xr-x root/root 399 2011-04-10 18:37 ./usr/bin/docky docky_2.1.2-1_i386.changes: Format: 1.8 Date: Wed, 06 Apr 2011 19:45:56 +0200 Source: docky Binary: docky Architecture: all i386_translations Version: 2.1.2-1 Distribution: natty Urgency: low Maintainer: Ubuntu/i386 Build Daemon Changed-By: Rico Tzschichholz Description: docky - Elegant, powerful, clean dock Launchpad-Bugs-Fixed: 574817 708772 738955 Changes: docky (2.1.2-1) experimental; urgency=low . * New upstream release 2.1.2 "Docks love Mono", changes include: + fix drawing with mono 2.10+ + fix problem with curtain when struts are set + fix crash when drag/droping onto docky and nautilus isnt drawing desktop (LP: #574817) + fix nm docklet crashing docky on startup if nm isnt running (LP: #738955) + fix item-drop at the first place (LP: #708772) Checksums-Sha1: 9a477004c1fb55e3d4889b406eafa71008559a72 807232 docky_2.1.2-1_all.deb 5a1d2ae5bdea614751e98b43454d92eeb7548b84 643239 docky_2.1.2-1_i386_translations.tar.gz Checksums-Sha256: 8e2002a8e714322fccabb73f4682fad10f597fb96e2fc0d94553977580297883 807232 docky_2.1.2-1_all.deb 63104c00bb68b339818f5241f0f87a406ad6b72dca602139deb21e3a5b65293a 643239 docky_2.1.2-1_i386_translations.tar.gz Files: 8599fa5a5d564fd297931b002471fe25 807232 x11 optional docky_2.1.2-1_all.deb d2bd6c7555d8d152632abe9a3db24242 643239 raw-translations - docky_2.1.2-1_i386_translations.tar.gz ****************************************************************************** Built successfully Purging chroot-autobuild/build/buildd/docky-2.1.2 ------------------------------------------------------------------------------ /usr/bin/sudo dpkg --purge groff-base libavahi-common3 libx11-data libgnome2-0 m4 mono-devel x11-common libdbus1.0-cil libidl-dev libvorbis0a libxi6 automake libmono2.0-cil libmono-cecil-private-cil libmono0 libxcursor1 libdbus1.0-cil-dev x11proto-input-dev libxml-sax-perl libexpat1-dev libgnome2.24-cil libart2.0-cil-dev libmono-i18n-west1.0-cil libmono-i18n2.0-cil libdbus-glib-1-2 libmono-npgsql1.0-cil libmono-sharpzip2.84-cil libmono-debugger-soft0.0-cil libmono-npgsql2.0-cil libx11-6 libmono-winforms2.0-cil xtrans-dev libmono-addins0.2-cil cli-common-dev xorg-sgml-doctools libgif4 libmono-corlib1.0-cil libxdamage1 libnotify0.4-cil libmono-system-runtime1.0-cil libmono-accessibility2.0-cil libdbus-1-dev libmono-posix2.0-cil libhtml-tree-perl libmono-ldap1.0-cil libmono-bytefx0.7.6.1-cil libglib2.0-dev libmono-oracle1.0-cil x11proto-xext-dev pkg-config libmono-microsoft-build2.0-cil librsvg2-2.0-cil-dev libmono-relaxng1.0-cil libxml-namespacesupport-perl libmono-sharpzip2.6-cil libxrender1 libfontconfig1-dev libpython2.7 libglib2.0-cil libxrandr-dev libcups2 libxau-dev libdatrie1 libgnome-keyring1.0-cil-dev libmono-system2.0-cil libmono-addins-gui-cil-dev libpng12-dev libxft2 libxext6 libpipeline1 libgnomedesktop2.20-cil libmono-messaging2.0-cil libltdl7 libasound2 libsqlite3-0 libxml-perl libbonobo2-0 libxcb-aux0 libmono-system-runtime2.0-cil libmono-c5-1.1-cil libcairo2-dev libgail18 libexif12 fontconfig liburi-perl libmono-sharpzip0.84-cil libstartup-notification0 mono-gac libcroco3 libgamin0 libgnomeui-0 libfreetype6 libmono-security2.0-cil libgtk2.0-cil libatk1.0-0 libmono-addins-gui0.2-cil python2.7 libglade2.0-cil x11proto-damage-dev libidl0 libxcb1 libmono1.0-cil html2text libxrandr2 debhelper libthai0 python libnunit2.4-cil libart2.0-cil libgnome-keyring0 libmagic1 mono-runtime libtiff4 libexpat1 libxau6 libpango1.0-dev mono-gmcs libxcomposite1 x11proto-composite-dev libgconf2-4 mono-2.0-gac mime-support libcanberra0 libmono-dev libgconf2.0-cil libxi-dev gamin libwww-perl shared-mime-info libxfixes3 libgtk2.0-dev libwnck2.20-cil libmono-system-data1.0-cil libavahi-glib1 x11proto-kb-dev x11proto-xinerama-dev libpthread-stubs0-dev libpango1.0-0 libdbus-glib1.0-cil-dev libmono-management2.0-cil libgnomeui-common gettext-base libmono-cscompmgd8.0-cil libunistring0 libmono-security1.0-cil libmono-corlib2.0-cil libgnomevfs2-0 libgio-cil libxcb-render0 libmono-data2.0-cil libxres1 libglib2.0-bin libxfixes-dev fontconfig-config libgconf2-dev file gettext libmono-sqlite2.0-cil zlib1g-dev libhtml-parser-perl libmono-sqlite1.0-cil libmono-system-web-mvc1.0-cil librsvg2-2.18-cil libmono-bytefx0.7.6.2-cil libmono-peapi2.0-cil libcairo2 libgdiplus libmono-accessibility1.0-cil libmono-rabbitmq2.0-cil libcairo-gobject2 libx11-dev libatk1.0-data libwnck22 libgnome-vfs2.0-cil-dev libjpeg62 libbonobo2-common libbonoboui2-common libmono-cil-dev libxml-dom-perl libmono-sharpzip0.6-cil libmono-windowsbase3.0-cil libxcb-event1 cli-common libmono-webbrowser0.5-cil libnunit-cil-dev libgdk-pixbuf2.0-0 libjasper1 libmono-system-web1.0-cil libpixman-1-dev libgnome-keyring1.0-cil libxcomposite-dev libxml-libxml-perl libfontconfig1 libmono-posix1.0-cil libart-2.0-2 libxml-regexp-perl libxcb-shm0-dev x11proto-randr-dev psmisc libxinerama-dev libmono-simd2.0-cil libglib2.0-data libgnome2.0-cil-dev libmono-system-web-mvc2.0-cil libglib2.0-cil-dev libxml2-utils libgdk-pixbuf2.0-dev libmono-winforms1.0-cil gconf2 libhtml-tagset-perl libxml2 dbus libmono-ldap2.0-cil libgio2.0-cil-dev libthai-data libdbus-glib1.0-cil libice6 intltool-debian libavahi-client3 libmono-microsoft7.0-cil libmono-system-data2.0-cil liborbit2-dev libmono-cairo2.0-cil mono-2.0-devel libxext-dev libmono-system-web2.0-cil libmono-system-data-linq2.0-cil libxrender-dev libgnomedesktop2.0-cil-dev libmono-microsoft8.0-cil libavahi-common-data x11proto-render-dev libmono-messaging-rabbitmq2.0-cil libmono-addins-cil-dev libmono-tasklets2.0-cil libmono-cscompmgd7.0-cil libxinerama1 libmono-getoptions1.0-cil libsm-dev libxdamage-dev gconf2-common libnotify-cil-dev libgnomevfs2-common libxdmcp-dev ttf-dejavu-core libgnomecanvas2-0 librsvg2-2 libmono-i18n-west2.0-cil libmono-oracle2.0-cil libxcb-render0-dev libndesk-dbus-glib1.0-cil autotools-dev liborbit2 mono-utils libpopt0 libmono-system-messaging2.0-cil libwnck-common libice-dev libmono-i18n1.0-cil libvorbisfile3 x11proto-fixes-dev libfreetype6-dev libgtk2.0-0 libgnome-desktop-2-17 libxcb-atom1 libmono-data-tds2.0-cil libglade2-0 libmono-relaxng2.0-cil libmono-system-ldap1.0-cil libpthread-stubs0 libgnomecanvas2-common libxcb-shm0 gnome-mime-data libmono-data-tds1.0-cil bsdmainutils libtdb1 libxcursor-dev libmono-system-messaging1.0-cil x11proto-core-dev libmono-system-ldap2.0-cil intltool libmono-peapi1.0-cil libogg0 libxcb1-dev libgnome2-common libxdmcp6 po-debconf libatk1.0-dev libxml-parser-perl libmono-system1.0-cil libxft-dev libgconf2.0-cil-dev man-db dbus-x11 libmono-wcf3.0-cil libpixman-1-0 libbonoboui2-0 libndesk-dbus1.0-cil ucf gtk-sharp2-gapi libgtk2.0-common libgnome-vfs2.0-cil libsqlite0 libmono-data1.0-cil libwnck1.0-cil-dev libsm6 libgtk2.0-cil-dev libcairo-script-interpreter2 libmono-getoptions2.0-cil libmono-cairo1.0-cil autoconf libmono-db2-1.0-cil (Reading database ... 22694 files and directories currently installed.) Removing cli-common-dev ... Removing librsvg2-2.0-cil-dev ... Removing libgnome-keyring1.0-cil-dev ... Removing libmono-addins-gui-cil-dev ... Removing libmono-addins-gui0.2-cil ... Removing libmono-addins-gui0.2-cil from Mono Removing debhelper ... Removing libgtk2.0-dev ... Removing libdbus-glib1.0-cil-dev ... Removing libgconf2-dev ... Removing librsvg2-2.18-cil ... Removing librsvg2-2.18-cil from Mono Removing libxml-dom-perl ... Removing libgnome-keyring1.0-cil ... Removing libgnome-keyring1.0-cil from Mono Removing libxcomposite-dev ... Removing libxml-regexp-perl ... Removing libxinerama-dev ... Removing libxml2-utils ... Removing libgdk-pixbuf2.0-dev ... Removing libgio2.0-cil-dev ... Removing libdbus-glib1.0-cil ... Removing libdbus-glib1.0-cil from Mono Removing liborbit2-dev ... Removing libgnomedesktop2.0-cil-dev ... Removing libmono-addins-cil-dev ... Removing libxdamage-dev ... Removing libnotify-cil-dev ... Removing librsvg2-2 ... Purging configuration files for librsvg2-2 ... Removing mono-utils ... Removing libxcursor-dev ... Removing intltool ... Removing po-debconf ... Removing libatk1.0-dev ... Removing libgconf2.0-cil-dev ... Removing man-db ... Purging configuration files for man-db ... Removing catpages as well as /var/cache/man hierarchy. Removing gtk-sharp2-gapi ... Removing libwnck1.0-cil-dev ... Removing groff-base ... Purging configuration files for groff-base ... Removing mono-devel ... Removing libidl-dev ... Removing automake ... Removing libdbus1.0-cil-dev ... Removing libmono-addins0.2-cil ... Removing libmono-addins0.2-cil from Mono Removing libnotify0.4-cil ... Removing libnotify0.4-cil from Mono Removing libdbus-1-dev ... Removing libxrandr-dev ... Removing libpipeline1 ... Purging configuration files for libpipeline1 ... Removing libgnomedesktop2.20-cil ... Removing libgnomedesktop2.20-cil from Mono Removing libxml-perl ... Removing x11proto-damage-dev ... Removing html2text ... Purging configuration files for html2text ... Removing libpango1.0-dev ... Removing x11proto-composite-dev ... Removing libxi-dev ... Removing libwnck2.20-cil ... Removing libwnck2.20-cil from Mono Removing x11proto-xinerama-dev ... Removing libgio-cil ... Removing libxfixes-dev ... Removing file ... Removing libwnck22 ... Purging configuration files for libwnck22 ... Removing libmono-cil-dev ... Removing libmono-sharpzip0.6-cil ... Removing libmono-windowsbase3.0-cil ... Removing libnunit-cil-dev ... Removing libxml-libxml-perl ... update-perl-sax-parsers: Unregistering Perl SAX parser XML::LibXML::SAX::Parser with priority 50... update-perl-sax-parsers: Unregistering Perl SAX parser XML::LibXML::SAX with priority 50... update-perl-sax-parsers: Updating overall Perl SAX parser modules info file... Replacing config file /etc/perl/XML/SAX/ParserDetails.ini with new version Removing x11proto-randr-dev ... Removing libmono-simd2.0-cil ... Removing libgnome2.0-cil-dev ... Removing libmono-system-web-mvc2.0-cil ... Removing libmono-winforms1.0-cil ... Removing intltool-debian ... Removing libmono-microsoft7.0-cil ... Removing mono-2.0-devel ... Purging configuration files for mono-2.0-devel ... Removing libxext-dev ... Removing libmono-microsoft8.0-cil ... Removing libmono-messaging-rabbitmq2.0-cil ... Removing libmono-tasklets2.0-cil ... Removing libmono-cscompmgd7.0-cil ... Removing libmono-getoptions1.0-cil ... Removing libmono-oracle2.0-cil ... Removing libndesk-dbus-glib1.0-cil ... Removing libndesk-dbus-glib1.0-cil from Mono Removing autotools-dev ... Removing libwnck-common ... Removing libmono-i18n1.0-cil ... Removing x11proto-fixes-dev ... Removing libgnome-desktop-2-17 ... Purging configuration files for libgnome-desktop-2-17 ... Removing libmono-relaxng2.0-cil ... Removing libmono-system-ldap1.0-cil ... Removing bsdmainutils ... Purging configuration files for bsdmainutils ... Removing libmono-system-messaging1.0-cil ... Removing libmono-system-ldap2.0-cil ... Removing libmono-peapi1.0-cil ... Removing libxml-parser-perl ... Removing libxft-dev ... Removing libndesk-dbus1.0-cil ... Removing libndesk-dbus1.0-cil from Mono Removing libmono-data1.0-cil ... Removing libgtk2.0-cil-dev ... Removing libmono-getoptions2.0-cil ... Removing libmono-cairo1.0-cil ... Removing autoconf ... Purging configuration files for autoconf ... Removing libmono-db2-1.0-cil ... Removing m4 ... Removing libdbus1.0-cil ... Removing libdbus1.0-cil from Mono Removing libxml-sax-perl ... update-perl-sax-parsers: Unregistering Perl SAX parser XML::SAX::PurePerl with priority 50... update-perl-sax-parsers: Updating overall Perl SAX parser modules info file... Purging configuration files for libxml-sax-perl ... Removing libgnome2.24-cil ... Removing libgnome2.24-cil from Mono Removing libart2.0-cil-dev ... Removing libmono-i18n-west1.0-cil ... Removing libmono-i18n2.0-cil ... Removing libmono-npgsql1.0-cil ... Removing libmono-debugger-soft0.0-cil ... Removing libmono-npgsql2.0-cil ... Removing libmono-winforms2.0-cil ... Removing xorg-sgml-doctools ... Removing libmono-system-runtime1.0-cil ... Removing libmono-accessibility2.0-cil ... Removing libmono-ldap1.0-cil ... Removing libmono-bytefx0.7.6.1-cil ... Removing libmono-oracle1.0-cil ... Removing x11proto-xext-dev ... Removing libmono-microsoft-build2.0-cil ... Removing libmono-relaxng1.0-cil ... Removing libxml-namespacesupport-perl ... Removing libmono-sharpzip2.6-cil ... Removing libmono-c5-1.1-cil ... Removing libcairo2-dev ... Removing libstartup-notification0 ... Purging configuration files for libstartup-notification0 ... Removing libgnomeui-0 ... Purging configuration files for libgnomeui-0 ... Removing libglade2.0-cil ... Removing libglade2.0-cil from Mono Purging configuration files for libglade2.0-cil ... Removing libmono1.0-cil ... Removing libnunit2.4-cil ... Removing libnunit2.4-cil from Mono Removing libart2.0-cil ... Removing libart2.0-cil from Mono Removing libgnome-keyring0 ... Purging configuration files for libgnome-keyring0 ... Removing libmagic1 ... Purging configuration files for libmagic1 ... Removing mono-gmcs ... Removing libmono-dev ... Removing libgconf2.0-cil ... Removing libgconf2.0-cil from Mono Removing libwww-perl ... Removing libmono-management2.0-cil ... Removing libgnomeui-common ... Removing libmono-cscompmgd8.0-cil ... Removing libmono-data2.0-cil ... Removing libxres1 ... Purging configuration files for libxres1 ... Removing gettext ... Removing libmono-sqlite1.0-cil ... Removing libmono-system-web-mvc1.0-cil ... Removing libmono-bytefx0.7.6.2-cil ... Removing libmono-peapi2.0-cil ... Removing libmono-accessibility1.0-cil ... Removing libmono-rabbitmq2.0-cil ... Removing libcairo-gobject2 ... Purging configuration files for libcairo-gobject2 ... Removing libgnome-vfs2.0-cil-dev ... Removing libxcb-event1 ... Purging configuration files for libxcb-event1 ... Removing libmono-webbrowser0.5-cil ... Removing libmono-system-web1.0-cil ... Removing libpixman-1-dev ... Removing libmono-posix1.0-cil ... Removing libxcb-shm0-dev ... Removing libglib2.0-cil-dev ... Removing libmono-ldap2.0-cil ... Removing libxrender-dev ... Removing x11proto-render-dev ... Removing libsm-dev ... Removing libmono-i18n-west2.0-cil ... Removing libxcb-render0-dev ... Removing libice-dev ... Removing libxcb-atom1 ... Purging configuration files for libxcb-atom1 ... Removing libbonoboui2-0 ... Purging configuration files for libbonoboui2-0 ... Removing libgnome-vfs2.0-cil ... Removing libgnome-vfs2.0-cil from Mono Removing libsm6 ... Purging configuration files for libsm6 ... Removing libcairo-script-interpreter2 ... Purging configuration files for libcairo-script-interpreter2 ... Removing libgnome2-0 ... Purging configuration files for libgnome2-0 ... Removing libmono-cecil-private-cil ... Removing libmono0 ... Purging configuration files for libmono0 ... Removing libhtml-tree-perl ... Removing libglib2.0-dev ... Removing libfontconfig1-dev ... Removing libpng12-dev ... Removing libbonobo2-0 ... Purging configuration files for libbonobo2-0 ... Removing libxcb-aux0 ... Purging configuration files for libxcb-aux0 ... Removing libmono-system-runtime2.0-cil ... Removing libmono-sharpzip0.84-cil ... Removing libcroco3 ... Purging configuration files for libcroco3 ... Removing libgtk2.0-cil ... Removing libgtk2.0-cil from Mono Purging configuration files for libgtk2.0-cil ... Removing libcanberra0 ... Purging configuration files for libcanberra0 ... Removing libmono-system-data1.0-cil ... Removing gettext-base ... Removing libunistring0 ... Purging configuration files for libunistring0 ... Removing libgnomevfs2-0 ... Purging configuration files for libgnomevfs2-0 ... Removing libglib2.0-bin ... Removing libhtml-parser-perl ... Removing libx11-dev ... Removing libbonobo2-common ... Purging configuration files for libbonobo2-common ... Removing libbonoboui2-common ... Removing libglib2.0-data ... Removing libhtml-tagset-perl ... Removing libice6 ... Purging configuration files for libice6 ... Removing libmono-cairo2.0-cil ... Removing libgnomevfs2-common ... Purging configuration files for libgnomevfs2-common ... Removing libgnomecanvas2-0 ... Purging configuration files for libgnomecanvas2-0 ... Removing libvorbisfile3 ... Purging configuration files for libvorbisfile3 ... Removing libfreetype6-dev ... Removing libglade2-0 ... Purging configuration files for libglade2-0 ... Removing libgnomecanvas2-common ... Removing gnome-mime-data ... Purging configuration files for gnome-mime-data ... Removing libmono-data-tds1.0-cil ... Removing libtdb1 ... Purging configuration files for libtdb1 ... Removing libxcb1-dev ... Removing libgnome2-common ... Purging configuration files for libgnome2-common ... Removing libvorbis0a ... Purging configuration files for libvorbis0a ... Removing x11proto-input-dev ... Removing libexpat1-dev ... Removing xtrans-dev ... Removing pkg-config ... Removing libglib2.0-cil ... Removing libglib2.0-cil from Mono Purging configuration files for libglib2.0-cil ... Removing libxau-dev ... Removing libltdl7 ... Purging configuration files for libltdl7 ... Removing libasound2 ... Purging configuration files for libasound2 ... Removing libgail18 ... Purging configuration files for libgail18 ... Removing liburi-perl ... Removing libavahi-glib1 ... Purging configuration files for libavahi-glib1 ... Removing x11proto-kb-dev ... Removing libpthread-stubs0-dev ... Removing libmono-security1.0-cil ... Removing zlib1g-dev ... Removing cli-common ... Removing libart-2.0-2 ... Purging configuration files for libart-2.0-2 ... Removing gconf2 ... Purging configuration files for gconf2 ... Removing libxdmcp-dev ... Removing libpopt0 ... Purging configuration files for libpopt0 ... Removing libgtk2.0-0 ... Purging configuration files for libgtk2.0-0 ... dpkg: warning: while removing libgtk2.0-0, directory '/usr/lib/gtk-2.0/2.10.0' not empty so not removed. dpkg: warning: while removing libgtk2.0-0, directory '/usr/lib/gtk-2.0' not empty so not removed. Removing libpthread-stubs0 ... Removing x11proto-core-dev ... Removing libogg0 ... Purging configuration files for libogg0 ... Removing libmono-system1.0-cil ... Removing dbus-x11 ... Purging configuration files for dbus-x11 ... Removing libgtk2.0-common ... Removing x11-common ... Purging configuration files for x11-common ... Removing libxi6 ... Purging configuration files for libxi6 ... Removing libxcursor1 ... Purging configuration files for libxcursor1 ... Removing libmono-corlib1.0-cil ... Removing libxdamage1 ... Purging configuration files for libxdamage1 ... Removing libpython2.7 ... Purging configuration files for libpython2.7 ... Removing libcups2 ... Purging configuration files for libcups2 ... Removing libatk1.0-0 ... Purging configuration files for libatk1.0-0 ... Removing libxrandr2 ... Purging configuration files for libxrandr2 ... Removing python ... Purging configuration files for python ... Removing libxcomposite1 ... Purging configuration files for libxcomposite1 ... Removing libgconf2-4 ... Purging configuration files for libgconf2-4 ... Removing shared-mime-info ... Purging configuration files for shared-mime-info ... Removing libxfixes3 ... Purging configuration files for libxfixes3 ... Removing libpango1.0-0 ... Purging configuration files for libpango1.0-0 ... Removing libatk1.0-data ... Removing libgdk-pixbuf2.0-0 ... Purging configuration files for libgdk-pixbuf2.0-0 ... Removing libjasper1 ... Purging configuration files for libjasper1 ... Removing psmisc ... Purging configuration files for psmisc ... Removing libxml2 ... Purging configuration files for libxml2 ... Removing libavahi-client3 ... Purging configuration files for libavahi-client3 ... Removing libxinerama1 ... Purging configuration files for libxinerama1 ... Removing gconf2-common ... Purging configuration files for gconf2-common ... Removing liborbit2 ... Purging configuration files for liborbit2 ... Removing libavahi-common3 ... Purging configuration files for libavahi-common3 ... Removing libdbus-glib-1-2 ... Purging configuration files for libdbus-glib-1-2 ... Removing libxft2 ... Purging configuration files for libxft2 ... Removing libxext6 ... Purging configuration files for libxext6 ... Removing fontconfig ... Purging configuration files for fontconfig ... Removing python2.7 ... Purging configuration files for python2.7 ... Removing libidl0 ... Purging configuration files for libidl0 ... Removing libthai0 ... Purging configuration files for libthai0 ... Removing mime-support ... Purging configuration files for mime-support ... Removing dbus ... Purging configuration files for dbus ... rmdir: failed to remove `/var/lib/dbus': No such file or directory Removing libthai-data ... Removing libavahi-common-data ... Removing libdatrie1 ... Purging configuration files for libdatrie1 ... Removing libmono-system-web2.0-cil ... Removing libmono-system-data-linq2.0-cil ... Removing libmono-wcf3.0-cil ... Removing libmono2.0-cil ... Removing libmono-sharpzip2.84-cil ... Removing libgamin0 ... Purging configuration files for libgamin0 ... Removing gamin ... Purging configuration files for gamin ... Removing libmono-sqlite2.0-cil ... Removing libgdiplus ... Purging configuration files for libgdiplus ... Removing libmono-system-data2.0-cil ... Removing libmono-system-messaging2.0-cil ... Removing libmono-data-tds2.0-cil ... Removing libsqlite0 ... Purging configuration files for libsqlite0 ... Removing libgif4 ... Purging configuration files for libgif4 ... Removing libmono-messaging2.0-cil ... Removing libsqlite3-0 ... Purging configuration files for libsqlite3-0 ... Removing libexif12 ... Purging configuration files for libexif12 ... Removing libmono-security2.0-cil ... Removing libtiff4 ... Purging configuration files for libtiff4 ... Removing libcairo2 ... Purging configuration files for libcairo2 ... Removing libjpeg62 ... Removing libfontconfig1 ... Purging configuration files for libfontconfig1 ... Removing libxcb-shm0 ... Purging configuration files for libxcb-shm0 ... Removing libpixman-1-0 ... Purging configuration files for libpixman-1-0 ... Removing libxrender1 ... Purging configuration files for libxrender1 ... Removing libmono-system2.0-cil ... Removing libfreetype6 ... Purging configuration files for libfreetype6 ... Removing libexpat1 ... Purging configuration files for libexpat1 ... Removing libxcb-render0 ... Purging configuration files for libxcb-render0 ... Removing fontconfig-config ... Purging configuration files for fontconfig-config ... Removing ttf-dejavu-core ... Removing ucf ... Purging configuration files for ucf ... Removing libx11-6 ... Purging configuration files for libx11-6 ... Removing libmono-posix2.0-cil ... Removing libxcb1 ... Purging configuration files for libxcb1 ... Removing libxau6 ... Purging configuration files for libxau6 ... Removing libmono-corlib2.0-cil ... Removing libxdmcp6 ... Purging configuration files for libxdmcp6 ... Removing libx11-data ... Removing mono-runtime ... Purging configuration files for mono-runtime ... Removing mono-gac ... Removing mono-2.0-gac ... Processing triggers for libc-bin ... ldconfig deferred processing now taking place Processing triggers for libglib2.0-0 ... ****************************************************************************** Finished at 20110410-1838 Build needed 00:01:20, 16124k disk space RUN: /usr/share/launchpad-buildd/slavebin/scan-for-processes ['/usr/share/launchpad-buildd/slavebin/scan-for-processes', 'a5bf95798123a7de5b0ac6630436238ddb2ef38c'] Scanning for processes to kill in build /home/buildd/build-a5bf95798123a7de5b0ac6630436238ddb2ef38c/chroot-autobuild... RUN: /usr/share/launchpad-buildd/slavebin/umount-chroot ['umount-chroot', 'a5bf95798123a7de5b0ac6630436238ddb2ef38c'] Unmounting chroot for build a5bf95798123a7de5b0ac6630436238ddb2ef38c... RUN: /usr/share/launchpad-buildd/slavebin/remove-build ['remove-build', 'a5bf95798123a7de5b0ac6630436238ddb2ef38c'] Removing build a5bf95798123a7de5b0ac6630436238ddb2ef38c