RUN: /bin/echo ['echo', 'Forking build subprocess...'] Forking build subprocess... RUN: /usr/share/launchpad-buildd/slavebin/unpack-chroot ['unpack-chroot', '9634f4163eca24760ea2b949fdeee220510f9de9', '/home/buildd/filecache-default/d267a7b39544795f0e98d00c3cf7862045311464'] Uncompressing the tarball... Synching the system clock with the buildd NTP service... 6 Oct 17:28:43 ntpdate[3397]: step time server 10.211.37.1 offset -79789.163525 sec Unpacking chroot for build 9634f4163eca24760ea2b949fdeee220510f9de9 RUN: /usr/share/launchpad-buildd/slavebin/mount-chroot ['mount-chroot', '9634f4163eca24760ea2b949fdeee220510f9de9'] Mounting chroot for build 9634f4163eca24760ea2b949fdeee220510f9de9 RUN: /usr/share/launchpad-buildd/slavebin/override-sources-list ['override-sources-list', '9634f4163eca24760ea2b949fdeee220510f9de9', 'deb http://ppa.launchpad.net/r0lf/ppa/ubuntu lucid main', 'deb http://ftpmaster.internal/ubuntu lucid main restricted universe multiverse', 'deb http://ftpmaster.internal/ubuntu lucid-security main restricted universe multiverse', 'deb http://ftpmaster.internal/ubuntu lucid-updates main restricted universe multiverse'] Overriding sources.list in build-9634f4163eca24760ea2b949fdeee220510f9de9 RUN: /usr/share/launchpad-buildd/slavebin/update-debian-chroot ['update-debian-chroot', '9634f4163eca24760ea2b949fdeee220510f9de9', 'i386'] Updating debian chroot for build 9634f4163eca24760ea2b949fdeee220510f9de9 Get:1 http://ftpmaster.internal lucid Release.gpg [189B] Get:2 http://ftpmaster.internal lucid-security Release.gpg [198B] Get:3 http://ftpmaster.internal lucid-updates Release.gpg [198B] Get:4 http://ftpmaster.internal lucid Release [57.2kB] Get:5 http://ftpmaster.internal lucid-security Release [44.7kB] Get:6 http://ppa.launchpad.net lucid Release.gpg [316B] Get:7 http://ppa.launchpad.net lucid Release [13.9kB] Get:8 http://ftpmaster.internal lucid-updates Release [44.7kB] Ign http://ppa.launchpad.net lucid Release Get:9 http://ftpmaster.internal lucid/main Packages [1386kB] Get:10 http://ppa.launchpad.net lucid/main Packages [9200B] Get:11 http://ftpmaster.internal lucid/restricted Packages [6208B] Get:12 http://ftpmaster.internal lucid/universe Packages [5448kB] Get:13 http://ftpmaster.internal lucid/multiverse Packages [180kB] Get:14 http://ftpmaster.internal lucid-security/main Packages [210kB] Get:15 http://ftpmaster.internal lucid-security/restricted Packages [14B] Get:16 http://ftpmaster.internal lucid-security/universe Packages [86.8kB] Get:17 http://ftpmaster.internal lucid-security/multiverse Packages [4559B] Get:18 http://ftpmaster.internal lucid-updates/main Packages [517kB] Get:19 http://ftpmaster.internal lucid-updates/restricted Packages [3240B] Get:20 http://ftpmaster.internal lucid-updates/universe Packages [230kB] Get:21 http://ftpmaster.internal lucid-updates/multiverse Packages [10.5kB] Fetched 8253kB in 3s (2107kB/s) Reading package lists... W: GPG error: http://ppa.launchpad.net lucid Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 15331454B72FD7EC Reading package lists... Building dependency tree... Reading state information... The following packages will be upgraded: apt apt-transport-https base-files binutils bsdutils bzip2 ca-certificates coreutils dpkg dpkg-dev e2fslibs e2fsprogs gzip ifupdown initscripts libblkid1 libbz2-1.0 libc-bin libc-dev-bin libc6 libc6-dev libcomerr2 libcurl3-gnutls libdbus-1-3 libglib2.0-0 libgssapi-krb5-2 libk5crypto3 libkrb5-3 libkrb5support0 libldap-2.4-2 libpam-modules libpam-runtime libpam0g libplymouth2 libpng12-0 libss2 libssl0.9.8 libudev0 libusb-0.1-4 libuuid1 linux-libc-dev login mount mountall openssl passwd perl perl-base perl-modules pkg-create-dbgsym plymouth sysv-rc sysvinit-utils tar tzdata udev upstart util-linux 58 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 39.8MB of archives. After this operation, 111kB of additional disk space will be used. WARNING: The following packages cannot be authenticated! libpam-modules base-files coreutils dpkg libc-dev-bin libc6-dev libc-bin libc6 linux-libc-dev tzdata e2fslibs e2fsprogs gzip login mount perl-modules bzip2 libbz2-1.0 perl perl-base tar sysvinit-utils sysv-rc libpam0g passwd initscripts libdbus-1-3 libudev0 ifupdown libglib2.0-0 libusb-0.1-4 util-linux udev plymouth libpng12-0 libplymouth2 mountall upstart bsdutils apt libuuid1 libblkid1 libcomerr2 libpam-runtime libss2 libssl0.9.8 openssl ca-certificates libk5crypto3 libgssapi-krb5-2 libkrb5-3 libkrb5support0 libldap-2.4-2 libcurl3-gnutls apt-transport-https binutils dpkg-dev pkg-create-dbgsym Authentication warning overridden. Get:1 http://ftpmaster.internal/ubuntu/ lucid-security/main libpam-modules 1.1.1-2ubuntu5.3 [371kB] Get:2 http://ftpmaster.internal/ubuntu/ lucid-updates/main base-files 5.0.0ubuntu20.10.04.4 [70.3kB] Get:3 http://ftpmaster.internal/ubuntu/ lucid-updates/main coreutils 7.4-2ubuntu3 [2435kB] Get:4 http://ftpmaster.internal/ubuntu/ lucid-security/main dpkg 1.15.5.6ubuntu4.5 [2192kB] Get:5 http://ftpmaster.internal/ubuntu/ lucid-updates/main libc-dev-bin 2.11.1-0ubuntu7.8 [214kB] Get:6 http://ftpmaster.internal/ubuntu/ lucid-updates/main libc6-dev 2.11.1-0ubuntu7.8 [4839kB] Get:7 http://ftpmaster.internal/ubuntu/ lucid-updates/main libc-bin 2.11.1-0ubuntu7.8 [723kB] Get:8 http://ftpmaster.internal/ubuntu/ lucid-updates/main libc6 2.11.1-0ubuntu7.8 [3780kB] Get:9 http://ftpmaster.internal/ubuntu/ lucid-security/main linux-libc-dev 2.6.32-34.77 [827kB] Get:10 http://ftpmaster.internal/ubuntu/ lucid-updates/main tzdata 2011j-0ubuntu0.10.04 [635kB] Get:11 http://ftpmaster.internal/ubuntu/ lucid-updates/main e2fslibs 1.41.11-1ubuntu2.1 [140kB] Get:12 http://ftpmaster.internal/ubuntu/ lucid-updates/main e2fsprogs 1.41.11-1ubuntu2.1 [792kB] Get:13 http://ftpmaster.internal/ubuntu/ lucid-updates/main gzip 1.3.12-9ubuntu1.1 [102kB] Get:14 http://ftpmaster.internal/ubuntu/ lucid-security/main login 1:4.1.4.2-1ubuntu2.2 [316kB] Get:15 http://ftpmaster.internal/ubuntu/ lucid-updates/main mount 2.17.2-0ubuntu1.10.04.2 [175kB] Get:16 http://ftpmaster.internal/ubuntu/ lucid-security/main perl-modules 5.10.1-8ubuntu2.1 [3489kB] Get:17 http://ftpmaster.internal/ubuntu/ lucid-security/main bzip2 1.0.5-4ubuntu0.1 [47.5kB] Get:18 http://ftpmaster.internal/ubuntu/ lucid-security/main libbz2-1.0 1.0.5-4ubuntu0.1 [45.5kB] Get:19 http://ftpmaster.internal/ubuntu/ lucid-security/main perl 5.10.1-8ubuntu2.1 [3743kB] Get:20 http://ftpmaster.internal/ubuntu/ lucid-security/main perl-base 5.10.1-8ubuntu2.1 [1003kB] Get:21 http://ftpmaster.internal/ubuntu/ lucid-updates/main tar 1.22-2ubuntu1 [343kB] Get:22 http://ftpmaster.internal/ubuntu/ lucid-updates/main sysvinit-utils 2.87dsf-4ubuntu17.4 [111kB] Get:23 http://ftpmaster.internal/ubuntu/ lucid-updates/main sysv-rc 2.87dsf-4ubuntu17.4 [79.7kB] Get:24 http://ftpmaster.internal/ubuntu/ lucid-security/main libpam0g 1.1.1-2ubuntu5.3 [123kB] Get:25 http://ftpmaster.internal/ubuntu/ lucid-security/main passwd 1:4.1.4.2-1ubuntu2.2 [881kB] Get:26 http://ftpmaster.internal/ubuntu/ lucid-updates/main initscripts 2.87dsf-4ubuntu17.4 [74.6kB] Get:27 http://ftpmaster.internal/ubuntu/ lucid-security/main libdbus-1-3 1.2.16-2ubuntu4.3 [128kB] Get:28 http://ftpmaster.internal/ubuntu/ lucid-updates/main libudev0 151-12.3 [119kB] Get:29 http://ftpmaster.internal/ubuntu/ lucid-security/main ifupdown 0.6.8ubuntu29.2 [60.5kB] Get:30 http://ftpmaster.internal/ubuntu/ lucid-updates/main libglib2.0-0 2.24.1-0ubuntu1 [1029kB] Get:31 http://ftpmaster.internal/ubuntu/ lucid-updates/main libusb-0.1-4 2:0.1.12-14ubuntu0.2 [20.5kB] Get:32 http://ftpmaster.internal/ubuntu/ lucid-updates/main util-linux 2.17.2-0ubuntu1.10.04.2 [533kB] Get:33 http://ftpmaster.internal/ubuntu/ lucid-updates/main udev 151-12.3 [410kB] Get:34 http://ftpmaster.internal/ubuntu/ lucid-updates/main plymouth 0.8.2-2ubuntu2.2 [115kB] Get:35 http://ftpmaster.internal/ubuntu/ lucid-security/main libpng12-0 1.2.42-1ubuntu2.2 [177kB] Get:36 http://ftpmaster.internal/ubuntu/ lucid-updates/main libplymouth2 0.8.2-2ubuntu2.2 [92.0kB] Get:37 http://ftpmaster.internal/ubuntu/ lucid-updates/main mountall 2.15.3 [52.5kB] Get:38 http://ftpmaster.internal/ubuntu/ lucid-updates/main upstart 0.6.5-8 [289kB] Get:39 http://ftpmaster.internal/ubuntu/ lucid-updates/main bsdutils 1:2.17.2-0ubuntu1.10.04.2 [81.2kB] Get:40 http://ftpmaster.internal/ubuntu/ lucid-security/main apt 0.7.25.3ubuntu9.7 [1811kB] Get:41 http://ftpmaster.internal/ubuntu/ lucid-updates/main libuuid1 2.17.2-0ubuntu1.10.04.2 [61.8kB] Get:42 http://ftpmaster.internal/ubuntu/ lucid-updates/main libblkid1 2.17.2-0ubuntu1.10.04.2 [111kB] Get:43 http://ftpmaster.internal/ubuntu/ lucid-updates/main libcomerr2 1.41.11-1ubuntu2.1 [50.7kB] Get:44 http://ftpmaster.internal/ubuntu/ lucid-security/main libpam-runtime 1.1.1-2ubuntu5.3 [115kB] Get:45 http://ftpmaster.internal/ubuntu/ lucid-updates/main libss2 1.41.11-1ubuntu2.1 [55.7kB] Get:46 http://ftpmaster.internal/ubuntu/ lucid-security/main libssl0.9.8 0.9.8k-7ubuntu8.6 [3015kB] Get:47 http://ftpmaster.internal/ubuntu/ lucid-security/main openssl 0.9.8k-7ubuntu8.6 [400kB] Get:48 http://ftpmaster.internal/ubuntu/ lucid-security/main ca-certificates 20090814ubuntu0.10.04.1 [146kB] Get:49 http://ftpmaster.internal/ubuntu/ lucid-security/main libk5crypto3 1.8.1+dfsg-2ubuntu0.9 [96.9kB] Get:50 http://ftpmaster.internal/ubuntu/ lucid-security/main libgssapi-krb5-2 1.8.1+dfsg-2ubuntu0.9 [121kB] Get:51 http://ftpmaster.internal/ubuntu/ lucid-security/main libkrb5-3 1.8.1+dfsg-2ubuntu0.9 [351kB] Get:52 http://ftpmaster.internal/ubuntu/ lucid-security/main libkrb5support0 1.8.1+dfsg-2ubuntu0.9 [42.9kB] Get:53 http://ftpmaster.internal/ubuntu/ lucid-updates/main libldap-2.4-2 2.4.21-0ubuntu5.5 [202kB] Get:54 http://ftpmaster.internal/ubuntu/ lucid-security/main libcurl3-gnutls 7.19.7-1ubuntu1.1 [216kB] Get:55 http://ftpmaster.internal/ubuntu/ lucid-security/main apt-transport-https 0.7.25.3ubuntu9.7 [81.3kB] Get:56 http://ftpmaster.internal/ubuntu/ lucid-security/main binutils 2.20.1-3ubuntu7.1 [1601kB] Get:57 http://ftpmaster.internal/ubuntu/ lucid-security/main dpkg-dev 1.15.5.6ubuntu4.5 [654kB] Get:58 http://ftpmaster.internal/ubuntu/ lucid-updates/main pkg-create-dbgsym 0.43 [13.1kB] debconf: delaying package configuration, since apt-utils is not installed Fetched 39.8MB in 2s (19.8MB/s) (Reading database ... 13401 files and directories currently installed.) Preparing to replace libpam-modules 1.1.1-2ubuntu2 (using .../libpam-modules_1.1.1-2ubuntu5.3_i386.deb) ... Unpacking replacement libpam-modules ... Setting up libpam-modules (1.1.1-2ubuntu5.3) ... (Reading database ... 13401 files and directories currently installed.) Preparing to replace base-files 5.0.0ubuntu20 (using .../base-files_5.0.0ubuntu20.10.04.4_i386.deb) ... Unpacking replacement base-files ... Setting up base-files (5.0.0ubuntu20.10.04.4) ... Installing new version of config file /etc/issue ... Installing new version of config file /etc/issue.net ... Installing new version of config file /etc/lsb-release ... (Reading database ... 13401 files and directories currently installed.) Preparing to replace coreutils 7.4-2ubuntu2 (using .../coreutils_7.4-2ubuntu3_i386.deb) ... Unpacking replacement coreutils ... Setting up coreutils (7.4-2ubuntu3) ... (Reading database ... 13401 files and directories currently installed.) Preparing to replace dpkg 1.15.5.6ubuntu4 (using .../dpkg_1.15.5.6ubuntu4.5_i386.deb) ... Unpacking replacement dpkg ... Setting up dpkg (1.15.5.6ubuntu4.5) ... (Reading database ... 13401 files and directories currently installed.) Preparing to replace libc-dev-bin 2.11.1-0ubuntu7 (using .../libc-dev-bin_2.11.1-0ubuntu7.8_i386.deb) ... Unpacking replacement libc-dev-bin ... Preparing to replace libc6-dev 2.11.1-0ubuntu7 (using .../libc6-dev_2.11.1-0ubuntu7.8_i386.deb) ... Unpacking replacement libc6-dev ... Preparing to replace libc-bin 2.11.1-0ubuntu7 (using .../libc-bin_2.11.1-0ubuntu7.8_i386.deb) ... Unpacking replacement libc-bin ... Setting up libc-bin (2.11.1-0ubuntu7.8) ... (Reading database ... 13401 files and directories currently installed.) Preparing to replace libc6 2.11.1-0ubuntu7 (using .../libc6_2.11.1-0ubuntu7.8_i386.deb) ... Unpacking replacement libc6 ... Setting up libc6 (2.11.1-0ubuntu7.8) ... Processing triggers for libc-bin ... ldconfig deferred processing now taking place (Reading database ... 13401 files and directories currently installed.) Preparing to replace linux-libc-dev 2.6.32-21.32 (using .../linux-libc-dev_2.6.32-34.77_i386.deb) ... Unpacking replacement linux-libc-dev ... Preparing to replace tzdata 2010i-1 (using .../tzdata_2011j-0ubuntu0.10.04_all.deb) ... Unpacking replacement tzdata ... Setting up tzdata (2011j-0ubuntu0.10.04) ... Current default time zone: 'Etc/UTC' Local time is now: Wed Oct 5 19:20:04 UTC 2011. Universal Time is now: Wed Oct 5 19:20:04 UTC 2011. Run 'dpkg-reconfigure tzdata' if you wish to change it. (Reading database ... 13428 files and directories currently installed.) Preparing to replace e2fslibs 1.41.11-1ubuntu2 (using .../e2fslibs_1.41.11-1ubuntu2.1_i386.deb) ... Unpacking replacement e2fslibs ... Setting up e2fslibs (1.41.11-1ubuntu2.1) ... Processing triggers for libc-bin ... ldconfig deferred processing now taking place (Reading database ... 13428 files and directories currently installed.) Preparing to replace e2fsprogs 1.41.11-1ubuntu2 (using .../e2fsprogs_1.41.11-1ubuntu2.1_i386.deb) ... Unpacking replacement e2fsprogs ... Setting up e2fsprogs (1.41.11-1ubuntu2.1) ... (Reading database ... 13428 files and directories currently installed.) Preparing to replace gzip 1.3.12-9ubuntu1 (using .../gzip_1.3.12-9ubuntu1.1_i386.deb) ... Unpacking replacement gzip ... Setting up gzip (1.3.12-9ubuntu1.1) ... (Reading database ... 13428 files and directories currently installed.) Preparing to replace login 1:4.1.4.2-1ubuntu2 (using .../login_1%3a4.1.4.2-1ubuntu2.2_i386.deb) ... Unpacking replacement login ... Setting up login (1:4.1.4.2-1ubuntu2.2) ... (Reading database ... 13428 files and directories currently installed.) Preparing to replace mount 2.17.2-0ubuntu1 (using .../mount_2.17.2-0ubuntu1.10.04.2_i386.deb) ... Unpacking replacement mount ... Setting up mount (2.17.2-0ubuntu1.10.04.2) ... (Reading database ... 13428 files and directories currently installed.) Preparing to replace perl-modules 5.10.1-8ubuntu2 (using .../perl-modules_5.10.1-8ubuntu2.1_all.deb) ... Unpacking replacement perl-modules ... Preparing to replace bzip2 1.0.5-4 (using .../bzip2_1.0.5-4ubuntu0.1_i386.deb) ... Unpacking replacement bzip2 ... Preparing to replace libbz2-1.0 1.0.5-4 (using .../libbz2-1.0_1.0.5-4ubuntu0.1_i386.deb) ... Unpacking replacement libbz2-1.0 ... Preparing to replace perl 5.10.1-8ubuntu2 (using .../perl_5.10.1-8ubuntu2.1_i386.deb) ... Unpacking replacement perl ... Preparing to replace perl-base 5.10.1-8ubuntu2 (using .../perl-base_5.10.1-8ubuntu2.1_i386.deb) ... Unpacking replacement perl-base ... Setting up perl-base (5.10.1-8ubuntu2.1) ... (Reading database ... 13428 files and directories currently installed.) Preparing to replace tar 1.22-2 (using .../tar_1.22-2ubuntu1_i386.deb) ... Unpacking replacement tar ... Setting up tar (1.22-2ubuntu1) ... (Reading database ... 13428 files and directories currently installed.) Preparing to replace sysvinit-utils 2.87dsf-4ubuntu17 (using .../sysvinit-utils_2.87dsf-4ubuntu17.4_i386.deb) ... Unpacking replacement sysvinit-utils ... Preparing to replace sysv-rc 2.87dsf-4ubuntu17 (using .../sysv-rc_2.87dsf-4ubuntu17.4_all.deb) ... Unpacking replacement sysv-rc ... Preparing to replace libpam0g 1.1.1-2ubuntu2 (using .../libpam0g_1.1.1-2ubuntu5.3_i386.deb) ... Unpacking replacement libpam0g ... Setting up libpam0g (1.1.1-2ubuntu5.3) ... Processing triggers for libc-bin ... ldconfig deferred processing now taking place (Reading database ... 13428 files and directories currently installed.) Preparing to replace passwd 1:4.1.4.2-1ubuntu2 (using .../passwd_1%3a4.1.4.2-1ubuntu2.2_i386.deb) ... Unpacking replacement passwd ... Setting up passwd (1:4.1.4.2-1ubuntu2.2) ... (Reading database ... 13428 files and directories currently installed.) Preparing to replace initscripts 2.87dsf-4ubuntu17 (using .../initscripts_2.87dsf-4ubuntu17.4_i386.deb) ... Unpacking replacement initscripts ... Preparing to replace libdbus-1-3 1.2.16-2ubuntu4 (using .../libdbus-1-3_1.2.16-2ubuntu4.3_i386.deb) ... Unpacking replacement libdbus-1-3 ... Preparing to replace libudev0 151-12 (using .../libudev0_151-12.3_i386.deb) ... Unpacking replacement libudev0 ... Preparing to replace ifupdown 0.6.8ubuntu29 (using .../ifupdown_0.6.8ubuntu29.2_i386.deb) ... Unpacking replacement ifupdown ... Preparing to replace libglib2.0-0 2.24.0-0ubuntu4 (using .../libglib2.0-0_2.24.1-0ubuntu1_i386.deb) ... Unpacking replacement libglib2.0-0 ... Preparing to replace libusb-0.1-4 2:0.1.12-14 (using .../libusb-0.1-4_2%3a0.1.12-14ubuntu0.2_i386.deb) ... Unpacking replacement libusb-0.1-4 ... Preparing to replace util-linux 2.17.2-0ubuntu1 (using .../util-linux_2.17.2-0ubuntu1.10.04.2_i386.deb) ... Unpacking replacement util-linux ... Setting up util-linux (2.17.2-0ubuntu1.10.04.2) ... (Reading database ... 13428 files and directories currently installed.) Preparing to replace udev 151-12 (using .../udev_151-12.3_i386.deb) ... Adding `local diversion of /sbin/udevadm to /sbin/udevadm.upgrade' Unpacking replacement udev ... Preparing to replace plymouth 0.8.2-2ubuntu2 (using .../plymouth_0.8.2-2ubuntu2.2_i386.deb) ... Unpacking replacement plymouth ... Preparing to replace libpng12-0 1.2.42-1ubuntu2 (using .../libpng12-0_1.2.42-1ubuntu2.2_i386.deb) ... Unpacking replacement libpng12-0 ... Preparing to replace libplymouth2 0.8.2-2ubuntu2 (using .../libplymouth2_0.8.2-2ubuntu2.2_i386.deb) ... Unpacking replacement libplymouth2 ... Preparing to replace mountall 2.14 (using .../mountall_2.15.3_i386.deb) ... Unpacking replacement mountall ... Preparing to replace upstart 0.6.5-6 (using .../upstart_0.6.5-8_i386.deb) ... Unpacking replacement upstart ... Preparing to replace bsdutils 1:2.17.2-0ubuntu1 (using .../bsdutils_1%3a2.17.2-0ubuntu1.10.04.2_i386.deb) ... Unpacking replacement bsdutils ... Setting up bsdutils (1:2.17.2-0ubuntu1.10.04.2) ... (Reading database ... 13429 files and directories currently installed.) Preparing to replace apt 0.7.25.3ubuntu7 (using .../apt_0.7.25.3ubuntu9.7_i386.deb) ... Unpacking replacement apt ... Setting up apt (0.7.25.3ubuntu9.7) ... Installing new version of config file /etc/cron.daily/apt ... Processing triggers for libc-bin ... ldconfig deferred processing now taking place (Reading database ... 13429 files and directories currently installed.) Preparing to replace libuuid1 2.17.2-0ubuntu1 (using .../libuuid1_2.17.2-0ubuntu1.10.04.2_i386.deb) ... Unpacking replacement libuuid1 ... Setting up libuuid1 (2.17.2-0ubuntu1.10.04.2) ... Processing triggers for libc-bin ... ldconfig deferred processing now taking place (Reading database ... 13429 files and directories currently installed.) Preparing to replace libblkid1 2.17.2-0ubuntu1 (using .../libblkid1_2.17.2-0ubuntu1.10.04.2_i386.deb) ... Unpacking replacement libblkid1 ... Setting up libblkid1 (2.17.2-0ubuntu1.10.04.2) ... Processing triggers for libc-bin ... ldconfig deferred processing now taking place (Reading database ... 13429 files and directories currently installed.) Preparing to replace libcomerr2 1.41.11-1ubuntu2 (using .../libcomerr2_1.41.11-1ubuntu2.1_i386.deb) ... Unpacking replacement libcomerr2 ... Setting up libcomerr2 (1.41.11-1ubuntu2.1) ... Processing triggers for libc-bin ... ldconfig deferred processing now taking place (Reading database ... 13429 files and directories currently installed.) Preparing to replace libpam-runtime 1.1.1-2ubuntu2 (using .../libpam-runtime_1.1.1-2ubuntu5.3_all.deb) ... Unpacking replacement libpam-runtime ... Setting up libpam-runtime (1.1.1-2ubuntu5.3) ... (Reading database ... 13429 files and directories currently installed.) Preparing to replace libss2 1.41.11-1ubuntu2 (using .../libss2_1.41.11-1ubuntu2.1_i386.deb) ... Unpacking replacement libss2 ... Setting up libss2 (1.41.11-1ubuntu2.1) ... Processing triggers for libc-bin ... ldconfig deferred processing now taking place (Reading database ... 13429 files and directories currently installed.) Preparing to replace libssl0.9.8 0.9.8k-7ubuntu8 (using .../libssl0.9.8_0.9.8k-7ubuntu8.6_i386.deb) ... Unpacking replacement libssl0.9.8 ... Setting up libssl0.9.8 (0.9.8k-7ubuntu8.6) ... Processing triggers for libc-bin ... ldconfig deferred processing now taking place (Reading database ... 13429 files and directories currently installed.) Preparing to replace openssl 0.9.8k-7ubuntu8 (using .../openssl_0.9.8k-7ubuntu8.6_i386.deb) ... Unpacking replacement openssl ... Preparing to replace ca-certificates 20090814 (using .../ca-certificates_20090814ubuntu0.10.04.1_all.deb) ... Unpacking replacement ca-certificates ... Preparing to replace libk5crypto3 1.8.1+dfsg-2 (using .../libk5crypto3_1.8.1+dfsg-2ubuntu0.9_i386.deb) ... Unpacking replacement libk5crypto3 ... Preparing to replace libgssapi-krb5-2 1.8.1+dfsg-2 (using .../libgssapi-krb5-2_1.8.1+dfsg-2ubuntu0.9_i386.deb) ... Unpacking replacement libgssapi-krb5-2 ... Preparing to replace libkrb5-3 1.8.1+dfsg-2 (using .../libkrb5-3_1.8.1+dfsg-2ubuntu0.9_i386.deb) ... Unpacking replacement libkrb5-3 ... Preparing to replace libkrb5support0 1.8.1+dfsg-2 (using .../libkrb5support0_1.8.1+dfsg-2ubuntu0.9_i386.deb) ... Unpacking replacement libkrb5support0 ... Preparing to replace libldap-2.4-2 2.4.21-0ubuntu5 (using .../libldap-2.4-2_2.4.21-0ubuntu5.5_i386.deb) ... Unpacking replacement libldap-2.4-2 ... Preparing to replace libcurl3-gnutls 7.19.7-1ubuntu1 (using .../libcurl3-gnutls_7.19.7-1ubuntu1.1_i386.deb) ... Unpacking replacement libcurl3-gnutls ... Preparing to replace apt-transport-https 0.7.25.3ubuntu7 (using .../apt-transport-https_0.7.25.3ubuntu9.7_i386.deb) ... Unpacking replacement apt-transport-https ... Preparing to replace binutils 2.20.1-3ubuntu5 (using .../binutils_2.20.1-3ubuntu7.1_i386.deb) ... Unpacking replacement binutils ... Preparing to replace dpkg-dev 1.15.5.6ubuntu4 (using .../dpkg-dev_1.15.5.6ubuntu4.5_all.deb) ... Unpacking replacement dpkg-dev ... Preparing to replace pkg-create-dbgsym 0.42 (using .../pkg-create-dbgsym_0.43_all.deb) ... Unpacking replacement pkg-create-dbgsym ... Setting up libc-dev-bin (2.11.1-0ubuntu7.8) ... Setting up linux-libc-dev (2.6.32-34.77) ... Setting up libc6-dev (2.11.1-0ubuntu7.8) ... Setting up libbz2-1.0 (1.0.5-4ubuntu0.1) ... Setting up bzip2 (1.0.5-4ubuntu0.1) ... Setting up sysvinit-utils (2.87dsf-4ubuntu17.4) ... Setting up sysv-rc (2.87dsf-4ubuntu17.4) ... Setting up libdbus-1-3 (1.2.16-2ubuntu4.3) ... Setting up libudev0 (151-12.3) ... Setting up libglib2.0-0 (2.24.1-0ubuntu1) ... Setting up libusb-0.1-4 (2:0.1.12-14ubuntu0.2) ... Setting up libpng12-0 (1.2.42-1ubuntu2.2) ... Setting up libplymouth2 (0.8.2-2ubuntu2.2) ... Setting up openssl (0.9.8k-7ubuntu8.6) ... Setting up ca-certificates (20090814ubuntu0.10.04.1) ... Updating certificates in /etc/ssl/certs... WARNING: Skipping duplicate certificate ca-certificates.crt 0 added, 1 removed; done. Running hooks in /etc/ca-certificates/update.d....done. Setting up libkrb5support0 (1.8.1+dfsg-2ubuntu0.9) ... Setting up libk5crypto3 (1.8.1+dfsg-2ubuntu0.9) ... Setting up libkrb5-3 (1.8.1+dfsg-2ubuntu0.9) ... Setting up libgssapi-krb5-2 (1.8.1+dfsg-2ubuntu0.9) ... Setting up libldap-2.4-2 (2.4.21-0ubuntu5.5) ... Setting up libcurl3-gnutls (7.19.7-1ubuntu1.1) ... Setting up apt-transport-https (0.7.25.3ubuntu9.7) ... Setting up binutils (2.20.1-3ubuntu7.1) ... Setting up pkg-create-dbgsym (0.43) ... Setting up perl-modules (5.10.1-8ubuntu2.1) ... Setting up perl (5.10.1-8ubuntu2.1) ... Setting up mountall (2.15.3) ... Installing new version of config file /etc/init/mountall.conf ... Setting up upstart (0.6.5-8) ... Setting up initscripts (2.87dsf-4ubuntu17.4) ... Installing new version of config file /etc/init.d/sendsigs ... Installing new version of config file /etc/init.d/umountroot ... Setting up dpkg-dev (1.15.5.6ubuntu4.5) ... Setting up udev (151-12.3) ... Removing `local diversion of /sbin/udevadm to /sbin/udevadm.upgrade' update-initramfs: deferring update (trigger activated) Setting up plymouth (0.8.2-2ubuntu2.2) ... update-initramfs: deferring update (trigger activated) Setting up ifupdown (0.6.8ubuntu29.2) ... 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', '9634f4163eca24760ea2b949fdeee220510f9de9', 'i386', 'lucid', '--nolog', '--batch', '--archive=ubuntu', '--dist=lucid', '-A', '--purpose=PPA', '--architecture=i386', '--comp=main', 'alarm-clock-applet_0.3.1-1.dsc'] Initiating build 9634f4163eca24760ea2b949fdeee220510f9de9 with 2 processor cores. Automatic build of alarm-clock-applet_0.3.1-1 on doubah by sbuild/i386 1.170.5 Build started at 20111005-1920 ****************************************************************************** alarm-clock-applet_0.3.1-1.dsc exists in cwd ** Using build dependencies supplied by package: Build-Depends: debhelper (>= 7.0.50), autotools-dev, intltool (>= 0.40), libglib2.0-dev (>= 2.16.0), libgtk2.0-dev (>= 2.12.0), libgconf2-dev (>= 2.8.0), libgstreamer0.10-dev (>= 0.10.2), libnotify-dev (>= 0.4.1), gnome-icon-theme (>= 2.15.91), libxml2-dev, libunique-dev Checking for already installed source dependencies... debhelper: missing autotools-dev: missing intltool: missing libglib2.0-dev: missing libgtk2.0-dev: missing libgconf2-dev: missing libgstreamer0.10-dev: missing libnotify-dev: missing gnome-icon-theme: missing libxml2-dev: missing libunique-dev: missing Checking for source dependency conflicts... /usr/bin/sudo /usr/bin/apt-get --purge $CHROOT_OPTIONS -q -y install debhelper autotools-dev intltool libglib2.0-dev libgtk2.0-dev libgconf2-dev libgstreamer0.10-dev libnotify-dev gnome-icon-theme libxml2-dev libunique-dev Reading package lists... Building dependency tree... Reading state information... The following extra packages will be installed: autoconf automake bsdmainutils dbus dbus-x11 defoma file fontconfig fontconfig-config gconf2 gconf2-common gettext gettext-base groff-base hicolor-icon-theme html2text intltool-debian libatk1.0-0 libatk1.0-dev libavahi-client3 libavahi-common-data libavahi-common3 libcairo2 libcairo2-dev libcroco3 libcups2 libdatrie1 libdbus-1-dev libdbus-glib-1-2 libdbus-glib-1-dev libdirectfb-1.2-0 libdirectfb-dev libdirectfb-extra libexpat1 libexpat1-dev libfontconfig1 libfontconfig1-dev libfreetype6 libfreetype6-dev libgconf2-4 libgsf-1-114 libgsf-1-common libgstreamer0.10-0 libgtk2.0-0 libgtk2.0-bin libgtk2.0-common libhtml-parser-perl libhtml-tagset-perl libhtml-tree-perl libice-dev libice6 libidl-dev libidl0 libjasper1 libjpeg62 libjpeg62-dev libmagic1 libncursesw5 libnewt0.52 libnotify1 liborbit2 liborbit2-dev libpango1.0-0 libpango1.0-common libpango1.0-dev libpixman-1-0 libpixman-1-dev libpng12-dev libpopt0 libpthread-stubs0 libpthread-stubs0-dev librsvg2-2 librsvg2-common libsm-dev libsm6 libsqlite3-0 libsysfs-dev libsysfs2 libthai-data libthai0 libtiff4 libts-0.0-0 libunique-1.0-0 liburi-perl libwww-perl libx11-6 libx11-data libx11-dev libxau-dev libxau6 libxcb-render-util0 libxcb-render-util0-dev libxcb-render0 libxcb-render0-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 python2.6 shared-mime-info tsconf ttf-dejavu-core ucf whiptail 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 xtrans-dev zlib1g-dev Suggested packages: autoconf2.13 autoconf-archive gnu-standards autoconf-doc libtool wamerican wordlist whois vacation dh-make defoma-doc psfontmgr x-ttcidfont-conf dfontmgr libfont-freetype-perl gconf-defaults-service gettext-doc groff libcairo2-doc cups-common libglib2.0-doc python-subunit gstreamer0.10-tools gstreamer0.10-plugins gstreamer0.10-doc gvfs libgtk2.0-doc libdata-dump-perl libjasper-runtime ttf-japanese-gothic ttf-japanese-mincho ttf-thryomanes ttf-baekmuk ttf-arphic-gbsn00lp ttf-arphic-bsmi00lp ttf-arphic-gkai00mp ttf-arphic-bkai00mp libpango1.0-doc imagemagick librsvg2-bin libunique-doc libcrypt-ssleay-perl libio-socket-ssl-perl less www-browser libmail-box-perl python-doc python-tk python-profiler python2.6-doc python2.6-profiler Recommended packages: consolekit curl wget lynx cvs libatk1.0-data libgpm2 libfribidi0 notification-daemon orbit2 libmailtools-perl libhtml-format-perl xml-core libmail-sendmail-perl The following NEW packages will be installed: autoconf automake autotools-dev bsdmainutils dbus dbus-x11 debhelper defoma file fontconfig fontconfig-config gconf2 gconf2-common gettext gettext-base gnome-icon-theme groff-base hicolor-icon-theme html2text intltool intltool-debian libatk1.0-0 libatk1.0-dev libavahi-client3 libavahi-common-data libavahi-common3 libcairo2 libcairo2-dev libcroco3 libcups2 libdatrie1 libdbus-1-dev libdbus-glib-1-2 libdbus-glib-1-dev libdirectfb-1.2-0 libdirectfb-dev libdirectfb-extra libexpat1 libexpat1-dev libfontconfig1 libfontconfig1-dev libfreetype6 libfreetype6-dev libgconf2-4 libgconf2-dev libglib2.0-dev libgsf-1-114 libgsf-1-common libgstreamer0.10-0 libgstreamer0.10-dev libgtk2.0-0 libgtk2.0-bin libgtk2.0-common libgtk2.0-dev libhtml-parser-perl libhtml-tagset-perl libhtml-tree-perl libice-dev libice6 libidl-dev libidl0 libjasper1 libjpeg62 libjpeg62-dev libmagic1 libncursesw5 libnewt0.52 libnotify-dev libnotify1 liborbit2 liborbit2-dev libpango1.0-0 libpango1.0-common libpango1.0-dev libpixman-1-0 libpixman-1-dev libpng12-dev libpopt0 libpthread-stubs0 libpthread-stubs0-dev librsvg2-2 librsvg2-common libsm-dev libsm6 libsqlite3-0 libsysfs-dev libsysfs2 libthai-data libthai0 libtiff4 libts-0.0-0 libunique-1.0-0 libunique-dev liburi-perl libwww-perl libx11-6 libx11-data libx11-dev libxau-dev libxau6 libxcb-render-util0 libxcb-render-util0-dev libxcb-render0 libxcb-render0-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-dev libxml2-utils libxrandr-dev libxrandr2 libxrender-dev libxrender1 m4 man-db mime-support pkg-config po-debconf psmisc python python2.6 shared-mime-info tsconf ttf-dejavu-core ucf whiptail 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 xtrans-dev zlib1g-dev 0 upgraded, 158 newly installed, 0 to remove and 0 not upgraded. Need to get 46.7MB of archives. After this operation, 193MB of additional disk space will be used. WARNING: The following packages cannot be authenticated! x11-common libice6 x11proto-core-dev libice-dev libxau6 libxdmcp6 libxcb1 libx11-data libx11-6 libxau-dev libxdmcp-dev x11proto-input-dev x11proto-kb-dev xtrans-dev libpthread-stubs0 libpthread-stubs0-dev libxcb1-dev libx11-dev libxext6 libxfixes3 libxcomposite1 x11proto-xext-dev x11proto-fixes-dev libxfixes-dev x11proto-composite-dev libxext-dev libxcomposite-dev libmagic1 file libncursesw5 libnewt0.52 libpopt0 libsqlite3-0 mime-support python2.6 python ucf whiptail bsdmainutils gettext-base groff-base libexpat1 liburi-perl libhtml-tagset-perl libhtml-parser-perl libhtml-tree-perl libwww-perl libxml-parser-perl libxml2 man-db psmisc m4 autoconf autotools-dev automake dbus dbus-x11 html2text libcroco3 gettext intltool-debian po-debconf debhelper defoma libfreetype6 ttf-dejavu-core fontconfig-config libfontconfig1 fontconfig libdbus-glib-1-2 libidl0 liborbit2 gconf2-common libgconf2-4 gconf2 hicolor-icon-theme libgtk2.0-common libatk1.0-0 libsysfs2 tsconf libts-0.0-0 libdirectfb-1.2-0 libpixman-1-0 libxcb-render0 libxcb-render-util0 libxrender1 libcairo2 libavahi-common-data libavahi-common3 libavahi-client3 libcups2 libjpeg62 libjasper1 libpango1.0-common libdatrie1 libthai-data libthai0 libxft2 libpango1.0-0 libtiff4 libxcursor1 libxdamage1 libxi6 libxinerama1 libxrandr2 shared-mime-info libgtk2.0-0 libgtk2.0-bin libgsf-1-common libgsf-1-114 librsvg2-2 librsvg2-common gnome-icon-theme intltool pkg-config zlib1g-dev libglib2.0-dev libatk1.0-dev libexpat1-dev libfreetype6-dev libfontconfig1-dev x11proto-render-dev libxrender-dev libpng12-dev libdirectfb-extra libjpeg62-dev libsysfs-dev libdirectfb-dev libsm6 libsm-dev libpixman-1-dev libxcb-render0-dev libxcb-render-util0-dev libcairo2-dev libdbus-1-dev libdbus-glib-1-dev libidl-dev liborbit2-dev libgconf2-dev libgstreamer0.10-0 libxml2-dev libgstreamer0.10-dev libxft-dev libpango1.0-dev x11proto-xinerama-dev libxinerama-dev libxi-dev x11proto-randr-dev libxrandr-dev libxcursor-dev x11proto-damage-dev libxdamage-dev libxml2-utils libgtk2.0-dev libnotify1 libnotify-dev libunique-1.0-0 libunique-dev Authentication warning overridden. Get:1 http://ftpmaster.internal/ubuntu/ lucid/main x11-common 1:7.5+5ubuntu1 [308kB] Get:2 http://ftpmaster.internal/ubuntu/ lucid/main libice6 2:1.0.6-1 [50.5kB] Get:3 http://ftpmaster.internal/ubuntu/ lucid/main x11proto-core-dev 7.0.16-1 [92.2kB] Get:4 http://ftpmaster.internal/ubuntu/ lucid/main libice-dev 2:1.0.6-1 [60.0kB] Get:5 http://ftpmaster.internal/ubuntu/ lucid/main libxau6 1:1.0.5-1 [13.9kB] Get:6 http://ftpmaster.internal/ubuntu/ lucid/main libxdmcp6 1:1.0.3-1 [18.2kB] Get:7 http://ftpmaster.internal/ubuntu/ lucid/main libxcb1 1.5-2 [39.4kB] Get:8 http://ftpmaster.internal/ubuntu/ lucid/main libx11-data 2:1.3.2-1ubuntu3 [220kB] Get:9 http://ftpmaster.internal/ubuntu/ lucid/main libx11-6 2:1.3.2-1ubuntu3 [816kB] Get:10 http://ftpmaster.internal/ubuntu/ lucid/main libxau-dev 1:1.0.5-1 [17.1kB] Get:11 http://ftpmaster.internal/ubuntu/ lucid/main libxdmcp-dev 1:1.0.3-1 [21.2kB] Get:12 http://ftpmaster.internal/ubuntu/ lucid/main x11proto-input-dev 2.0-2 [62.5kB] Get:13 http://ftpmaster.internal/ubuntu/ lucid/main x11proto-kb-dev 1.0.4-1 [27.3kB] Get:14 http://ftpmaster.internal/ubuntu/ lucid/main xtrans-dev 1.2.5-1 [68.5kB] Get:15 http://ftpmaster.internal/ubuntu/ lucid/main libpthread-stubs0 0.3-2 [3196B] Get:16 http://ftpmaster.internal/ubuntu/ lucid/main libpthread-stubs0-dev 0.3-2 [2414B] Get:17 http://ftpmaster.internal/ubuntu/ lucid/main libxcb1-dev 1.5-2 [73.8kB] Get:18 http://ftpmaster.internal/ubuntu/ lucid/main libx11-dev 2:1.3.2-1ubuntu3 [3505kB] Get:19 http://ftpmaster.internal/ubuntu/ lucid/main libxext6 2:1.1.1-2 [39.6kB] Get:20 http://ftpmaster.internal/ubuntu/ lucid/main libxfixes3 1:4.0.4-1 [15.2kB] Get:21 http://ftpmaster.internal/ubuntu/ lucid/main libxcomposite1 1:0.4.1-1 [12.4kB] Get:22 http://ftpmaster.internal/ubuntu/ lucid/main x11proto-xext-dev 7.1.1-2 [27.2kB] Get:23 http://ftpmaster.internal/ubuntu/ lucid/main x11proto-fixes-dev 1:4.1.1-2 [15.5kB] Get:24 http://ftpmaster.internal/ubuntu/ lucid/main libxfixes-dev 1:4.0.4-1 [17.4kB] Get:25 http://ftpmaster.internal/ubuntu/ lucid/main x11proto-composite-dev 1:0.4.1-1 [13.3kB] Get:26 http://ftpmaster.internal/ubuntu/ lucid/main libxext-dev 2:1.1.1-2 [102kB] Get:27 http://ftpmaster.internal/ubuntu/ lucid/main libxcomposite-dev 1:0.4.1-1 [15.6kB] Get:28 http://ftpmaster.internal/ubuntu/ lucid/main libmagic1 5.03-5ubuntu1 [392kB] Get:29 http://ftpmaster.internal/ubuntu/ lucid/main file 5.03-5ubuntu1 [47.4kB] Get:30 http://ftpmaster.internal/ubuntu/ lucid/main libncursesw5 5.7+20090803-2ubuntu3 [214kB] Get:31 http://ftpmaster.internal/ubuntu/ lucid/main libnewt0.52 0.52.10-5ubuntu1 [53.7kB] Get:32 http://ftpmaster.internal/ubuntu/ lucid/main libpopt0 1.15-1 [31.4kB] Get:33 http://ftpmaster.internal/ubuntu/ lucid/main libsqlite3-0 3.6.22-1 [294kB] Get:34 http://ftpmaster.internal/ubuntu/ lucid/main mime-support 3.48-1ubuntu1 [34.6kB] Get:35 http://ftpmaster.internal/ubuntu/ lucid/main python2.6 2.6.5-1ubuntu6 [2463kB] Get:36 http://ftpmaster.internal/ubuntu/ lucid/main python 2.6.5-0ubuntu1 [148kB] Get:37 http://ftpmaster.internal/ubuntu/ lucid/main ucf 3.0025 [68.1kB] Get:38 http://ftpmaster.internal/ubuntu/ lucid/main whiptail 0.52.10-5ubuntu1 [38.6kB] Get:39 http://ftpmaster.internal/ubuntu/ lucid/main bsdmainutils 8.0.1ubuntu1 [191kB] Get:40 http://ftpmaster.internal/ubuntu/ lucid/main gettext-base 0.17-8ubuntu3 [70.5kB] Get:41 http://ftpmaster.internal/ubuntu/ lucid/main groff-base 1.20.1-7 [1090kB] Get:42 http://ftpmaster.internal/ubuntu/ lucid/main libexpat1 2.0.1-7ubuntu1 [139kB] Get:43 http://ftpmaster.internal/ubuntu/ lucid/main liburi-perl 1.52-1 [96.8kB] Get:44 http://ftpmaster.internal/ubuntu/ lucid/main libhtml-tagset-perl 3.20-2 [13.5kB] Get:45 http://ftpmaster.internal/ubuntu/ lucid/main libhtml-parser-perl 3.64-1 [113kB] Get:46 http://ftpmaster.internal/ubuntu/ lucid/main libhtml-tree-perl 3.23-1 [209kB] Get:47 http://ftpmaster.internal/ubuntu/ lucid-security/main libwww-perl 5.834-1ubuntu0.1 [401kB] Get:48 http://ftpmaster.internal/ubuntu/ lucid/main libxml-parser-perl 2.36-1.1build3 [323kB] Get:49 http://ftpmaster.internal/ubuntu/ lucid-security/main libxml2 2.7.6.dfsg-1ubuntu1.2 [829kB] Get:50 http://ftpmaster.internal/ubuntu/ lucid-updates/main man-db 2.5.7-2ubuntu1 [1082kB] Get:51 http://ftpmaster.internal/ubuntu/ lucid/main psmisc 22.10-1 [58.0kB] Get:52 http://ftpmaster.internal/ubuntu/ lucid/main m4 1.4.13-3 [241kB] Get:53 http://ftpmaster.internal/ubuntu/ lucid/main autoconf 2.65-3ubuntu1 [772kB] Get:54 http://ftpmaster.internal/ubuntu/ lucid/main autotools-dev 20090611.1 [64.1kB] Get:55 http://ftpmaster.internal/ubuntu/ lucid/main automake 1:1.11.1-1 [608kB] Get:56 http://ftpmaster.internal/ubuntu/ lucid-security/main dbus 1.2.16-2ubuntu4.3 [189kB] Get:57 http://ftpmaster.internal/ubuntu/ lucid-security/main dbus-x11 1.2.16-2ubuntu4.3 [41.9kB] Get:58 http://ftpmaster.internal/ubuntu/ lucid/main html2text 1.3.2a-14build1 [101kB] Get:59 http://ftpmaster.internal/ubuntu/ lucid/main libcroco3 0.6.2-1 [92.5kB] Get:60 http://ftpmaster.internal/ubuntu/ lucid/main gettext 0.17-8ubuntu3 [1732kB] Get:61 http://ftpmaster.internal/ubuntu/ lucid/main intltool-debian 0.35.0+20060710.1 [31.6kB] Get:62 http://ftpmaster.internal/ubuntu/ lucid/main po-debconf 1.0.16 [224kB] Get:63 http://ftpmaster.internal/ubuntu/ lucid/main debhelper 7.4.15ubuntu1 [461kB] Get:64 http://ftpmaster.internal/ubuntu/ lucid/main defoma 0.11.10-4ubuntu1 [101kB] Get:65 http://ftpmaster.internal/ubuntu/ lucid-security/main libfreetype6 2.3.11-1ubuntu2.4 [419kB] Get:66 http://ftpmaster.internal/ubuntu/ lucid/main ttf-dejavu-core 2.30-2 [1436kB] Get:67 http://ftpmaster.internal/ubuntu/ lucid/main fontconfig-config 2.8.0-2ubuntu1 [205kB] Get:68 http://ftpmaster.internal/ubuntu/ lucid/main libfontconfig1 2.8.0-2ubuntu1 [98.9kB] Get:69 http://ftpmaster.internal/ubuntu/ lucid/main fontconfig 2.8.0-2ubuntu1 [156kB] Get:70 http://ftpmaster.internal/ubuntu/ lucid-security/main libdbus-glib-1-2 0.84-1ubuntu0.2 [159kB] Get:71 http://ftpmaster.internal/ubuntu/ lucid/main libidl0 0.8.13-1 [88.6kB] Get:72 http://ftpmaster.internal/ubuntu/ lucid/main liborbit2 1:2.14.18-0.1 [251kB] Get:73 http://ftpmaster.internal/ubuntu/ lucid/main gconf2-common 2.28.1-0ubuntu1 [28.7kB] Get:74 http://ftpmaster.internal/ubuntu/ lucid/main libgconf2-4 2.28.1-0ubuntu1 [157kB] Get:75 http://ftpmaster.internal/ubuntu/ lucid/main gconf2 2.28.1-0ubuntu1 [58.1kB] Get:76 http://ftpmaster.internal/ubuntu/ lucid/main hicolor-icon-theme 0.11-1 [9956B] Get:77 http://ftpmaster.internal/ubuntu/ lucid-updates/main libgtk2.0-common 2.20.1-0ubuntu2 [723kB] Get:78 http://ftpmaster.internal/ubuntu/ lucid-updates/main libatk1.0-0 1.30.0-0ubuntu2.1 [52.4kB] Get:79 http://ftpmaster.internal/ubuntu/ lucid/main libsysfs2 2.1.0-6 [23.3kB] Get:80 http://ftpmaster.internal/ubuntu/ lucid/main tsconf 1.0-7build1 [12.8kB] Get:81 http://ftpmaster.internal/ubuntu/ lucid/main libts-0.0-0 1.0-7build1 [28.3kB] Get:82 http://ftpmaster.internal/ubuntu/ lucid/main libdirectfb-1.2-0 1.2.8-5ubuntu2 [1126kB] Get:83 http://ftpmaster.internal/ubuntu/ lucid/main libpixman-1-0 0.16.4-1ubuntu2 [236kB] Get:84 http://ftpmaster.internal/ubuntu/ lucid/main libxcb-render0 1.5-2 [14.5kB] Get:85 http://ftpmaster.internal/ubuntu/ lucid/main libxcb-render-util0 0.3.6-1build1 [9632B] Get:86 http://ftpmaster.internal/ubuntu/ lucid/main libxrender1 1:0.9.5-1 [27.1kB] Get:87 http://ftpmaster.internal/ubuntu/ lucid/main libcairo2 1.8.10-2ubuntu1 [518kB] Get:88 http://ftpmaster.internal/ubuntu/ lucid-security/main libavahi-common-data 0.6.25-1ubuntu6.2 [34.2kB] Get:89 http://ftpmaster.internal/ubuntu/ lucid-security/main libavahi-common3 0.6.25-1ubuntu6.2 [23.5kB] Get:90 http://ftpmaster.internal/ubuntu/ lucid-security/main libavahi-client3 0.6.25-1ubuntu6.2 [54.2kB] Get:91 http://ftpmaster.internal/ubuntu/ lucid-security/main libcups2 1.4.3-1ubuntu1.5 [218kB] Get:92 http://ftpmaster.internal/ubuntu/ lucid/main libjpeg62 6b-15ubuntu1 [88.0kB] Get:93 http://ftpmaster.internal/ubuntu/ lucid/main libjasper1 1.900.1-7 [143kB] Get:94 http://ftpmaster.internal/ubuntu/ lucid-security/main libpango1.0-common 1.28.0-0ubuntu2.2 [111kB] Get:95 http://ftpmaster.internal/ubuntu/ lucid/main libdatrie1 0.2.2-3 [24.5kB] Get:96 http://ftpmaster.internal/ubuntu/ lucid/main libthai-data 0.1.13-1build1 [196kB] Get:97 http://ftpmaster.internal/ubuntu/ lucid/main libthai0 0.1.13-1build1 [39.6kB] Get:98 http://ftpmaster.internal/ubuntu/ lucid/main libxft2 2.1.14-1ubuntu1 [51.9kB] Get:99 http://ftpmaster.internal/ubuntu/ lucid-security/main libpango1.0-0 1.28.0-0ubuntu2.2 [298kB] Get:100 http://ftpmaster.internal/ubuntu/ lucid-security/main libtiff4 3.9.2-2ubuntu0.7 [137kB] Get:101 http://ftpmaster.internal/ubuntu/ lucid/main libxcursor1 1:1.1.10-1 [24.2kB] Get:102 http://ftpmaster.internal/ubuntu/ lucid/main libxdamage1 1:1.1.2-1 [11.7kB] Get:103 http://ftpmaster.internal/ubuntu/ lucid/main libxi6 2:1.3-3 [54.4kB] Get:104 http://ftpmaster.internal/ubuntu/ lucid/main libxinerama1 2:1.1-2 [12.0kB] Get:105 http://ftpmaster.internal/ubuntu/ lucid/main libxrandr2 2:1.3.0-3 [26.6kB] Get:106 http://ftpmaster.internal/ubuntu/ lucid/main shared-mime-info 0.71-1ubuntu2 [428kB] Get:107 http://ftpmaster.internal/ubuntu/ lucid-updates/main libgtk2.0-0 2.20.1-0ubuntu2 [2514kB] Get:108 http://ftpmaster.internal/ubuntu/ lucid-updates/main libgtk2.0-bin 2.20.1-0ubuntu2 [337kB] Get:109 http://ftpmaster.internal/ubuntu/ lucid/main libgsf-1-common 1.14.16-1ubuntu1 [58.5kB] Get:110 http://ftpmaster.internal/ubuntu/ lucid/main libgsf-1-114 1.14.16-1ubuntu1 [155kB] Get:111 http://ftpmaster.internal/ubuntu/ lucid-security/main librsvg2-2 2.26.3-0ubuntu1.1 [107kB] Get:112 http://ftpmaster.internal/ubuntu/ lucid-security/main librsvg2-common 2.26.3-0ubuntu1.1 [18.2kB] Get:113 http://ftpmaster.internal/ubuntu/ lucid/main gnome-icon-theme 2.28.0-1ubuntu1 [3626kB] Get:114 http://ftpmaster.internal/ubuntu/ lucid/main intltool 0.41.0-0ubuntu1 [52.5kB] Get:115 http://ftpmaster.internal/ubuntu/ lucid/main pkg-config 0.22-1build2 [52.9kB] Get:116 http://ftpmaster.internal/ubuntu/ lucid/main zlib1g-dev 1:1.2.3.3.dfsg-15ubuntu1 [162kB] Get:117 http://ftpmaster.internal/ubuntu/ lucid-updates/main libglib2.0-dev 2.24.1-0ubuntu1 [1123kB] Get:118 http://ftpmaster.internal/ubuntu/ lucid-updates/main libatk1.0-dev 1.30.0-0ubuntu2.1 [106kB] Get:119 http://ftpmaster.internal/ubuntu/ lucid/main libexpat1-dev 2.0.1-7ubuntu1 [213kB] Get:120 http://ftpmaster.internal/ubuntu/ lucid-security/main libfreetype6-dev 2.3.11-1ubuntu2.4 [705kB] Get:121 http://ftpmaster.internal/ubuntu/ lucid/main libfontconfig1-dev 2.8.0-2ubuntu1 [820kB] Get:122 http://ftpmaster.internal/ubuntu/ lucid/main x11proto-render-dev 2:0.11-1 [7404B] Get:123 http://ftpmaster.internal/ubuntu/ lucid/main libxrender-dev 1:0.9.5-1 [34.5kB] Get:124 http://ftpmaster.internal/ubuntu/ lucid-security/main libpng12-dev 1.2.42-1ubuntu2.2 [262kB] Get:125 http://ftpmaster.internal/ubuntu/ lucid/main libdirectfb-extra 1.2.8-5ubuntu2 [32.8kB] Get:126 http://ftpmaster.internal/ubuntu/ lucid/main libjpeg62-dev 6b-15ubuntu1 [188kB] Get:127 http://ftpmaster.internal/ubuntu/ lucid/main libsysfs-dev 2.1.0-6 [34.6kB] Get:128 http://ftpmaster.internal/ubuntu/ lucid/main libdirectfb-dev 1.2.8-5ubuntu2 [818kB] Get:129 http://ftpmaster.internal/ubuntu/ lucid/main libsm6 2:1.1.1-1 [24.3kB] Get:130 http://ftpmaster.internal/ubuntu/ lucid/main libsm-dev 2:1.1.1-1 [26.6kB] Get:131 http://ftpmaster.internal/ubuntu/ lucid/main libpixman-1-dev 0.16.4-1ubuntu2 [261kB] Get:132 http://ftpmaster.internal/ubuntu/ lucid/main libxcb-render0-dev 1.5-2 [21.8kB] Get:133 http://ftpmaster.internal/ubuntu/ lucid/main libxcb-render-util0-dev 0.3.6-1build1 [7176B] Get:134 http://ftpmaster.internal/ubuntu/ lucid/main libcairo2-dev 1.8.10-2ubuntu1 [592kB] Get:135 http://ftpmaster.internal/ubuntu/ lucid-security/main libdbus-1-dev 1.2.16-2ubuntu4.3 [25.3kB] Get:136 http://ftpmaster.internal/ubuntu/ lucid-security/main libdbus-glib-1-dev 0.84-1ubuntu0.2 [98.3kB] Get:137 http://ftpmaster.internal/ubuntu/ lucid/main libidl-dev 0.8.13-1 [84.0kB] Get:138 http://ftpmaster.internal/ubuntu/ lucid/main liborbit2-dev 1:2.14.18-0.1 [378kB] Get:139 http://ftpmaster.internal/ubuntu/ lucid/main libgconf2-dev 2.28.1-0ubuntu1 [221kB] Get:140 http://ftpmaster.internal/ubuntu/ lucid/main libgstreamer0.10-0 0.10.28-1 [637kB] Get:141 http://ftpmaster.internal/ubuntu/ lucid-security/main libxml2-dev 2.7.6.dfsg-1ubuntu1.2 [753kB] Get:142 http://ftpmaster.internal/ubuntu/ lucid/main libgstreamer0.10-dev 0.10.28-1 [886kB] Get:143 http://ftpmaster.internal/ubuntu/ lucid/main libxft-dev 2.1.14-1ubuntu1 [65.1kB] Get:144 http://ftpmaster.internal/ubuntu/ lucid-security/main libpango1.0-dev 1.28.0-0ubuntu2.2 [422kB] Get:145 http://ftpmaster.internal/ubuntu/ lucid/main x11proto-xinerama-dev 1.2-2 [4782B] Get:146 http://ftpmaster.internal/ubuntu/ lucid/main libxinerama-dev 2:1.1-2 [14.5kB] Get:147 http://ftpmaster.internal/ubuntu/ lucid/main libxi-dev 2:1.3-3 [134kB] Get:148 http://ftpmaster.internal/ubuntu/ lucid/main x11proto-randr-dev 1.3.1-1 [38.2kB] Get:149 http://ftpmaster.internal/ubuntu/ lucid/main libxrandr-dev 2:1.3.0-3 [33.7kB] Get:150 http://ftpmaster.internal/ubuntu/ lucid/main libxcursor-dev 1:1.1.10-1 [31.4kB] Get:151 http://ftpmaster.internal/ubuntu/ lucid/main x11proto-damage-dev 1:1.2.0-1 [10.2kB] Get:152 http://ftpmaster.internal/ubuntu/ lucid/main libxdamage-dev 1:1.1.2-1 [11.5kB] Get:153 http://ftpmaster.internal/ubuntu/ lucid-security/main libxml2-utils 2.7.6.dfsg-1ubuntu1.2 [89.3kB] Get:154 http://ftpmaster.internal/ubuntu/ lucid-updates/main libgtk2.0-dev 2.20.1-0ubuntu2 [3768kB] Get:155 http://ftpmaster.internal/ubuntu/ lucid-updates/main libnotify1 0.4.5-1ubuntu4 [20.3kB] Get:156 http://ftpmaster.internal/ubuntu/ lucid-updates/main libnotify-dev 0.4.5-1ubuntu4 [15.9kB] Get:157 http://ftpmaster.internal/ubuntu/ lucid/main libunique-1.0-0 1.1.6-1ubuntu2 [22.9kB] Get:158 http://ftpmaster.internal/ubuntu/ lucid/main libunique-dev 1.1.6-1ubuntu2 [29.9kB] debconf: delaying package configuration, since apt-utils is not installed Fetched 46.7MB in 6s (6933kB/s) Selecting previously deselected package x11-common. (Reading database ... 13427 files and directories currently installed.) Unpacking x11-common (from .../x11-common_1%3a7.5+5ubuntu1_all.deb) ... Selecting previously deselected package libice6. Unpacking libice6 (from .../libice6_2%3a1.0.6-1_i386.deb) ... Selecting previously deselected package x11proto-core-dev. Unpacking x11proto-core-dev (from .../x11proto-core-dev_7.0.16-1_all.deb) ... Setting up x11-common (1:7.5+5ubuntu1) ... Selecting previously deselected package libice-dev. (Reading database ... 13547 files and directories currently installed.) Unpacking libice-dev (from .../libice-dev_2%3a1.0.6-1_i386.deb) ... Selecting previously deselected package libxau6. Unpacking libxau6 (from .../libxau6_1%3a1.0.5-1_i386.deb) ... Selecting previously deselected package libxdmcp6. Unpacking libxdmcp6 (from .../libxdmcp6_1%3a1.0.3-1_i386.deb) ... Selecting previously deselected package libxcb1. Unpacking libxcb1 (from .../libxcb1_1.5-2_i386.deb) ... Selecting previously deselected package libx11-data. Unpacking libx11-data (from .../libx11-data_2%3a1.3.2-1ubuntu3_all.deb) ... Selecting previously deselected package libx11-6. Unpacking libx11-6 (from .../libx11-6_2%3a1.3.2-1ubuntu3_i386.deb) ... Selecting previously deselected package libxau-dev. Unpacking libxau-dev (from .../libxau-dev_1%3a1.0.5-1_i386.deb) ... Selecting previously deselected package libxdmcp-dev. Unpacking libxdmcp-dev (from .../libxdmcp-dev_1%3a1.0.3-1_i386.deb) ... Selecting previously deselected package x11proto-input-dev. Unpacking x11proto-input-dev (from .../x11proto-input-dev_2.0-2_all.deb) ... Selecting previously deselected package x11proto-kb-dev. Unpacking x11proto-kb-dev (from .../x11proto-kb-dev_1.0.4-1_all.deb) ... Selecting previously deselected package xtrans-dev. Unpacking xtrans-dev (from .../xtrans-dev_1.2.5-1_all.deb) ... Selecting previously deselected package libpthread-stubs0. Unpacking libpthread-stubs0 (from .../libpthread-stubs0_0.3-2_i386.deb) ... Selecting previously deselected package libpthread-stubs0-dev. Unpacking libpthread-stubs0-dev (from .../libpthread-stubs0-dev_0.3-2_i386.deb) ... Selecting previously deselected package libxcb1-dev. Unpacking libxcb1-dev (from .../libxcb1-dev_1.5-2_i386.deb) ... Selecting previously deselected package libx11-dev. Unpacking libx11-dev (from .../libx11-dev_2%3a1.3.2-1ubuntu3_i386.deb) ... Selecting previously deselected package libxext6. Unpacking libxext6 (from .../libxext6_2%3a1.1.1-2_i386.deb) ... Selecting previously deselected package libxfixes3. Unpacking libxfixes3 (from .../libxfixes3_1%3a4.0.4-1_i386.deb) ... Selecting previously deselected package libxcomposite1. Unpacking libxcomposite1 (from .../libxcomposite1_1%3a0.4.1-1_i386.deb) ... Selecting previously deselected package x11proto-xext-dev. Unpacking x11proto-xext-dev (from .../x11proto-xext-dev_7.1.1-2_all.deb) ... Selecting previously deselected package x11proto-fixes-dev. Unpacking x11proto-fixes-dev (from .../x11proto-fixes-dev_1%3a4.1.1-2_all.deb) ... Selecting previously deselected package libxfixes-dev. Unpacking libxfixes-dev (from .../libxfixes-dev_1%3a4.0.4-1_i386.deb) ... Selecting previously deselected package x11proto-composite-dev. Unpacking x11proto-composite-dev (from .../x11proto-composite-dev_1%3a0.4.1-1_all.deb) ... Selecting previously deselected package libxext-dev. Unpacking libxext-dev (from .../libxext-dev_2%3a1.1.1-2_i386.deb) ... Selecting previously deselected package libxcomposite-dev. Unpacking libxcomposite-dev (from .../libxcomposite-dev_1%3a0.4.1-1_i386.deb) ... Selecting previously deselected package libmagic1. Unpacking libmagic1 (from .../libmagic1_5.03-5ubuntu1_i386.deb) ... Selecting previously deselected package file. Unpacking file (from .../file_5.03-5ubuntu1_i386.deb) ... Selecting previously deselected package libncursesw5. Unpacking libncursesw5 (from .../libncursesw5_5.7+20090803-2ubuntu3_i386.deb) ... Selecting previously deselected package libnewt0.52. Unpacking libnewt0.52 (from .../libnewt0.52_0.52.10-5ubuntu1_i386.deb) ... Selecting previously deselected package libpopt0. Unpacking libpopt0 (from .../libpopt0_1.15-1_i386.deb) ... Selecting previously deselected package libsqlite3-0. Unpacking libsqlite3-0 (from .../libsqlite3-0_3.6.22-1_i386.deb) ... Selecting previously deselected package mime-support. Unpacking mime-support (from .../mime-support_3.48-1ubuntu1_all.deb) ... Selecting previously deselected package python2.6. Unpacking python2.6 (from .../python2.6_2.6.5-1ubuntu6_i386.deb) ... Selecting previously deselected package python. Unpacking python (from .../python_2.6.5-0ubuntu1_all.deb) ... Selecting previously deselected package ucf. Unpacking ucf (from .../archives/ucf_3.0025_all.deb) ... Moving old data out of the way Selecting previously deselected package whiptail. Unpacking whiptail (from .../whiptail_0.52.10-5ubuntu1_i386.deb) ... Selecting previously deselected package bsdmainutils. Unpacking bsdmainutils (from .../bsdmainutils_8.0.1ubuntu1_i386.deb) ... Selecting previously deselected package gettext-base. Unpacking gettext-base (from .../gettext-base_0.17-8ubuntu3_i386.deb) ... Selecting previously deselected package groff-base. Unpacking groff-base (from .../groff-base_1.20.1-7_i386.deb) ... Selecting previously deselected package libexpat1. Unpacking libexpat1 (from .../libexpat1_2.0.1-7ubuntu1_i386.deb) ... Selecting previously deselected package liburi-perl. Unpacking liburi-perl (from .../liburi-perl_1.52-1_all.deb) ... Selecting previously deselected package libhtml-tagset-perl. Unpacking libhtml-tagset-perl (from .../libhtml-tagset-perl_3.20-2_all.deb) ... Selecting previously deselected package libhtml-parser-perl. Unpacking libhtml-parser-perl (from .../libhtml-parser-perl_3.64-1_i386.deb) ... Selecting previously deselected package libhtml-tree-perl. Unpacking libhtml-tree-perl (from .../libhtml-tree-perl_3.23-1_all.deb) ... Selecting previously deselected package libwww-perl. Unpacking libwww-perl (from .../libwww-perl_5.834-1ubuntu0.1_all.deb) ... Selecting previously deselected package libxml-parser-perl. Unpacking libxml-parser-perl (from .../libxml-parser-perl_2.36-1.1build3_i386.deb) ... Selecting previously deselected package libxml2. Unpacking libxml2 (from .../libxml2_2.7.6.dfsg-1ubuntu1.2_i386.deb) ... Selecting previously deselected package man-db. Unpacking man-db (from .../man-db_2.5.7-2ubuntu1_i386.deb) ... Selecting previously deselected package psmisc. Unpacking psmisc (from .../psmisc_22.10-1_i386.deb) ... Selecting previously deselected package m4. Unpacking m4 (from .../archives/m4_1.4.13-3_i386.deb) ... Selecting previously deselected package autoconf. Unpacking autoconf (from .../autoconf_2.65-3ubuntu1_all.deb) ... Selecting previously deselected package autotools-dev. Unpacking autotools-dev (from .../autotools-dev_20090611.1_all.deb) ... Selecting previously deselected package automake. Unpacking automake (from .../automake_1%3a1.11.1-1_all.deb) ... Selecting previously deselected package dbus. Unpacking dbus (from .../dbus_1.2.16-2ubuntu4.3_i386.deb) ... Selecting previously deselected package dbus-x11. Unpacking dbus-x11 (from .../dbus-x11_1.2.16-2ubuntu4.3_i386.deb) ... Selecting previously deselected package html2text. Unpacking html2text (from .../html2text_1.3.2a-14build1_i386.deb) ... Selecting previously deselected package libcroco3. Unpacking libcroco3 (from .../libcroco3_0.6.2-1_i386.deb) ... Selecting previously deselected package gettext. Unpacking gettext (from .../gettext_0.17-8ubuntu3_i386.deb) ... Selecting previously deselected package intltool-debian. Unpacking intltool-debian (from .../intltool-debian_0.35.0+20060710.1_all.deb) ... Selecting previously deselected package po-debconf. Unpacking po-debconf (from .../po-debconf_1.0.16_all.deb) ... Selecting previously deselected package debhelper. Unpacking debhelper (from .../debhelper_7.4.15ubuntu1_all.deb) ... Selecting previously deselected package defoma. Unpacking defoma (from .../defoma_0.11.10-4ubuntu1_all.deb) ... Selecting previously deselected package libfreetype6. Unpacking libfreetype6 (from .../libfreetype6_2.3.11-1ubuntu2.4_i386.deb) ... Selecting previously deselected package ttf-dejavu-core. Unpacking ttf-dejavu-core (from .../ttf-dejavu-core_2.30-2_all.deb) ... Selecting previously deselected package fontconfig-config. Unpacking fontconfig-config (from .../fontconfig-config_2.8.0-2ubuntu1_all.deb) ... Selecting previously deselected package libfontconfig1. Unpacking libfontconfig1 (from .../libfontconfig1_2.8.0-2ubuntu1_i386.deb) ... Selecting previously deselected package fontconfig. Unpacking fontconfig (from .../fontconfig_2.8.0-2ubuntu1_i386.deb) ... Selecting previously deselected package libdbus-glib-1-2. Unpacking libdbus-glib-1-2 (from .../libdbus-glib-1-2_0.84-1ubuntu0.2_i386.deb) ... Selecting previously deselected package libidl0. Unpacking libidl0 (from .../libidl0_0.8.13-1_i386.deb) ... Selecting previously deselected package liborbit2. Unpacking liborbit2 (from .../liborbit2_1%3a2.14.18-0.1_i386.deb) ... Selecting previously deselected package gconf2-common. Unpacking gconf2-common (from .../gconf2-common_2.28.1-0ubuntu1_all.deb) ... Selecting previously deselected package libgconf2-4. Unpacking libgconf2-4 (from .../libgconf2-4_2.28.1-0ubuntu1_i386.deb) ... Selecting previously deselected package gconf2. Unpacking gconf2 (from .../gconf2_2.28.1-0ubuntu1_i386.deb) ... Selecting previously deselected package hicolor-icon-theme. Unpacking hicolor-icon-theme (from .../hicolor-icon-theme_0.11-1_all.deb) ... Selecting previously deselected package libgtk2.0-common. Unpacking libgtk2.0-common (from .../libgtk2.0-common_2.20.1-0ubuntu2_all.deb) ... Selecting previously deselected package libatk1.0-0. Unpacking libatk1.0-0 (from .../libatk1.0-0_1.30.0-0ubuntu2.1_i386.deb) ... Selecting previously deselected package libsysfs2. Unpacking libsysfs2 (from .../libsysfs2_2.1.0-6_i386.deb) ... Selecting previously deselected package tsconf. Unpacking tsconf (from .../tsconf_1.0-7build1_all.deb) ... Selecting previously deselected package libts-0.0-0. Unpacking libts-0.0-0 (from .../libts-0.0-0_1.0-7build1_i386.deb) ... Selecting previously deselected package libdirectfb-1.2-0. Unpacking libdirectfb-1.2-0 (from .../libdirectfb-1.2-0_1.2.8-5ubuntu2_i386.deb) ... Selecting previously deselected package libpixman-1-0. Unpacking libpixman-1-0 (from .../libpixman-1-0_0.16.4-1ubuntu2_i386.deb) ... Selecting previously deselected package libxcb-render0. Unpacking libxcb-render0 (from .../libxcb-render0_1.5-2_i386.deb) ... Selecting previously deselected package libxcb-render-util0. Unpacking libxcb-render-util0 (from .../libxcb-render-util0_0.3.6-1build1_i386.deb) ... Selecting previously deselected package libxrender1. Unpacking libxrender1 (from .../libxrender1_1%3a0.9.5-1_i386.deb) ... Selecting previously deselected package libcairo2. Unpacking libcairo2 (from .../libcairo2_1.8.10-2ubuntu1_i386.deb) ... Selecting previously deselected package libavahi-common-data. Unpacking libavahi-common-data (from .../libavahi-common-data_0.6.25-1ubuntu6.2_i386.deb) ... Selecting previously deselected package libavahi-common3. Unpacking libavahi-common3 (from .../libavahi-common3_0.6.25-1ubuntu6.2_i386.deb) ... Selecting previously deselected package libavahi-client3. Unpacking libavahi-client3 (from .../libavahi-client3_0.6.25-1ubuntu6.2_i386.deb) ... Selecting previously deselected package libcups2. Unpacking libcups2 (from .../libcups2_1.4.3-1ubuntu1.5_i386.deb) ... Selecting previously deselected package libjpeg62. Unpacking libjpeg62 (from .../libjpeg62_6b-15ubuntu1_i386.deb) ... Selecting previously deselected package libjasper1. Unpacking libjasper1 (from .../libjasper1_1.900.1-7_i386.deb) ... Selecting previously deselected package libpango1.0-common. Unpacking libpango1.0-common (from .../libpango1.0-common_1.28.0-0ubuntu2.2_all.deb) ... Selecting previously deselected package libdatrie1. Unpacking libdatrie1 (from .../libdatrie1_0.2.2-3_i386.deb) ... Selecting previously deselected package libthai-data. Unpacking libthai-data (from .../libthai-data_0.1.13-1build1_all.deb) ... Selecting previously deselected package libthai0. Unpacking libthai0 (from .../libthai0_0.1.13-1build1_i386.deb) ... Selecting previously deselected package libxft2. Unpacking libxft2 (from .../libxft2_2.1.14-1ubuntu1_i386.deb) ... Selecting previously deselected package libpango1.0-0. Unpacking libpango1.0-0 (from .../libpango1.0-0_1.28.0-0ubuntu2.2_i386.deb) ... Selecting previously deselected package libtiff4. Unpacking libtiff4 (from .../libtiff4_3.9.2-2ubuntu0.7_i386.deb) ... Selecting previously deselected package libxcursor1. Unpacking libxcursor1 (from .../libxcursor1_1%3a1.1.10-1_i386.deb) ... Selecting previously deselected package libxdamage1. Unpacking libxdamage1 (from .../libxdamage1_1%3a1.1.2-1_i386.deb) ... Selecting previously deselected package libxi6. Unpacking libxi6 (from .../libxi6_2%3a1.3-3_i386.deb) ... Selecting previously deselected package libxinerama1. Unpacking libxinerama1 (from .../libxinerama1_2%3a1.1-2_i386.deb) ... Selecting previously deselected package libxrandr2. Unpacking libxrandr2 (from .../libxrandr2_2%3a1.3.0-3_i386.deb) ... Selecting previously deselected package shared-mime-info. Unpacking shared-mime-info (from .../shared-mime-info_0.71-1ubuntu2_i386.deb) ... Selecting previously deselected package libgtk2.0-0. Unpacking libgtk2.0-0 (from .../libgtk2.0-0_2.20.1-0ubuntu2_i386.deb) ... Selecting previously deselected package libgtk2.0-bin. Unpacking libgtk2.0-bin (from .../libgtk2.0-bin_2.20.1-0ubuntu2_all.deb) ... Selecting previously deselected package libgsf-1-common. Unpacking libgsf-1-common (from .../libgsf-1-common_1.14.16-1ubuntu1_all.deb) ... Selecting previously deselected package libgsf-1-114. Unpacking libgsf-1-114 (from .../libgsf-1-114_1.14.16-1ubuntu1_i386.deb) ... Selecting previously deselected package librsvg2-2. Unpacking librsvg2-2 (from .../librsvg2-2_2.26.3-0ubuntu1.1_i386.deb) ... Selecting previously deselected package librsvg2-common. Unpacking librsvg2-common (from .../librsvg2-common_2.26.3-0ubuntu1.1_i386.deb) ... Selecting previously deselected package gnome-icon-theme. Unpacking gnome-icon-theme (from .../gnome-icon-theme_2.28.0-1ubuntu1_all.deb) ... Selecting previously deselected package intltool. Unpacking intltool (from .../intltool_0.41.0-0ubuntu1_all.deb) ... Selecting previously deselected package pkg-config. Unpacking pkg-config (from .../pkg-config_0.22-1build2_i386.deb) ... Selecting previously deselected package zlib1g-dev. Unpacking zlib1g-dev (from .../zlib1g-dev_1%3a1.2.3.3.dfsg-15ubuntu1_i386.deb) ... Selecting previously deselected package libglib2.0-dev. Unpacking libglib2.0-dev (from .../libglib2.0-dev_2.24.1-0ubuntu1_i386.deb) ... Selecting previously deselected package libatk1.0-dev. Unpacking libatk1.0-dev (from .../libatk1.0-dev_1.30.0-0ubuntu2.1_i386.deb) ... Selecting previously deselected package libexpat1-dev. Unpacking libexpat1-dev (from .../libexpat1-dev_2.0.1-7ubuntu1_i386.deb) ... Selecting previously deselected package libfreetype6-dev. Unpacking libfreetype6-dev (from .../libfreetype6-dev_2.3.11-1ubuntu2.4_i386.deb) ... Selecting previously deselected package libfontconfig1-dev. Unpacking libfontconfig1-dev (from .../libfontconfig1-dev_2.8.0-2ubuntu1_i386.deb) ... Selecting previously deselected package x11proto-render-dev. Unpacking x11proto-render-dev (from .../x11proto-render-dev_2%3a0.11-1_all.deb) ... Selecting previously deselected package libxrender-dev. Unpacking libxrender-dev (from .../libxrender-dev_1%3a0.9.5-1_i386.deb) ... Selecting previously deselected package libpng12-dev. Unpacking libpng12-dev (from .../libpng12-dev_1.2.42-1ubuntu2.2_i386.deb) ... Selecting previously deselected package libdirectfb-extra. Unpacking libdirectfb-extra (from .../libdirectfb-extra_1.2.8-5ubuntu2_i386.deb) ... Selecting previously deselected package libjpeg62-dev. Unpacking libjpeg62-dev (from .../libjpeg62-dev_6b-15ubuntu1_i386.deb) ... Selecting previously deselected package libsysfs-dev. Unpacking libsysfs-dev (from .../libsysfs-dev_2.1.0-6_i386.deb) ... Selecting previously deselected package libdirectfb-dev. Unpacking libdirectfb-dev (from .../libdirectfb-dev_1.2.8-5ubuntu2_i386.deb) ... Selecting previously deselected package libsm6. Unpacking libsm6 (from .../libsm6_2%3a1.1.1-1_i386.deb) ... Selecting previously deselected package libsm-dev. Unpacking libsm-dev (from .../libsm-dev_2%3a1.1.1-1_i386.deb) ... Selecting previously deselected package libpixman-1-dev. Unpacking libpixman-1-dev (from .../libpixman-1-dev_0.16.4-1ubuntu2_i386.deb) ... Selecting previously deselected package libxcb-render0-dev. Unpacking libxcb-render0-dev (from .../libxcb-render0-dev_1.5-2_i386.deb) ... Selecting previously deselected package libxcb-render-util0-dev. Unpacking libxcb-render-util0-dev (from .../libxcb-render-util0-dev_0.3.6-1build1_i386.deb) ... Selecting previously deselected package libcairo2-dev. Unpacking libcairo2-dev (from .../libcairo2-dev_1.8.10-2ubuntu1_i386.deb) ... Selecting previously deselected package libdbus-1-dev. Unpacking libdbus-1-dev (from .../libdbus-1-dev_1.2.16-2ubuntu4.3_i386.deb) ... Selecting previously deselected package libdbus-glib-1-dev. Unpacking libdbus-glib-1-dev (from .../libdbus-glib-1-dev_0.84-1ubuntu0.2_i386.deb) ... Selecting previously deselected package libidl-dev. Unpacking libidl-dev (from .../libidl-dev_0.8.13-1_i386.deb) ... Selecting previously deselected package liborbit2-dev. Unpacking liborbit2-dev (from .../liborbit2-dev_1%3a2.14.18-0.1_i386.deb) ... Selecting previously deselected package libgconf2-dev. Unpacking libgconf2-dev (from .../libgconf2-dev_2.28.1-0ubuntu1_i386.deb) ... Selecting previously deselected package libgstreamer0.10-0. Unpacking libgstreamer0.10-0 (from .../libgstreamer0.10-0_0.10.28-1_i386.deb) ... Selecting previously deselected package libxml2-dev. Unpacking libxml2-dev (from .../libxml2-dev_2.7.6.dfsg-1ubuntu1.2_i386.deb) ... Selecting previously deselected package libgstreamer0.10-dev. Unpacking libgstreamer0.10-dev (from .../libgstreamer0.10-dev_0.10.28-1_i386.deb) ... Selecting previously deselected package libxft-dev. Unpacking libxft-dev (from .../libxft-dev_2.1.14-1ubuntu1_i386.deb) ... Selecting previously deselected package libpango1.0-dev. Unpacking libpango1.0-dev (from .../libpango1.0-dev_1.28.0-0ubuntu2.2_i386.deb) ... Selecting previously deselected package x11proto-xinerama-dev. Unpacking x11proto-xinerama-dev (from .../x11proto-xinerama-dev_1.2-2_all.deb) ... Selecting previously deselected package libxinerama-dev. Unpacking libxinerama-dev (from .../libxinerama-dev_2%3a1.1-2_i386.deb) ... Selecting previously deselected package libxi-dev. Unpacking libxi-dev (from .../libxi-dev_2%3a1.3-3_i386.deb) ... Selecting previously deselected package x11proto-randr-dev. Unpacking x11proto-randr-dev (from .../x11proto-randr-dev_1.3.1-1_all.deb) ... Selecting previously deselected package libxrandr-dev. Unpacking libxrandr-dev (from .../libxrandr-dev_2%3a1.3.0-3_i386.deb) ... Selecting previously deselected package libxcursor-dev. Unpacking libxcursor-dev (from .../libxcursor-dev_1%3a1.1.10-1_i386.deb) ... Selecting previously deselected package x11proto-damage-dev. Unpacking x11proto-damage-dev (from .../x11proto-damage-dev_1%3a1.2.0-1_all.deb) ... Selecting previously deselected package libxdamage-dev. Unpacking libxdamage-dev (from .../libxdamage-dev_1%3a1.1.2-1_i386.deb) ... Selecting previously deselected package libxml2-utils. Unpacking libxml2-utils (from .../libxml2-utils_2.7.6.dfsg-1ubuntu1.2_i386.deb) ... Selecting previously deselected package libgtk2.0-dev. Unpacking libgtk2.0-dev (from .../libgtk2.0-dev_2.20.1-0ubuntu2_i386.deb) ... Selecting previously deselected package libnotify1. Unpacking libnotify1 (from .../libnotify1_0.4.5-1ubuntu4_i386.deb) ... Selecting previously deselected package libnotify-dev. Unpacking libnotify-dev (from .../libnotify-dev_0.4.5-1ubuntu4_i386.deb) ... Selecting previously deselected package libunique-1.0-0. Unpacking libunique-1.0-0 (from .../libunique-1.0-0_1.1.6-1ubuntu2_i386.deb) ... Selecting previously deselected package libunique-dev. Unpacking libunique-dev (from .../libunique-dev_1.1.6-1ubuntu2_i386.deb) ... Setting up libice6 (2:1.0.6-1) ... Setting up x11proto-core-dev (7.0.16-1) ... Setting up libice-dev (2:1.0.6-1) ... Setting up libxau6 (1:1.0.5-1) ... Setting up libxdmcp6 (1:1.0.3-1) ... Setting up libxcb1 (1.5-2) ... Setting up libx11-data (2:1.3.2-1ubuntu3) ... Setting up libx11-6 (2:1.3.2-1ubuntu3) ... Setting up libxau-dev (1:1.0.5-1) ... Setting up libxdmcp-dev (1:1.0.3-1) ... Setting up x11proto-input-dev (2.0-2) ... Setting up x11proto-kb-dev (1.0.4-1) ... Setting up xtrans-dev (1.2.5-1) ... Setting up libpthread-stubs0 (0.3-2) ... Setting up libpthread-stubs0-dev (0.3-2) ... Setting up libxcb1-dev (1.5-2) ... Setting up libx11-dev (2:1.3.2-1ubuntu3) ... Setting up libxext6 (2:1.1.1-2) ... Setting up libxfixes3 (1:4.0.4-1) ... Setting up libxcomposite1 (1:0.4.1-1) ... Setting up x11proto-xext-dev (7.1.1-2) ... Setting up x11proto-fixes-dev (1:4.1.1-2) ... Setting up libxfixes-dev (1:4.0.4-1) ... Setting up x11proto-composite-dev (1:0.4.1-1) ... Setting up libxext-dev (2:1.1.1-2) ... Setting up libxcomposite-dev (1:0.4.1-1) ... Setting up libmagic1 (5.03-5ubuntu1) ... Setting up file (5.03-5ubuntu1) ... Setting up libncursesw5 (5.7+20090803-2ubuntu3) ... Setting up libnewt0.52 (0.52.10-5ubuntu1) ... Setting up libpopt0 (1.15-1) ... Setting up libsqlite3-0 (3.6.22-1) ... Setting up mime-support (3.48-1ubuntu1) ... update-alternatives: using /usr/bin/see to provide /usr/bin/view (view) in auto mode. Setting up python2.6 (2.6.5-1ubuntu6) ... Setting up python (2.6.5-0ubuntu1) ... Setting up ucf (3.0025) ... Setting up whiptail (0.52.10-5ubuntu1) ... Setting up bsdmainutils (8.0.1ubuntu1) ... update-alternatives: using /usr/bin/bsd-write to provide /usr/bin/write (write) in auto mode. Setting up gettext-base (0.17-8ubuntu3) ... Setting up groff-base (1.20.1-7) ... Setting up libexpat1 (2.0.1-7ubuntu1) ... Setting up liburi-perl (1.52-1) ... Setting up libhtml-tagset-perl (3.20-2) ... Setting up libhtml-parser-perl (3.64-1) ... Setting up libhtml-tree-perl (3.23-1) ... Setting up libwww-perl (5.834-1ubuntu0.1) ... Setting up libxml-parser-perl (2.36-1.1build3) ... Setting up libxml2 (2.7.6.dfsg-1ubuntu1.2) ... Setting up man-db (2.5.7-2ubuntu1) ... Building database of manual pages ... Setting up psmisc (22.10-1) ... Setting up m4 (1.4.13-3) ... Setting up autoconf (2.65-3ubuntu1) ... Setting up autotools-dev (20090611.1) ... Setting up automake (1:1.11.1-1) ... update-alternatives: using /usr/bin/automake-1.11 to provide /usr/bin/automake (automake) in auto mode. Setting up dbus (1.2.16-2ubuntu4.3) ... Adding system user `messagebus' (UID 101) ... Adding new group `messagebus' (GID 102) ... Adding new user `messagebus' (UID 101) with group `messagebus' ... Not creating home directory `/var/run/dbus'. Setting up dbus-x11 (1.2.16-2ubuntu4.3) ... Setting up html2text (1.3.2a-14build1) ... Setting up libcroco3 (0.6.2-1) ... Setting up gettext (0.17-8ubuntu3) ... Setting up intltool-debian (0.35.0+20060710.1) ... Setting up po-debconf (1.0.16) ... Setting up debhelper (7.4.15ubuntu1) ... Setting up defoma (0.11.10-4ubuntu1) ... Setting up libfreetype6 (2.3.11-1ubuntu2.4) ... Setting up ttf-dejavu-core (2.30-2) ... Setting up fontconfig-config (2.8.0-2ubuntu1) ... Setting up libfontconfig1 (2.8.0-2ubuntu1) ... Setting up fontconfig (2.8.0-2ubuntu1) ... Updating font configuration of fontconfig... Cleaning up category cid.. Cleaning up category truetype.. Cleaning up category type1.. Updating category type1.. Updating category truetype.. Updating category cid.. Cleaning up old fontconfig caches... done. Regenerating fonts cache... done. Setting up libdbus-glib-1-2 (0.84-1ubuntu0.2) ... Setting up libidl0 (0.8.13-1) ... Setting up liborbit2 (1:2.14.18-0.1) ... Setting up gconf2-common (2.28.1-0ubuntu1) ... Creating config file /etc/gconf/2/path with new version Setting up libgconf2-4 (2.28.1-0ubuntu1) ... Setting up gconf2 (2.28.1-0ubuntu1) ... update-alternatives: using /usr/bin/gconftool-2 to provide /usr/bin/gconftool (gconftool) in auto mode. Setting up hicolor-icon-theme (0.11-1) ... Setting up libgtk2.0-common (2.20.1-0ubuntu2) ... Setting up libatk1.0-0 (1.30.0-0ubuntu2.1) ... Setting up libsysfs2 (2.1.0-6) ... Setting up tsconf (1.0-7build1) ... Setting up libts-0.0-0 (1.0-7build1) ... Setting up libdirectfb-1.2-0 (1.2.8-5ubuntu2) ... Setting up libpixman-1-0 (0.16.4-1ubuntu2) ... Setting up libxcb-render0 (1.5-2) ... Setting up libxcb-render-util0 (0.3.6-1build1) ... Setting up libxrender1 (1:0.9.5-1) ... Setting up libcairo2 (1.8.10-2ubuntu1) ... Setting up libavahi-common-data (0.6.25-1ubuntu6.2) ... Setting up libavahi-common3 (0.6.25-1ubuntu6.2) ... Setting up libavahi-client3 (0.6.25-1ubuntu6.2) ... Setting up libcups2 (1.4.3-1ubuntu1.5) ... Setting up libjpeg62 (6b-15ubuntu1) ... Setting up libjasper1 (1.900.1-7) ... Setting up libpango1.0-common (1.28.0-0ubuntu2.2) ... Cleaning up font configuration of pango... Updating font configuration of pango... Cleaning up category xfont.. Updating category xfont.. *** You don't have any defomized font packages. *** So we are trying to force to generate pangox.aliases... Setting up libdatrie1 (0.2.2-3) ... Setting up libthai-data (0.1.13-1build1) ... Setting up libthai0 (0.1.13-1build1) ... Setting up libxft2 (2.1.14-1ubuntu1) ... Setting up libpango1.0-0 (1.28.0-0ubuntu2.2) ... Setting up libtiff4 (3.9.2-2ubuntu0.7) ... Setting up libxcursor1 (1:1.1.10-1) ... Setting up libxdamage1 (1:1.1.2-1) ... Setting up libxi6 (2:1.3-3) ... Setting up libxinerama1 (2:1.1-2) ... Setting up libxrandr2 (2:1.3.0-3) ... Setting up shared-mime-info (0.71-1ubuntu2) ... Setting up libgtk2.0-0 (2.20.1-0ubuntu2) ... Setting up libgtk2.0-bin (2.20.1-0ubuntu2) ... Setting up libgsf-1-common (1.14.16-1ubuntu1) ... Setting up libgsf-1-114 (1.14.16-1ubuntu1) ... Setting up librsvg2-2 (2.26.3-0ubuntu1.1) ... Setting up librsvg2-common (2.26.3-0ubuntu1.1) ... Setting up gnome-icon-theme (2.28.0-1ubuntu1) ... update-alternatives: using /usr/share/icons/gnome/scalable/places/ubuntu-logo.svg to provide /usr/share/icons/gnome/scalable/places/start-here.svg (start-here.svg) in auto mode. Setting up intltool (0.41.0-0ubuntu1) ... Setting up pkg-config (0.22-1build2) ... Setting up zlib1g-dev (1:1.2.3.3.dfsg-15ubuntu1) ... Setting up libglib2.0-dev (2.24.1-0ubuntu1) ... Setting up libatk1.0-dev (1.30.0-0ubuntu2.1) ... Setting up libexpat1-dev (2.0.1-7ubuntu1) ... Setting up libfreetype6-dev (2.3.11-1ubuntu2.4) ... Setting up libfontconfig1-dev (2.8.0-2ubuntu1) ... Setting up x11proto-render-dev (2:0.11-1) ... Setting up libxrender-dev (1:0.9.5-1) ... Setting up libpng12-dev (1.2.42-1ubuntu2.2) ... Setting up libdirectfb-extra (1.2.8-5ubuntu2) ... Setting up libjpeg62-dev (6b-15ubuntu1) ... Setting up libsysfs-dev (2.1.0-6) ... Setting up libdirectfb-dev (1.2.8-5ubuntu2) ... Setting up libsm6 (2:1.1.1-1) ... Setting up libsm-dev (2:1.1.1-1) ... Setting up libpixman-1-dev (0.16.4-1ubuntu2) ... Setting up libxcb-render0-dev (1.5-2) ... Setting up libxcb-render-util0-dev (0.3.6-1build1) ... Setting up libcairo2-dev (1.8.10-2ubuntu1) ... Setting up libdbus-1-dev (1.2.16-2ubuntu4.3) ... Setting up libdbus-glib-1-dev (0.84-1ubuntu0.2) ... Setting up libidl-dev (0.8.13-1) ... Setting up liborbit2-dev (1:2.14.18-0.1) ... Setting up libgconf2-dev (2.28.1-0ubuntu1) ... Setting up libgstreamer0.10-0 (0.10.28-1) ... Setting up libxml2-dev (2.7.6.dfsg-1ubuntu1.2) ... Setting up libgstreamer0.10-dev (0.10.28-1) ... Setting up libxft-dev (2.1.14-1ubuntu1) ... Setting up libpango1.0-dev (1.28.0-0ubuntu2.2) ... Setting up x11proto-xinerama-dev (1.2-2) ... Setting up libxinerama-dev (2:1.1-2) ... Setting up libxi-dev (2:1.3-3) ... Setting up x11proto-randr-dev (1.3.1-1) ... Setting up libxrandr-dev (2:1.3.0-3) ... Setting up libxcursor-dev (1:1.1.10-1) ... Setting up x11proto-damage-dev (1:1.2.0-1) ... Setting up libxdamage-dev (1:1.1.2-1) ... Setting up libxml2-utils (2.7.6.dfsg-1ubuntu1.2) ... Setting up libgtk2.0-dev (2.20.1-0ubuntu2) ... Setting up libnotify1 (0.4.5-1ubuntu4) ... Setting up libnotify-dev (0.4.5-1ubuntu4) ... Setting up libunique-1.0-0 (1.1.6-1ubuntu2) ... Setting up libunique-dev (1.1.6-1ubuntu2) ... Processing triggers for libc-bin ... ldconfig deferred processing now taking place Checking correctness of source dependencies... Toolchain package versions: libc6-dev_2.11.1-0ubuntu7.8 make_3.81-7ubuntu1 dpkg-dev_1.15.5.6ubuntu4.5 g++-4.4_4.4.3-4ubuntu5 gcc-4.4_4.4.3-4ubuntu5 binutils_2.20.1-3ubuntu7.1 libstdc++6_4.4.3-4ubuntu5 libstdc++6-4.4-dev_4.4.3-4ubuntu5 ------------------------------------------------------------------------------ dpkg-source: warning: -sn is not a valid option for Dpkg::Source::Package::V3::quilt gpgv: Signature made Mon Oct 3 04:54:57 2011 UTC using RSA key ID 6E511C31 gpgv: Can't check signature: public key not found dpkg-source: warning: failed to verify signature on ./alarm-clock-applet_0.3.1-1.dsc dpkg-source: info: extracting alarm-clock-applet in alarm-clock-applet-0.3.1 dpkg-source: info: unpacking alarm-clock-applet_0.3.1.orig.tar.gz dpkg-source: info: unpacking alarm-clock-applet_0.3.1-1.debian.tar.gz dpkg-buildpackage: set CFLAGS to default value: -g -O2 dpkg-buildpackage: set CPPFLAGS to default value: dpkg-buildpackage: set LDFLAGS to default value: -Wl,-Bsymbolic-functions dpkg-buildpackage: set FFLAGS to default value: -g -O2 dpkg-buildpackage: set CXXFLAGS to default value: -g -O2 dpkg-buildpackage: source package alarm-clock-applet dpkg-buildpackage: source version 0.3.1-1 dpkg-buildpackage: host architecture i386 /usr/bin/fakeroot debian/rules clean dh clean dh_testdir dh_auto_clean dh_clean debian/rules build dh build dh_testdir dh_auto_configure 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 disable maintainer-specific portions of Makefiles... no checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for style of include used by make... GNU checking dependency style of gcc... none checking whether gcc understands -Wno-sign-compare... yes checking what warning flags to pass to the C compiler... -Wall -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare checking what language compliance flags to pass to the C compiler... checking for BASE... yes checking for GTK... yes checking for GSTREAMER... yes checking for GNOME... yes checking for gconftool-2... /usr/bin/gconftool-2 Using config source xml:merged:/etc/gconf/gconf.xml.defaults for schema installation Using $(sysconfdir)/gconf/schemas as install directory for schema files checking whether NLS is requested... yes checking for intltool >= 0.40.0... 0.41.0 found checking for intltool-update... /usr/bin/intltool-update checking for intltool-merge... /usr/bin/intltool-merge checking for intltool-extract... /usr/bin/intltool-extract checking for xgettext... /usr/bin/xgettext checking for msgmerge... /usr/bin/msgmerge checking for msgfmt... /usr/bin/msgfmt checking for gmsgfmt... /usr/bin/msgfmt checking for perl... /usr/bin/perl checking for perl >= 5.8.1... 5.10.1 checking for XML::Parser... ok checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking locale.h usability... yes checking locale.h presence... yes checking for locale.h... yes checking for LC_MESSAGES... yes checking libintl.h usability... yes checking libintl.h presence... yes checking for libintl.h... yes checking for ngettext in libc... yes checking for dgettext in libc... yes checking for bind_textdomain_codeset... yes checking for msgfmt... (cached) /usr/bin/msgfmt checking for dcgettext... yes checking if msgfmt accepts -c... yes checking for gmsgfmt... (cached) /usr/bin/msgfmt checking for xgettext... (cached) /usr/bin/xgettext configure: creating ./config.status config.status: creating Makefile config.status: creating src/Makefile config.status: creating src/tests/Makefile config.status: creating data/Makefile config.status: creating data/icons/Makefile config.status: creating po/Makefile.in config.status: creating config.h config.status: executing depfiles commands config.status: executing default-1 commands config.status: executing po/stamp-it commands ************************************************* alarm-clock 0.3.1 Configure summary: prefix: /usr source code location: . ************************************************* dh_auto_build make[1]: Entering directory `/build/buildd/alarm-clock-applet-0.3.1' make all-recursive make[2]: Entering directory `/build/buildd/alarm-clock-applet-0.3.1' Making all in src make[3]: Entering directory `/build/buildd/alarm-clock-applet-0.3.1/src' Making all in tests make[4]: Entering directory `/build/buildd/alarm-clock-applet-0.3.1/src/tests' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/build/buildd/alarm-clock-applet-0.3.1/src/tests' make[4]: Entering directory `/build/buildd/alarm-clock-applet-0.3.1/src' CC alarm-applet.o gcc -DHAVE_CONFIG_H -I. -I.. -DALARM_CLOCK_DATADIR=\"/usr/share\" -DALARM_CLOCK_PKGDATADIR=\"/usr/share/alarm-clock-applet\" -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -D_REENTRANT -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -pthread -I/usr/include/gstreamer-0.10 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libxml2 -DORBIT2=1 -pthread -D_REENTRANT -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/libxml2 -I/usr/include/unique-1.0 -Wall -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare -g -O2 -c alarm-applet.c CC player.o gcc -DHAVE_CONFIG_H -I. -I.. -DALARM_CLOCK_DATADIR=\"/usr/share\" -DALARM_CLOCK_PKGDATADIR=\"/usr/share/alarm-clock-applet\" -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -D_REENTRANT -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -pthread -I/usr/include/gstreamer-0.10 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libxml2 -DORBIT2=1 -pthread -D_REENTRANT -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/libxml2 -I/usr/include/unique-1.0 -Wall -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare -g -O2 -c player.c CC util.o gcc -DHAVE_CONFIG_H -I. -I.. -DALARM_CLOCK_DATADIR=\"/usr/share\" -DALARM_CLOCK_PKGDATADIR=\"/usr/share/alarm-clock-applet\" -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -D_REENTRANT -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -pthread -I/usr/include/gstreamer-0.10 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libxml2 -DORBIT2=1 -pthread -D_REENTRANT -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/libxml2 -I/usr/include/unique-1.0 -Wall -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare -g -O2 -c util.c CC list-entry.o gcc -DHAVE_CONFIG_H -I. -I.. -DALARM_CLOCK_DATADIR=\"/usr/share\" -DALARM_CLOCK_PKGDATADIR=\"/usr/share/alarm-clock-applet\" -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -D_REENTRANT -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -pthread -I/usr/include/gstreamer-0.10 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libxml2 -DORBIT2=1 -pthread -D_REENTRANT -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/libxml2 -I/usr/include/unique-1.0 -Wall -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare -g -O2 -c list-entry.c CC alarm.o gcc -DHAVE_CONFIG_H -I. -I.. -DALARM_CLOCK_DATADIR=\"/usr/share\" -DALARM_CLOCK_PKGDATADIR=\"/usr/share/alarm-clock-applet\" -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -D_REENTRANT -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -pthread -I/usr/include/gstreamer-0.10 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libxml2 -DORBIT2=1 -pthread -D_REENTRANT -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/libxml2 -I/usr/include/unique-1.0 -Wall -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare -g -O2 -c alarm.c alarm.c:120: warning: 'AlarmProp' defined but not used alarm.c:144: warning: 'AlarmSignal' defined but not used CC alarm-gconf.o gcc -DHAVE_CONFIG_H -I. -I.. -DALARM_CLOCK_DATADIR=\"/usr/share\" -DALARM_CLOCK_PKGDATADIR=\"/usr/share/alarm-clock-applet\" -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -D_REENTRANT -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -pthread -I/usr/include/gstreamer-0.10 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libxml2 -DORBIT2=1 -pthread -D_REENTRANT -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/libxml2 -I/usr/include/unique-1.0 -Wall -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare -g -O2 -c alarm-gconf.c alarm-applet.h:46: warning: array 'supported_sound_mime_types' assumed to have one element CC ui.o gcc -DHAVE_CONFIG_H -I. -I.. -DALARM_CLOCK_DATADIR=\"/usr/share\" -DALARM_CLOCK_PKGDATADIR=\"/usr/share/alarm-clock-applet\" -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -D_REENTRANT -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -pthread -I/usr/include/gstreamer-0.10 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libxml2 -DORBIT2=1 -pthread -D_REENTRANT -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/libxml2 -I/usr/include/unique-1.0 -Wall -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare -g -O2 -c ui.c alarm-applet.h:46: warning: array 'supported_sound_mime_types' assumed to have one element CC alarm-actions.o gcc -DHAVE_CONFIG_H -I. -I.. -DALARM_CLOCK_DATADIR=\"/usr/share\" -DALARM_CLOCK_PKGDATADIR=\"/usr/share/alarm-clock-applet\" -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -D_REENTRANT -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -pthread -I/usr/include/gstreamer-0.10 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libxml2 -DORBIT2=1 -pthread -D_REENTRANT -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/libxml2 -I/usr/include/unique-1.0 -Wall -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare -g -O2 -c alarm-actions.c alarm-applet.h:46: warning: array 'supported_sound_mime_types' assumed to have one element CC alarm-list-window.o gcc -DHAVE_CONFIG_H -I. -I.. -DALARM_CLOCK_DATADIR=\"/usr/share\" -DALARM_CLOCK_PKGDATADIR=\"/usr/share/alarm-clock-applet\" -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -D_REENTRANT -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -pthread -I/usr/include/gstreamer-0.10 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libxml2 -DORBIT2=1 -pthread -D_REENTRANT -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/libxml2 -I/usr/include/unique-1.0 -Wall -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare -g -O2 -c alarm-list-window.c alarm-applet.h:46: warning: array 'supported_sound_mime_types' assumed to have one element CC alarm-settings.o gcc -DHAVE_CONFIG_H -I. -I.. -DALARM_CLOCK_DATADIR=\"/usr/share\" -DALARM_CLOCK_PKGDATADIR=\"/usr/share/alarm-clock-applet\" -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -D_REENTRANT -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -pthread -I/usr/include/gstreamer-0.10 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libxml2 -DORBIT2=1 -pthread -D_REENTRANT -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/libxml2 -I/usr/include/unique-1.0 -Wall -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare -g -O2 -c alarm-settings.c alarm-applet.h:46: warning: array 'supported_sound_mime_types' assumed to have one element CC prefs.o gcc -DHAVE_CONFIG_H -I. -I.. -DALARM_CLOCK_DATADIR=\"/usr/share\" -DALARM_CLOCK_PKGDATADIR=\"/usr/share/alarm-clock-applet\" -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -D_REENTRANT -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -pthread -I/usr/include/gstreamer-0.10 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libxml2 -DORBIT2=1 -pthread -D_REENTRANT -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/libxml2 -I/usr/include/unique-1.0 -Wall -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare -g -O2 -c prefs.c alarm-applet.h:46: warning: array 'supported_sound_mime_types' assumed to have one element CCLD alarm-clock-applet make[4]: Leaving directory `/build/buildd/alarm-clock-applet-0.3.1/src' make[3]: Leaving directory `/build/buildd/alarm-clock-applet-0.3.1/src' Making all in data make[3]: Entering directory `/build/buildd/alarm-clock-applet-0.3.1/data' Making all in icons make[4]: Entering directory `/build/buildd/alarm-clock-applet-0.3.1/data/icons' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/build/buildd/alarm-clock-applet-0.3.1/data/icons' make[4]: Entering directory `/build/buildd/alarm-clock-applet-0.3.1/data' LC_ALL=C /usr/bin/intltool-merge -d -u -c ../po/.intltool-merge-cache ../po alarm-clock-applet.desktop.in alarm-clock-applet.desktop Generating and caching the translation database Merging translations into alarm-clock-applet.desktop. LC_ALL=C /usr/bin/intltool-merge -s -u -c ../po/.intltool-merge-cache ../po alarm-clock.schemas.in alarm-clock.schemas Found cached translation database Merging translations into alarm-clock.schemas. make[4]: Leaving directory `/build/buildd/alarm-clock-applet-0.3.1/data' make[3]: Leaving directory `/build/buildd/alarm-clock-applet-0.3.1/data' Making all in po make[3]: Entering directory `/build/buildd/alarm-clock-applet-0.3.1/po' file=`echo ar | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file ar.po file=`echo be | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file be.po file=`echo bg | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file bg.po file=`echo ca | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file ca.po file=`echo da | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file da.po file=`echo de | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file de.po file=`echo es | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file es.po file=`echo fi | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file fi.po file=`echo fo | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file fo.po file=`echo fr | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file fr.po file=`echo gl | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file gl.po file=`echo he | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file he.po file=`echo hi | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file hi.po file=`echo hu | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file hu.po file=`echo id | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file id.po file=`echo ja | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file ja.po file=`echo ms | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file ms.po file=`echo nb | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file nb.po file=`echo nn | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file nn.po file=`echo pl | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file pl.po file=`echo pt_BR | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file pt_BR.po file=`echo pt | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file pt.po file=`echo ru | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file ru.po file=`echo zh_CN | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file zh_CN.po make[3]: Leaving directory `/build/buildd/alarm-clock-applet-0.3.1/po' make[3]: Entering directory `/build/buildd/alarm-clock-applet-0.3.1' make[3]: Nothing to be done for `all-am'. make[3]: Leaving directory `/build/buildd/alarm-clock-applet-0.3.1' make[2]: Leaving directory `/build/buildd/alarm-clock-applet-0.3.1' make[1]: Leaving directory `/build/buildd/alarm-clock-applet-0.3.1' # Skipping dh_auto_test - empty override /usr/bin/fakeroot debian/rules binary dh binary dh_testroot dh_prep dh_installdirs debian/rules override_dh_auto_install make[1]: Entering directory `/build/buildd/alarm-clock-applet-0.3.1' dh_auto_install make[2]: Entering directory `/build/buildd/alarm-clock-applet-0.3.1' Making install in src make[3]: Entering directory `/build/buildd/alarm-clock-applet-0.3.1/src' Making install in tests make[4]: Entering directory `/build/buildd/alarm-clock-applet-0.3.1/src/tests' make[5]: Entering directory `/build/buildd/alarm-clock-applet-0.3.1/src/tests' make[5]: Nothing to be done for `install-exec-am'. make[5]: Nothing to be done for `install-data-am'. make[5]: Leaving directory `/build/buildd/alarm-clock-applet-0.3.1/src/tests' make[4]: Leaving directory `/build/buildd/alarm-clock-applet-0.3.1/src/tests' make[4]: Entering directory `/build/buildd/alarm-clock-applet-0.3.1/src' make[5]: Entering directory `/build/buildd/alarm-clock-applet-0.3.1/src' test -z "/usr/bin" || /bin/mkdir -p "/build/buildd/alarm-clock-applet-0.3.1/debian/alarm-clock-applet/usr/bin" /usr/bin/install -c alarm-clock-applet '/build/buildd/alarm-clock-applet-0.3.1/debian/alarm-clock-applet/usr/bin' make[5]: Nothing to be done for `install-data-am'. make[5]: Leaving directory `/build/buildd/alarm-clock-applet-0.3.1/src' make[4]: Leaving directory `/build/buildd/alarm-clock-applet-0.3.1/src' make[3]: Leaving directory `/build/buildd/alarm-clock-applet-0.3.1/src' Making install in data make[3]: Entering directory `/build/buildd/alarm-clock-applet-0.3.1/data' Making install in icons make[4]: Entering directory `/build/buildd/alarm-clock-applet-0.3.1/data/icons' make[5]: Entering directory `/build/buildd/alarm-clock-applet-0.3.1/data/icons' make[5]: Nothing to be done for `install-exec-am'. for icon in alarm-clock.svg alarm-clock.16.png alarm-clock.22.png alarm-clock.24.png alarm-clock.32.png alarm-clock.36.png alarm-clock.48.png alarm-clock.64.png alarm-timer.svg alarm-timer.16.png alarm-timer.22.png alarm-timer.24.png alarm-timer.32.png alarm-timer.36.png alarm-timer.48.png alarm-timer.64.png alarm-snooze.16.png alarm-snooze.22.png alarm-snooze.24.png alarm-snooze.32.png alarm-snooze.36.png alarm-snooze.48.png alarm-snooze.64.png ; do \ SIZE=`basename $icon | cut -d. -f2`; \ FILE=`basename $icon | cut -d. -f1,3`; \ if [ "$SIZE" = "svg" ]; then \ SIZE="scalable"; \ FILE="$FILE.svg"; \ else \ SIZE="${SIZE}x${SIZE}"; \ fi; \ mkdir -p /build/buildd/alarm-clock-applet-0.3.1/debian/alarm-clock-applet/usr/share/icons/hicolor/$SIZE/apps/; \ /usr/bin/install -c -m 644 ./$icon /build/buildd/alarm-clock-applet-0.3.1/debian/alarm-clock-applet/usr/share/icons/hicolor/$SIZE/apps/$FILE; \ done *** Icon cache not updated. After (un)install, run this: *** gtk-update-icon-cache -f -t /usr/share/icons/hicolor make[5]: Leaving directory `/build/buildd/alarm-clock-applet-0.3.1/data/icons' make[4]: Leaving directory `/build/buildd/alarm-clock-applet-0.3.1/data/icons' make[4]: Entering directory `/build/buildd/alarm-clock-applet-0.3.1/data' make[5]: Entering directory `/build/buildd/alarm-clock-applet-0.3.1/data' make[5]: Nothing to be done for `install-exec-am'. GCONF_CONFIG_SOURCE=xml:merged:/etc/gconf/gconf.xml.defaults \ /usr/bin/gconftool-2 --makefile-install-rule alarm-clock.schemas (gconftool-2:24705): GConf-WARNING **: None of the resolved addresses are writable; saving configuration settings will not be possible WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/type', locale `da': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/type', locale `C': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/type', locale `nb': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/type', locale `id': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/type', locale `de': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/type', locale `be': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/type', locale `bg': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/type', locale `he': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/type', locale `hi': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/type', locale `ja': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/type', locale `gl': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/type', locale `pl': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/type', locale `nn': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/type', locale `fo': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/type', locale `zh_CN': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/type', locale `pt_BR': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/type', locale `fr': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/type', locale `es': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/type', locale `ms': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/type', locale `hu': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/type', locale `ru': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/type', locale `pt': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/timestamp', locale `da': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/timestamp', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/timestamp', locale `C': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/timestamp', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/timestamp', locale `nb': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/timestamp', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/timestamp', locale `id': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/timestamp', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/timestamp', locale `he': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/timestamp', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/timestamp', locale `de': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/timestamp', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/timestamp', locale `ja': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/timestamp', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/timestamp', locale `be': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/timestamp', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/timestamp', locale `hi': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/timestamp', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/timestamp', locale `zh_CN': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/timestamp', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/timestamp', locale `nn': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/timestamp', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/timestamp', locale `fo': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/timestamp', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/timestamp', locale `pt_BR': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/timestamp', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/timestamp', locale `es': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/timestamp', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/timestamp', locale `ms': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/timestamp', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/timestamp', locale `ru': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/timestamp', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/time', locale `da': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/time', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/time', locale `C': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/time', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/time', locale `nb': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/time', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/time', locale `id': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/time', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/time', locale `de': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/time', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/time', locale `be': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/time', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/time', locale `bg': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/time', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/time', locale `he': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/time', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/time', locale `hi': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/time', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/time', locale `ja': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/time', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/time', locale `gl': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/time', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/time', locale `pl': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/time', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/time', locale `nn': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/time', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/time', locale `fo': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/time', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/time', locale `zh_CN': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/time', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/time', locale `pt_BR': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/time', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/time', locale `fr': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/time', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/time', locale `es': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/time', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/time', locale `ms': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/time', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/time', locale `hu': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/time', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/time', locale `ru': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/time', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/time', locale `pt': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/time', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/message', locale `da': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/message', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/message', locale `C': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/message', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/message', locale `nb': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/message', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/message', locale `id': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/message', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/message', locale `de': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/message', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/message', locale `be': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/message', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/message', locale `bg': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/message', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/message', locale `he': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/message', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/message', locale `hi': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/message', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/message', locale `ja': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/message', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/message', locale `gl': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/message', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/message', locale `pl': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/message', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/message', locale `nn': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/message', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/message', locale `fo': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/message', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/message', locale `zh_CN': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/message', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/message', locale `pt_BR': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/message', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/message', locale `fr': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/message', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/message', locale `es': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/message', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/message', locale `ms': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/message', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/message', locale `hu': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/message', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/message', locale `ru': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/message', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/message', locale `pt': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/message', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/active', locale `da': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/active', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/active', locale `C': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/active', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/active', locale `nb': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/active', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/active', locale `id': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/active', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/active', locale `de': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/active', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/active', locale `be': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/active', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/active', locale `bg': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/active', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/active', locale `he': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/active', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/active', locale `hi': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/active', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/active', locale `ja': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/active', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/active', locale `gl': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/active', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/active', locale `zh_CN': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/active', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/active', locale `nn': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/active', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/active', locale `fo': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/active', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/active', locale `pt_BR': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/active', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/active', locale `fr': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/active', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/active', locale `es': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/active', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/active', locale `ms': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/active', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/active', locale `pt': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/active', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/active', locale `ru': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/active', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/repeat', locale `da': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/repeat', locale `C': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/repeat', locale `nb': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/repeat', locale `id': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/repeat', locale `de': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/repeat', locale `be': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/repeat', locale `ja': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/repeat', locale `he': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/repeat', locale `gl': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/repeat', locale `pl': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/repeat', locale `nn': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/repeat', locale `fo': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/repeat', locale `zh_CN': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/repeat', locale `pt_BR': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/repeat', locale `fr': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/repeat', locale `es': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/repeat', locale `ms': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/repeat', locale `hu': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/repeat', locale `ru': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/repeat', locale `pt': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/notify_type', locale `da': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/notify_type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/notify_type', locale `C': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/notify_type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/notify_type', locale `nb': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/notify_type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/notify_type', locale `id': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/notify_type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/notify_type', locale `de': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/notify_type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/notify_type', locale `be': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/notify_type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/notify_type', locale `ja': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/notify_type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/notify_type', locale `he': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/notify_type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/notify_type', locale `hi': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/notify_type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/notify_type', locale `gl': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/notify_type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/notify_type', locale `pl': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/notify_type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/notify_type', locale `nn': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/notify_type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/notify_type', locale `fo': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/notify_type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/notify_type', locale `zh_CN': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/notify_type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/notify_type', locale `pt_BR': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/notify_type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/notify_type', locale `fr': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/notify_type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/notify_type', locale `es': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/notify_type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/notify_type', locale `ms': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/notify_type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/notify_type', locale `pt': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/notify_type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/notify_type', locale `ru': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/notify_type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_file', locale `da': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_file', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_file', locale `C': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_file', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_file', locale `nb': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_file', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_file', locale `id': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_file', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_file', locale `de': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_file', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_file', locale `be': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_file', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_file', locale `bg': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_file', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_file', locale `he': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_file', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_file', locale `hi': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_file', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_file', locale `ja': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_file', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_file', locale `gl': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_file', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_file', locale `pl': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_file', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_file', locale `nn': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_file', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_file', locale `fo': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_file', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_file', locale `zh_CN': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_file', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_file', locale `pt_BR': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_file', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_file', locale `fr': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_file', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_file', locale `es': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_file', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_file', locale `ms': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_file', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_file', locale `hu': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_file', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_file', locale `ru': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_file', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_file', locale `pt': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_file', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_repeat', locale `da': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_repeat', locale `C': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_repeat', locale `nb': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_repeat', locale `id': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_repeat', locale `de': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_repeat', locale `be': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_repeat', locale `ja': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_repeat', locale `he': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_repeat', locale `hi': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_repeat', locale `gl': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_repeat', locale `pl': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_repeat', locale `nn': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_repeat', locale `fo': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_repeat', locale `zh_CN': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_repeat', locale `pt_BR': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_repeat', locale `fr': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_repeat', locale `es': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_repeat', locale `ms': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_repeat', locale `pt': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_repeat', locale `ru': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/command', locale `da': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/command', locale `C': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/command', locale `nb': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/command', locale `id': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/command', locale `de': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/command', locale `be': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/command', locale `bg': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/command', locale `he': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/command', locale `hi': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/command', locale `ja': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/command', locale `gl': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/command', locale `pl': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/command', locale `nn': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/command', locale `fo': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/command', locale `zh_CN': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/command', locale `pt_BR': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/command', locale `fr': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/command', locale `es': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/command', locale `ms': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/command', locale `hu': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/command', locale `ru': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/command', locale `pt': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only 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/applications" || /bin/mkdir -p "/build/buildd/alarm-clock-applet-0.3.1/debian/alarm-clock-applet/usr/share/applications" /usr/bin/install -c -m 644 alarm-clock-applet.desktop '/build/buildd/alarm-clock-applet-0.3.1/debian/alarm-clock-applet/usr/share/applications' test -z "/etc/gconf/schemas" || /bin/mkdir -p "/build/buildd/alarm-clock-applet-0.3.1/debian/alarm-clock-applet/etc/gconf/schemas" /usr/bin/install -c -m 644 alarm-clock.schemas '/build/buildd/alarm-clock-applet-0.3.1/debian/alarm-clock-applet/etc/gconf/schemas' test -z "/usr/share/alarm-clock-applet" || /bin/mkdir -p "/build/buildd/alarm-clock-applet-0.3.1/debian/alarm-clock-applet/usr/share/alarm-clock-applet" /usr/bin/install -c -m 644 alarm-clock.ui '/build/buildd/alarm-clock-applet-0.3.1/debian/alarm-clock-applet/usr/share/alarm-clock-applet' make[5]: Leaving directory `/build/buildd/alarm-clock-applet-0.3.1/data' make[4]: Leaving directory `/build/buildd/alarm-clock-applet-0.3.1/data' make[3]: Leaving directory `/build/buildd/alarm-clock-applet-0.3.1/data' Making install in po make[3]: Entering directory `/build/buildd/alarm-clock-applet-0.3.1/po' linguas="ar be bg ca da de es fi fo fr gl he hi hu id ja ms nb nn pl pt_BR pt ru zh_CN "; \ for lang in $linguas; do \ dir=/build/buildd/alarm-clock-applet-0.3.1/debian/alarm-clock-applet/usr/share/locale/$lang/LC_MESSAGES; \ /bin/bash /build/buildd/alarm-clock-applet-0.3.1/install-sh -d $dir; \ if test -r $lang.gmo; then \ /usr/bin/install -c -m 644 $lang.gmo $dir/alarm-clock-applet.mo; \ echo "installing $lang.gmo as $dir/alarm-clock-applet.mo"; \ else \ /usr/bin/install -c -m 644 ./$lang.gmo $dir/alarm-clock-applet.mo; \ echo "installing ./$lang.gmo as" \ "$dir/alarm-clock-applet.mo"; \ fi; \ if test -r $lang.gmo.m; then \ /usr/bin/install -c -m 644 $lang.gmo.m $dir/alarm-clock-applet.mo.m; \ echo "installing $lang.gmo.m as $dir/alarm-clock-applet.mo.m"; \ else \ if test -r ./$lang.gmo.m ; then \ /usr/bin/install -c -m 644 ./$lang.gmo.m \ $dir/alarm-clock-applet.mo.m; \ echo "installing ./$lang.gmo.m as" \ "$dir/alarm-clock-applet.mo.m"; \ else \ true; \ fi; \ fi; \ done installing ar.gmo as /build/buildd/alarm-clock-applet-0.3.1/debian/alarm-clock-applet/usr/share/locale/ar/LC_MESSAGES/alarm-clock-applet.mo installing be.gmo as /build/buildd/alarm-clock-applet-0.3.1/debian/alarm-clock-applet/usr/share/locale/be/LC_MESSAGES/alarm-clock-applet.mo installing bg.gmo as /build/buildd/alarm-clock-applet-0.3.1/debian/alarm-clock-applet/usr/share/locale/bg/LC_MESSAGES/alarm-clock-applet.mo installing ca.gmo as /build/buildd/alarm-clock-applet-0.3.1/debian/alarm-clock-applet/usr/share/locale/ca/LC_MESSAGES/alarm-clock-applet.mo installing da.gmo as /build/buildd/alarm-clock-applet-0.3.1/debian/alarm-clock-applet/usr/share/locale/da/LC_MESSAGES/alarm-clock-applet.mo installing de.gmo as /build/buildd/alarm-clock-applet-0.3.1/debian/alarm-clock-applet/usr/share/locale/de/LC_MESSAGES/alarm-clock-applet.mo installing es.gmo as /build/buildd/alarm-clock-applet-0.3.1/debian/alarm-clock-applet/usr/share/locale/es/LC_MESSAGES/alarm-clock-applet.mo installing fi.gmo as /build/buildd/alarm-clock-applet-0.3.1/debian/alarm-clock-applet/usr/share/locale/fi/LC_MESSAGES/alarm-clock-applet.mo installing fo.gmo as /build/buildd/alarm-clock-applet-0.3.1/debian/alarm-clock-applet/usr/share/locale/fo/LC_MESSAGES/alarm-clock-applet.mo installing fr.gmo as /build/buildd/alarm-clock-applet-0.3.1/debian/alarm-clock-applet/usr/share/locale/fr/LC_MESSAGES/alarm-clock-applet.mo installing gl.gmo as /build/buildd/alarm-clock-applet-0.3.1/debian/alarm-clock-applet/usr/share/locale/gl/LC_MESSAGES/alarm-clock-applet.mo installing he.gmo as /build/buildd/alarm-clock-applet-0.3.1/debian/alarm-clock-applet/usr/share/locale/he/LC_MESSAGES/alarm-clock-applet.mo installing hi.gmo as /build/buildd/alarm-clock-applet-0.3.1/debian/alarm-clock-applet/usr/share/locale/hi/LC_MESSAGES/alarm-clock-applet.mo installing hu.gmo as /build/buildd/alarm-clock-applet-0.3.1/debian/alarm-clock-applet/usr/share/locale/hu/LC_MESSAGES/alarm-clock-applet.mo installing id.gmo as /build/buildd/alarm-clock-applet-0.3.1/debian/alarm-clock-applet/usr/share/locale/id/LC_MESSAGES/alarm-clock-applet.mo installing ja.gmo as /build/buildd/alarm-clock-applet-0.3.1/debian/alarm-clock-applet/usr/share/locale/ja/LC_MESSAGES/alarm-clock-applet.mo installing ms.gmo as /build/buildd/alarm-clock-applet-0.3.1/debian/alarm-clock-applet/usr/share/locale/ms/LC_MESSAGES/alarm-clock-applet.mo installing nb.gmo as /build/buildd/alarm-clock-applet-0.3.1/debian/alarm-clock-applet/usr/share/locale/nb/LC_MESSAGES/alarm-clock-applet.mo installing nn.gmo as /build/buildd/alarm-clock-applet-0.3.1/debian/alarm-clock-applet/usr/share/locale/nn/LC_MESSAGES/alarm-clock-applet.mo installing pl.gmo as /build/buildd/alarm-clock-applet-0.3.1/debian/alarm-clock-applet/usr/share/locale/pl/LC_MESSAGES/alarm-clock-applet.mo installing pt_BR.gmo as /build/buildd/alarm-clock-applet-0.3.1/debian/alarm-clock-applet/usr/share/locale/pt_BR/LC_MESSAGES/alarm-clock-applet.mo installing pt.gmo as /build/buildd/alarm-clock-applet-0.3.1/debian/alarm-clock-applet/usr/share/locale/pt/LC_MESSAGES/alarm-clock-applet.mo installing ru.gmo as /build/buildd/alarm-clock-applet-0.3.1/debian/alarm-clock-applet/usr/share/locale/ru/LC_MESSAGES/alarm-clock-applet.mo installing zh_CN.gmo as /build/buildd/alarm-clock-applet-0.3.1/debian/alarm-clock-applet/usr/share/locale/zh_CN/LC_MESSAGES/alarm-clock-applet.mo make[3]: Leaving directory `/build/buildd/alarm-clock-applet-0.3.1/po' make[3]: Entering directory `/build/buildd/alarm-clock-applet-0.3.1' make[4]: Entering directory `/build/buildd/alarm-clock-applet-0.3.1' 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/alarm-clock-applet-0.3.1' make[3]: Leaving directory `/build/buildd/alarm-clock-applet-0.3.1' make[2]: Leaving directory `/build/buildd/alarm-clock-applet-0.3.1' make[1]: Leaving directory `/build/buildd/alarm-clock-applet-0.3.1' dh_install dh_installdocs debian/rules override_dh_installchangelogs make[1]: Entering directory `/build/buildd/alarm-clock-applet-0.3.1' dh_installchangelogs ChangeLog make[1]: Leaving directory `/build/buildd/alarm-clock-applet-0.3.1' dh_installexamples dh_installman dh_installcatalogs dh_installcron dh_installdebconf dh_installemacsen dh_installifupdown dh_installinfo dh_installinit dh_installmenu dh_installmime dh_installmodules dh_installlogcheck dh_installlogrotate dh_installpam dh_installppp dh_installudev dh_installwm dh_installxfonts dh_bugfiles dh_lintian dh_gconf dh_icons dh_perl dh_usrlocal dh_link dh_compress dh_fixperms dh_strip dh_strip debug symbol extraction: disabling for PPA build dh_strip debug symbol extraction: not doing anything since NO_PKG_MANGLE is given dh_makeshlibs dh_shlibdeps dpkg-shlibdeps: warning: dependency on libpthread.so.0 could be avoided if "debian/alarm-clock-applet/usr/bin/alarm-clock-applet" were not uselessly linked against it (they use none of its symbols). dh_installdeb dh_gencontrol dh_md5sums dh_builddeb INFO: Disabling pkgbinarymangler for PPA build WARNING: not running pkgbinarymangler for this package, as requested dpkg-deb: building package `alarm-clock-applet' in `../alarm-clock-applet_0.3.1-1_i386.deb'. dpkg-genchanges -b -mUbuntu Build Daemon >../alarm-clock-applet_0.3.1-1_i386.changes dpkg-genchanges: binary-only upload - not including any source code dpkg-buildpackage: binary only upload (no source included) ****************************************************************************** Build finished at 20111005-1922 chroot-autobuild/build/buildd/alarm-clock-applet_0.3.1-1_i386.deb: new debian package, version 2.0. size 144216 bytes: control archive= 2438 bytes. 856 bytes, 17 lines control 4708 bytes, 55 lines md5sums 167 bytes, 7 lines * postinst #!/bin/sh 186 bytes, 7 lines * prerm #!/bin/sh Package: alarm-clock-applet Version: 0.3.1-1 Architecture: i386 Maintainer: Chow Loong Jin Installed-Size: 848 Depends: libc6 (>= 2.7), libgconf2-4 (>= 2.27.0), libglib2.0-0 (>= 2.20.0), libgstreamer0.10-0 (>= 0.10.7), libgtk2.0-0 (>= 2.18.0), libnotify1 (>= 0.4.5), libnotify1-gtk2.10, libunique-1.0-0 (>= 1.0.0), libxml2 (>= 2.7.4), gconf2 (>= 2.10.1-2) Section: gnome Priority: optional Homepage: http://alarm-clock.pseudoberries.com/ Description: Alarm Clock applet Alarm Clock is a fully-featured alarm clock which resides in the notification area It is easy to use yet powerful with support for multiple and repeatable alarms, as well as snoozing and a flexible notification system. . Two types of alarms are supported: Alarm Clocks and Timers. Notification is done by either playing a sound or launching an application. chroot-autobuild/build/buildd/alarm-clock-applet_0.3.1-1_i386.deb: drwxr-xr-x root/root 0 2011-10-05 19:22 ./ drwxr-xr-x root/root 0 2011-10-05 19:22 ./etc/ drwxr-xr-x root/root 0 2011-10-05 19:22 ./etc/xdg/ drwxr-xr-x root/root 0 2011-10-05 19:22 ./etc/xdg/autostart/ drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/ drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/bin/ -rwxr-xr-x root/root 84600 2011-10-05 19:22 ./usr/bin/alarm-clock-applet drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/ drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/locale/ drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/locale/da/ drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/locale/da/LC_MESSAGES/ -rw-r--r-- root/root 7442 2011-10-05 19:22 ./usr/share/locale/da/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/locale/hu/ drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/locale/hu/LC_MESSAGES/ -rw-r--r-- root/root 2596 2011-10-05 19:22 ./usr/share/locale/hu/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/locale/ms/ drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/locale/ms/LC_MESSAGES/ -rw-r--r-- root/root 7671 2011-10-05 19:22 ./usr/share/locale/ms/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/locale/ru/ drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/locale/ru/LC_MESSAGES/ -rw-r--r-- root/root 9463 2011-10-05 19:22 ./usr/share/locale/ru/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/locale/fo/ drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/locale/fo/LC_MESSAGES/ -rw-r--r-- root/root 4749 2011-10-05 19:22 ./usr/share/locale/fo/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/locale/pt_BR/ drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/locale/pt_BR/LC_MESSAGES/ -rw-r--r-- root/root 7953 2011-10-05 19:22 ./usr/share/locale/pt_BR/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/locale/gl/ drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/locale/gl/LC_MESSAGES/ -rw-r--r-- root/root 7449 2011-10-05 19:22 ./usr/share/locale/gl/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/locale/he/ drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/locale/he/LC_MESSAGES/ -rw-r--r-- root/root 8243 2011-10-05 19:22 ./usr/share/locale/he/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/locale/bg/ drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/locale/bg/LC_MESSAGES/ -rw-r--r-- root/root 3159 2011-10-05 19:22 ./usr/share/locale/bg/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/locale/fi/ drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/locale/fi/LC_MESSAGES/ -rw-r--r-- root/root 473 2011-10-05 19:22 ./usr/share/locale/fi/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/locale/pl/ drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/locale/pl/LC_MESSAGES/ -rw-r--r-- root/root 3155 2011-10-05 19:22 ./usr/share/locale/pl/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/locale/hi/ drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/locale/hi/LC_MESSAGES/ -rw-r--r-- root/root 5291 2011-10-05 19:22 ./usr/share/locale/hi/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/locale/ca/ drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/locale/ca/LC_MESSAGES/ -rw-r--r-- root/root 473 2011-10-05 19:22 ./usr/share/locale/ca/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/locale/zh_CN/ drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/locale/zh_CN/LC_MESSAGES/ -rw-r--r-- root/root 6085 2011-10-05 19:22 ./usr/share/locale/zh_CN/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/locale/id/ drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/locale/id/LC_MESSAGES/ -rw-r--r-- root/root 4348 2011-10-05 19:22 ./usr/share/locale/id/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/locale/ja/ drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/locale/ja/LC_MESSAGES/ -rw-r--r-- root/root 7702 2011-10-05 19:22 ./usr/share/locale/ja/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/locale/fr/ drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/locale/fr/LC_MESSAGES/ -rw-r--r-- root/root 4410 2011-10-05 19:22 ./usr/share/locale/fr/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/locale/be/ drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/locale/be/LC_MESSAGES/ -rw-r--r-- root/root 8787 2011-10-05 19:22 ./usr/share/locale/be/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/locale/es/ drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/locale/es/LC_MESSAGES/ -rw-r--r-- root/root 2007 2011-10-05 19:22 ./usr/share/locale/es/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/locale/nb/ drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/locale/nb/LC_MESSAGES/ -rw-r--r-- root/root 7515 2011-10-05 19:22 ./usr/share/locale/nb/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/locale/ar/ drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/locale/ar/LC_MESSAGES/ -rw-r--r-- root/root 536 2011-10-05 19:22 ./usr/share/locale/ar/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/locale/pt/ drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/locale/pt/LC_MESSAGES/ -rw-r--r-- root/root 1549 2011-10-05 19:22 ./usr/share/locale/pt/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/locale/nn/ drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/locale/nn/LC_MESSAGES/ -rw-r--r-- root/root 2903 2011-10-05 19:22 ./usr/share/locale/nn/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/locale/de/ drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/locale/de/LC_MESSAGES/ -rw-r--r-- root/root 7836 2011-10-05 19:22 ./usr/share/locale/de/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/gconf/ drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/gconf/schemas/ -rw-r--r-- root/root 37328 2011-10-05 19:22 ./usr/share/gconf/schemas/alarm-clock.schemas drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/doc/ drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/doc/alarm-clock-applet/ -rw-r--r-- root/root 8763 2010-05-16 20:31 ./usr/share/doc/alarm-clock-applet/changelog.gz -rw-r--r-- root/root 726 2010-05-18 16:26 ./usr/share/doc/alarm-clock-applet/changelog.Debian.gz -rw-r--r-- root/root 1429 2010-05-18 16:26 ./usr/share/doc/alarm-clock-applet/copyright drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/alarm-clock-applet/ -rw-r--r-- root/root 64492 2011-10-05 19:22 ./usr/share/alarm-clock-applet/alarm-clock.ui drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/icons/ drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/icons/hicolor/ drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/icons/hicolor/36x36/ drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/icons/hicolor/36x36/apps/ -rw-r--r-- root/root 2518 2011-10-05 19:22 ./usr/share/icons/hicolor/36x36/apps/alarm-clock.png -rw-r--r-- root/root 2257 2011-10-05 19:22 ./usr/share/icons/hicolor/36x36/apps/alarm-timer.png -rw-r--r-- root/root 1880 2011-10-05 19:22 ./usr/share/icons/hicolor/36x36/apps/alarm-snooze.png drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/icons/hicolor/32x32/ drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/icons/hicolor/32x32/apps/ -rw-r--r-- root/root 2167 2011-10-05 19:22 ./usr/share/icons/hicolor/32x32/apps/alarm-clock.png -rw-r--r-- root/root 2021 2011-10-05 19:22 ./usr/share/icons/hicolor/32x32/apps/alarm-timer.png -rw-r--r-- root/root 1589 2011-10-05 19:22 ./usr/share/icons/hicolor/32x32/apps/alarm-snooze.png drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/icons/hicolor/22x22/ drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/icons/hicolor/22x22/apps/ -rw-r--r-- root/root 1277 2011-10-05 19:22 ./usr/share/icons/hicolor/22x22/apps/alarm-clock.png -rw-r--r-- root/root 1250 2011-10-05 19:22 ./usr/share/icons/hicolor/22x22/apps/alarm-timer.png -rw-r--r-- root/root 1054 2011-10-05 19:22 ./usr/share/icons/hicolor/22x22/apps/alarm-snooze.png drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/icons/hicolor/64x64/ drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/icons/hicolor/64x64/apps/ -rw-r--r-- root/root 4912 2011-10-05 19:22 ./usr/share/icons/hicolor/64x64/apps/alarm-clock.png -rw-r--r-- root/root 4360 2011-10-05 19:22 ./usr/share/icons/hicolor/64x64/apps/alarm-timer.png -rw-r--r-- root/root 3661 2011-10-05 19:22 ./usr/share/icons/hicolor/64x64/apps/alarm-snooze.png drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/icons/hicolor/48x48/ drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/icons/hicolor/48x48/apps/ -rw-r--r-- root/root 3453 2011-10-05 19:22 ./usr/share/icons/hicolor/48x48/apps/alarm-clock.png -rw-r--r-- root/root 2999 2011-10-05 19:22 ./usr/share/icons/hicolor/48x48/apps/alarm-timer.png -rw-r--r-- root/root 2602 2011-10-05 19:22 ./usr/share/icons/hicolor/48x48/apps/alarm-snooze.png drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/icons/hicolor/24x24/ drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/icons/hicolor/24x24/apps/ -rw-r--r-- root/root 1518 2011-10-05 19:22 ./usr/share/icons/hicolor/24x24/apps/alarm-clock.png -rw-r--r-- root/root 1366 2011-10-05 19:22 ./usr/share/icons/hicolor/24x24/apps/alarm-timer.png -rw-r--r-- root/root 1156 2011-10-05 19:22 ./usr/share/icons/hicolor/24x24/apps/alarm-snooze.png drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/icons/hicolor/scalable/ drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/icons/hicolor/scalable/apps/ -rw-r--r-- root/root 10076 2011-10-05 19:22 ./usr/share/icons/hicolor/scalable/apps/alarm-clock.svg -rw-r--r-- root/root 8970 2011-10-05 19:22 ./usr/share/icons/hicolor/scalable/apps/alarm-timer.svg drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/icons/hicolor/16x16/ drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/icons/hicolor/16x16/apps/ -rw-r--r-- root/root 904 2011-10-05 19:22 ./usr/share/icons/hicolor/16x16/apps/alarm-clock.png -rw-r--r-- root/root 711 2011-10-05 19:22 ./usr/share/icons/hicolor/16x16/apps/alarm-timer.png -rw-r--r-- root/root 669 2011-10-05 19:22 ./usr/share/icons/hicolor/16x16/apps/alarm-snooze.png drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/applications/ -rw-r--r-- root/root 1267 2011-10-05 19:22 ./usr/share/applications/alarm-clock-applet.desktop drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/man/ drwxr-xr-x root/root 0 2011-10-05 19:22 ./usr/share/man/man1/ -rw-r--r-- root/root 554 2011-10-05 19:22 ./usr/share/man/man1/alarm-clock-applet.1.gz lrwxrwxrwx root/root 0 2011-10-05 19:22 ./etc/xdg/autostart/alarm-clock-applet.desktop -> /usr/share/applications/alarm-clock-applet.desktop alarm-clock-applet_0.3.1-1_i386.changes: Format: 1.8 Date: Wed, 19 May 2010 00:26:36 +0800 Source: alarm-clock-applet Binary: alarm-clock-applet Architecture: i386 Version: 0.3.1-1 Distribution: lucid Urgency: low Maintainer: Ubuntu Build Daemon Changed-By: Chow Loong Jin Description: alarm-clock-applet - Alarm Clock applet Closes: 577276 Changes: alarm-clock-applet (0.3.1-1) unstable; urgency=low . * New upstraem release * debian/alarm-clock-applet.links: + Link alarm-clock-applet.desktop into /etc/xdg/autostart to make it start up automatically (Closes: #577276) Checksums-Sha1: 28d213496f170d8caaa612c20a2681784d26f82e 144216 alarm-clock-applet_0.3.1-1_i386.deb Checksums-Sha256: 8d88922fa15170bf4b5a505eea6ca96c5b37569748f033c3ad13e35bb9f74ede 144216 alarm-clock-applet_0.3.1-1_i386.deb Files: 51315a49db73313934d0454db5df20c9 144216 gnome optional alarm-clock-applet_0.3.1-1_i386.deb ****************************************************************************** Built successfully Purging chroot-autobuild/build/buildd/alarm-clock-applet-0.3.1 ------------------------------------------------------------------------------ /usr/bin/sudo dpkg --purge groff-base libavahi-common3 libxfixes-dev libx11-data m4 libgconf2-dev fontconfig-config gettext file zlib1g-dev libhtml-parser-perl libcairo2 x11-common libidl-dev python2.6 libx11-dev libxi6 automake libjpeg62 libnotify-dev libxcursor1 libgstreamer0.10-0 x11proto-input-dev libexpat1-dev libjasper1 libpixman-1-dev libjpeg62-dev libxcomposite-dev libfontconfig1 libdbus-glib-1-2 libgstreamer0.10-dev libsysfs-dev libx11-6 xtrans-dev x11proto-randr-dev psmisc libnewt0.52 libxinerama-dev libpango1.0-common libxdamage1 libxml2-utils libdbus-1-dev libhtml-tree-perl libglib2.0-dev libxcb-render-util0 gconf2 libunique-dev tsconf libdirectfb-dev hicolor-icon-theme libhtml-tagset-perl libxml2 dbus x11proto-xext-dev pkg-config libthai-data libice6 intltool-debian libavahi-client3 libxrender1 liborbit2-dev libfontconfig1-dev libxml2-dev libxrandr-dev libxext-dev libcups2 libdirectfb-extra libxau-dev libdatrie1 libxcb-render-util0-dev libxrender-dev libpng12-dev libavahi-common-data libxft2 x11proto-render-dev libxext6 libsysfs2 libsqlite3-0 libnotify1 libxinerama1 libdbus-glib-1-dev libxdamage-dev libsm-dev libncursesw5 gconf2-common libgsf-1-common defoma libxdmcp-dev ttf-dejavu-core librsvg2-2 libcairo2-dev fontconfig libxcb-render0-dev liburi-perl autotools-dev libcroco3 liborbit2 libpopt0 libfreetype6 libice-dev libatk1.0-0 x11proto-fixes-dev libfreetype6-dev libgtk2.0-0 x11proto-damage-dev libidl0 libxcb1 libgtk2.0-bin html2text libgsf-1-114 libxrandr2 debhelper libpthread-stubs0 libthai0 python libmagic1 libtiff4 libexpat1 bsdmainutils libxau6 libpango1.0-dev libxcursor-dev libxcomposite1 x11proto-composite-dev libgconf2-4 mime-support librsvg2-common x11proto-core-dev whiptail intltool libts-0.0-0 libxcb1-dev libxi-dev libwww-perl shared-mime-info libxdmcp6 libxfixes3 libgtk2.0-dev po-debconf libatk1.0-dev libdirectfb-1.2-0 libxml-parser-perl libxft-dev man-db dbus-x11 x11proto-kb-dev gnome-icon-theme libpixman-1-0 x11proto-xinerama-dev libpango1.0-0 libpthread-stubs0-dev ucf libgtk2.0-common gettext-base libsm6 libxcb-render0 libunique-1.0-0 autoconf (Reading database ... 27317 files and directories currently installed.) Removing libgconf2-dev ... Removing libnotify-dev ... Removing libgstreamer0.10-dev ... Removing gconf2 ... Purging configuration files for gconf2 ... Removing libunique-dev ... Removing liborbit2-dev ... Removing libxml2-dev ... Removing libnotify1 ... Purging configuration files for libnotify1 ... Removing libdbus-glib-1-dev ... Removing debhelper ... Removing python ... Purging configuration files for python ... Removing libgconf2-4 ... Purging configuration files for libgconf2-4 ... Removing intltool ... Removing libgtk2.0-dev ... Removing po-debconf ... Removing libatk1.0-dev ... Removing libxml-parser-perl ... Removing man-db ... Purging configuration files for man-db ... Removing catpages as well as /var/cache/man hierarchy. Removing dbus-x11 ... Purging configuration files for dbus-x11 ... Removing gnome-icon-theme ... Removing libunique-1.0-0 ... Purging configuration files for libunique-1.0-0 ... Removing groff-base ... Purging configuration files for groff-base ... Removing libidl-dev ... Removing python2.6 ... Purging configuration files for python2.6 ... Removing automake ... Removing libgstreamer0.10-0 ... Purging configuration files for libgstreamer0.10-0 ... Removing libxcomposite-dev ... Removing libdbus-glib-1-2 ... Purging configuration files for libdbus-glib-1-2 ... Removing psmisc ... Purging configuration files for psmisc ... Removing libxinerama-dev ... Removing libxml2-utils ... Removing libdbus-1-dev ... Removing hicolor-icon-theme ... Removing intltool-debian ... Removing libxrandr-dev ... Removing libsqlite3-0 ... Purging configuration files for libsqlite3-0 ... Removing libxdamage-dev ... Removing libncursesw5 ... Purging configuration files for libncursesw5 ... Removing gconf2-common ... Purging configuration files for gconf2-common ... Removing autotools-dev ... Removing liborbit2 ... Purging configuration files for liborbit2 ... Removing x11proto-damage-dev ... Removing libidl0 ... Purging configuration files for libidl0 ... Removing libgtk2.0-bin ... Removing html2text ... Purging configuration files for html2text ... Removing bsdmainutils ... Purging configuration files for bsdmainutils ... Removing libpango1.0-dev ... Removing libxcursor-dev ... Removing x11proto-composite-dev ... Removing mime-support ... Purging configuration files for mime-support ... Removing librsvg2-common ... Removing libxi-dev ... Removing libwww-perl ... Removing libxft-dev ... Removing x11proto-xinerama-dev ... Removing autoconf ... Purging configuration files for autoconf ... Removing libxfixes-dev ... Removing m4 ... Removing gettext ... Removing x11proto-randr-dev ... Removing libhtml-tree-perl ... Removing libglib2.0-dev ... Removing dbus ... Purging configuration files for dbus ... rmdir: failed to remove `/var/lib/dbus': No such file or directory Removing librsvg2-2 ... Purging configuration files for librsvg2-2 ... Removing libcairo2-dev ... Removing libcroco3 ... Purging configuration files for libcroco3 ... Removing x11proto-fixes-dev ... Removing libgtk2.0-0 ... Purging configuration files for libgtk2.0-0 ... Removing libgsf-1-114 ... Purging configuration files for libgsf-1-114 ... Removing libxrandr2 ... Purging configuration files for libxrandr2 ... Removing libtiff4 ... Purging configuration files for libtiff4 ... Removing libxcomposite1 ... Purging configuration files for libxcomposite1 ... Removing shared-mime-info ... Purging configuration files for shared-mime-info ... dpkg: warning: while removing shared-mime-info, directory '/usr/share/mime' not empty so not removed. Removing libpango1.0-0 ... Purging configuration files for libpango1.0-0 ... Removing libgtk2.0-common ... Removing gettext-base ... Removing libhtml-parser-perl ... Removing libcairo2 ... Purging configuration files for libcairo2 ... Removing libxi6 ... Purging configuration files for libxi6 ... Removing libxcursor1 ... Purging configuration files for libxcursor1 ... Removing libjasper1 ... Purging configuration files for libjasper1 ... Removing libpixman-1-dev ... Removing libpango1.0-common ... Purging font configuration of pango... Purging category xfont.. Purging configuration files for libpango1.0-common ... Removing libxdamage1 ... Purging configuration files for libxdamage1 ... Removing libdirectfb-dev ... Removing libhtml-tagset-perl ... Removing libxml2 ... Purging configuration files for libxml2 ... Removing libfontconfig1-dev ... Removing libxext-dev ... Removing libcups2 ... Purging configuration files for libcups2 ... Removing libdirectfb-extra ... Removing libxcb-render-util0-dev ... Removing libxrender-dev ... Removing libpng12-dev ... Removing libxft2 ... Purging configuration files for libxft2 ... Removing x11proto-render-dev ... Removing libxinerama1 ... Purging configuration files for libxinerama1 ... Removing libsm-dev ... Removing libgsf-1-common ... Removing defoma ... Purging configuration files for defoma ... dpkg: warning: while removing defoma, directory '/etc/defoma' not empty so not removed. Removing fontconfig ... Purging configuration files for fontconfig ... Removing libxcb-render0-dev ... Removing liburi-perl ... Removing libice-dev ... Removing libatk1.0-0 ... Purging configuration files for libatk1.0-0 ... Removing libfreetype6-dev ... Removing libthai0 ... Purging configuration files for libthai0 ... Removing whiptail ... Removing libxfixes3 ... Purging configuration files for libxfixes3 ... Removing libdirectfb-1.2-0 ... Purging configuration files for libdirectfb-1.2-0 ... Removing libpixman-1-0 ... Purging configuration files for libpixman-1-0 ... Removing libsm6 ... Purging configuration files for libsm6 ... Removing file ... Purging configuration files for file ... Removing zlib1g-dev ... Removing libx11-dev ... Removing libexpat1-dev ... Removing libjpeg62-dev ... Removing libfontconfig1 ... Purging configuration files for libfontconfig1 ... Removing libsysfs-dev ... Removing xtrans-dev ... Removing libnewt0.52 ... Purging configuration files for libnewt0.52 ... Removing libxcb-render-util0 ... Purging configuration files for libxcb-render-util0 ... Removing x11proto-xext-dev ... Removing pkg-config ... Removing libthai-data ... Removing libice6 ... Purging configuration files for libice6 ... Removing libavahi-client3 ... Purging configuration files for libavahi-client3 ... Removing libxrender1 ... Purging configuration files for libxrender1 ... Removing libdatrie1 ... Purging configuration files for libdatrie1 ... Removing libxext6 ... Purging configuration files for libxext6 ... Removing libsysfs2 ... Purging configuration files for libsysfs2 ... Removing libpopt0 ... Purging configuration files for libpopt0 ... Removing libfreetype6 ... Purging configuration files for libfreetype6 ... Removing libmagic1 ... Purging configuration files for libmagic1 ... Removing libexpat1 ... Purging configuration files for libexpat1 ... Removing libts-0.0-0 ... Purging configuration files for libts-0.0-0 ... Removing libxcb1-dev ... Removing x11proto-kb-dev ... Removing libpthread-stubs0-dev ... Removing libxcb-render0 ... Purging configuration files for libxcb-render0 ... Removing libavahi-common3 ... Purging configuration files for libavahi-common3 ... Removing fontconfig-config ... Purging configuration files for fontconfig-config ... Removing libjpeg62 ... Removing x11proto-input-dev ... Removing libx11-6 ... Purging configuration files for libx11-6 ... Removing tsconf ... Purging configuration files for tsconf ... Removing libxau-dev ... Removing libavahi-common-data ... Removing libxdmcp-dev ... Removing ttf-dejavu-core ... 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 x11-common ... Purging configuration files for x11-common ... Processing triggers for libc-bin ... ldconfig deferred processing now taking place ****************************************************************************** Finished at 20111005-1922 Build needed 00:00:19, 3872k disk space Can't open average time db /var/debbuild/avg-build-times Can't open average space db /var/debbuild/avg-build-space RUN: /usr/share/launchpad-buildd/slavebin/scan-for-processes ['/usr/share/launchpad-buildd/slavebin/scan-for-processes', '9634f4163eca24760ea2b949fdeee220510f9de9'] Scanning for processes to kill in build /home/buildd/build-9634f4163eca24760ea2b949fdeee220510f9de9/chroot-autobuild... RUN: /usr/share/launchpad-buildd/slavebin/umount-chroot ['umount-chroot', '9634f4163eca24760ea2b949fdeee220510f9de9'] Unmounting chroot for build 9634f4163eca24760ea2b949fdeee220510f9de9... none /home/buildd/build-9634f4163eca24760ea2b949fdeee220510f9de9/chroot-autobuild/proc proc rw,relatime 0 0 none /home/buildd/build-9634f4163eca24760ea2b949fdeee220510f9de9/chroot-autobuild/dev/pts devpts rw,relatime 0 0 none /home/buildd/build-9634f4163eca24760ea2b949fdeee220510f9de9/chroot-autobuild/sys sysfs rw,relatime 0 0 none /home/buildd/build-9634f4163eca24760ea2b949fdeee220510f9de9/chroot-autobuild/dev/shm tmpfs rw,relatime 0 0 RUN: /usr/share/launchpad-buildd/slavebin/remove-build ['remove-build', '9634f4163eca24760ea2b949fdeee220510f9de9'] Removing build 9634f4163eca24760ea2b949fdeee220510f9de9