RUN: /bin/echo ['echo', 'Forking build subprocess...'] Forking build subprocess... RUN: /usr/share/launchpad-buildd/slavebin/unpack-chroot ['unpack-chroot', '3b732c62e95fb1ec0c9361c263fc2210c0fcdb8a', '/home/buildd/filecache-default/242c487390f058a1d75a2cb7f5b6bf1c4775bbd5'] Synching the system clock with the buildd NTP service... 5 Dec 08:35:52 ntpdate[25743]: adjust time server 10.211.37.1 offset 0.001164 sec Unpacking chroot for build 3b732c62e95fb1ec0c9361c263fc2210c0fcdb8a RUN: /usr/share/launchpad-buildd/slavebin/mount-chroot ['mount-chroot', '3b732c62e95fb1ec0c9361c263fc2210c0fcdb8a'] Mounting chroot for build 3b732c62e95fb1ec0c9361c263fc2210c0fcdb8a RUN: /usr/share/launchpad-buildd/slavebin/override-sources-list ['override-sources-list', '3b732c62e95fb1ec0c9361c263fc2210c0fcdb8a', 'deb http://ftpmaster.internal/ubuntu precise main universe'] Overriding sources.list in build-3b732c62e95fb1ec0c9361c263fc2210c0fcdb8a RUN: /usr/share/launchpad-buildd/slavebin/update-debian-chroot ['update-debian-chroot', '3b732c62e95fb1ec0c9361c263fc2210c0fcdb8a', 'i386'] Updating debian chroot for build 3b732c62e95fb1ec0c9361c263fc2210c0fcdb8a Ign http://ftpmaster.internal precise InRelease Get:1 http://ftpmaster.internal precise Release.gpg [198 B] Get:2 http://ftpmaster.internal precise Release [49.6 kB] Get:3 http://ftpmaster.internal precise/main i386 Packages [1272 kB] Get:4 http://ftpmaster.internal precise/universe i386 Packages [4682 kB] Get:5 http://ftpmaster.internal precise/main TranslationIndex [3502 B] Get:6 http://ftpmaster.internal precise/universe TranslationIndex [2712 B] Get:7 http://ftpmaster.internal precise/main Translation-en [714 kB] Get:8 http://ftpmaster.internal precise/universe Translation-en [3301 kB] Fetched 10.0 MB in 13s (743 kB/s) Reading package lists... Reading package lists... Building dependency tree... Reading state information... The following NEW packages will be installed: libasn1-8-heimdal libgssapi3-heimdal libhcrypto4-heimdal libheimbase1-heimdal libheimntlm0-heimdal libhx509-5-heimdal libkrb5-26-heimdal libroken18-heimdal libsqlite3-0 libwind0-heimdal The following packages will be upgraded: base-files bash binutils coreutils cpp-4.6 debconf dpkg dpkg-dev g++-4.6 gcc-4.6 gcc-4.6-base gnupg gpgv initramfs-tools initramfs-tools-bin initscripts klibc-utils libacl1 libalgorithm-diff-xs-perl libattr1 libc-bin libc-dev-bin libc6 libc6-dev libcurl3-gnutls libdb5.1 libdpkg-perl libgcc1 libgnutls26 libgomp1 libgssapi-krb5-2 libk5crypto3 libklibc libkrb5-3 libkrb5support0 libldap-2.4-2 libmpfr4 libncurses5 libncursesw5 libquadmath0 libreadline6 libsasl2-2 libselinux1 libstdc++6 libstdc++6-4.6-dev libtinfo5 libudev0 linux-libc-dev locales login lsb-base module-init-tools multiarch-support ncurses-base ncurses-bin passwd perl perl-base perl-modules pkg-create-dbgsym pkgbinarymangler procps python-minimal python2.7-minimal readline-common sysv-rc sysvinit-utils tar ubuntu-keyring udev 70 upgraded, 10 newly installed, 0 to remove and 0 not upgraded. Need to get 61.0 MB of archives. After this operation, 10.8 MB disk space will be freed. WARNING: The following packages cannot be authenticated! base-files bash libc-dev-bin libc6-dev libc-bin libc6 linux-libc-dev libgomp1 gcc-4.6-base libgcc1 cpp-4.6 libquadmath0 libstdc++6-4.6-dev g++-4.6 gcc-4.6 libstdc++6 libmpfr4 binutils libattr1 libacl1 dpkg coreutils login libncursesw5 libtinfo5 libncurses5 ncurses-bin perl libalgorithm-diff-xs-perl perl-base perl-modules libdb5.1 tar ncurses-base python2.7-minimal python-minimal readline-common libreadline6 debconf libselinux1 libsqlite3-0 libudev0 module-init-tools libgnutls26 libk5crypto3 libgssapi-krb5-2 libkrb5-3 libkrb5support0 libroken18-heimdal libasn1-8-heimdal libhcrypto4-heimdal libheimbase1-heimdal libwind0-heimdal libhx509-5-heimdal libkrb5-26-heimdal libheimntlm0-heimdal libgssapi3-heimdal libsasl2-2 libldap-2.4-2 libcurl3-gnutls gpgv gnupg ubuntu-keyring lsb-base multiarch-support passwd initramfs-tools initramfs-tools-bin klibc-utils libklibc sysvinit-utils sysv-rc initscripts procps udev locales dpkg-dev libdpkg-perl pkg-create-dbgsym pkgbinarymangler Authentication warning overridden. Get:1 http://ftpmaster.internal/ubuntu/ precise/main base-files i386 6.5ubuntu3 [65.6 kB] Get:2 http://ftpmaster.internal/ubuntu/ precise/main bash i386 4.2-1ubuntu1 [616 kB] Get:3 http://ftpmaster.internal/ubuntu/ precise/main libc-dev-bin i386 2.13-20ubuntu9 [77.5 kB] Get:4 http://ftpmaster.internal/ubuntu/ precise/main libc6-dev i386 2.13-20ubuntu9 [5031 kB] Get:5 http://ftpmaster.internal/ubuntu/ precise/main libc-bin i386 2.13-20ubuntu9 [932 kB] Get:6 http://ftpmaster.internal/ubuntu/ precise/main libc6 i386 2.13-20ubuntu9 [3797 kB] Get:7 http://ftpmaster.internal/ubuntu/ precise/main linux-libc-dev i386 3.2.0-3.8 [822 kB] Get:8 http://ftpmaster.internal/ubuntu/ precise/main libgomp1 i386 4.6.2-5ubuntu1 [28.3 kB] Get:9 http://ftpmaster.internal/ubuntu/ precise/main gcc-4.6-base i386 4.6.2-5ubuntu1 [15.3 kB] Get:10 http://ftpmaster.internal/ubuntu/ precise/main libgcc1 i386 1:4.6.2-5ubuntu1 [54.3 kB] Get:11 http://ftpmaster.internal/ubuntu/ precise/main cpp-4.6 i386 4.6.2-5ubuntu1 [4650 kB] Get:12 http://ftpmaster.internal/ubuntu/ precise/main libquadmath0 i386 4.6.2-5ubuntu1 [195 kB] Get:13 http://ftpmaster.internal/ubuntu/ precise/main libstdc++6-4.6-dev i386 4.6.2-5ubuntu1 [1591 kB] Get:14 http://ftpmaster.internal/ubuntu/ precise/main g++-4.6 i386 4.6.2-5ubuntu1 [6191 kB] Get:15 http://ftpmaster.internal/ubuntu/ precise/main gcc-4.6 i386 4.6.2-5ubuntu1 [7534 kB] Get:16 http://ftpmaster.internal/ubuntu/ precise/main libstdc++6 i386 4.6.2-5ubuntu1 [333 kB] Get:17 http://ftpmaster.internal/ubuntu/ precise/main libmpfr4 i386 3.1.0-3 [199 kB] Get:18 http://ftpmaster.internal/ubuntu/ precise/main binutils i386 2.22-1ubuntu1 [2384 kB] Get:19 http://ftpmaster.internal/ubuntu/ precise/main libattr1 i386 1:2.4.46-3ubuntu1 [10.9 kB] Get:20 http://ftpmaster.internal/ubuntu/ precise/main libacl1 i386 2.2.51-4ubuntu1 [18.5 kB] Get:21 http://ftpmaster.internal/ubuntu/ precise/main dpkg i386 1.16.1.2ubuntu3 [1814 kB] Get:22 http://ftpmaster.internal/ubuntu/ precise/main coreutils i386 8.13-3ubuntu2 [2516 kB] Get:23 http://ftpmaster.internal/ubuntu/ precise/main login i386 1:4.1.4.2+svn3283-3ubuntu3 [284 kB] Get:24 http://ftpmaster.internal/ubuntu/ precise/main libncursesw5 i386 5.9-4 [145 kB] Get:25 http://ftpmaster.internal/ubuntu/ precise/main libtinfo5 i386 5.9-4 [90.0 kB] Get:26 http://ftpmaster.internal/ubuntu/ precise/main libncurses5 i386 5.9-4 [116 kB] Get:27 http://ftpmaster.internal/ubuntu/ precise/main ncurses-bin i386 5.9-4 [151 kB] Get:28 http://ftpmaster.internal/ubuntu/ precise/main perl i386 5.14.2-5ubuntu1 [3675 kB] Get:29 http://ftpmaster.internal/ubuntu/ precise/main libalgorithm-diff-xs-perl i386 0.04-2build2 [12.9 kB] Get:30 http://ftpmaster.internal/ubuntu/ precise/main perl-base i386 5.14.2-5ubuntu1 [1423 kB] Get:31 http://ftpmaster.internal/ubuntu/ precise/main perl-modules all 5.14.2-5ubuntu1 [3369 kB] Get:32 http://ftpmaster.internal/ubuntu/ precise/main libdb5.1 i386 5.1.25-11build1 [736 kB] Get:33 http://ftpmaster.internal/ubuntu/ precise/main tar i386 1.26-3ubuntu1 [219 kB] Get:34 http://ftpmaster.internal/ubuntu/ precise/main ncurses-base all 5.9-4 [21.0 kB] Get:35 http://ftpmaster.internal/ubuntu/ precise/main python2.7-minimal i386 2.7.2-8build1 [1582 kB] Get:36 http://ftpmaster.internal/ubuntu/ precise/main python-minimal all 2.7.2-9ubuntu1 [29.7 kB] Get:37 http://ftpmaster.internal/ubuntu/ precise/main readline-common i386 6.2-8 [49.9 kB] Get:38 http://ftpmaster.internal/ubuntu/ precise/main libreadline6 i386 6.2-8 [134 kB] Get:39 http://ftpmaster.internal/ubuntu/ precise/main debconf i386 1.5.41ubuntu1 [145 kB] Get:40 http://ftpmaster.internal/ubuntu/ precise/main libselinux1 i386 2.1.0-4ubuntu1 [62.2 kB] Get:41 http://ftpmaster.internal/ubuntu/ precise/main libsqlite3-0 i386 3.7.9-2ubuntu1 [354 kB] Get:42 http://ftpmaster.internal/ubuntu/ precise/main libudev0 i386 175-0ubuntu2 [33.2 kB] Get:43 http://ftpmaster.internal/ubuntu/ precise/main module-init-tools i386 3.16-1ubuntu2 [102 kB] Get:44 http://ftpmaster.internal/ubuntu/ precise/main libgnutls26 i386 2.12.14-3 [448 kB] Get:45 http://ftpmaster.internal/ubuntu/ precise/main libk5crypto3 i386 1.9.1+dfsg-3ubuntu1 [79.9 kB] Get:46 http://ftpmaster.internal/ubuntu/ precise/main libgssapi-krb5-2 i386 1.9.1+dfsg-3ubuntu1 [120 kB] Get:47 http://ftpmaster.internal/ubuntu/ precise/main libkrb5-3 i386 1.9.1+dfsg-3ubuntu1 [360 kB] Get:48 http://ftpmaster.internal/ubuntu/ precise/main libkrb5support0 i386 1.9.1+dfsg-3ubuntu1 [23.9 kB] Get:49 http://ftpmaster.internal/ubuntu/ precise/main libroken18-heimdal i386 1.5.dfsg.1-3 [46.4 kB] Get:50 http://ftpmaster.internal/ubuntu/ precise/main libasn1-8-heimdal i386 1.5.dfsg.1-3 [228 kB] Get:51 http://ftpmaster.internal/ubuntu/ precise/main libhcrypto4-heimdal i386 1.5.dfsg.1-3 [103 kB] Get:52 http://ftpmaster.internal/ubuntu/ precise/main libheimbase1-heimdal i386 1.5.dfsg.1-3 [11.9 kB] Get:53 http://ftpmaster.internal/ubuntu/ precise/main libwind0-heimdal i386 1.5.dfsg.1-3 [77.5 kB] Get:54 http://ftpmaster.internal/ubuntu/ precise/main libhx509-5-heimdal i386 1.5.dfsg.1-3 [126 kB] Get:55 http://ftpmaster.internal/ubuntu/ precise/main libkrb5-26-heimdal i386 1.5.dfsg.1-3 [224 kB] Get:56 http://ftpmaster.internal/ubuntu/ precise/main libheimntlm0-heimdal i386 1.5.dfsg.1-3 [16.7 kB] Get:57 http://ftpmaster.internal/ubuntu/ precise/main libgssapi3-heimdal i386 1.5.dfsg.1-3 [111 kB] Get:58 http://ftpmaster.internal/ubuntu/ precise/main libsasl2-2 i386 2.1.24~rc1.dfsg1+cvs2011-05-23-4ubuntu3 [69.9 kB] Get:59 http://ftpmaster.internal/ubuntu/ precise/main libldap-2.4-2 i386 2.4.25-4ubuntu1 [184 kB] Get:60 http://ftpmaster.internal/ubuntu/ precise/main libcurl3-gnutls i386 7.22.0-3ubuntu1 [232 kB] Get:61 http://ftpmaster.internal/ubuntu/ precise/main gpgv i386 1.4.11-3ubuntu2 [179 kB] Get:62 http://ftpmaster.internal/ubuntu/ precise/main gnupg i386 1.4.11-3ubuntu2 [790 kB] Get:63 http://ftpmaster.internal/ubuntu/ precise/main ubuntu-keyring i386 2011.11.21 [11.4 kB] Get:64 http://ftpmaster.internal/ubuntu/ precise/main lsb-base all 4.0-0ubuntu17 [10.5 kB] Get:65 http://ftpmaster.internal/ubuntu/ precise/main multiarch-support i386 2.13-20ubuntu9 [4478 B] Get:66 http://ftpmaster.internal/ubuntu/ precise/main passwd i386 1:4.1.4.2+svn3283-3ubuntu3 [926 kB] Get:67 http://ftpmaster.internal/ubuntu/ precise/main initramfs-tools i386 0.99ubuntu9 [48.6 kB] Get:68 http://ftpmaster.internal/ubuntu/ precise/main initramfs-tools-bin i386 0.99ubuntu9 [11.8 kB] Get:69 http://ftpmaster.internal/ubuntu/ precise/main klibc-utils i386 1.5.25-1ubuntu1 [160 kB] Get:70 http://ftpmaster.internal/ubuntu/ precise/main libklibc i386 1.5.25-1ubuntu1 [46.4 kB] Get:71 http://ftpmaster.internal/ubuntu/ precise/main sysvinit-utils i386 2.88dsf-13.10ubuntu5 [61.1 kB] Get:72 http://ftpmaster.internal/ubuntu/ precise/main sysv-rc all 2.88dsf-13.10ubuntu5 [44.5 kB] Get:73 http://ftpmaster.internal/ubuntu/ precise/main initscripts i386 2.88dsf-13.10ubuntu5 [27.2 kB] Get:74 http://ftpmaster.internal/ubuntu/ precise/main procps i386 1:3.2.8-11ubuntu4 [226 kB] Get:75 http://ftpmaster.internal/ubuntu/ precise/main udev i386 175-0ubuntu2 [348 kB] Get:76 http://ftpmaster.internal/ubuntu/ precise/main locales all 2.13+git20111116-1 [3349 kB] Get:77 http://ftpmaster.internal/ubuntu/ precise/main dpkg-dev i386 1.16.1.2ubuntu3 [468 kB] Get:78 http://ftpmaster.internal/ubuntu/ precise/main libdpkg-perl i386 1.16.1.2ubuntu3 [181 kB] Get:79 http://ftpmaster.internal/ubuntu/ precise/main pkg-create-dbgsym all 0.50 [8334 B] Get:80 http://ftpmaster.internal/ubuntu/ precise/main pkgbinarymangler all 109 [28.1 kB] debconf: delaying package configuration, since apt-utils is not installed Fetched 61.0 MB in 5s (10.7 MB/s) (Reading database ... 14144 files and directories currently installed.) Preparing to replace base-files 6.5ubuntu2 (using .../base-files_6.5ubuntu3_i386.deb) ... Unpacking replacement base-files ... Setting up base-files (6.5ubuntu3) ... (Reading database ... 14144 files and directories currently installed.) Preparing to replace bash 4.2-0ubuntu4 (using .../bash_4.2-1ubuntu1_i386.deb) ... Unpacking replacement bash ... Setting up bash (4.2-1ubuntu1) ... Installing new version of config file /etc/skel/.bashrc ... 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 ... 14145 files and directories currently installed.) Preparing to replace libc-dev-bin 2.13-20ubuntu5 (using .../libc-dev-bin_2.13-20ubuntu9_i386.deb) ... Unpacking replacement libc-dev-bin ... Preparing to replace libc6-dev 2.13-20ubuntu5 (using .../libc6-dev_2.13-20ubuntu9_i386.deb) ... Unpacking replacement libc6-dev ... Preparing to replace libc-bin 2.13-20ubuntu5 (using .../libc-bin_2.13-20ubuntu9_i386.deb) ... Unpacking replacement libc-bin ... Setting up libc-bin (2.13-20ubuntu9) ... (Reading database ... 14145 files and directories currently installed.) Preparing to replace libc6 2.13-20ubuntu5 (using .../libc6_2.13-20ubuntu9_i386.deb) ... Unpacking replacement libc6 ... Setting up libc6 (2.13-20ubuntu9) ... Processing triggers for libc-bin ... ldconfig deferred processing now taking place (Reading database ... 14145 files and directories currently installed.) Preparing to replace linux-libc-dev 3.1.0-2.3 (using .../linux-libc-dev_3.2.0-3.8_i386.deb) ... Unpacking replacement linux-libc-dev ... Preparing to replace libgomp1 4.6.2-2ubuntu1 (using .../libgomp1_4.6.2-5ubuntu1_i386.deb) ... Unpacking replacement libgomp1 ... Preparing to replace gcc-4.6-base 4.6.2-2ubuntu1 (using .../gcc-4.6-base_4.6.2-5ubuntu1_i386.deb) ... Unpacking replacement gcc-4.6-base ... Setting up gcc-4.6-base (4.6.2-5ubuntu1) ... (Reading database ... 14146 files and directories currently installed.) Preparing to replace libgcc1 1:4.6.2-2ubuntu1 (using .../libgcc1_1%3a4.6.2-5ubuntu1_i386.deb) ... Unpacking replacement libgcc1 ... Setting up libgcc1 (1:4.6.2-5ubuntu1) ... Processing triggers for libc-bin ... ldconfig deferred processing now taking place (Reading database ... 14146 files and directories currently installed.) Preparing to replace cpp-4.6 4.6.2-2ubuntu1 (using .../cpp-4.6_4.6.2-5ubuntu1_i386.deb) ... Unpacking replacement cpp-4.6 ... Preparing to replace libquadmath0 4.6.2-2ubuntu1 (using .../libquadmath0_4.6.2-5ubuntu1_i386.deb) ... Unpacking replacement libquadmath0 ... Preparing to replace libstdc++6-4.6-dev 4.6.2-2ubuntu1 (using .../libstdc++6-4.6-dev_4.6.2-5ubuntu1_i386.deb) ... Unpacking replacement libstdc++6-4.6-dev ... Preparing to replace g++-4.6 4.6.2-2ubuntu1 (using .../g++-4.6_4.6.2-5ubuntu1_i386.deb) ... Unpacking replacement g++-4.6 ... Preparing to replace gcc-4.6 4.6.2-2ubuntu1 (using .../gcc-4.6_4.6.2-5ubuntu1_i386.deb) ... Unpacking replacement gcc-4.6 ... Preparing to replace libstdc++6 4.6.2-2ubuntu1 (using .../libstdc++6_4.6.2-5ubuntu1_i386.deb) ... Unpacking replacement libstdc++6 ... Setting up libstdc++6 (4.6.2-5ubuntu1) ... Processing triggers for libc-bin ... ldconfig deferred processing now taking place (Reading database ... 14146 files and directories currently installed.) Preparing to replace libmpfr4 3.1.0-2 (using .../libmpfr4_3.1.0-3_i386.deb) ... Unpacking replacement libmpfr4 ... Preparing to replace binutils 2.21.90.20111025-1ubuntu1 (using .../binutils_2.22-1ubuntu1_i386.deb) ... Unpacking replacement binutils ... Preparing to replace libattr1 1:2.4.46-3 (using .../libattr1_1%3a2.4.46-3ubuntu1_i386.deb) ... Unpacking replacement libattr1 ... Setting up libattr1 (1:2.4.46-3ubuntu1) ... Processing triggers for libc-bin ... ldconfig deferred processing now taking place (Reading database ... 14146 files and directories currently installed.) Preparing to replace libacl1 2.2.51-3 (using .../libacl1_2.2.51-4ubuntu1_i386.deb) ... Unpacking replacement libacl1 ... Setting up libacl1 (2.2.51-4ubuntu1) ... Processing triggers for libc-bin ... ldconfig deferred processing now taking place (Reading database ... 14146 files and directories currently installed.) Preparing to replace dpkg 1.16.1.1ubuntu3 (using .../dpkg_1.16.1.2ubuntu3_i386.deb) ... Unpacking replacement dpkg ... Setting up dpkg (1.16.1.2ubuntu3) ... (Reading database ... 14146 files and directories currently installed.) Preparing to replace coreutils 8.13-3ubuntu1 (using .../coreutils_8.13-3ubuntu2_i386.deb) ... Unpacking replacement coreutils ... Setting up coreutils (8.13-3ubuntu2) ... (Reading database ... 14146 files and directories currently installed.) Preparing to replace login 1:4.1.4.2+svn3283-3ubuntu2 (using .../login_1%3a4.1.4.2+svn3283-3ubuntu3_i386.deb) ... Unpacking replacement login ... Setting up login (1:4.1.4.2+svn3283-3ubuntu3) ... Installing new version of config file /etc/securetty ... (Reading database ... 14146 files and directories currently installed.) Preparing to replace libncursesw5 5.9-2 (using .../libncursesw5_5.9-4_i386.deb) ... Unpacking replacement libncursesw5 ... Preparing to replace libtinfo5 5.9-2 (using .../libtinfo5_5.9-4_i386.deb) ... Unpacking replacement libtinfo5 ... Replacing files in old package libncurses5 ... Setting up libtinfo5 (5.9-4) ... Processing triggers for libc-bin ... ldconfig deferred processing now taking place (Reading database ... 14144 files and directories currently installed.) Preparing to replace libncurses5 5.9-2 (using .../libncurses5_5.9-4_i386.deb) ... Unpacking replacement libncurses5 ... Setting up libncurses5 (5.9-4) ... Processing triggers for libc-bin ... ldconfig deferred processing now taking place (Reading database ... 14144 files and directories currently installed.) Preparing to replace ncurses-bin 5.9-2 (using .../ncurses-bin_5.9-4_i386.deb) ... Unpacking replacement ncurses-bin ... Setting up ncurses-bin (5.9-4) ... (Reading database ... 14144 files and directories currently installed.) Preparing to replace perl 5.12.4-6 (using .../perl_5.14.2-5ubuntu1_i386.deb) ... Unpacking replacement perl ... Preparing to replace libalgorithm-diff-xs-perl 0.04-2 (using .../libalgorithm-diff-xs-perl_0.04-2build2_i386.deb) ... Unpacking replacement libalgorithm-diff-xs-perl ... Preparing to replace perl-base 5.12.4-6 (using .../perl-base_5.14.2-5ubuntu1_i386.deb) ... Unpacking replacement perl-base ... Setting up perl-base (5.14.2-5ubuntu1) ... (Reading database ... 14175 files and directories currently installed.) Preparing to replace perl-modules 5.12.4-6 (using .../perl-modules_5.14.2-5ubuntu1_all.deb) ... Unpacking replacement perl-modules ... Preparing to replace libdb5.1 5.1.25-11 (using .../libdb5.1_5.1.25-11build1_i386.deb) ... Unpacking replacement libdb5.1 ... Setting up libdb5.1 (5.1.25-11build1) ... Processing triggers for libc-bin ... ldconfig deferred processing now taking place (Reading database ... 14222 files and directories currently installed.) Preparing to replace tar 1.25-3 (using .../tar_1.26-3ubuntu1_i386.deb) ... Unpacking replacement tar ... Setting up tar (1.26-3ubuntu1) ... (Reading database ... 14222 files and directories currently installed.) Preparing to replace ncurses-base 5.9-2 (using .../ncurses-base_5.9-4_all.deb) ... Unpacking replacement ncurses-base ... Setting up ncurses-base (5.9-4) ... Installing new version of config file /etc/terminfo/README ... (Reading database ... 14222 files and directories currently installed.) Preparing to replace python2.7-minimal 2.7.2-5ubuntu1 (using .../python2.7-minimal_2.7.2-8build1_i386.deb) ... Unpacking replacement python2.7-minimal ... Setting up python2.7-minimal (2.7.2-8build1) ... (Reading database ... 14222 files and directories currently installed.) Preparing to replace python-minimal 2.7.2-7ubuntu4 (using .../python-minimal_2.7.2-9ubuntu1_all.deb) ... Unpacking replacement python-minimal ... Setting up python-minimal (2.7.2-9ubuntu1) ... (Reading database ... 14222 files and directories currently installed.) Preparing to replace readline-common 6.2-7ubuntu1 (using .../readline-common_6.2-8_i386.deb) ... Unpacking replacement readline-common ... Setting up readline-common (6.2-8) ... (Reading database ... 14222 files and directories currently installed.) Preparing to replace libreadline6 6.2-7ubuntu1 (using .../libreadline6_6.2-8_i386.deb) ... Unpacking replacement libreadline6 ... Setting up libreadline6 (6.2-8) ... Processing triggers for libc-bin ... ldconfig deferred processing now taking place (Reading database ... 14222 files and directories currently installed.) Preparing to replace debconf 1.5.40ubuntu1 (using .../debconf_1.5.41ubuntu1_i386.deb) ... Unpacking replacement debconf ... Setting up debconf (1.5.41ubuntu1) ... (Reading database ... 14219 files and directories currently installed.) Preparing to replace libselinux1 2.1.0-1 (using .../libselinux1_2.1.0-4ubuntu1_i386.deb) ... Unpacking replacement libselinux1 ... Setting up libselinux1 (2.1.0-4ubuntu1) ... Processing triggers for libc-bin ... ldconfig deferred processing now taking place Selecting previously unselected package libsqlite3-0. (Reading database ... 14219 files and directories currently installed.) Unpacking libsqlite3-0 (from .../libsqlite3-0_3.7.9-2ubuntu1_i386.deb) ... Preparing to replace libudev0 175-0ubuntu1 (using .../libudev0_175-0ubuntu2_i386.deb) ... Unpacking replacement libudev0 ... Preparing to replace module-init-tools 3.16-1ubuntu1 (using .../module-init-tools_3.16-1ubuntu2_i386.deb) ... Unpacking replacement module-init-tools ... Preparing to replace libgnutls26 2.12.11-1 (using .../libgnutls26_2.12.14-3_i386.deb) ... Unpacking replacement libgnutls26 ... Preparing to replace libk5crypto3 1.9.1+dfsg-1ubuntu2.1 (using .../libk5crypto3_1.9.1+dfsg-3ubuntu1_i386.deb) ... Unpacking replacement libk5crypto3 ... Preparing to replace libgssapi-krb5-2 1.9.1+dfsg-1ubuntu2.1 (using .../libgssapi-krb5-2_1.9.1+dfsg-3ubuntu1_i386.deb) ... Unpacking replacement libgssapi-krb5-2 ... Preparing to replace libkrb5-3 1.9.1+dfsg-1ubuntu2.1 (using .../libkrb5-3_1.9.1+dfsg-3ubuntu1_i386.deb) ... Unpacking replacement libkrb5-3 ... Preparing to replace libkrb5support0 1.9.1+dfsg-1ubuntu2.1 (using .../libkrb5support0_1.9.1+dfsg-3ubuntu1_i386.deb) ... Unpacking replacement libkrb5support0 ... Selecting previously unselected package libroken18-heimdal. Unpacking libroken18-heimdal (from .../libroken18-heimdal_1.5.dfsg.1-3_i386.deb) ... Selecting previously unselected package libasn1-8-heimdal. Unpacking libasn1-8-heimdal (from .../libasn1-8-heimdal_1.5.dfsg.1-3_i386.deb) ... Selecting previously unselected package libhcrypto4-heimdal. Unpacking libhcrypto4-heimdal (from .../libhcrypto4-heimdal_1.5.dfsg.1-3_i386.deb) ... Selecting previously unselected package libheimbase1-heimdal. Unpacking libheimbase1-heimdal (from .../libheimbase1-heimdal_1.5.dfsg.1-3_i386.deb) ... Selecting previously unselected package libwind0-heimdal. Unpacking libwind0-heimdal (from .../libwind0-heimdal_1.5.dfsg.1-3_i386.deb) ... Selecting previously unselected package libhx509-5-heimdal. Unpacking libhx509-5-heimdal (from .../libhx509-5-heimdal_1.5.dfsg.1-3_i386.deb) ... Selecting previously unselected package libkrb5-26-heimdal. Unpacking libkrb5-26-heimdal (from .../libkrb5-26-heimdal_1.5.dfsg.1-3_i386.deb) ... Selecting previously unselected package libheimntlm0-heimdal. Unpacking libheimntlm0-heimdal (from .../libheimntlm0-heimdal_1.5.dfsg.1-3_i386.deb) ... Selecting previously unselected package libgssapi3-heimdal. Unpacking libgssapi3-heimdal (from .../libgssapi3-heimdal_1.5.dfsg.1-3_i386.deb) ... Preparing to replace libsasl2-2 2.1.24~rc1.dfsg1+cvs2011-05-23-4ubuntu2 (using .../libsasl2-2_2.1.24~rc1.dfsg1+cvs2011-05-23-4ubuntu3_i386.deb) ... Unpacking replacement libsasl2-2 ... Preparing to replace libldap-2.4-2 2.4.25-3ubuntu1 (using .../libldap-2.4-2_2.4.25-4ubuntu1_i386.deb) ... Unpacking replacement libldap-2.4-2 ... Preparing to replace libcurl3-gnutls 7.21.7-3ubuntu1 (using .../libcurl3-gnutls_7.22.0-3ubuntu1_i386.deb) ... Unpacking replacement libcurl3-gnutls ... Preparing to replace gpgv 1.4.11-3ubuntu1 (using .../gpgv_1.4.11-3ubuntu2_i386.deb) ... Unpacking replacement gpgv ... Setting up gpgv (1.4.11-3ubuntu2) ... (Reading database ... 14279 files and directories currently installed.) Preparing to replace gnupg 1.4.11-3ubuntu1 (using .../gnupg_1.4.11-3ubuntu2_i386.deb) ... Unpacking replacement gnupg ... Setting up gnupg (1.4.11-3ubuntu2) ... (Reading database ... 14279 files and directories currently installed.) Preparing to replace ubuntu-keyring 2010.+09.30 (using .../ubuntu-keyring_2011.11.21_i386.deb) ... Unpacking replacement ubuntu-keyring ... Setting up ubuntu-keyring (2011.11.21) ... 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 (Reading database ... 14279 files and directories currently installed.) Preparing to replace lsb-base 4.0-0ubuntu16 (using .../lsb-base_4.0-0ubuntu17_all.deb) ... Unpacking replacement lsb-base ... Setting up lsb-base (4.0-0ubuntu17) ... (Reading database ... 14279 files and directories currently installed.) Preparing to replace multiarch-support 2.13-20ubuntu5 (using .../multiarch-support_2.13-20ubuntu9_i386.deb) ... Unpacking replacement multiarch-support ... Setting up multiarch-support (2.13-20ubuntu9) ... (Reading database ... 14279 files and directories currently installed.) Preparing to replace passwd 1:4.1.4.2+svn3283-3ubuntu2 (using .../passwd_1%3a4.1.4.2+svn3283-3ubuntu3_i386.deb) ... Unpacking replacement passwd ... Setting up passwd (1:4.1.4.2+svn3283-3ubuntu3) ... (Reading database ... 14279 files and directories currently installed.) Preparing to replace initramfs-tools 0.99ubuntu8 (using .../initramfs-tools_0.99ubuntu9_i386.deb) ... Unpacking replacement initramfs-tools ... Preparing to replace initramfs-tools-bin 0.99ubuntu8 (using .../initramfs-tools-bin_0.99ubuntu9_i386.deb) ... Unpacking replacement initramfs-tools-bin ... Preparing to replace klibc-utils 1.5.22-1ubuntu2 (using .../klibc-utils_1.5.25-1ubuntu1_i386.deb) ... Unpacking replacement klibc-utils ... Preparing to replace libklibc 1.5.22-1ubuntu2 (using .../libklibc_1.5.25-1ubuntu1_i386.deb) ... Unpacking replacement libklibc ... Preparing to replace sysvinit-utils 2.88dsf-13.10ubuntu4 (using .../sysvinit-utils_2.88dsf-13.10ubuntu5_i386.deb) ... Unpacking replacement sysvinit-utils ... Preparing to replace sysv-rc 2.88dsf-13.10ubuntu4 (using .../sysv-rc_2.88dsf-13.10ubuntu5_all.deb) ... Unpacking replacement sysv-rc ... Preparing to replace initscripts 2.88dsf-13.10ubuntu4 (using .../initscripts_2.88dsf-13.10ubuntu5_i386.deb) ... Unpacking replacement initscripts ... Preparing to replace procps 1:3.2.8-11ubuntu1 (using .../procps_1%3a3.2.8-11ubuntu4_i386.deb) ... invoke-rc.d: policy-rc.d denied execution of stop. Unpacking replacement procps ... Preparing to replace udev 175-0ubuntu1 (using .../udev_175-0ubuntu2_i386.deb) ... Adding 'diversion of /sbin/udevadm to /sbin/udevadm.upgrade by fake-udev' Unpacking replacement udev ... Preparing to replace locales 2.13+git20110622-2 (using .../locales_2.13+git20111116-1_all.deb) ... Unpacking replacement locales ... Preparing to replace dpkg-dev 1.16.1.1ubuntu3 (using .../dpkg-dev_1.16.1.2ubuntu3_i386.deb) ... Unpacking replacement dpkg-dev ... Preparing to replace libdpkg-perl 1.16.1.1ubuntu3 (using .../libdpkg-perl_1.16.1.2ubuntu3_i386.deb) ... Unpacking replacement libdpkg-perl ... Preparing to replace pkg-create-dbgsym 0.49 (using .../pkg-create-dbgsym_0.50_all.deb) ... Unpacking replacement pkg-create-dbgsym ... Preparing to replace pkgbinarymangler 105 (using .../pkgbinarymangler_109_all.deb) ... Unpacking replacement pkgbinarymangler ... Setting up libc-dev-bin (2.13-20ubuntu9) ... Setting up linux-libc-dev (3.2.0-3.8) ... Setting up libc6-dev (2.13-20ubuntu9) ... Setting up libgomp1 (4.6.2-5ubuntu1) ... Setting up libmpfr4 (3.1.0-3) ... Setting up cpp-4.6 (4.6.2-5ubuntu1) ... Setting up libquadmath0 (4.6.2-5ubuntu1) ... Setting up binutils (2.22-1ubuntu1) ... Setting up gcc-4.6 (4.6.2-5ubuntu1) ... Setting up libncursesw5 (5.9-4) ... Setting up libsqlite3-0 (3.7.9-2ubuntu1) ... Setting up libudev0 (175-0ubuntu2) ... Setting up module-init-tools (3.16-1ubuntu2) ... Setting up libgnutls26 (2.12.14-3) ... Setting up libkrb5support0 (1.9.1+dfsg-3ubuntu1) ... Setting up libk5crypto3 (1.9.1+dfsg-3ubuntu1) ... Setting up libkrb5-3 (1.9.1+dfsg-3ubuntu1) ... Setting up libgssapi-krb5-2 (1.9.1+dfsg-3ubuntu1) ... Setting up libroken18-heimdal (1.5.dfsg.1-3) ... Setting up libasn1-8-heimdal (1.5.dfsg.1-3) ... Setting up libhcrypto4-heimdal (1.5.dfsg.1-3) ... Setting up libheimbase1-heimdal (1.5.dfsg.1-3) ... Setting up libwind0-heimdal (1.5.dfsg.1-3) ... Setting up libhx509-5-heimdal (1.5.dfsg.1-3) ... Setting up libkrb5-26-heimdal (1.5.dfsg.1-3) ... Setting up libheimntlm0-heimdal (1.5.dfsg.1-3) ... Setting up libgssapi3-heimdal (1.5.dfsg.1-3) ... Setting up libsasl2-2 (2.1.24~rc1.dfsg1+cvs2011-05-23-4ubuntu3) ... Setting up libldap-2.4-2 (2.4.25-4ubuntu1) ... Setting up libcurl3-gnutls (7.22.0-3ubuntu1) ... Setting up initramfs-tools-bin (0.99ubuntu9) ... Setting up libklibc (1.5.25-1ubuntu1) ... Setting up klibc-utils (1.5.25-1ubuntu1) ... Setting up sysvinit-utils (2.88dsf-13.10ubuntu5) ... Setting up sysv-rc (2.88dsf-13.10ubuntu5) ... Setting up initscripts (2.88dsf-13.10ubuntu5) ... guest environment detected: Linking /run/shm to /dev/shm Setting up procps (1:3.2.8-11ubuntu4) ... Installing new version of config file /etc/init/procps.conf ... invoke-rc.d: policy-rc.d denied execution of start. Setting up locales (2.13+git20111116-1) ... Setting up pkg-create-dbgsym (0.50) ... Setting up pkgbinarymangler (109) ... Installing new version of config file /etc/pkgbinarymangler/striptranslations.blacklist ... Setting up libstdc++6-4.6-dev (4.6.2-5ubuntu1) ... Setting up perl-modules (5.14.2-5ubuntu1) ... Setting up perl (5.14.2-5ubuntu1) ... Setting up libalgorithm-diff-xs-perl (0.04-2build2) ... Setting up udev (175-0ubuntu2) ... Installing new version of config file /etc/init/udev.conf ... invoke-rc.d: policy-rc.d denied execution of restart. Removing 'diversion of /sbin/udevadm to /sbin/udevadm.upgrade by fake-udev' update-initramfs: deferring update (trigger activated) Setting up initramfs-tools (0.99ubuntu9) ... update-initramfs: deferring update (trigger activated) Setting up libdpkg-perl (1.16.1.2ubuntu3) ... Setting up dpkg-dev (1.16.1.2ubuntu3) ... Setting up g++-4.6 (4.6.2-5ubuntu1) ... 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', '3b732c62e95fb1ec0c9361c263fc2210c0fcdb8a', 'i386', 'precise', '--nolog', '--batch', '--archive=ubuntu', '--dist=precise', '-A', '--purpose=PRIMARY', '--architecture=i386', '--comp=universe', 'sugar-0.88_0.88.1-5ubuntu1.dsc'] Initiating build 3b732c62e95fb1ec0c9361c263fc2210c0fcdb8a with 2 processor cores. Automatic build of sugar-0.88_0.88.1-5ubuntu1 on vernadsky by sbuild/i386 1.170.5 Build started at 20111205-0836 ****************************************************************************** sugar-0.88_0.88.1-5ubuntu1.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: devscripts (>= 2.10.7~), python-central, cdbs (>= 0.4.75~), python, debhelper (>= 6), dh-buildinfo, libglib2.0-dev, python-gtk2-dev, libgconf2-dev, gettext, intltool, shared-mime-info, python-empy 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... devscripts: missing python-central: missing cdbs: missing python: missing debhelper: missing dh-buildinfo: missing libglib2.0-dev: missing python-gtk2-dev: missing libgconf2-dev: missing gettext: missing intltool: missing shared-mime-info: missing python-empy: missing Checking for source dependency conflicts... /usr/bin/sudo /usr/bin/apt-get --purge $CHROOT_OPTIONS -q -y install devscripts python-central cdbs python debhelper dh-buildinfo libglib2.0-dev python-gtk2-dev libgconf2-dev gettext intltool shared-mime-info python-empy Reading package lists... Building dependency tree... Reading state information... The following extra packages will be installed: autoconf automake autotools-dev bsdmainutils dbus dbus-x11 dh-translations file fontconfig fontconfig-config gconf2 gconf2-common gettext-base gir1.2-atk-1.0 gir1.2-freedesktop gir1.2-gconf-2.0 gir1.2-gdkpixbuf-2.0 gir1.2-glib-2.0 gir1.2-pango-1.0 groff-base html2text intltool-debian libatk1.0-0 libatk1.0-data libatk1.0-dev libavahi-client3 libavahi-common-data libavahi-common3 libcairo-gobject2 libcairo-script-interpreter2 libcairo2 libcairo2-dev libcroco3 libcups2 libdatrie1 libdb4.8 libdbus-1-dev libdbus-glib-1-2 libencode-locale-perl libexpat1 libexpat1-dev libffi-dev libfile-listing-perl libfontconfig1 libfontconfig1-dev libfreetype6 libfreetype6-dev libgconf2-4 libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-dev libgettextpo0 libgirepository-1.0-1 libglib2.0-bin libglib2.0-data libgtk2.0-0 libgtk2.0-common libgtk2.0-dev libhtml-parser-perl libhtml-tagset-perl libhtml-tree-perl libhttp-cookies-perl libhttp-date-perl libhttp-message-perl libhttp-negotiate-perl libice-dev libice6 libio-socket-ssl-perl libjasper1 libjpeg8 liblwp-mediatypes-perl liblwp-protocol-https-perl libmagic1 libnet-http-perl libnet-ssleay-perl libpango1.0-0 libpango1.0-dev libpipeline1 libpixman-1-0 libpixman-1-dev libpng12-dev libpopt0 libpthread-stubs0 libpthread-stubs0-dev libpython2.7 libsm-dev libsm6 libssl-dev libthai-data libthai0 libtiff4 libunistring0 liburi-perl libwww-perl libwww-robotrules-perl libx11-6 libx11-data libx11-dev libxau-dev libxau6 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-parser-perl libxml2 libxml2-utils libxrandr-dev libxrandr2 libxrender-dev libxrender1 m4 man-db mime-support pkg-config po-debconf psmisc python-cairo python-dev python-gi python-gi-dev python-gobject python-gobject-2 python-gobject-2-dev python-gobject-dev python-gtk2 python-scour python-support python2.7 python2.7-dev 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 bsd-mailx mailx cvs-buildpackage debian-keyring devscripts-el equivs gnuplot libauthen-sasl-perl libcrypt-ssleay-perl libfile-desktopentry-perl libnet-smtp-ssl-perl libsoap-lite-perl libterm-size-perl libyaml-syck-perl mutt ssh-client svn-buildpackage w3m defoma gconf-defaults-service gettext-doc groff libcairo2-doc cups-common libglib2.0-doc librsvg2-common gvfs libgtk2.0-doc libdata-dump-perl libjasper-runtime ttf-baekmuk ttf-arphic-gbsn00lp ttf-arphic-bsmi00lp ttf-arphic-gkai00mp ttf-arphic-bkai00mp libpango1.0-doc imagemagick libauthen-ntlm-perl less www-browser libmail-box-perl python-doc python-tk python-gi-cairo python-gobject-2-dbg python-gtk2-doc python-rsvg python2.7-doc Recommended packages: at curl wget dctrl-tools dput dupload libjson-perl libparse-debcontrol-perl lintian patchutils python-debian python-magic strace unzip wdiff libgtk-3-0 hicolor-icon-theme libgtk2.0-bin libio-socket-inet6-perl x-ttcidfont-conf libssl-doc libhtml-form-perl libhtml-format-perl libhttp-daemon-perl libmailtools-perl libx11-doc xml-core libmail-sendmail-perl docbook-xsl The following NEW packages will be installed: autoconf automake autotools-dev bsdmainutils cdbs dbus dbus-x11 debhelper devscripts dh-buildinfo dh-translations file fontconfig fontconfig-config gconf2 gconf2-common gettext gettext-base gir1.2-atk-1.0 gir1.2-freedesktop gir1.2-gconf-2.0 gir1.2-gdkpixbuf-2.0 gir1.2-glib-2.0 gir1.2-pango-1.0 groff-base html2text intltool intltool-debian libatk1.0-0 libatk1.0-data libatk1.0-dev libavahi-client3 libavahi-common-data libavahi-common3 libcairo-gobject2 libcairo-script-interpreter2 libcairo2 libcairo2-dev libcroco3 libcups2 libdatrie1 libdb4.8 libdbus-1-dev libdbus-glib-1-2 libencode-locale-perl libexpat1 libexpat1-dev libffi-dev libfile-listing-perl libfontconfig1 libfontconfig1-dev libfreetype6 libfreetype6-dev libgconf2-4 libgconf2-dev libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-dev libgettextpo0 libgirepository-1.0-1 libglib2.0-bin libglib2.0-data libglib2.0-dev libgtk2.0-0 libgtk2.0-common libgtk2.0-dev libhtml-parser-perl libhtml-tagset-perl libhtml-tree-perl libhttp-cookies-perl libhttp-date-perl libhttp-message-perl libhttp-negotiate-perl libice-dev libice6 libio-socket-ssl-perl libjasper1 libjpeg8 liblwp-mediatypes-perl liblwp-protocol-https-perl libmagic1 libnet-http-perl libnet-ssleay-perl libpango1.0-0 libpango1.0-dev libpipeline1 libpixman-1-0 libpixman-1-dev libpng12-dev libpopt0 libpthread-stubs0 libpthread-stubs0-dev libpython2.7 libsm-dev libsm6 libssl-dev libthai-data libthai0 libtiff4 libunistring0 liburi-perl libwww-perl libwww-robotrules-perl libx11-6 libx11-data libx11-dev libxau-dev libxau6 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-parser-perl libxml2 libxml2-utils libxrandr-dev libxrandr2 libxrender-dev libxrender1 m4 man-db mime-support pkg-config po-debconf psmisc python python-cairo python-central python-dev python-empy python-gi python-gi-dev python-gobject python-gobject-2 python-gobject-2-dev python-gobject-dev python-gtk2 python-gtk2-dev python-scour python-support python2.7 python2.7-dev 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, 178 newly installed, 0 to remove and 0 not upgraded. Need to get 45.9 MB of archives. After this operation, 161 MB of additional disk space will be used. WARNING: The following packages cannot be authenticated! libdb4.8 libexpat1 libpopt0 libfreetype6 ucf ttf-dejavu-core fontconfig-config libfontconfig1 libpixman-1-0 libxau6 libxdmcp6 libxcb1 libx11-data libx11-6 libxcb-render0 libxcb-shm0 libxrender1 libcairo2 libdbus-glib-1-2 libpipeline1 libxext6 libxml2 libatk1.0-data libatk1.0-0 libavahi-common-data libavahi-common3 libavahi-client3 libcairo-gobject2 libcairo-script-interpreter2 libcroco3 libcups2 libdatrie1 libjpeg8 libjasper1 libtiff4 libgdk-pixbuf2.0-0 libunistring0 libgettextpo0 libgtk2.0-common libthai-data libthai0 libxft2 fontconfig libpango1.0-0 libxcomposite1 libxfixes3 libxcursor1 libxdamage1 libxi6 libxinerama1 libxrandr2 shared-mime-info libgtk2.0-0 x11-common libice6 libsm6 libmagic1 file mime-support python2.7 python bsdmainutils dbus gettext-base libgirepository-1.0-1 gir1.2-glib-2.0 groff-base man-db psmisc python-cairo python-gi python-gobject-2 python-gobject m4 autoconf autotools-dev automake html2text gettext intltool-debian po-debconf debhelper liburi-perl libencode-locale-perl libhttp-date-perl libfile-listing-perl libhtml-tagset-perl libhtml-parser-perl libhtml-tree-perl liblwp-mediatypes-perl libhttp-message-perl libhttp-cookies-perl libhttp-negotiate-perl libnet-http-perl libnet-ssleay-perl libio-socket-ssl-perl liblwp-protocol-https-perl libwww-robotrules-perl libwww-perl libxml-parser-perl intltool dh-translations python-scour cdbs dbus-x11 devscripts dh-buildinfo gconf2-common libgconf2-4 gconf2 gir1.2-atk-1.0 gir1.2-freedesktop gir1.2-gconf-2.0 gir1.2-gdkpixbuf-2.0 gir1.2-pango-1.0 pkg-config libglib2.0-data libglib2.0-bin zlib1g-dev libglib2.0-dev libatk1.0-dev libexpat1-dev libfreetype6-dev libfontconfig1-dev xorg-sgml-doctools x11proto-core-dev libxau-dev libxdmcp-dev x11proto-input-dev x11proto-kb-dev xtrans-dev libpthread-stubs0 libpthread-stubs0-dev libxcb1-dev libx11-dev x11proto-render-dev libxrender-dev libpng12-dev libice-dev libsm-dev libpixman-1-dev libxcb-render0-dev libxcb-shm0-dev libcairo2-dev libdbus-1-dev libgconf2-dev libgdk-pixbuf2.0-dev libxft-dev libpango1.0-dev x11proto-xext-dev libxext-dev x11proto-xinerama-dev libxinerama-dev 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 libpython2.7 libssl-dev python-central python2.7-dev python-dev python-support python-empy libffi-dev python-gi-dev python-gobject-2-dev python-gobject-dev python-gtk2 python-gtk2-dev Authentication warning overridden. Get:1 http://ftpmaster.internal/ubuntu/ precise/main libdb4.8 i386 4.8.30-10 [711 kB] Get:2 http://ftpmaster.internal/ubuntu/ precise/main libexpat1 i386 2.0.1-7.2 [130 kB] Get:3 http://ftpmaster.internal/ubuntu/ precise/main libpopt0 i386 1.16-1ubuntu1 [29.0 kB] Get:4 http://ftpmaster.internal/ubuntu/ precise/main libfreetype6 i386 2.4.8-1 [344 kB] Get:5 http://ftpmaster.internal/ubuntu/ precise/main ucf all 3.0025+nmu2ubuntu1 [54.4 kB] Get:6 http://ftpmaster.internal/ubuntu/ precise/main ttf-dejavu-core i386 2.33-2 [1550 kB] Get:7 http://ftpmaster.internal/ubuntu/ precise/main fontconfig-config i386 2.8.0-3ubuntu2 [44.5 kB] Get:8 http://ftpmaster.internal/ubuntu/ precise/main libfontconfig1 i386 2.8.0-3ubuntu2 [125 kB] Get:9 http://ftpmaster.internal/ubuntu/ precise/main libpixman-1-0 i386 0.24.0-1 [243 kB] Get:10 http://ftpmaster.internal/ubuntu/ precise/main libxau6 i386 1:1.0.6-4 [8344 B] Get:11 http://ftpmaster.internal/ubuntu/ precise/main libxdmcp6 i386 1:1.1.0-4 [13.0 kB] Get:12 http://ftpmaster.internal/ubuntu/ precise/main libxcb1 i386 1.7-4 [44.2 kB] Get:13 http://ftpmaster.internal/ubuntu/ precise/main libx11-data i386 2:1.4.4-4 [172 kB] Get:14 http://ftpmaster.internal/ubuntu/ precise/main libx11-6 i386 2:1.4.4-4 [772 kB] Get:15 http://ftpmaster.internal/ubuntu/ precise/main libxcb-render0 i386 1.7-4 [12.8 kB] Get:16 http://ftpmaster.internal/ubuntu/ precise/main libxcb-shm0 i386 1.7-4 [5650 B] Get:17 http://ftpmaster.internal/ubuntu/ precise/main libxrender1 i386 1:0.9.6-2 [20.4 kB] Get:18 http://ftpmaster.internal/ubuntu/ precise/main libcairo2 i386 1.10.2-6.1ubuntu2 [490 kB] Get:19 http://ftpmaster.internal/ubuntu/ precise/main libdbus-glib-1-2 i386 0.98-1ubuntu1 [74.3 kB] Get:20 http://ftpmaster.internal/ubuntu/ precise/main libpipeline1 i386 1.2.0-5 [25.7 kB] Get:21 http://ftpmaster.internal/ubuntu/ precise/main libxext6 i386 2:1.3.0-3 [34.8 kB] Get:22 http://ftpmaster.internal/ubuntu/ precise/main libxml2 i386 2.7.8.dfsg-5ubuntu1 [662 kB] Get:23 http://ftpmaster.internal/ubuntu/ precise/main libatk1.0-data i386 2.2.0-2 [12.4 kB] Get:24 http://ftpmaster.internal/ubuntu/ precise/main libatk1.0-0 i386 2.2.0-2 [58.3 kB] Get:25 http://ftpmaster.internal/ubuntu/ precise/main libavahi-common-data i386 0.6.30-5ubuntu1 [22.4 kB] Get:26 http://ftpmaster.internal/ubuntu/ precise/main libavahi-common3 i386 0.6.30-5ubuntu1 [26.0 kB] Get:27 http://ftpmaster.internal/ubuntu/ precise/main libavahi-client3 i386 0.6.30-5ubuntu1 [43.8 kB] Get:28 http://ftpmaster.internal/ubuntu/ precise/main libcairo-gobject2 i386 1.10.2-6.1ubuntu2 [19.5 kB] Get:29 http://ftpmaster.internal/ubuntu/ precise/main libcairo-script-interpreter2 i386 1.10.2-6.1ubuntu2 [62.6 kB] Get:30 http://ftpmaster.internal/ubuntu/ precise/main libcroco3 i386 0.6.2-2 [100 kB] Get:31 http://ftpmaster.internal/ubuntu/ precise/main libcups2 i386 1.5.0-13build1 [175 kB] Get:32 http://ftpmaster.internal/ubuntu/ precise/main libdatrie1 i386 0.2.5-2 [17.0 kB] Get:33 http://ftpmaster.internal/ubuntu/ precise/main libjpeg8 i386 8c-2ubuntu4 [121 kB] Get:34 http://ftpmaster.internal/ubuntu/ precise/main libjasper1 i386 1.900.1-11 [153 kB] Get:35 http://ftpmaster.internal/ubuntu/ precise/main libtiff4 i386 3.9.5-2 [142 kB] Get:36 http://ftpmaster.internal/ubuntu/ precise/main libgdk-pixbuf2.0-0 i386 2.24.0-1ubuntu2 [190 kB] Get:37 http://ftpmaster.internal/ubuntu/ precise/main libunistring0 i386 0.9.3-5 [432 kB] Get:38 http://ftpmaster.internal/ubuntu/ precise/main libgettextpo0 i386 0.18.1.1-5ubuntu3 [118 kB] Get:39 http://ftpmaster.internal/ubuntu/ precise/main libgtk2.0-common i386 2.24.8-0ubuntu4 [535 kB] Get:40 http://ftpmaster.internal/ubuntu/ precise/main libthai-data i386 0.1.16-2 [178 kB] Get:41 http://ftpmaster.internal/ubuntu/ precise/main libthai0 i386 0.1.16-2 [20.2 kB] Get:42 http://ftpmaster.internal/ubuntu/ precise/main libxft2 i386 2.2.0-3ubuntu1 [42.4 kB] Get:43 http://ftpmaster.internal/ubuntu/ precise/main fontconfig i386 2.8.0-3ubuntu2 [157 kB] Get:44 http://ftpmaster.internal/ubuntu/ precise/main libpango1.0-0 i386 1.29.4-2ubuntu1 [365 kB] Get:45 http://ftpmaster.internal/ubuntu/ precise/main libxcomposite1 i386 1:0.4.3-2 [7718 B] Get:46 http://ftpmaster.internal/ubuntu/ precise/main libxfixes3 i386 1:5.0-4 [12.6 kB] Get:47 http://ftpmaster.internal/ubuntu/ precise/main libxcursor1 i386 1:1.1.12-1 [23.0 kB] Get:48 http://ftpmaster.internal/ubuntu/ precise/main libxdamage1 i386 1:1.1.3-2 [7368 B] Get:49 http://ftpmaster.internal/ubuntu/ precise/main libxi6 i386 2:1.4.3-3ubuntu1 [31.2 kB] Get:50 http://ftpmaster.internal/ubuntu/ precise/main libxinerama1 i386 2:1.1.1-3 [8092 B] Get:51 http://ftpmaster.internal/ubuntu/ precise/main libxrandr2 i386 2:1.3.2-2 [17.7 kB] Get:52 http://ftpmaster.internal/ubuntu/ precise/main shared-mime-info i386 0.91-0ubuntu1 [451 kB] Get:53 http://ftpmaster.internal/ubuntu/ precise/main libgtk2.0-0 i386 2.24.8-0ubuntu4 [2675 kB] Get:54 http://ftpmaster.internal/ubuntu/ precise/main x11-common i386 1:7.6+7ubuntu7 [56.6 kB] Get:55 http://ftpmaster.internal/ubuntu/ precise/main libice6 i386 2:1.0.7-2 [44.8 kB] Get:56 http://ftpmaster.internal/ubuntu/ precise/main libsm6 i386 2:1.2.0-2 [17.6 kB] Get:57 http://ftpmaster.internal/ubuntu/ precise/main libmagic1 i386 5.09-2 [219 kB] Get:58 http://ftpmaster.internal/ubuntu/ precise/main file i386 5.09-2 [19.4 kB] Get:59 http://ftpmaster.internal/ubuntu/ precise/main mime-support all 3.51-1ubuntu1 [30.7 kB] Get:60 http://ftpmaster.internal/ubuntu/ precise/main python2.7 i386 2.7.2-8build1 [2573 kB] Get:61 http://ftpmaster.internal/ubuntu/ precise/main python all 2.7.2-9ubuntu1 [168 kB] Get:62 http://ftpmaster.internal/ubuntu/ precise/main bsdmainutils i386 8.2.3 [196 kB] Get:63 http://ftpmaster.internal/ubuntu/ precise/main dbus i386 1.4.16-1ubuntu1 [552 kB] Get:64 http://ftpmaster.internal/ubuntu/ precise/main gettext-base i386 0.18.1.1-5ubuntu3 [58.2 kB] Get:65 http://ftpmaster.internal/ubuntu/ precise/main libgirepository-1.0-1 i386 1.31.0-1 [103 kB] Get:66 http://ftpmaster.internal/ubuntu/ precise/main gir1.2-glib-2.0 i386 1.31.0-1 [153 kB] Get:67 http://ftpmaster.internal/ubuntu/ precise/main groff-base i386 1.21-6 [1024 kB] Get:68 http://ftpmaster.internal/ubuntu/ precise/main man-db i386 2.6.0.2-3 [721 kB] Get:69 http://ftpmaster.internal/ubuntu/ precise/main psmisc i386 22.14-1 [51.4 kB] Get:70 http://ftpmaster.internal/ubuntu/ precise/main python-cairo i386 1.8.8-1ubuntu2 [80.3 kB] Get:71 http://ftpmaster.internal/ubuntu/ precise/main python-gi i386 3.0.2-4 [212 kB] Get:72 http://ftpmaster.internal/ubuntu/ precise/main python-gobject-2 i386 2.28.6-7 [228 kB] Get:73 http://ftpmaster.internal/ubuntu/ precise/main python-gobject all 3.0.2-4 [2452 B] Get:74 http://ftpmaster.internal/ubuntu/ precise/main m4 i386 1.4.16-2ubuntu1 [195 kB] Get:75 http://ftpmaster.internal/ubuntu/ precise/main autoconf i386 2.68-1ubuntu2 [560 kB] Get:76 http://ftpmaster.internal/ubuntu/ precise/main autotools-dev all 20110511.1 [44.7 kB] Get:77 http://ftpmaster.internal/ubuntu/ precise/main automake i386 1:1.11.1-1ubuntu2 [544 kB] Get:78 http://ftpmaster.internal/ubuntu/ precise/main html2text i386 1.3.2a-15 [101 kB] Get:79 http://ftpmaster.internal/ubuntu/ precise/main gettext i386 0.18.1.1-5ubuntu3 [1122 kB] Get:80 http://ftpmaster.internal/ubuntu/ precise/main intltool-debian all 0.35.0+20060710.1 [31.6 kB] Get:81 http://ftpmaster.internal/ubuntu/ precise/main po-debconf i386 1.0.16+nmu1ubuntu1 [211 kB] Get:82 http://ftpmaster.internal/ubuntu/ precise/main debhelper i386 8.9.9ubuntu1 [477 kB] Get:83 http://ftpmaster.internal/ubuntu/ precise/main liburi-perl all 1.59-1 [90.3 kB] Get:84 http://ftpmaster.internal/ubuntu/ precise/main libencode-locale-perl all 1.02-2 [12.0 kB] Get:85 http://ftpmaster.internal/ubuntu/ precise/main libhttp-date-perl all 6.00-1 [10.1 kB] Get:86 http://ftpmaster.internal/ubuntu/ precise/main libfile-listing-perl all 6.03-1 [9690 B] Get:87 http://ftpmaster.internal/ubuntu/ precise/main libhtml-tagset-perl all 3.20-2 [13.5 kB] Get:88 http://ftpmaster.internal/ubuntu/ precise/main libhtml-parser-perl i386 3.69-1build1 [99.2 kB] Get:89 http://ftpmaster.internal/ubuntu/ precise/main libhtml-tree-perl all 4.2-1 [205 kB] Get:90 http://ftpmaster.internal/ubuntu/ precise/main liblwp-mediatypes-perl all 6.01-1 [17.5 kB] Get:91 http://ftpmaster.internal/ubuntu/ precise/main libhttp-message-perl all 6.01-1 [77.6 kB] Get:92 http://ftpmaster.internal/ubuntu/ precise/main libhttp-cookies-perl all 6.00-2 [23.3 kB] Get:93 http://ftpmaster.internal/ubuntu/ precise/main libhttp-negotiate-perl all 6.00-2 [13.4 kB] Get:94 http://ftpmaster.internal/ubuntu/ precise/main libnet-http-perl all 6.01-1 [20.5 kB] Get:95 http://ftpmaster.internal/ubuntu/ precise/main libnet-ssleay-perl i386 1.42-1build1 [184 kB] Get:96 http://ftpmaster.internal/ubuntu/ precise/main libio-socket-ssl-perl all 1.49-1 [47.5 kB] Get:97 http://ftpmaster.internal/ubuntu/ precise/main liblwp-protocol-https-perl all 6.02-1 [6746 B] Get:98 http://ftpmaster.internal/ubuntu/ precise/main libwww-robotrules-perl all 6.01-1 [14.1 kB] Get:99 http://ftpmaster.internal/ubuntu/ precise/main libwww-perl all 6.03-1 [156 kB] Get:100 http://ftpmaster.internal/ubuntu/ precise/main libxml-parser-perl i386 2.41-1build1 [264 kB] Get:101 http://ftpmaster.internal/ubuntu/ precise/main intltool all 0.41.1-3 [100 kB] Get:102 http://ftpmaster.internal/ubuntu/ precise/main dh-translations all 109 [20.9 kB] Get:103 http://ftpmaster.internal/ubuntu/ precise/main python-scour all 0.26-2 [46.3 kB] Get:104 http://ftpmaster.internal/ubuntu/ precise/main cdbs all 0.4.99ubuntu1 [48.9 kB] Get:105 http://ftpmaster.internal/ubuntu/ precise/main dbus-x11 i386 1.4.16-1ubuntu1 [24.8 kB] Get:106 http://ftpmaster.internal/ubuntu/ precise/main devscripts i386 2.11.1ubuntu5 [613 kB] Get:107 http://ftpmaster.internal/ubuntu/ precise/main dh-buildinfo all 0.9 [15.3 kB] Get:108 http://ftpmaster.internal/ubuntu/ precise/main gconf2-common all 3.2.3-1ubuntu1 [20.5 kB] Get:109 http://ftpmaster.internal/ubuntu/ precise/main libgconf2-4 i386 3.2.3-1ubuntu1 [165 kB] Get:110 http://ftpmaster.internal/ubuntu/ precise/main gconf2 i386 3.2.3-1ubuntu1 [77.8 kB] Get:111 http://ftpmaster.internal/ubuntu/ precise/main gir1.2-atk-1.0 i386 2.2.0-2 [22.4 kB] Get:112 http://ftpmaster.internal/ubuntu/ precise/main gir1.2-freedesktop i386 1.31.0-1 [15.9 kB] Get:113 http://ftpmaster.internal/ubuntu/ precise/main gir1.2-gconf-2.0 i386 3.2.3-1ubuntu1 [7062 B] Get:114 http://ftpmaster.internal/ubuntu/ precise/main gir1.2-gdkpixbuf-2.0 i386 2.24.0-1ubuntu2 [8706 B] Get:115 http://ftpmaster.internal/ubuntu/ precise/main gir1.2-pango-1.0 i386 1.29.4-2ubuntu1 [25.6 kB] Get:116 http://ftpmaster.internal/ubuntu/ precise/main pkg-config i386 0.26-1ubuntu1 [40.3 kB] Get:117 http://ftpmaster.internal/ubuntu/ precise/main libglib2.0-data i386 2.30.1-2ubuntu1 [78.4 kB] Get:118 http://ftpmaster.internal/ubuntu/ precise/main libglib2.0-bin i386 2.30.1-2ubuntu1 [33.0 kB] Get:119 http://ftpmaster.internal/ubuntu/ precise/main zlib1g-dev i386 1:1.2.3.4.dfsg-3ubuntu4 [162 kB] Get:120 http://ftpmaster.internal/ubuntu/ precise/main libglib2.0-dev i386 2.30.1-2ubuntu1 [1662 kB] Get:121 http://ftpmaster.internal/ubuntu/ precise/main libatk1.0-dev i386 2.2.0-2 [126 kB] Get:122 http://ftpmaster.internal/ubuntu/ precise/main libexpat1-dev i386 2.0.1-7.2 [207 kB] Get:123 http://ftpmaster.internal/ubuntu/ precise/main libfreetype6-dev i386 2.4.8-1 [778 kB] Get:124 http://ftpmaster.internal/ubuntu/ precise/main libfontconfig1-dev i386 2.8.0-3ubuntu2 [652 kB] Get:125 http://ftpmaster.internal/ubuntu/ precise/main xorg-sgml-doctools i386 1:1.8-2 [10.9 kB] Get:126 http://ftpmaster.internal/ubuntu/ precise/main x11proto-core-dev i386 7.0.22-1 [299 kB] Get:127 http://ftpmaster.internal/ubuntu/ precise/main libxau-dev i386 1:1.0.6-4 [10.2 kB] Get:128 http://ftpmaster.internal/ubuntu/ precise/main libxdmcp-dev i386 1:1.1.0-4 [26.5 kB] Get:129 http://ftpmaster.internal/ubuntu/ precise/main x11proto-input-dev i386 2.0.2-2ubuntu1 [69.0 kB] Get:130 http://ftpmaster.internal/ubuntu/ precise/main x11proto-kb-dev i386 1.0.5-2 [27.6 kB] Get:131 http://ftpmaster.internal/ubuntu/ precise/main xtrans-dev i386 1.2.6-2 [82.9 kB] Get:132 http://ftpmaster.internal/ubuntu/ precise/main libpthread-stubs0 i386 0.3-2.1ubuntu1 [3360 B] Get:133 http://ftpmaster.internal/ubuntu/ precise/main libpthread-stubs0-dev i386 0.3-2.1ubuntu1 [2482 B] Get:134 http://ftpmaster.internal/ubuntu/ precise/main libxcb1-dev i386 1.7-4 [77.8 kB] Get:135 http://ftpmaster.internal/ubuntu/ precise/main libx11-dev i386 2:1.4.4-4 [899 kB] Get:136 http://ftpmaster.internal/ubuntu/ precise/main x11proto-render-dev i386 2:0.11.1-2 [20.1 kB] Get:137 http://ftpmaster.internal/ubuntu/ precise/main libxrender-dev i386 1:0.9.6-2 [27.7 kB] Get:138 http://ftpmaster.internal/ubuntu/ precise/main libpng12-dev i386 1.2.46-3ubuntu1 [207 kB] Get:139 http://ftpmaster.internal/ubuntu/ precise/main libice-dev i386 2:1.0.7-2 [128 kB] Get:140 http://ftpmaster.internal/ubuntu/ precise/main libsm-dev i386 2:1.2.0-2 [86.4 kB] Get:141 http://ftpmaster.internal/ubuntu/ precise/main libpixman-1-dev i386 0.24.0-1 [268 kB] Get:142 http://ftpmaster.internal/ubuntu/ precise/main libxcb-render0-dev i386 1.7-4 [21.3 kB] Get:143 http://ftpmaster.internal/ubuntu/ precise/main libxcb-shm0-dev i386 1.7-4 [8364 B] Get:144 http://ftpmaster.internal/ubuntu/ precise/main libcairo2-dev i386 1.10.2-6.1ubuntu2 [569 kB] Get:145 http://ftpmaster.internal/ubuntu/ precise/main libdbus-1-dev i386 1.4.16-1ubuntu1 [213 kB] Get:146 http://ftpmaster.internal/ubuntu/ precise/main libgconf2-dev i386 3.2.3-1ubuntu1 [200 kB] Get:147 http://ftpmaster.internal/ubuntu/ precise/main libgdk-pixbuf2.0-dev i386 2.24.0-1ubuntu2 [49.0 kB] Get:148 http://ftpmaster.internal/ubuntu/ precise/main libxft-dev i386 2.2.0-3ubuntu1 [51.7 kB] Get:149 http://ftpmaster.internal/ubuntu/ precise/main libpango1.0-dev i386 1.29.4-2ubuntu1 [477 kB] Get:150 http://ftpmaster.internal/ubuntu/ precise/main x11proto-xext-dev i386 7.2.0-3 [253 kB] Get:151 http://ftpmaster.internal/ubuntu/ precise/main libxext-dev i386 2:1.3.0-3 [141 kB] Get:152 http://ftpmaster.internal/ubuntu/ precise/main x11proto-xinerama-dev i386 1.2.1-2 [4966 B] Get:153 http://ftpmaster.internal/ubuntu/ precise/main libxinerama-dev i386 2:1.1.1-3 [8364 B] Get:154 http://ftpmaster.internal/ubuntu/ precise/main libxi-dev i386 2:1.4.3-3ubuntu1 [216 kB] Get:155 http://ftpmaster.internal/ubuntu/ precise/main x11proto-randr-dev i386 1.4.0+git20101207.0d32bb07-0ubuntu2 [32.0 kB] Get:156 http://ftpmaster.internal/ubuntu/ precise/main libxrandr-dev i386 2:1.3.2-2 [24.1 kB] Get:157 http://ftpmaster.internal/ubuntu/ precise/main x11proto-fixes-dev i386 1:5.0-2 [14.4 kB] Get:158 http://ftpmaster.internal/ubuntu/ precise/main libxfixes-dev i386 1:5.0-4 [13.5 kB] Get:159 http://ftpmaster.internal/ubuntu/ precise/main libxcursor-dev i386 1:1.1.12-1 [29.3 kB] Get:160 http://ftpmaster.internal/ubuntu/ precise/main x11proto-composite-dev i386 1:0.4.2-2 [10.5 kB] Get:161 http://ftpmaster.internal/ubuntu/ precise/main libxcomposite-dev i386 1:0.4.3-2 [9700 B] Get:162 http://ftpmaster.internal/ubuntu/ precise/main x11proto-damage-dev i386 1:1.2.1-2 [8286 B] Get:163 http://ftpmaster.internal/ubuntu/ precise/main libxdamage-dev i386 1:1.1.3-2 [5454 B] Get:164 http://ftpmaster.internal/ubuntu/ precise/main libxml2-utils i386 2.7.8.dfsg-5ubuntu1 [40.2 kB] Get:165 http://ftpmaster.internal/ubuntu/ precise/main libgtk2.0-dev i386 2.24.8-0ubuntu4 [3696 kB] Get:166 http://ftpmaster.internal/ubuntu/ precise/main libpython2.7 i386 2.7.2-8build1 [1134 kB] Get:167 http://ftpmaster.internal/ubuntu/ precise/main libssl-dev i386 1.0.0e-2ubuntu4 [1398 kB] Get:168 http://ftpmaster.internal/ubuntu/ precise/main python-central all 0.6.17 [41.5 kB] Get:169 http://ftpmaster.internal/ubuntu/ precise/main python2.7-dev i386 2.7.2-8build1 [4902 kB] Get:170 http://ftpmaster.internal/ubuntu/ precise/main python-dev all 2.7.2-9ubuntu1 [1006 B] Get:171 http://ftpmaster.internal/ubuntu/ precise/main python-support all 1.0.14ubuntu2 [26.1 kB] Get:172 http://ftpmaster.internal/ubuntu/ precise/universe python-empy all 3.3-6ubuntu1 [103 kB] Get:173 http://ftpmaster.internal/ubuntu/ precise/main libffi-dev i386 3.0.11~rc1-5 [87.0 kB] Get:174 http://ftpmaster.internal/ubuntu/ precise/main python-gi-dev all 3.0.2-4 [8712 B] Get:175 http://ftpmaster.internal/ubuntu/ precise/main python-gobject-2-dev all 2.28.6-7 [268 kB] Get:176 http://ftpmaster.internal/ubuntu/ precise/main python-gobject-dev all 3.0.2-4 [5522 B] Get:177 http://ftpmaster.internal/ubuntu/ precise/main python-gtk2 i386 2.24.0-2 [1605 kB] Get:178 http://ftpmaster.internal/ubuntu/ precise/main python-gtk2-dev all 2.24.0-2 [142 kB] debconf: delaying package configuration, since apt-utils is not installed Fetched 45.9 MB in 4s (10.2 MB/s) Selecting previously unselected package libdb4.8. (Reading database ... 14283 files and directories currently installed.) Unpacking libdb4.8 (from .../libdb4.8_4.8.30-10_i386.deb) ... Selecting previously unselected package libexpat1. Unpacking libexpat1 (from .../libexpat1_2.0.1-7.2_i386.deb) ... Selecting previously unselected package libpopt0. Unpacking libpopt0 (from .../libpopt0_1.16-1ubuntu1_i386.deb) ... Selecting previously unselected package libfreetype6. Unpacking libfreetype6 (from .../libfreetype6_2.4.8-1_i386.deb) ... Selecting previously unselected package ucf. Unpacking ucf (from .../ucf_3.0025+nmu2ubuntu1_all.deb) ... Moving old data out of the way Selecting previously unselected package ttf-dejavu-core. Unpacking ttf-dejavu-core (from .../ttf-dejavu-core_2.33-2_i386.deb) ... Selecting previously unselected package fontconfig-config. Unpacking fontconfig-config (from .../fontconfig-config_2.8.0-3ubuntu2_i386.deb) ... Selecting previously unselected package libfontconfig1. Unpacking libfontconfig1 (from .../libfontconfig1_2.8.0-3ubuntu2_i386.deb) ... Selecting previously unselected package libpixman-1-0. Unpacking libpixman-1-0 (from .../libpixman-1-0_0.24.0-1_i386.deb) ... Selecting previously unselected package libxau6. Unpacking libxau6 (from .../libxau6_1%3a1.0.6-4_i386.deb) ... Selecting previously unselected package libxdmcp6. Unpacking libxdmcp6 (from .../libxdmcp6_1%3a1.1.0-4_i386.deb) ... Selecting previously unselected package libxcb1. Unpacking libxcb1 (from .../libxcb1_1.7-4_i386.deb) ... Selecting previously unselected package libx11-data. Unpacking libx11-data (from .../libx11-data_2%3a1.4.4-4_i386.deb) ... Selecting previously unselected package libx11-6. Unpacking libx11-6 (from .../libx11-6_2%3a1.4.4-4_i386.deb) ... Selecting previously unselected package libxcb-render0. Unpacking libxcb-render0 (from .../libxcb-render0_1.7-4_i386.deb) ... Selecting previously unselected package libxcb-shm0. Unpacking libxcb-shm0 (from .../libxcb-shm0_1.7-4_i386.deb) ... Selecting previously unselected package libxrender1. Unpacking libxrender1 (from .../libxrender1_1%3a0.9.6-2_i386.deb) ... Selecting previously unselected package libcairo2. Unpacking libcairo2 (from .../libcairo2_1.10.2-6.1ubuntu2_i386.deb) ... Selecting previously unselected package libdbus-glib-1-2. Unpacking libdbus-glib-1-2 (from .../libdbus-glib-1-2_0.98-1ubuntu1_i386.deb) ... Selecting previously unselected package libpipeline1. Unpacking libpipeline1 (from .../libpipeline1_1.2.0-5_i386.deb) ... Selecting previously unselected package libxext6. Unpacking libxext6 (from .../libxext6_2%3a1.3.0-3_i386.deb) ... Selecting previously unselected package libxml2. Unpacking libxml2 (from .../libxml2_2.7.8.dfsg-5ubuntu1_i386.deb) ... Selecting previously unselected package libatk1.0-data. Unpacking libatk1.0-data (from .../libatk1.0-data_2.2.0-2_i386.deb) ... Selecting previously unselected package libatk1.0-0. Unpacking libatk1.0-0 (from .../libatk1.0-0_2.2.0-2_i386.deb) ... Selecting previously unselected package libavahi-common-data. Unpacking libavahi-common-data (from .../libavahi-common-data_0.6.30-5ubuntu1_i386.deb) ... Selecting previously unselected package libavahi-common3. Unpacking libavahi-common3 (from .../libavahi-common3_0.6.30-5ubuntu1_i386.deb) ... Selecting previously unselected package libavahi-client3. Unpacking libavahi-client3 (from .../libavahi-client3_0.6.30-5ubuntu1_i386.deb) ... Selecting previously unselected package libcairo-gobject2. Unpacking libcairo-gobject2 (from .../libcairo-gobject2_1.10.2-6.1ubuntu2_i386.deb) ... Selecting previously unselected package libcairo-script-interpreter2. Unpacking libcairo-script-interpreter2 (from .../libcairo-script-interpreter2_1.10.2-6.1ubuntu2_i386.deb) ... Selecting previously unselected package libcroco3. Unpacking libcroco3 (from .../libcroco3_0.6.2-2_i386.deb) ... Selecting previously unselected package libcups2. Unpacking libcups2 (from .../libcups2_1.5.0-13build1_i386.deb) ... Selecting previously unselected package libdatrie1. Unpacking libdatrie1 (from .../libdatrie1_0.2.5-2_i386.deb) ... Selecting previously unselected package libjpeg8. Unpacking libjpeg8 (from .../libjpeg8_8c-2ubuntu4_i386.deb) ... Selecting previously unselected package libjasper1. Unpacking libjasper1 (from .../libjasper1_1.900.1-11_i386.deb) ... Selecting previously unselected package libtiff4. Unpacking libtiff4 (from .../libtiff4_3.9.5-2_i386.deb) ... Selecting previously unselected package libgdk-pixbuf2.0-0. Unpacking libgdk-pixbuf2.0-0 (from .../libgdk-pixbuf2.0-0_2.24.0-1ubuntu2_i386.deb) ... Selecting previously unselected package libunistring0. Unpacking libunistring0 (from .../libunistring0_0.9.3-5_i386.deb) ... Selecting previously unselected package libgettextpo0. Unpacking libgettextpo0 (from .../libgettextpo0_0.18.1.1-5ubuntu3_i386.deb) ... Selecting previously unselected package libgtk2.0-common. Unpacking libgtk2.0-common (from .../libgtk2.0-common_2.24.8-0ubuntu4_i386.deb) ... Selecting previously unselected package libthai-data. Unpacking libthai-data (from .../libthai-data_0.1.16-2_i386.deb) ... Selecting previously unselected package libthai0. Unpacking libthai0 (from .../libthai0_0.1.16-2_i386.deb) ... Selecting previously unselected package libxft2. Unpacking libxft2 (from .../libxft2_2.2.0-3ubuntu1_i386.deb) ... Selecting previously unselected package fontconfig. Unpacking fontconfig (from .../fontconfig_2.8.0-3ubuntu2_i386.deb) ... Selecting previously unselected package libpango1.0-0. Unpacking libpango1.0-0 (from .../libpango1.0-0_1.29.4-2ubuntu1_i386.deb) ... Selecting previously unselected package libxcomposite1. Unpacking libxcomposite1 (from .../libxcomposite1_1%3a0.4.3-2_i386.deb) ... Selecting previously unselected package libxfixes3. Unpacking libxfixes3 (from .../libxfixes3_1%3a5.0-4_i386.deb) ... Selecting previously unselected package libxcursor1. Unpacking libxcursor1 (from .../libxcursor1_1%3a1.1.12-1_i386.deb) ... Selecting previously unselected package libxdamage1. Unpacking libxdamage1 (from .../libxdamage1_1%3a1.1.3-2_i386.deb) ... Selecting previously unselected package libxi6. Unpacking libxi6 (from .../libxi6_2%3a1.4.3-3ubuntu1_i386.deb) ... Selecting previously unselected package libxinerama1. Unpacking libxinerama1 (from .../libxinerama1_2%3a1.1.1-3_i386.deb) ... Selecting previously unselected package libxrandr2. Unpacking libxrandr2 (from .../libxrandr2_2%3a1.3.2-2_i386.deb) ... Selecting previously unselected package shared-mime-info. Unpacking shared-mime-info (from .../shared-mime-info_0.91-0ubuntu1_i386.deb) ... Selecting previously unselected package libgtk2.0-0. Unpacking libgtk2.0-0 (from .../libgtk2.0-0_2.24.8-0ubuntu4_i386.deb) ... Selecting previously unselected package x11-common. Unpacking x11-common (from .../x11-common_1%3a7.6+7ubuntu7_i386.deb) ... Selecting previously unselected package libice6. Unpacking libice6 (from .../libice6_2%3a1.0.7-2_i386.deb) ... Selecting previously unselected package libsm6. Unpacking libsm6 (from .../libsm6_2%3a1.2.0-2_i386.deb) ... Selecting previously unselected package libmagic1. Unpacking libmagic1 (from .../libmagic1_5.09-2_i386.deb) ... Selecting previously unselected package file. Unpacking file (from .../archives/file_5.09-2_i386.deb) ... Selecting previously unselected package mime-support. Unpacking mime-support (from .../mime-support_3.51-1ubuntu1_all.deb) ... Selecting previously unselected package python2.7. Unpacking python2.7 (from .../python2.7_2.7.2-8build1_i386.deb) ... Selecting previously unselected package python. Unpacking python (from .../python_2.7.2-9ubuntu1_all.deb) ... Selecting previously unselected package bsdmainutils. Unpacking bsdmainutils (from .../bsdmainutils_8.2.3_i386.deb) ... Selecting previously unselected package dbus. Unpacking dbus (from .../dbus_1.4.16-1ubuntu1_i386.deb) ... Selecting previously unselected package gettext-base. Unpacking gettext-base (from .../gettext-base_0.18.1.1-5ubuntu3_i386.deb) ... Selecting previously unselected package libgirepository-1.0-1. Unpacking libgirepository-1.0-1 (from .../libgirepository-1.0-1_1.31.0-1_i386.deb) ... Selecting previously unselected package gir1.2-glib-2.0. Unpacking gir1.2-glib-2.0 (from .../gir1.2-glib-2.0_1.31.0-1_i386.deb) ... Selecting previously unselected package groff-base. Unpacking groff-base (from .../groff-base_1.21-6_i386.deb) ... Selecting previously unselected package man-db. Unpacking man-db (from .../man-db_2.6.0.2-3_i386.deb) ... Selecting previously unselected package psmisc. Unpacking psmisc (from .../psmisc_22.14-1_i386.deb) ... Selecting previously unselected package python-cairo. Unpacking python-cairo (from .../python-cairo_1.8.8-1ubuntu2_i386.deb) ... Selecting previously unselected package python-gi. Unpacking python-gi (from .../python-gi_3.0.2-4_i386.deb) ... Selecting previously unselected package python-gobject-2. Unpacking python-gobject-2 (from .../python-gobject-2_2.28.6-7_i386.deb) ... Selecting previously unselected package python-gobject. Unpacking python-gobject (from .../python-gobject_3.0.2-4_all.deb) ... Selecting previously unselected package m4. Unpacking m4 (from .../m4_1.4.16-2ubuntu1_i386.deb) ... Selecting previously unselected package autoconf. Unpacking autoconf (from .../autoconf_2.68-1ubuntu2_i386.deb) ... Selecting previously unselected package autotools-dev. Unpacking autotools-dev (from .../autotools-dev_20110511.1_all.deb) ... Selecting previously unselected package automake. Unpacking automake (from .../automake_1%3a1.11.1-1ubuntu2_i386.deb) ... Selecting previously unselected package html2text. Unpacking html2text (from .../html2text_1.3.2a-15_i386.deb) ... Selecting previously unselected package gettext. Unpacking gettext (from .../gettext_0.18.1.1-5ubuntu3_i386.deb) ... Selecting previously unselected package intltool-debian. Unpacking intltool-debian (from .../intltool-debian_0.35.0+20060710.1_all.deb) ... Selecting previously unselected package po-debconf. Unpacking po-debconf (from .../po-debconf_1.0.16+nmu1ubuntu1_i386.deb) ... Selecting previously unselected package debhelper. Unpacking debhelper (from .../debhelper_8.9.9ubuntu1_i386.deb) ... Selecting previously unselected package liburi-perl. Unpacking liburi-perl (from .../liburi-perl_1.59-1_all.deb) ... Selecting previously unselected package libencode-locale-perl. Unpacking libencode-locale-perl (from .../libencode-locale-perl_1.02-2_all.deb) ... Selecting previously unselected package libhttp-date-perl. Unpacking libhttp-date-perl (from .../libhttp-date-perl_6.00-1_all.deb) ... Selecting previously unselected package libfile-listing-perl. Unpacking libfile-listing-perl (from .../libfile-listing-perl_6.03-1_all.deb) ... Selecting previously unselected package libhtml-tagset-perl. Unpacking libhtml-tagset-perl (from .../libhtml-tagset-perl_3.20-2_all.deb) ... Selecting previously unselected package libhtml-parser-perl. Unpacking libhtml-parser-perl (from .../libhtml-parser-perl_3.69-1build1_i386.deb) ... Selecting previously unselected package libhtml-tree-perl. Unpacking libhtml-tree-perl (from .../libhtml-tree-perl_4.2-1_all.deb) ... Selecting previously unselected package liblwp-mediatypes-perl. Unpacking liblwp-mediatypes-perl (from .../liblwp-mediatypes-perl_6.01-1_all.deb) ... Selecting previously unselected package libhttp-message-perl. Unpacking libhttp-message-perl (from .../libhttp-message-perl_6.01-1_all.deb) ... Selecting previously unselected package libhttp-cookies-perl. Unpacking libhttp-cookies-perl (from .../libhttp-cookies-perl_6.00-2_all.deb) ... Selecting previously unselected package libhttp-negotiate-perl. Unpacking libhttp-negotiate-perl (from .../libhttp-negotiate-perl_6.00-2_all.deb) ... Selecting previously unselected package libnet-http-perl. Unpacking libnet-http-perl (from .../libnet-http-perl_6.01-1_all.deb) ... Selecting previously unselected package libnet-ssleay-perl. Unpacking libnet-ssleay-perl (from .../libnet-ssleay-perl_1.42-1build1_i386.deb) ... Selecting previously unselected package libio-socket-ssl-perl. Unpacking libio-socket-ssl-perl (from .../libio-socket-ssl-perl_1.49-1_all.deb) ... Selecting previously unselected package liblwp-protocol-https-perl. Unpacking liblwp-protocol-https-perl (from .../liblwp-protocol-https-perl_6.02-1_all.deb) ... Selecting previously unselected package libwww-robotrules-perl. Unpacking libwww-robotrules-perl (from .../libwww-robotrules-perl_6.01-1_all.deb) ... Selecting previously unselected package libwww-perl. Unpacking libwww-perl (from .../libwww-perl_6.03-1_all.deb) ... Selecting previously unselected package libxml-parser-perl. Unpacking libxml-parser-perl (from .../libxml-parser-perl_2.41-1build1_i386.deb) ... Selecting previously unselected package intltool. Unpacking intltool (from .../intltool_0.41.1-3_all.deb) ... Selecting previously unselected package dh-translations. Unpacking dh-translations (from .../dh-translations_109_all.deb) ... Selecting previously unselected package python-scour. Unpacking python-scour (from .../python-scour_0.26-2_all.deb) ... Selecting previously unselected package cdbs. Unpacking cdbs (from .../cdbs_0.4.99ubuntu1_all.deb) ... Selecting previously unselected package dbus-x11. Unpacking dbus-x11 (from .../dbus-x11_1.4.16-1ubuntu1_i386.deb) ... Selecting previously unselected package devscripts. Unpacking devscripts (from .../devscripts_2.11.1ubuntu5_i386.deb) ... Selecting previously unselected package dh-buildinfo. Unpacking dh-buildinfo (from .../dh-buildinfo_0.9_all.deb) ... Selecting previously unselected package gconf2-common. Unpacking gconf2-common (from .../gconf2-common_3.2.3-1ubuntu1_all.deb) ... Selecting previously unselected package libgconf2-4. Unpacking libgconf2-4 (from .../libgconf2-4_3.2.3-1ubuntu1_i386.deb) ... Selecting previously unselected package gconf2. Unpacking gconf2 (from .../gconf2_3.2.3-1ubuntu1_i386.deb) ... Selecting previously unselected package gir1.2-atk-1.0. Unpacking gir1.2-atk-1.0 (from .../gir1.2-atk-1.0_2.2.0-2_i386.deb) ... Selecting previously unselected package gir1.2-freedesktop. Unpacking gir1.2-freedesktop (from .../gir1.2-freedesktop_1.31.0-1_i386.deb) ... Selecting previously unselected package gir1.2-gconf-2.0. Unpacking gir1.2-gconf-2.0 (from .../gir1.2-gconf-2.0_3.2.3-1ubuntu1_i386.deb) ... Selecting previously unselected package gir1.2-gdkpixbuf-2.0. Unpacking gir1.2-gdkpixbuf-2.0 (from .../gir1.2-gdkpixbuf-2.0_2.24.0-1ubuntu2_i386.deb) ... Selecting previously unselected package gir1.2-pango-1.0. Unpacking gir1.2-pango-1.0 (from .../gir1.2-pango-1.0_1.29.4-2ubuntu1_i386.deb) ... Selecting previously unselected package pkg-config. Unpacking pkg-config (from .../pkg-config_0.26-1ubuntu1_i386.deb) ... Selecting previously unselected package libglib2.0-data. Unpacking libglib2.0-data (from .../libglib2.0-data_2.30.1-2ubuntu1_i386.deb) ... Selecting previously unselected package libglib2.0-bin. Unpacking libglib2.0-bin (from .../libglib2.0-bin_2.30.1-2ubuntu1_i386.deb) ... Selecting previously unselected package zlib1g-dev. Unpacking zlib1g-dev (from .../zlib1g-dev_1%3a1.2.3.4.dfsg-3ubuntu4_i386.deb) ... Selecting previously unselected package libglib2.0-dev. Unpacking libglib2.0-dev (from .../libglib2.0-dev_2.30.1-2ubuntu1_i386.deb) ... Selecting previously unselected package libatk1.0-dev. Unpacking libatk1.0-dev (from .../libatk1.0-dev_2.2.0-2_i386.deb) ... Selecting previously unselected package libexpat1-dev. Unpacking libexpat1-dev (from .../libexpat1-dev_2.0.1-7.2_i386.deb) ... Selecting previously unselected package libfreetype6-dev. Unpacking libfreetype6-dev (from .../libfreetype6-dev_2.4.8-1_i386.deb) ... Selecting previously unselected package libfontconfig1-dev. Unpacking libfontconfig1-dev (from .../libfontconfig1-dev_2.8.0-3ubuntu2_i386.deb) ... Selecting previously unselected package xorg-sgml-doctools. Unpacking xorg-sgml-doctools (from .../xorg-sgml-doctools_1%3a1.8-2_i386.deb) ... Selecting previously unselected package x11proto-core-dev. Unpacking x11proto-core-dev (from .../x11proto-core-dev_7.0.22-1_i386.deb) ... Selecting previously unselected package libxau-dev. Unpacking libxau-dev (from .../libxau-dev_1%3a1.0.6-4_i386.deb) ... Selecting previously unselected package libxdmcp-dev. Unpacking libxdmcp-dev (from .../libxdmcp-dev_1%3a1.1.0-4_i386.deb) ... Selecting previously unselected package x11proto-input-dev. Unpacking x11proto-input-dev (from .../x11proto-input-dev_2.0.2-2ubuntu1_i386.deb) ... Selecting previously unselected package x11proto-kb-dev. Unpacking x11proto-kb-dev (from .../x11proto-kb-dev_1.0.5-2_i386.deb) ... Selecting previously unselected package xtrans-dev. Unpacking xtrans-dev (from .../xtrans-dev_1.2.6-2_i386.deb) ... Selecting previously unselected package libpthread-stubs0. Unpacking libpthread-stubs0 (from .../libpthread-stubs0_0.3-2.1ubuntu1_i386.deb) ... Selecting previously unselected package libpthread-stubs0-dev. Unpacking libpthread-stubs0-dev (from .../libpthread-stubs0-dev_0.3-2.1ubuntu1_i386.deb) ... Selecting previously unselected package libxcb1-dev. Unpacking libxcb1-dev (from .../libxcb1-dev_1.7-4_i386.deb) ... Selecting previously unselected package libx11-dev. Unpacking libx11-dev (from .../libx11-dev_2%3a1.4.4-4_i386.deb) ... Selecting previously unselected package x11proto-render-dev. Unpacking x11proto-render-dev (from .../x11proto-render-dev_2%3a0.11.1-2_i386.deb) ... Selecting previously unselected package libxrender-dev. Unpacking libxrender-dev (from .../libxrender-dev_1%3a0.9.6-2_i386.deb) ... Selecting previously unselected package libpng12-dev. Unpacking libpng12-dev (from .../libpng12-dev_1.2.46-3ubuntu1_i386.deb) ... Selecting previously unselected package libice-dev. Unpacking libice-dev (from .../libice-dev_2%3a1.0.7-2_i386.deb) ... Selecting previously unselected package libsm-dev. Unpacking libsm-dev (from .../libsm-dev_2%3a1.2.0-2_i386.deb) ... Selecting previously unselected package libpixman-1-dev. Unpacking libpixman-1-dev (from .../libpixman-1-dev_0.24.0-1_i386.deb) ... Selecting previously unselected package libxcb-render0-dev. Unpacking libxcb-render0-dev (from .../libxcb-render0-dev_1.7-4_i386.deb) ... Selecting previously unselected package libxcb-shm0-dev. Unpacking libxcb-shm0-dev (from .../libxcb-shm0-dev_1.7-4_i386.deb) ... Selecting previously unselected package libcairo2-dev. Unpacking libcairo2-dev (from .../libcairo2-dev_1.10.2-6.1ubuntu2_i386.deb) ... Selecting previously unselected package libdbus-1-dev. Unpacking libdbus-1-dev (from .../libdbus-1-dev_1.4.16-1ubuntu1_i386.deb) ... Selecting previously unselected package libgconf2-dev. Unpacking libgconf2-dev (from .../libgconf2-dev_3.2.3-1ubuntu1_i386.deb) ... Selecting previously unselected package libgdk-pixbuf2.0-dev. Unpacking libgdk-pixbuf2.0-dev (from .../libgdk-pixbuf2.0-dev_2.24.0-1ubuntu2_i386.deb) ... Selecting previously unselected package libxft-dev. Unpacking libxft-dev (from .../libxft-dev_2.2.0-3ubuntu1_i386.deb) ... Selecting previously unselected package libpango1.0-dev. Unpacking libpango1.0-dev (from .../libpango1.0-dev_1.29.4-2ubuntu1_i386.deb) ... Selecting previously unselected package x11proto-xext-dev. Unpacking x11proto-xext-dev (from .../x11proto-xext-dev_7.2.0-3_i386.deb) ... Selecting previously unselected package libxext-dev. Unpacking libxext-dev (from .../libxext-dev_2%3a1.3.0-3_i386.deb) ... Selecting previously unselected package x11proto-xinerama-dev. Unpacking x11proto-xinerama-dev (from .../x11proto-xinerama-dev_1.2.1-2_i386.deb) ... Selecting previously unselected package libxinerama-dev. Unpacking libxinerama-dev (from .../libxinerama-dev_2%3a1.1.1-3_i386.deb) ... Selecting previously unselected package libxi-dev. Unpacking libxi-dev (from .../libxi-dev_2%3a1.4.3-3ubuntu1_i386.deb) ... Selecting previously unselected package x11proto-randr-dev. Unpacking x11proto-randr-dev (from .../x11proto-randr-dev_1.4.0+git20101207.0d32bb07-0ubuntu2_i386.deb) ... Selecting previously unselected package libxrandr-dev. Unpacking libxrandr-dev (from .../libxrandr-dev_2%3a1.3.2-2_i386.deb) ... Selecting previously unselected package x11proto-fixes-dev. Unpacking x11proto-fixes-dev (from .../x11proto-fixes-dev_1%3a5.0-2_i386.deb) ... Selecting previously unselected package libxfixes-dev. Unpacking libxfixes-dev (from .../libxfixes-dev_1%3a5.0-4_i386.deb) ... Selecting previously unselected package libxcursor-dev. Unpacking libxcursor-dev (from .../libxcursor-dev_1%3a1.1.12-1_i386.deb) ... Selecting previously unselected package x11proto-composite-dev. Unpacking x11proto-composite-dev (from .../x11proto-composite-dev_1%3a0.4.2-2_i386.deb) ... Selecting previously unselected package libxcomposite-dev. Unpacking libxcomposite-dev (from .../libxcomposite-dev_1%3a0.4.3-2_i386.deb) ... Selecting previously unselected package x11proto-damage-dev. Unpacking x11proto-damage-dev (from .../x11proto-damage-dev_1%3a1.2.1-2_i386.deb) ... Selecting previously unselected package libxdamage-dev. Unpacking libxdamage-dev (from .../libxdamage-dev_1%3a1.1.3-2_i386.deb) ... Selecting previously unselected package libxml2-utils. Unpacking libxml2-utils (from .../libxml2-utils_2.7.8.dfsg-5ubuntu1_i386.deb) ... Selecting previously unselected package libgtk2.0-dev. Unpacking libgtk2.0-dev (from .../libgtk2.0-dev_2.24.8-0ubuntu4_i386.deb) ... Selecting previously unselected package libpython2.7. Unpacking libpython2.7 (from .../libpython2.7_2.7.2-8build1_i386.deb) ... Selecting previously unselected package libssl-dev. Unpacking libssl-dev (from .../libssl-dev_1.0.0e-2ubuntu4_i386.deb) ... Selecting previously unselected package python-central. Unpacking python-central (from .../python-central_0.6.17_all.deb) ... Selecting previously unselected package python2.7-dev. Unpacking python2.7-dev (from .../python2.7-dev_2.7.2-8build1_i386.deb) ... Selecting previously unselected package python-dev. Unpacking python-dev (from .../python-dev_2.7.2-9ubuntu1_all.deb) ... Selecting previously unselected package python-support. Unpacking python-support (from .../python-support_1.0.14ubuntu2_all.deb) ... Selecting previously unselected package python-empy. Unpacking python-empy (from .../python-empy_3.3-6ubuntu1_all.deb) ... Selecting previously unselected package libffi-dev. Unpacking libffi-dev (from .../libffi-dev_3.0.11~rc1-5_i386.deb) ... Selecting previously unselected package python-gi-dev. Unpacking python-gi-dev (from .../python-gi-dev_3.0.2-4_all.deb) ... Selecting previously unselected package python-gobject-2-dev. Unpacking python-gobject-2-dev (from .../python-gobject-2-dev_2.28.6-7_all.deb) ... Selecting previously unselected package python-gobject-dev. Unpacking python-gobject-dev (from .../python-gobject-dev_3.0.2-4_all.deb) ... Selecting previously unselected package python-gtk2. Unpacking python-gtk2 (from .../python-gtk2_2.24.0-2_i386.deb) ... Selecting previously unselected package python-gtk2-dev. Unpacking python-gtk2-dev (from .../python-gtk2-dev_2.24.0-2_all.deb) ... Processing triggers for libglib2.0-0 ... No schema files found: doing nothing. Setting up libdb4.8 (4.8.30-10) ... Setting up libexpat1 (2.0.1-7.2) ... Setting up libpopt0 (1.16-1ubuntu1) ... Setting up libfreetype6 (2.4.8-1) ... Setting up ucf (3.0025+nmu2ubuntu1) ... Setting up ttf-dejavu-core (2.33-2) ... Setting up fontconfig-config (2.8.0-3ubuntu2) ... Setting up libfontconfig1 (2.8.0-3ubuntu2) ... Setting up libpixman-1-0 (0.24.0-1) ... Setting up libxau6 (1:1.0.6-4) ... Setting up libxdmcp6 (1:1.1.0-4) ... Setting up libxcb1 (1.7-4) ... Setting up libx11-data (2:1.4.4-4) ... Setting up libx11-6 (2:1.4.4-4) ... Setting up libxcb-render0 (1.7-4) ... Setting up libxcb-shm0 (1.7-4) ... Setting up libxrender1 (1:0.9.6-2) ... Setting up libcairo2 (1.10.2-6.1ubuntu2) ... Setting up libdbus-glib-1-2 (0.98-1ubuntu1) ... Setting up libpipeline1 (1.2.0-5) ... Setting up libxext6 (2:1.3.0-3) ... Setting up libxml2 (2.7.8.dfsg-5ubuntu1) ... Setting up libatk1.0-data (2.2.0-2) ... Setting up libatk1.0-0 (2.2.0-2) ... Setting up libavahi-common-data (0.6.30-5ubuntu1) ... Setting up libavahi-common3 (0.6.30-5ubuntu1) ... Setting up libavahi-client3 (0.6.30-5ubuntu1) ... Setting up libcairo-gobject2 (1.10.2-6.1ubuntu2) ... Setting up libcairo-script-interpreter2 (1.10.2-6.1ubuntu2) ... Setting up libcroco3 (0.6.2-2) ... Setting up libcups2 (1.5.0-13build1) ... Setting up libdatrie1 (0.2.5-2) ... Setting up libjpeg8 (8c-2ubuntu4) ... Setting up libjasper1 (1.900.1-11) ... Setting up libtiff4 (3.9.5-2) ... Setting up libgdk-pixbuf2.0-0 (2.24.0-1ubuntu2) ... Setting up libunistring0 (0.9.3-5) ... Setting up libgettextpo0 (0.18.1.1-5ubuntu3) ... Setting up libgtk2.0-common (2.24.8-0ubuntu4) ... Setting up libthai-data (0.1.16-2) ... Setting up libthai0 (0.1.16-2) ... Setting up libxft2 (2.2.0-3ubuntu1) ... Setting up fontconfig (2.8.0-3ubuntu2) ... Cleaning up old fontconfig caches... done. Regenerating fonts cache... done. Setting up libpango1.0-0 (1.29.4-2ubuntu1) ... Setting up libxcomposite1 (1:0.4.3-2) ... Setting up libxfixes3 (1:5.0-4) ... Setting up libxcursor1 (1:1.1.12-1) ... Setting up libxdamage1 (1:1.1.3-2) ... Setting up libxi6 (2:1.4.3-3ubuntu1) ... Setting up libxinerama1 (2:1.1.1-3) ... Setting up libxrandr2 (2:1.3.2-2) ... Setting up shared-mime-info (0.91-0ubuntu1) ... Setting up libgtk2.0-0 (2.24.8-0ubuntu4) ... Cannot load module /usr/lib/gtk-2.0/2.10.0/immodules/*.so: /usr/lib/gtk-2.0/2.10.0/immodules/*.so: cannot open shared object file: No such file or directory /usr/lib/gtk-2.0/2.10.0/immodules/*.so does not export GTK+ IM module API: /usr/lib/gtk-2.0/2.10.0/immodules/*.so: cannot open shared object file: No such file or directory Setting up x11-common (1:7.6+7ubuntu7) ... invoke-rc.d: policy-rc.d denied execution of start. Setting up libice6 (2:1.0.7-2) ... Setting up libsm6 (2:1.2.0-2) ... Setting up libmagic1 (5.09-2) ... Setting up file (5.09-2) ... 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.2-8build1) ... Setting up python (2.7.2-9ubuntu1) ... Setting up bsdmainutils (8.2.3) ... 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 dbus (1.4.16-1ubuntu1) ... invoke-rc.d: policy-rc.d denied execution of start. Setting up gettext-base (0.18.1.1-5ubuntu3) ... Setting up libgirepository-1.0-1 (1.31.0-1) ... Setting up gir1.2-glib-2.0 (1.31.0-1) ... Setting up groff-base (1.21-6) ... Setting up man-db (2.6.0.2-3) ... Building database of manual pages ... Setting up psmisc (22.14-1) ... Setting up python-cairo (1.8.8-1ubuntu2) ... Setting up python-gi (3.0.2-4) ... Setting up python-gobject-2 (2.28.6-7) ... Setting up python-gobject (3.0.2-4) ... Setting up m4 (1.4.16-2ubuntu1) ... Setting up autoconf (2.68-1ubuntu2) ... Setting up autotools-dev (20110511.1) ... Setting up automake (1:1.11.1-1ubuntu2) ... update-alternatives: using /usr/bin/automake-1.11 to provide /usr/bin/automake (automake) in auto mode. Setting up html2text (1.3.2a-15) ... Setting up gettext (0.18.1.1-5ubuntu3) ... Setting up intltool-debian (0.35.0+20060710.1) ... Setting up po-debconf (1.0.16+nmu1ubuntu1) ... Setting up debhelper (8.9.9ubuntu1) ... Setting up liburi-perl (1.59-1) ... Setting up libencode-locale-perl (1.02-2) ... Setting up libhttp-date-perl (6.00-1) ... Setting up libfile-listing-perl (6.03-1) ... Setting up libhtml-tagset-perl (3.20-2) ... Setting up libhtml-parser-perl (3.69-1build1) ... Setting up libhtml-tree-perl (4.2-1) ... Setting up liblwp-mediatypes-perl (6.01-1) ... Setting up libhttp-message-perl (6.01-1) ... Setting up libhttp-cookies-perl (6.00-2) ... Setting up libhttp-negotiate-perl (6.00-2) ... Setting up libnet-http-perl (6.01-1) ... Setting up libnet-ssleay-perl (1.42-1build1) ... Setting up libio-socket-ssl-perl (1.49-1) ... Setting up libwww-robotrules-perl (6.01-1) ... Setting up python-scour (0.26-2) ... Setting up dbus-x11 (1.4.16-1ubuntu1) ... Setting up devscripts (2.11.1ubuntu5) ... Setting up dh-buildinfo (0.9) ... Setting up gconf2-common (3.2.3-1ubuntu1) ... Creating config file /etc/gconf/2/path with new version Setting up libgconf2-4 (3.2.3-1ubuntu1) ... Setting up gconf2 (3.2.3-1ubuntu1) ... update-alternatives: using /usr/bin/gconftool-2 to provide /usr/bin/gconftool (gconftool) in auto mode. Setting up gir1.2-atk-1.0 (2.2.0-2) ... Setting up gir1.2-freedesktop (1.31.0-1) ... Setting up gir1.2-gconf-2.0 (3.2.3-1ubuntu1) ... Setting up gir1.2-gdkpixbuf-2.0 (2.24.0-1ubuntu2) ... Setting up gir1.2-pango-1.0 (1.29.4-2ubuntu1) ... Setting up pkg-config (0.26-1ubuntu1) ... Setting up libglib2.0-data (2.30.1-2ubuntu1) ... Setting up libglib2.0-bin (2.30.1-2ubuntu1) ... Setting up zlib1g-dev (1:1.2.3.4.dfsg-3ubuntu4) ... Setting up libglib2.0-dev (2.30.1-2ubuntu1) ... Setting up libatk1.0-dev (2.2.0-2) ... Setting up libexpat1-dev (2.0.1-7.2) ... Setting up libfreetype6-dev (2.4.8-1) ... Setting up libfontconfig1-dev (2.8.0-3ubuntu2) ... Setting up xorg-sgml-doctools (1:1.8-2) ... Setting up x11proto-core-dev (7.0.22-1) ... Setting up libxau-dev (1:1.0.6-4) ... Setting up libxdmcp-dev (1:1.1.0-4) ... Setting up x11proto-input-dev (2.0.2-2ubuntu1) ... Setting up x11proto-kb-dev (1.0.5-2) ... Setting up xtrans-dev (1.2.6-2) ... Setting up libpthread-stubs0 (0.3-2.1ubuntu1) ... Setting up libpthread-stubs0-dev (0.3-2.1ubuntu1) ... Setting up libxcb1-dev (1.7-4) ... Setting up libx11-dev (2:1.4.4-4) ... Setting up x11proto-render-dev (2:0.11.1-2) ... Setting up libxrender-dev (1:0.9.6-2) ... Setting up libpng12-dev (1.2.46-3ubuntu1) ... Setting up libice-dev (2:1.0.7-2) ... Setting up libsm-dev (2:1.2.0-2) ... Setting up libpixman-1-dev (0.24.0-1) ... Setting up libxcb-render0-dev (1.7-4) ... Setting up libxcb-shm0-dev (1.7-4) ... Setting up libcairo2-dev (1.10.2-6.1ubuntu2) ... Setting up libdbus-1-dev (1.4.16-1ubuntu1) ... Setting up libgconf2-dev (3.2.3-1ubuntu1) ... Setting up libgdk-pixbuf2.0-dev (2.24.0-1ubuntu2) ... Setting up libxft-dev (2.2.0-3ubuntu1) ... Setting up libpango1.0-dev (1.29.4-2ubuntu1) ... Setting up x11proto-xext-dev (7.2.0-3) ... Setting up libxext-dev (2:1.3.0-3) ... Setting up x11proto-xinerama-dev (1.2.1-2) ... Setting up libxinerama-dev (2:1.1.1-3) ... Setting up libxi-dev (2:1.4.3-3ubuntu1) ... Setting up x11proto-randr-dev (1.4.0+git20101207.0d32bb07-0ubuntu2) ... Setting up libxrandr-dev (2:1.3.2-2) ... Setting up x11proto-fixes-dev (1:5.0-2) ... Setting up libxfixes-dev (1:5.0-4) ... Setting up libxcursor-dev (1:1.1.12-1) ... Setting up x11proto-composite-dev (1:0.4.2-2) ... Setting up libxcomposite-dev (1:0.4.3-2) ... Setting up x11proto-damage-dev (1:1.2.1-2) ... Setting up libxdamage-dev (1:1.1.3-2) ... Setting up libxml2-utils (2.7.8.dfsg-5ubuntu1) ... Setting up libgtk2.0-dev (2.24.8-0ubuntu4) ... Setting up libpython2.7 (2.7.2-8build1) ... Setting up libssl-dev (1.0.0e-2ubuntu4) ... Setting up python-central (0.6.17) ... Setting up python2.7-dev (2.7.2-8build1) ... Setting up python-dev (2.7.2-9ubuntu1) ... Setting up python-support (1.0.14ubuntu2) ... Setting up python-empy (3.3-6ubuntu1) ... Setting up libffi-dev (3.0.11~rc1-5) ... Setting up python-gi-dev (3.0.2-4) ... Setting up python-gobject-2-dev (2.28.6-7) ... Setting up python-gobject-dev (3.0.2-4) ... Setting up python-gtk2 (2.24.0-2) ... Setting up python-gtk2-dev (2.24.0-2) ... Setting up liblwp-protocol-https-perl (6.02-1) ... Setting up libwww-perl (6.03-1) ... Setting up libxml-parser-perl (2.41-1build1) ... Setting up intltool (0.41.1-3) ... Setting up dh-translations (109) ... Setting up cdbs (0.4.99ubuntu1) ... Processing triggers for libc-bin ... ldconfig deferred processing now taking place Processing triggers for python-support ... Checking correctness of source dependencies... Toolchain package versions: libc6-dev_2.13-20ubuntu9 make_3.81-8.1ubuntu1 dpkg-dev_1.16.1.2ubuntu3 gcc-4.6_4.6.2-5ubuntu1 g++-4.6_4.6.2-5ubuntu1 binutils_2.22-1ubuntu1 libstdc++6-4.6-dev_4.6.2-5ubuntu1 libstdc++6_4.6.2-5ubuntu1 ------------------------------------------------------------------------------ dpkg-source: warning: -sn is not a valid option for Dpkg::Source::Package::V3::quilt gpgv: Signature made Mon Dec 5 08:32:36 2011 UTC using DSA key ID AA97FD59 gpgv: Can't check signature: public key not found dpkg-source: warning: failed to verify signature on ./sugar-0.88_0.88.1-5ubuntu1.dsc dpkg-source: info: extracting sugar-0.88 in sugar-0.88-0.88.1 dpkg-source: info: unpacking sugar-0.88_0.88.1.orig.tar.bz2 dpkg-source: info: unpacking sugar-0.88_0.88.1-5ubuntu1.debian.tar.gz dpkg-source: info: applying empy_from_system.patch dpkg-source: info: applying empy_from_system_autotools.patch dpkg-source: info: applying gconf_settings_mouse_bug.patch dpkg-source: info: applying display_sugar_instead_of_zephyr.patch dpkg-buildpackage: export CFLAGS from dpkg-buildflags (origin: vendor): -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security dpkg-buildpackage: export CPPFLAGS from dpkg-buildflags (origin: vendor): -D_FORTIFY_SOURCE=2 dpkg-buildpackage: export CXXFLAGS from dpkg-buildflags (origin: vendor): -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security dpkg-buildpackage: export FFLAGS from dpkg-buildflags (origin: vendor): -g -O2 dpkg-buildpackage: export LDFLAGS from dpkg-buildflags (origin: vendor): -Wl,-Bsymbolic-functions -Wl,-z,relro dpkg-buildpackage: source package sugar-0.88 dpkg-buildpackage: source version 0.88.1-5ubuntu1 dpkg-source --before-build sugar-0.88-0.88.1 dpkg-buildpackage: host architecture i386 /usr/bin/fakeroot debian/rules clean test -x debian/rules dh_testroot rmdir build rmdir: failed to remove `build': No such file or directory make: [cleanbuilddir] Error 1 (ignored) rm -f debian/stamp-makefile-build debian/stamp-makefile-install /usr/bin/make -C build -k distclean make: *** build: No such file or directory. Stop. make: [makefile-clean] Error 2 (ignored) rm -f debian/stamp-autotools rmdir --ignore-fail-on-non-empty build rmdir: failed to remove `build': No such file or directory make: [makefile-clean] Error 1 (ignored) rm -f debian/cdbs-install-list debian/cdbs-package-list debian/stamp-copyright-check rm -f debian/stamp-autotools-files dh_clean rm -f debian/python-jarabe-0.88.install debian/sugar-emulator-0.88.install debian/sugar-emulator-0.88.menu debian/sugar-session-0.88.install debian/sugar-session-0.88.menu debian/sugar-tools-0.88.install debian/rules build test -x debian/rules mkdir -p "build" /usr/share/cdbs/1/rules/buildcore.mk:109: WARNING: DEB_PYTHON_PRIVATE_MODULES_DIRS is a deprecated variable Scanning upstream source for new/changed copyright notices... licensecheck -c '.*' -r --copyright -i '^debian/(changelog|copyright(|_hints|_newhints))' -l '99999' * | /usr/lib/cdbs/licensecheck2dep5 > debian/copyright_newhints 61 combinations of copyright and licensing found. WARNING: The following (and possibly more) new or changed notices discovered: Format: http://svn.debian.org/wsvn/dep/web/deps/dep5.mdwn?… Upstream-Name: FIXME Upstream-Contact: FIXME Source: FIXME Disclaimer: Autogenerated by CDBS Files: AUTHORS Makefile.am README bin/Makefile.am bin/sugar-emulator bin/sugar-install-bundle bin/sugar.in configure.ac data/Makefile.am data/activities.defaults data/gtkrc.em data/icons/Makefile.am data/icons/module-about_me.svg data/icons/module-about_my_computer.svg data/icons/module-date_and_time.svg data/icons/module-frame.svg data/icons/module-keyboard.svg data/icons/module-language.svg data/icons/module-modemconfiguration.svg data/icons/module-network.svg data/icons/module-power.svg data/icons/module-updater.svg data/kbdconfig data/mime.defaults data/nm-user-settings.conf data/sugar-100.gtkrc data/sugar-72.gtkrc data/sugar-emulator.desktop.in data/sugar-xo.svg data/sugar.desktop data/sugar.schemas.in data/sugar.xml.in debian/README.source debian/compat debian/control debian/control.in debian/gbp.conf debian/patches/danish_l10n_autotools.patch debian/patches/display_sugar_instead_of_zephyr.patch debian/patches/empy_from_system.patch debian/patches/empy_from_system_autotools.patch debian/patches/fix_tz_config_path.patch debian/patches/gconf_settings_mouse_bug.patch debian/patches/series debian/pycompat debian/python-jarabe-__VER__.install.in debian/source/format debian/sugar-emulator-__VER__.install.in debian/sugar-emulator-__VER__.menu.in debian/sugar-emulator.desktop debian/sugar-session-__VER__.install.in debian/sugar-session-__VER__.menu.in debian/sugar-tools-__VER__.install.in debian/sugar.desktop debian/watch extensions/Makefile.am extensions/cpsection/Makefile.am extensions/cpsection/aboutcomputer/Makefile.am extensions/cpsection/aboutme/Makefile.am extensions/cpsection/datetime/Makefile.am extensions/cpsection/frame/Makefile.am extensions/cpsection/keyboard/Makefile.am extensions/cpsection/language/Makefile.am extensions/cpsection/modemconfiguration/Makefile.am extensions/cpsection/network/Makefile.am extensions/cpsection/power/Makefile.am extensions/cpsection/updater/Makefile.am extensions/cpsection/updater/backends/Makefile.am extensions/deviceicon/Makefile.am extensions/globalkey/Makefile.am intltool-extract.in intltool-merge.in intltool-update.in po/POTFILES.in po/POTFILES.skip po/pl.po src/Makefile.am src/jarabe/Makefile.am src/jarabe/controlpanel/Makefile.am src/jarabe/desktop/Makefile.am src/jarabe/frame/Makefile.am src/jarabe/intro/Makefile.am src/jarabe/intro/__init__.py src/jarabe/intro/default-picture.png src/jarabe/journal/Makefile.am src/jarabe/model/Makefile.am src/jarabe/util/Makefile.am src/jarabe/util/telepathy/Makefile.am src/jarabe/view/Makefile.am Files: po/af.po po/am.po po/ay.po po/bg.po po/bn.po po/bn_IN.po po/da.po po/dz.po po/el.po po/en.po po/ff.po po/gu.po po/ha.po po/hi.po po/ht.po po/is.po po/km.po po/ko.po po/kos.po po/mg.po po/mk.po po/ml.po po/mn.po po/mr.po po/mvo.po po/nb.po po/pa.po po/pap.po po/pis.po po/ps.po po/pt_BR.po po/qu.po po/ro.po po/ru.po po/rw.po po/sd.po po/sq.po po/sw.po po/te.po po/th.po po/tpi.po po/tvl.po po/tzo.po po/ur.po po/yo.po po/zh_CN.po Files: bin/sugar-activity bin/sugar-control-panel bin/sugar-launch bin/sugar-ui-check extensions/cpsection/network/__init__.py extensions/deviceicon/battery.py src/jarabe/__init__.py src/jarabe/config.py.in src/jarabe/controlpanel/__init__.py src/jarabe/desktop/__init__.py src/jarabe/desktop/friendview.py src/jarabe/desktop/groupbox.py src/jarabe/desktop/homewindow.py src/jarabe/desktop/myicon.py src/jarabe/desktop/snowflakelayout.py src/jarabe/desktop/spreadlayout.py src/jarabe/desktop/transitionbox.py src/jarabe/frame/__init__.py src/jarabe/frame/clipboard.py src/jarabe/frame/eventarea.py src/jarabe/frame/frame.py src/jarabe/frame/framewindow.py src/jarabe/frame/friendstray.py src/jarabe/intro/colorpicker.py src/jarabe/intro/window.py src/jarabe/journal/keepicon.py src/jarabe/model/__init__.py src/jarabe/model/buddy.py src/jarabe/model/friends.py src/jarabe/model/invites.py src/jarabe/model/neighborhood.py src/jarabe/model/screen.py src/jarabe/model/session.py src/jarabe/model/sound.py src/jarabe/util/emulator.py src/jarabe/view/__init__.py src/jarabe/view/buddyicon.py src/jarabe/view/buddymenu.py src/jarabe/view/launcher.py src/jarabe/view/service.py 2006-2007, Red Hat, Inc 2006-2008, Red Hat, Inc 2007, Red Hat, Inc 2008, Red Hat, Inc Files: extensions/cpsection/aboutcomputer/model.py extensions/cpsection/aboutme/model.py extensions/cpsection/datetime/model.py extensions/cpsection/frame/model.py extensions/cpsection/language/model.py extensions/cpsection/network/model.py extensions/cpsection/power/model.py extensions/deviceicon/volume.py src/jarabe/controlpanel/cmd.py src/jarabe/controlpanel/gui.py src/jarabe/controlpanel/toolbar.py src/jarabe/desktop/favoriteslayout.py src/jarabe/desktop/homebox.py src/jarabe/desktop/schoolserver.py src/jarabe/frame/clipboardmenu.py To fix the situation please do the following: 1) Fully compare debian/copyright_hints with debian/copyright_newhints 2) Update debian/copyright as needed 3) Replace debian/copyright_hints with debian/copyright_newhints touch debian/stamp-copyright-check sed 's/__VER__/0.88/' debian/python-jarabe-0.88.install sed 's/__VER__/0.88/' debian/sugar-emulator-0.88.install sed 's/__VER__/0.88/' debian/sugar-emulator-0.88.menu sed 's/__VER__/0.88/' debian/sugar-session-0.88.install sed 's/__VER__/0.88/' debian/sugar-session-0.88.menu sed 's/__VER__/0.88/' debian/sugar-tools-0.88.install touch debian/stamp-autotools-files chmod a+x /build/buildd/sugar-0.88-0.88.1/./configure mkdir -p build cd build && CFLAGS="-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -Wall" CXXFLAGS="-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -Wall" CPPFLAGS="-D_FORTIFY_SOURCE=2" LDFLAGS="-Wl,-Bsymbolic-functions -Wl,-z,relro" PYTHON="python" /build/buildd/sugar-0.88-0.88.1/./configure --build=i686-linux-gnu --prefix=/usr --includedir="\${prefix}/include" --mandir="\${prefix}/share/man" --infodir="\${prefix}/share/info" --sysconfdir=/etc --localstatedir=/var --libexecdir="\${prefix}/lib/sugar-0.88" --disable-maintainer-mode --disable-dependency-tracking --disable-silent-rules configure: WARNING: unrecognized options: --disable-silent-rules 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 whether to enable maintainer-specific portions of Makefiles... no checking for python version... 2.7 checking for python platform... linux2 checking for python script directory... ${prefix}/lib/python2.7/dist-packages checking for python extension module directory... ${exec_prefix}/lib/python2.7/dist-packages checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for SHELL... yes checking whether NLS is requested... yes checking for style of include used by make... GNU checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking dependency style of gcc... none checking for intltool >= 0.33... 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.14.2 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... af am ar ay bg bi bn_IN bn ca cpp cs da de dz el en es fa_AF fa ff fil fr gu ha he hi ht hu id ig is it ja km ko kos mg mi mk ml mn mr ms mvo nb ne nl pa pap pis pl ps pt_BR pt qu ro ru rw sd si sk sl sq sv sw ta te th tpi tr tvl tzo ug ur vi wa yo zh_CN zh_TW 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 configure: creating ./config.status config.status: creating bin/Makefile config.status: creating bin/sugar config.status: creating data/icons/Makefile config.status: creating data/Makefile config.status: creating data/sugar-emulator.desktop config.status: creating extensions/cpsection/aboutcomputer/Makefile config.status: creating extensions/cpsection/aboutme/Makefile config.status: creating extensions/cpsection/datetime/Makefile config.status: creating extensions/cpsection/frame/Makefile config.status: creating extensions/cpsection/keyboard/Makefile config.status: creating extensions/cpsection/language/Makefile config.status: creating extensions/cpsection/modemconfiguration/Makefile config.status: creating extensions/cpsection/Makefile config.status: creating extensions/cpsection/network/Makefile config.status: creating extensions/cpsection/power/Makefile config.status: creating extensions/cpsection/updater/backends/Makefile config.status: creating extensions/cpsection/updater/Makefile config.status: creating extensions/deviceicon/Makefile config.status: creating extensions/globalkey/Makefile config.status: creating extensions/Makefile config.status: creating Makefile config.status: creating po/Makefile.in config.status: creating src/jarabe/config.py config.status: creating src/jarabe/controlpanel/Makefile config.status: creating src/jarabe/desktop/Makefile config.status: creating src/jarabe/frame/Makefile config.status: creating src/jarabe/intro/Makefile config.status: creating src/jarabe/journal/Makefile config.status: creating src/jarabe/Makefile config.status: creating src/jarabe/model/Makefile config.status: creating src/jarabe/util/Makefile config.status: creating src/jarabe/util/telepathy/Makefile config.status: creating src/jarabe/view/Makefile config.status: creating src/Makefile config.status: executing depfiles commands config.status: executing default-1 commands config.status: executing po/stamp-it commands configure: WARNING: unrecognized options: --disable-silent-rules touch debian/stamp-autotools /usr/bin/make -C build make[1]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build' Making all in bin make[2]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/bin' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/bin' Making all in data make[2]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/data' Making all in icons make[3]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/data/icons' make[3]: Nothing to be done for `all'. make[3]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/data/icons' make[3]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/data' LC_ALL=C /usr/bin/intltool-merge -x -u -c ../po/.intltool-merge-cache /build/buildd/sugar-0.88-0.88.1/./po /build/buildd/sugar-0.88-0.88.1/./data/sugar.xml.in sugar.xml Generating and caching the translation database Merging translations into sugar.xml. CREATED sugar.xml LC_ALL=C /usr/bin/intltool-merge -s -u -c ../po/.intltool-merge-cache /build/buildd/sugar-0.88-0.88.1/./po /build/buildd/sugar-0.88-0.88.1/./data/sugar.schemas.in sugar.schemas Found cached translation database Merging translations into sugar.schemas. make[3]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/data' make[2]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/data' Making all in po make[2]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/po' file=`echo af | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/af.po file=`echo am | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/am.po file=`echo ar | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/ar.po file=`echo ay | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/ay.po file=`echo bg | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/bg.po file=`echo bi | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/bi.po file=`echo bn_IN | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/bn_IN.po file=`echo bn | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/bn.po file=`echo ca | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/ca.po file=`echo cpp | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/cpp.po file=`echo cs | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/cs.po file=`echo da | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/da.po file=`echo de | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/de.po file=`echo dz | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/dz.po file=`echo el | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/el.po file=`echo en | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/en.po file=`echo es | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/es.po file=`echo fa_AF | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/fa_AF.po file=`echo fa | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/fa.po file=`echo ff | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/ff.po file=`echo fil | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/fil.po file=`echo fr | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/fr.po file=`echo gu | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/gu.po file=`echo ha | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/ha.po file=`echo he | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/he.po file=`echo hi | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/hi.po file=`echo ht | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/ht.po file=`echo hu | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/hu.po file=`echo id | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/id.po file=`echo ig | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/ig.po file=`echo is | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/is.po file=`echo it | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/it.po file=`echo ja | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/ja.po file=`echo km | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/km.po file=`echo ko | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/ko.po file=`echo kos | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/kos.po file=`echo mg | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/mg.po file=`echo mi | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/mi.po file=`echo mk | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/mk.po file=`echo ml | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/ml.po file=`echo mn | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/mn.po file=`echo mr | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/mr.po file=`echo ms | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/ms.po file=`echo mvo | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/mvo.po file=`echo nb | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/nb.po file=`echo ne | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/ne.po file=`echo nl | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/nl.po file=`echo pa | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/pa.po file=`echo pap | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/pap.po file=`echo pis | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/pis.po file=`echo pl | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/pl.po file=`echo ps | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/ps.po file=`echo pt_BR | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/pt_BR.po file=`echo pt | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/pt.po file=`echo qu | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/qu.po file=`echo ro | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/ro.po file=`echo ru | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/ru.po file=`echo rw | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/rw.po file=`echo sd | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/sd.po file=`echo si | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/si.po file=`echo sk | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/sk.po file=`echo sl | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/sl.po file=`echo sq | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/sq.po file=`echo sv | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/sv.po file=`echo sw | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/sw.po file=`echo ta | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/ta.po file=`echo te | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/te.po file=`echo th | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/th.po file=`echo tpi | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/tpi.po file=`echo tr | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/tr.po file=`echo tvl | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/tvl.po file=`echo tzo | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/tzo.po file=`echo ug | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/ug.po file=`echo ur | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/ur.po file=`echo vi | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/vi.po file=`echo wa | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/wa.po file=`echo yo | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/yo.po file=`echo zh_CN | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/zh_CN.po file=`echo zh_TW | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/sugar-0.88-0.88.1/./po/zh_TW.po make[2]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/po' Making all in src make[2]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/src' Making all in jarabe make[3]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe' Making all in controlpanel make[4]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe/controlpanel' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe/controlpanel' Making all in desktop make[4]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe/desktop' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe/desktop' Making all in frame make[4]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe/frame' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe/frame' Making all in journal make[4]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe/journal' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe/journal' Making all in model make[4]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe/model' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe/model' Making all in view make[4]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe/view' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe/view' Making all in intro make[4]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe/intro' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe/intro' Making all in util make[4]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe/util' Making all in telepathy make[5]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe/util/telepathy' make[5]: Nothing to be done for `all'. make[5]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe/util/telepathy' make[5]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe/util' make[5]: Nothing to be done for `all-am'. make[5]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe/util' make[4]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe/util' make[4]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe' make[4]: Nothing to be done for `all-am'. make[4]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe' make[3]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe' make[3]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/src' make[3]: Nothing to be done for `all-am'. make[3]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/src' make[2]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/src' Making all in extensions make[2]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/extensions' Making all in cpsection make[3]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection' Making all in aboutme make[4]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/aboutme' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/aboutme' Making all in aboutcomputer make[4]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/aboutcomputer' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/aboutcomputer' Making all in datetime make[4]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/datetime' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/datetime' Making all in frame make[4]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/frame' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/frame' Making all in keyboard make[4]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/keyboard' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/keyboard' Making all in language make[4]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/language' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/language' Making all in modemconfiguration make[4]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/modemconfiguration' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/modemconfiguration' Making all in network make[4]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/network' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/network' Making all in power make[4]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/power' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/power' Making all in updater make[4]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/updater' Making all in backends make[5]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/updater/backends' make[5]: Nothing to be done for `all'. make[5]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/updater/backends' make[5]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/updater' make[5]: Nothing to be done for `all-am'. make[5]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/updater' make[4]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/updater' make[4]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection' make[4]: Nothing to be done for `all-am'. make[4]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection' make[3]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection' Making all in deviceicon make[3]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/deviceicon' make[3]: Nothing to be done for `all'. make[3]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/deviceicon' Making all in globalkey make[3]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/globalkey' make[3]: Nothing to be done for `all'. make[3]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/globalkey' make[3]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/extensions' make[3]: Nothing to be done for `all-am'. make[3]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/extensions' make[2]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/extensions' make[2]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build' make[2]: Nothing to be done for `all-am'. make[2]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build' make[1]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build' touch debian/stamp-makefile-build DEB_MAKE_CHECK_TARGET unset, not running checks /usr/bin/fakeroot debian/rules binary test -x debian/rules dh_testroot dh_clean -k dh_clean: dh_clean -k is deprecated; use dh_prep instead dh_installdirs -A mkdir -p "build" /usr/share/cdbs/1/rules/buildcore.mk:109: WARNING: DEB_PYTHON_PRIVATE_MODULES_DIRS is a deprecated variable DEB_MAKE_CHECK_TARGET unset, not running checks /usr/bin/make -C build install DESTDIR=/build/buildd/sugar-0.88-0.88.1/debian/tmp/ make[1]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build' Making install in bin make[2]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/bin' make[3]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/bin' test -z "/usr/bin" || /bin/mkdir -p "/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/bin" /usr/bin/install -c sugar /build/buildd/sugar-0.88-0.88.1/./bin/sugar-activity /build/buildd/sugar-0.88-0.88.1/./bin/sugar-control-panel /build/buildd/sugar-0.88-0.88.1/./bin/sugar-emulator /build/buildd/sugar-0.88-0.88.1/./bin/sugar-install-bundle /build/buildd/sugar-0.88-0.88.1/./bin/sugar-launch /build/buildd/sugar-0.88-0.88.1/./bin/sugar-session /build/buildd/sugar-0.88-0.88.1/./bin/sugar-ui-check '/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/bin' make[3]: Nothing to be done for `install-data-am'. make[3]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/bin' make[2]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/bin' Making install in data make[2]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/data' Making install in icons make[3]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/data/icons' make[4]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/data/icons' make[4]: Nothing to be done for `install-exec-am'. test -z "/usr/share/sugar/data/icons" || /bin/mkdir -p "/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/sugar/data/icons" /usr/bin/install -c -m 644 /build/buildd/sugar-0.88-0.88.1/./data/icons/module-about_me.svg /build/buildd/sugar-0.88-0.88.1/./data/icons/module-about_my_computer.svg /build/buildd/sugar-0.88-0.88.1/./data/icons/module-date_and_time.svg /build/buildd/sugar-0.88-0.88.1/./data/icons/module-frame.svg /build/buildd/sugar-0.88-0.88.1/./data/icons/module-keyboard.svg /build/buildd/sugar-0.88-0.88.1/./data/icons/module-language.svg /build/buildd/sugar-0.88-0.88.1/./data/icons/module-modemconfiguration.svg /build/buildd/sugar-0.88-0.88.1/./data/icons/module-network.svg /build/buildd/sugar-0.88-0.88.1/./data/icons/module-power.svg /build/buildd/sugar-0.88-0.88.1/./data/icons/module-updater.svg '/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/sugar/data/icons' make[4]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/data/icons' make[3]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/data/icons' make[3]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/data' make[4]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/data' make[4]: Nothing to be done for `install-exec-am'. test -z "/usr/share/applications" || /bin/mkdir -p "/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/applications" /usr/bin/install -c -m 644 sugar-emulator.desktop '/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/applications' GCONF_CONFIG_SOURCE=xml:merged:/etc/gconf/gconf.xml.defaults /usr/bin/gconftool-2 --makefile-install-rule sugar.schemas 2>&1 > /dev/null (gconftool-2:13250): GConf-WARNING **: None of the resolved addresses are writable; saving configuration settings will not be possible WARNING: failed to install schema `/schemas/desktop/sugar/user/nick', locale `de': Unable to store a value at key '/schemas/desktop/sugar/user/nick', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/user/nick', locale `sl': Unable to store a value at key '/schemas/desktop/sugar/user/nick', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/user/nick', locale `ar': Unable to store a value at key '/schemas/desktop/sugar/user/nick', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/user/nick', locale `ja': Unable to store a value at key '/schemas/desktop/sugar/user/nick', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/user/nick', locale `C': Unable to store a value at key '/schemas/desktop/sugar/user/nick', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/user/nick', locale `vi': Unable to store a value at key '/schemas/desktop/sugar/user/nick', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/user/nick', locale `pt': Unable to store a value at key '/schemas/desktop/sugar/user/nick', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/user/nick', locale `hi': Unable to store a value at key '/schemas/desktop/sugar/user/nick', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/user/nick', locale `es': Unable to store a value at key '/schemas/desktop/sugar/user/nick', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/user/nick', locale `fr': Unable to store a value at key '/schemas/desktop/sugar/user/nick', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/user/nick', locale `sv': Unable to store a value at key '/schemas/desktop/sugar/user/nick', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/user/nick', locale `mg': Unable to store a value at key '/schemas/desktop/sugar/user/nick', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/user/nick', locale `ne': Unable to store a value at key '/schemas/desktop/sugar/user/nick', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/user/nick', locale `zh_TW': Unable to store a value at key '/schemas/desktop/sugar/user/nick', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/user/nick', locale `it': Unable to store a value at key '/schemas/desktop/sugar/user/nick', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/user/nick', locale `mn': Unable to store a value at key '/schemas/desktop/sugar/user/nick', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/user/nick', locale `nl': Unable to store a value at key '/schemas/desktop/sugar/user/nick', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/user/nick', locale `ta': Unable to store a value at key '/schemas/desktop/sugar/user/nick', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/user/default_nick', locale `C': Unable to store a value at key '/schemas/desktop/sugar/user/default_nick', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/user/default_nick', locale `vi': Unable to store a value at key '/schemas/desktop/sugar/user/default_nick', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/user/default_nick', locale `ar': Unable to store a value at key '/schemas/desktop/sugar/user/default_nick', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/user/default_nick', locale `it': Unable to store a value at key '/schemas/desktop/sugar/user/default_nick', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/user/default_nick', locale `de': Unable to store a value at key '/schemas/desktop/sugar/user/default_nick', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/user/default_nick', locale `ja': Unable to store a value at key '/schemas/desktop/sugar/user/default_nick', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/user/default_nick', locale `zh_TW': Unable to store a value at key '/schemas/desktop/sugar/user/default_nick', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/user/color', locale `de': Unable to store a value at key '/schemas/desktop/sugar/user/color', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/user/color', locale `sl': Unable to store a value at key '/schemas/desktop/sugar/user/color', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/user/color', locale `ar': Unable to store a value at key '/schemas/desktop/sugar/user/color', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/user/color', locale `ja': Unable to store a value at key '/schemas/desktop/sugar/user/color', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/user/color', locale `C': Unable to store a value at key '/schemas/desktop/sugar/user/color', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/user/color', locale `vi': Unable to store a value at key '/schemas/desktop/sugar/user/color', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/user/color', locale `pt': Unable to store a value at key '/schemas/desktop/sugar/user/color', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/user/color', locale `hi': Unable to store a value at key '/schemas/desktop/sugar/user/color', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/user/color', locale `es': Unable to store a value at key '/schemas/desktop/sugar/user/color', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/user/color', locale `fr': Unable to store a value at key '/schemas/desktop/sugar/user/color', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/user/color', locale `sv': Unable to store a value at key '/schemas/desktop/sugar/user/color', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/user/color', locale `mg': Unable to store a value at key '/schemas/desktop/sugar/user/color', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/user/color', locale `ne': Unable to store a value at key '/schemas/desktop/sugar/user/color', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/user/color', locale `zh_TW': Unable to store a value at key '/schemas/desktop/sugar/user/color', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/user/color', locale `it': Unable to store a value at key '/schemas/desktop/sugar/user/color', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/user/color', locale `mn': Unable to store a value at key '/schemas/desktop/sugar/user/color', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/user/color', locale `nl': Unable to store a value at key '/schemas/desktop/sugar/user/color', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/user/color', locale `ta': Unable to store a value at key '/schemas/desktop/sugar/user/color', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/sound/volume', locale `de': Unable to store a value at key '/schemas/desktop/sugar/sound/volume', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/sound/volume', locale `sl': Unable to store a value at key '/schemas/desktop/sugar/sound/volume', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/sound/volume', locale `ar': Unable to store a value at key '/schemas/desktop/sugar/sound/volume', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/sound/volume', locale `ja': Unable to store a value at key '/schemas/desktop/sugar/sound/volume', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/sound/volume', locale `C': Unable to store a value at key '/schemas/desktop/sugar/sound/volume', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/sound/volume', locale `vi': Unable to store a value at key '/schemas/desktop/sugar/sound/volume', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/sound/volume', locale `pt': Unable to store a value at key '/schemas/desktop/sugar/sound/volume', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/sound/volume', locale `hi': Unable to store a value at key '/schemas/desktop/sugar/sound/volume', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/sound/volume', locale `sq': Unable to store a value at key '/schemas/desktop/sugar/sound/volume', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/sound/volume', locale `es': Unable to store a value at key '/schemas/desktop/sugar/sound/volume', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/sound/volume', locale `fr': Unable to store a value at key '/schemas/desktop/sugar/sound/volume', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/sound/volume', locale `sv': Unable to store a value at key '/schemas/desktop/sugar/sound/volume', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/sound/volume', locale `mg': Unable to store a value at key '/schemas/desktop/sugar/sound/volume', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/sound/volume', locale `ne': Unable to store a value at key '/schemas/desktop/sugar/sound/volume', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/sound/volume', locale `zh_TW': Unable to store a value at key '/schemas/desktop/sugar/sound/volume', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/sound/volume', locale `it': Unable to store a value at key '/schemas/desktop/sugar/sound/volume', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/sound/volume', locale `mn': Unable to store a value at key '/schemas/desktop/sugar/sound/volume', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/sound/volume', locale `nl': Unable to store a value at key '/schemas/desktop/sugar/sound/volume', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/sound/volume', locale `ta': Unable to store a value at key '/schemas/desktop/sugar/sound/volume', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/sound/mute', locale `de': Unable to store a value at key '/schemas/desktop/sugar/sound/mute', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/sound/mute', locale `sl': Unable to store a value at key '/schemas/desktop/sugar/sound/mute', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/sound/mute', locale `ar': Unable to store a value at key '/schemas/desktop/sugar/sound/mute', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/sound/mute', locale `ja': Unable to store a value at key '/schemas/desktop/sugar/sound/mute', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/sound/mute', locale `C': Unable to store a value at key '/schemas/desktop/sugar/sound/mute', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/sound/mute', locale `vi': Unable to store a value at key '/schemas/desktop/sugar/sound/mute', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/sound/mute', locale `pt': Unable to store a value at key '/schemas/desktop/sugar/sound/mute', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/sound/mute', locale `hi': Unable to store a value at key '/schemas/desktop/sugar/sound/mute', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/sound/mute', locale `es': Unable to store a value at key '/schemas/desktop/sugar/sound/mute', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/sound/mute', locale `fr': Unable to store a value at key '/schemas/desktop/sugar/sound/mute', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/sound/mute', locale `sv': Unable to store a value at key '/schemas/desktop/sugar/sound/mute', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/sound/mute', locale `mg': Unable to store a value at key '/schemas/desktop/sugar/sound/mute', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/sound/mute', locale `ne': Unable to store a value at key '/schemas/desktop/sugar/sound/mute', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/sound/mute', locale `zh_TW': Unable to store a value at key '/schemas/desktop/sugar/sound/mute', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/sound/mute', locale `it': Unable to store a value at key '/schemas/desktop/sugar/sound/mute', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/sound/mute', locale `nl': Unable to store a value at key '/schemas/desktop/sugar/sound/mute', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/sound/mute', locale `ta': Unable to store a value at key '/schemas/desktop/sugar/sound/mute', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/backup_url', locale `de': Unable to store a value at key '/schemas/desktop/sugar/backup_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/backup_url', locale `sl': Unable to store a value at key '/schemas/desktop/sugar/backup_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/backup_url', locale `ar': Unable to store a value at key '/schemas/desktop/sugar/backup_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/backup_url', locale `ja': Unable to store a value at key '/schemas/desktop/sugar/backup_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/backup_url', locale `C': Unable to store a value at key '/schemas/desktop/sugar/backup_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/backup_url', locale `vi': Unable to store a value at key '/schemas/desktop/sugar/backup_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/backup_url', locale `pt': Unable to store a value at key '/schemas/desktop/sugar/backup_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/backup_url', locale `hi': Unable to store a value at key '/schemas/desktop/sugar/backup_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/backup_url', locale `sq': Unable to store a value at key '/schemas/desktop/sugar/backup_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/backup_url', locale `es': Unable to store a value at key '/schemas/desktop/sugar/backup_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/backup_url', locale `fr': Unable to store a value at key '/schemas/desktop/sugar/backup_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/backup_url', locale `sv': Unable to store a value at key '/schemas/desktop/sugar/backup_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/backup_url', locale `mg': Unable to store a value at key '/schemas/desktop/sugar/backup_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/backup_url', locale `ne': Unable to store a value at key '/schemas/desktop/sugar/backup_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/backup_url', locale `zh_TW': Unable to store a value at key '/schemas/desktop/sugar/backup_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/backup_url', locale `it': Unable to store a value at key '/schemas/desktop/sugar/backup_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/backup_url', locale `nl': Unable to store a value at key '/schemas/desktop/sugar/backup_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/backup_url', locale `ta': Unable to store a value at key '/schemas/desktop/sugar/backup_url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/date/timezone', locale `zh_TW': Unable to store a value at key '/schemas/desktop/sugar/date/timezone', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/date/timezone', locale `de': Unable to store a value at key '/schemas/desktop/sugar/date/timezone', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/date/timezone', locale `mr': Unable to store a value at key '/schemas/desktop/sugar/date/timezone', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/date/timezone', locale `te': Unable to store a value at key '/schemas/desktop/sugar/date/timezone', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/date/timezone', locale `si': Unable to store a value at key '/schemas/desktop/sugar/date/timezone', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/date/timezone', locale `vi': Unable to store a value at key '/schemas/desktop/sugar/date/timezone', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/date/timezone', locale `sl': Unable to store a value at key '/schemas/desktop/sugar/date/timezone', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/date/timezone', locale `ar': Unable to store a value at key '/schemas/desktop/sugar/date/timezone', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/date/timezone', locale `ja': Unable to store a value at key '/schemas/desktop/sugar/date/timezone', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/date/timezone', locale `C': Unable to store a value at key '/schemas/desktop/sugar/date/timezone', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/date/timezone', locale `el': Unable to store a value at key '/schemas/desktop/sugar/date/timezone', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/date/timezone', locale `pt': Unable to store a value at key '/schemas/desktop/sugar/date/timezone', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/date/timezone', locale `hi': Unable to store a value at key '/schemas/desktop/sugar/date/timezone', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/date/timezone', locale `sq': Unable to store a value at key '/schemas/desktop/sugar/date/timezone', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/date/timezone', locale `rw': Unable to store a value at key '/schemas/desktop/sugar/date/timezone', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/date/timezone', locale `es': Unable to store a value at key '/schemas/desktop/sugar/date/timezone', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/date/timezone', locale `fr': Unable to store a value at key '/schemas/desktop/sugar/date/timezone', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/date/timezone', locale `nb': Unable to store a value at key '/schemas/desktop/sugar/date/timezone', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/date/timezone', locale `sv': Unable to store a value at key '/schemas/desktop/sugar/date/timezone', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/date/timezone', locale `ne': Unable to store a value at key '/schemas/desktop/sugar/date/timezone', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/date/timezone', locale `ur': Unable to store a value at key '/schemas/desktop/sugar/date/timezone', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/date/timezone', locale `tr': Unable to store a value at key '/schemas/desktop/sugar/date/timezone', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/date/timezone', locale `it': Unable to store a value at key '/schemas/desktop/sugar/date/timezone', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/date/timezone', locale `af': Unable to store a value at key '/schemas/desktop/sugar/date/timezone', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/date/timezone', locale `da': Unable to store a value at key '/schemas/desktop/sugar/date/timezone', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/date/timezone', locale `mn': Unable to store a value at key '/schemas/desktop/sugar/date/timezone', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/date/timezone', locale `ta': Unable to store a value at key '/schemas/desktop/sugar/date/timezone', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/date/timezone', locale `nl': Unable to store a value at key '/schemas/desktop/sugar/date/timezone', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/desktop/favorites_layout', locale `de': Unable to store a value at key '/schemas/desktop/sugar/desktop/favorites_layout', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/desktop/favorites_layout', locale `sl': Unable to store a value at key '/schemas/desktop/sugar/desktop/favorites_layout', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/desktop/favorites_layout', locale `ar': Unable to store a value at key '/schemas/desktop/sugar/desktop/favorites_layout', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/desktop/favorites_layout', locale `ja': Unable to store a value at key '/schemas/desktop/sugar/desktop/favorites_layout', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/desktop/favorites_layout', locale `C': Unable to store a value at key '/schemas/desktop/sugar/desktop/favorites_layout', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/desktop/favorites_layout', locale `vi': Unable to store a value at key '/schemas/desktop/sugar/desktop/favorites_layout', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/desktop/favorites_layout', locale `pt': Unable to store a value at key '/schemas/desktop/sugar/desktop/favorites_layout', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/desktop/favorites_layout', locale `hi': Unable to store a value at key '/schemas/desktop/sugar/desktop/favorites_layout', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/desktop/favorites_layout', locale `es': Unable to store a value at key '/schemas/desktop/sugar/desktop/favorites_layout', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/desktop/favorites_layout', locale `fr': Unable to store a value at key '/schemas/desktop/sugar/desktop/favorites_layout', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/desktop/favorites_layout', locale `sv': Unable to store a value at key '/schemas/desktop/sugar/desktop/favorites_layout', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/desktop/favorites_layout', locale `ne': Unable to store a value at key '/schemas/desktop/sugar/desktop/favorites_layout', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/desktop/favorites_layout', locale `zh_TW': Unable to store a value at key '/schemas/desktop/sugar/desktop/favorites_layout', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/desktop/favorites_layout', locale `it': Unable to store a value at key '/schemas/desktop/sugar/desktop/favorites_layout', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/desktop/favorites_layout', locale `nl': Unable to store a value at key '/schemas/desktop/sugar/desktop/favorites_layout', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/desktop/favorites_layout', locale `ta': Unable to store a value at key '/schemas/desktop/sugar/desktop/favorites_layout', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/desktop/favorites_mode', locale `de': Unable to store a value at key '/schemas/desktop/sugar/desktop/favorites_mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/desktop/favorites_mode', locale `sl': Unable to store a value at key '/schemas/desktop/sugar/desktop/favorites_mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/desktop/favorites_mode', locale `ar': Unable to store a value at key '/schemas/desktop/sugar/desktop/favorites_mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/desktop/favorites_mode', locale `ja': Unable to store a value at key '/schemas/desktop/sugar/desktop/favorites_mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/desktop/favorites_mode', locale `C': Unable to store a value at key '/schemas/desktop/sugar/desktop/favorites_mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/desktop/favorites_mode', locale `vi': Unable to store a value at key '/schemas/desktop/sugar/desktop/favorites_mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/desktop/favorites_mode', locale `pt': Unable to store a value at key '/schemas/desktop/sugar/desktop/favorites_mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/desktop/favorites_mode', locale `hi': Unable to store a value at key '/schemas/desktop/sugar/desktop/favorites_mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/desktop/favorites_mode', locale `es': Unable to store a value at key '/schemas/desktop/sugar/desktop/favorites_mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/desktop/favorites_mode', locale `fr': Unable to store a value at key '/schemas/desktop/sugar/desktop/favorites_mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/desktop/favorites_mode', locale `sv': Unable to store a value at key '/schemas/desktop/sugar/desktop/favorites_mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/desktop/favorites_mode', locale `ne': Unable to store a value at key '/schemas/desktop/sugar/desktop/favorites_mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/desktop/favorites_mode', locale `zh_TW': Unable to store a value at key '/schemas/desktop/sugar/desktop/favorites_mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/desktop/favorites_mode', locale `it': Unable to store a value at key '/schemas/desktop/sugar/desktop/favorites_mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/desktop/favorites_mode', locale `nl': Unable to store a value at key '/schemas/desktop/sugar/desktop/favorites_mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/desktop/favorites_mode', locale `ta': Unable to store a value at key '/schemas/desktop/sugar/desktop/favorites_mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/frame/edge_delay', locale `de': Unable to store a value at key '/schemas/desktop/sugar/frame/edge_delay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/frame/edge_delay', locale `sl': Unable to store a value at key '/schemas/desktop/sugar/frame/edge_delay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/frame/edge_delay', locale `ar': Unable to store a value at key '/schemas/desktop/sugar/frame/edge_delay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/frame/edge_delay', locale `ja': Unable to store a value at key '/schemas/desktop/sugar/frame/edge_delay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/frame/edge_delay', locale `C': Unable to store a value at key '/schemas/desktop/sugar/frame/edge_delay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/frame/edge_delay', locale `vi': Unable to store a value at key '/schemas/desktop/sugar/frame/edge_delay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/frame/edge_delay', locale `pt': Unable to store a value at key '/schemas/desktop/sugar/frame/edge_delay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/frame/edge_delay', locale `hi': Unable to store a value at key '/schemas/desktop/sugar/frame/edge_delay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/frame/edge_delay', locale `es': Unable to store a value at key '/schemas/desktop/sugar/frame/edge_delay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/frame/edge_delay', locale `fr': Unable to store a value at key '/schemas/desktop/sugar/frame/edge_delay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/frame/edge_delay', locale `sv': Unable to store a value at key '/schemas/desktop/sugar/frame/edge_delay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/frame/edge_delay', locale `ne': Unable to store a value at key '/schemas/desktop/sugar/frame/edge_delay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/frame/edge_delay', locale `zh_TW': Unable to store a value at key '/schemas/desktop/sugar/frame/edge_delay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/frame/edge_delay', locale `it': Unable to store a value at key '/schemas/desktop/sugar/frame/edge_delay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/frame/edge_delay', locale `nl': Unable to store a value at key '/schemas/desktop/sugar/frame/edge_delay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/frame/edge_delay', locale `ta': Unable to store a value at key '/schemas/desktop/sugar/frame/edge_delay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/frame/corner_delay', locale `de': Unable to store a value at key '/schemas/desktop/sugar/frame/corner_delay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/frame/corner_delay', locale `sl': Unable to store a value at key '/schemas/desktop/sugar/frame/corner_delay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/frame/corner_delay', locale `ar': Unable to store a value at key '/schemas/desktop/sugar/frame/corner_delay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/frame/corner_delay', locale `ja': Unable to store a value at key '/schemas/desktop/sugar/frame/corner_delay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/frame/corner_delay', locale `C': Unable to store a value at key '/schemas/desktop/sugar/frame/corner_delay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/frame/corner_delay', locale `vi': Unable to store a value at key '/schemas/desktop/sugar/frame/corner_delay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/frame/corner_delay', locale `pt': Unable to store a value at key '/schemas/desktop/sugar/frame/corner_delay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/frame/corner_delay', locale `hi': Unable to store a value at key '/schemas/desktop/sugar/frame/corner_delay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/frame/corner_delay', locale `es': Unable to store a value at key '/schemas/desktop/sugar/frame/corner_delay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/frame/corner_delay', locale `fr': Unable to store a value at key '/schemas/desktop/sugar/frame/corner_delay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/frame/corner_delay', locale `sv': Unable to store a value at key '/schemas/desktop/sugar/frame/corner_delay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/frame/corner_delay', locale `ne': Unable to store a value at key '/schemas/desktop/sugar/frame/corner_delay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/frame/corner_delay', locale `zh_TW': Unable to store a value at key '/schemas/desktop/sugar/frame/corner_delay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/frame/corner_delay', locale `it': Unable to store a value at key '/schemas/desktop/sugar/frame/corner_delay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/frame/corner_delay', locale `nl': Unable to store a value at key '/schemas/desktop/sugar/frame/corner_delay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/frame/corner_delay', locale `ta': Unable to store a value at key '/schemas/desktop/sugar/frame/corner_delay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/collaboration/jabber_server', locale `de': Unable to store a value at key '/schemas/desktop/sugar/collaboration/jabber_server', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/collaboration/jabber_server', locale `sl': Unable to store a value at key '/schemas/desktop/sugar/collaboration/jabber_server', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/collaboration/jabber_server', locale `ar': Unable to store a value at key '/schemas/desktop/sugar/collaboration/jabber_server', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/collaboration/jabber_server', locale `ja': Unable to store a value at key '/schemas/desktop/sugar/collaboration/jabber_server', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/collaboration/jabber_server', locale `C': Unable to store a value at key '/schemas/desktop/sugar/collaboration/jabber_server', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/collaboration/jabber_server', locale `vi': Unable to store a value at key '/schemas/desktop/sugar/collaboration/jabber_server', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/collaboration/jabber_server', locale `pt': Unable to store a value at key '/schemas/desktop/sugar/collaboration/jabber_server', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/collaboration/jabber_server', locale `hi': Unable to store a value at key '/schemas/desktop/sugar/collaboration/jabber_server', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/collaboration/jabber_server', locale `es': Unable to store a value at key '/schemas/desktop/sugar/collaboration/jabber_server', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/collaboration/jabber_server', locale `fr': Unable to store a value at key '/schemas/desktop/sugar/collaboration/jabber_server', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/collaboration/jabber_server', locale `sv': Unable to store a value at key '/schemas/desktop/sugar/collaboration/jabber_server', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/collaboration/jabber_server', locale `ne': Unable to store a value at key '/schemas/desktop/sugar/collaboration/jabber_server', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/collaboration/jabber_server', locale `zh_TW': Unable to store a value at key '/schemas/desktop/sugar/collaboration/jabber_server', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/collaboration/jabber_server', locale `it': Unable to store a value at key '/schemas/desktop/sugar/collaboration/jabber_server', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/collaboration/jabber_server', locale `mn': Unable to store a value at key '/schemas/desktop/sugar/collaboration/jabber_server', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/collaboration/jabber_server', locale `nl': Unable to store a value at key '/schemas/desktop/sugar/collaboration/jabber_server', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/collaboration/jabber_server', locale `ta': Unable to store a value at key '/schemas/desktop/sugar/collaboration/jabber_server', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/power/automatic', locale `de': Unable to store a value at key '/schemas/desktop/sugar/power/automatic', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/power/automatic', locale `sl': Unable to store a value at key '/schemas/desktop/sugar/power/automatic', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/power/automatic', locale `ar': Unable to store a value at key '/schemas/desktop/sugar/power/automatic', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/power/automatic', locale `ja': Unable to store a value at key '/schemas/desktop/sugar/power/automatic', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/power/automatic', locale `C': Unable to store a value at key '/schemas/desktop/sugar/power/automatic', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/power/automatic', locale `vi': Unable to store a value at key '/schemas/desktop/sugar/power/automatic', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/power/automatic', locale `pt': Unable to store a value at key '/schemas/desktop/sugar/power/automatic', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/power/automatic', locale `hi': Unable to store a value at key '/schemas/desktop/sugar/power/automatic', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/power/automatic', locale `es': Unable to store a value at key '/schemas/desktop/sugar/power/automatic', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/power/automatic', locale `fr': Unable to store a value at key '/schemas/desktop/sugar/power/automatic', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/power/automatic', locale `sv': Unable to store a value at key '/schemas/desktop/sugar/power/automatic', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/power/automatic', locale `ne': Unable to store a value at key '/schemas/desktop/sugar/power/automatic', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/power/automatic', locale `zh_TW': Unable to store a value at key '/schemas/desktop/sugar/power/automatic', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/power/automatic', locale `it': Unable to store a value at key '/schemas/desktop/sugar/power/automatic', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/power/automatic', locale `nl': Unable to store a value at key '/schemas/desktop/sugar/power/automatic', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/power/automatic', locale `ta': Unable to store a value at key '/schemas/desktop/sugar/power/automatic', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/power/extreme', locale `de': Unable to store a value at key '/schemas/desktop/sugar/power/extreme', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/power/extreme', locale `sl': Unable to store a value at key '/schemas/desktop/sugar/power/extreme', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/power/extreme', locale `ar': Unable to store a value at key '/schemas/desktop/sugar/power/extreme', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/power/extreme', locale `ja': Unable to store a value at key '/schemas/desktop/sugar/power/extreme', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/power/extreme', locale `C': Unable to store a value at key '/schemas/desktop/sugar/power/extreme', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/power/extreme', locale `vi': Unable to store a value at key '/schemas/desktop/sugar/power/extreme', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/power/extreme', locale `pt': Unable to store a value at key '/schemas/desktop/sugar/power/extreme', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/power/extreme', locale `hi': Unable to store a value at key '/schemas/desktop/sugar/power/extreme', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/power/extreme', locale `es': Unable to store a value at key '/schemas/desktop/sugar/power/extreme', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/power/extreme', locale `fr': Unable to store a value at key '/schemas/desktop/sugar/power/extreme', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/power/extreme', locale `sv': Unable to store a value at key '/schemas/desktop/sugar/power/extreme', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/power/extreme', locale `ne': Unable to store a value at key '/schemas/desktop/sugar/power/extreme', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/power/extreme', locale `zh_TW': Unable to store a value at key '/schemas/desktop/sugar/power/extreme', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/power/extreme', locale `it': Unable to store a value at key '/schemas/desktop/sugar/power/extreme', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/power/extreme', locale `nl': Unable to store a value at key '/schemas/desktop/sugar/power/extreme', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/power/extreme', locale `ta': Unable to store a value at key '/schemas/desktop/sugar/power/extreme', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/collaboration/publish_gadget', locale `de': Unable to store a value at key '/schemas/desktop/sugar/collaboration/publish_gadget', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/collaboration/publish_gadget', locale `sl': Unable to store a value at key '/schemas/desktop/sugar/collaboration/publish_gadget', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/collaboration/publish_gadget', locale `ar': Unable to store a value at key '/schemas/desktop/sugar/collaboration/publish_gadget', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/collaboration/publish_gadget', locale `ja': Unable to store a value at key '/schemas/desktop/sugar/collaboration/publish_gadget', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/collaboration/publish_gadget', locale `C': Unable to store a value at key '/schemas/desktop/sugar/collaboration/publish_gadget', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/collaboration/publish_gadget', locale `vi': Unable to store a value at key '/schemas/desktop/sugar/collaboration/publish_gadget', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/collaboration/publish_gadget', locale `pt': Unable to store a value at key '/schemas/desktop/sugar/collaboration/publish_gadget', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/collaboration/publish_gadget', locale `hi': Unable to store a value at key '/schemas/desktop/sugar/collaboration/publish_gadget', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/collaboration/publish_gadget', locale `es': Unable to store a value at key '/schemas/desktop/sugar/collaboration/publish_gadget', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/collaboration/publish_gadget', locale `fr': Unable to store a value at key '/schemas/desktop/sugar/collaboration/publish_gadget', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/collaboration/publish_gadget', locale `sv': Unable to store a value at key '/schemas/desktop/sugar/collaboration/publish_gadget', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/collaboration/publish_gadget', locale `ne': Unable to store a value at key '/schemas/desktop/sugar/collaboration/publish_gadget', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/collaboration/publish_gadget', locale `zh_TW': Unable to store a value at key '/schemas/desktop/sugar/collaboration/publish_gadget', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/collaboration/publish_gadget', locale `it': Unable to store a value at key '/schemas/desktop/sugar/collaboration/publish_gadget', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/collaboration/publish_gadget', locale `nl': Unable to store a value at key '/schemas/desktop/sugar/collaboration/publish_gadget', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/collaboration/publish_gadget', locale `ta': Unable to store a value at key '/schemas/desktop/sugar/collaboration/publish_gadget', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/show_logout', locale `de': Unable to store a value at key '/schemas/desktop/sugar/show_logout', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/show_logout', locale `ar': Unable to store a value at key '/schemas/desktop/sugar/show_logout', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/show_logout', locale `ja': Unable to store a value at key '/schemas/desktop/sugar/show_logout', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/show_logout', locale `C': Unable to store a value at key '/schemas/desktop/sugar/show_logout', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/show_logout', locale `vi': Unable to store a value at key '/schemas/desktop/sugar/show_logout', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/show_logout', locale `pt': Unable to store a value at key '/schemas/desktop/sugar/show_logout', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/show_logout', locale `hi': Unable to store a value at key '/schemas/desktop/sugar/show_logout', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/show_logout', locale `es': Unable to store a value at key '/schemas/desktop/sugar/show_logout', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/show_logout', locale `fr': Unable to store a value at key '/schemas/desktop/sugar/show_logout', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/show_logout', locale `sv': Unable to store a value at key '/schemas/desktop/sugar/show_logout', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/show_logout', locale `zh_TW': Unable to store a value at key '/schemas/desktop/sugar/show_logout', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/show_logout', locale `it': Unable to store a value at key '/schemas/desktop/sugar/show_logout', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/show_logout', locale `nl': Unable to store a value at key '/schemas/desktop/sugar/show_logout', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/show_logout', locale `ta': Unable to store a value at key '/schemas/desktop/sugar/show_logout', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/peripherals/keyboard/layouts', locale `de': Unable to store a value at key '/schemas/desktop/sugar/peripherals/keyboard/layouts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/peripherals/keyboard/layouts', locale `ar': Unable to store a value at key '/schemas/desktop/sugar/peripherals/keyboard/layouts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/peripherals/keyboard/layouts', locale `ja': Unable to store a value at key '/schemas/desktop/sugar/peripherals/keyboard/layouts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/peripherals/keyboard/layouts', locale `C': Unable to store a value at key '/schemas/desktop/sugar/peripherals/keyboard/layouts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/peripherals/keyboard/layouts', locale `vi': Unable to store a value at key '/schemas/desktop/sugar/peripherals/keyboard/layouts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/peripherals/keyboard/layouts', locale `pt': Unable to store a value at key '/schemas/desktop/sugar/peripherals/keyboard/layouts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/peripherals/keyboard/layouts', locale `hi': Unable to store a value at key '/schemas/desktop/sugar/peripherals/keyboard/layouts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/peripherals/keyboard/layouts', locale `es': Unable to store a value at key '/schemas/desktop/sugar/peripherals/keyboard/layouts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/peripherals/keyboard/layouts', locale `fr': Unable to store a value at key '/schemas/desktop/sugar/peripherals/keyboard/layouts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/peripherals/keyboard/layouts', locale `sv': Unable to store a value at key '/schemas/desktop/sugar/peripherals/keyboard/layouts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/peripherals/keyboard/layouts', locale `zh_TW': Unable to store a value at key '/schemas/desktop/sugar/peripherals/keyboard/layouts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/peripherals/keyboard/layouts', locale `it': Unable to store a value at key '/schemas/desktop/sugar/peripherals/keyboard/layouts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/peripherals/keyboard/layouts', locale `nl': Unable to store a value at key '/schemas/desktop/sugar/peripherals/keyboard/layouts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/peripherals/keyboard/options', locale `de': Unable to store a value at key '/schemas/desktop/sugar/peripherals/keyboard/options', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/peripherals/keyboard/options', locale `ar': Unable to store a value at key '/schemas/desktop/sugar/peripherals/keyboard/options', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/peripherals/keyboard/options', locale `ja': Unable to store a value at key '/schemas/desktop/sugar/peripherals/keyboard/options', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/peripherals/keyboard/options', locale `C': Unable to store a value at key '/schemas/desktop/sugar/peripherals/keyboard/options', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/peripherals/keyboard/options', locale `vi': Unable to store a value at key '/schemas/desktop/sugar/peripherals/keyboard/options', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/peripherals/keyboard/options', locale `pt': Unable to store a value at key '/schemas/desktop/sugar/peripherals/keyboard/options', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/peripherals/keyboard/options', locale `hi': Unable to store a value at key '/schemas/desktop/sugar/peripherals/keyboard/options', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/peripherals/keyboard/options', locale `es': Unable to store a value at key '/schemas/desktop/sugar/peripherals/keyboard/options', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/peripherals/keyboard/options', locale `fr': Unable to store a value at key '/schemas/desktop/sugar/peripherals/keyboard/options', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/peripherals/keyboard/options', locale `sv': Unable to store a value at key '/schemas/desktop/sugar/peripherals/keyboard/options', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/peripherals/keyboard/options', locale `zh_TW': Unable to store a value at key '/schemas/desktop/sugar/peripherals/keyboard/options', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/peripherals/keyboard/options', locale `it': Unable to store a value at key '/schemas/desktop/sugar/peripherals/keyboard/options', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/peripherals/keyboard/options', locale `nl': Unable to store a value at key '/schemas/desktop/sugar/peripherals/keyboard/options', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/peripherals/keyboard/model', locale `de': Unable to store a value at key '/schemas/desktop/sugar/peripherals/keyboard/model', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/peripherals/keyboard/model', locale `ar': Unable to store a value at key '/schemas/desktop/sugar/peripherals/keyboard/model', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/peripherals/keyboard/model', locale `ja': Unable to store a value at key '/schemas/desktop/sugar/peripherals/keyboard/model', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/peripherals/keyboard/model', locale `C': Unable to store a value at key '/schemas/desktop/sugar/peripherals/keyboard/model', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/peripherals/keyboard/model', locale `vi': Unable to store a value at key '/schemas/desktop/sugar/peripherals/keyboard/model', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/peripherals/keyboard/model', locale `pt': Unable to store a value at key '/schemas/desktop/sugar/peripherals/keyboard/model', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/peripherals/keyboard/model', locale `hi': Unable to store a value at key '/schemas/desktop/sugar/peripherals/keyboard/model', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/peripherals/keyboard/model', locale `es': Unable to store a value at key '/schemas/desktop/sugar/peripherals/keyboard/model', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/peripherals/keyboard/model', locale `fr': Unable to store a value at key '/schemas/desktop/sugar/peripherals/keyboard/model', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/peripherals/keyboard/model', locale `sv': Unable to store a value at key '/schemas/desktop/sugar/peripherals/keyboard/model', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/peripherals/keyboard/model', locale `zh_TW': Unable to store a value at key '/schemas/desktop/sugar/peripherals/keyboard/model', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/peripherals/keyboard/model', locale `it': Unable to store a value at key '/schemas/desktop/sugar/peripherals/keyboard/model', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/peripherals/keyboard/model', locale `nl': Unable to store a value at key '/schemas/desktop/sugar/peripherals/keyboard/model', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/font/default_face', locale `C': Unable to store a value at key '/schemas/desktop/sugar/font/default_face', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/font/default_face', locale `vi': Unable to store a value at key '/schemas/desktop/sugar/font/default_face', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/font/default_face', locale `ar': Unable to store a value at key '/schemas/desktop/sugar/font/default_face', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/font/default_face', locale `it': Unable to store a value at key '/schemas/desktop/sugar/font/default_face', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/font/default_face', locale `de': Unable to store a value at key '/schemas/desktop/sugar/font/default_face', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/font/default_face', locale `ja': Unable to store a value at key '/schemas/desktop/sugar/font/default_face', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/font/default_face', locale `zh_TW': Unable to store a value at key '/schemas/desktop/sugar/font/default_face', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/font/default_size', locale `C': Unable to store a value at key '/schemas/desktop/sugar/font/default_size', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/font/default_size', locale `vi': Unable to store a value at key '/schemas/desktop/sugar/font/default_size', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/font/default_size', locale `ar': Unable to store a value at key '/schemas/desktop/sugar/font/default_size', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/font/default_size', locale `it': Unable to store a value at key '/schemas/desktop/sugar/font/default_size', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/font/default_size', locale `de': Unable to store a value at key '/schemas/desktop/sugar/font/default_size', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/font/default_size', locale `ja': Unable to store a value at key '/schemas/desktop/sugar/font/default_size', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/font/default_size', locale `zh_TW': Unable to store a value at key '/schemas/desktop/sugar/font/default_size', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/i18n/langpackdir', locale `C': Unable to store a value at key '/schemas/desktop/sugar/i18n/langpackdir', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/i18n/langpackdir', locale `de': Unable to store a value at key '/schemas/desktop/sugar/i18n/langpackdir', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/network/gsm/username', locale `C': Unable to store a value at key '/schemas/desktop/sugar/network/gsm/username', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/network/gsm/username', locale `de': Unable to store a value at key '/schemas/desktop/sugar/network/gsm/username', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/network/gsm/password', locale `C': Unable to store a value at key '/schemas/desktop/sugar/network/gsm/password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/network/gsm/password', locale `de': Unable to store a value at key '/schemas/desktop/sugar/network/gsm/password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/network/gsm/number', locale `C': Unable to store a value at key '/schemas/desktop/sugar/network/gsm/number', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/network/gsm/number', locale `de': Unable to store a value at key '/schemas/desktop/sugar/network/gsm/number', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/network/gsm/apn', locale `C': Unable to store a value at key '/schemas/desktop/sugar/network/gsm/apn', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/network/gsm/apn', locale `de': Unable to store a value at key '/schemas/desktop/sugar/network/gsm/apn', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/network/gsm/pin', locale `C': Unable to store a value at key '/schemas/desktop/sugar/network/gsm/pin', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/network/gsm/pin', locale `de': Unable to store a value at key '/schemas/desktop/sugar/network/gsm/pin', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/network/gsm/puk', locale `C': Unable to store a value at key '/schemas/desktop/sugar/network/gsm/puk', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/desktop/sugar/network/gsm/puk', locale `de': Unable to store a value at key '/schemas/desktop/sugar/network/gsm/puk', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only 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/icons/hicolor/scalable/apps" || /bin/mkdir -p "/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/icons/hicolor/scalable/apps" /usr/bin/install -c -m 644 /build/buildd/sugar-0.88-0.88.1/./data/sugar-xo.svg '/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/icons/hicolor/scalable/apps' test -z "/usr/share/mime/packages" || /bin/mkdir -p "/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/mime/packages" /usr/bin/install -c -m 644 sugar.xml '/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/mime/packages' test -z "/etc/dbus-1/system.d/" || /bin/mkdir -p "/build/buildd/sugar-0.88-0.88.1/debian/tmp//etc/dbus-1/system.d/" /usr/bin/install -c -m 644 /build/buildd/sugar-0.88-0.88.1/./data/nm-user-settings.conf '/build/buildd/sugar-0.88-0.88.1/debian/tmp//etc/dbus-1/system.d/' test -z "/etc/gconf/schemas" || /bin/mkdir -p "/build/buildd/sugar-0.88-0.88.1/debian/tmp//etc/gconf/schemas" /usr/bin/install -c -m 644 sugar.schemas '/build/buildd/sugar-0.88-0.88.1/debian/tmp//etc/gconf/schemas' test -z "/usr/share/sugar/data" || /bin/mkdir -p "/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/sugar/data" /usr/bin/install -c -m 644 /build/buildd/sugar-0.88-0.88.1/./data/activities.defaults /build/buildd/sugar-0.88-0.88.1/./data/kbdconfig /build/buildd/sugar-0.88-0.88.1/./data/mime.defaults /build/buildd/sugar-0.88-0.88.1/./data/GPLv2 /build/buildd/sugar-0.88-0.88.1/./data/sugar-72.gtkrc /build/buildd/sugar-0.88-0.88.1/./data/sugar-100.gtkrc '/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/sugar/data' test -z "/usr/share/xsessions" || /bin/mkdir -p "/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/xsessions" /usr/bin/install -c -m 644 /build/buildd/sugar-0.88-0.88.1/./data/sugar.desktop '/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/xsessions' /usr/bin/make install-data-hook make[5]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/data' if [ -z "$DESTDIR" ]; then \ update-mime-database "/usr/share/mime"; \ fi make[5]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/data' make[4]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/data' make[3]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/data' make[2]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/data' Making install in po make[2]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/po' linguas="af am ar ay bg bi bn_IN bn ca cpp cs da de dz el en es fa_AF fa ff fil fr gu ha he hi ht hu id ig is it ja km ko kos mg mi mk ml mn mr ms mvo nb ne nl pa pap pis pl ps pt_BR pt qu ro ru rw sd si sk sl sq sv sw ta te th tpi tr tvl tzo ug ur vi wa yo zh_CN zh_TW "; \ for lang in $linguas; do \ dir=/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/$lang/LC_MESSAGES; \ /bin/bash /build/buildd/sugar-0.88-0.88.1/install-sh -d $dir; \ if test -r $lang.gmo; then \ /usr/bin/install -c -m 644 $lang.gmo $dir/sugar.mo; \ echo "installing $lang.gmo as $dir/sugar.mo"; \ else \ /usr/bin/install -c -m 644 /build/buildd/sugar-0.88-0.88.1/./po/$lang.gmo $dir/sugar.mo; \ echo "installing /build/buildd/sugar-0.88-0.88.1/./po/$lang.gmo as" \ "$dir/sugar.mo"; \ fi; \ if test -r $lang.gmo.m; then \ /usr/bin/install -c -m 644 $lang.gmo.m $dir/sugar.mo.m; \ echo "installing $lang.gmo.m as $dir/sugar.mo.m"; \ else \ if test -r /build/buildd/sugar-0.88-0.88.1/./po/$lang.gmo.m ; then \ /usr/bin/install -c -m 644 /build/buildd/sugar-0.88-0.88.1/./po/$lang.gmo.m \ $dir/sugar.mo.m; \ echo "installing /build/buildd/sugar-0.88-0.88.1/./po/$lang.gmo.m as" \ "$dir/sugar.mo.m"; \ else \ true; \ fi; \ fi; \ done installing af.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/af/LC_MESSAGES/sugar.mo installing am.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/am/LC_MESSAGES/sugar.mo installing ar.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/ar/LC_MESSAGES/sugar.mo installing ay.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/ay/LC_MESSAGES/sugar.mo installing bg.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/bg/LC_MESSAGES/sugar.mo installing bi.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/bi/LC_MESSAGES/sugar.mo installing bn_IN.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/bn_IN/LC_MESSAGES/sugar.mo installing bn.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/bn/LC_MESSAGES/sugar.mo installing ca.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/ca/LC_MESSAGES/sugar.mo installing cpp.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/cpp/LC_MESSAGES/sugar.mo installing cs.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/cs/LC_MESSAGES/sugar.mo installing da.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/da/LC_MESSAGES/sugar.mo installing de.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/de/LC_MESSAGES/sugar.mo installing dz.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/dz/LC_MESSAGES/sugar.mo installing el.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/el/LC_MESSAGES/sugar.mo installing en.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/en/LC_MESSAGES/sugar.mo installing es.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/es/LC_MESSAGES/sugar.mo installing fa_AF.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/fa_AF/LC_MESSAGES/sugar.mo installing fa.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/fa/LC_MESSAGES/sugar.mo installing ff.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/ff/LC_MESSAGES/sugar.mo installing fil.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/fil/LC_MESSAGES/sugar.mo installing fr.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/fr/LC_MESSAGES/sugar.mo installing gu.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/gu/LC_MESSAGES/sugar.mo installing ha.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/ha/LC_MESSAGES/sugar.mo installing he.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/he/LC_MESSAGES/sugar.mo installing hi.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/hi/LC_MESSAGES/sugar.mo installing ht.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/ht/LC_MESSAGES/sugar.mo installing hu.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/hu/LC_MESSAGES/sugar.mo installing id.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/id/LC_MESSAGES/sugar.mo installing ig.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/ig/LC_MESSAGES/sugar.mo installing is.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/is/LC_MESSAGES/sugar.mo installing it.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/it/LC_MESSAGES/sugar.mo installing ja.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/ja/LC_MESSAGES/sugar.mo installing km.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/km/LC_MESSAGES/sugar.mo installing ko.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/ko/LC_MESSAGES/sugar.mo installing kos.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/kos/LC_MESSAGES/sugar.mo installing mg.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/mg/LC_MESSAGES/sugar.mo installing mi.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/mi/LC_MESSAGES/sugar.mo installing mk.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/mk/LC_MESSAGES/sugar.mo installing ml.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/ml/LC_MESSAGES/sugar.mo installing mn.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/mn/LC_MESSAGES/sugar.mo installing mr.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/mr/LC_MESSAGES/sugar.mo installing ms.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/ms/LC_MESSAGES/sugar.mo installing mvo.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/mvo/LC_MESSAGES/sugar.mo installing nb.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/nb/LC_MESSAGES/sugar.mo installing ne.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/ne/LC_MESSAGES/sugar.mo installing nl.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/nl/LC_MESSAGES/sugar.mo installing pa.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/pa/LC_MESSAGES/sugar.mo installing pap.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/pap/LC_MESSAGES/sugar.mo installing pis.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/pis/LC_MESSAGES/sugar.mo installing pl.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/pl/LC_MESSAGES/sugar.mo installing ps.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/ps/LC_MESSAGES/sugar.mo installing pt_BR.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/pt_BR/LC_MESSAGES/sugar.mo installing pt.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/pt/LC_MESSAGES/sugar.mo installing qu.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/qu/LC_MESSAGES/sugar.mo installing ro.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/ro/LC_MESSAGES/sugar.mo installing ru.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/ru/LC_MESSAGES/sugar.mo installing rw.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/rw/LC_MESSAGES/sugar.mo installing sd.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/sd/LC_MESSAGES/sugar.mo installing si.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/si/LC_MESSAGES/sugar.mo installing sk.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/sk/LC_MESSAGES/sugar.mo installing sl.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/sl/LC_MESSAGES/sugar.mo installing sq.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/sq/LC_MESSAGES/sugar.mo installing sv.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/sv/LC_MESSAGES/sugar.mo installing sw.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/sw/LC_MESSAGES/sugar.mo installing ta.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/ta/LC_MESSAGES/sugar.mo installing te.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/te/LC_MESSAGES/sugar.mo installing th.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/th/LC_MESSAGES/sugar.mo installing tpi.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/tpi/LC_MESSAGES/sugar.mo installing tr.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/tr/LC_MESSAGES/sugar.mo installing tvl.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/tvl/LC_MESSAGES/sugar.mo installing tzo.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/tzo/LC_MESSAGES/sugar.mo installing ug.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/ug/LC_MESSAGES/sugar.mo installing ur.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/ur/LC_MESSAGES/sugar.mo installing vi.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/vi/LC_MESSAGES/sugar.mo installing wa.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/wa/LC_MESSAGES/sugar.mo installing yo.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/yo/LC_MESSAGES/sugar.mo installing zh_CN.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/zh_CN/LC_MESSAGES/sugar.mo installing zh_TW.gmo as /build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/locale/zh_TW/LC_MESSAGES/sugar.mo make[2]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/po' Making install in src make[2]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/src' Making install in jarabe make[3]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe' Making install in controlpanel make[4]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe/controlpanel' make[5]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe/controlpanel' make[5]: Nothing to be done for `install-exec-am'. test -z "/usr/lib/python2.7/dist-packages/jarabe/controlpanel" || /bin/mkdir -p "/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/lib/python2.7/dist-packages/jarabe/controlpanel" /usr/bin/install -c -m 644 /build/buildd/sugar-0.88-0.88.1/./src/jarabe/controlpanel/__init__.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/controlpanel/cmd.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/controlpanel/gui.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/controlpanel/inlinealert.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/controlpanel/sectionview.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/controlpanel/toolbar.py '/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/lib/python2.7/dist-packages/jarabe/controlpanel' Byte-compiling python modules... __init__.pycmd.pygui.pyinlinealert.pysectionview.pytoolbar.py Byte-compiling python modules (optimized versions) ... __init__.pycmd.pygui.pyinlinealert.pysectionview.pytoolbar.py make[5]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe/controlpanel' make[4]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe/controlpanel' Making install in desktop make[4]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe/desktop' make[5]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe/desktop' make[5]: Nothing to be done for `install-exec-am'. test -z "/usr/lib/python2.7/dist-packages/jarabe/desktop" || /bin/mkdir -p "/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/lib/python2.7/dist-packages/jarabe/desktop" /usr/bin/install -c -m 644 /build/buildd/sugar-0.88-0.88.1/./src/jarabe/desktop/__init__.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/desktop/activitieslist.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/desktop/favoritesview.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/desktop/favoriteslayout.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/desktop/friendview.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/desktop/grid.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/desktop/groupbox.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/desktop/homebox.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/desktop/homewindow.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/desktop/keydialog.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/desktop/meshbox.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/desktop/myicon.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/desktop/schoolserver.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/desktop/snowflakelayout.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/desktop/spreadlayout.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/desktop/transitionbox.py '/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/lib/python2.7/dist-packages/jarabe/desktop' Byte-compiling python modules... __init__.pyactivitieslist.pyfavoritesview.pyfavoriteslayout.pyfriendview.pygrid.pygroupbox.pyhomebox.pyhomewindow.pykeydialog.pymeshbox.pymyicon.pyschoolserver.pysnowflakelayout.pyspreadlayout.pytransitionbox.py Byte-compiling python modules (optimized versions) ... __init__.pyactivitieslist.pyfavoritesview.pyfavoriteslayout.pyfriendview.pygrid.pygroupbox.pyhomebox.pyhomewindow.pykeydialog.pymeshbox.pymyicon.pyschoolserver.pysnowflakelayout.pyspreadlayout.pytransitionbox.py make[5]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe/desktop' make[4]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe/desktop' Making install in frame make[4]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe/frame' make[5]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe/frame' make[5]: Nothing to be done for `install-exec-am'. test -z "/usr/lib/python2.7/dist-packages/jarabe/frame" || /bin/mkdir -p "/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/lib/python2.7/dist-packages/jarabe/frame" /usr/bin/install -c -m 644 /build/buildd/sugar-0.88-0.88.1/./src/jarabe/frame/__init__.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/frame/activitiestray.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/frame/clipboard.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/frame/clipboardicon.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/frame/clipboardmenu.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/frame/clipboardobject.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/frame/clipboardpanelwindow.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/frame/clipboardtray.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/frame/devicestray.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/frame/frameinvoker.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/frame/friendstray.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/frame/eventarea.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/frame/frame.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/frame/notification.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/frame/framewindow.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/frame/zoomtoolbar.py '/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/lib/python2.7/dist-packages/jarabe/frame' Byte-compiling python modules... __init__.pyactivitiestray.pyclipboard.pyclipboardicon.pyclipboardmenu.pyclipboardobject.pyclipboardpanelwindow.pyclipboardtray.pydevicestray.pyframeinvoker.pyfriendstray.pyeventarea.pyframe.pynotification.pyframewindow.pyzoomtoolbar.py Byte-compiling python modules (optimized versions) ... __init__.pyactivitiestray.pyclipboard.pyclipboardicon.pyclipboardmenu.pyclipboardobject.pyclipboardpanelwindow.pyclipboardtray.pydevicestray.pyframeinvoker.pyfriendstray.pyeventarea.pyframe.pynotification.pyframewindow.pyzoomtoolbar.py make[5]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe/frame' make[4]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe/frame' Making install in journal make[4]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe/journal' make[5]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe/journal' make[5]: Nothing to be done for `install-exec-am'. test -z "/usr/lib/python2.7/dist-packages/jarabe/journal" || /bin/mkdir -p "/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/lib/python2.7/dist-packages/jarabe/journal" /usr/bin/install -c -m 644 /build/buildd/sugar-0.88-0.88.1/./src/jarabe/journal/__init__.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/journal/detailview.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/journal/expandedentry.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/journal/journalactivity.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/journal/journalentrybundle.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/journal/journaltoolbox.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/journal/keepicon.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/journal/listmodel.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/journal/listview.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/journal/misc.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/journal/modalalert.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/journal/model.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/journal/objectchooser.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/journal/palettes.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/journal/volumestoolbar.py '/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/lib/python2.7/dist-packages/jarabe/journal' Byte-compiling python modules... __init__.pydetailview.pyexpandedentry.pyjournalactivity.pyjournalentrybundle.pyjournaltoolbox.pykeepicon.pylistmodel.pylistview.pymisc.pymodalalert.pymodel.pyobjectchooser.pypalettes.pyvolumestoolbar.py Byte-compiling python modules (optimized versions) ... __init__.pydetailview.pyexpandedentry.pyjournalactivity.pyjournalentrybundle.pyjournaltoolbox.pykeepicon.pylistmodel.pylistview.pymisc.pymodalalert.pymodel.pyobjectchooser.pypalettes.pyvolumestoolbar.py make[5]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe/journal' make[4]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe/journal' Making install in model make[4]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe/model' make[5]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe/model' make[5]: Nothing to be done for `install-exec-am'. test -z "/usr/lib/python2.7/dist-packages/jarabe/model" || /bin/mkdir -p "/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/lib/python2.7/dist-packages/jarabe/model" /usr/bin/install -c -m 644 /build/buildd/sugar-0.88-0.88.1/./src/jarabe/model/__init__.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/model/buddy.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/model/bundleregistry.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/model/filetransfer.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/model/friends.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/model/invites.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/model/olpcmesh.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/model/owner.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/model/mimeregistry.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/model/neighborhood.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/model/network.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/model/notifications.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/model/shell.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/model/screen.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/model/session.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/model/sound.py '/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/lib/python2.7/dist-packages/jarabe/model' Byte-compiling python modules... __init__.pybuddy.pybundleregistry.pyfiletransfer.pyfriends.pyinvites.pyolpcmesh.pyowner.pymimeregistry.pyneighborhood.pynetwork.pynotifications.pyshell.pyscreen.pysession.pysound.py Byte-compiling python modules (optimized versions) ... __init__.pybuddy.pybundleregistry.pyfiletransfer.pyfriends.pyinvites.pyolpcmesh.pyowner.pymimeregistry.pyneighborhood.pynetwork.pynotifications.pyshell.pyscreen.pysession.pysound.py make[5]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe/model' make[4]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe/model' Making install in view make[4]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe/view' make[5]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe/view' make[5]: Nothing to be done for `install-exec-am'. test -z "/usr/lib/python2.7/dist-packages/jarabe/view" || /bin/mkdir -p "/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/lib/python2.7/dist-packages/jarabe/view" /usr/bin/install -c -m 644 /build/buildd/sugar-0.88-0.88.1/./src/jarabe/view/__init__.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/view/buddyicon.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/view/buddymenu.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/view/keyhandler.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/view/launcher.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/view/palettes.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/view/pulsingicon.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/view/service.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/view/tabbinghandler.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/view/viewsource.py '/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/lib/python2.7/dist-packages/jarabe/view' Byte-compiling python modules... __init__.pybuddyicon.pybuddymenu.pykeyhandler.pylauncher.pypalettes.pypulsingicon.pyservice.pytabbinghandler.pyviewsource.py Byte-compiling python modules (optimized versions) ... __init__.pybuddyicon.pybuddymenu.pykeyhandler.pylauncher.pypalettes.pypulsingicon.pyservice.pytabbinghandler.pyviewsource.py make[5]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe/view' make[4]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe/view' Making install in intro make[4]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe/intro' make[5]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe/intro' make[5]: Nothing to be done for `install-exec-am'. test -z "/usr/lib/python2.7/dist-packages/jarabe/intro" || /bin/mkdir -p "/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/lib/python2.7/dist-packages/jarabe/intro" /usr/bin/install -c -m 644 /build/buildd/sugar-0.88-0.88.1/./src/jarabe/intro/default-picture.png '/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/lib/python2.7/dist-packages/jarabe/intro' test -z "/usr/lib/python2.7/dist-packages/jarabe/intro" || /bin/mkdir -p "/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/lib/python2.7/dist-packages/jarabe/intro" /usr/bin/install -c -m 644 /build/buildd/sugar-0.88-0.88.1/./src/jarabe/intro/__init__.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/intro/colorpicker.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/intro/window.py '/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/lib/python2.7/dist-packages/jarabe/intro' Byte-compiling python modules... __init__.pycolorpicker.pywindow.py Byte-compiling python modules (optimized versions) ... __init__.pycolorpicker.pywindow.py make[5]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe/intro' make[4]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe/intro' Making install in util make[4]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe/util' Making install in telepathy make[5]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe/util/telepathy' make[6]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe/util/telepathy' make[6]: Nothing to be done for `install-exec-am'. test -z "/usr/lib/python2.7/dist-packages/jarabe/util/telepathy" || /bin/mkdir -p "/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/lib/python2.7/dist-packages/jarabe/util/telepathy" /usr/bin/install -c -m 644 /build/buildd/sugar-0.88-0.88.1/./src/jarabe/util/telepathy/__init__.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/util/telepathy/connection_watcher.py '/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/lib/python2.7/dist-packages/jarabe/util/telepathy' Byte-compiling python modules... __init__.pyconnection_watcher.py Byte-compiling python modules (optimized versions) ... __init__.pyconnection_watcher.py make[6]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe/util/telepathy' make[5]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe/util/telepathy' make[5]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe/util' make[6]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe/util' make[6]: Nothing to be done for `install-exec-am'. test -z "/usr/lib/python2.7/dist-packages/jarabe/util" || /bin/mkdir -p "/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/lib/python2.7/dist-packages/jarabe/util" /usr/bin/install -c -m 644 /build/buildd/sugar-0.88-0.88.1/./src/jarabe/util/__init__.py /build/buildd/sugar-0.88-0.88.1/./src/jarabe/util/emulator.py '/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/lib/python2.7/dist-packages/jarabe/util' Byte-compiling python modules... __init__.pyemulator.py Byte-compiling python modules (optimized versions) ... __init__.pyemulator.py make[6]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe/util' make[5]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe/util' make[4]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe/util' make[4]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe' make[5]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe' make[5]: Nothing to be done for `install-exec-am'. test -z "/usr/lib/python2.7/dist-packages/jarabe" || /bin/mkdir -p "/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/lib/python2.7/dist-packages/jarabe" /usr/bin/install -c -m 644 config.py '/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/lib/python2.7/dist-packages/jarabe' Byte-compiling python modules... config.py Byte-compiling python modules (optimized versions) ... config.py test -z "/usr/lib/python2.7/dist-packages/jarabe" || /bin/mkdir -p "/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/lib/python2.7/dist-packages/jarabe" /usr/bin/install -c -m 644 /build/buildd/sugar-0.88-0.88.1/./src/jarabe/__init__.py '/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/lib/python2.7/dist-packages/jarabe' Byte-compiling python modules... __init__.py Byte-compiling python modules (optimized versions) ... __init__.py make[5]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe' make[4]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe' make[3]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/src/jarabe' make[3]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/src' make[4]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/src' 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/sugar-0.88-0.88.1/build/src' make[3]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/src' make[2]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/src' Making install in extensions make[2]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/extensions' Making install in cpsection make[3]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection' Making install in aboutme make[4]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/aboutme' make[5]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/aboutme' make[5]: Nothing to be done for `install-exec-am'. test -z "/usr/share/sugar/extensions/cpsection/aboutme" || /bin/mkdir -p "/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/sugar/extensions/cpsection/aboutme" /usr/bin/install -c -m 644 /build/buildd/sugar-0.88-0.88.1/./extensions/cpsection/aboutme/__init__.py /build/buildd/sugar-0.88-0.88.1/./extensions/cpsection/aboutme/model.py /build/buildd/sugar-0.88-0.88.1/./extensions/cpsection/aboutme/view.py '/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/sugar/extensions/cpsection/aboutme' Byte-compiling python modules... __init__.pymodel.pyview.py Byte-compiling python modules (optimized versions) ... __init__.pymodel.pyview.py make[5]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/aboutme' make[4]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/aboutme' Making install in aboutcomputer make[4]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/aboutcomputer' make[5]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/aboutcomputer' make[5]: Nothing to be done for `install-exec-am'. test -z "/usr/share/sugar/extensions/cpsection/aboutcomputer" || /bin/mkdir -p "/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/sugar/extensions/cpsection/aboutcomputer" /usr/bin/install -c -m 644 /build/buildd/sugar-0.88-0.88.1/./extensions/cpsection/aboutcomputer/__init__.py /build/buildd/sugar-0.88-0.88.1/./extensions/cpsection/aboutcomputer/model.py /build/buildd/sugar-0.88-0.88.1/./extensions/cpsection/aboutcomputer/view.py '/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/sugar/extensions/cpsection/aboutcomputer' Byte-compiling python modules... __init__.pymodel.pyview.py Byte-compiling python modules (optimized versions) ... __init__.pymodel.pyview.py make[5]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/aboutcomputer' make[4]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/aboutcomputer' Making install in datetime make[4]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/datetime' make[5]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/datetime' make[5]: Nothing to be done for `install-exec-am'. test -z "/usr/share/sugar/extensions/cpsection/datetime" || /bin/mkdir -p "/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/sugar/extensions/cpsection/datetime" /usr/bin/install -c -m 644 /build/buildd/sugar-0.88-0.88.1/./extensions/cpsection/datetime/__init__.py /build/buildd/sugar-0.88-0.88.1/./extensions/cpsection/datetime/model.py /build/buildd/sugar-0.88-0.88.1/./extensions/cpsection/datetime/view.py '/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/sugar/extensions/cpsection/datetime' Byte-compiling python modules... __init__.pymodel.pyview.py Byte-compiling python modules (optimized versions) ... __init__.pymodel.pyview.py make[5]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/datetime' make[4]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/datetime' Making install in frame make[4]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/frame' make[5]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/frame' make[5]: Nothing to be done for `install-exec-am'. test -z "/usr/share/sugar/extensions/cpsection/frame" || /bin/mkdir -p "/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/sugar/extensions/cpsection/frame" /usr/bin/install -c -m 644 /build/buildd/sugar-0.88-0.88.1/./extensions/cpsection/frame/__init__.py /build/buildd/sugar-0.88-0.88.1/./extensions/cpsection/frame/model.py /build/buildd/sugar-0.88-0.88.1/./extensions/cpsection/frame/view.py '/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/sugar/extensions/cpsection/frame' Byte-compiling python modules... __init__.pymodel.pyview.py Byte-compiling python modules (optimized versions) ... __init__.pymodel.pyview.py make[5]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/frame' make[4]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/frame' Making install in keyboard make[4]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/keyboard' make[5]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/keyboard' make[5]: Nothing to be done for `install-exec-am'. test -z "/usr/share/sugar/extensions/cpsection/keyboard" || /bin/mkdir -p "/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/sugar/extensions/cpsection/keyboard" /usr/bin/install -c -m 644 /build/buildd/sugar-0.88-0.88.1/./extensions/cpsection/keyboard/__init__.py /build/buildd/sugar-0.88-0.88.1/./extensions/cpsection/keyboard/model.py /build/buildd/sugar-0.88-0.88.1/./extensions/cpsection/keyboard/view.py '/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/sugar/extensions/cpsection/keyboard' Byte-compiling python modules... __init__.pymodel.pyview.py Byte-compiling python modules (optimized versions) ... __init__.pymodel.pyview.py make[5]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/keyboard' make[4]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/keyboard' Making install in language make[4]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/language' make[5]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/language' make[5]: Nothing to be done for `install-exec-am'. test -z "/usr/share/sugar/extensions/cpsection/language" || /bin/mkdir -p "/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/sugar/extensions/cpsection/language" /usr/bin/install -c -m 644 /build/buildd/sugar-0.88-0.88.1/./extensions/cpsection/language/__init__.py /build/buildd/sugar-0.88-0.88.1/./extensions/cpsection/language/model.py /build/buildd/sugar-0.88-0.88.1/./extensions/cpsection/language/view.py '/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/sugar/extensions/cpsection/language' Byte-compiling python modules... __init__.pymodel.pyview.py Byte-compiling python modules (optimized versions) ... __init__.pymodel.pyview.py make[5]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/language' make[4]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/language' Making install in modemconfiguration make[4]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/modemconfiguration' make[5]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/modemconfiguration' make[5]: Nothing to be done for `install-exec-am'. test -z "/usr/share/sugar/extensions/cpsection/modemconfiguration" || /bin/mkdir -p "/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/sugar/extensions/cpsection/modemconfiguration" /usr/bin/install -c -m 644 /build/buildd/sugar-0.88-0.88.1/./extensions/cpsection/modemconfiguration/__init__.py /build/buildd/sugar-0.88-0.88.1/./extensions/cpsection/modemconfiguration/model.py /build/buildd/sugar-0.88-0.88.1/./extensions/cpsection/modemconfiguration/view.py '/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/sugar/extensions/cpsection/modemconfiguration' Byte-compiling python modules... __init__.pymodel.pyview.py Byte-compiling python modules (optimized versions) ... __init__.pymodel.pyview.py make[5]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/modemconfiguration' make[4]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/modemconfiguration' Making install in network make[4]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/network' make[5]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/network' make[5]: Nothing to be done for `install-exec-am'. test -z "/usr/share/sugar/extensions/cpsection/network" || /bin/mkdir -p "/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/sugar/extensions/cpsection/network" /usr/bin/install -c -m 644 /build/buildd/sugar-0.88-0.88.1/./extensions/cpsection/network/__init__.py /build/buildd/sugar-0.88-0.88.1/./extensions/cpsection/network/model.py /build/buildd/sugar-0.88-0.88.1/./extensions/cpsection/network/view.py '/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/sugar/extensions/cpsection/network' Byte-compiling python modules... __init__.pymodel.pyview.py Byte-compiling python modules (optimized versions) ... __init__.pymodel.pyview.py make[5]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/network' make[4]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/network' Making install in power make[4]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/power' make[5]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/power' make[5]: Nothing to be done for `install-exec-am'. test -z "/usr/share/sugar/extensions/cpsection/power" || /bin/mkdir -p "/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/sugar/extensions/cpsection/power" /usr/bin/install -c -m 644 /build/buildd/sugar-0.88-0.88.1/./extensions/cpsection/power/__init__.py /build/buildd/sugar-0.88-0.88.1/./extensions/cpsection/power/model.py /build/buildd/sugar-0.88-0.88.1/./extensions/cpsection/power/view.py '/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/sugar/extensions/cpsection/power' Byte-compiling python modules... __init__.pymodel.pyview.py Byte-compiling python modules (optimized versions) ... __init__.pymodel.pyview.py make[5]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/power' make[4]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/power' Making install in updater make[4]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/updater' Making install in backends make[5]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/updater/backends' make[6]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/updater/backends' make[6]: Nothing to be done for `install-exec-am'. test -z "/usr/share/sugar/extensions/cpsection/updater/backends" || /bin/mkdir -p "/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/sugar/extensions/cpsection/updater/backends" /usr/bin/install -c -m 644 /build/buildd/sugar-0.88-0.88.1/./extensions/cpsection/updater/backends/aslo.py /build/buildd/sugar-0.88-0.88.1/./extensions/cpsection/updater/backends/__init__.py '/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/sugar/extensions/cpsection/updater/backends' Byte-compiling python modules... aslo.py__init__.py Byte-compiling python modules (optimized versions) ... aslo.py__init__.py make[6]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/updater/backends' make[5]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/updater/backends' make[5]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/updater' make[6]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/updater' make[6]: Nothing to be done for `install-exec-am'. test -z "/usr/share/sugar/extensions/cpsection/updater" || /bin/mkdir -p "/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/sugar/extensions/cpsection/updater" /usr/bin/install -c -m 644 /build/buildd/sugar-0.88-0.88.1/./extensions/cpsection/updater/__init__.py /build/buildd/sugar-0.88-0.88.1/./extensions/cpsection/updater/model.py /build/buildd/sugar-0.88-0.88.1/./extensions/cpsection/updater/view.py '/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/sugar/extensions/cpsection/updater' Byte-compiling python modules... __init__.pymodel.pyview.py Byte-compiling python modules (optimized versions) ... __init__.pymodel.pyview.py make[6]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/updater' make[5]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/updater' make[4]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection/updater' make[4]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection' make[5]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection' make[5]: Nothing to be done for `install-exec-am'. test -z "/usr/share/sugar/extensions/cpsection" || /bin/mkdir -p "/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/sugar/extensions/cpsection" /usr/bin/install -c -m 644 /build/buildd/sugar-0.88-0.88.1/./extensions/cpsection/__init__.py '/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/sugar/extensions/cpsection' Byte-compiling python modules... __init__.py Byte-compiling python modules (optimized versions) ... __init__.py make[5]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection' make[4]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection' make[3]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/cpsection' Making install in deviceicon make[3]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/deviceicon' make[4]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/deviceicon' make[4]: Nothing to be done for `install-exec-am'. test -z "/usr/share/sugar/extensions/deviceicon" || /bin/mkdir -p "/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/sugar/extensions/deviceicon" /usr/bin/install -c -m 644 /build/buildd/sugar-0.88-0.88.1/./extensions/deviceicon/__init__.py /build/buildd/sugar-0.88-0.88.1/./extensions/deviceicon/battery.py /build/buildd/sugar-0.88-0.88.1/./extensions/deviceicon/network.py /build/buildd/sugar-0.88-0.88.1/./extensions/deviceicon/speaker.py /build/buildd/sugar-0.88-0.88.1/./extensions/deviceicon/volume.py '/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/sugar/extensions/deviceicon' Byte-compiling python modules... __init__.pybattery.pynetwork.pyspeaker.pyvolume.py Byte-compiling python modules (optimized versions) ... __init__.pybattery.pynetwork.pyspeaker.pyvolume.py make[4]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/deviceicon' make[3]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/deviceicon' Making install in globalkey make[3]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/globalkey' make[4]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/globalkey' make[4]: Nothing to be done for `install-exec-am'. test -z "/usr/share/sugar/extensions/globalkey" || /bin/mkdir -p "/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/sugar/extensions/globalkey" /usr/bin/install -c -m 644 /build/buildd/sugar-0.88-0.88.1/./extensions/globalkey/__init__.py /build/buildd/sugar-0.88-0.88.1/./extensions/globalkey/screenshot.py /build/buildd/sugar-0.88-0.88.1/./extensions/globalkey/viewsource.py '/build/buildd/sugar-0.88-0.88.1/debian/tmp//usr/share/sugar/extensions/globalkey' Byte-compiling python modules... __init__.pyscreenshot.pyviewsource.py Byte-compiling python modules (optimized versions) ... __init__.pyscreenshot.pyviewsource.py make[4]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/globalkey' make[3]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/extensions/globalkey' make[3]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/extensions' make[4]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build/extensions' 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/sugar-0.88-0.88.1/build/extensions' make[3]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/extensions' make[2]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build/extensions' make[2]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build' make[3]: Entering directory `/build/buildd/sugar-0.88-0.88.1/build' 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/sugar-0.88-0.88.1/build' make[2]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build' make[1]: Leaving directory `/build/buildd/sugar-0.88-0.88.1/build' touch debian/stamp-makefile-install Adding cdbs dependencies to debian/sucrose-0.88.substvars dh_installdirs -psucrose-0.88 Adding cdbs dependencies to debian/sugar-session-0.88.substvars dh_installdirs -psugar-session-0.88 Adding cdbs dependencies to debian/sugar-emulator-0.88.substvars dh_installdirs -psugar-emulator-0.88 Adding cdbs dependencies to debian/sugar-tools-0.88.substvars dh_installdirs -psugar-tools-0.88 Adding cdbs dependencies to debian/python-jarabe-0.88.substvars dh_installdirs -ppython-jarabe-0.88 dh_installdocs -psucrose-0.88 ./README ./AUTHORS dh_installexamples -psucrose-0.88 dh_installman -psucrose-0.88 dh_installinfo -psucrose-0.88 dh_installmenu -psucrose-0.88 dh_installcron -psucrose-0.88 dh_installinit -psucrose-0.88 dh_installdebconf -psucrose-0.88 dh_installemacsen -psucrose-0.88 dh_installcatalogs -psucrose-0.88 dh_installpam -psucrose-0.88 dh_installlogrotate -psucrose-0.88 dh_installlogcheck -psucrose-0.88 dh_installchangelogs -psucrose-0.88 dh_installudev -psucrose-0.88 dh_lintian -psucrose-0.88 dh_bugfiles -psucrose-0.88 dh_install -psucrose-0.88 dh_link -psucrose-0.88 dh_buildinfo -psucrose-0.88 dh_installmime -psucrose-0.88 dh_installgsettings -psucrose-0.88 dh_pycentral -psucrose-0.88 /usr/share/sugar \1 better written as $1 at /usr/bin/dh_pycentral line 203. pycentral: pycentral debhelper: missing XB-Python-Version attribute in package sucrose-0.88 dh_installdocs -psugar-session-0.88 ./README ./AUTHORS dh_installexamples -psugar-session-0.88 dh_installman -psugar-session-0.88 dh_installinfo -psugar-session-0.88 dh_installmenu -psugar-session-0.88 dh_installcron -psugar-session-0.88 dh_installinit -psugar-session-0.88 dh_installdebconf -psugar-session-0.88 dh_installemacsen -psugar-session-0.88 dh_installcatalogs -psugar-session-0.88 dh_installpam -psugar-session-0.88 dh_installlogrotate -psugar-session-0.88 dh_installlogcheck -psugar-session-0.88 dh_installchangelogs -psugar-session-0.88 dh_installudev -psugar-session-0.88 dh_lintian -psugar-session-0.88 dh_bugfiles -psugar-session-0.88 dh_install -psugar-session-0.88 dh_link -psugar-session-0.88 dh_buildinfo -psugar-session-0.88 dh_installmime -psugar-session-0.88 dh_installgsettings -psugar-session-0.88 dh_gconf -psugar-session-0.88 dh_pycentral -psugar-session-0.88 /usr/share/sugar \1 better written as $1 at /usr/bin/dh_pycentral line 203. dh_installdocs -psugar-emulator-0.88 ./README ./AUTHORS dh_installexamples -psugar-emulator-0.88 dh_installman -psugar-emulator-0.88 dh_installinfo -psugar-emulator-0.88 dh_installmenu -psugar-emulator-0.88 dh_installcron -psugar-emulator-0.88 dh_installinit -psugar-emulator-0.88 dh_installdebconf -psugar-emulator-0.88 dh_installemacsen -psugar-emulator-0.88 dh_installcatalogs -psugar-emulator-0.88 dh_installpam -psugar-emulator-0.88 dh_installlogrotate -psugar-emulator-0.88 dh_installlogcheck -psugar-emulator-0.88 dh_installchangelogs -psugar-emulator-0.88 dh_installudev -psugar-emulator-0.88 dh_lintian -psugar-emulator-0.88 dh_bugfiles -psugar-emulator-0.88 dh_install -psugar-emulator-0.88 dh_link -psugar-emulator-0.88 dh_buildinfo -psugar-emulator-0.88 dh_installmime -psugar-emulator-0.88 dh_installgsettings -psugar-emulator-0.88 dh_pycentral -psugar-emulator-0.88 /usr/share/sugar \1 better written as $1 at /usr/bin/dh_pycentral line 203. dh_installdocs -psugar-tools-0.88 ./README ./AUTHORS dh_installexamples -psugar-tools-0.88 dh_installman -psugar-tools-0.88 dh_installinfo -psugar-tools-0.88 dh_installmenu -psugar-tools-0.88 dh_installcron -psugar-tools-0.88 dh_installinit -psugar-tools-0.88 dh_installdebconf -psugar-tools-0.88 dh_installemacsen -psugar-tools-0.88 dh_installcatalogs -psugar-tools-0.88 dh_installpam -psugar-tools-0.88 dh_installlogrotate -psugar-tools-0.88 dh_installlogcheck -psugar-tools-0.88 dh_installchangelogs -psugar-tools-0.88 dh_installudev -psugar-tools-0.88 dh_lintian -psugar-tools-0.88 dh_bugfiles -psugar-tools-0.88 dh_install -psugar-tools-0.88 dh_link -psugar-tools-0.88 dh_buildinfo -psugar-tools-0.88 dh_installmime -psugar-tools-0.88 dh_installgsettings -psugar-tools-0.88 dh_pycentral -psugar-tools-0.88 /usr/share/sugar \1 better written as $1 at /usr/bin/dh_pycentral line 203. dh_installdocs -ppython-jarabe-0.88 ./README ./AUTHORS dh_installexamples -ppython-jarabe-0.88 dh_installman -ppython-jarabe-0.88 dh_installinfo -ppython-jarabe-0.88 dh_installmenu -ppython-jarabe-0.88 dh_installcron -ppython-jarabe-0.88 dh_installinit -ppython-jarabe-0.88 dh_installdebconf -ppython-jarabe-0.88 dh_installemacsen -ppython-jarabe-0.88 dh_installcatalogs -ppython-jarabe-0.88 dh_installpam -ppython-jarabe-0.88 dh_installlogrotate -ppython-jarabe-0.88 dh_installlogcheck -ppython-jarabe-0.88 dh_installchangelogs -ppython-jarabe-0.88 dh_installudev -ppython-jarabe-0.88 dh_lintian -ppython-jarabe-0.88 dh_bugfiles -ppython-jarabe-0.88 dh_install -ppython-jarabe-0.88 dh_link -ppython-jarabe-0.88 dh_buildinfo -ppython-jarabe-0.88 dh_installmime -ppython-jarabe-0.88 dh_installgsettings -ppython-jarabe-0.88 dh_pycentral -ppython-jarabe-0.88 /usr/share/sugar \1 better written as $1 at /usr/bin/dh_pycentral line 203. dh_strip -psucrose-0.88 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: dh_compress -psucrose-0.88 dh_fixperms -psucrose-0.88 dh_makeshlibs -psucrose-0.88 dh_strip -psugar-session-0.88 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: dh_compress -psugar-session-0.88 dh_fixperms -psugar-session-0.88 dh_makeshlibs -psugar-session-0.88 dh_strip -psugar-emulator-0.88 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: dh_compress -psugar-emulator-0.88 dh_fixperms -psugar-emulator-0.88 dh_makeshlibs -psugar-emulator-0.88 dh_strip -psugar-tools-0.88 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: dh_compress -psugar-tools-0.88 dh_fixperms -psugar-tools-0.88 dh_makeshlibs -psugar-tools-0.88 dh_strip -ppython-jarabe-0.88 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: dh_compress -ppython-jarabe-0.88 dh_fixperms -ppython-jarabe-0.88 dh_makeshlibs -ppython-jarabe-0.88 dh_installdeb -psucrose-0.88 dh_perl -psucrose-0.88 dh_shlibdeps -psucrose-0.88 dh_installdeb -psugar-session-0.88 dh_perl -psugar-session-0.88 dh_shlibdeps -psugar-session-0.88 dh_installdeb -psugar-emulator-0.88 dh_perl -psugar-emulator-0.88 dh_shlibdeps -psugar-emulator-0.88 dh_installdeb -psugar-tools-0.88 dh_perl -psugar-tools-0.88 dh_shlibdeps -psugar-tools-0.88 dh_installdeb -ppython-jarabe-0.88 dh_perl -ppython-jarabe-0.88 dh_shlibdeps -ppython-jarabe-0.88 dh_gencontrol -psucrose-0.88 dpkg-gencontrol: warning: Recommends field of package sucrose-0.88: unknown substitution variable ${cdbs:Recommends} dpkg-gencontrol: warning: Conflicts field of package sucrose-0.88: unknown substitution variable ${cdbs:Conflicts} dpkg-gencontrol: warning: Replaces field of package sucrose-0.88: unknown substitution variable ${cdbs:Replaces} dpkg-gencontrol: warning: Provides field of package sucrose-0.88: unknown substitution variable ${python:Provides} dpkg-gencontrol: warning: Provides field of package sucrose-0.88: unknown substitution variable ${cdbs:Provides} dpkg-gencontrol: warning: package sucrose-0.88: unused substitution variable ${python:Versions} # only call dh_scour for packages in main if grep -q '^Component:[[:space:]]*main' /CurrentlyBuilding 2>/dev/null; then dh_scour -psucrose-0.88 ; fi dh_md5sums -psucrose-0.88 dh_builddeb -psucrose-0.88 INFO: pkgstriptranslations version 109 pkgstriptranslations: processing sucrose-0.88 (in debian/sucrose-0.88); do_strip: , oemstrip: pkgmaintainermangler: Not overriding Maintainer for domain lists.ubuntu.com pkgstripfiles: processing control file: debian/sucrose-0.88/DEBIAN/control, package sucrose-0.88, directory debian/sucrose-0.88 .. removing usr/share/doc/sucrose-0.88/buildinfo.gz grep: ../sugar-session-0.88/DEBIAN/control: No such file or directory Searching for duplicated docs in dependency sugar-session-0.88... symlinking README in sucrose-0.88 to file in sugar-session-0.88 symlinking AUTHORS in sucrose-0.88 to file in sugar-session-0.88 symlinking changelog.Debian.gz in sucrose-0.88 to file in sugar-session-0.88 grep: ../sugar-emulator-0.88/DEBIAN/control: No such file or directory Searching for duplicated docs in dependency sugar-emulator-0.88... grep: ../sugar-tools-0.88/DEBIAN/control: No such file or directory Searching for duplicated docs in dependency sugar-tools-0.88... dpkg-deb: warning: 'debian/sucrose-0.88/DEBIAN/control' contains user-defined field 'Original-Maintainer' dpkg-deb: warning: ignoring 1 warning about the control file(s) dpkg-deb: building package `sucrose-0.88' in `../sucrose-0.88_0.88.1-5ubuntu1_all.deb'. dh_gencontrol -psugar-session-0.88 dpkg-gencontrol: warning: Depends field of package sugar-session-0.88: unknown substitution variable ${shlibs:Depends} dpkg-gencontrol: warning: Provides field of package sugar-session-0.88: unknown substitution variable ${python:Provides} # only call dh_scour for packages in main if grep -q '^Component:[[:space:]]*main' /CurrentlyBuilding 2>/dev/null; then dh_scour -psugar-session-0.88 ; fi dh_md5sums -psugar-session-0.88 dh_builddeb -psugar-session-0.88 INFO: pkgstriptranslations version 109 pkgstriptranslations: processing sugar-session-0.88 (in debian/sugar-session-0.88); do_strip: , oemstrip: debian/sugar-session-0.88/usr/share/xsessions/sugar.desktop: does not have gettext domain, not stripping pkgmaintainermangler: Not overriding Maintainer for domain lists.ubuntu.com pkgstripfiles: processing control file: debian/sugar-session-0.88/DEBIAN/control, package sugar-session-0.88, directory debian/sugar-session-0.88 .. removing usr/share/doc/sugar-session-0.88/buildinfo.gz grep: ../python-jarabe-0.88/DEBIAN/control: No such file or directory Searching for duplicated docs in dependency python-jarabe-0.88... symlinking README in sugar-session-0.88 to file in python-jarabe-0.88 symlinking AUTHORS in sugar-session-0.88 to file in python-jarabe-0.88 symlinking changelog.Debian.gz in sugar-session-0.88 to file in python-jarabe-0.88 dpkg-deb: warning: 'debian/sugar-session-0.88/DEBIAN/control' contains user-defined field 'Original-Maintainer' dpkg-deb: warning: 'debian/sugar-session-0.88/DEBIAN/control' contains user-defined field 'Python-Version' dpkg-deb: warning: ignoring 2 warnings about the control file(s) dpkg-deb: building package `sugar-session-0.88' in `../sugar-session-0.88_0.88.1-5ubuntu1_all.deb'. dh_gencontrol -psugar-emulator-0.88 dpkg-gencontrol: warning: Depends field of package sugar-emulator-0.88: unknown substitution variable ${shlibs:Depends} dpkg-gencontrol: warning: Depends field of package sugar-emulator-0.88: unknown substitution variable ${python:Depends} dpkg-gencontrol: warning: Recommends field of package sugar-emulator-0.88: unknown substitution variable ${cdbs:Recommends} dpkg-gencontrol: warning: Suggests field of package sugar-emulator-0.88: unknown substitution variable ${cdbs:Suggests} dpkg-gencontrol: warning: Provides field of package sugar-emulator-0.88: unknown substitution variable ${python:Provides} # only call dh_scour for packages in main if grep -q '^Component:[[:space:]]*main' /CurrentlyBuilding 2>/dev/null; then dh_scour -psugar-emulator-0.88 ; fi dh_md5sums -psugar-emulator-0.88 dh_builddeb -psugar-emulator-0.88 INFO: pkgstriptranslations version 109 pkgstriptranslations: processing sugar-emulator-0.88 (in debian/sugar-emulator-0.88); do_strip: , oemstrip: debian/sugar-emulator-0.88/usr/share/applications/sugar-emulator.desktop: does not have gettext domain, not stripping pkgmaintainermangler: Not overriding Maintainer for domain lists.ubuntu.com pkgstripfiles: processing control file: debian/sugar-emulator-0.88/DEBIAN/control, package sugar-emulator-0.88, directory debian/sugar-emulator-0.88 .. removing usr/share/doc/sugar-emulator-0.88/buildinfo.gz Searching for duplicated docs in dependency sugar-session-0.88... symlinking README in sugar-emulator-0.88 to file in python-jarabe-0.88 symlinking AUTHORS in sugar-emulator-0.88 to file in python-jarabe-0.88 symlinking changelog.Debian.gz in sugar-emulator-0.88 to file in python-jarabe-0.88 grep: ../python-jarabe-0.88/DEBIAN/control: No such file or directory Searching for duplicated docs in dependency python-jarabe-0.88... dpkg-deb: warning: 'debian/sugar-emulator-0.88/DEBIAN/control' contains user-defined field 'Original-Maintainer' dpkg-deb: warning: 'debian/sugar-emulator-0.88/DEBIAN/control' contains user-defined field 'Python-Version' dpkg-deb: warning: ignoring 2 warnings about the control file(s) dpkg-deb: building package `sugar-emulator-0.88' in `../sugar-emulator-0.88_0.88.1-5ubuntu1_all.deb'. dh_gencontrol -psugar-tools-0.88 dpkg-gencontrol: warning: Depends field of package sugar-tools-0.88: unknown substitution variable ${shlibs:Depends} dpkg-gencontrol: warning: Provides field of package sugar-tools-0.88: unknown substitution variable ${python:Provides} # only call dh_scour for packages in main if grep -q '^Component:[[:space:]]*main' /CurrentlyBuilding 2>/dev/null; then dh_scour -psugar-tools-0.88 ; fi dh_md5sums -psugar-tools-0.88 dh_builddeb -psugar-tools-0.88 INFO: pkgstriptranslations version 109 pkgstriptranslations: processing sugar-tools-0.88 (in debian/sugar-tools-0.88); do_strip: , oemstrip: pkgmaintainermangler: Not overriding Maintainer for domain lists.ubuntu.com pkgstripfiles: processing control file: debian/sugar-tools-0.88/DEBIAN/control, package sugar-tools-0.88, directory debian/sugar-tools-0.88 .. removing usr/share/doc/sugar-tools-0.88/buildinfo.gz grep: ../python-jarabe-0.88/DEBIAN/control: No such file or directory Searching for duplicated docs in dependency python-jarabe-0.88... symlinking README in sugar-tools-0.88 to file in python-jarabe-0.88 symlinking AUTHORS in sugar-tools-0.88 to file in python-jarabe-0.88 symlinking changelog.Debian.gz in sugar-tools-0.88 to file in python-jarabe-0.88 dpkg-deb: warning: 'debian/sugar-tools-0.88/DEBIAN/control' contains user-defined field 'Original-Maintainer' dpkg-deb: warning: 'debian/sugar-tools-0.88/DEBIAN/control' contains user-defined field 'Python-Version' dpkg-deb: warning: ignoring 2 warnings about the control file(s) dpkg-deb: building package `sugar-tools-0.88' in `../sugar-tools-0.88_0.88.1-5ubuntu1_all.deb'. dh_gencontrol -ppython-jarabe-0.88 dpkg-gencontrol: warning: Depends field of package python-jarabe-0.88: unknown substitution variable ${shlibs:Depends} dpkg-gencontrol: warning: Provides field of package python-jarabe-0.88: unknown substitution variable ${python:Provides} # only call dh_scour for packages in main if grep -q '^Component:[[:space:]]*main' /CurrentlyBuilding 2>/dev/null; then dh_scour -ppython-jarabe-0.88 ; fi dh_md5sums -ppython-jarabe-0.88 dh_builddeb -ppython-jarabe-0.88 INFO: pkgstriptranslations version 109 pkgstriptranslations: processing python-jarabe-0.88 (in debian/python-jarabe-0.88); do_strip: , oemstrip: pkgmaintainermangler: Not overriding Maintainer for domain lists.ubuntu.com pkgstripfiles: processing control file: debian/python-jarabe-0.88/DEBIAN/control, package python-jarabe-0.88, directory debian/python-jarabe-0.88 .. removing usr/share/doc/python-jarabe-0.88/buildinfo.gz pkgstripfiles: Truncating usr/share/doc/python-jarabe-0.88/changelog.Debian.gz to topmost ten records OptiPNG 0.6.4: Advanced PNG optimizer. Copyright (C) 2001-2010 Cosmin Truta. ** Processing: ./usr/share/pyshared/jarabe/intro/default-picture.png 400x300 pixels, 3x8 bits/pixel, RGB Reducing image to 8 bits/pixel, grayscale Input IDAT size = 10333 bytes Input file size = 10442 bytes Trying: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 4176 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 = 4176 Output IDAT size = 4176 bytes (6157 bytes decrease) Output file size = 4273 bytes (6169 bytes = 59.08% decrease) 4273 4273 100% ./usr/share/pyshared/jarabe/intro/default-picture.png (Unsupported bit depth/color type, 8/0) 4273 4273 100% dpkg-deb: warning: 'debian/python-jarabe-0.88/DEBIAN/control' contains user-defined field 'Original-Maintainer' dpkg-deb: warning: 'debian/python-jarabe-0.88/DEBIAN/control' contains user-defined field 'Python-Version' dpkg-deb: warning: ignoring 2 warnings about the control file(s) dpkg-deb: building package `python-jarabe-0.88' in `../python-jarabe-0.88_0.88.1-5ubuntu1_all.deb'. dpkg-genchanges -b -mUbuntu/i386 Build Daemon >../sugar-0.88_0.88.1-5ubuntu1_i386.changes dpkg-genchanges: binary-only upload - not including any source code dpkg-source --after-build sugar-0.88-0.88.1 dpkg-buildpackage: binary only upload (no source included) ****************************************************************************** Build finished at 20111205-0839 chroot-autobuild/build/buildd/sucrose-0.88_0.88.1-5ubuntu1_all.deb: new debian package, version 2.0. size 4396 bytes: control archive= 878 bytes. 1231 bytes, 21 lines control 71 bytes, 1 lines md5sums Package: sucrose-0.88 Source: sugar-0.88 Version: 0.88.1-5ubuntu1 Architecture: all Maintainer: Ubuntu Developers Installed-Size: 51 Depends: sugar-session-0.88, sugar-emulator-0.88, sugar-tools-0.88, python-carquinyol-0.88, sugar-terminal-activity, sugar-turtleart-activity, sugar-pippy-activity, sugar-log-activity-0.86, sugar-chat-activity-0.86, sugar-write-activity-0.86, python-xklavier, network-manager, modemmanager, gvfs, wpasupplicant, avahi-autoipd, openssh-client, x11-xserver-utils, lsb-release, ethtool, tzdata, alsa-utils, gdb Suggests: sugar-calculate-activity, sugar-etoys-activity, sugar-jukebox-activity-0.88, sugar-imageviewer-activity-0.88 Section: x11 Priority: optional Homepage: http://wiki.sugarlabs.org/go/Sugar Description: Sugar graphical shell - Sucrose 0.88 Sugar is a graphical user interface aimed at children. . Originating as intregral part of the OLPC "XO" a.k.a. the $100 laptop, Sugar has since grown into a more widely usable low-ressource desktop environment for kids. . This package depends on all packages which make up Sucrose, the official base Sugar environment. Original-Maintainer: Debian OLPC chroot-autobuild/build/buildd/sugar-session-0.88_0.88.1-5ubuntu1_all.deb: new debian package, version 2.0. size 264232 bytes: control archive= 5536 bytes. 43 bytes, 1 lines conffiles 1738 bytes, 26 lines control 11460 bytes, 145 lines md5sums 741 bytes, 21 lines * postinst #!/bin/sh 334 bytes, 10 lines * postrm #!/bin/sh 286 bytes, 10 lines * preinst #!/bin/sh 1243 bytes, 47 lines * prerm #!/bin/sh Package: sugar-session-0.88 Source: sugar-0.88 Version: 0.88.1-5ubuntu1 Architecture: all Maintainer: Ubuntu Developers Installed-Size: 1695 Depends: python, python-central (>= 0.6.11), gconf2 (>= 2.28.1-2), python-sugar-0.88, python-sugar-toolkit-0.88, sugar-artwork-0.88, python-jarabe-0.88, python-gobject (>= 2.15.0), python-gtk2, python-dbus, python-wnck | python-gnome2-desktop (<= 2.24.0-1), python-gconf | python-gnome2 (<= 2.22.3-2), metacity (>= 1:2.27.1), dbus-x11 Recommends: sugar-emulator-0.88, sugar-tools-0.88, python-carquinyol-0.88, sugar-terminal-activity, sugar-turtleart-activity, sugar-pippy-activity, sugar-log-activity-0.86 | sugar-log-activity, sugar-chat-activity-0.86 | sugar-chat-activity, sugar-write-activity-0.86 | sugar-write-activity, python-xklavier, openssh-client, network-manager, modemmanager, gvfs, x11-xserver-utils, lsb-release, ethtool, tzdata, sucrose-0.88 Suggests: sugar-calculate-activity, sugar-etoys-activity, sugar-jukebox-activity-0.88 | sugar-jukebox-activity, sugar-imageviewer-activity-0.88 | sugar-imageviewer-activity Conflicts: sugar-session Breaks: sugar (<= 0.82.9-5) Replaces: sugar (<= 0.82.9-5) Provides: sugar Section: x11 Priority: optional Homepage: http://wiki.sugarlabs.org/go/Sugar Description: Sugar graphical shell - window manager Sugar is a graphical user interface aimed at children. . Originating as intregral part of the OLPC "XO" a.k.a. the $100 laptop, Sugar has since grown into a more widely usable low-ressource desktop environment for kids. . This package contains the integrated session and window manager Sugar. Original-Maintainer: Debian OLPC Python-Version: all chroot-autobuild/build/buildd/sugar-emulator-0.88_0.88.1-5ubuntu1_all.deb: new debian package, version 2.0. size 5128 bytes: control archive= 1054 bytes. 966 bytes, 25 lines control 284 bytes, 4 lines md5sums 185 bytes, 7 lines * postinst #!/bin/sh 160 bytes, 5 lines * postrm #!/bin/sh Package: sugar-emulator-0.88 Source: sugar-0.88 Version: 0.88.1-5ubuntu1 Architecture: all Maintainer: Ubuntu Developers Installed-Size: 64 Depends: sugar-session-0.88, python-jarabe-0.88, dbus-x11, xserver-xephyr, x11-utils Conflicts: sugar-emulator Breaks: sugar (<= 0.82.9-5) Replaces: sugar (<= 0.82.9-5) Provides: sugar-emulator Section: x11 Priority: optional Homepage: http://wiki.sugarlabs.org/go/Sugar Description: Sugar graphical shell - emulator Sugar is a graphical user interface aimed at children. . Originating as intregral part of the OLPC "XO" a.k.a. the $100 laptop, Sugar has since grown into a more widely usable low-ressource desktop environment for kids. . This package contains a wrapper script to run Sugar in a Xephyr window, making it possible to run it from inside another Desktop environment. Original-Maintainer: Debian OLPC Python-Version: all chroot-autobuild/build/buildd/sugar-tools-0.88_0.88.1-5ubuntu1_all.deb: new debian package, version 2.0. size 6842 bytes: control archive= 1033 bytes. 1221 bytes, 31 lines control 369 bytes, 6 lines md5sums Package: sugar-tools-0.88 Source: sugar-0.88 Version: 0.88.1-5ubuntu1 Architecture: all Maintainer: Ubuntu Developers Installed-Size: 65 Depends: python, python-sugar-0.88, python-sugar-toolkit-0.88, python-jarabe-0.88 Recommends: sugar-session-0.88, python-gobject (>= 2.15.0), python-gtk2, python-dbus, python-wnck | python-gnome2-desktop (<= 2.24.0-1), network-manager, modemmanager, x11-xserver-utils, lsb-release, ethtool, tzdata, dbus Suggests: gdb Conflicts: sugar-tools Breaks: sugar (<= 0.82.9-5) Replaces: sugar (<= 0.82.9-5) Provides: sugar-tools Section: x11 Priority: optional Homepage: http://wiki.sugarlabs.org/go/Sugar Description: Sugar graphical shell - window manager Sugar is a graphical user interface aimed at children. . Originating as intregral part of the OLPC "XO" a.k.a. the $100 laptop, Sugar has since grown into a more widely usable low-ressource desktop environment for kids. . This package contains the following helper utilities for Sugar: - sugar-activity - sugar-control-panel - sugar-install-bundle - sugar-launch - sugar-ui-check Original-Maintainer: Debian OLPC Python-Version: all chroot-autobuild/build/buildd/python-jarabe-0.88_0.88.1-5ubuntu1_all.deb: new debian package, version 2.0. size 139134 bytes: control archive= 4512 bytes. 1580 bytes, 31 lines control 7592 bytes, 94 lines md5sums 373 bytes, 11 lines * postinst #!/bin/sh 286 bytes, 10 lines * preinst #!/bin/sh 1243 bytes, 47 lines * prerm #!/bin/sh Package: python-jarabe-0.88 Source: sugar-0.88 Version: 0.88.1-5ubuntu1 Architecture: all Maintainer: Ubuntu Developers Installed-Size: 760 Depends: python, python-central (>= 0.6.11), python-sugar-0.88, python-sugar-toolkit-0.88, sugar-presence-service-0.88, python-hippocanvas, python-gobject (>= 2.15.0), python-gtk2, python-cairo, python-dbus, python-telepathy (>= 0.15.9), python-simplejson, python-gtksourceview2, python-wnck | python-gnome2-desktop (<= 2.24.0-1), python-gconf | python-gnome2 (<= 2.22.3-2) Recommends: sugar-session-0.88, network-manager, modemmanager, wpasupplicant, avahi-autoipd, openssh-client, alsa-utils Suggests: xserver-xephyr, x11-utils Conflicts: python-jarabe Breaks: sugar (<= 0.82.9-5), sugar-journal-activity Replaces: sugar (<= 0.82.9-5), sugar-journal-activity Provides: python-jarabe Section: python Priority: optional Homepage: http://wiki.sugarlabs.org/go/Sugar Description: Sugar graphical shell - library Sugar is a graphical user interface aimed at children. . Originating as intregral part of the OLPC "XO" a.k.a. the $100 laptop, Sugar has since grown into a more widely usable low-ressource desktop environment for kids. . This package contains Jarabe, the Sugar Graphical "Shell" Interface providing the shell-level operations for Sugar. It interacts heavily with the Sugar UI libraries. . This is a "graphical" shell, the name does not refer to a command-line "shell" interface. Original-Maintainer: Debian OLPC Python-Version: all chroot-autobuild/build/buildd/sucrose-0.88_0.88.1-5ubuntu1_all.deb: drwxr-xr-x root/root 0 2011-12-05 08:38 ./ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/doc/ drwxr-xr-x root/root 0 2011-12-05 08:39 ./usr/share/doc/sucrose-0.88/ -rw-r--r-- root/root 10406 2011-11-08 05:45 ./usr/share/doc/sucrose-0.88/copyright lrwxrwxrwx root/root 0 2011-12-05 08:39 ./usr/share/doc/sucrose-0.88/README -> ../sugar-session-0.88/README lrwxrwxrwx root/root 0 2011-12-05 08:39 ./usr/share/doc/sucrose-0.88/AUTHORS -> ../sugar-session-0.88/AUTHORS lrwxrwxrwx root/root 0 2011-12-05 08:39 ./usr/share/doc/sucrose-0.88/changelog.Debian.gz -> ../sugar-session-0.88/changelog.Debian.gz chroot-autobuild/build/buildd/sugar-session-0.88_0.88.1-5ubuntu1_all.deb: drwxr-xr-x root/root 0 2011-12-05 08:38 ./ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/doc/ drwxr-xr-x root/root 0 2011-12-05 08:39 ./usr/share/doc/sugar-session-0.88/ -rw-r--r-- root/root 10406 2011-11-08 05:45 ./usr/share/doc/sugar-session-0.88/copyright drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/menu/ -rw-r--r-- root/root 109 2011-12-05 08:38 ./usr/share/menu/sugar-session-0.88 drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/xsessions/ -rw-r--r-- root/root 88 2011-12-05 08:38 ./usr/share/xsessions/sugar.desktop drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/icons/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/icons/hicolor/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/icons/hicolor/scalable/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/icons/hicolor/scalable/apps/ -rw-r--r-- root/root 1166 2011-12-05 08:38 ./usr/share/icons/hicolor/scalable/apps/sugar-xo.svg drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/af/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/af/LC_MESSAGES/ -rw-r--r-- root/root 4595 2011-12-05 08:38 ./usr/share/locale/af/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/am/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/am/LC_MESSAGES/ -rw-r--r-- root/root 404 2011-12-05 08:38 ./usr/share/locale/am/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/ar/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/ar/LC_MESSAGES/ -rw-r--r-- root/root 21941 2011-12-05 08:38 ./usr/share/locale/ar/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/ay/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/ay/LC_MESSAGES/ -rw-r--r-- root/root 404 2011-12-05 08:38 ./usr/share/locale/ay/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/bg/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/bg/LC_MESSAGES/ -rw-r--r-- root/root 8004 2011-12-05 08:38 ./usr/share/locale/bg/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/bi/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/bi/LC_MESSAGES/ -rw-r--r-- root/root 407 2011-12-05 08:38 ./usr/share/locale/bi/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/bn_IN/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/bn_IN/LC_MESSAGES/ -rw-r--r-- root/root 7605 2011-12-05 08:38 ./usr/share/locale/bn_IN/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/bn/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/bn/LC_MESSAGES/ -rw-r--r-- root/root 7605 2011-12-05 08:38 ./usr/share/locale/bn/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/ca/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/ca/LC_MESSAGES/ -rw-r--r-- root/root 5190 2011-12-05 08:38 ./usr/share/locale/ca/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/cpp/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/cpp/LC_MESSAGES/ -rw-r--r-- root/root 407 2011-12-05 08:38 ./usr/share/locale/cpp/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/cs/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/cs/LC_MESSAGES/ -rw-r--r-- root/root 407 2011-12-05 08:38 ./usr/share/locale/cs/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/da/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/da/LC_MESSAGES/ -rw-r--r-- root/root 8362 2011-12-05 08:38 ./usr/share/locale/da/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/de/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/de/LC_MESSAGES/ -rw-r--r-- root/root 22299 2011-12-05 08:38 ./usr/share/locale/de/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/dz/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/dz/LC_MESSAGES/ -rw-r--r-- root/root 404 2011-12-05 08:38 ./usr/share/locale/dz/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/el/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/el/LC_MESSAGES/ -rw-r--r-- root/root 11383 2011-12-05 08:38 ./usr/share/locale/el/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/en/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/en/LC_MESSAGES/ -rw-r--r-- root/root 404 2011-12-05 08:38 ./usr/share/locale/en/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/es/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/es/LC_MESSAGES/ -rw-r--r-- root/root 18999 2011-12-05 08:38 ./usr/share/locale/es/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/fa_AF/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/fa_AF/LC_MESSAGES/ -rw-r--r-- root/root 6318 2011-12-05 08:38 ./usr/share/locale/fa_AF/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/fa/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/fa/LC_MESSAGES/ -rw-r--r-- root/root 6297 2011-12-05 08:38 ./usr/share/locale/fa/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/ff/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/ff/LC_MESSAGES/ -rw-r--r-- root/root 404 2011-12-05 08:38 ./usr/share/locale/ff/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/fil/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/fil/LC_MESSAGES/ -rw-r--r-- root/root 407 2011-12-05 08:38 ./usr/share/locale/fil/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/fr/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/fr/LC_MESSAGES/ -rw-r--r-- root/root 19135 2011-12-05 08:38 ./usr/share/locale/fr/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/gu/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/gu/LC_MESSAGES/ -rw-r--r-- root/root 404 2011-12-05 08:38 ./usr/share/locale/gu/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/ha/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/ha/LC_MESSAGES/ -rw-r--r-- root/root 665 2011-12-05 08:38 ./usr/share/locale/ha/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/he/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/he/LC_MESSAGES/ -rw-r--r-- root/root 407 2011-12-05 08:38 ./usr/share/locale/he/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/hi/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/hi/LC_MESSAGES/ -rw-r--r-- root/root 27554 2011-12-05 08:38 ./usr/share/locale/hi/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/ht/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/ht/LC_MESSAGES/ -rw-r--r-- root/root 3804 2011-12-05 08:38 ./usr/share/locale/ht/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/hu/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/hu/LC_MESSAGES/ -rw-r--r-- root/root 407 2011-12-05 08:38 ./usr/share/locale/hu/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/id/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/id/LC_MESSAGES/ -rw-r--r-- root/root 407 2011-12-05 08:38 ./usr/share/locale/id/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/ig/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/ig/LC_MESSAGES/ -rw-r--r-- root/root 703 2011-12-05 08:38 ./usr/share/locale/ig/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/is/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/is/LC_MESSAGES/ -rw-r--r-- root/root 404 2011-12-05 08:38 ./usr/share/locale/is/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/it/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/it/LC_MESSAGES/ -rw-r--r-- root/root 20271 2011-12-05 08:38 ./usr/share/locale/it/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/ja/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/ja/LC_MESSAGES/ -rw-r--r-- root/root 21413 2011-12-05 08:38 ./usr/share/locale/ja/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/km/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/km/LC_MESSAGES/ -rw-r--r-- root/root 4912 2011-12-05 08:38 ./usr/share/locale/km/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/ko/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/ko/LC_MESSAGES/ -rw-r--r-- root/root 404 2011-12-05 08:38 ./usr/share/locale/ko/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/kos/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/kos/LC_MESSAGES/ -rw-r--r-- root/root 481 2011-12-05 08:38 ./usr/share/locale/kos/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/mg/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/mg/LC_MESSAGES/ -rw-r--r-- root/root 4662 2011-12-05 08:38 ./usr/share/locale/mg/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/mi/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/mi/LC_MESSAGES/ -rw-r--r-- root/root 407 2011-12-05 08:38 ./usr/share/locale/mi/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/mk/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/mk/LC_MESSAGES/ -rw-r--r-- root/root 2053 2011-12-05 08:38 ./usr/share/locale/mk/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/ml/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/ml/LC_MESSAGES/ -rw-r--r-- root/root 404 2011-12-05 08:38 ./usr/share/locale/ml/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/mn/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/mn/LC_MESSAGES/ -rw-r--r-- root/root 13013 2011-12-05 08:38 ./usr/share/locale/mn/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/mr/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/mr/LC_MESSAGES/ -rw-r--r-- root/root 10264 2011-12-05 08:38 ./usr/share/locale/mr/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/ms/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/ms/LC_MESSAGES/ -rw-r--r-- root/root 407 2011-12-05 08:38 ./usr/share/locale/ms/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/mvo/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/mvo/LC_MESSAGES/ -rw-r--r-- root/root 407 2011-12-05 08:38 ./usr/share/locale/mvo/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/nb/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/nb/LC_MESSAGES/ -rw-r--r-- root/root 5142 2011-12-05 08:38 ./usr/share/locale/nb/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/ne/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/ne/LC_MESSAGES/ -rw-r--r-- root/root 22018 2011-12-05 08:38 ./usr/share/locale/ne/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/nl/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/nl/LC_MESSAGES/ -rw-r--r-- root/root 18842 2011-12-05 08:38 ./usr/share/locale/nl/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/pa/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/pa/LC_MESSAGES/ -rw-r--r-- root/root 404 2011-12-05 08:38 ./usr/share/locale/pa/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/pap/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/pap/LC_MESSAGES/ -rw-r--r-- root/root 2815 2011-12-05 08:38 ./usr/share/locale/pap/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/pis/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/pis/LC_MESSAGES/ -rw-r--r-- root/root 407 2011-12-05 08:38 ./usr/share/locale/pis/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/pl/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/pl/LC_MESSAGES/ -rw-r--r-- root/root 4125 2011-12-05 08:38 ./usr/share/locale/pl/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/ps/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/ps/LC_MESSAGES/ -rw-r--r-- root/root 5599 2011-12-05 08:38 ./usr/share/locale/ps/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/pt_BR/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/pt_BR/LC_MESSAGES/ -rw-r--r-- root/root 5653 2011-12-05 08:38 ./usr/share/locale/pt_BR/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/pt/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/pt/LC_MESSAGES/ -rw-r--r-- root/root 19160 2011-12-05 08:38 ./usr/share/locale/pt/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/qu/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/qu/LC_MESSAGES/ -rw-r--r-- root/root 404 2011-12-05 08:38 ./usr/share/locale/qu/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/ro/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/ro/LC_MESSAGES/ -rw-r--r-- root/root 2069 2011-12-05 08:38 ./usr/share/locale/ro/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/ru/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/ru/LC_MESSAGES/ -rw-r--r-- root/root 6468 2011-12-05 08:38 ./usr/share/locale/ru/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/rw/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/rw/LC_MESSAGES/ -rw-r--r-- root/root 8519 2011-12-05 08:38 ./usr/share/locale/rw/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/sd/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/sd/LC_MESSAGES/ -rw-r--r-- root/root 407 2011-12-05 08:38 ./usr/share/locale/sd/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/si/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/si/LC_MESSAGES/ -rw-r--r-- root/root 17339 2011-12-05 08:38 ./usr/share/locale/si/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/sk/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/sk/LC_MESSAGES/ -rw-r--r-- root/root 407 2011-12-05 08:38 ./usr/share/locale/sk/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/sl/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/sl/LC_MESSAGES/ -rw-r--r-- root/root 15754 2011-12-05 08:38 ./usr/share/locale/sl/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/sq/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/sq/LC_MESSAGES/ -rw-r--r-- root/root 7455 2011-12-05 08:38 ./usr/share/locale/sq/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/sv/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/sv/LC_MESSAGES/ -rw-r--r-- root/root 18787 2011-12-05 08:38 ./usr/share/locale/sv/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/sw/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/sw/LC_MESSAGES/ -rw-r--r-- root/root 4478 2011-12-05 08:38 ./usr/share/locale/sw/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/ta/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/ta/LC_MESSAGES/ -rw-r--r-- root/root 26784 2011-12-05 08:38 ./usr/share/locale/ta/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/te/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/te/LC_MESSAGES/ -rw-r--r-- root/root 11465 2011-12-05 08:38 ./usr/share/locale/te/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/th/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/th/LC_MESSAGES/ -rw-r--r-- root/root 404 2011-12-05 08:38 ./usr/share/locale/th/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/tpi/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/tpi/LC_MESSAGES/ -rw-r--r-- root/root 407 2011-12-05 08:38 ./usr/share/locale/tpi/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/tr/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/tr/LC_MESSAGES/ -rw-r--r-- root/root 11991 2011-12-05 08:38 ./usr/share/locale/tr/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/tvl/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/tvl/LC_MESSAGES/ -rw-r--r-- root/root 404 2011-12-05 08:38 ./usr/share/locale/tvl/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/tzo/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/tzo/LC_MESSAGES/ -rw-r--r-- root/root 404 2011-12-05 08:38 ./usr/share/locale/tzo/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/ug/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/ug/LC_MESSAGES/ -rw-r--r-- root/root 407 2011-12-05 08:38 ./usr/share/locale/ug/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/ur/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/ur/LC_MESSAGES/ -rw-r--r-- root/root 9810 2011-12-05 08:38 ./usr/share/locale/ur/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/vi/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/vi/LC_MESSAGES/ -rw-r--r-- root/root 21250 2011-12-05 08:38 ./usr/share/locale/vi/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/wa/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/wa/LC_MESSAGES/ -rw-r--r-- root/root 407 2011-12-05 08:38 ./usr/share/locale/wa/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/yo/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/yo/LC_MESSAGES/ -rw-r--r-- root/root 748 2011-12-05 08:38 ./usr/share/locale/yo/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/zh_CN/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/zh_CN/LC_MESSAGES/ -rw-r--r-- root/root 5128 2011-12-05 08:38 ./usr/share/locale/zh_CN/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/zh_TW/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/locale/zh_TW/LC_MESSAGES/ -rw-r--r-- root/root 18798 2011-12-05 08:38 ./usr/share/locale/zh_TW/LC_MESSAGES/sugar.mo drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/mime/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/mime/packages/ -rw-r--r-- root/root 397 2011-12-05 08:38 ./usr/share/mime/packages/sugar.xml drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/sugar/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/sugar/data/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/sugar/data/icons/ -rw-r--r-- root/root 1195 2011-12-05 08:38 ./usr/share/sugar/data/icons/module-about_me.svg -rw-r--r-- root/root 1086 2011-12-05 08:38 ./usr/share/sugar/data/icons/module-about_my_computer.svg -rw-r--r-- root/root 3063 2011-12-05 08:38 ./usr/share/sugar/data/icons/module-date_and_time.svg -rw-r--r-- root/root 1095 2011-12-05 08:38 ./usr/share/sugar/data/icons/module-frame.svg -rw-r--r-- root/root 6510 2011-12-05 08:38 ./usr/share/sugar/data/icons/module-keyboard.svg -rw-r--r-- root/root 9707 2011-12-05 08:38 ./usr/share/sugar/data/icons/module-language.svg -rw-r--r-- root/root 1009 2011-12-05 08:38 ./usr/share/sugar/data/icons/module-modemconfiguration.svg -rw-r--r-- root/root 1627 2011-12-05 08:38 ./usr/share/sugar/data/icons/module-network.svg -rw-r--r-- root/root 972 2011-12-05 08:38 ./usr/share/sugar/data/icons/module-power.svg -rw-r--r-- root/root 1348 2011-12-05 08:38 ./usr/share/sugar/data/icons/module-updater.svg -rw-r--r-- root/root 669 2011-12-05 08:38 ./usr/share/sugar/data/activities.defaults -rw-r--r-- root/root 80 2011-12-05 08:38 ./usr/share/sugar/data/kbdconfig -rw-r--r-- root/root 1226 2011-12-05 08:38 ./usr/share/sugar/data/mime.defaults -rw-r--r-- root/root 17987 2011-12-05 08:38 ./usr/share/sugar/data/GPLv2 -rw-r--r-- root/root 200 2011-12-05 08:38 ./usr/share/sugar/data/sugar-72.gtkrc -rw-r--r-- root/root 201 2011-12-05 08:38 ./usr/share/sugar/data/sugar-100.gtkrc drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/sugar/extensions/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/sugar/extensions/cpsection/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/sugar/extensions/cpsection/aboutme/ -rw-r--r-- root/root 988 2011-12-05 08:38 ./usr/share/sugar/extensions/cpsection/aboutme/__init__.py -rw-r--r-- root/root 4101 2011-12-05 08:38 ./usr/share/sugar/extensions/cpsection/aboutme/model.py -rw-r--r-- root/root 7951 2011-12-05 08:38 ./usr/share/sugar/extensions/cpsection/aboutme/view.py drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/sugar/extensions/cpsection/aboutcomputer/ -rw-r--r-- root/root 854 2011-12-05 08:38 ./usr/share/sugar/extensions/cpsection/aboutcomputer/__init__.py -rw-r--r-- root/root 4056 2011-12-05 08:38 ./usr/share/sugar/extensions/cpsection/aboutcomputer/model.py -rw-r--r-- root/root 9051 2011-12-05 08:38 ./usr/share/sugar/extensions/cpsection/aboutcomputer/view.py drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/sugar/extensions/cpsection/datetime/ -rw-r--r-- root/root 838 2011-12-05 08:38 ./usr/share/sugar/extensions/cpsection/datetime/__init__.py -rw-r--r-- root/root 2867 2011-12-05 08:38 ./usr/share/sugar/extensions/cpsection/datetime/model.py -rw-r--r-- root/root 5274 2011-12-05 08:38 ./usr/share/sugar/extensions/cpsection/datetime/view.py drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/sugar/extensions/cpsection/frame/ -rw-r--r-- root/root 821 2011-12-05 08:38 ./usr/share/sugar/extensions/cpsection/frame/__init__.py -rw-r--r-- root/root 2144 2011-12-05 08:38 ./usr/share/sugar/extensions/cpsection/frame/model.py -rw-r--r-- root/root 9395 2011-12-05 08:38 ./usr/share/sugar/extensions/cpsection/frame/view.py drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/sugar/extensions/cpsection/keyboard/ -rw-r--r-- root/root 831 2011-12-05 08:38 ./usr/share/sugar/extensions/cpsection/keyboard/__init__.py -rw-r--r-- root/root 6204 2011-12-05 08:38 ./usr/share/sugar/extensions/cpsection/keyboard/model.py -rw-r--r-- root/root 16591 2011-12-05 08:38 ./usr/share/sugar/extensions/cpsection/keyboard/view.py drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/sugar/extensions/cpsection/language/ -rw-r--r-- root/root 831 2011-12-05 08:38 ./usr/share/sugar/extensions/cpsection/language/__init__.py -rw-r--r-- root/root 5094 2011-12-05 08:38 ./usr/share/sugar/extensions/cpsection/language/model.py -rw-r--r-- root/root 9780 2011-12-05 08:38 ./usr/share/sugar/extensions/cpsection/language/view.py drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/sugar/extensions/cpsection/modemconfiguration/ -rw-r--r-- root/root 886 2011-12-05 08:38 ./usr/share/sugar/extensions/cpsection/modemconfiguration/__init__.py -rw-r--r-- root/root 2276 2011-12-05 08:38 ./usr/share/sugar/extensions/cpsection/modemconfiguration/model.py -rw-r--r-- root/root 8167 2011-12-05 08:38 ./usr/share/sugar/extensions/cpsection/modemconfiguration/view.py drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/sugar/extensions/cpsection/network/ -rw-r--r-- root/root 897 2011-12-05 08:38 ./usr/share/sugar/extensions/cpsection/network/__init__.py -rw-r--r-- root/root 4563 2011-12-05 08:38 ./usr/share/sugar/extensions/cpsection/network/model.py -rw-r--r-- root/root 9718 2011-12-05 08:38 ./usr/share/sugar/extensions/cpsection/network/view.py drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/sugar/extensions/cpsection/power/ -rw-r--r-- root/root 889 2011-12-05 08:38 ./usr/share/sugar/extensions/cpsection/power/__init__.py -rw-r--r-- root/root 3607 2011-12-05 08:38 ./usr/share/sugar/extensions/cpsection/power/model.py -rw-r--r-- root/root 7044 2011-12-05 08:38 ./usr/share/sugar/extensions/cpsection/power/view.py drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/sugar/extensions/cpsection/updater/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/sugar/extensions/cpsection/updater/backends/ -rw-r--r-- root/root 5451 2011-12-05 08:38 ./usr/share/sugar/extensions/cpsection/updater/backends/aslo.py -rw-r--r-- root/root 753 2011-12-05 08:38 ./usr/share/sugar/extensions/cpsection/updater/backends/__init__.py -rw-r--r-- root/root 889 2011-12-05 08:38 ./usr/share/sugar/extensions/cpsection/updater/__init__.py -rw-r--r-- root/root 11981 2011-12-05 08:38 ./usr/share/sugar/extensions/cpsection/updater/model.py -rw-r--r-- root/root 13897 2011-12-05 08:38 ./usr/share/sugar/extensions/cpsection/updater/view.py -rw-r--r-- root/root 0 2011-12-05 08:38 ./usr/share/sugar/extensions/cpsection/__init__.py drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/sugar/extensions/deviceicon/ -rw-r--r-- root/root 0 2011-12-05 08:38 ./usr/share/sugar/extensions/deviceicon/__init__.py -rw-r--r-- root/root 9058 2011-12-05 08:38 ./usr/share/sugar/extensions/deviceicon/battery.py -rw-r--r-- root/root 41334 2011-12-05 08:38 ./usr/share/sugar/extensions/deviceicon/network.py -rw-r--r-- root/root 7208 2011-12-05 08:38 ./usr/share/sugar/extensions/deviceicon/speaker.py -rw-r--r-- root/root 3936 2011-12-05 08:38 ./usr/share/sugar/extensions/deviceicon/volume.py drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/sugar/extensions/globalkey/ -rw-r--r-- root/root 0 2011-12-05 08:38 ./usr/share/sugar/extensions/globalkey/__init__.py -rw-r--r-- root/root 3458 2011-12-05 08:38 ./usr/share/sugar/extensions/globalkey/screenshot.py -rw-r--r-- root/root 1068 2011-12-05 08:38 ./usr/share/sugar/extensions/globalkey/viewsource.py drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/gconf/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/gconf/schemas/ -rw-r--r-- root/root 65904 2011-12-05 08:38 ./usr/share/gconf/schemas/sugar.schemas drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/pyshared-data/ -rw-r--r-- root/root 2488 2011-12-05 08:38 ./usr/share/pyshared-data/sugar-session-0.88 drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/bin/ -rwxr-xr-x root/root 1394 2011-12-05 08:38 ./usr/bin/sugar -rwxr-xr-x root/root 8707 2011-12-05 08:38 ./usr/bin/sugar-session drwxr-xr-x root/root 0 2011-12-05 08:38 ./etc/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./etc/dbus-1/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./etc/dbus-1/system.d/ -rw-r--r-- root/root 1168 2011-12-05 08:38 ./etc/dbus-1/system.d/nm-user-settings.conf lrwxrwxrwx root/root 0 2011-12-05 08:39 ./usr/share/doc/sugar-session-0.88/README -> ../python-jarabe-0.88/README lrwxrwxrwx root/root 0 2011-12-05 08:39 ./usr/share/doc/sugar-session-0.88/AUTHORS -> ../python-jarabe-0.88/AUTHORS lrwxrwxrwx root/root 0 2011-12-05 08:39 ./usr/share/doc/sugar-session-0.88/changelog.Debian.gz -> ../python-jarabe-0.88/changelog.Debian.gz chroot-autobuild/build/buildd/sugar-emulator-0.88_0.88.1-5ubuntu1_all.deb: drwxr-xr-x root/root 0 2011-12-05 08:38 ./ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/doc/ drwxr-xr-x root/root 0 2011-12-05 08:39 ./usr/share/doc/sugar-emulator-0.88/ -rw-r--r-- root/root 10406 2011-11-08 05:45 ./usr/share/doc/sugar-emulator-0.88/copyright drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/menu/ -rw-r--r-- root/root 136 2011-12-05 08:38 ./usr/share/menu/sugar-emulator-0.88 drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/applications/ -rw-r--r-- root/root 241 2011-11-08 05:45 ./usr/share/applications/sugar-emulator.desktop drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/bin/ -rwxr-xr-x root/root 307 2011-12-05 08:38 ./usr/bin/sugar-emulator lrwxrwxrwx root/root 0 2011-12-05 08:39 ./usr/share/doc/sugar-emulator-0.88/README -> ../python-jarabe-0.88/README lrwxrwxrwx root/root 0 2011-12-05 08:39 ./usr/share/doc/sugar-emulator-0.88/AUTHORS -> ../python-jarabe-0.88/AUTHORS lrwxrwxrwx root/root 0 2011-12-05 08:39 ./usr/share/doc/sugar-emulator-0.88/changelog.Debian.gz -> ../python-jarabe-0.88/changelog.Debian.gz chroot-autobuild/build/buildd/sugar-tools-0.88_0.88.1-5ubuntu1_all.deb: drwxr-xr-x root/root 0 2011-12-05 08:38 ./ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/doc/ drwxr-xr-x root/root 0 2011-12-05 08:39 ./usr/share/doc/sugar-tools-0.88/ -rw-r--r-- root/root 10406 2011-11-08 05:45 ./usr/share/doc/sugar-tools-0.88/copyright drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/bin/ -rwxr-xr-x root/root 813 2011-12-05 08:38 ./usr/bin/sugar-activity -rwxr-xr-x root/root 886 2011-12-05 08:38 ./usr/bin/sugar-control-panel -rwxr-xr-x root/root 457 2011-12-05 08:38 ./usr/bin/sugar-install-bundle -rwxr-xr-x root/root 2612 2011-12-05 08:38 ./usr/bin/sugar-launch -rwxr-xr-x root/root 4603 2011-12-05 08:38 ./usr/bin/sugar-ui-check lrwxrwxrwx root/root 0 2011-12-05 08:39 ./usr/share/doc/sugar-tools-0.88/README -> ../python-jarabe-0.88/README lrwxrwxrwx root/root 0 2011-12-05 08:39 ./usr/share/doc/sugar-tools-0.88/AUTHORS -> ../python-jarabe-0.88/AUTHORS lrwxrwxrwx root/root 0 2011-12-05 08:39 ./usr/share/doc/sugar-tools-0.88/changelog.Debian.gz -> ../python-jarabe-0.88/changelog.Debian.gz chroot-autobuild/build/buildd/python-jarabe-0.88_0.88.1-5ubuntu1_all.deb: drwxr-xr-x root/root 0 2011-12-05 08:38 ./ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/doc/ drwxr-xr-x root/root 0 2011-12-05 08:39 ./usr/share/doc/python-jarabe-0.88/ -rw-r--r-- root/root 1084 2010-05-19 10:12 ./usr/share/doc/python-jarabe-0.88/README -rw-r--r-- root/root 542 2010-02-20 16:47 ./usr/share/doc/python-jarabe-0.88/AUTHORS -rw-r--r-- root/root 10406 2011-11-08 05:45 ./usr/share/doc/python-jarabe-0.88/copyright -rw-r--r-- root/root 1577 2011-12-05 08:39 ./usr/share/doc/python-jarabe-0.88/changelog.Debian.gz drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/pyshared/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/pyshared/jarabe/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/pyshared/jarabe/controlpanel/ -rw-r--r-- root/root 745 2011-12-05 08:38 ./usr/share/pyshared/jarabe/controlpanel/__init__.py -rw-r--r-- root/root 5973 2011-12-05 08:38 ./usr/share/pyshared/jarabe/controlpanel/cmd.py -rw-r--r-- root/root 16065 2011-12-05 08:38 ./usr/share/pyshared/jarabe/controlpanel/gui.py -rw-r--r-- root/root 2797 2011-12-05 08:38 ./usr/share/pyshared/jarabe/controlpanel/inlinealert.py -rw-r--r-- root/root 1782 2011-12-05 08:38 ./usr/share/pyshared/jarabe/controlpanel/sectionview.py -rw-r--r-- root/root 5005 2011-12-05 08:38 ./usr/share/pyshared/jarabe/controlpanel/toolbar.py drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/pyshared/jarabe/desktop/ -rw-r--r-- root/root 745 2011-12-05 08:38 ./usr/share/pyshared/jarabe/desktop/__init__.py -rw-r--r-- root/root 17351 2011-12-05 08:38 ./usr/share/pyshared/jarabe/desktop/activitieslist.py -rw-r--r-- root/root 25521 2011-12-05 08:38 ./usr/share/pyshared/jarabe/desktop/favoritesview.py -rw-r--r-- root/root 17965 2011-12-05 08:38 ./usr/share/pyshared/jarabe/desktop/favoriteslayout.py -rw-r--r-- root/root 3375 2011-12-05 08:38 ./usr/share/pyshared/jarabe/desktop/friendview.py -rw-r--r-- root/root 7140 2011-12-05 08:38 ./usr/share/pyshared/jarabe/desktop/grid.py -rw-r--r-- root/root 3285 2011-12-05 08:38 ./usr/share/pyshared/jarabe/desktop/groupbox.py -rw-r--r-- root/root 10375 2011-12-05 08:38 ./usr/share/pyshared/jarabe/desktop/homebox.py -rw-r--r-- root/root 6543 2011-12-05 08:38 ./usr/share/pyshared/jarabe/desktop/homewindow.py -rw-r--r-- root/root 10622 2011-12-05 08:38 ./usr/share/pyshared/jarabe/desktop/keydialog.py -rw-r--r-- root/root 45465 2011-12-05 08:38 ./usr/share/pyshared/jarabe/desktop/meshbox.py -rw-r--r-- root/root 1159 2011-12-05 08:38 ./usr/share/pyshared/jarabe/desktop/myicon.py -rw-r--r-- root/root 4277 2011-12-05 08:38 ./usr/share/pyshared/jarabe/desktop/schoolserver.py -rw-r--r-- root/root 3657 2011-12-05 08:38 ./usr/share/pyshared/jarabe/desktop/snowflakelayout.py -rw-r--r-- root/root 2916 2011-12-05 08:38 ./usr/share/pyshared/jarabe/desktop/spreadlayout.py -rw-r--r-- root/root 3152 2011-12-05 08:38 ./usr/share/pyshared/jarabe/desktop/transitionbox.py drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/pyshared/jarabe/frame/ -rw-r--r-- root/root 889 2011-12-05 08:38 ./usr/share/pyshared/jarabe/frame/__init__.py -rw-r--r-- root/root 32328 2011-12-05 08:38 ./usr/share/pyshared/jarabe/frame/activitiestray.py -rw-r--r-- root/root 5400 2011-12-05 08:38 ./usr/share/pyshared/jarabe/frame/clipboard.py -rw-r--r-- root/root 6238 2011-12-05 08:38 ./usr/share/pyshared/jarabe/frame/clipboardicon.py -rw-r--r-- root/root 9271 2011-12-05 08:38 ./usr/share/pyshared/jarabe/frame/clipboardmenu.py -rw-r--r-- root/root 4257 2011-12-05 08:38 ./usr/share/pyshared/jarabe/frame/clipboardobject.py -rw-r--r-- root/root 3982 2011-12-05 08:38 ./usr/share/pyshared/jarabe/frame/clipboardpanelwindow.py -rw-r--r-- root/root 7959 2011-12-05 08:38 ./usr/share/pyshared/jarabe/frame/clipboardtray.py -rw-r--r-- root/root 2027 2011-12-05 08:38 ./usr/share/pyshared/jarabe/frame/devicestray.py -rw-r--r-- root/root 1335 2011-12-05 08:38 ./usr/share/pyshared/jarabe/frame/frameinvoker.py -rw-r--r-- root/root 4734 2011-12-05 08:38 ./usr/share/pyshared/jarabe/frame/friendstray.py -rw-r--r-- root/root 5439 2011-12-05 08:38 ./usr/share/pyshared/jarabe/frame/eventarea.py -rw-r--r-- root/root 11162 2011-12-05 08:38 ./usr/share/pyshared/jarabe/frame/frame.py -rw-r--r-- root/root 3495 2011-12-05 08:38 ./usr/share/pyshared/jarabe/frame/notification.py -rw-r--r-- root/root 4336 2011-12-05 08:38 ./usr/share/pyshared/jarabe/frame/framewindow.py -rw-r--r-- root/root 3401 2011-12-05 08:38 ./usr/share/pyshared/jarabe/frame/zoomtoolbar.py drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/pyshared/jarabe/journal/ -rw-r--r-- root/root 746 2011-12-05 08:38 ./usr/share/pyshared/jarabe/journal/__init__.py -rw-r--r-- root/root 4043 2011-12-05 08:38 ./usr/share/pyshared/jarabe/journal/detailview.py -rw-r--r-- root/root 15425 2011-12-05 08:38 ./usr/share/pyshared/jarabe/journal/expandedentry.py -rw-r--r-- root/root 12777 2011-12-05 08:38 ./usr/share/pyshared/jarabe/journal/journalactivity.py -rw-r--r-- root/root 3049 2011-12-05 08:38 ./usr/share/pyshared/jarabe/journal/journalentrybundle.py -rw-r--r-- root/root 17150 2011-12-05 08:38 ./usr/share/pyshared/jarabe/journal/journaltoolbox.py -rw-r--r-- root/root 2232 2011-12-05 08:38 ./usr/share/pyshared/jarabe/journal/keepicon.py -rw-r--r-- root/root 6382 2011-12-05 08:38 ./usr/share/pyshared/jarabe/journal/listmodel.py -rw-r--r-- root/root 23632 2011-12-05 08:38 ./usr/share/pyshared/jarabe/journal/listview.py -rw-r--r-- root/root 9110 2011-12-05 08:38 ./usr/share/pyshared/jarabe/journal/misc.py -rw-r--r-- root/root 3557 2011-12-05 08:38 ./usr/share/pyshared/jarabe/journal/modalalert.py -rw-r--r-- root/root 17725 2011-12-05 08:38 ./usr/share/pyshared/jarabe/journal/model.py -rw-r--r-- root/root 6736 2011-12-05 08:38 ./usr/share/pyshared/jarabe/journal/objectchooser.py -rw-r--r-- root/root 8785 2011-12-05 08:38 ./usr/share/pyshared/jarabe/journal/palettes.py -rw-r--r-- root/root 6182 2011-12-05 08:38 ./usr/share/pyshared/jarabe/journal/volumestoolbar.py drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/pyshared/jarabe/model/ -rw-r--r-- root/root 745 2011-12-05 08:38 ./usr/share/pyshared/jarabe/model/__init__.py -rw-r--r-- root/root 6553 2011-12-05 08:38 ./usr/share/pyshared/jarabe/model/buddy.py -rw-r--r-- root/root 16729 2011-12-05 08:38 ./usr/share/pyshared/jarabe/model/bundleregistry.py -rw-r--r-- root/root 14445 2011-12-05 08:38 ./usr/share/pyshared/jarabe/model/filetransfer.py -rw-r--r-- root/root 3723 2011-12-05 08:38 ./usr/share/pyshared/jarabe/model/friends.py -rw-r--r-- root/root 4063 2011-12-05 08:38 ./usr/share/pyshared/jarabe/model/invites.py -rw-r--r-- root/root 8497 2011-12-05 08:38 ./usr/share/pyshared/jarabe/model/olpcmesh.py -rw-r--r-- root/root 4029 2011-12-05 08:38 ./usr/share/pyshared/jarabe/model/owner.py -rw-r--r-- root/root 1549 2011-12-05 08:38 ./usr/share/pyshared/jarabe/model/mimeregistry.py -rw-r--r-- root/root 10728 2011-12-05 08:38 ./usr/share/pyshared/jarabe/model/neighborhood.py -rw-r--r-- root/root 25006 2011-12-05 08:38 ./usr/share/pyshared/jarabe/model/network.py -rw-r--r-- root/root 3293 2011-12-05 08:38 ./usr/share/pyshared/jarabe/model/notifications.py -rw-r--r-- root/root 22423 2011-12-05 08:38 ./usr/share/pyshared/jarabe/model/shell.py -rw-r--r-- root/root 1532 2011-12-05 08:38 ./usr/share/pyshared/jarabe/model/screen.py -rw-r--r-- root/root 2814 2011-12-05 08:38 ./usr/share/pyshared/jarabe/model/session.py -rw-r--r-- root/root 1656 2011-12-05 08:38 ./usr/share/pyshared/jarabe/model/sound.py drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/pyshared/jarabe/view/ -rw-r--r-- root/root 745 2011-12-05 08:38 ./usr/share/pyshared/jarabe/view/__init__.py -rw-r--r-- root/root 2349 2011-12-05 08:38 ./usr/share/pyshared/jarabe/view/buddyicon.py -rw-r--r-- root/root 5864 2011-12-05 08:38 ./usr/share/pyshared/jarabe/view/buddymenu.py -rw-r--r-- root/root 8747 2011-12-05 08:38 ./usr/share/pyshared/jarabe/view/keyhandler.py -rw-r--r-- root/root 7149 2011-12-05 08:38 ./usr/share/pyshared/jarabe/view/launcher.py -rw-r--r-- root/root 9273 2011-12-05 08:38 ./usr/share/pyshared/jarabe/view/palettes.py -rw-r--r-- root/root 6842 2011-12-05 08:38 ./usr/share/pyshared/jarabe/view/pulsingicon.py -rw-r--r-- root/root 4670 2011-12-05 08:38 ./usr/share/pyshared/jarabe/view/service.py -rw-r--r-- root/root 5176 2011-12-05 08:38 ./usr/share/pyshared/jarabe/view/tabbinghandler.py -rw-r--r-- root/root 16655 2011-12-05 08:38 ./usr/share/pyshared/jarabe/view/viewsource.py drwxr-xr-x root/root 0 2011-12-05 08:39 ./usr/share/pyshared/jarabe/intro/ -rw-r--r-- root/root 4273 2011-12-05 08:38 ./usr/share/pyshared/jarabe/intro/default-picture.png -rw-r--r-- root/root 584 2011-12-05 08:38 ./usr/share/pyshared/jarabe/intro/__init__.py -rw-r--r-- root/root 1591 2011-12-05 08:38 ./usr/share/pyshared/jarabe/intro/colorpicker.py -rw-r--r-- root/root 9335 2011-12-05 08:38 ./usr/share/pyshared/jarabe/intro/window.py drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/pyshared/jarabe/util/ drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/pyshared/jarabe/util/telepathy/ -rw-r--r-- root/root 799 2011-12-05 08:38 ./usr/share/pyshared/jarabe/util/telepathy/__init__.py -rw-r--r-- root/root 3807 2011-12-05 08:38 ./usr/share/pyshared/jarabe/util/telepathy/connection_watcher.py -rw-r--r-- root/root 789 2011-12-05 08:38 ./usr/share/pyshared/jarabe/util/__init__.py -rw-r--r-- root/root 5412 2011-12-05 08:38 ./usr/share/pyshared/jarabe/util/emulator.py -rw-r--r-- root/root 1001 2011-12-05 08:38 ./usr/share/pyshared/jarabe/config.py -rw-r--r-- root/root 1030 2011-12-05 08:38 ./usr/share/pyshared/jarabe/__init__.py drwxr-xr-x root/root 0 2011-12-05 08:38 ./usr/share/pyshared-data/ -rw-r--r-- root/root 4909 2011-12-05 08:38 ./usr/share/pyshared-data/python-jarabe-0.88 sugar-0.88_0.88.1-5ubuntu1_i386.changes: Format: 1.8 Date: Mon, 05 Dec 2011 02:24:52 -0600 Source: sugar-0.88 Binary: sucrose-0.88 sugar-session-0.88 sugar-emulator-0.88 sugar-tools-0.88 python-jarabe-0.88 Architecture: all Version: 0.88.1-5ubuntu1 Distribution: precise Urgency: low Maintainer: Ubuntu/i386 Build Daemon Changed-By: Micah Gersten Description: python-jarabe-0.88 - Sugar graphical shell - library sucrose-0.88 - Sugar graphical shell - Sucrose 0.88 sugar-emulator-0.88 - Sugar graphical shell - emulator sugar-session-0.88 - Sugar graphical shell - window manager sugar-tools-0.88 - Sugar graphical shell - window manager Changes: sugar-0.88 (0.88.1-5ubuntu1) precise; urgency=low . * Merge from Debian testing. Remaining changes: - debian/patches/display_sugar_instead_of_zephyr.patch: + Display 'Sugar inside Xephyr' instead of 'Xephyr on'. - debian/rules: Drop browse activity as a dependency. Checksums-Sha1: 1c79e30b32450b4fbbc9a84d7508a5233596e8f6 4396 sucrose-0.88_0.88.1-5ubuntu1_all.deb aa35e283e7eaa7df2e55ead52155da6840b821b7 264232 sugar-session-0.88_0.88.1-5ubuntu1_all.deb e99c0d6fdda96a765b821eb73fa7ee054ef985f7 5128 sugar-emulator-0.88_0.88.1-5ubuntu1_all.deb fe87c7a331db60df6037e45755bbc5e07120deff 6842 sugar-tools-0.88_0.88.1-5ubuntu1_all.deb bb7cee35786eefe11fb0271cbab9b4ca49593b38 139134 python-jarabe-0.88_0.88.1-5ubuntu1_all.deb Checksums-Sha256: 07e3863d76784e5ef232db55509811dd020962cfadb37bd76ac8be4e5ad0bd62 4396 sucrose-0.88_0.88.1-5ubuntu1_all.deb 7563086125e2390769cd1555ddb0f2cdee333ae30f71516946b8fd02592530fe 264232 sugar-session-0.88_0.88.1-5ubuntu1_all.deb 123bb2501b3a92f5d9dbc952c39e5ed13adcdd42390cd2600645a52ab33c57a0 5128 sugar-emulator-0.88_0.88.1-5ubuntu1_all.deb c5ce3bdc71df76630b2407075d0703334e59b6f75caf74125ee510076af2ef02 6842 sugar-tools-0.88_0.88.1-5ubuntu1_all.deb 614cf6ae3d843cc148de1b0c27f8ae698d81c57ecf20a47cd22254520fb4689a 139134 python-jarabe-0.88_0.88.1-5ubuntu1_all.deb Files: 0993d80f19369fdd737913a6990fd5fd 4396 x11 optional sucrose-0.88_0.88.1-5ubuntu1_all.deb 08a9443443268a1754c4c4acda91e431 264232 x11 optional sugar-session-0.88_0.88.1-5ubuntu1_all.deb 0501049b1ddc155f7c171c22ac269d10 5128 x11 optional sugar-emulator-0.88_0.88.1-5ubuntu1_all.deb 22c54fc42ba44d47d137bfee920e085e 6842 x11 optional sugar-tools-0.88_0.88.1-5ubuntu1_all.deb 5f3f1398fb76c99090683449ef795453 139134 python optional python-jarabe-0.88_0.88.1-5ubuntu1_all.deb Original-Maintainer: Debian OLPC ****************************************************************************** Built successfully Purging chroot-autobuild/build/buildd/sugar-0.88-0.88.1 ------------------------------------------------------------------------------ /usr/bin/sudo dpkg --purge groff-base python-gobject-dev libavahi-common3 libxfixes-dev libx11-data m4 libgconf2-dev fontconfig-config gettext file zlib1g-dev libhtml-parser-perl libhttp-cookies-perl libcairo2 x11-common libcairo-gobject2 libx11-dev gir1.2-gconf-2.0 libxi6 libatk1.0-data libgettextpo0 automake python-scour libnet-ssleay-perl libxcursor1 libencode-locale-perl python-gtk2 x11proto-input-dev libexpat1-dev libgdk-pixbuf2.0-0 libjasper1 libpixman-1-dev libxcomposite-dev libfontconfig1 libdbus-glib-1-2 libxcb-shm0-dev python-cairo libx11-6 liblwp-mediatypes-perl gir1.2-gdkpixbuf-2.0 xtrans-dev x11proto-randr-dev psmisc libhttp-message-perl xorg-sgml-doctools libxinerama-dev libglib2.0-data libxdamage1 libxml2-utils libdbus-1-dev libhtml-tree-perl libgdk-pixbuf2.0-dev libglib2.0-dev gconf2 libhtml-tagset-perl libxml2 dbus x11proto-xext-dev libjpeg8 pkg-config libthai-data libice6 intltool-debian python2.7-dev libavahi-client3 libxrender1 libfontconfig1-dev libio-socket-ssl-perl libpython2.7 libxrandr-dev libxext-dev liblwp-protocol-https-perl libcups2 libxau-dev libdatrie1 libxrender-dev gir1.2-atk-1.0 libpng12-dev libavahi-common-data libxft2 x11proto-render-dev libxext6 libpipeline1 libxinerama1 libxdamage-dev libsm-dev gconf2-common libxdmcp-dev ttf-dejavu-core libcairo2-dev gir1.2-freedesktop fontconfig libxcb-render0-dev liburi-perl devscripts autotools-dev libdb4.8 dh-translations libcroco3 python-support libpopt0 gir1.2-glib-2.0 libfreetype6 libffi-dev libice-dev libatk1.0-0 libfile-listing-perl x11proto-fixes-dev libfreetype6-dev libgtk2.0-0 libhttp-negotiate-perl python2.7 x11proto-damage-dev libxcb1 gir1.2-pango-1.0 html2text libxrandr2 debhelper libpthread-stubs0 libthai0 python libmagic1 python-gobject libtiff4 libxcb-shm0 libexpat1 libssl-dev bsdmainutils libxau6 libpango1.0-dev libxcursor-dev libxcomposite1 x11proto-composite-dev libgconf2-4 mime-support x11proto-core-dev intltool libxcb1-dev libxi-dev libwww-perl shared-mime-info libxdmcp6 libxfixes3 python-gtk2-dev libgtk2.0-dev po-debconf libnet-http-perl libatk1.0-dev libxml-parser-perl libxft-dev libhttp-date-perl python-gi python-dev man-db python-gobject-2-dev dbus-x11 x11proto-kb-dev python-gobject-2 libpixman-1-0 x11proto-xinerama-dev python-empy libpango1.0-0 libpthread-stubs0-dev ucf cdbs libgtk2.0-common libgirepository-1.0-1 libwww-robotrules-perl gettext-base dh-buildinfo libunistring0 libsm6 python-central libcairo-script-interpreter2 libxcb-render0 python-gi-dev libglib2.0-bin autoconf (Reading database ... 21000 files and directories currently installed.) Removing libgconf2-dev ... Removing gir1.2-gconf-2.0 ... Removing libdbus-1-dev ... Removing gconf2 ... Purging configuration files for gconf2 ... Removing devscripts ... Purging configuration files for devscripts ... Removing libgconf2-4 ... Purging configuration files for libgconf2-4 ... Removing python-gtk2-dev ... Removing libgtk2.0-dev ... Removing libatk1.0-dev ... Removing dbus-x11 ... Purging configuration files for dbus-x11 ... Removing python-empy ... Removing cdbs ... Removing dh-buildinfo ... Removing python-central ... Purging configuration files for python-central ... Removing python-gobject-dev ... Removing python-scour ... Removing python-gtk2 ... Removing libxcomposite-dev ... Removing libdbus-glib-1-2 ... Purging configuration files for libdbus-glib-1-2 ... Removing python-cairo ... Removing psmisc ... Purging configuration files for psmisc ... Removing libxinerama-dev ... Removing libxml2-utils ... Removing libgdk-pixbuf2.0-dev ... Removing libxrandr-dev ... Removing gir1.2-atk-1.0 ... Removing libxdamage-dev ... Removing gconf2-common ... Purging configuration files for gconf2-common ... Removing dh-translations ... Removing python-support ... Purging configuration files for python-support ... Removing libgtk2.0-0 ... Purging configuration files for libgtk2.0-0 ... dpkg: warning: while removing libgtk2.0-0, directory '/usr/lib/i386-linux-gnu/gtk-2.0/2.10.0' not empty so not removed. Removing x11proto-damage-dev ... Removing libxrandr2 ... Purging configuration files for libxrandr2 ... Removing debhelper ... Removing libpango1.0-dev ... Removing libxcursor-dev ... Removing libxcomposite1 ... Purging configuration files for libxcomposite1 ... Removing x11proto-composite-dev ... Removing intltool ... Removing libxi-dev ... Removing shared-mime-info ... Purging configuration files for shared-mime-info ... Removing po-debconf ... Removing libxml-parser-perl ... Removing libxft-dev ... Removing man-db ... Purging configuration files for man-db ... Removing catpages as well as /var/cache/man hierarchy. Removing python-gobject-2-dev ... Removing x11proto-xinerama-dev ... Removing libgtk2.0-common ... Removing python-gi-dev ... Removing groff-base ... Purging configuration files for groff-base ... Removing libxfixes-dev ... Removing file ... Removing libxi6 ... Purging configuration files for libxi6 ... Removing automake ... Removing libxcursor1 ... Purging configuration files for libxcursor1 ... Removing gir1.2-gdkpixbuf-2.0 ... Removing x11proto-randr-dev ... Removing libxdamage1 ... Purging configuration files for libxdamage1 ... Removing dbus ... invoke-rc.d: policy-rc.d denied execution of stop. Purging configuration files for dbus ... rmdir: failed to remove `/var/run/dbus': No such file or directory Removing intltool-debian ... Removing libxext-dev ... Removing libcups2 ... Purging configuration files for libcups2 ... Removing libpipeline1 ... Purging configuration files for libpipeline1 ... Removing libxinerama1 ... Purging configuration files for libxinerama1 ... Removing libcairo2-dev ... Removing libxcb-render0-dev ... Removing autotools-dev ... Removing libffi-dev ... Removing libatk1.0-0 ... Purging configuration files for libatk1.0-0 ... Removing x11proto-fixes-dev ... Removing gir1.2-pango-1.0 ... Removing html2text ... Purging configuration files for html2text ... Removing libmagic1 ... Purging configuration files for libmagic1 ... Removing python-gobject ... Removing bsdmainutils ... Purging configuration files for bsdmainutils ... Removing libxfixes3 ... Purging configuration files for libxfixes3 ... Removing python-gi ... Purging configuration files for python-gi ... Removing python-dev ... Removing python-gobject-2 ... Purging configuration files for python-gobject-2 ... Removing libpango1.0-0 ... Purging configuration files for libpango1.0-0 ... Removing libcairo-script-interpreter2 ... Purging configuration files for libcairo-script-interpreter2 ... Removing autoconf ... Purging configuration files for autoconf ... Removing m4 ... Removing gettext ... Removing libcairo-gobject2 ... Purging configuration files for libcairo-gobject2 ... Removing libatk1.0-data ... Removing libgettextpo0 ... Removing libgdk-pixbuf2.0-0 ... Purging configuration files for libgdk-pixbuf2.0-0 ... Removing libjasper1 ... Purging configuration files for libjasper1 ... Removing libpixman-1-dev ... Removing libxcb-shm0-dev ... Removing libglib2.0-dev ... Removing x11proto-xext-dev ... Removing python2.7-dev ... Removing libavahi-client3 ... Purging configuration files for libavahi-client3 ... Removing libfontconfig1-dev ... Removing libpython2.7 ... Purging configuration files for libpython2.7 ... Removing libxrender-dev ... Removing libpng12-dev ... Removing libxft2 ... Purging configuration files for libxft2 ... Removing x11proto-render-dev ... Removing libxext6 ... Purging configuration files for libxext6 ... Removing libsm-dev ... Removing gir1.2-freedesktop ... Removing fontconfig ... Purging configuration files for fontconfig ... Removing libcroco3 ... Purging configuration files for libcroco3 ... Removing gir1.2-glib-2.0 ... Removing libice-dev ... Removing libfreetype6-dev ... Removing libthai0 ... Purging configuration files for libthai0 ... Removing python ... Purging configuration files for python ... Removing libtiff4 ... Purging configuration files for libtiff4 ... Removing libssl-dev ... Removing libgirepository-1.0-1 ... Purging configuration files for libgirepository-1.0-1 ... Removing gettext-base ... Removing libunistring0 ... Purging configuration files for libunistring0 ... Removing libsm6 ... Purging configuration files for libsm6 ... Removing libglib2.0-bin ... Purging configuration files for libglib2.0-bin ... Removing libavahi-common3 ... Purging configuration files for libavahi-common3 ... Removing zlib1g-dev ... Removing libcairo2 ... Purging configuration files for libcairo2 ... Removing libx11-dev ... Removing x11proto-input-dev ... Removing libexpat1-dev ... Removing libfontconfig1 ... Purging configuration files for libfontconfig1 ... Removing xtrans-dev ... Removing libglib2.0-data ... Removing libxml2 ... Purging configuration files for libxml2 ... Removing libjpeg8 ... Removing pkg-config ... Removing libthai-data ... Removing libice6 ... Purging configuration files for libice6 ... Removing libxrender1 ... Purging configuration files for libxrender1 ... Removing libdatrie1 ... Purging configuration files for libdatrie1 ... Removing libavahi-common-data ... Removing libpopt0 ... Purging configuration files for libpopt0 ... Removing libfreetype6 ... Purging configuration files for libfreetype6 ... Removing python2.7 ... Purging configuration files for python2.7 ... Removing libxcb-shm0 ... Purging configuration files for libxcb-shm0 ... Removing libexpat1 ... Purging configuration files for libexpat1 ... Removing mime-support ... Purging configuration files for mime-support ... Removing libxcb1-dev ... Removing x11proto-kb-dev ... Removing libpixman-1-0 ... Purging configuration files for libpixman-1-0 ... Removing libpthread-stubs0-dev ... Removing libxcb-render0 ... Purging configuration files for libxcb-render0 ... Removing fontconfig-config ... Purging configuration files for fontconfig-config ... Removing x11-common ... invoke-rc.d: policy-rc.d denied execution of stop. Purging configuration files for x11-common ... Removing libx11-6 ... Purging configuration files for libx11-6 ... Removing libxau-dev ... Removing libxdmcp-dev ... Removing ttf-dejavu-core ... Removing libdb4.8 ... Removing libxcb1 ... Purging configuration files for libxcb1 ... Removing libpthread-stubs0 ... Removing libxau6 ... Purging configuration files for libxau6 ... Removing x11proto-core-dev ... Removing libxdmcp6 ... Purging configuration files for libxdmcp6 ... Removing ucf ... Purging configuration files for ucf ... Removing libx11-data ... Removing xorg-sgml-doctools ... Removing liblwp-protocol-https-perl ... Removing libwww-perl ... Removing libnet-http-perl ... Removing libwww-robotrules-perl ... Removing libhttp-cookies-perl ... Removing libhtml-tree-perl ... Removing libio-socket-ssl-perl ... Removing libfile-listing-perl ... Removing libhttp-negotiate-perl ... Removing libnet-ssleay-perl ... Removing libhttp-message-perl ... Removing libhttp-date-perl ... Removing libhtml-parser-perl ... Removing libencode-locale-perl ... Removing liblwp-mediatypes-perl ... Removing libhtml-tagset-perl ... Removing liburi-perl ... Processing triggers for libc-bin ... ldconfig deferred processing now taking place Processing triggers for libglib2.0-0 ... No schema files found: doing nothing. ****************************************************************************** Finished at 20111205-0839 Build needed 00:01:12, 15864k disk space RUN: /usr/share/launchpad-buildd/slavebin/scan-for-processes ['/usr/share/launchpad-buildd/slavebin/scan-for-processes', '3b732c62e95fb1ec0c9361c263fc2210c0fcdb8a'] Scanning for processes to kill in build /home/buildd/build-3b732c62e95fb1ec0c9361c263fc2210c0fcdb8a/chroot-autobuild... RUN: /usr/share/launchpad-buildd/slavebin/umount-chroot ['umount-chroot', '3b732c62e95fb1ec0c9361c263fc2210c0fcdb8a'] Unmounting chroot for build 3b732c62e95fb1ec0c9361c263fc2210c0fcdb8a... none /home/buildd/build-3b732c62e95fb1ec0c9361c263fc2210c0fcdb8a/chroot-autobuild/proc proc rw,relatime 0 0 none /home/buildd/build-3b732c62e95fb1ec0c9361c263fc2210c0fcdb8a/chroot-autobuild/dev/pts devpts rw,relatime 0 0 none /home/buildd/build-3b732c62e95fb1ec0c9361c263fc2210c0fcdb8a/chroot-autobuild/sys sysfs rw,relatime 0 0 none /home/buildd/build-3b732c62e95fb1ec0c9361c263fc2210c0fcdb8a/chroot-autobuild/dev/shm tmpfs rw,relatime 0 0 RUN: /usr/share/launchpad-buildd/slavebin/remove-build ['remove-build', '3b732c62e95fb1ec0c9361c263fc2210c0fcdb8a'] Removing build 3b732c62e95fb1ec0c9361c263fc2210c0fcdb8a