RUN: /usr/share/launchpad-buildd/slavebin/slave-prep ['slave-prep'] Forking launchpad-buildd slave process... Kernel version: Linux bos01-ppc64el-009 3.13.0-62-generic #102-Ubuntu SMP Tue Aug 11 14:42:17 UTC 2015 ppc64le Buildd toolchain package versions: launchpad-buildd_133 python-lpbuildd_133 sbuild_0.65.2-1ubuntu2~ubuntu14.04.1~ppa6 bzr-builder_0.7.3+bzr174~ppa13~ubuntu14.04.1 bzr_2.6.0+bzr6593-1ubuntu1.1 dpkg-dev_1.17.5ubuntu5.4 python-debian_0.1.27ubuntu1~ubuntu14.04.1~ppa1. Syncing the system clock with the buildd NTP service... 2 Sep 09:45:11 ntpdate[1618]: adjust time server 10.211.37.1 offset 0.001819 sec RUN: /usr/share/launchpad-buildd/slavebin/unpack-chroot ['unpack-chroot', 'PACKAGEBUILD-7857231', '/home/buildd/filecache-default/2387c8e04212eb06cac6188888dcd8c11dca9fd7'] Unpacking chroot for build PACKAGEBUILD-7857231 RUN: /usr/share/launchpad-buildd/slavebin/mount-chroot ['mount-chroot', 'PACKAGEBUILD-7857231'] Mounting chroot for build PACKAGEBUILD-7857231 RUN: /usr/share/launchpad-buildd/slavebin/override-sources-list ['override-sources-list', 'PACKAGEBUILD-7857231', 'deb http://ftpmaster.internal/ubuntu wily main restricted universe multiverse', 'deb http://ftpmaster.internal/ubuntu wily-security main restricted universe multiverse', 'deb http://ftpmaster.internal/ubuntu wily-updates main restricted universe multiverse'] Overriding sources.list in build-PACKAGEBUILD-7857231 RUN: /usr/share/launchpad-buildd/slavebin/update-debian-chroot ['update-debian-chroot', 'PACKAGEBUILD-7857231', 'ppc64el'] Updating debian chroot for build PACKAGEBUILD-7857231 Ign http://ftpmaster.internal wily InRelease Ign http://ftpmaster.internal wily-security InRelease Ign http://archive-team.internal wily InRelease Ign http://ftpmaster.internal wily-updates InRelease Ign http://archive-team.internal wily Release.gpg Get:1 http://ftpmaster.internal wily Release.gpg [933 B] Get:2 http://ftpmaster.internal wily-security Release.gpg [933 B] Hit http://archive-team.internal wily Release Get:3 http://ftpmaster.internal wily-updates Release.gpg [933 B] Ign http://archive-team.internal wily/main ppc64el Packages/DiffIndex Get:4 http://ftpmaster.internal wily Release [217 kB] Get:5 http://ftpmaster.internal wily-security Release [63.5 kB] Get:6 http://ftpmaster.internal wily-updates Release [63.5 kB] Ign http://archive-team.internal wily/main Translation-en Get:7 http://ftpmaster.internal wily/main ppc64el Packages [1392 kB] Hit http://archive-team.internal wily/main ppc64el Packages Get:8 http://ftpmaster.internal wily/restricted ppc64el Packages [28 B] Get:9 http://ftpmaster.internal wily/universe ppc64el Packages [6450 kB] Get:10 http://ftpmaster.internal wily/multiverse ppc64el Packages [115 kB] Get:11 http://ftpmaster.internal wily/main Translation-en [845 kB] Get:12 http://ftpmaster.internal wily/multiverse Translation-en [107 kB] Get:13 http://ftpmaster.internal wily/restricted Translation-en [4531 B] Get:14 http://ftpmaster.internal wily/universe Translation-en [4557 kB] Get:15 http://ftpmaster.internal wily-security/main ppc64el Packages [28 B] Get:16 http://ftpmaster.internal wily-security/restricted ppc64el Packages [28 B] Get:17 http://ftpmaster.internal wily-security/universe ppc64el Packages [28 B] Get:18 http://ftpmaster.internal wily-security/multiverse ppc64el Packages [28 B] Get:19 http://ftpmaster.internal wily-security/main Translation-en [28 B] Get:20 http://ftpmaster.internal wily-security/multiverse Translation-en [28 B] Get:21 http://ftpmaster.internal wily-security/restricted Translation-en [28 B] Get:22 http://ftpmaster.internal wily-security/universe Translation-en [28 B] Get:23 http://ftpmaster.internal wily-updates/main ppc64el Packages [28 B] Get:24 http://ftpmaster.internal wily-updates/restricted ppc64el Packages [28 B] Get:25 http://ftpmaster.internal wily-updates/universe ppc64el Packages [28 B] Get:26 http://ftpmaster.internal wily-updates/multiverse ppc64el Packages [28 B] Get:27 http://ftpmaster.internal wily-updates/main Translation-en [28 B] Get:28 http://ftpmaster.internal wily-updates/multiverse Translation-en [28 B] Get:29 http://ftpmaster.internal wily-updates/restricted Translation-en [28 B] Get:30 http://ftpmaster.internal wily-updates/universe Translation-en [28 B] Fetched 13.8 MB in 7s (1875 kB/s) Reading package lists... Reading package lists... Building dependency tree... Reading state information... The following package was automatically installed and is no longer required: libtimedate-perl Use 'apt-get autoremove' to remove it. The following NEW packages will be installed: libapt-pkg4.16 The following packages will be upgraded: apt apt-transport-https bash cpp-5 debconf dpkg dpkg-dev g++-5 gcc-5 gcc-5-base libapparmor1 libasan2 libatomic1 libaudit-common libaudit1 libcc1-0 libcryptsetup4 libdbus-1-3 libdpkg-perl libgcc-5-dev libgcc1 libgomp1 libitm1 libkmod2 libpcre3 libstdc++-5-dev libstdc++6 libsystemd0 libubsan0 libudev1 systemd systemd-sysv udev 33 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 88.0 MB of archives. After this operation, 1616 kB of additional disk space will be used. Get:1 http://ftpmaster.internal/ubuntu/ wily/main bash ppc64el 4.3-13ubuntu1 [615 kB] Get:2 http://ftpmaster.internal/ubuntu/ wily/main dpkg ppc64el 1.18.2ubuntu3 [2097 kB] Get:3 http://ftpmaster.internal/ubuntu/ wily/main libgomp1 ppc64el 5.2.1-15ubuntu5 [50.5 kB] Get:4 http://ftpmaster.internal/ubuntu/ wily/main libitm1 ppc64el 5.2.1-15ubuntu5 [27.4 kB] Get:5 http://ftpmaster.internal/ubuntu/ wily/main libatomic1 ppc64el 5.2.1-15ubuntu5 [8200 B] Get:6 http://ftpmaster.internal/ubuntu/ wily/main libasan2 ppc64el 5.2.1-15ubuntu5 [237 kB] Get:7 http://ftpmaster.internal/ubuntu/ wily/main gcc-5-base ppc64el 5.2.1-15ubuntu5 [17.0 kB] Get:8 http://ftpmaster.internal/ubuntu/ wily/main libgcc1 ppc64el 1:5.2.1-15ubuntu5 [27.6 kB] Get:9 http://ftpmaster.internal/ubuntu/ wily/main libubsan0 ppc64el 5.2.1-15ubuntu5 [96.4 kB] Get:10 http://ftpmaster.internal/ubuntu/ wily/main cpp-5 ppc64el 5.2.1-15ubuntu5 [24.3 MB] Get:11 http://ftpmaster.internal/ubuntu/ wily/main libcc1-0 ppc64el 5.2.1-15ubuntu5 [31.0 kB] Get:12 http://ftpmaster.internal/ubuntu/ wily/main g++-5 ppc64el 5.2.1-15ubuntu5 [26.0 MB] Get:13 http://ftpmaster.internal/ubuntu/ wily/main gcc-5 ppc64el 5.2.1-15ubuntu5 [24.5 MB] Get:14 http://ftpmaster.internal/ubuntu/ wily/main libgcc-5-dev ppc64el 5.2.1-15ubuntu5 [578 kB] Get:15 http://ftpmaster.internal/ubuntu/ wily/main libstdc++-5-dev ppc64el 5.2.1-15ubuntu5 [1344 kB] Get:16 http://ftpmaster.internal/ubuntu/ wily/main libstdc++6 ppc64el 5.2.1-15ubuntu5 [409 kB] Get:17 http://ftpmaster.internal/ubuntu/ wily/main libapt-pkg4.16 ppc64el 1.0.9.10ubuntu6 [613 kB] Get:18 http://ftpmaster.internal/ubuntu/ wily/main apt ppc64el 1.0.9.10ubuntu6 [969 kB] Get:19 http://ftpmaster.internal/ubuntu/ wily/main debconf all 1.5.57ubuntu1 [136 kB] Get:20 http://ftpmaster.internal/ubuntu/ wily/main libpcre3 ppc64el 2:8.35-7ubuntu5 [217 kB] Get:21 http://ftpmaster.internal/ubuntu/ wily/main libsystemd0 ppc64el 224-2ubuntu2 [194 kB] Get:22 http://ftpmaster.internal/ubuntu/ wily/main systemd ppc64el 224-2ubuntu2 [3391 kB] Get:23 http://ftpmaster.internal/ubuntu/ wily/main libudev1 ppc64el 224-2ubuntu2 [57.0 kB] Get:24 http://ftpmaster.internal/ubuntu/ wily/main udev ppc64el 224-2ubuntu2 [965 kB] Get:25 http://ftpmaster.internal/ubuntu/ wily/main libkmod2 ppc64el 21-1ubuntu1 [36.3 kB] Get:26 http://ftpmaster.internal/ubuntu/ wily/main libapparmor1 ppc64el 2.10-0ubuntu4 [29.5 kB] Get:27 http://ftpmaster.internal/ubuntu/ wily/main libaudit-common all 1:2.4.2-1ubuntu1 [4080 B] Get:28 http://ftpmaster.internal/ubuntu/ wily/main libaudit1 ppc64el 1:2.4.2-1ubuntu1 [37.7 kB] Get:29 http://ftpmaster.internal/ubuntu/ wily/main libcryptsetup4 ppc64el 2:1.6.6-5ubuntu2 [70.8 kB] Get:30 http://ftpmaster.internal/ubuntu/ wily/main systemd-sysv ppc64el 224-2ubuntu2 [15.1 kB] Get:31 http://ftpmaster.internal/ubuntu/ wily/main apt-transport-https ppc64el 1.0.9.10ubuntu6 [24.7 kB] Get:32 http://ftpmaster.internal/ubuntu/ wily/main libdbus-1-3 ppc64el 1.9.20-1ubuntu2 [155 kB] Get:33 http://ftpmaster.internal/ubuntu/ wily/main dpkg-dev all 1.18.2ubuntu3 [583 kB] Get:34 http://ftpmaster.internal/ubuntu/ wily/main libdpkg-perl all 1.18.2ubuntu3 [194 kB] debconf: delaying package configuration, since apt-utils is not installed Fetched 88.0 MB in 1min 7s (1311 kB/s) (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 11598 files and directories currently installed.) Preparing to unpack .../bash_4.3-13ubuntu1_ppc64el.deb ... Unpacking bash (4.3-13ubuntu1) over (4.3-11ubuntu3) ... Setting up bash (4.3-13ubuntu1) ... Installing new version of config file /etc/skel/.bashrc ... update-alternatives: using /usr/share/man/man7/bash-builtins.7.gz to provide /usr/share/man/man7/builtins.7.gz (builtins.7.gz) in auto mode (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 11598 files and directories currently installed.) Preparing to unpack .../dpkg_1.18.2ubuntu3_ppc64el.deb ... Unpacking dpkg (1.18.2ubuntu3) over (1.18.1ubuntu1) ... Setting up dpkg (1.18.2ubuntu3) ... (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 11595 files and directories currently installed.) Preparing to unpack .../libgomp1_5.2.1-15ubuntu5_ppc64el.deb ... Unpacking libgomp1:ppc64el (5.2.1-15ubuntu5) over (5.2.1-15ubuntu1) ... Preparing to unpack .../libitm1_5.2.1-15ubuntu5_ppc64el.deb ... Unpacking libitm1:ppc64el (5.2.1-15ubuntu5) over (5.2.1-15ubuntu1) ... Preparing to unpack .../libatomic1_5.2.1-15ubuntu5_ppc64el.deb ... Unpacking libatomic1:ppc64el (5.2.1-15ubuntu5) over (5.2.1-15ubuntu1) ... Preparing to unpack .../libasan2_5.2.1-15ubuntu5_ppc64el.deb ... Unpacking libasan2:ppc64el (5.2.1-15ubuntu5) over (5.2.1-15ubuntu1) ... Preparing to unpack .../gcc-5-base_5.2.1-15ubuntu5_ppc64el.deb ... Unpacking gcc-5-base:ppc64el (5.2.1-15ubuntu5) over (5.2.1-15ubuntu1) ... Setting up gcc-5-base:ppc64el (5.2.1-15ubuntu5) ... (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 11595 files and directories currently installed.) Preparing to unpack .../libgcc1_1%3a5.2.1-15ubuntu5_ppc64el.deb ... Unpacking libgcc1:ppc64el (1:5.2.1-15ubuntu5) over (1:5.2.1-15ubuntu1) ... Setting up libgcc1:ppc64el (1:5.2.1-15ubuntu5) ... Processing triggers for libc-bin (2.21-0ubuntu4) ... (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 11595 files and directories currently installed.) Preparing to unpack .../libubsan0_5.2.1-15ubuntu5_ppc64el.deb ... Unpacking libubsan0:ppc64el (5.2.1-15ubuntu5) over (5.2.1-15ubuntu1) ... Preparing to unpack .../cpp-5_5.2.1-15ubuntu5_ppc64el.deb ... Unpacking cpp-5 (5.2.1-15ubuntu5) over (5.2.1-15ubuntu1) ... Preparing to unpack .../libcc1-0_5.2.1-15ubuntu5_ppc64el.deb ... Unpacking libcc1-0:ppc64el (5.2.1-15ubuntu5) over (5.2.1-15ubuntu1) ... Preparing to unpack .../g++-5_5.2.1-15ubuntu5_ppc64el.deb ... Unpacking g++-5 (5.2.1-15ubuntu5) over (5.2.1-15ubuntu1) ... Preparing to unpack .../gcc-5_5.2.1-15ubuntu5_ppc64el.deb ... Unpacking gcc-5 (5.2.1-15ubuntu5) over (5.2.1-15ubuntu1) ... Preparing to unpack .../libgcc-5-dev_5.2.1-15ubuntu5_ppc64el.deb ... Unpacking libgcc-5-dev:ppc64el (5.2.1-15ubuntu5) over (5.2.1-15ubuntu1) ... Preparing to unpack .../libstdc++-5-dev_5.2.1-15ubuntu5_ppc64el.deb ... Unpacking libstdc++-5-dev:ppc64el (5.2.1-15ubuntu5) over (5.2.1-15ubuntu1) ... Preparing to unpack .../libstdc++6_5.2.1-15ubuntu5_ppc64el.deb ... Unpacking libstdc++6:ppc64el (5.2.1-15ubuntu5) over (5.2.1-15ubuntu1) ... Setting up libstdc++6:ppc64el (5.2.1-15ubuntu5) ... Processing triggers for libc-bin (2.21-0ubuntu4) ... Selecting previously unselected package libapt-pkg4.16:ppc64el. (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 11602 files and directories currently installed.) Preparing to unpack .../libapt-pkg4.16_1.0.9.10ubuntu6_ppc64el.deb ... Unpacking libapt-pkg4.16:ppc64el (1.0.9.10ubuntu6) ... Setting up libapt-pkg4.16:ppc64el (1.0.9.10ubuntu6) ... Processing triggers for libc-bin (2.21-0ubuntu4) ... (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 11651 files and directories currently installed.) Preparing to unpack .../apt_1.0.9.10ubuntu6_ppc64el.deb ... Unpacking apt (1.0.9.10ubuntu6) over (1.0.9.10ubuntu1) ... Setting up apt (1.0.9.10ubuntu6) ... Processing triggers for libc-bin (2.21-0ubuntu4) ... (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 11651 files and directories currently installed.) Preparing to unpack .../debconf_1.5.57ubuntu1_all.deb ... Unpacking debconf (1.5.57ubuntu1) over (1.5.55ubuntu3) ... Setting up debconf (1.5.57ubuntu1) ... (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 11651 files and directories currently installed.) Preparing to unpack .../libpcre3_2%3a8.35-7ubuntu5_ppc64el.deb ... Unpacking libpcre3:ppc64el (2:8.35-7ubuntu5) over (2:8.35-7ubuntu2) ... Setting up libpcre3:ppc64el (2:8.35-7ubuntu5) ... Processing triggers for libc-bin (2.21-0ubuntu4) ... (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 11651 files and directories currently installed.) Preparing to unpack .../libsystemd0_224-2ubuntu2_ppc64el.deb ... Unpacking libsystemd0:ppc64el (224-2ubuntu2) over (224-1ubuntu2) ... Setting up libsystemd0:ppc64el (224-2ubuntu2) ... Processing triggers for libc-bin (2.21-0ubuntu4) ... (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 11651 files and directories currently installed.) Preparing to unpack .../systemd_224-2ubuntu2_ppc64el.deb ... Unpacking systemd (224-2ubuntu2) over (224-1ubuntu2) ... Setting up systemd (224-2ubuntu2) ... addgroup: The group `systemd-journal' already exists as a system group. Exiting. addgroup: The group `systemd-journal-remote' already exists as a system group. Exiting. (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 11625 files and directories currently installed.) Preparing to unpack .../libudev1_224-2ubuntu2_ppc64el.deb ... Unpacking libudev1:ppc64el (224-2ubuntu2) over (224-1ubuntu2) ... Setting up libudev1:ppc64el (224-2ubuntu2) ... Processing triggers for libc-bin (2.21-0ubuntu4) ... (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 11625 files and directories currently installed.) Preparing to unpack .../udev_224-2ubuntu2_ppc64el.deb ... Unpacking udev (224-2ubuntu2) over (224-1ubuntu2) ... Setting up udev (224-2ubuntu2) ... addgroup: The group `input' already exists as a system group. Exiting. A chroot environment has been detected, udev not started. Processing triggers for systemd (224-2ubuntu2) ... (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 11628 files and directories currently installed.) Preparing to unpack .../libkmod2_21-1ubuntu1_ppc64el.deb ... Unpacking libkmod2:ppc64el (21-1ubuntu1) over (18-3ubuntu1) ... Setting up libkmod2:ppc64el (21-1ubuntu1) ... Processing triggers for libc-bin (2.21-0ubuntu4) ... (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 11628 files and directories currently installed.) Preparing to unpack .../libapparmor1_2.10-0ubuntu4_ppc64el.deb ... Unpacking libapparmor1:ppc64el (2.10-0ubuntu4) over (2.10-0ubuntu2) ... Setting up libapparmor1:ppc64el (2.10-0ubuntu4) ... Processing triggers for libc-bin (2.21-0ubuntu4) ... (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 11628 files and directories currently installed.) Preparing to unpack .../libaudit-common_1%3a2.4.2-1ubuntu1_all.deb ... Unpacking libaudit-common (1:2.4.2-1ubuntu1) over (1:2.3.7-1ubuntu3) ... Setting up libaudit-common (1:2.4.2-1ubuntu1) ... (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 11628 files and directories currently installed.) Preparing to unpack .../libaudit1_1%3a2.4.2-1ubuntu1_ppc64el.deb ... Unpacking libaudit1:ppc64el (1:2.4.2-1ubuntu1) over (1:2.3.7-1ubuntu3) ... Setting up libaudit1:ppc64el (1:2.4.2-1ubuntu1) ... Processing triggers for libc-bin (2.21-0ubuntu4) ... (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 11628 files and directories currently installed.) Preparing to unpack .../libcryptsetup4_2%3a1.6.6-5ubuntu2_ppc64el.deb ... Unpacking libcryptsetup4:ppc64el (2:1.6.6-5ubuntu2) over (2:1.6.6-5ubuntu1) ... Setting up libcryptsetup4:ppc64el (2:1.6.6-5ubuntu2) ... Processing triggers for libc-bin (2.21-0ubuntu4) ... (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 11628 files and directories currently installed.) Preparing to unpack .../systemd-sysv_224-2ubuntu2_ppc64el.deb ... Unpacking systemd-sysv (224-2ubuntu2) over (224-1ubuntu2) ... Setting up systemd-sysv (224-2ubuntu2) ... (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 11628 files and directories currently installed.) Preparing to unpack .../apt-transport-https_1.0.9.10ubuntu6_ppc64el.deb ... Unpacking apt-transport-https (1.0.9.10ubuntu6) over (1.0.9.10ubuntu1) ... Preparing to unpack .../libdbus-1-3_1.9.20-1ubuntu2_ppc64el.deb ... Unpacking libdbus-1-3:ppc64el (1.9.20-1ubuntu2) over (1.8.12-1ubuntu5) ... Preparing to unpack .../dpkg-dev_1.18.2ubuntu3_all.deb ... Unpacking dpkg-dev (1.18.2ubuntu3) over (1.18.1ubuntu1) ... Preparing to unpack .../libdpkg-perl_1.18.2ubuntu3_all.deb ... Unpacking libdpkg-perl (1.18.2ubuntu3) over (1.18.1ubuntu1) ... Setting up libgomp1:ppc64el (5.2.1-15ubuntu5) ... Setting up libitm1:ppc64el (5.2.1-15ubuntu5) ... Setting up libatomic1:ppc64el (5.2.1-15ubuntu5) ... Setting up libasan2:ppc64el (5.2.1-15ubuntu5) ... Setting up libubsan0:ppc64el (5.2.1-15ubuntu5) ... Setting up cpp-5 (5.2.1-15ubuntu5) ... Setting up libcc1-0:ppc64el (5.2.1-15ubuntu5) ... Setting up libgcc-5-dev:ppc64el (5.2.1-15ubuntu5) ... Setting up gcc-5 (5.2.1-15ubuntu5) ... Setting up libstdc++-5-dev:ppc64el (5.2.1-15ubuntu5) ... Setting up g++-5 (5.2.1-15ubuntu5) ... Setting up apt-transport-https (1.0.9.10ubuntu6) ... Setting up libdbus-1-3:ppc64el (1.9.20-1ubuntu2) ... Setting up libdpkg-perl (1.18.2ubuntu3) ... Setting up dpkg-dev (1.18.2ubuntu3) ... Processing triggers for libc-bin (2.21-0ubuntu4) ... RUN: /usr/share/launchpad-buildd/slavebin/sbuild-package ['sbuild-package', 'PACKAGEBUILD-7857231', 'ppc64el', 'wily', '-c', 'chroot:autobuild', '--arch=ppc64el', '--dist=wily', '--purge=never', '--nolog', '-A', 'alarm-clock-applet_0.3.4-1.dsc'] Initiating build PACKAGEBUILD-7857231 with 4 jobs across 4 processor cores. Kernel reported to sbuild: 3.13.0-62-generic #102-Ubuntu SMP Tue Aug 11 14:42:17 UTC 2015 ppc64le sbuild (Debian sbuild) 0.65.2 (24 Mar 2015) on bos01-ppc64el-009.buildd ╔══════════════════════════════════════════════════════════════════════════════╗ ║ alarm-clock-applet 0.3.4-1 (ppc64el) 02 Sep 2015 09:46 ║ ╚══════════════════════════════════════════════════════════════════════════════╝ Package: alarm-clock-applet Version: 0.3.4-1 Source Version: 0.3.4-1 Distribution: wily Machine Architecture: ppc64el Host Architecture: ppc64el Build Architecture: ppc64el I: NOTICE: Log filtering will replace 'build/alarm-clock-applet-0QMTtt/alarm-clock-applet-0.3.4' with '«PKGBUILDDIR»' I: NOTICE: Log filtering will replace 'build/alarm-clock-applet-0QMTtt' with '«BUILDDIR»' I: NOTICE: Log filtering will replace 'home/buildd/build-PACKAGEBUILD-7857231/chroot-autobuild' with '«CHROOT»' ┌──────────────────────────────────────────────────────────────────────────────┐ │ Fetch source files │ └──────────────────────────────────────────────────────────────────────────────┘ Local sources ───────────── alarm-clock-applet_0.3.4-1.dsc exists in .; copying to chroot Check architectures ─────────────────── Check dependencies ────────────────── Merged Build-Depends: build-essential, fakeroot Filtered Build-Depends: build-essential, fakeroot dpkg-deb: building package 'sbuild-build-depends-core-dummy' in '/«BUILDDIR»/resolver-Ic4lWO/apt_archive/sbuild-build-depends-core-dummy.deb'. Ign file: ./ InRelease Ign file: ./ Release.gpg Get:1 file: ./ Release [2119 B] Ign file: ./ Translation-en Reading package lists... Reading package lists... ┌──────────────────────────────────────────────────────────────────────────────┐ │ Install core build dependencies (apt-based resolver) │ └──────────────────────────────────────────────────────────────────────────────┘ Installing build dependencies Reading package lists... Building dependency tree... Reading state information... The following package was automatically installed and is no longer required: libtimedate-perl Use 'apt-get autoremove' to remove it. The following NEW packages will be installed: sbuild-build-depends-core-dummy 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/770 B of archives. After this operation, 0 B of additional disk space will be used. WARNING: The following packages cannot be authenticated! sbuild-build-depends-core-dummy debconf: delaying package configuration, since apt-utils is not installed Authentication warning overridden. Selecting previously unselected package sbuild-build-depends-core-dummy. (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 11626 files and directories currently installed.) Preparing to unpack .../sbuild-build-depends-core-dummy.deb ... Unpacking sbuild-build-depends-core-dummy (0.invalid.0) ... Setting up sbuild-build-depends-core-dummy (0.invalid.0) ... Merged Build-Depends: base-files, base-passwd, bash, bsdutils, coreutils, dash, debianutils, diffutils, dpkg, e2fsprogs, findutils, grep, gzip, hostname, libc-bin, login, mount, ncurses-base, ncurses-bin, perl-base, sed, tar, util-linux, libc6-dev | libc-dev, gcc (>= 4:4.4.3), g++ (>= 4:4.4.3), make, dpkg-dev (>= 1.13.5), debhelper (>= 9), autotools-dev, intltool (>= 0.40), libglib2.0-dev (>= 2.16.0), libgtk2.0-dev (>= 2.12.0), libgconf2-dev (>= 2.8.0), libgstreamer1.0-dev, libnotify-dev (>= 0.4.1), gnome-icon-theme (>= 2.15.91), libxml2-dev, libunique-dev, libappindicator-dev (>= 0.0.7) Filtered Build-Depends: base-files, base-passwd, bash, bsdutils, coreutils, dash, debianutils, diffutils, dpkg, e2fsprogs, findutils, grep, gzip, hostname, libc-bin, login, mount, ncurses-base, ncurses-bin, perl-base, sed, tar, util-linux, libc6-dev | libc-dev, gcc (>= 4:4.4.3), g++ (>= 4:4.4.3), make, dpkg-dev (>= 1.13.5), debhelper (>= 9), autotools-dev, intltool (>= 0.40), libglib2.0-dev (>= 2.16.0), libgtk2.0-dev (>= 2.12.0), libgconf2-dev (>= 2.8.0), libgstreamer1.0-dev, libnotify-dev (>= 0.4.1), gnome-icon-theme (>= 2.15.91), libxml2-dev, libunique-dev, libappindicator-dev (>= 0.0.7) dpkg-deb: building package 'sbuild-build-depends-alarm-clock-applet-dummy' in '/«BUILDDIR»/resolver-jK2GJe/apt_archive/sbuild-build-depends-alarm-clock-applet-dummy.deb'. Ign file: ./ InRelease Ign file: ./ Release.gpg Get:1 file: ./ Release [2119 B] Ign file: ./ Translation-en Reading package lists... Reading package lists... ┌──────────────────────────────────────────────────────────────────────────────┐ │ Install alarm-clock-applet build dependencies (apt-based resolver) │ └──────────────────────────────────────────────────────────────────────────────┘ Installing build dependencies Reading package lists... Building dependency tree... Reading state information... The following extra packages will be installed: adwaita-icon-theme autoconf automake autotools-dev bsdmainutils dbus dbus-x11 dconf-gsettings-backend dconf-service debhelper dh-python file fontconfig fontconfig-config fonts-dejavu-core gconf-service gconf-service-backend gconf2 gconf2-common gettext gettext-base gir1.2-appindicator-0.1 gir1.2-atk-1.0 gir1.2-dbusmenu-glib-0.4 gir1.2-freedesktop gir1.2-gconf-2.0 gir1.2-gdkpixbuf-2.0 gir1.2-glib-2.0 gir1.2-gstreamer-1.0 gir1.2-gtk-2.0 gir1.2-notify-0.7 gir1.2-pango-1.0 glib-networking glib-networking-common glib-networking-services gnome-icon-theme groff-base gsettings-desktop-schemas hicolor-icon-theme humanity-icon-theme icu-devtools intltool intltool-debian libappindicator-dev libappindicator1 libasprintf0v5 libatk-bridge2.0-0 libatk1.0-0 libatk1.0-data libatk1.0-dev libatspi2.0-0 libavahi-client3 libavahi-common-data libavahi-common3 libboost-filesystem1.58.0 libboost-system1.58.0 libcairo-gobject2 libcairo-script-interpreter2 libcairo2 libcairo2-dev libcap-ng0 libcolord2 libcroco3 libcups2 libdatrie1 libdbus-1-dev libdbus-glib-1-2 libdbus-glib-1-dev libdbusmenu-glib-dev libdbusmenu-glib4 libdbusmenu-gtk4 libdconf1 libdrm-nouveau2 libdrm-radeon1 libdrm2 libegl1-mesa libelf1 libencode-locale-perl libepoxy0 libexpat1 libexpat1-dev libfile-listing-perl libfontconfig1 libfontconfig1-dev libfreetype6 libfreetype6-dev libgbm1 libgconf-2-4 libgconf2-dev libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-common libgdk-pixbuf2.0-dev libgirepository-1.0-1 libgl1-mesa-dri libglib2.0-0 libglib2.0-bin libglib2.0-data libglib2.0-dev libgraphite2-3 libgstreamer1.0-0 libgstreamer1.0-dev libgtk-3-0 libgtk-3-bin libgtk-3-common libgtk2.0-0 libgtk2.0-common libgtk2.0-dev libharfbuzz-dev libharfbuzz-gobject0 libharfbuzz-icu0 libharfbuzz0b libhtml-parser-perl libhtml-tagset-perl libhtml-tree-perl libhttp-cookies-perl libhttp-date-perl libhttp-message-perl libhttp-negotiate-perl libice-dev libice6 libicu-dev libicu55 libindicator7 libio-html-perl libio-socket-ssl-perl libjasper1 libjbig0 libjpeg-turbo8 libjpeg8 libjson-glib-1.0-0 libjson-glib-1.0-common liblcms2-2 liblwp-mediatypes-perl liblwp-protocol-https-perl liblzo2-2 libmagic1 libmirclient9 libmircommon5 libmirprotobuf1 libmpdec2 libnet-http-perl libnet-ssleay-perl libnotify-dev libnotify4 libpango-1.0-0 libpango1.0-dev libpangocairo-1.0-0 libpangoft2-1.0-0 libpangoxft-1.0-0 libpcre16-3 libpcre3-dev libpcre32-3 libpcrecpp0v5 libpipeline1 libpixman-1-0 libpixman-1-dev libpng12-dev libprotobuf-lite9v5 libproxy1v5 libpthread-stubs0-dev libpython-stdlib libpython2.7-minimal libpython2.7-stdlib libpython3-stdlib libpython3.4-minimal libpython3.4-stdlib librest-0.7-0 librsvg2-2 librsvg2-common libsigsegv2 libsm-dev libsm6 libsoup-gnome2.4-1 libsoup2.4-1 libthai-data libthai0 libtiff5 libunique-1.0-0 libunique-dev libunistring0 liburi-perl libwayland-client0 libwayland-cursor0 libwayland-egl1-mesa libwayland-server0 libwww-perl libwww-robotrules-perl libx11-6 libx11-data libx11-dev libx11-xcb1 libxau-dev libxau6 libxcb-dri2-0 libxcb-render0 libxcb-render0-dev libxcb-shm0 libxcb-shm0-dev libxcb-xfixes0 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 libxkbcommon0 libxml-parser-perl libxml2 libxml2-dev libxml2-utils libxrandr-dev libxrandr2 libxrender-dev libxrender1 m4 man-db mime-support netbase pkg-config po-debconf psmisc python python-minimal python2.7 python2.7-minimal python3 python3-minimal python3.4 python3.4-minimal shared-mime-info ubuntu-mono ucf x11-common x11proto-composite-dev x11proto-core-dev x11proto-damage-dev x11proto-fixes-dev x11proto-input-dev x11proto-kb-dev x11proto-randr-dev x11proto-render-dev x11proto-xext-dev x11proto-xinerama-dev xkb-data xorg-sgml-doctools xtrans-dev zlib1g-dev Suggested packages: autoconf-archive gnu-standards autoconf-doc libtool wamerican wordlist whois vacation dh-make gconf-defaults-service gettext-doc groff libcairo2-doc cups-common libglib2.0-doc gstreamer1.0-tools gstreamer1.0-plugins-base gstreamer1.0-doc gvfs libgtk2.0-doc libdata-dump-perl libice-doc icu-doc libjasper-runtime liblcms2-utils libcrypt-ssleay-perl imagemagick libpango1.0-doc librsvg2-bin libsm-doc libunique-doc libauthen-ntlm-perl libxcb-doc libxext-doc less www-browser libmail-box-perl python-doc python-tk python2.7-doc binfmt-support python3-doc python3-tk python3-venv python3.4-venv python3.4-doc Recommended packages: curl wget lynx-cur libasprintf-dev libgettextpo-dev indicator-application at-spi2-core colord libgconf2-doc libtxc-dxtn-s2tc0 libtxc-dxtn0 xdg-user-dirs libgtk2.0-bin libhtml-format-perl notification-daemon libhtml-form-perl libhttp-daemon-perl libmailtools-perl libx11-doc xml-core ifupdown libmail-sendmail-perl The following NEW packages will be installed: adwaita-icon-theme autoconf automake autotools-dev bsdmainutils dbus dbus-x11 dconf-gsettings-backend dconf-service debhelper dh-python file fontconfig fontconfig-config fonts-dejavu-core gconf-service gconf-service-backend gconf2 gconf2-common gettext gettext-base gir1.2-appindicator-0.1 gir1.2-atk-1.0 gir1.2-dbusmenu-glib-0.4 gir1.2-freedesktop gir1.2-gconf-2.0 gir1.2-gdkpixbuf-2.0 gir1.2-glib-2.0 gir1.2-gstreamer-1.0 gir1.2-gtk-2.0 gir1.2-notify-0.7 gir1.2-pango-1.0 glib-networking glib-networking-common glib-networking-services gnome-icon-theme groff-base gsettings-desktop-schemas hicolor-icon-theme humanity-icon-theme icu-devtools intltool intltool-debian libappindicator-dev libappindicator1 libasprintf0v5 libatk-bridge2.0-0 libatk1.0-0 libatk1.0-data libatk1.0-dev libatspi2.0-0 libavahi-client3 libavahi-common-data libavahi-common3 libboost-filesystem1.58.0 libboost-system1.58.0 libcairo-gobject2 libcairo-script-interpreter2 libcairo2 libcairo2-dev libcap-ng0 libcolord2 libcroco3 libcups2 libdatrie1 libdbus-1-dev libdbus-glib-1-2 libdbus-glib-1-dev libdbusmenu-glib-dev libdbusmenu-glib4 libdbusmenu-gtk4 libdconf1 libdrm-nouveau2 libdrm-radeon1 libdrm2 libegl1-mesa libelf1 libencode-locale-perl libepoxy0 libexpat1 libexpat1-dev libfile-listing-perl libfontconfig1 libfontconfig1-dev libfreetype6 libfreetype6-dev libgbm1 libgconf-2-4 libgconf2-dev libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-common libgdk-pixbuf2.0-dev libgirepository-1.0-1 libgl1-mesa-dri libglib2.0-0 libglib2.0-bin libglib2.0-data libglib2.0-dev libgraphite2-3 libgstreamer1.0-0 libgstreamer1.0-dev libgtk-3-0 libgtk-3-bin libgtk-3-common libgtk2.0-0 libgtk2.0-common libgtk2.0-dev libharfbuzz-dev libharfbuzz-gobject0 libharfbuzz-icu0 libharfbuzz0b libhtml-parser-perl libhtml-tagset-perl libhtml-tree-perl libhttp-cookies-perl libhttp-date-perl libhttp-message-perl libhttp-negotiate-perl libice-dev libice6 libicu-dev libicu55 libindicator7 libio-html-perl libio-socket-ssl-perl libjasper1 libjbig0 libjpeg-turbo8 libjpeg8 libjson-glib-1.0-0 libjson-glib-1.0-common liblcms2-2 liblwp-mediatypes-perl liblwp-protocol-https-perl liblzo2-2 libmagic1 libmirclient9 libmircommon5 libmirprotobuf1 libmpdec2 libnet-http-perl libnet-ssleay-perl libnotify-dev libnotify4 libpango-1.0-0 libpango1.0-dev libpangocairo-1.0-0 libpangoft2-1.0-0 libpangoxft-1.0-0 libpcre16-3 libpcre3-dev libpcre32-3 libpcrecpp0v5 libpipeline1 libpixman-1-0 libpixman-1-dev libpng12-dev libprotobuf-lite9v5 libproxy1v5 libpthread-stubs0-dev libpython-stdlib libpython2.7-minimal libpython2.7-stdlib libpython3-stdlib libpython3.4-minimal libpython3.4-stdlib librest-0.7-0 librsvg2-2 librsvg2-common libsigsegv2 libsm-dev libsm6 libsoup-gnome2.4-1 libsoup2.4-1 libthai-data libthai0 libtiff5 libunique-1.0-0 libunique-dev libunistring0 liburi-perl libwayland-client0 libwayland-cursor0 libwayland-egl1-mesa libwayland-server0 libwww-perl libwww-robotrules-perl libx11-6 libx11-data libx11-dev libx11-xcb1 libxau-dev libxau6 libxcb-dri2-0 libxcb-render0 libxcb-render0-dev libxcb-shm0 libxcb-shm0-dev libxcb-xfixes0 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 libxkbcommon0 libxml-parser-perl libxml2 libxml2-dev libxml2-utils libxrandr-dev libxrandr2 libxrender-dev libxrender1 m4 man-db mime-support netbase pkg-config po-debconf psmisc python python-minimal python2.7 python2.7-minimal python3 python3-minimal python3.4 python3.4-minimal sbuild-build-depends-alarm-clock-applet-dummy shared-mime-info ubuntu-mono ucf x11-common x11proto-composite-dev x11proto-core-dev x11proto-damage-dev x11proto-fixes-dev x11proto-input-dev x11proto-kb-dev x11proto-randr-dev x11proto-render-dev x11proto-xext-dev x11proto-xinerama-dev xkb-data xorg-sgml-doctools xtrans-dev zlib1g-dev 0 upgraded, 262 newly installed, 0 to remove and 0 not upgraded. Need to get 67.5 MB/67.5 MB of archives. After this operation, 424 MB of additional disk space will be used. WARNING: The following packages cannot be authenticated! sbuild-build-depends-alarm-clock-applet-dummy Authentication warning overridden. Get:1 http://ftpmaster.internal/ubuntu/ wily/main libmpdec2 ppc64el 2.4.1-1 [84.7 kB] Get:2 http://ftpmaster.internal/ubuntu/ wily/main libpython3.4-minimal ppc64el 3.4.3-8 [462 kB] Get:3 http://ftpmaster.internal/ubuntu/ wily/main mime-support all 3.58ubuntu1 [31.6 kB] Get:4 http://ftpmaster.internal/ubuntu/ wily/main libpython3.4-stdlib ppc64el 3.4.3-8 [2009 kB] Get:5 http://ftpmaster.internal/ubuntu/ wily/main libexpat1 ppc64el 2.1.0-7 [76.5 kB] Get:6 http://ftpmaster.internal/ubuntu/ wily/main python3.4-minimal ppc64el 3.4.3-8 [1180 kB] Get:7 http://ftpmaster.internal/ubuntu/ wily/main python3-minimal ppc64el 3.4.3-4ubuntu1 [23.4 kB] Get:8 http://ftpmaster.internal/ubuntu/ wily/main python3.4 ppc64el 3.4.3-8 [183 kB] Get:9 http://ftpmaster.internal/ubuntu/ wily/main libpython3-stdlib ppc64el 3.4.3-4ubuntu1 [6990 B] Get:10 http://ftpmaster.internal/ubuntu/ wily/main dh-python all 2.20150826 [69.6 kB] Get:11 http://ftpmaster.internal/ubuntu/ wily/main python3 ppc64el 3.4.3-4ubuntu1 [8818 B] Get:12 http://ftpmaster.internal/ubuntu/ wily/main libasprintf0v5 ppc64el 0.19.4-1ubuntu3 [6832 B] Get:13 http://ftpmaster.internal/ubuntu/ wily/main libcap-ng0 ppc64el 0.7.6-1 [11.3 kB] Get:14 http://ftpmaster.internal/ubuntu/ wily/main libxau6 ppc64el 1:1.0.8-1 [7460 B] Get:15 http://ftpmaster.internal/ubuntu/ wily/main libxdmcp6 ppc64el 1:1.1.2-1 [11.9 kB] Get:16 http://ftpmaster.internal/ubuntu/ wily/main libxcb1 ppc64el 1.11-0ubuntu1 [37.7 kB] Get:17 http://ftpmaster.internal/ubuntu/ wily/main libx11-data all 2:1.6.3-1ubuntu1 [113 kB] Get:18 http://ftpmaster.internal/ubuntu/ wily/main libx11-6 ppc64el 2:1.6.3-1ubuntu1 [573 kB] Get:19 http://ftpmaster.internal/ubuntu/ wily/main libxext6 ppc64el 2:1.3.3-1 [30.7 kB] Get:20 http://ftpmaster.internal/ubuntu/ wily/main groff-base ppc64el 1.22.3-1 [1396 kB] Get:21 http://ftpmaster.internal/ubuntu/ wily/main bsdmainutils ppc64el 9.0.6ubuntu1 [175 kB] Get:22 http://ftpmaster.internal/ubuntu/ wily/main libpipeline1 ppc64el 1.4.1-1 [24.0 kB] Get:23 http://ftpmaster.internal/ubuntu/ wily/main man-db ppc64el 2.7.2-1 [850 kB] Get:24 http://ftpmaster.internal/ubuntu/ wily/main fonts-dejavu-core all 2.35-1 [1039 kB] Get:25 http://ftpmaster.internal/ubuntu/ wily/main ucf all 3.0030 [55.5 kB] Get:26 http://ftpmaster.internal/ubuntu/ wily/main fontconfig-config all 2.11.1-0ubuntu6 [48.7 kB] Get:27 http://ftpmaster.internal/ubuntu/ wily/main libfreetype6 ppc64el 2.5.2-4ubuntu1 [333 kB] Get:28 http://ftpmaster.internal/ubuntu/ wily/main libfontconfig1 ppc64el 2.11.1-0ubuntu6 [141 kB] Get:29 http://ftpmaster.internal/ubuntu/ wily/main fontconfig ppc64el 2.11.1-0ubuntu6 [175 kB] Get:30 http://ftpmaster.internal/ubuntu/ wily/main libdbusmenu-glib4 ppc64el 12.10.3+15.04.20150410.2-0ubuntu1 [37.3 kB] Get:31 http://ftpmaster.internal/ubuntu/ wily/main libglib2.0-0 ppc64el 2.45.6-1 [1032 kB] Get:32 http://ftpmaster.internal/ubuntu/ wily/main libatk1.0-data all 2.16.0-2 [16.9 kB] Get:33 http://ftpmaster.internal/ubuntu/ wily/main libatk1.0-0 ppc64el 2.16.0-2 [53.3 kB] Get:34 http://ftpmaster.internal/ubuntu/ wily/main libjpeg-turbo8 ppc64el 1.3.0-0ubuntu2 [119 kB] Get:35 http://ftpmaster.internal/ubuntu/ wily/main libjpeg8 ppc64el 8c-2ubuntu8 [2146 B] Get:36 http://ftpmaster.internal/ubuntu/ wily/main libjasper1 ppc64el 1.900.1-debian1-2.4 [142 kB] Get:37 http://ftpmaster.internal/ubuntu/ wily/main libjbig0 ppc64el 2.1-3.1 [26.4 kB] Get:38 http://ftpmaster.internal/ubuntu/ wily/main libtiff5 ppc64el 4.0.3-12.3ubuntu2 [156 kB] Get:39 http://ftpmaster.internal/ubuntu/ wily/main libgdk-pixbuf2.0-common all 2.31.5-1 [10.2 kB] Get:40 http://ftpmaster.internal/ubuntu/ wily/main libgdk-pixbuf2.0-0 ppc64el 2.31.5-1 [184 kB] Get:41 http://ftpmaster.internal/ubuntu/ wily/main libthai-data all 0.1.22-2 [131 kB] Get:42 http://ftpmaster.internal/ubuntu/ wily/main libdatrie1 ppc64el 0.2.9-2 [16.6 kB] Get:43 http://ftpmaster.internal/ubuntu/ wily/main libthai0 ppc64el 0.1.22-2 [17.2 kB] Get:44 http://ftpmaster.internal/ubuntu/ wily/main libpango-1.0-0 ppc64el 1.36.8-3 [156 kB] Get:45 http://ftpmaster.internal/ubuntu/ wily/main libdbusmenu-gtk4 ppc64el 12.10.3+15.04.20150410.2-0ubuntu1 [25.4 kB] Get:46 http://ftpmaster.internal/ubuntu/ wily/main libgtk2.0-common all 2.24.28-0ubuntu1 [121 kB] Get:47 http://ftpmaster.internal/ubuntu/ wily/main libpixman-1-0 ppc64el 0.32.6-3 [188 kB] Get:48 http://ftpmaster.internal/ubuntu/ wily/main libxcb-render0 ppc64el 1.11-0ubuntu1 [11.0 kB] Get:49 http://ftpmaster.internal/ubuntu/ wily/main libxcb-shm0 ppc64el 1.11-0ubuntu1 [5768 B] Get:50 http://ftpmaster.internal/ubuntu/ wily/main libxrender1 ppc64el 1:0.9.9-0ubuntu1 [18.1 kB] Get:51 http://ftpmaster.internal/ubuntu/ wily/main libcairo2 ppc64el 1.14.2-2ubuntu2 [605 kB] Get:52 http://ftpmaster.internal/ubuntu/ wily/main libavahi-common-data ppc64el 0.6.31-4ubuntu4 [21.1 kB] Get:53 http://ftpmaster.internal/ubuntu/ wily/main libavahi-common3 ppc64el 0.6.31-4ubuntu4 [19.9 kB] Get:54 http://ftpmaster.internal/ubuntu/ wily/main libavahi-client3 ppc64el 0.6.31-4ubuntu4 [23.0 kB] Get:55 http://ftpmaster.internal/ubuntu/ wily/main libcups2 ppc64el 2.1~rc1-3 [190 kB] Get:56 http://ftpmaster.internal/ubuntu/ wily/main libgraphite2-3 ppc64el 1.2.4-3ubuntu1 [52.3 kB] Get:57 http://ftpmaster.internal/ubuntu/ wily/main libharfbuzz0b ppc64el 1.0.1-1build1 [137 kB] Get:58 http://ftpmaster.internal/ubuntu/ wily/main libpangoft2-1.0-0 ppc64el 1.36.8-3 [34.1 kB] Get:59 http://ftpmaster.internal/ubuntu/ wily/main libpangocairo-1.0-0 ppc64el 1.36.8-3 [20.6 kB] Get:60 http://ftpmaster.internal/ubuntu/ wily/main libxcomposite1 ppc64el 1:0.4.4-1 [6872 B] Get:61 http://ftpmaster.internal/ubuntu/ wily/main libxfixes3 ppc64el 1:5.0.1-2 [11.2 kB] Get:62 http://ftpmaster.internal/ubuntu/ wily/main libxcursor1 ppc64el 1:1.1.14-1 [21.6 kB] Get:63 http://ftpmaster.internal/ubuntu/ wily/main libxdamage1 ppc64el 1:1.1.4-2 [6820 B] Get:64 http://ftpmaster.internal/ubuntu/ wily/main libxi6 ppc64el 2:1.7.4-1 [28.5 kB] Get:65 http://ftpmaster.internal/ubuntu/ wily/main libxinerama1 ppc64el 2:1.1.3-1 [7160 B] Get:66 http://ftpmaster.internal/ubuntu/ wily/main libxrandr2 ppc64el 2:1.5.0-1 [16.8 kB] Get:67 http://ftpmaster.internal/ubuntu/ wily/main libicu55 ppc64el 55.1-4 [7760 kB] Get:68 http://ftpmaster.internal/ubuntu/ wily/main libxml2 ppc64el 2.9.2+dfsg1-3ubuntu1 [606 kB] Get:69 http://ftpmaster.internal/ubuntu/ wily/main shared-mime-info ppc64el 1.3-1 [389 kB] Get:70 http://ftpmaster.internal/ubuntu/ wily/main libgtk2.0-0 ppc64el 2.24.28-0ubuntu1 [1572 kB] Get:71 http://ftpmaster.internal/ubuntu/ wily/main libindicator7 ppc64el 12.10.2+14.10.20140922-0ubuntu1 [20.3 kB] Get:72 http://ftpmaster.internal/ubuntu/ wily/main libappindicator1 ppc64el 12.10.1+15.04.20141110-0ubuntu1 [17.1 kB] Get:73 http://ftpmaster.internal/ubuntu/ wily/main libcroco3 ppc64el 0.6.8-3 [77.2 kB] Get:74 http://ftpmaster.internal/ubuntu/ wily/main x11-common all 1:7.7+7ubuntu4 [58.6 kB] Get:75 http://ftpmaster.internal/ubuntu/ wily/main libice6 ppc64el 2:1.0.9-1 [38.0 kB] Get:76 http://ftpmaster.internal/ubuntu/ wily/main liblcms2-2 ppc64el 2.6-3ubuntu2 [169 kB] Get:77 http://ftpmaster.internal/ubuntu/ wily/main liblzo2-2 ppc64el 2.08-1.2 [67.2 kB] Get:78 http://ftpmaster.internal/ubuntu/ wily/main libnotify4 ppc64el 0.7.6-2svn1 [16.1 kB] Get:79 http://ftpmaster.internal/ubuntu/ wily/main libxft2 ppc64el 2.3.2-1 [39.3 kB] Get:80 http://ftpmaster.internal/ubuntu/ wily/main libpangoxft-1.0-0 ppc64el 1.36.8-3 [15.4 kB] Get:81 http://ftpmaster.internal/ubuntu/ wily/main libpcrecpp0v5 ppc64el 2:8.35-7ubuntu5 [16.1 kB] Get:82 http://ftpmaster.internal/ubuntu/ wily/main libproxy1v5 ppc64el 0.4.11-4ubuntu3~gcc5.3 [53.7 kB] Get:83 http://ftpmaster.internal/ubuntu/ wily/main glib-networking-common all 2.45.1-1build1 [10.9 kB] Get:84 http://ftpmaster.internal/ubuntu/ wily/main glib-networking-services ppc64el 2.45.1-1build1 [15.8 kB] Get:85 http://ftpmaster.internal/ubuntu/ wily/main libdconf1 ppc64el 0.24.0-2 [30.4 kB] Get:86 http://ftpmaster.internal/ubuntu/ wily/main dconf-service ppc64el 0.24.0-2 [28.1 kB] Get:87 http://ftpmaster.internal/ubuntu/ wily/main dconf-gsettings-backend ppc64el 0.24.0-2 [18.6 kB] Get:88 http://ftpmaster.internal/ubuntu/ wily/main gsettings-desktop-schemas all 3.16.1-1ubuntu1 [25.8 kB] Get:89 http://ftpmaster.internal/ubuntu/ wily/main glib-networking ppc64el 2.45.1-1build1 [38.2 kB] Get:90 http://ftpmaster.internal/ubuntu/ wily/main libsoup2.4-1 ppc64el 2.50.0-2 [244 kB] Get:91 http://ftpmaster.internal/ubuntu/ wily/main libsoup-gnome2.4-1 ppc64el 2.50.0-2 [5152 B] Get:92 http://ftpmaster.internal/ubuntu/ wily/main librest-0.7-0 ppc64el 0.7.93-1 [28.8 kB] Get:93 http://ftpmaster.internal/ubuntu/ wily/main libsigsegv2 ppc64el 2.10-4 [13.9 kB] Get:94 http://ftpmaster.internal/ubuntu/ wily/main libsm6 ppc64el 2:1.2.2-1 [15.1 kB] Get:95 http://ftpmaster.internal/ubuntu/ wily/main libunistring0 ppc64el 0.9.3-5.2ubuntu1 [269 kB] Get:96 http://ftpmaster.internal/ubuntu/ wily/main libpython2.7-minimal ppc64el 2.7.10-3 [338 kB] Get:97 http://ftpmaster.internal/ubuntu/ wily/main python2.7-minimal ppc64el 2.7.10-3 [971 kB] Get:98 http://ftpmaster.internal/ubuntu/ wily/main python-minimal ppc64el 2.7.9-1 [28.4 kB] Get:99 http://ftpmaster.internal/ubuntu/ wily/main libpython2.7-stdlib ppc64el 2.7.10-3 [1763 kB] Get:100 http://ftpmaster.internal/ubuntu/ wily/main python2.7 ppc64el 2.7.10-3 [210 kB] Get:101 http://ftpmaster.internal/ubuntu/ wily/main libpython-stdlib ppc64el 2.7.9-1 [7798 B] Get:102 http://ftpmaster.internal/ubuntu/ wily/main python ppc64el 2.7.9-1 [137 kB] Get:103 http://ftpmaster.internal/ubuntu/ wily/main libmagic1 ppc64el 1:5.22+15-2ubuntu1 [215 kB] Get:104 http://ftpmaster.internal/ubuntu/ wily/main file ppc64el 1:5.22+15-2ubuntu1 [21.2 kB] Get:105 http://ftpmaster.internal/ubuntu/ wily/main netbase all 5.3 [12.9 kB] Get:106 http://ftpmaster.internal/ubuntu/ wily/main xkb-data all 2.12-1ubuntu1 [297 kB] Get:107 http://ftpmaster.internal/ubuntu/ wily/main dbus ppc64el 1.9.20-1ubuntu2 [134 kB] Get:108 http://ftpmaster.internal/ubuntu/ wily/main gettext-base ppc64el 0.19.4-1ubuntu3 [47.2 kB] Get:109 http://ftpmaster.internal/ubuntu/ wily/main libgirepository-1.0-1 ppc64el 1.44.0-1 [85.7 kB] Get:110 http://ftpmaster.internal/ubuntu/ wily/main gir1.2-glib-2.0 ppc64el 1.44.0-1 [126 kB] Get:111 http://ftpmaster.internal/ubuntu/ wily/main libdbus-glib-1-2 ppc64el 0.104-1build1 [65.7 kB] Get:112 http://ftpmaster.internal/ubuntu/ wily/main libdrm2 ppc64el 2.4.64-1 [27.1 kB] Get:113 http://ftpmaster.internal/ubuntu/ wily/main libelf1 ppc64el 0.163-4ubuntu1 [38.4 kB] Get:114 http://ftpmaster.internal/ubuntu/ wily/main libglib2.0-data all 2.45.6-1 [127 kB] Get:115 http://ftpmaster.internal/ubuntu/ wily/main psmisc ppc64el 22.21-2build1 [48.4 kB] Get:116 http://ftpmaster.internal/ubuntu/ wily/main hicolor-icon-theme all 0.15-0ubuntu1 [7750 B] Get:117 http://ftpmaster.internal/ubuntu/ wily/main libgtk-3-common all 3.16.6-1ubuntu1 [196 kB] Get:118 http://ftpmaster.internal/ubuntu/ wily/main libatspi2.0-0 ppc64el 2.16.0-1ubuntu1 [54.9 kB] Get:119 http://ftpmaster.internal/ubuntu/ wily/main libatk-bridge2.0-0 ppc64el 2.16.0-1ubuntu1 [50.1 kB] Get:120 http://ftpmaster.internal/ubuntu/ wily/main libcairo-gobject2 ppc64el 1.14.2-2ubuntu2 [17.1 kB] Get:121 http://ftpmaster.internal/ubuntu/ wily/main libcolord2 ppc64el 1.2.11-0ubuntu1 [96.5 kB] Get:122 http://ftpmaster.internal/ubuntu/ wily/main libepoxy0 ppc64el 1.2-1 [146 kB] Get:123 http://ftpmaster.internal/ubuntu/ wily/main libjson-glib-1.0-common all 1.0.4-1 [5852 B] Get:124 http://ftpmaster.internal/ubuntu/ wily/main libjson-glib-1.0-0 ppc64el 1.0.4-1 [50.6 kB] Get:125 http://ftpmaster.internal/ubuntu/ wily/main libboost-system1.58.0 ppc64el 1.58.0+dfsg-0ubuntu5 [9782 B] Get:126 http://ftpmaster.internal/ubuntu/ wily/main libboost-filesystem1.58.0 ppc64el 1.58.0+dfsg-0ubuntu5 [37.7 kB] Get:127 http://ftpmaster.internal/ubuntu/ wily/main libmircommon5 ppc64el 0.15.1+15.10.20150825-0ubuntu1 [63.3 kB] Get:128 http://ftpmaster.internal/ubuntu/ wily/main libprotobuf-lite9v5 ppc64el 2.6.1-1.2 [57.1 kB] Get:129 http://ftpmaster.internal/ubuntu/ wily/main libmirprotobuf1 ppc64el 0.15.1+15.10.20150825-0ubuntu1 [94.3 kB] Get:130 http://ftpmaster.internal/ubuntu/ wily/main libxkbcommon0 ppc64el 0.5.0-1ubuntu2 [110 kB] Get:131 http://ftpmaster.internal/ubuntu/ wily/main libmirclient9 ppc64el 0.15.1+15.10.20150825-0ubuntu1 [160 kB] Get:132 http://ftpmaster.internal/ubuntu/ wily/main libwayland-client0 ppc64el 1.8.1-1 [21.3 kB] Get:133 http://ftpmaster.internal/ubuntu/ wily/main libwayland-cursor0 ppc64el 1.8.1-1 [11.3 kB] Get:134 http://ftpmaster.internal/ubuntu/ wily/main libwayland-server0 ppc64el 1.8.1-1 [25.8 kB] Get:135 http://ftpmaster.internal/ubuntu/ wily/main libdrm-nouveau2 ppc64el 2.4.64-1 [15.4 kB] Get:136 http://ftpmaster.internal/ubuntu/ wily/main libdrm-radeon1 ppc64el 2.4.64-1 [23.1 kB] Get:137 http://ftpmaster.internal/ubuntu/ wily/main libgl1-mesa-dri ppc64el 10.6.3-1ubuntu1 [4023 kB] Get:138 http://ftpmaster.internal/ubuntu/ wily/main libgbm1 ppc64el 10.6.3-1ubuntu1 [24.0 kB] Get:139 http://ftpmaster.internal/ubuntu/ wily/main libx11-xcb1 ppc64el 2:1.6.3-1ubuntu1 [9148 B] Get:140 http://ftpmaster.internal/ubuntu/ wily/main libxcb-dri2-0 ppc64el 1.11-0ubuntu1 [6986 B] Get:141 http://ftpmaster.internal/ubuntu/ wily/main libxcb-xfixes0 ppc64el 1.11-0ubuntu1 [8612 B] Get:142 http://ftpmaster.internal/ubuntu/ wily/main libegl1-mesa ppc64el 10.6.3-1ubuntu1 [60.0 kB] Get:143 http://ftpmaster.internal/ubuntu/ wily/main libwayland-egl1-mesa ppc64el 10.6.3-1ubuntu1 [6728 B] Get:144 http://ftpmaster.internal/ubuntu/ wily/main libgtk-3-0 ppc64el 3.16.6-1ubuntu1 [2214 kB] Get:145 http://ftpmaster.internal/ubuntu/ wily/main libgtk-3-bin ppc64el 3.16.6-1ubuntu1 [49.4 kB] Get:146 http://ftpmaster.internal/ubuntu/ wily/main librsvg2-2 ppc64el 2.40.10-1 [102 kB] Get:147 http://ftpmaster.internal/ubuntu/ wily/main librsvg2-common ppc64el 2.40.10-1 [5144 B] Get:148 http://ftpmaster.internal/ubuntu/ wily/main humanity-icon-theme all 0.6.9 [1315 kB] Get:149 http://ftpmaster.internal/ubuntu/ wily/main ubuntu-mono all 14.04+15.10.20150813-0ubuntu1 [177 kB] Get:150 http://ftpmaster.internal/ubuntu/ wily/main adwaita-icon-theme all 3.16.2.1-2ubuntu1 [944 kB] Get:151 http://ftpmaster.internal/ubuntu/ wily/main m4 ppc64el 1.4.17-4 [194 kB] Get:152 http://ftpmaster.internal/ubuntu/ wily/main autoconf all 2.69-8 [321 kB] Get:153 http://ftpmaster.internal/ubuntu/ wily/main autotools-dev all 20140911.1 [39.6 kB] Get:154 http://ftpmaster.internal/ubuntu/ wily/main automake all 1:1.15-1ubuntu1 [511 kB] Get:155 http://ftpmaster.internal/ubuntu/ wily/main dbus-x11 ppc64el 1.9.20-1ubuntu2 [21.3 kB] Get:156 http://ftpmaster.internal/ubuntu/ wily/main gettext ppc64el 0.19.4-1ubuntu3 [874 kB] Get:157 http://ftpmaster.internal/ubuntu/ wily/main intltool-debian all 0.35.0+20060710.2 [24.5 kB] Get:158 http://ftpmaster.internal/ubuntu/ wily/main po-debconf all 1.0.18 [234 kB] Get:159 http://ftpmaster.internal/ubuntu/ wily/main debhelper all 9.20150811ubuntu1 [731 kB] Get:160 http://ftpmaster.internal/ubuntu/ wily/main gconf2-common all 3.2.6-3ubuntu3 [21.1 kB] Get:161 http://ftpmaster.internal/ubuntu/ wily/main libgconf-2-4 ppc64el 3.2.6-3ubuntu3 [79.2 kB] Get:162 http://ftpmaster.internal/ubuntu/ wily/main gconf-service-backend ppc64el 3.2.6-3ubuntu3 [56.3 kB] Get:163 http://ftpmaster.internal/ubuntu/ wily/main gconf-service ppc64el 3.2.6-3ubuntu3 [2104 B] Get:164 http://ftpmaster.internal/ubuntu/ wily/main gconf2 ppc64el 3.2.6-3ubuntu3 [69.7 kB] Get:165 http://ftpmaster.internal/ubuntu/ wily/main gir1.2-atk-1.0 ppc64el 2.16.0-2 [17.7 kB] Get:166 http://ftpmaster.internal/ubuntu/ wily/main gir1.2-freedesktop ppc64el 1.44.0-1 [5770 B] Get:167 http://ftpmaster.internal/ubuntu/ wily/main gir1.2-gdkpixbuf-2.0 ppc64el 2.31.5-1 [8146 B] Get:168 http://ftpmaster.internal/ubuntu/ wily/main gir1.2-pango-1.0 ppc64el 1.36.8-3 [20.9 kB] Get:169 http://ftpmaster.internal/ubuntu/ wily/main gir1.2-gtk-2.0 ppc64el 2.24.28-0ubuntu1 [172 kB] Get:170 http://ftpmaster.internal/ubuntu/ wily/main gir1.2-appindicator-0.1 ppc64el 12.10.1+15.04.20141110-0ubuntu1 [3408 B] Get:171 http://ftpmaster.internal/ubuntu/ wily/main gir1.2-dbusmenu-glib-0.4 ppc64el 12.10.3+15.04.20150410.2-0ubuntu1 [6230 B] Get:172 http://ftpmaster.internal/ubuntu/ wily/main gir1.2-gconf-2.0 ppc64el 3.2.6-3ubuntu3 [6256 B] Get:173 http://ftpmaster.internal/ubuntu/ wily/main libgstreamer1.0-0 ppc64el 1.5.2-1 [646 kB] Get:174 http://ftpmaster.internal/ubuntu/ wily/main gir1.2-gstreamer-1.0 ppc64el 1.5.2-1 [64.7 kB] Get:175 http://ftpmaster.internal/ubuntu/ wily/main gir1.2-notify-0.7 ppc64el 0.7.6-2svn1 [3534 B] Get:176 http://ftpmaster.internal/ubuntu/ wily/main gnome-icon-theme all 3.12.0-1ubuntu1 [779 kB] Get:177 http://ftpmaster.internal/ubuntu/ wily/main icu-devtools ppc64el 55.1-4 [175 kB] Get:178 http://ftpmaster.internal/ubuntu/ wily/main liburi-perl all 1.69-1 [84.5 kB] Get:179 http://ftpmaster.internal/ubuntu/ wily/main libencode-locale-perl all 1.03-1 [12.4 kB] Get:180 http://ftpmaster.internal/ubuntu/ wily/main libhttp-date-perl all 6.02-1 [10.4 kB] Get:181 http://ftpmaster.internal/ubuntu/ wily/main libfile-listing-perl all 6.04-1 [9774 B] Get:182 http://ftpmaster.internal/ubuntu/ wily/main libhtml-tagset-perl all 3.20-2 [13.5 kB] Get:183 http://ftpmaster.internal/ubuntu/ wily/main libhtml-parser-perl ppc64el 3.71-2 [95.7 kB] Get:184 http://ftpmaster.internal/ubuntu/ wily/main libhtml-tree-perl all 5.03-2 [197 kB] Get:185 http://ftpmaster.internal/ubuntu/ wily/main libio-html-perl all 1.001-1 [14.9 kB] Get:186 http://ftpmaster.internal/ubuntu/ wily/main liblwp-mediatypes-perl all 6.02-1 [21.7 kB] Get:187 http://ftpmaster.internal/ubuntu/ wily/main libhttp-message-perl all 6.06-1 [78.7 kB] Get:188 http://ftpmaster.internal/ubuntu/ wily/main libhttp-cookies-perl all 6.01-1 [17.2 kB] Get:189 http://ftpmaster.internal/ubuntu/ wily/main libhttp-negotiate-perl all 6.00-2 [13.4 kB] Get:190 http://ftpmaster.internal/ubuntu/ wily/main libnet-ssleay-perl ppc64el 1.70-1 [248 kB] Get:191 http://ftpmaster.internal/ubuntu/ wily/main libio-socket-ssl-perl all 1.965-1ubuntu1 [73.7 kB] Get:192 http://ftpmaster.internal/ubuntu/ wily/main libnet-http-perl all 6.09-1 [24.0 kB] Get:193 http://ftpmaster.internal/ubuntu/ wily/main liblwp-protocol-https-perl all 6.06-2 [8682 B] Get:194 http://ftpmaster.internal/ubuntu/ wily/main libwww-robotrules-perl all 6.01-1 [14.1 kB] Get:195 http://ftpmaster.internal/ubuntu/ wily/main libwww-perl all 6.13-1 [146 kB] Get:196 http://ftpmaster.internal/ubuntu/ wily/main libxml-parser-perl ppc64el 2.41-3 [201 kB] Get:197 http://ftpmaster.internal/ubuntu/ wily/main intltool all 0.51.0-1 [44.7 kB] Get:198 http://ftpmaster.internal/ubuntu/ wily/main pkg-config ppc64el 0.28-1ubuntu1 [39.4 kB] Get:199 http://ftpmaster.internal/ubuntu/ wily/main libdbus-1-dev ppc64el 1.9.20-1ubuntu2 [176 kB] Get:200 http://ftpmaster.internal/ubuntu/ wily/main libglib2.0-bin ppc64el 2.45.6-1 [38.7 kB] Get:201 http://ftpmaster.internal/ubuntu/ wily/main libpcre16-3 ppc64el 2:8.35-7ubuntu5 [139 kB] Get:202 http://ftpmaster.internal/ubuntu/ wily/main libpcre32-3 ppc64el 2:8.35-7ubuntu5 [130 kB] Get:203 http://ftpmaster.internal/ubuntu/ wily/main libpcre3-dev ppc64el 2:8.35-7ubuntu5 [500 kB] Get:204 http://ftpmaster.internal/ubuntu/ wily/main zlib1g-dev ppc64el 1:1.2.8.dfsg-2ubuntu1 [169 kB] Get:205 http://ftpmaster.internal/ubuntu/ wily/main libglib2.0-dev ppc64el 2.45.6-1 [1523 kB] Get:206 http://ftpmaster.internal/ubuntu/ wily/main libdbus-glib-1-dev ppc64el 0.104-1build1 [98.1 kB] Get:207 http://ftpmaster.internal/ubuntu/ wily/main xorg-sgml-doctools all 1:1.11-1 [12.9 kB] Get:208 http://ftpmaster.internal/ubuntu/ wily/main x11proto-core-dev all 7.0.28-0ubuntu1 [699 kB] Get:209 http://ftpmaster.internal/ubuntu/ wily/main libxau-dev ppc64el 1:1.0.8-1 [9358 B] Get:210 http://ftpmaster.internal/ubuntu/ wily/main libxdmcp-dev ppc64el 1:1.1.2-1 [26.3 kB] Get:211 http://ftpmaster.internal/ubuntu/ wily/main x11proto-input-dev all 2.3.1-1 [118 kB] Get:212 http://ftpmaster.internal/ubuntu/ wily/main x11proto-kb-dev all 1.0.7-0ubuntu1 [224 kB] Get:213 http://ftpmaster.internal/ubuntu/ wily/main xtrans-dev all 1.3.5-1 [70.5 kB] Get:214 http://ftpmaster.internal/ubuntu/ wily/main libpthread-stubs0-dev ppc64el 0.3-4 [3894 B] Get:215 http://ftpmaster.internal/ubuntu/ wily/main libxcb1-dev ppc64el 1.11-0ubuntu1 [73.7 kB] Get:216 http://ftpmaster.internal/ubuntu/ wily/main libx11-dev ppc64el 2:1.6.3-1ubuntu1 [656 kB] Get:217 http://ftpmaster.internal/ubuntu/ wily/main libpng12-dev ppc64el 1.2.51-0ubuntu3 [237 kB] Get:218 http://ftpmaster.internal/ubuntu/ wily/main libgdk-pixbuf2.0-dev ppc64el 2.31.5-1 [44.9 kB] Get:219 http://ftpmaster.internal/ubuntu/ wily/main libcairo-script-interpreter2 ppc64el 1.14.2-2ubuntu2 [55.8 kB] Get:220 http://ftpmaster.internal/ubuntu/ wily/main libexpat1-dev ppc64el 2.1.0-7 [123 kB] Get:221 http://ftpmaster.internal/ubuntu/ wily/main libfreetype6-dev ppc64el 2.5.2-4ubuntu1 [664 kB] Get:222 http://ftpmaster.internal/ubuntu/ wily/main libfontconfig1-dev ppc64el 2.11.1-0ubuntu6 [660 kB] Get:223 http://ftpmaster.internal/ubuntu/ wily/main x11proto-render-dev all 2:0.11.1-2 [20.1 kB] Get:224 http://ftpmaster.internal/ubuntu/ wily/main libxrender-dev ppc64el 1:0.9.9-0ubuntu1 [24.5 kB] Get:225 http://ftpmaster.internal/ubuntu/ wily/main x11proto-xext-dev all 7.3.0-1 [212 kB] Get:226 http://ftpmaster.internal/ubuntu/ wily/main libxext-dev ppc64el 2:1.3.3-1 [86.5 kB] Get:227 http://ftpmaster.internal/ubuntu/ wily/main libice-dev ppc64el 2:1.0.9-1 [48.7 kB] Get:228 http://ftpmaster.internal/ubuntu/ wily/main libsm-dev ppc64el 2:1.2.2-1 [16.6 kB] Get:229 http://ftpmaster.internal/ubuntu/ wily/main libpixman-1-dev ppc64el 0.32.6-3 [219 kB] Get:230 http://ftpmaster.internal/ubuntu/ wily/main libxcb-render0-dev ppc64el 1.11-0ubuntu1 [15.0 kB] Get:231 http://ftpmaster.internal/ubuntu/ wily/main libxcb-shm0-dev ppc64el 1.11-0ubuntu1 [6742 B] Get:232 http://ftpmaster.internal/ubuntu/ wily/main libcairo2-dev ppc64el 1.14.2-2ubuntu2 [667 kB] Get:233 http://ftpmaster.internal/ubuntu/ wily/main libharfbuzz-icu0 ppc64el 1.0.1-1build1 [5376 B] Get:234 http://ftpmaster.internal/ubuntu/ wily/main libharfbuzz-gobject0 ppc64el 1.0.1-1build1 [10.8 kB] Get:235 http://ftpmaster.internal/ubuntu/ wily/main libharfbuzz-dev ppc64el 1.0.1-1build1 [192 kB] Get:236 http://ftpmaster.internal/ubuntu/ wily/main libxft-dev ppc64el 2.3.2-1 [51.4 kB] Get:237 http://ftpmaster.internal/ubuntu/ wily/main libpango1.0-dev ppc64el 1.36.8-3 [319 kB] Get:238 http://ftpmaster.internal/ubuntu/ wily/main libatk1.0-dev ppc64el 2.16.0-2 [79.0 kB] Get:239 http://ftpmaster.internal/ubuntu/ wily/main x11proto-xinerama-dev all 1.2.1-2 [4966 B] Get:240 http://ftpmaster.internal/ubuntu/ wily/main libxinerama-dev ppc64el 2:1.1.3-1 [8024 B] Get:241 http://ftpmaster.internal/ubuntu/ wily/main x11proto-fixes-dev all 1:5.0-2ubuntu2 [14.2 kB] Get:242 http://ftpmaster.internal/ubuntu/ wily/main libxfixes-dev ppc64el 1:5.0.1-2 [11.4 kB] Get:243 http://ftpmaster.internal/ubuntu/ wily/main libxi-dev ppc64el 2:1.7.4-1 [186 kB] Get:244 http://ftpmaster.internal/ubuntu/ wily/main x11proto-randr-dev all 1.5.0-1 [33.7 kB] Get:245 http://ftpmaster.internal/ubuntu/ wily/main libxrandr-dev ppc64el 2:1.5.0-1 [23.9 kB] Get:246 http://ftpmaster.internal/ubuntu/ wily/main libxcursor-dev ppc64el 1:1.1.14-1 [29.5 kB] Get:247 http://ftpmaster.internal/ubuntu/ wily/main x11proto-composite-dev all 1:0.4.2-2 [10.5 kB] Get:248 http://ftpmaster.internal/ubuntu/ wily/main libxcomposite-dev ppc64el 1:0.4.4-1 [9360 B] Get:249 http://ftpmaster.internal/ubuntu/ wily/main x11proto-damage-dev all 1:1.2.1-2 [8286 B] Get:250 http://ftpmaster.internal/ubuntu/ wily/main libxdamage-dev ppc64el 1:1.1.4-2 [5116 B] Get:251 http://ftpmaster.internal/ubuntu/ wily/main libxml2-utils ppc64el 2.9.2+dfsg1-3ubuntu1 [34.4 kB] Get:252 http://ftpmaster.internal/ubuntu/ wily/main libgtk2.0-dev ppc64el 2.24.28-0ubuntu1 [2576 kB] Get:253 http://ftpmaster.internal/ubuntu/ wily/main libdbusmenu-glib-dev ppc64el 12.10.3+15.04.20150410.2-0ubuntu1 [74.9 kB] Get:254 http://ftpmaster.internal/ubuntu/ wily/main libappindicator-dev ppc64el 12.10.1+15.04.20141110-0ubuntu1 [10.8 kB] Get:255 http://ftpmaster.internal/ubuntu/ wily/main libgconf2-dev ppc64el 3.2.6-3ubuntu3 [104 kB] Get:256 http://ftpmaster.internal/ubuntu/ wily/main libgstreamer1.0-dev ppc64el 1.5.2-1 [356 kB] Get:257 http://ftpmaster.internal/ubuntu/ wily/main libicu-dev ppc64el 55.1-4 [8931 kB] Get:258 http://ftpmaster.internal/ubuntu/ wily/main libnotify-dev ppc64el 0.7.6-2svn1 [18.6 kB] Get:259 http://ftpmaster.internal/ubuntu/ wily/main libunique-1.0-0 ppc64el 1.1.6-5 [19.9 kB] Get:260 http://ftpmaster.internal/ubuntu/ wily/main libunique-dev ppc64el 1.1.6-5 [24.6 kB] Get:261 http://ftpmaster.internal/ubuntu/ wily/main libxml2-dev ppc64el 2.9.2+dfsg1-3ubuntu1 [684 kB] debconf: delaying package configuration, since apt-utils is not installed Fetched 67.5 MB in 46s (1458 kB/s) Selecting previously unselected package libmpdec2:ppc64el. (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 11626 files and directories currently installed.) Preparing to unpack .../libmpdec2_2.4.1-1_ppc64el.deb ... Unpacking libmpdec2:ppc64el (2.4.1-1) ... Selecting previously unselected package libpython3.4-minimal:ppc64el. Preparing to unpack .../libpython3.4-minimal_3.4.3-8_ppc64el.deb ... Unpacking libpython3.4-minimal:ppc64el (3.4.3-8) ... Selecting previously unselected package mime-support. Preparing to unpack .../mime-support_3.58ubuntu1_all.deb ... Unpacking mime-support (3.58ubuntu1) ... Selecting previously unselected package libpython3.4-stdlib:ppc64el. Preparing to unpack .../libpython3.4-stdlib_3.4.3-8_ppc64el.deb ... Unpacking libpython3.4-stdlib:ppc64el (3.4.3-8) ... Selecting previously unselected package libexpat1:ppc64el. Preparing to unpack .../libexpat1_2.1.0-7_ppc64el.deb ... Unpacking libexpat1:ppc64el (2.1.0-7) ... Selecting previously unselected package python3.4-minimal. Preparing to unpack .../python3.4-minimal_3.4.3-8_ppc64el.deb ... Unpacking python3.4-minimal (3.4.3-8) ... Selecting previously unselected package python3-minimal. Preparing to unpack .../python3-minimal_3.4.3-4ubuntu1_ppc64el.deb ... Unpacking python3-minimal (3.4.3-4ubuntu1) ... Selecting previously unselected package python3.4. Preparing to unpack .../python3.4_3.4.3-8_ppc64el.deb ... Unpacking python3.4 (3.4.3-8) ... Selecting previously unselected package libpython3-stdlib:ppc64el. Preparing to unpack .../libpython3-stdlib_3.4.3-4ubuntu1_ppc64el.deb ... Unpacking libpython3-stdlib:ppc64el (3.4.3-4ubuntu1) ... Selecting previously unselected package dh-python. Preparing to unpack .../dh-python_2.20150826_all.deb ... Unpacking dh-python (2.20150826) ... Setting up libpython3.4-minimal:ppc64el (3.4.3-8) ... Setting up libexpat1:ppc64el (2.1.0-7) ... Setting up python3.4-minimal (3.4.3-8) ... Setting up python3-minimal (3.4.3-4ubuntu1) ... Processing triggers for libc-bin (2.21-0ubuntu4) ... Selecting previously unselected package python3. (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 12565 files and directories currently installed.) Preparing to unpack .../python3_3.4.3-4ubuntu1_ppc64el.deb ... Unpacking python3 (3.4.3-4ubuntu1) ... Selecting previously unselected package libasprintf0v5:ppc64el. Preparing to unpack .../libasprintf0v5_0.19.4-1ubuntu3_ppc64el.deb ... Unpacking libasprintf0v5:ppc64el (0.19.4-1ubuntu3) ... Selecting previously unselected package libcap-ng0:ppc64el. Preparing to unpack .../libcap-ng0_0.7.6-1_ppc64el.deb ... Unpacking libcap-ng0:ppc64el (0.7.6-1) ... Selecting previously unselected package libxau6:ppc64el. Preparing to unpack .../libxau6_1%3a1.0.8-1_ppc64el.deb ... Unpacking libxau6:ppc64el (1:1.0.8-1) ... Selecting previously unselected package libxdmcp6:ppc64el. Preparing to unpack .../libxdmcp6_1%3a1.1.2-1_ppc64el.deb ... Unpacking libxdmcp6:ppc64el (1:1.1.2-1) ... Selecting previously unselected package libxcb1:ppc64el. Preparing to unpack .../libxcb1_1.11-0ubuntu1_ppc64el.deb ... Unpacking libxcb1:ppc64el (1.11-0ubuntu1) ... Selecting previously unselected package libx11-data. Preparing to unpack .../libx11-data_2%3a1.6.3-1ubuntu1_all.deb ... Unpacking libx11-data (2:1.6.3-1ubuntu1) ... Selecting previously unselected package libx11-6:ppc64el. Preparing to unpack .../libx11-6_2%3a1.6.3-1ubuntu1_ppc64el.deb ... Unpacking libx11-6:ppc64el (2:1.6.3-1ubuntu1) ... Selecting previously unselected package libxext6:ppc64el. Preparing to unpack .../libxext6_2%3a1.3.3-1_ppc64el.deb ... Unpacking libxext6:ppc64el (2:1.3.3-1) ... Selecting previously unselected package groff-base. Preparing to unpack .../groff-base_1.22.3-1_ppc64el.deb ... Unpacking groff-base (1.22.3-1) ... Selecting previously unselected package bsdmainutils. Preparing to unpack .../bsdmainutils_9.0.6ubuntu1_ppc64el.deb ... Unpacking bsdmainutils (9.0.6ubuntu1) ... Selecting previously unselected package libpipeline1:ppc64el. Preparing to unpack .../libpipeline1_1.4.1-1_ppc64el.deb ... Unpacking libpipeline1:ppc64el (1.4.1-1) ... Selecting previously unselected package man-db. Preparing to unpack .../man-db_2.7.2-1_ppc64el.deb ... Unpacking man-db (2.7.2-1) ... Selecting previously unselected package fonts-dejavu-core. Preparing to unpack .../fonts-dejavu-core_2.35-1_all.deb ... Unpacking fonts-dejavu-core (2.35-1) ... Selecting previously unselected package ucf. Preparing to unpack .../archives/ucf_3.0030_all.deb ... Moving old data out of the way Unpacking ucf (3.0030) ... Selecting previously unselected package fontconfig-config. Preparing to unpack .../fontconfig-config_2.11.1-0ubuntu6_all.deb ... Unpacking fontconfig-config (2.11.1-0ubuntu6) ... Selecting previously unselected package libfreetype6:ppc64el. Preparing to unpack .../libfreetype6_2.5.2-4ubuntu1_ppc64el.deb ... Unpacking libfreetype6:ppc64el (2.5.2-4ubuntu1) ... Selecting previously unselected package libfontconfig1:ppc64el. Preparing to unpack .../libfontconfig1_2.11.1-0ubuntu6_ppc64el.deb ... Unpacking libfontconfig1:ppc64el (2.11.1-0ubuntu6) ... Selecting previously unselected package fontconfig. Preparing to unpack .../fontconfig_2.11.1-0ubuntu6_ppc64el.deb ... Unpacking fontconfig (2.11.1-0ubuntu6) ... Selecting previously unselected package libdbusmenu-glib4:ppc64el. Preparing to unpack .../libdbusmenu-glib4_12.10.3+15.04.20150410.2-0ubuntu1_ppc64el.deb ... Unpacking libdbusmenu-glib4:ppc64el (12.10.3+15.04.20150410.2-0ubuntu1) ... Selecting previously unselected package libglib2.0-0:ppc64el. Preparing to unpack .../libglib2.0-0_2.45.6-1_ppc64el.deb ... Unpacking libglib2.0-0:ppc64el (2.45.6-1) ... Selecting previously unselected package libatk1.0-data. Preparing to unpack .../libatk1.0-data_2.16.0-2_all.deb ... Unpacking libatk1.0-data (2.16.0-2) ... Selecting previously unselected package libatk1.0-0:ppc64el. Preparing to unpack .../libatk1.0-0_2.16.0-2_ppc64el.deb ... Unpacking libatk1.0-0:ppc64el (2.16.0-2) ... Selecting previously unselected package libjpeg-turbo8:ppc64el. Preparing to unpack .../libjpeg-turbo8_1.3.0-0ubuntu2_ppc64el.deb ... Unpacking libjpeg-turbo8:ppc64el (1.3.0-0ubuntu2) ... Selecting previously unselected package libjpeg8:ppc64el. Preparing to unpack .../libjpeg8_8c-2ubuntu8_ppc64el.deb ... Unpacking libjpeg8:ppc64el (8c-2ubuntu8) ... Selecting previously unselected package libjasper1:ppc64el. Preparing to unpack .../libjasper1_1.900.1-debian1-2.4_ppc64el.deb ... Unpacking libjasper1:ppc64el (1.900.1-debian1-2.4) ... Selecting previously unselected package libjbig0:ppc64el. Preparing to unpack .../libjbig0_2.1-3.1_ppc64el.deb ... Unpacking libjbig0:ppc64el (2.1-3.1) ... Selecting previously unselected package libtiff5:ppc64el. Preparing to unpack .../libtiff5_4.0.3-12.3ubuntu2_ppc64el.deb ... Unpacking libtiff5:ppc64el (4.0.3-12.3ubuntu2) ... Selecting previously unselected package libgdk-pixbuf2.0-common. Preparing to unpack .../libgdk-pixbuf2.0-common_2.31.5-1_all.deb ... Unpacking libgdk-pixbuf2.0-common (2.31.5-1) ... Selecting previously unselected package libgdk-pixbuf2.0-0:ppc64el. Preparing to unpack .../libgdk-pixbuf2.0-0_2.31.5-1_ppc64el.deb ... Unpacking libgdk-pixbuf2.0-0:ppc64el (2.31.5-1) ... Selecting previously unselected package libthai-data. Preparing to unpack .../libthai-data_0.1.22-2_all.deb ... Unpacking libthai-data (0.1.22-2) ... Selecting previously unselected package libdatrie1:ppc64el. Preparing to unpack .../libdatrie1_0.2.9-2_ppc64el.deb ... Unpacking libdatrie1:ppc64el (0.2.9-2) ... Selecting previously unselected package libthai0:ppc64el. Preparing to unpack .../libthai0_0.1.22-2_ppc64el.deb ... Unpacking libthai0:ppc64el (0.1.22-2) ... Selecting previously unselected package libpango-1.0-0:ppc64el. Preparing to unpack .../libpango-1.0-0_1.36.8-3_ppc64el.deb ... Unpacking libpango-1.0-0:ppc64el (1.36.8-3) ... Selecting previously unselected package libdbusmenu-gtk4:ppc64el. Preparing to unpack .../libdbusmenu-gtk4_12.10.3+15.04.20150410.2-0ubuntu1_ppc64el.deb ... Unpacking libdbusmenu-gtk4:ppc64el (12.10.3+15.04.20150410.2-0ubuntu1) ... Selecting previously unselected package libgtk2.0-common. Preparing to unpack .../libgtk2.0-common_2.24.28-0ubuntu1_all.deb ... Unpacking libgtk2.0-common (2.24.28-0ubuntu1) ... Selecting previously unselected package libpixman-1-0:ppc64el. Preparing to unpack .../libpixman-1-0_0.32.6-3_ppc64el.deb ... Unpacking libpixman-1-0:ppc64el (0.32.6-3) ... Selecting previously unselected package libxcb-render0:ppc64el. Preparing to unpack .../libxcb-render0_1.11-0ubuntu1_ppc64el.deb ... Unpacking libxcb-render0:ppc64el (1.11-0ubuntu1) ... Selecting previously unselected package libxcb-shm0:ppc64el. Preparing to unpack .../libxcb-shm0_1.11-0ubuntu1_ppc64el.deb ... Unpacking libxcb-shm0:ppc64el (1.11-0ubuntu1) ... Selecting previously unselected package libxrender1:ppc64el. Preparing to unpack .../libxrender1_1%3a0.9.9-0ubuntu1_ppc64el.deb ... Unpacking libxrender1:ppc64el (1:0.9.9-0ubuntu1) ... Selecting previously unselected package libcairo2:ppc64el. Preparing to unpack .../libcairo2_1.14.2-2ubuntu2_ppc64el.deb ... Unpacking libcairo2:ppc64el (1.14.2-2ubuntu2) ... Selecting previously unselected package libavahi-common-data:ppc64el. Preparing to unpack .../libavahi-common-data_0.6.31-4ubuntu4_ppc64el.deb ... Unpacking libavahi-common-data:ppc64el (0.6.31-4ubuntu4) ... Selecting previously unselected package libavahi-common3:ppc64el. Preparing to unpack .../libavahi-common3_0.6.31-4ubuntu4_ppc64el.deb ... Unpacking libavahi-common3:ppc64el (0.6.31-4ubuntu4) ... Selecting previously unselected package libavahi-client3:ppc64el. Preparing to unpack .../libavahi-client3_0.6.31-4ubuntu4_ppc64el.deb ... Unpacking libavahi-client3:ppc64el (0.6.31-4ubuntu4) ... Selecting previously unselected package libcups2:ppc64el. Preparing to unpack .../libcups2_2.1~rc1-3_ppc64el.deb ... Unpacking libcups2:ppc64el (2.1~rc1-3) ... Selecting previously unselected package libgraphite2-3:ppc64el. Preparing to unpack .../libgraphite2-3_1.2.4-3ubuntu1_ppc64el.deb ... Unpacking libgraphite2-3:ppc64el (1.2.4-3ubuntu1) ... Selecting previously unselected package libharfbuzz0b:ppc64el. Preparing to unpack .../libharfbuzz0b_1.0.1-1build1_ppc64el.deb ... Unpacking libharfbuzz0b:ppc64el (1.0.1-1build1) ... Selecting previously unselected package libpangoft2-1.0-0:ppc64el. Preparing to unpack .../libpangoft2-1.0-0_1.36.8-3_ppc64el.deb ... Unpacking libpangoft2-1.0-0:ppc64el (1.36.8-3) ... Selecting previously unselected package libpangocairo-1.0-0:ppc64el. Preparing to unpack .../libpangocairo-1.0-0_1.36.8-3_ppc64el.deb ... Unpacking libpangocairo-1.0-0:ppc64el (1.36.8-3) ... Selecting previously unselected package libxcomposite1:ppc64el. Preparing to unpack .../libxcomposite1_1%3a0.4.4-1_ppc64el.deb ... Unpacking libxcomposite1:ppc64el (1:0.4.4-1) ... Selecting previously unselected package libxfixes3:ppc64el. Preparing to unpack .../libxfixes3_1%3a5.0.1-2_ppc64el.deb ... Unpacking libxfixes3:ppc64el (1:5.0.1-2) ... Selecting previously unselected package libxcursor1:ppc64el. Preparing to unpack .../libxcursor1_1%3a1.1.14-1_ppc64el.deb ... Unpacking libxcursor1:ppc64el (1:1.1.14-1) ... Selecting previously unselected package libxdamage1:ppc64el. Preparing to unpack .../libxdamage1_1%3a1.1.4-2_ppc64el.deb ... Unpacking libxdamage1:ppc64el (1:1.1.4-2) ... Selecting previously unselected package libxi6:ppc64el. Preparing to unpack .../libxi6_2%3a1.7.4-1_ppc64el.deb ... Unpacking libxi6:ppc64el (2:1.7.4-1) ... Selecting previously unselected package libxinerama1:ppc64el. Preparing to unpack .../libxinerama1_2%3a1.1.3-1_ppc64el.deb ... Unpacking libxinerama1:ppc64el (2:1.1.3-1) ... Selecting previously unselected package libxrandr2:ppc64el. Preparing to unpack .../libxrandr2_2%3a1.5.0-1_ppc64el.deb ... Unpacking libxrandr2:ppc64el (2:1.5.0-1) ... Selecting previously unselected package libicu55:ppc64el. Preparing to unpack .../libicu55_55.1-4_ppc64el.deb ... Unpacking libicu55:ppc64el (55.1-4) ... Selecting previously unselected package libxml2:ppc64el. Preparing to unpack .../libxml2_2.9.2+dfsg1-3ubuntu1_ppc64el.deb ... Unpacking libxml2:ppc64el (2.9.2+dfsg1-3ubuntu1) ... Selecting previously unselected package shared-mime-info. Preparing to unpack .../shared-mime-info_1.3-1_ppc64el.deb ... Unpacking shared-mime-info (1.3-1) ... Selecting previously unselected package libgtk2.0-0:ppc64el. Preparing to unpack .../libgtk2.0-0_2.24.28-0ubuntu1_ppc64el.deb ... Unpacking libgtk2.0-0:ppc64el (2.24.28-0ubuntu1) ... Selecting previously unselected package libindicator7. Preparing to unpack .../libindicator7_12.10.2+14.10.20140922-0ubuntu1_ppc64el.deb ... Unpacking libindicator7 (12.10.2+14.10.20140922-0ubuntu1) ... Selecting previously unselected package libappindicator1. Preparing to unpack .../libappindicator1_12.10.1+15.04.20141110-0ubuntu1_ppc64el.deb ... Unpacking libappindicator1 (12.10.1+15.04.20141110-0ubuntu1) ... Selecting previously unselected package libcroco3:ppc64el. Preparing to unpack .../libcroco3_0.6.8-3_ppc64el.deb ... Unpacking libcroco3:ppc64el (0.6.8-3) ... Selecting previously unselected package x11-common. Preparing to unpack .../x11-common_1%3a7.7+7ubuntu4_all.deb ... Unpacking x11-common (1:7.7+7ubuntu4) ... Selecting previously unselected package libice6:ppc64el. Preparing to unpack .../libice6_2%3a1.0.9-1_ppc64el.deb ... Unpacking libice6:ppc64el (2:1.0.9-1) ... Selecting previously unselected package liblcms2-2:ppc64el. Preparing to unpack .../liblcms2-2_2.6-3ubuntu2_ppc64el.deb ... Unpacking liblcms2-2:ppc64el (2.6-3ubuntu2) ... Selecting previously unselected package liblzo2-2:ppc64el. Preparing to unpack .../liblzo2-2_2.08-1.2_ppc64el.deb ... Unpacking liblzo2-2:ppc64el (2.08-1.2) ... Selecting previously unselected package libnotify4:ppc64el. Preparing to unpack .../libnotify4_0.7.6-2svn1_ppc64el.deb ... Unpacking libnotify4:ppc64el (0.7.6-2svn1) ... Selecting previously unselected package libxft2:ppc64el. Preparing to unpack .../libxft2_2.3.2-1_ppc64el.deb ... Unpacking libxft2:ppc64el (2.3.2-1) ... Selecting previously unselected package libpangoxft-1.0-0:ppc64el. Preparing to unpack .../libpangoxft-1.0-0_1.36.8-3_ppc64el.deb ... Unpacking libpangoxft-1.0-0:ppc64el (1.36.8-3) ... Selecting previously unselected package libpcrecpp0v5:ppc64el. Preparing to unpack .../libpcrecpp0v5_2%3a8.35-7ubuntu5_ppc64el.deb ... Unpacking libpcrecpp0v5:ppc64el (2:8.35-7ubuntu5) ... Selecting previously unselected package libproxy1v5:ppc64el. Preparing to unpack .../libproxy1v5_0.4.11-4ubuntu3~gcc5.3_ppc64el.deb ... Unpacking libproxy1v5:ppc64el (0.4.11-4ubuntu3~gcc5.3) ... Selecting previously unselected package glib-networking-common. Preparing to unpack .../glib-networking-common_2.45.1-1build1_all.deb ... Unpacking glib-networking-common (2.45.1-1build1) ... Selecting previously unselected package glib-networking-services. Preparing to unpack .../glib-networking-services_2.45.1-1build1_ppc64el.deb ... Unpacking glib-networking-services (2.45.1-1build1) ... Selecting previously unselected package libdconf1:ppc64el. Preparing to unpack .../libdconf1_0.24.0-2_ppc64el.deb ... Unpacking libdconf1:ppc64el (0.24.0-2) ... Selecting previously unselected package dconf-service. Preparing to unpack .../dconf-service_0.24.0-2_ppc64el.deb ... Unpacking dconf-service (0.24.0-2) ... Selecting previously unselected package dconf-gsettings-backend:ppc64el. Preparing to unpack .../dconf-gsettings-backend_0.24.0-2_ppc64el.deb ... Unpacking dconf-gsettings-backend:ppc64el (0.24.0-2) ... Selecting previously unselected package gsettings-desktop-schemas. Preparing to unpack .../gsettings-desktop-schemas_3.16.1-1ubuntu1_all.deb ... Unpacking gsettings-desktop-schemas (3.16.1-1ubuntu1) ... Selecting previously unselected package glib-networking:ppc64el. Preparing to unpack .../glib-networking_2.45.1-1build1_ppc64el.deb ... Unpacking glib-networking:ppc64el (2.45.1-1build1) ... Selecting previously unselected package libsoup2.4-1:ppc64el. Preparing to unpack .../libsoup2.4-1_2.50.0-2_ppc64el.deb ... Unpacking libsoup2.4-1:ppc64el (2.50.0-2) ... Selecting previously unselected package libsoup-gnome2.4-1:ppc64el. Preparing to unpack .../libsoup-gnome2.4-1_2.50.0-2_ppc64el.deb ... Unpacking libsoup-gnome2.4-1:ppc64el (2.50.0-2) ... Selecting previously unselected package librest-0.7-0:ppc64el. Preparing to unpack .../librest-0.7-0_0.7.93-1_ppc64el.deb ... Unpacking librest-0.7-0:ppc64el (0.7.93-1) ... Selecting previously unselected package libsigsegv2:ppc64el. Preparing to unpack .../libsigsegv2_2.10-4_ppc64el.deb ... Unpacking libsigsegv2:ppc64el (2.10-4) ... Selecting previously unselected package libsm6:ppc64el. Preparing to unpack .../libsm6_2%3a1.2.2-1_ppc64el.deb ... Unpacking libsm6:ppc64el (2:1.2.2-1) ... Selecting previously unselected package libunistring0:ppc64el. Preparing to unpack .../libunistring0_0.9.3-5.2ubuntu1_ppc64el.deb ... Unpacking libunistring0:ppc64el (0.9.3-5.2ubuntu1) ... Selecting previously unselected package libpython2.7-minimal:ppc64el. Preparing to unpack .../libpython2.7-minimal_2.7.10-3_ppc64el.deb ... Unpacking libpython2.7-minimal:ppc64el (2.7.10-3) ... Selecting previously unselected package python2.7-minimal. Preparing to unpack .../python2.7-minimal_2.7.10-3_ppc64el.deb ... Unpacking python2.7-minimal (2.7.10-3) ... Selecting previously unselected package python-minimal. Preparing to unpack .../python-minimal_2.7.9-1_ppc64el.deb ... Unpacking python-minimal (2.7.9-1) ... Selecting previously unselected package libpython2.7-stdlib:ppc64el. Preparing to unpack .../libpython2.7-stdlib_2.7.10-3_ppc64el.deb ... Unpacking libpython2.7-stdlib:ppc64el (2.7.10-3) ... Selecting previously unselected package python2.7. Preparing to unpack .../python2.7_2.7.10-3_ppc64el.deb ... Unpacking python2.7 (2.7.10-3) ... Selecting previously unselected package libpython-stdlib:ppc64el. Preparing to unpack .../libpython-stdlib_2.7.9-1_ppc64el.deb ... Unpacking libpython-stdlib:ppc64el (2.7.9-1) ... Processing triggers for systemd (224-2ubuntu2) ... Setting up libpython2.7-minimal:ppc64el (2.7.10-3) ... Setting up python2.7-minimal (2.7.10-3) ... Setting up python-minimal (2.7.9-1) ... Selecting previously unselected package python. (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 14883 files and directories currently installed.) Preparing to unpack .../python_2.7.9-1_ppc64el.deb ... Unpacking python (2.7.9-1) ... Selecting previously unselected package libmagic1:ppc64el. Preparing to unpack .../libmagic1_1%3a5.22+15-2ubuntu1_ppc64el.deb ... Unpacking libmagic1:ppc64el (1:5.22+15-2ubuntu1) ... Selecting previously unselected package file. Preparing to unpack .../file_1%3a5.22+15-2ubuntu1_ppc64el.deb ... Unpacking file (1:5.22+15-2ubuntu1) ... Selecting previously unselected package netbase. Preparing to unpack .../archives/netbase_5.3_all.deb ... Unpacking netbase (5.3) ... Selecting previously unselected package xkb-data. Preparing to unpack .../xkb-data_2.12-1ubuntu1_all.deb ... Unpacking xkb-data (2.12-1ubuntu1) ... Selecting previously unselected package dbus. Preparing to unpack .../dbus_1.9.20-1ubuntu2_ppc64el.deb ... Unpacking dbus (1.9.20-1ubuntu2) ... Selecting previously unselected package gettext-base. Preparing to unpack .../gettext-base_0.19.4-1ubuntu3_ppc64el.deb ... Unpacking gettext-base (0.19.4-1ubuntu3) ... Selecting previously unselected package libgirepository-1.0-1:ppc64el. Preparing to unpack .../libgirepository-1.0-1_1.44.0-1_ppc64el.deb ... Unpacking libgirepository-1.0-1:ppc64el (1.44.0-1) ... Selecting previously unselected package gir1.2-glib-2.0:ppc64el. Preparing to unpack .../gir1.2-glib-2.0_1.44.0-1_ppc64el.deb ... Unpacking gir1.2-glib-2.0:ppc64el (1.44.0-1) ... Selecting previously unselected package libdbus-glib-1-2:ppc64el. Preparing to unpack .../libdbus-glib-1-2_0.104-1build1_ppc64el.deb ... Unpacking libdbus-glib-1-2:ppc64el (0.104-1build1) ... Selecting previously unselected package libdrm2:ppc64el. Preparing to unpack .../libdrm2_2.4.64-1_ppc64el.deb ... Unpacking libdrm2:ppc64el (2.4.64-1) ... Selecting previously unselected package libelf1:ppc64el. Preparing to unpack .../libelf1_0.163-4ubuntu1_ppc64el.deb ... Unpacking libelf1:ppc64el (0.163-4ubuntu1) ... Selecting previously unselected package libglib2.0-data. Preparing to unpack .../libglib2.0-data_2.45.6-1_all.deb ... Unpacking libglib2.0-data (2.45.6-1) ... Selecting previously unselected package psmisc. Preparing to unpack .../psmisc_22.21-2build1_ppc64el.deb ... Unpacking psmisc (22.21-2build1) ... Selecting previously unselected package hicolor-icon-theme. Preparing to unpack .../hicolor-icon-theme_0.15-0ubuntu1_all.deb ... Unpacking hicolor-icon-theme (0.15-0ubuntu1) ... Selecting previously unselected package libgtk-3-common. Preparing to unpack .../libgtk-3-common_3.16.6-1ubuntu1_all.deb ... Unpacking libgtk-3-common (3.16.6-1ubuntu1) ... Selecting previously unselected package libatspi2.0-0:ppc64el. Preparing to unpack .../libatspi2.0-0_2.16.0-1ubuntu1_ppc64el.deb ... Unpacking libatspi2.0-0:ppc64el (2.16.0-1ubuntu1) ... Selecting previously unselected package libatk-bridge2.0-0:ppc64el. Preparing to unpack .../libatk-bridge2.0-0_2.16.0-1ubuntu1_ppc64el.deb ... Unpacking libatk-bridge2.0-0:ppc64el (2.16.0-1ubuntu1) ... Selecting previously unselected package libcairo-gobject2:ppc64el. Preparing to unpack .../libcairo-gobject2_1.14.2-2ubuntu2_ppc64el.deb ... Unpacking libcairo-gobject2:ppc64el (1.14.2-2ubuntu2) ... Selecting previously unselected package libcolord2:ppc64el. Preparing to unpack .../libcolord2_1.2.11-0ubuntu1_ppc64el.deb ... Unpacking libcolord2:ppc64el (1.2.11-0ubuntu1) ... Selecting previously unselected package libepoxy0. Preparing to unpack .../libepoxy0_1.2-1_ppc64el.deb ... Unpacking libepoxy0 (1.2-1) ... Selecting previously unselected package libjson-glib-1.0-common. Preparing to unpack .../libjson-glib-1.0-common_1.0.4-1_all.deb ... Unpacking libjson-glib-1.0-common (1.0.4-1) ... Selecting previously unselected package libjson-glib-1.0-0:ppc64el. Preparing to unpack .../libjson-glib-1.0-0_1.0.4-1_ppc64el.deb ... Unpacking libjson-glib-1.0-0:ppc64el (1.0.4-1) ... Selecting previously unselected package libboost-system1.58.0:ppc64el. Preparing to unpack .../libboost-system1.58.0_1.58.0+dfsg-0ubuntu5_ppc64el.deb ... Unpacking libboost-system1.58.0:ppc64el (1.58.0+dfsg-0ubuntu5) ... Selecting previously unselected package libboost-filesystem1.58.0:ppc64el. Preparing to unpack .../libboost-filesystem1.58.0_1.58.0+dfsg-0ubuntu5_ppc64el.deb ... Unpacking libboost-filesystem1.58.0:ppc64el (1.58.0+dfsg-0ubuntu5) ... Selecting previously unselected package libmircommon5:ppc64el. Preparing to unpack .../libmircommon5_0.15.1+15.10.20150825-0ubuntu1_ppc64el.deb ... Unpacking libmircommon5:ppc64el (0.15.1+15.10.20150825-0ubuntu1) ... Selecting previously unselected package libprotobuf-lite9v5:ppc64el. Preparing to unpack .../libprotobuf-lite9v5_2.6.1-1.2_ppc64el.deb ... Unpacking libprotobuf-lite9v5:ppc64el (2.6.1-1.2) ... Selecting previously unselected package libmirprotobuf1:ppc64el. Preparing to unpack .../libmirprotobuf1_0.15.1+15.10.20150825-0ubuntu1_ppc64el.deb ... Unpacking libmirprotobuf1:ppc64el (0.15.1+15.10.20150825-0ubuntu1) ... Selecting previously unselected package libxkbcommon0:ppc64el. Preparing to unpack .../libxkbcommon0_0.5.0-1ubuntu2_ppc64el.deb ... Unpacking libxkbcommon0:ppc64el (0.5.0-1ubuntu2) ... Selecting previously unselected package libmirclient9:ppc64el. Preparing to unpack .../libmirclient9_0.15.1+15.10.20150825-0ubuntu1_ppc64el.deb ... Unpacking libmirclient9:ppc64el (0.15.1+15.10.20150825-0ubuntu1) ... Selecting previously unselected package libwayland-client0:ppc64el. Preparing to unpack .../libwayland-client0_1.8.1-1_ppc64el.deb ... Unpacking libwayland-client0:ppc64el (1.8.1-1) ... Selecting previously unselected package libwayland-cursor0:ppc64el. Preparing to unpack .../libwayland-cursor0_1.8.1-1_ppc64el.deb ... Unpacking libwayland-cursor0:ppc64el (1.8.1-1) ... Selecting previously unselected package libwayland-server0:ppc64el. Preparing to unpack .../libwayland-server0_1.8.1-1_ppc64el.deb ... Unpacking libwayland-server0:ppc64el (1.8.1-1) ... Selecting previously unselected package libdrm-nouveau2:ppc64el. Preparing to unpack .../libdrm-nouveau2_2.4.64-1_ppc64el.deb ... Unpacking libdrm-nouveau2:ppc64el (2.4.64-1) ... Selecting previously unselected package libdrm-radeon1:ppc64el. Preparing to unpack .../libdrm-radeon1_2.4.64-1_ppc64el.deb ... Unpacking libdrm-radeon1:ppc64el (2.4.64-1) ... Selecting previously unselected package libgl1-mesa-dri:ppc64el. Preparing to unpack .../libgl1-mesa-dri_10.6.3-1ubuntu1_ppc64el.deb ... Unpacking libgl1-mesa-dri:ppc64el (10.6.3-1ubuntu1) ... Selecting previously unselected package libgbm1:ppc64el. Preparing to unpack .../libgbm1_10.6.3-1ubuntu1_ppc64el.deb ... Unpacking libgbm1:ppc64el (10.6.3-1ubuntu1) ... Selecting previously unselected package libx11-xcb1:ppc64el. Preparing to unpack .../libx11-xcb1_2%3a1.6.3-1ubuntu1_ppc64el.deb ... Unpacking libx11-xcb1:ppc64el (2:1.6.3-1ubuntu1) ... Selecting previously unselected package libxcb-dri2-0:ppc64el. Preparing to unpack .../libxcb-dri2-0_1.11-0ubuntu1_ppc64el.deb ... Unpacking libxcb-dri2-0:ppc64el (1.11-0ubuntu1) ... Selecting previously unselected package libxcb-xfixes0:ppc64el. Preparing to unpack .../libxcb-xfixes0_1.11-0ubuntu1_ppc64el.deb ... Unpacking libxcb-xfixes0:ppc64el (1.11-0ubuntu1) ... Selecting previously unselected package libegl1-mesa:ppc64el. Preparing to unpack .../libegl1-mesa_10.6.3-1ubuntu1_ppc64el.deb ... Unpacking libegl1-mesa:ppc64el (10.6.3-1ubuntu1) ... Selecting previously unselected package libwayland-egl1-mesa:ppc64el. Preparing to unpack .../libwayland-egl1-mesa_10.6.3-1ubuntu1_ppc64el.deb ... Unpacking libwayland-egl1-mesa:ppc64el (10.6.3-1ubuntu1) ... Selecting previously unselected package libgtk-3-0:ppc64el. Preparing to unpack .../libgtk-3-0_3.16.6-1ubuntu1_ppc64el.deb ... Unpacking libgtk-3-0:ppc64el (3.16.6-1ubuntu1) ... Selecting previously unselected package libgtk-3-bin. Preparing to unpack .../libgtk-3-bin_3.16.6-1ubuntu1_ppc64el.deb ... Adding 'diversion of /usr/sbin/update-icon-caches to /usr/sbin/update-icon-caches.gtk2 by libgtk-3-bin' Adding 'diversion of /usr/share/man/man8/update-icon-caches.8.gz to /usr/share/man/man8/update-icon-caches.gtk2.8.gz by libgtk-3-bin' Unpacking libgtk-3-bin (3.16.6-1ubuntu1) ... Selecting previously unselected package librsvg2-2:ppc64el. Preparing to unpack .../librsvg2-2_2.40.10-1_ppc64el.deb ... Unpacking librsvg2-2:ppc64el (2.40.10-1) ... Selecting previously unselected package librsvg2-common:ppc64el. Preparing to unpack .../librsvg2-common_2.40.10-1_ppc64el.deb ... Unpacking librsvg2-common:ppc64el (2.40.10-1) ... Selecting previously unselected package humanity-icon-theme. Preparing to unpack .../humanity-icon-theme_0.6.9_all.deb ... Unpacking humanity-icon-theme (0.6.9) ... Selecting previously unselected package ubuntu-mono. Preparing to unpack .../ubuntu-mono_14.04+15.10.20150813-0ubuntu1_all.deb ... Unpacking ubuntu-mono (14.04+15.10.20150813-0ubuntu1) ... Selecting previously unselected package adwaita-icon-theme. Preparing to unpack .../adwaita-icon-theme_3.16.2.1-2ubuntu1_all.deb ... Unpacking adwaita-icon-theme (3.16.2.1-2ubuntu1) ... Selecting previously unselected package m4. Preparing to unpack .../m4_1.4.17-4_ppc64el.deb ... Unpacking m4 (1.4.17-4) ... Selecting previously unselected package autoconf. Preparing to unpack .../autoconf_2.69-8_all.deb ... Unpacking autoconf (2.69-8) ... Selecting previously unselected package autotools-dev. Preparing to unpack .../autotools-dev_20140911.1_all.deb ... Unpacking autotools-dev (20140911.1) ... Selecting previously unselected package automake. Preparing to unpack .../automake_1%3a1.15-1ubuntu1_all.deb ... Unpacking automake (1:1.15-1ubuntu1) ... Selecting previously unselected package dbus-x11. Preparing to unpack .../dbus-x11_1.9.20-1ubuntu2_ppc64el.deb ... Unpacking dbus-x11 (1.9.20-1ubuntu2) ... Selecting previously unselected package gettext. Preparing to unpack .../gettext_0.19.4-1ubuntu3_ppc64el.deb ... Unpacking gettext (0.19.4-1ubuntu3) ... Selecting previously unselected package intltool-debian. Preparing to unpack .../intltool-debian_0.35.0+20060710.2_all.deb ... Unpacking intltool-debian (0.35.0+20060710.2) ... Selecting previously unselected package po-debconf. Preparing to unpack .../po-debconf_1.0.18_all.deb ... Unpacking po-debconf (1.0.18) ... Selecting previously unselected package debhelper. Preparing to unpack .../debhelper_9.20150811ubuntu1_all.deb ... Unpacking debhelper (9.20150811ubuntu1) ... Selecting previously unselected package gconf2-common. Preparing to unpack .../gconf2-common_3.2.6-3ubuntu3_all.deb ... Unpacking gconf2-common (3.2.6-3ubuntu3) ... Selecting previously unselected package libgconf-2-4:ppc64el. Preparing to unpack .../libgconf-2-4_3.2.6-3ubuntu3_ppc64el.deb ... Unpacking libgconf-2-4:ppc64el (3.2.6-3ubuntu3) ... Selecting previously unselected package gconf-service-backend. Preparing to unpack .../gconf-service-backend_3.2.6-3ubuntu3_ppc64el.deb ... Unpacking gconf-service-backend (3.2.6-3ubuntu3) ... Selecting previously unselected package gconf-service. Preparing to unpack .../gconf-service_3.2.6-3ubuntu3_ppc64el.deb ... Unpacking gconf-service (3.2.6-3ubuntu3) ... Selecting previously unselected package gconf2. Preparing to unpack .../gconf2_3.2.6-3ubuntu3_ppc64el.deb ... Unpacking gconf2 (3.2.6-3ubuntu3) ... Selecting previously unselected package gir1.2-atk-1.0. Preparing to unpack .../gir1.2-atk-1.0_2.16.0-2_ppc64el.deb ... Unpacking gir1.2-atk-1.0 (2.16.0-2) ... Selecting previously unselected package gir1.2-freedesktop:ppc64el. Preparing to unpack .../gir1.2-freedesktop_1.44.0-1_ppc64el.deb ... Unpacking gir1.2-freedesktop:ppc64el (1.44.0-1) ... Selecting previously unselected package gir1.2-gdkpixbuf-2.0:ppc64el. Preparing to unpack .../gir1.2-gdkpixbuf-2.0_2.31.5-1_ppc64el.deb ... Unpacking gir1.2-gdkpixbuf-2.0:ppc64el (2.31.5-1) ... Selecting previously unselected package gir1.2-pango-1.0:ppc64el. Preparing to unpack .../gir1.2-pango-1.0_1.36.8-3_ppc64el.deb ... Unpacking gir1.2-pango-1.0:ppc64el (1.36.8-3) ... Selecting previously unselected package gir1.2-gtk-2.0. Preparing to unpack .../gir1.2-gtk-2.0_2.24.28-0ubuntu1_ppc64el.deb ... Unpacking gir1.2-gtk-2.0 (2.24.28-0ubuntu1) ... Selecting previously unselected package gir1.2-appindicator-0.1. Preparing to unpack .../gir1.2-appindicator-0.1_12.10.1+15.04.20141110-0ubuntu1_ppc64el.deb ... Unpacking gir1.2-appindicator-0.1 (12.10.1+15.04.20141110-0ubuntu1) ... Selecting previously unselected package gir1.2-dbusmenu-glib-0.4:ppc64el. Preparing to unpack .../gir1.2-dbusmenu-glib-0.4_12.10.3+15.04.20150410.2-0ubuntu1_ppc64el.deb ... Unpacking gir1.2-dbusmenu-glib-0.4:ppc64el (12.10.3+15.04.20150410.2-0ubuntu1) ... Selecting previously unselected package gir1.2-gconf-2.0. Preparing to unpack .../gir1.2-gconf-2.0_3.2.6-3ubuntu3_ppc64el.deb ... Unpacking gir1.2-gconf-2.0 (3.2.6-3ubuntu3) ... Selecting previously unselected package libgstreamer1.0-0:ppc64el. Preparing to unpack .../libgstreamer1.0-0_1.5.2-1_ppc64el.deb ... Unpacking libgstreamer1.0-0:ppc64el (1.5.2-1) ... Selecting previously unselected package gir1.2-gstreamer-1.0. Preparing to unpack .../gir1.2-gstreamer-1.0_1.5.2-1_ppc64el.deb ... Unpacking gir1.2-gstreamer-1.0 (1.5.2-1) ... Selecting previously unselected package gir1.2-notify-0.7. Preparing to unpack .../gir1.2-notify-0.7_0.7.6-2svn1_ppc64el.deb ... Unpacking gir1.2-notify-0.7 (0.7.6-2svn1) ... Selecting previously unselected package gnome-icon-theme. Preparing to unpack .../gnome-icon-theme_3.12.0-1ubuntu1_all.deb ... Unpacking gnome-icon-theme (3.12.0-1ubuntu1) ... Selecting previously unselected package icu-devtools. Preparing to unpack .../icu-devtools_55.1-4_ppc64el.deb ... Unpacking icu-devtools (55.1-4) ... Selecting previously unselected package liburi-perl. Preparing to unpack .../liburi-perl_1.69-1_all.deb ... Unpacking liburi-perl (1.69-1) ... Selecting previously unselected package libencode-locale-perl. Preparing to unpack .../libencode-locale-perl_1.03-1_all.deb ... Unpacking libencode-locale-perl (1.03-1) ... Selecting previously unselected package libhttp-date-perl. Preparing to unpack .../libhttp-date-perl_6.02-1_all.deb ... Unpacking libhttp-date-perl (6.02-1) ... Selecting previously unselected package libfile-listing-perl. Preparing to unpack .../libfile-listing-perl_6.04-1_all.deb ... Unpacking libfile-listing-perl (6.04-1) ... Selecting previously unselected package libhtml-tagset-perl. Preparing to unpack .../libhtml-tagset-perl_3.20-2_all.deb ... Unpacking libhtml-tagset-perl (3.20-2) ... Selecting previously unselected package libhtml-parser-perl. Preparing to unpack .../libhtml-parser-perl_3.71-2_ppc64el.deb ... Unpacking libhtml-parser-perl (3.71-2) ... Selecting previously unselected package libhtml-tree-perl. Preparing to unpack .../libhtml-tree-perl_5.03-2_all.deb ... Unpacking libhtml-tree-perl (5.03-2) ... Selecting previously unselected package libio-html-perl. Preparing to unpack .../libio-html-perl_1.001-1_all.deb ... Unpacking libio-html-perl (1.001-1) ... Selecting previously unselected package liblwp-mediatypes-perl. Preparing to unpack .../liblwp-mediatypes-perl_6.02-1_all.deb ... Unpacking liblwp-mediatypes-perl (6.02-1) ... Selecting previously unselected package libhttp-message-perl. Preparing to unpack .../libhttp-message-perl_6.06-1_all.deb ... Unpacking libhttp-message-perl (6.06-1) ... Selecting previously unselected package libhttp-cookies-perl. Preparing to unpack .../libhttp-cookies-perl_6.01-1_all.deb ... Unpacking libhttp-cookies-perl (6.01-1) ... Selecting previously unselected package libhttp-negotiate-perl. Preparing to unpack .../libhttp-negotiate-perl_6.00-2_all.deb ... Unpacking libhttp-negotiate-perl (6.00-2) ... Selecting previously unselected package libnet-ssleay-perl. Preparing to unpack .../libnet-ssleay-perl_1.70-1_ppc64el.deb ... Unpacking libnet-ssleay-perl (1.70-1) ... Selecting previously unselected package libio-socket-ssl-perl. Preparing to unpack .../libio-socket-ssl-perl_1.965-1ubuntu1_all.deb ... Unpacking libio-socket-ssl-perl (1.965-1ubuntu1) ... Selecting previously unselected package libnet-http-perl. Preparing to unpack .../libnet-http-perl_6.09-1_all.deb ... Unpacking libnet-http-perl (6.09-1) ... Selecting previously unselected package liblwp-protocol-https-perl. Preparing to unpack .../liblwp-protocol-https-perl_6.06-2_all.deb ... Unpacking liblwp-protocol-https-perl (6.06-2) ... Selecting previously unselected package libwww-robotrules-perl. Preparing to unpack .../libwww-robotrules-perl_6.01-1_all.deb ... Unpacking libwww-robotrules-perl (6.01-1) ... Selecting previously unselected package libwww-perl. Preparing to unpack .../libwww-perl_6.13-1_all.deb ... Unpacking libwww-perl (6.13-1) ... Selecting previously unselected package libxml-parser-perl. Preparing to unpack .../libxml-parser-perl_2.41-3_ppc64el.deb ... Unpacking libxml-parser-perl (2.41-3) ... Selecting previously unselected package intltool. Preparing to unpack .../intltool_0.51.0-1_all.deb ... Unpacking intltool (0.51.0-1) ... Selecting previously unselected package pkg-config. Preparing to unpack .../pkg-config_0.28-1ubuntu1_ppc64el.deb ... Unpacking pkg-config (0.28-1ubuntu1) ... Selecting previously unselected package libdbus-1-dev:ppc64el. Preparing to unpack .../libdbus-1-dev_1.9.20-1ubuntu2_ppc64el.deb ... Unpacking libdbus-1-dev:ppc64el (1.9.20-1ubuntu2) ... Selecting previously unselected package libglib2.0-bin. Preparing to unpack .../libglib2.0-bin_2.45.6-1_ppc64el.deb ... Unpacking libglib2.0-bin (2.45.6-1) ... Selecting previously unselected package libpcre16-3:ppc64el. Preparing to unpack .../libpcre16-3_2%3a8.35-7ubuntu5_ppc64el.deb ... Unpacking libpcre16-3:ppc64el (2:8.35-7ubuntu5) ... Selecting previously unselected package libpcre32-3:ppc64el. Preparing to unpack .../libpcre32-3_2%3a8.35-7ubuntu5_ppc64el.deb ... Unpacking libpcre32-3:ppc64el (2:8.35-7ubuntu5) ... Selecting previously unselected package libpcre3-dev:ppc64el. Preparing to unpack .../libpcre3-dev_2%3a8.35-7ubuntu5_ppc64el.deb ... Unpacking libpcre3-dev:ppc64el (2:8.35-7ubuntu5) ... Selecting previously unselected package zlib1g-dev:ppc64el. Preparing to unpack .../zlib1g-dev_1%3a1.2.8.dfsg-2ubuntu1_ppc64el.deb ... Unpacking zlib1g-dev:ppc64el (1:1.2.8.dfsg-2ubuntu1) ... Selecting previously unselected package libglib2.0-dev. Preparing to unpack .../libglib2.0-dev_2.45.6-1_ppc64el.deb ... Unpacking libglib2.0-dev (2.45.6-1) ... Selecting previously unselected package libdbus-glib-1-dev. Preparing to unpack .../libdbus-glib-1-dev_0.104-1build1_ppc64el.deb ... Unpacking libdbus-glib-1-dev (0.104-1build1) ... Selecting previously unselected package xorg-sgml-doctools. Preparing to unpack .../xorg-sgml-doctools_1%3a1.11-1_all.deb ... Unpacking xorg-sgml-doctools (1:1.11-1) ... Selecting previously unselected package x11proto-core-dev. Preparing to unpack .../x11proto-core-dev_7.0.28-0ubuntu1_all.deb ... Unpacking x11proto-core-dev (7.0.28-0ubuntu1) ... Selecting previously unselected package libxau-dev:ppc64el. Preparing to unpack .../libxau-dev_1%3a1.0.8-1_ppc64el.deb ... Unpacking libxau-dev:ppc64el (1:1.0.8-1) ... Selecting previously unselected package libxdmcp-dev:ppc64el. Preparing to unpack .../libxdmcp-dev_1%3a1.1.2-1_ppc64el.deb ... Unpacking libxdmcp-dev:ppc64el (1:1.1.2-1) ... Selecting previously unselected package x11proto-input-dev. Preparing to unpack .../x11proto-input-dev_2.3.1-1_all.deb ... Unpacking x11proto-input-dev (2.3.1-1) ... Selecting previously unselected package x11proto-kb-dev. Preparing to unpack .../x11proto-kb-dev_1.0.7-0ubuntu1_all.deb ... Unpacking x11proto-kb-dev (1.0.7-0ubuntu1) ... Selecting previously unselected package xtrans-dev. Preparing to unpack .../xtrans-dev_1.3.5-1_all.deb ... Unpacking xtrans-dev (1.3.5-1) ... Selecting previously unselected package libpthread-stubs0-dev:ppc64el. Preparing to unpack .../libpthread-stubs0-dev_0.3-4_ppc64el.deb ... Unpacking libpthread-stubs0-dev:ppc64el (0.3-4) ... Selecting previously unselected package libxcb1-dev:ppc64el. Preparing to unpack .../libxcb1-dev_1.11-0ubuntu1_ppc64el.deb ... Unpacking libxcb1-dev:ppc64el (1.11-0ubuntu1) ... Selecting previously unselected package libx11-dev:ppc64el. Preparing to unpack .../libx11-dev_2%3a1.6.3-1ubuntu1_ppc64el.deb ... Unpacking libx11-dev:ppc64el (2:1.6.3-1ubuntu1) ... Selecting previously unselected package libpng12-dev:ppc64el. Preparing to unpack .../libpng12-dev_1.2.51-0ubuntu3_ppc64el.deb ... Unpacking libpng12-dev:ppc64el (1.2.51-0ubuntu3) ... Selecting previously unselected package libgdk-pixbuf2.0-dev. Preparing to unpack .../libgdk-pixbuf2.0-dev_2.31.5-1_ppc64el.deb ... Unpacking libgdk-pixbuf2.0-dev (2.31.5-1) ... Selecting previously unselected package libcairo-script-interpreter2:ppc64el. Preparing to unpack .../libcairo-script-interpreter2_1.14.2-2ubuntu2_ppc64el.deb ... Unpacking libcairo-script-interpreter2:ppc64el (1.14.2-2ubuntu2) ... Selecting previously unselected package libexpat1-dev:ppc64el. Preparing to unpack .../libexpat1-dev_2.1.0-7_ppc64el.deb ... Unpacking libexpat1-dev:ppc64el (2.1.0-7) ... Selecting previously unselected package libfreetype6-dev:ppc64el. Preparing to unpack .../libfreetype6-dev_2.5.2-4ubuntu1_ppc64el.deb ... Unpacking libfreetype6-dev:ppc64el (2.5.2-4ubuntu1) ... Selecting previously unselected package libfontconfig1-dev:ppc64el. Preparing to unpack .../libfontconfig1-dev_2.11.1-0ubuntu6_ppc64el.deb ... Unpacking libfontconfig1-dev:ppc64el (2.11.1-0ubuntu6) ... Selecting previously unselected package x11proto-render-dev. Preparing to unpack .../x11proto-render-dev_2%3a0.11.1-2_all.deb ... Unpacking x11proto-render-dev (2:0.11.1-2) ... Selecting previously unselected package libxrender-dev:ppc64el. Preparing to unpack .../libxrender-dev_1%3a0.9.9-0ubuntu1_ppc64el.deb ... Unpacking libxrender-dev:ppc64el (1:0.9.9-0ubuntu1) ... Selecting previously unselected package x11proto-xext-dev. Preparing to unpack .../x11proto-xext-dev_7.3.0-1_all.deb ... Unpacking x11proto-xext-dev (7.3.0-1) ... Selecting previously unselected package libxext-dev:ppc64el. Preparing to unpack .../libxext-dev_2%3a1.3.3-1_ppc64el.deb ... Unpacking libxext-dev:ppc64el (2:1.3.3-1) ... Selecting previously unselected package libice-dev:ppc64el. Preparing to unpack .../libice-dev_2%3a1.0.9-1_ppc64el.deb ... Unpacking libice-dev:ppc64el (2:1.0.9-1) ... Selecting previously unselected package libsm-dev:ppc64el. Preparing to unpack .../libsm-dev_2%3a1.2.2-1_ppc64el.deb ... Unpacking libsm-dev:ppc64el (2:1.2.2-1) ... Selecting previously unselected package libpixman-1-dev. Preparing to unpack .../libpixman-1-dev_0.32.6-3_ppc64el.deb ... Unpacking libpixman-1-dev (0.32.6-3) ... Selecting previously unselected package libxcb-render0-dev:ppc64el. Preparing to unpack .../libxcb-render0-dev_1.11-0ubuntu1_ppc64el.deb ... Unpacking libxcb-render0-dev:ppc64el (1.11-0ubuntu1) ... Selecting previously unselected package libxcb-shm0-dev:ppc64el. Preparing to unpack .../libxcb-shm0-dev_1.11-0ubuntu1_ppc64el.deb ... Unpacking libxcb-shm0-dev:ppc64el (1.11-0ubuntu1) ... Selecting previously unselected package libcairo2-dev. Preparing to unpack .../libcairo2-dev_1.14.2-2ubuntu2_ppc64el.deb ... Unpacking libcairo2-dev (1.14.2-2ubuntu2) ... Selecting previously unselected package libharfbuzz-icu0:ppc64el. Preparing to unpack .../libharfbuzz-icu0_1.0.1-1build1_ppc64el.deb ... Unpacking libharfbuzz-icu0:ppc64el (1.0.1-1build1) ... Selecting previously unselected package libharfbuzz-gobject0:ppc64el. Preparing to unpack .../libharfbuzz-gobject0_1.0.1-1build1_ppc64el.deb ... Unpacking libharfbuzz-gobject0:ppc64el (1.0.1-1build1) ... Selecting previously unselected package libharfbuzz-dev. Preparing to unpack .../libharfbuzz-dev_1.0.1-1build1_ppc64el.deb ... Unpacking libharfbuzz-dev (1.0.1-1build1) ... Selecting previously unselected package libxft-dev. Preparing to unpack .../libxft-dev_2.3.2-1_ppc64el.deb ... Unpacking libxft-dev (2.3.2-1) ... Selecting previously unselected package libpango1.0-dev. Preparing to unpack .../libpango1.0-dev_1.36.8-3_ppc64el.deb ... Unpacking libpango1.0-dev (1.36.8-3) ... Selecting previously unselected package libatk1.0-dev. Preparing to unpack .../libatk1.0-dev_2.16.0-2_ppc64el.deb ... Unpacking libatk1.0-dev (2.16.0-2) ... Selecting previously unselected package x11proto-xinerama-dev. Preparing to unpack .../x11proto-xinerama-dev_1.2.1-2_all.deb ... Unpacking x11proto-xinerama-dev (1.2.1-2) ... Selecting previously unselected package libxinerama-dev:ppc64el. Preparing to unpack .../libxinerama-dev_2%3a1.1.3-1_ppc64el.deb ... Unpacking libxinerama-dev:ppc64el (2:1.1.3-1) ... Selecting previously unselected package x11proto-fixes-dev. Preparing to unpack .../x11proto-fixes-dev_1%3a5.0-2ubuntu2_all.deb ... Unpacking x11proto-fixes-dev (1:5.0-2ubuntu2) ... Selecting previously unselected package libxfixes-dev:ppc64el. Preparing to unpack .../libxfixes-dev_1%3a5.0.1-2_ppc64el.deb ... Unpacking libxfixes-dev:ppc64el (1:5.0.1-2) ... Selecting previously unselected package libxi-dev. Preparing to unpack .../libxi-dev_2%3a1.7.4-1_ppc64el.deb ... Unpacking libxi-dev (2:1.7.4-1) ... Selecting previously unselected package x11proto-randr-dev. Preparing to unpack .../x11proto-randr-dev_1.5.0-1_all.deb ... Unpacking x11proto-randr-dev (1.5.0-1) ... Selecting previously unselected package libxrandr-dev:ppc64el. Preparing to unpack .../libxrandr-dev_2%3a1.5.0-1_ppc64el.deb ... Unpacking libxrandr-dev:ppc64el (2:1.5.0-1) ... Selecting previously unselected package libxcursor-dev:ppc64el. Preparing to unpack .../libxcursor-dev_1%3a1.1.14-1_ppc64el.deb ... Unpacking libxcursor-dev:ppc64el (1:1.1.14-1) ... Selecting previously unselected package x11proto-composite-dev. Preparing to unpack .../x11proto-composite-dev_1%3a0.4.2-2_all.deb ... Unpacking x11proto-composite-dev (1:0.4.2-2) ... Selecting previously unselected package libxcomposite-dev. Preparing to unpack .../libxcomposite-dev_1%3a0.4.4-1_ppc64el.deb ... Unpacking libxcomposite-dev (1:0.4.4-1) ... Selecting previously unselected package x11proto-damage-dev. Preparing to unpack .../x11proto-damage-dev_1%3a1.2.1-2_all.deb ... Unpacking x11proto-damage-dev (1:1.2.1-2) ... Selecting previously unselected package libxdamage-dev:ppc64el. Preparing to unpack .../libxdamage-dev_1%3a1.1.4-2_ppc64el.deb ... Unpacking libxdamage-dev:ppc64el (1:1.1.4-2) ... Selecting previously unselected package libxml2-utils. Preparing to unpack .../libxml2-utils_2.9.2+dfsg1-3ubuntu1_ppc64el.deb ... Unpacking libxml2-utils (2.9.2+dfsg1-3ubuntu1) ... Selecting previously unselected package libgtk2.0-dev. Preparing to unpack .../libgtk2.0-dev_2.24.28-0ubuntu1_ppc64el.deb ... Unpacking libgtk2.0-dev (2.24.28-0ubuntu1) ... Selecting previously unselected package libdbusmenu-glib-dev:ppc64el. Preparing to unpack .../libdbusmenu-glib-dev_12.10.3+15.04.20150410.2-0ubuntu1_ppc64el.deb ... Unpacking libdbusmenu-glib-dev:ppc64el (12.10.3+15.04.20150410.2-0ubuntu1) ... Selecting previously unselected package libappindicator-dev. Preparing to unpack .../libappindicator-dev_12.10.1+15.04.20141110-0ubuntu1_ppc64el.deb ... Unpacking libappindicator-dev (12.10.1+15.04.20141110-0ubuntu1) ... Selecting previously unselected package libgconf2-dev. Preparing to unpack .../libgconf2-dev_3.2.6-3ubuntu3_ppc64el.deb ... Unpacking libgconf2-dev (3.2.6-3ubuntu3) ... Selecting previously unselected package libgstreamer1.0-dev. Preparing to unpack .../libgstreamer1.0-dev_1.5.2-1_ppc64el.deb ... Adding 'diversion of /usr/bin/dh_gstscancodecs to /usr/bin/dh_gstscancodecs-gst0.10 by libgstreamer1.0-dev' Adding 'diversion of /usr/share/man/man1/dh_gstscancodecs.1.gz to /usr/share/man/man1/dh_gstscancodecs.1.gz-gst0.10 by libgstreamer1.0-dev' Unpacking libgstreamer1.0-dev (1.5.2-1) ... Selecting previously unselected package libicu-dev:ppc64el. Preparing to unpack .../libicu-dev_55.1-4_ppc64el.deb ... Unpacking libicu-dev:ppc64el (55.1-4) ... Selecting previously unselected package libnotify-dev. Preparing to unpack .../libnotify-dev_0.7.6-2svn1_ppc64el.deb ... Unpacking libnotify-dev (0.7.6-2svn1) ... Selecting previously unselected package libunique-1.0-0. Preparing to unpack .../libunique-1.0-0_1.1.6-5_ppc64el.deb ... Unpacking libunique-1.0-0 (1.1.6-5) ... Selecting previously unselected package libunique-dev. Preparing to unpack .../libunique-dev_1.1.6-5_ppc64el.deb ... Unpacking libunique-dev (1.1.6-5) ... Selecting previously unselected package libxml2-dev:ppc64el. Preparing to unpack .../libxml2-dev_2.9.2+dfsg1-3ubuntu1_ppc64el.deb ... Unpacking libxml2-dev:ppc64el (2.9.2+dfsg1-3ubuntu1) ... Selecting previously unselected package sbuild-build-depends-alarm-clock-applet-dummy. Preparing to unpack .../sbuild-build-depends-alarm-clock-applet-dummy.deb ... Unpacking sbuild-build-depends-alarm-clock-applet-dummy (0.invalid.0) ... Processing triggers for systemd (224-2ubuntu2) ... Setting up libmpdec2:ppc64el (2.4.1-1) ... Setting up mime-support (3.58ubuntu1) ... Setting up libpython3.4-stdlib:ppc64el (3.4.3-8) ... Setting up python3.4 (3.4.3-8) ... Setting up libpython3-stdlib:ppc64el (3.4.3-4ubuntu1) ... Setting up libasprintf0v5:ppc64el (0.19.4-1ubuntu3) ... Setting up libcap-ng0:ppc64el (0.7.6-1) ... Setting up libxau6:ppc64el (1:1.0.8-1) ... Setting up libxdmcp6:ppc64el (1:1.1.2-1) ... Setting up libxcb1:ppc64el (1.11-0ubuntu1) ... Setting up libx11-data (2:1.6.3-1ubuntu1) ... Setting up libx11-6:ppc64el (2:1.6.3-1ubuntu1) ... Setting up libxext6:ppc64el (2:1.3.3-1) ... Setting up groff-base (1.22.3-1) ... Setting up bsdmainutils (9.0.6ubuntu1) ... update-alternatives: using /usr/bin/bsd-write to provide /usr/bin/write (write) in auto mode update-alternatives: using /usr/bin/bsd-from to provide /usr/bin/from (from) in auto mode Setting up libpipeline1:ppc64el (1.4.1-1) ... Setting up man-db (2.7.2-1) ... Not building database; man-db/auto-update is not 'true'. Setting up fonts-dejavu-core (2.35-1) ... Setting up ucf (3.0030) ... Setting up fontconfig-config (2.11.1-0ubuntu6) ... Setting up libfreetype6:ppc64el (2.5.2-4ubuntu1) ... Setting up libfontconfig1:ppc64el (2.11.1-0ubuntu6) ... Setting up fontconfig (2.11.1-0ubuntu6) ... Regenerating fonts cache... done. Setting up libdbusmenu-glib4:ppc64el (12.10.3+15.04.20150410.2-0ubuntu1) ... Setting up libglib2.0-0:ppc64el (2.45.6-1) ... Setting up libatk1.0-data (2.16.0-2) ... Setting up libatk1.0-0:ppc64el (2.16.0-2) ... Setting up libjpeg-turbo8:ppc64el (1.3.0-0ubuntu2) ... Setting up libjpeg8:ppc64el (8c-2ubuntu8) ... Setting up libjasper1:ppc64el (1.900.1-debian1-2.4) ... Setting up libjbig0:ppc64el (2.1-3.1) ... Setting up libtiff5:ppc64el (4.0.3-12.3ubuntu2) ... Setting up libgdk-pixbuf2.0-common (2.31.5-1) ... Setting up libgdk-pixbuf2.0-0:ppc64el (2.31.5-1) ... Setting up libthai-data (0.1.22-2) ... Setting up libdatrie1:ppc64el (0.2.9-2) ... Setting up libthai0:ppc64el (0.1.22-2) ... Setting up libpango-1.0-0:ppc64el (1.36.8-3) ... Setting up libdbusmenu-gtk4:ppc64el (12.10.3+15.04.20150410.2-0ubuntu1) ... Setting up libgtk2.0-common (2.24.28-0ubuntu1) ... Setting up libpixman-1-0:ppc64el (0.32.6-3) ... Setting up libxcb-render0:ppc64el (1.11-0ubuntu1) ... Setting up libxcb-shm0:ppc64el (1.11-0ubuntu1) ... Setting up libxrender1:ppc64el (1:0.9.9-0ubuntu1) ... Setting up libcairo2:ppc64el (1.14.2-2ubuntu2) ... Setting up libavahi-common-data:ppc64el (0.6.31-4ubuntu4) ... Setting up libavahi-common3:ppc64el (0.6.31-4ubuntu4) ... Setting up libavahi-client3:ppc64el (0.6.31-4ubuntu4) ... Setting up libcups2:ppc64el (2.1~rc1-3) ... Setting up libgraphite2-3:ppc64el (1.2.4-3ubuntu1) ... Setting up libharfbuzz0b:ppc64el (1.0.1-1build1) ... Setting up libpangoft2-1.0-0:ppc64el (1.36.8-3) ... Setting up libpangocairo-1.0-0:ppc64el (1.36.8-3) ... Setting up libxcomposite1:ppc64el (1:0.4.4-1) ... Setting up libxfixes3:ppc64el (1:5.0.1-2) ... Setting up libxcursor1:ppc64el (1:1.1.14-1) ... Setting up libxdamage1:ppc64el (1:1.1.4-2) ... Setting up libxi6:ppc64el (2:1.7.4-1) ... Setting up libxinerama1:ppc64el (2:1.1.3-1) ... Setting up libxrandr2:ppc64el (2:1.5.0-1) ... Setting up libicu55:ppc64el (55.1-4) ... Setting up libxml2:ppc64el (2.9.2+dfsg1-3ubuntu1) ... Setting up shared-mime-info (1.3-1) ... Setting up libgtk2.0-0:ppc64el (2.24.28-0ubuntu1) ... Setting up libindicator7 (12.10.2+14.10.20140922-0ubuntu1) ... Setting up libappindicator1 (12.10.1+15.04.20141110-0ubuntu1) ... Setting up libcroco3:ppc64el (0.6.8-3) ... Setting up x11-common (1:7.7+7ubuntu4) ... update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults invoke-rc.d: policy-rc.d denied execution of start. Setting up libice6:ppc64el (2:1.0.9-1) ... Setting up liblcms2-2:ppc64el (2.6-3ubuntu2) ... Setting up liblzo2-2:ppc64el (2.08-1.2) ... Setting up libnotify4:ppc64el (0.7.6-2svn1) ... Setting up libxft2:ppc64el (2.3.2-1) ... Setting up libpangoxft-1.0-0:ppc64el (1.36.8-3) ... Setting up libpcrecpp0v5:ppc64el (2:8.35-7ubuntu5) ... Setting up libproxy1v5:ppc64el (0.4.11-4ubuntu3~gcc5.3) ... Setting up glib-networking-common (2.45.1-1build1) ... Setting up glib-networking-services (2.45.1-1build1) ... Setting up libdconf1:ppc64el (0.24.0-2) ... Setting up dconf-service (0.24.0-2) ... Setting up dconf-gsettings-backend:ppc64el (0.24.0-2) ... Setting up gsettings-desktop-schemas (3.16.1-1ubuntu1) ... Setting up glib-networking:ppc64el (2.45.1-1build1) ... Setting up libsoup2.4-1:ppc64el (2.50.0-2) ... Setting up libsoup-gnome2.4-1:ppc64el (2.50.0-2) ... Setting up librest-0.7-0:ppc64el (0.7.93-1) ... Setting up libsigsegv2:ppc64el (2.10-4) ... Setting up libsm6:ppc64el (2:1.2.2-1) ... Setting up libunistring0:ppc64el (0.9.3-5.2ubuntu1) ... Setting up libpython2.7-stdlib:ppc64el (2.7.10-3) ... Setting up python2.7 (2.7.10-3) ... Setting up libpython-stdlib:ppc64el (2.7.9-1) ... Setting up python (2.7.9-1) ... Setting up libmagic1:ppc64el (1:5.22+15-2ubuntu1) ... Setting up file (1:5.22+15-2ubuntu1) ... Setting up netbase (5.3) ... Setting up xkb-data (2.12-1ubuntu1) ... Setting up dbus (1.9.20-1ubuntu2) ... invoke-rc.d: policy-rc.d denied execution of start. Setting up gettext-base (0.19.4-1ubuntu3) ... Setting up libgirepository-1.0-1:ppc64el (1.44.0-1) ... Setting up gir1.2-glib-2.0:ppc64el (1.44.0-1) ... Setting up libdbus-glib-1-2:ppc64el (0.104-1build1) ... Setting up libdrm2:ppc64el (2.4.64-1) ... Setting up libelf1:ppc64el (0.163-4ubuntu1) ... Setting up libglib2.0-data (2.45.6-1) ... Setting up psmisc (22.21-2build1) ... Setting up hicolor-icon-theme (0.15-0ubuntu1) ... Setting up libatspi2.0-0:ppc64el (2.16.0-1ubuntu1) ... Setting up libatk-bridge2.0-0:ppc64el (2.16.0-1ubuntu1) ... Setting up libcairo-gobject2:ppc64el (1.14.2-2ubuntu2) ... Setting up libcolord2:ppc64el (1.2.11-0ubuntu1) ... Setting up libepoxy0 (1.2-1) ... Setting up libjson-glib-1.0-common (1.0.4-1) ... Setting up libjson-glib-1.0-0:ppc64el (1.0.4-1) ... Setting up libboost-system1.58.0:ppc64el (1.58.0+dfsg-0ubuntu5) ... Setting up libboost-filesystem1.58.0:ppc64el (1.58.0+dfsg-0ubuntu5) ... Setting up libmircommon5:ppc64el (0.15.1+15.10.20150825-0ubuntu1) ... Setting up libprotobuf-lite9v5:ppc64el (2.6.1-1.2) ... Setting up libmirprotobuf1:ppc64el (0.15.1+15.10.20150825-0ubuntu1) ... Setting up libxkbcommon0:ppc64el (0.5.0-1ubuntu2) ... Setting up libmirclient9:ppc64el (0.15.1+15.10.20150825-0ubuntu1) ... Setting up libwayland-client0:ppc64el (1.8.1-1) ... Setting up libwayland-cursor0:ppc64el (1.8.1-1) ... Setting up libwayland-server0:ppc64el (1.8.1-1) ... Setting up libdrm-nouveau2:ppc64el (2.4.64-1) ... Setting up libdrm-radeon1:ppc64el (2.4.64-1) ... Setting up libgl1-mesa-dri:ppc64el (10.6.3-1ubuntu1) ... Setting up libgbm1:ppc64el (10.6.3-1ubuntu1) ... Setting up libx11-xcb1:ppc64el (2:1.6.3-1ubuntu1) ... Setting up libxcb-dri2-0:ppc64el (1.11-0ubuntu1) ... Setting up libxcb-xfixes0:ppc64el (1.11-0ubuntu1) ... Setting up libegl1-mesa:ppc64el (10.6.3-1ubuntu1) ... update-alternatives: using /usr/lib/powerpc64le-linux-gnu/mesa-egl/ld.so.conf to provide /etc/ld.so.conf.d/powerpc64le-linux-gnu_EGL.conf (powerpc64le-linux-gnu_egl_conf) in auto mode Setting up libwayland-egl1-mesa:ppc64el (10.6.3-1ubuntu1) ... Setting up librsvg2-2:ppc64el (2.40.10-1) ... Setting up librsvg2-common:ppc64el (2.40.10-1) ... Setting up m4 (1.4.17-4) ... Setting up autoconf (2.69-8) ... Setting up autotools-dev (20140911.1) ... Setting up automake (1:1.15-1ubuntu1) ... update-alternatives: using /usr/bin/automake-1.15 to provide /usr/bin/automake (automake) in auto mode Setting up dbus-x11 (1.9.20-1ubuntu2) ... Setting up gettext (0.19.4-1ubuntu3) ... Setting up intltool-debian (0.35.0+20060710.2) ... Setting up po-debconf (1.0.18) ... Setting up debhelper (9.20150811ubuntu1) ... Setting up gconf2-common (3.2.6-3ubuntu3) ... Creating config file /etc/gconf/2/path with new version Setting up libgconf-2-4:ppc64el (3.2.6-3ubuntu3) ... Setting up gir1.2-atk-1.0 (2.16.0-2) ... Setting up gir1.2-freedesktop:ppc64el (1.44.0-1) ... Setting up gir1.2-gdkpixbuf-2.0:ppc64el (2.31.5-1) ... Setting up gir1.2-pango-1.0:ppc64el (1.36.8-3) ... Setting up gir1.2-gtk-2.0 (2.24.28-0ubuntu1) ... Setting up gir1.2-appindicator-0.1 (12.10.1+15.04.20141110-0ubuntu1) ... Setting up gir1.2-dbusmenu-glib-0.4:ppc64el (12.10.3+15.04.20150410.2-0ubuntu1) ... Setting up libgstreamer1.0-0:ppc64el (1.5.2-1) ... Setcap worked! gst-ptp-helper is not suid! Setting up gir1.2-gstreamer-1.0 (1.5.2-1) ... Setting up gir1.2-notify-0.7 (0.7.6-2svn1) ... Setting up icu-devtools (55.1-4) ... Setting up liburi-perl (1.69-1) ... Setting up libencode-locale-perl (1.03-1) ... Setting up libhttp-date-perl (6.02-1) ... Setting up libfile-listing-perl (6.04-1) ... Setting up libhtml-tagset-perl (3.20-2) ... Setting up libhtml-parser-perl (3.71-2) ... Setting up libhtml-tree-perl (5.03-2) ... Setting up libio-html-perl (1.001-1) ... Setting up liblwp-mediatypes-perl (6.02-1) ... Setting up libhttp-message-perl (6.06-1) ... Setting up libhttp-cookies-perl (6.01-1) ... Setting up libhttp-negotiate-perl (6.00-2) ... Setting up libnet-ssleay-perl (1.70-1) ... Setting up libio-socket-ssl-perl (1.965-1ubuntu1) ... Setting up libnet-http-perl (6.09-1) ... Setting up libwww-robotrules-perl (6.01-1) ... Setting up pkg-config (0.28-1ubuntu1) ... Setting up libdbus-1-dev:ppc64el (1.9.20-1ubuntu2) ... Setting up libglib2.0-bin (2.45.6-1) ... Setting up libpcre16-3:ppc64el (2:8.35-7ubuntu5) ... Setting up libpcre32-3:ppc64el (2:8.35-7ubuntu5) ... Setting up libpcre3-dev:ppc64el (2:8.35-7ubuntu5) ... Setting up zlib1g-dev:ppc64el (1:1.2.8.dfsg-2ubuntu1) ... Setting up libglib2.0-dev (2.45.6-1) ... Setting up libdbus-glib-1-dev (0.104-1build1) ... Setting up xorg-sgml-doctools (1:1.11-1) ... Setting up x11proto-core-dev (7.0.28-0ubuntu1) ... Setting up libxau-dev:ppc64el (1:1.0.8-1) ... Setting up libxdmcp-dev:ppc64el (1:1.1.2-1) ... Setting up x11proto-input-dev (2.3.1-1) ... Setting up x11proto-kb-dev (1.0.7-0ubuntu1) ... Setting up xtrans-dev (1.3.5-1) ... Setting up libpthread-stubs0-dev:ppc64el (0.3-4) ... Setting up libxcb1-dev:ppc64el (1.11-0ubuntu1) ... Setting up libx11-dev:ppc64el (2:1.6.3-1ubuntu1) ... Setting up libpng12-dev:ppc64el (1.2.51-0ubuntu3) ... Setting up libgdk-pixbuf2.0-dev (2.31.5-1) ... Setting up libcairo-script-interpreter2:ppc64el (1.14.2-2ubuntu2) ... Setting up libexpat1-dev:ppc64el (2.1.0-7) ... Setting up libfreetype6-dev:ppc64el (2.5.2-4ubuntu1) ... Setting up libfontconfig1-dev:ppc64el (2.11.1-0ubuntu6) ... Setting up x11proto-render-dev (2:0.11.1-2) ... Setting up libxrender-dev:ppc64el (1:0.9.9-0ubuntu1) ... Setting up x11proto-xext-dev (7.3.0-1) ... Setting up libxext-dev:ppc64el (2:1.3.3-1) ... Setting up libice-dev:ppc64el (2:1.0.9-1) ... Setting up libsm-dev:ppc64el (2:1.2.2-1) ... Setting up libpixman-1-dev (0.32.6-3) ... Setting up libxcb-render0-dev:ppc64el (1.11-0ubuntu1) ... Setting up libxcb-shm0-dev:ppc64el (1.11-0ubuntu1) ... Setting up libcairo2-dev (1.14.2-2ubuntu2) ... Setting up libharfbuzz-icu0:ppc64el (1.0.1-1build1) ... Setting up libharfbuzz-gobject0:ppc64el (1.0.1-1build1) ... Setting up libharfbuzz-dev (1.0.1-1build1) ... Setting up libxft-dev (2.3.2-1) ... Setting up libpango1.0-dev (1.36.8-3) ... Setting up libatk1.0-dev (2.16.0-2) ... Setting up x11proto-xinerama-dev (1.2.1-2) ... Setting up libxinerama-dev:ppc64el (2:1.1.3-1) ... Setting up x11proto-fixes-dev (1:5.0-2ubuntu2) ... Setting up libxfixes-dev:ppc64el (1:5.0.1-2) ... Setting up libxi-dev (2:1.7.4-1) ... Setting up x11proto-randr-dev (1.5.0-1) ... Setting up libxrandr-dev:ppc64el (2:1.5.0-1) ... Setting up libxcursor-dev:ppc64el (1:1.1.14-1) ... Setting up x11proto-composite-dev (1:0.4.2-2) ... Setting up libxcomposite-dev (1:0.4.4-1) ... Setting up x11proto-damage-dev (1:1.2.1-2) ... Setting up libxdamage-dev:ppc64el (1:1.1.4-2) ... Setting up libxml2-utils (2.9.2+dfsg1-3ubuntu1) ... Setting up libgtk2.0-dev (2.24.28-0ubuntu1) ... Setting up libdbusmenu-glib-dev:ppc64el (12.10.3+15.04.20150410.2-0ubuntu1) ... Setting up libappindicator-dev (12.10.1+15.04.20141110-0ubuntu1) ... Setting up libgstreamer1.0-dev (1.5.2-1) ... Setting up libicu-dev:ppc64el (55.1-4) ... Setting up libnotify-dev (0.7.6-2svn1) ... Setting up libunique-1.0-0 (1.1.6-5) ... Setting up libunique-dev (1.1.6-5) ... Setting up libxml2-dev:ppc64el (2.9.2+dfsg1-3ubuntu1) ... Setting up dh-python (2.20150826) ... Setting up python3 (3.4.3-4ubuntu1) ... Setting up libgtk-3-common (3.16.6-1ubuntu1) ... Setting up libgtk-3-0:ppc64el (3.16.6-1ubuntu1) ... Setting up gconf-service (3.2.6-3ubuntu3) ... Setting up gir1.2-gconf-2.0 (3.2.6-3ubuntu3) ... Setting up libwww-perl (6.13-1) ... Setting up libxml-parser-perl (2.41-3) ... Setting up intltool (0.51.0-1) ... Setting up libgtk-3-bin (3.16.6-1ubuntu1) ... Setting up adwaita-icon-theme (3.16.2.1-2ubuntu1) ... Setting up gconf-service-backend (3.2.6-3ubuntu3) ... Setting up gconf2 (3.2.6-3ubuntu3) ... Setting up liblwp-protocol-https-perl (6.06-2) ... Setting up libgconf2-dev (3.2.6-3ubuntu3) ... Setting up humanity-icon-theme (0.6.9) ... Setting up ubuntu-mono (14.04+15.10.20150813-0ubuntu1) ... Setting up gnome-icon-theme (3.12.0-1ubuntu1) ... Setting up sbuild-build-depends-alarm-clock-applet-dummy (0.invalid.0) ... Processing triggers for libc-bin (2.21-0ubuntu4) ... Processing triggers for systemd (224-2ubuntu2) ... Processing triggers for libgdk-pixbuf2.0-0:ppc64el (2.31.5-1) ... ┌──────────────────────────────────────────────────────────────────────────────┐ │ Build environment │ └──────────────────────────────────────────────────────────────────────────────┘ Kernel: Linux 3.13.0-62-generic ppc64el (ppc64le) Toolchain package versions: binutils_2.25.1-1ubuntu1 dpkg-dev_1.18.2ubuntu3 g++-5_5.2.1-15ubuntu5 gcc-5_5.2.1-15ubuntu5 libc6-dev_2.21-0ubuntu4 libstdc++-5-dev_5.2.1-15ubuntu5 libstdc++6_5.2.1-15ubuntu5 linux-libc-dev_4.1.0-3.3 Package versions: adduser_3.113+nmu3ubuntu4 advancecomp_1.19-1 adwaita-icon-theme_3.16.2.1-2ubuntu1 apt_1.0.9.10ubuntu6 apt-transport-https_1.0.9.10ubuntu6 autoconf_2.69-8 automake_1:1.15-1ubuntu1 autotools-dev_20140911.1 base-files_7.2ubuntu10 base-passwd_3.5.38 bash_4.3-13ubuntu1 binutils_2.25.1-1ubuntu1 bsdmainutils_9.0.6ubuntu1 bsdutils_1:2.26.2-6ubuntu3 build-essential_11.6ubuntu6 bzip2_1.0.6-8 ca-certificates_20150426ubuntu1 coreutils_8.23-3ubuntu1 cpp_4:5.2.1-3ubuntu1 cpp-5_5.2.1-15ubuntu5 dash_0.5.7-4ubuntu2 dbus_1.9.20-1ubuntu2 dbus-x11_1.9.20-1ubuntu2 dconf-gsettings-backend_0.24.0-2 dconf-service_0.24.0-2 debconf_1.5.57ubuntu1 debhelper_9.20150811ubuntu1 debianutils_4.5.1 dh-python_2.20150826 diffutils_1:3.3-1 dmsetup_2:1.02.99-1ubuntu1 dpkg_1.18.2ubuntu3 dpkg-dev_1.18.2ubuntu3 e2fslibs_1.42.12-1ubuntu2 e2fsprogs_1.42.12-1ubuntu2 fakeroot_1.20.2-1ubuntu1 file_1:5.22+15-2ubuntu1 findutils_4.4.2-9build1 fontconfig_2.11.1-0ubuntu6 fontconfig-config_2.11.1-0ubuntu6 fonts-dejavu-core_2.35-1 g++_4:5.2.1-3ubuntu1 g++-5_5.2.1-15ubuntu5 gcc_4:5.2.1-3ubuntu1 gcc-5_5.2.1-15ubuntu5 gcc-5-base_5.2.1-15ubuntu5 gconf-service_3.2.6-3ubuntu3 gconf-service-backend_3.2.6-3ubuntu3 gconf2_3.2.6-3ubuntu3 gconf2-common_3.2.6-3ubuntu3 gettext_0.19.4-1ubuntu3 gettext-base_0.19.4-1ubuntu3 gir1.2-appindicator-0.1_12.10.1+15.04.20141110-0ubuntu1 gir1.2-atk-1.0_2.16.0-2 gir1.2-dbusmenu-glib-0.4_12.10.3+15.04.20150410.2-0ubuntu1 gir1.2-freedesktop_1.44.0-1 gir1.2-gconf-2.0_3.2.6-3ubuntu3 gir1.2-gdkpixbuf-2.0_2.31.5-1 gir1.2-glib-2.0_1.44.0-1 gir1.2-gstreamer-1.0_1.5.2-1 gir1.2-gtk-2.0_2.24.28-0ubuntu1 gir1.2-notify-0.7_0.7.6-2svn1 gir1.2-pango-1.0_1.36.8-3 glib-networking_2.45.1-1build1 glib-networking-common_2.45.1-1build1 glib-networking-services_2.45.1-1build1 gnome-icon-theme_3.12.0-1ubuntu1 gnupg_1.4.18-7ubuntu1 gpgv_1.4.18-7ubuntu1 grep_2.21-2 groff-base_1.22.3-1 gsettings-desktop-schemas_3.16.1-1ubuntu1 gzip_1.6-4ubuntu1 hicolor-icon-theme_0.15-0ubuntu1 hostname_3.15ubuntu2 humanity-icon-theme_0.6.9 icu-devtools_55.1-4 init_1.23ubuntu3 initscripts_2.88dsf-59.2ubuntu1 insserv_1.14.0-5ubuntu3 intltool_0.51.0-1 intltool-debian_0.35.0+20060710.2 libacl1_2.2.52-2 libapparmor1_2.10-0ubuntu4 libappindicator-dev_12.10.1+15.04.20141110-0ubuntu1 libappindicator1_12.10.1+15.04.20141110-0ubuntu1 libapt-pkg4.12_1.0.9.10ubuntu1 libapt-pkg4.16_1.0.9.10ubuntu6 libasan2_5.2.1-15ubuntu5 libasn1-8-heimdal_1.6~rc2+dfsg-10 libasprintf0v5_0.19.4-1ubuntu3 libatk-bridge2.0-0_2.16.0-1ubuntu1 libatk1.0-0_2.16.0-2 libatk1.0-data_2.16.0-2 libatk1.0-dev_2.16.0-2 libatomic1_5.2.1-15ubuntu5 libatspi2.0-0_2.16.0-1ubuntu1 libattr1_1:2.4.47-2 libaudit-common_1:2.4.2-1ubuntu1 libaudit1_1:2.4.2-1ubuntu1 libavahi-client3_0.6.31-4ubuntu4 libavahi-common-data_0.6.31-4ubuntu4 libavahi-common3_0.6.31-4ubuntu4 libblkid1_2.26.2-6ubuntu3 libboost-filesystem1.58.0_1.58.0+dfsg-0ubuntu5 libboost-system1.58.0_1.58.0+dfsg-0ubuntu5 libbz2-1.0_1.0.6-8 libc-bin_2.21-0ubuntu4 libc-dev-bin_2.21-0ubuntu4 libc6_2.21-0ubuntu4 libc6-dev_2.21-0ubuntu4 libcairo-gobject2_1.14.2-2ubuntu2 libcairo-script-interpreter2_1.14.2-2ubuntu2 libcairo2_1.14.2-2ubuntu2 libcairo2-dev_1.14.2-2ubuntu2 libcap-ng0_0.7.6-1 libcap2_1:2.24-9 libcap2-bin_1:2.24-9 libcc1-0_5.2.1-15ubuntu5 libcolord2_1.2.11-0ubuntu1 libcomerr2_1.42.12-1ubuntu2 libcroco3_0.6.8-3 libcryptsetup4_2:1.6.6-5ubuntu2 libcups2_2.1~rc1-3 libcurl3-gnutls_7.43.0-1ubuntu1 libdatrie1_0.2.9-2 libdb5.3_5.3.28-9 libdbus-1-3_1.9.20-1ubuntu2 libdbus-1-dev_1.9.20-1ubuntu2 libdbus-glib-1-2_0.104-1build1 libdbus-glib-1-dev_0.104-1build1 libdbusmenu-glib-dev_12.10.3+15.04.20150410.2-0ubuntu1 libdbusmenu-glib4_12.10.3+15.04.20150410.2-0ubuntu1 libdbusmenu-gtk4_12.10.3+15.04.20150410.2-0ubuntu1 libdconf1_0.24.0-2 libdebconfclient0_0.192ubuntu1 libdevmapper1.02.1_2:1.02.99-1ubuntu1 libdpkg-perl_1.18.2ubuntu3 libdrm-nouveau2_2.4.64-1 libdrm-radeon1_2.4.64-1 libdrm2_2.4.64-1 libegl1-mesa_10.6.3-1ubuntu1 libelf1_0.163-4ubuntu1 libencode-locale-perl_1.03-1 libepoxy0_1.2-1 libexpat1_2.1.0-7 libexpat1-dev_2.1.0-7 libfakeroot_1.20.2-1ubuntu1 libfdisk1_2.26.2-6ubuntu3 libffi6_3.2.1-3 libfile-listing-perl_6.04-1 libfontconfig1_2.11.1-0ubuntu6 libfontconfig1-dev_2.11.1-0ubuntu6 libfreetype6_2.5.2-4ubuntu1 libfreetype6-dev_2.5.2-4ubuntu1 libgbm1_10.6.3-1ubuntu1 libgcc-5-dev_5.2.1-15ubuntu5 libgcc1_1:5.2.1-15ubuntu5 libgconf-2-4_3.2.6-3ubuntu3 libgconf2-dev_3.2.6-3ubuntu3 libgcrypt20_1.6.3-2ubuntu1 libgdbm3_1.8.3-13.1 libgdk-pixbuf2.0-0_2.31.5-1 libgdk-pixbuf2.0-common_2.31.5-1 libgdk-pixbuf2.0-dev_2.31.5-1 libgirepository-1.0-1_1.44.0-1 libgl1-mesa-dri_10.6.3-1ubuntu1 libglib2.0-0_2.45.6-1 libglib2.0-bin_2.45.6-1 libglib2.0-data_2.45.6-1 libglib2.0-dev_2.45.6-1 libgmp10_2:6.0.0+dfsg-7 libgnutls-deb0-28_3.3.15-5ubuntu1 libgomp1_5.2.1-15ubuntu5 libgpg-error0_1.19-2 libgraphite2-3_1.2.4-3ubuntu1 libgssapi-krb5-2_1.13.2+dfsg-2 libgssapi3-heimdal_1.6~rc2+dfsg-10 libgstreamer1.0-0_1.5.2-1 libgstreamer1.0-dev_1.5.2-1 libgtk-3-0_3.16.6-1ubuntu1 libgtk-3-bin_3.16.6-1ubuntu1 libgtk-3-common_3.16.6-1ubuntu1 libgtk2.0-0_2.24.28-0ubuntu1 libgtk2.0-common_2.24.28-0ubuntu1 libgtk2.0-dev_2.24.28-0ubuntu1 libharfbuzz-dev_1.0.1-1build1 libharfbuzz-gobject0_1.0.1-1build1 libharfbuzz-icu0_1.0.1-1build1 libharfbuzz0b_1.0.1-1build1 libhcrypto4-heimdal_1.6~rc2+dfsg-10 libheimbase1-heimdal_1.6~rc2+dfsg-10 libheimntlm0-heimdal_1.6~rc2+dfsg-10 libhogweed4_3.1.1-4 libhtml-parser-perl_3.71-2 libhtml-tagset-perl_3.20-2 libhtml-tree-perl_5.03-2 libhttp-cookies-perl_6.01-1 libhttp-date-perl_6.02-1 libhttp-message-perl_6.06-1 libhttp-negotiate-perl_6.00-2 libhx509-5-heimdal_1.6~rc2+dfsg-10 libice-dev_2:1.0.9-1 libice6_2:1.0.9-1 libicu-dev_55.1-4 libicu55_55.1-4 libidn11_1.28-1ubuntu2 libindicator7_12.10.2+14.10.20140922-0ubuntu1 libio-html-perl_1.001-1 libio-socket-ssl-perl_1.965-1ubuntu1 libisl13_0.14-2 libitm1_5.2.1-15ubuntu5 libjasper1_1.900.1-debian1-2.4 libjbig0_2.1-3.1 libjpeg-turbo8_1.3.0-0ubuntu2 libjpeg8_8c-2ubuntu8 libjson-glib-1.0-0_1.0.4-1 libjson-glib-1.0-common_1.0.4-1 libk5crypto3_1.13.2+dfsg-2 libkeyutils1_1.5.9-5ubuntu1 libkmod2_21-1ubuntu1 libkrb5-26-heimdal_1.6~rc2+dfsg-10 libkrb5-3_1.13.2+dfsg-2 libkrb5support0_1.13.2+dfsg-2 liblcms2-2_2.6-3ubuntu2 libldap-2.4-2_2.4.41+dfsg-1ubuntu1 liblockfile-bin_1.09-6ubuntu1 liblockfile1_1.09-6ubuntu1 liblwp-mediatypes-perl_6.02-1 liblwp-protocol-https-perl_6.06-2 liblzma5_5.1.1alpha+20120614-2ubuntu2 liblzo2-2_2.08-1.2 libmagic1_1:5.22+15-2ubuntu1 libmirclient9_0.15.1+15.10.20150825-0ubuntu1 libmircommon5_0.15.1+15.10.20150825-0ubuntu1 libmirprotobuf1_0.15.1+15.10.20150825-0ubuntu1 libmount1_2.26.2-6ubuntu3 libmpc3_1.0.3-1 libmpdec2_2.4.1-1 libmpfr4_3.1.3-1 libncurses5_5.9+20150516-2ubuntu1 libncursesw5_5.9+20150516-2ubuntu1 libnet-http-perl_6.09-1 libnet-ssleay-perl_1.70-1 libnettle6_3.1.1-4 libnih-dbus1_1.0.3-4ubuntu27 libnih1_1.0.3-4ubuntu27 libnotify-dev_0.7.6-2svn1 libnotify4_0.7.6-2svn1 libp11-kit0_0.23.1-3 libpam-modules_1.1.8-3.1ubuntu3 libpam-modules-bin_1.1.8-3.1ubuntu3 libpam-runtime_1.1.8-3.1ubuntu3 libpam0g_1.1.8-3.1ubuntu3 libpango-1.0-0_1.36.8-3 libpango1.0-dev_1.36.8-3 libpangocairo-1.0-0_1.36.8-3 libpangoft2-1.0-0_1.36.8-3 libpangoxft-1.0-0_1.36.8-3 libpcre16-3_2:8.35-7ubuntu5 libpcre3_2:8.35-7ubuntu5 libpcre3-dev_2:8.35-7ubuntu5 libpcre32-3_2:8.35-7ubuntu5 libpcrecpp0v5_2:8.35-7ubuntu5 libpipeline1_1.4.1-1 libpixman-1-0_0.32.6-3 libpixman-1-dev_0.32.6-3 libpng12-0_1.2.51-0ubuntu3 libpng12-dev_1.2.51-0ubuntu3 libprocps3_1:3.3.9-1ubuntu8 libprotobuf-lite9v5_2.6.1-1.2 libproxy1v5_0.4.11-4ubuntu3~gcc5.3 libpthread-stubs0-dev_0.3-4 libpython-stdlib_2.7.9-1 libpython2.7-minimal_2.7.10-3 libpython2.7-stdlib_2.7.10-3 libpython3-stdlib_3.4.3-4ubuntu1 libpython3.4-minimal_3.4.3-8 libpython3.4-stdlib_3.4.3-8 libreadline6_6.3-8ubuntu1 librest-0.7-0_0.7.93-1 libroken18-heimdal_1.6~rc2+dfsg-10 librsvg2-2_2.40.10-1 librsvg2-common_2.40.10-1 librtmp1_2.4+20150115.gita107cef-1build1 libsasl2-2_2.1.26.dfsg1-13 libsasl2-modules-db_2.1.26.dfsg1-13 libselinux1_2.3-2 libsemanage-common_2.3-1build1 libsemanage1_2.3-1build1 libsepol1_2.3-2 libsigsegv2_2.10-4 libslang2_2.3.0-2ubuntu1 libsm-dev_2:1.2.2-1 libsm6_2:1.2.2-1 libsmartcols1_2.26.2-6ubuntu3 libsoup-gnome2.4-1_2.50.0-2 libsoup2.4-1_2.50.0-2 libsqlite3-0_3.8.11.1-1 libss2_1.42.12-1ubuntu2 libssl1.0.0_1.0.2d-0ubuntu1 libstdc++-5-dev_5.2.1-15ubuntu5 libstdc++6_5.2.1-15ubuntu5 libsystemd0_224-2ubuntu2 libtasn1-6_4.5-2 libthai-data_0.1.22-2 libthai0_0.1.22-2 libtiff5_4.0.3-12.3ubuntu2 libtimedate-perl_2.3000-2 libtinfo5_5.9+20150516-2ubuntu1 libubsan0_5.2.1-15ubuntu5 libudev1_224-2ubuntu2 libunique-1.0-0_1.1.6-5 libunique-dev_1.1.6-5 libunistring0_0.9.3-5.2ubuntu1 liburi-perl_1.69-1 libusb-0.1-4_2:0.1.12-27 libustr-1.0-1_1.0.4-5 libuuid1_2.26.2-6ubuntu3 libwayland-client0_1.8.1-1 libwayland-cursor0_1.8.1-1 libwayland-egl1-mesa_10.6.3-1ubuntu1 libwayland-server0_1.8.1-1 libwind0-heimdal_1.6~rc2+dfsg-10 libwww-perl_6.13-1 libwww-robotrules-perl_6.01-1 libx11-6_2:1.6.3-1ubuntu1 libx11-data_2:1.6.3-1ubuntu1 libx11-dev_2:1.6.3-1ubuntu1 libx11-xcb1_2:1.6.3-1ubuntu1 libxau-dev_1:1.0.8-1 libxau6_1:1.0.8-1 libxcb-dri2-0_1.11-0ubuntu1 libxcb-render0_1.11-0ubuntu1 libxcb-render0-dev_1.11-0ubuntu1 libxcb-shm0_1.11-0ubuntu1 libxcb-shm0-dev_1.11-0ubuntu1 libxcb-xfixes0_1.11-0ubuntu1 libxcb1_1.11-0ubuntu1 libxcb1-dev_1.11-0ubuntu1 libxcomposite-dev_1:0.4.4-1 libxcomposite1_1:0.4.4-1 libxcursor-dev_1:1.1.14-1 libxcursor1_1:1.1.14-1 libxdamage-dev_1:1.1.4-2 libxdamage1_1:1.1.4-2 libxdmcp-dev_1:1.1.2-1 libxdmcp6_1:1.1.2-1 libxext-dev_2:1.3.3-1 libxext6_2:1.3.3-1 libxfixes-dev_1:5.0.1-2 libxfixes3_1:5.0.1-2 libxft-dev_2.3.2-1 libxft2_2.3.2-1 libxi-dev_2:1.7.4-1 libxi6_2:1.7.4-1 libxinerama-dev_2:1.1.3-1 libxinerama1_2:1.1.3-1 libxkbcommon0_0.5.0-1ubuntu2 libxml-parser-perl_2.41-3 libxml2_2.9.2+dfsg1-3ubuntu1 libxml2-dev_2.9.2+dfsg1-3ubuntu1 libxml2-utils_2.9.2+dfsg1-3ubuntu1 libxrandr-dev_2:1.5.0-1 libxrandr2_2:1.5.0-1 libxrender-dev_1:0.9.9-0ubuntu1 libxrender1_1:0.9.9-0ubuntu1 linux-libc-dev_4.1.0-3.3 lockfile-progs_0.1.17 login_1:4.1.5.1-1.1ubuntu7 lsb-base_4.1+Debian11ubuntu8 m4_1.4.17-4 make_4.0-8.1 man-db_2.7.2-1 mawk_1.3.3-17ubuntu2 mime-support_3.58ubuntu1 mount_2.26.2-6ubuntu3 multiarch-support_2.21-0ubuntu4 ncurses-base_5.9+20150516-2ubuntu1 ncurses-bin_5.9+20150516-2ubuntu1 netbase_5.3 openssl_1.0.2d-0ubuntu1 optipng_0.7.5-1 passwd_1:4.1.5.1-1.1ubuntu7 patch_2.7.5-1 perl_5.20.2-6 perl-base_5.20.2-6 perl-modules_5.20.2-6 pkg-config_0.28-1ubuntu1 pkg-create-dbgsym_0.69 pkgbinarymangler_121 po-debconf_1.0.18 policyrcd-script-zg2_0.1-2 procps_1:3.3.9-1ubuntu8 psmisc_22.21-2build1 python_2.7.9-1 python-minimal_2.7.9-1 python2.7_2.7.10-3 python2.7-minimal_2.7.10-3 python3_3.4.3-4ubuntu1 python3-minimal_3.4.3-4ubuntu1 python3.4_3.4.3-8 python3.4-minimal_3.4.3-8 readline-common_6.3-8ubuntu1 sbuild-build-depends-alarm-clock-applet-dummy_0.invalid.0 sbuild-build-depends-core-dummy_0.invalid.0 sed_4.2.2-6.1 sensible-utils_0.0.9 shared-mime-info_1.3-1 systemd_224-2ubuntu2 systemd-sysv_224-2ubuntu2 sysv-rc_2.88dsf-59.2ubuntu1 sysvinit-utils_2.88dsf-59.2ubuntu1 tar_1.27.1-2 tzdata_2015f-1 ubuntu-keyring_2012.05.19 ubuntu-mono_14.04+15.10.20150813-0ubuntu1 ucf_3.0030 udev_224-2ubuntu2 util-linux_2.26.2-6ubuntu3 x11-common_1:7.7+7ubuntu4 x11proto-composite-dev_1:0.4.2-2 x11proto-core-dev_7.0.28-0ubuntu1 x11proto-damage-dev_1:1.2.1-2 x11proto-fixes-dev_1:5.0-2ubuntu2 x11proto-input-dev_2.3.1-1 x11proto-kb-dev_1.0.7-0ubuntu1 x11proto-randr-dev_1.5.0-1 x11proto-render-dev_2:0.11.1-2 x11proto-xext-dev_7.3.0-1 x11proto-xinerama-dev_1.2.1-2 xkb-data_2.12-1ubuntu1 xorg-sgml-doctools_1:1.11-1 xtrans-dev_1.3.5-1 xz-utils_5.1.1alpha+20120614-2ubuntu2 zlib1g_1:1.2.8.dfsg-2ubuntu1 zlib1g-dev_1:1.2.8.dfsg-2ubuntu1 ┌──────────────────────────────────────────────────────────────────────────────┐ │ Build │ └──────────────────────────────────────────────────────────────────────────────┘ Unpack source ───────────── gpgv: Signature made Tue May 19 05:58:59 2015 UTC using RSA key ID 588752A1 gpgv: Can't check signature: public key not found dpkg-source: warning: failed to verify signature on ./alarm-clock-applet_0.3.4-1.dsc dpkg-source: info: extracting alarm-clock-applet in alarm-clock-applet-0.3.4 dpkg-source: info: unpacking alarm-clock-applet_0.3.4.orig.tar.gz dpkg-source: info: unpacking alarm-clock-applet_0.3.4-1.debian.tar.xz Check disc space ──────────────── Sufficient free space for build User Environment ──────────────── DEB_BUILD_OPTIONS=parallel=4 HOME=/home/buildd LANG=C LOGNAME=buildd MAIL=/var/mail/buildd OLDPWD=/ PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games PWD=/«PKGBUILDDIR» SHELL=/bin/sh SUDO_COMMAND=/usr/sbin/chroot /«CHROOT» su buildd -s /bin/sh -c cd '/«PKGBUILDDIR»' && 'env' SUDO_GID=2501 SUDO_UID=2001 SUDO_USER=buildd TERM=unknown USER=buildd USERNAME=root dpkg-buildpackage ───────────────── dpkg-buildpackage: source package alarm-clock-applet dpkg-buildpackage: source version 0.3.4-1 dpkg-buildpackage: source distribution unstable dpkg-source --before-build alarm-clock-applet-0.3.4 dpkg-buildpackage: host architecture ppc64el fakeroot debian/rules clean dh clean dh_testdir dh_auto_clean dh_clean debian/rules build dh build dh_testdir debian/rules override_dh_auto_configure make[1]: Entering directory '/«PKGBUILDDIR»' dh_auto_configure -- \ --enable-appindicator ./configure --build=powerpc64le-linux-gnu --prefix=/usr --includedir=\${prefix}/include --mandir=\${prefix}/share/man --infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var --disable-silent-rules --libdir=\${prefix}/lib/powerpc64le-linux-gnu --libexecdir=\${prefix}/lib/powerpc64le-linux-gnu --disable-maintainer-mode --disable-dependency-tracking --enable-appindicator 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 make supports nested variables... yes checking whether to enable maintainer-specific portions of Makefiles... no checking whether make supports nested variables... (cached) yes 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 whether gcc understands -c and -o together... yes checking for style of include used by make... GNU checking dependency style of gcc... none checking whether to enable debugging... no checking whether gcc understands -Wall... yes checking whether gcc understands -Wstrict-prototypes... yes checking whether gcc understands -Wnested-externs... yes checking whether gcc understands -Werror=missing-prototypes... yes checking whether gcc understands -Werror=implicit-function-declaration... yes checking whether gcc understands -Werror=pointer-arith... yes checking whether gcc understands -Werror=init-self... yes checking whether gcc understands -Werror=format-security... yes checking whether gcc understands -Werror=format=2... yes checking whether gcc understands -Werror=missing-include-dirs... yes checking what warning flags to pass to the C compiler... -Wall -Wstrict-prototypes -Wnested-externs -Werror=missing-prototypes -Werror=implicit-function-declaration -Werror=pointer-arith -Werror=init-self -Werror=format-security -Werror=format=2 -Werror=missing-include-dirs 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 for LIBNOTIFY_0_7... yes checking for APP_INDICATOR... yes checking whether NLS is requested... yes checking for intltool >= 0.40.0... 0.51.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.20.2 checking for XML::Parser... ok checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking locale.h usability... yes checking locale.h presence... yes checking for locale.h... yes checking for LC_MESSAGES... yes checking libintl.h usability... yes checking libintl.h presence... yes checking for libintl.h... yes checking for ngettext in libc... yes checking for dgettext in libc... yes checking for bind_textdomain_codeset... yes checking for msgfmt... (cached) /usr/bin/msgfmt checking for dcgettext... yes checking if msgfmt accepts -c... yes checking for gmsgfmt... (cached) /usr/bin/msgfmt checking for xgettext... (cached) /usr/bin/xgettext checking that generated files are newer than configure... done 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.4 Configure summary: prefix: /usr source code location: . application indicators: yes ************************************************* make[1]: Leaving directory '/«PKGBUILDDIR»' dh_auto_build make -j1 make[1]: Entering directory '/«PKGBUILDDIR»' make all-recursive make[2]: Entering directory '/«PKGBUILDDIR»' Making all in src make[3]: Entering directory '/«PKGBUILDDIR»/src' Making all in tests make[4]: Entering directory '/«PKGBUILDDIR»/src/tests' make[4]: Nothing to be done for 'all'. make[4]: Leaving directory '/«PKGBUILDDIR»/src/tests' make[4]: Entering directory '/«PKGBUILDDIR»/src' gcc -DHAVE_CONFIG_H -I. -I.. -D_FORTIFY_SOURCE=2 -DALARM_CLOCK_DATADIR=\"/usr/share\" -DALARM_CLOCK_PKGDATADIR=\"/usr/share/alarm-clock-applet\" -pthread -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/powerpc64le-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -pthread -I/usr/include/gstreamer-1.0 -I/usr/lib/powerpc64le-linux-gnu/gstreamer-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -pthread -I/usr/include/gconf/2 -I/usr/include/dbus-1.0 -I/usr/lib/powerpc64le-linux-gnu/dbus-1.0/include -I/usr/include/libxml2 -I/usr/include/gtk-2.0 -I/usr/lib/powerpc64le-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -I/usr/include/unique-1.0 -pthread -I/usr/include/libappindicator-0.1 -I/usr/include/libdbusmenu-glib-0.4 -I/usr/include/gtk-2.0 -I/usr/lib/powerpc64le-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -Wall -Wstrict-prototypes -Wnested-externs -Werror=missing-prototypes -Werror=implicit-function-declaration -Werror=pointer-arith -Werror=init-self -Werror=format-security -Werror=format=2 -Werror=missing-include-dirs -g -O3 -fstack-protector-strong -Wformat -Werror=format-security -c -o alarm-applet.o alarm-applet.c In file included from /usr/include/gtk-2.0/gtk/gtk.h:234:0, from alarm-applet.h:32, from alarm-applet.c:26: /usr/include/gtk-2.0/gtk/gtkitemfactory.h:47:1: warning: function declaration isn't a prototype [-Wstrict-prototypes] typedef void (*GtkItemFactoryCallback) (); ^ gcc -DHAVE_CONFIG_H -I. -I.. -D_FORTIFY_SOURCE=2 -DALARM_CLOCK_DATADIR=\"/usr/share\" -DALARM_CLOCK_PKGDATADIR=\"/usr/share/alarm-clock-applet\" -pthread -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/powerpc64le-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -pthread -I/usr/include/gstreamer-1.0 -I/usr/lib/powerpc64le-linux-gnu/gstreamer-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -pthread -I/usr/include/gconf/2 -I/usr/include/dbus-1.0 -I/usr/lib/powerpc64le-linux-gnu/dbus-1.0/include -I/usr/include/libxml2 -I/usr/include/gtk-2.0 -I/usr/lib/powerpc64le-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -I/usr/include/unique-1.0 -pthread -I/usr/include/libappindicator-0.1 -I/usr/include/libdbusmenu-glib-0.4 -I/usr/include/gtk-2.0 -I/usr/lib/powerpc64le-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -Wall -Wstrict-prototypes -Wnested-externs -Werror=missing-prototypes -Werror=implicit-function-declaration -Werror=pointer-arith -Werror=init-self -Werror=format-security -Werror=format=2 -Werror=missing-include-dirs -g -O3 -fstack-protector-strong -Wformat -Werror=format-security -c -o player.o player.c gcc -DHAVE_CONFIG_H -I. -I.. -D_FORTIFY_SOURCE=2 -DALARM_CLOCK_DATADIR=\"/usr/share\" -DALARM_CLOCK_PKGDATADIR=\"/usr/share/alarm-clock-applet\" -pthread -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/powerpc64le-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -pthread -I/usr/include/gstreamer-1.0 -I/usr/lib/powerpc64le-linux-gnu/gstreamer-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -pthread -I/usr/include/gconf/2 -I/usr/include/dbus-1.0 -I/usr/lib/powerpc64le-linux-gnu/dbus-1.0/include -I/usr/include/libxml2 -I/usr/include/gtk-2.0 -I/usr/lib/powerpc64le-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -I/usr/include/unique-1.0 -pthread -I/usr/include/libappindicator-0.1 -I/usr/include/libdbusmenu-glib-0.4 -I/usr/include/gtk-2.0 -I/usr/lib/powerpc64le-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -Wall -Wstrict-prototypes -Wnested-externs -Werror=missing-prototypes -Werror=implicit-function-declaration -Werror=pointer-arith -Werror=init-self -Werror=format-security -Werror=format=2 -Werror=missing-include-dirs -g -O3 -fstack-protector-strong -Wformat -Werror=format-security -c -o util.o util.c gcc -DHAVE_CONFIG_H -I. -I.. -D_FORTIFY_SOURCE=2 -DALARM_CLOCK_DATADIR=\"/usr/share\" -DALARM_CLOCK_PKGDATADIR=\"/usr/share/alarm-clock-applet\" -pthread -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/powerpc64le-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -pthread -I/usr/include/gstreamer-1.0 -I/usr/lib/powerpc64le-linux-gnu/gstreamer-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -pthread -I/usr/include/gconf/2 -I/usr/include/dbus-1.0 -I/usr/lib/powerpc64le-linux-gnu/dbus-1.0/include -I/usr/include/libxml2 -I/usr/include/gtk-2.0 -I/usr/lib/powerpc64le-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -I/usr/include/unique-1.0 -pthread -I/usr/include/libappindicator-0.1 -I/usr/include/libdbusmenu-glib-0.4 -I/usr/include/gtk-2.0 -I/usr/lib/powerpc64le-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -Wall -Wstrict-prototypes -Wnested-externs -Werror=missing-prototypes -Werror=implicit-function-declaration -Werror=pointer-arith -Werror=init-self -Werror=format-security -Werror=format=2 -Werror=missing-include-dirs -g -O3 -fstack-protector-strong -Wformat -Werror=format-security -c -o list-entry.o list-entry.c In file included from /usr/include/gtk-2.0/gtk/gtk.h:234:0, from list-entry.c:26: /usr/include/gtk-2.0/gtk/gtkitemfactory.h:47:1: warning: function declaration isn't a prototype [-Wstrict-prototypes] typedef void (*GtkItemFactoryCallback) (); ^ gcc -DHAVE_CONFIG_H -I. -I.. -D_FORTIFY_SOURCE=2 -DALARM_CLOCK_DATADIR=\"/usr/share\" -DALARM_CLOCK_PKGDATADIR=\"/usr/share/alarm-clock-applet\" -pthread -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/powerpc64le-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -pthread -I/usr/include/gstreamer-1.0 -I/usr/lib/powerpc64le-linux-gnu/gstreamer-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -pthread -I/usr/include/gconf/2 -I/usr/include/dbus-1.0 -I/usr/lib/powerpc64le-linux-gnu/dbus-1.0/include -I/usr/include/libxml2 -I/usr/include/gtk-2.0 -I/usr/lib/powerpc64le-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -I/usr/include/unique-1.0 -pthread -I/usr/include/libappindicator-0.1 -I/usr/include/libdbusmenu-glib-0.4 -I/usr/include/gtk-2.0 -I/usr/lib/powerpc64le-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -Wall -Wstrict-prototypes -Wnested-externs -Werror=missing-prototypes -Werror=implicit-function-declaration -Werror=pointer-arith -Werror=init-self -Werror=format-security -Werror=format=2 -Werror=missing-include-dirs -g -O3 -fstack-protector-strong -Wformat -Werror=format-security -c -o alarm.o alarm.c alarm.c: In function 'alarm_repeat_to_pretty': alarm.c:2008:9: warning: case value '62' not in enumerated type 'AlarmRepeat {aka enum }' [-Wswitch] case ALARM_REPEAT_WEEKDAYS: ^ alarm.c:2011:9: warning: case value '65' not in enumerated type 'AlarmRepeat {aka enum }' [-Wswitch] case ALARM_REPEAT_WEEKENDS: ^ alarm.c:2014:9: warning: case value '127' not in enumerated type 'AlarmRepeat {aka enum }' [-Wswitch] case ALARM_REPEAT_ALL: ^ gcc -DHAVE_CONFIG_H -I. -I.. -D_FORTIFY_SOURCE=2 -DALARM_CLOCK_DATADIR=\"/usr/share\" -DALARM_CLOCK_PKGDATADIR=\"/usr/share/alarm-clock-applet\" -pthread -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/powerpc64le-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -pthread -I/usr/include/gstreamer-1.0 -I/usr/lib/powerpc64le-linux-gnu/gstreamer-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -pthread -I/usr/include/gconf/2 -I/usr/include/dbus-1.0 -I/usr/lib/powerpc64le-linux-gnu/dbus-1.0/include -I/usr/include/libxml2 -I/usr/include/gtk-2.0 -I/usr/lib/powerpc64le-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -I/usr/include/unique-1.0 -pthread -I/usr/include/libappindicator-0.1 -I/usr/include/libdbusmenu-glib-0.4 -I/usr/include/gtk-2.0 -I/usr/lib/powerpc64le-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -Wall -Wstrict-prototypes -Wnested-externs -Werror=missing-prototypes -Werror=implicit-function-declaration -Werror=pointer-arith -Werror=init-self -Werror=format-security -Werror=format=2 -Werror=missing-include-dirs -g -O3 -fstack-protector-strong -Wformat -Werror=format-security -c -o alarm-gconf.o alarm-gconf.c In file included from /usr/include/gtk-2.0/gtk/gtk.h:234:0, from alarm-applet.h:32, from alarm-gconf.c:26: /usr/include/gtk-2.0/gtk/gtkitemfactory.h:47:1: warning: function declaration isn't a prototype [-Wstrict-prototypes] typedef void (*GtkItemFactoryCallback) (); ^ gcc -DHAVE_CONFIG_H -I. -I.. -D_FORTIFY_SOURCE=2 -DALARM_CLOCK_DATADIR=\"/usr/share\" -DALARM_CLOCK_PKGDATADIR=\"/usr/share/alarm-clock-applet\" -pthread -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/powerpc64le-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -pthread -I/usr/include/gstreamer-1.0 -I/usr/lib/powerpc64le-linux-gnu/gstreamer-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -pthread -I/usr/include/gconf/2 -I/usr/include/dbus-1.0 -I/usr/lib/powerpc64le-linux-gnu/dbus-1.0/include -I/usr/include/libxml2 -I/usr/include/gtk-2.0 -I/usr/lib/powerpc64le-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -I/usr/include/unique-1.0 -pthread -I/usr/include/libappindicator-0.1 -I/usr/include/libdbusmenu-glib-0.4 -I/usr/include/gtk-2.0 -I/usr/lib/powerpc64le-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -Wall -Wstrict-prototypes -Wnested-externs -Werror=missing-prototypes -Werror=implicit-function-declaration -Werror=pointer-arith -Werror=init-self -Werror=format-security -Werror=format=2 -Werror=missing-include-dirs -g -O3 -fstack-protector-strong -Wformat -Werror=format-security -c -o ui.o ui.c In file included from /usr/include/gtk-2.0/gtk/gtk.h:234:0, from alarm-applet.h:32, from ui.c:28: /usr/include/gtk-2.0/gtk/gtkitemfactory.h:47:1: warning: function declaration isn't a prototype [-Wstrict-prototypes] typedef void (*GtkItemFactoryCallback) (); ^ gcc -DHAVE_CONFIG_H -I. -I.. -D_FORTIFY_SOURCE=2 -DALARM_CLOCK_DATADIR=\"/usr/share\" -DALARM_CLOCK_PKGDATADIR=\"/usr/share/alarm-clock-applet\" -pthread -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/powerpc64le-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -pthread -I/usr/include/gstreamer-1.0 -I/usr/lib/powerpc64le-linux-gnu/gstreamer-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -pthread -I/usr/include/gconf/2 -I/usr/include/dbus-1.0 -I/usr/lib/powerpc64le-linux-gnu/dbus-1.0/include -I/usr/include/libxml2 -I/usr/include/gtk-2.0 -I/usr/lib/powerpc64le-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -I/usr/include/unique-1.0 -pthread -I/usr/include/libappindicator-0.1 -I/usr/include/libdbusmenu-glib-0.4 -I/usr/include/gtk-2.0 -I/usr/lib/powerpc64le-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -Wall -Wstrict-prototypes -Wnested-externs -Werror=missing-prototypes -Werror=implicit-function-declaration -Werror=pointer-arith -Werror=init-self -Werror=format-security -Werror=format=2 -Werror=missing-include-dirs -g -O3 -fstack-protector-strong -Wformat -Werror=format-security -c -o alarm-actions.o alarm-actions.c In file included from /usr/include/gtk-2.0/gtk/gtk.h:234:0, from alarm-applet.h:32, from alarm-actions.h:28, from alarm-actions.c:24: /usr/include/gtk-2.0/gtk/gtkitemfactory.h:47:1: warning: function declaration isn't a prototype [-Wstrict-prototypes] typedef void (*GtkItemFactoryCallback) (); ^ gcc -DHAVE_CONFIG_H -I. -I.. -D_FORTIFY_SOURCE=2 -DALARM_CLOCK_DATADIR=\"/usr/share\" -DALARM_CLOCK_PKGDATADIR=\"/usr/share/alarm-clock-applet\" -pthread -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/powerpc64le-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -pthread -I/usr/include/gstreamer-1.0 -I/usr/lib/powerpc64le-linux-gnu/gstreamer-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -pthread -I/usr/include/gconf/2 -I/usr/include/dbus-1.0 -I/usr/lib/powerpc64le-linux-gnu/dbus-1.0/include -I/usr/include/libxml2 -I/usr/include/gtk-2.0 -I/usr/lib/powerpc64le-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -I/usr/include/unique-1.0 -pthread -I/usr/include/libappindicator-0.1 -I/usr/include/libdbusmenu-glib-0.4 -I/usr/include/gtk-2.0 -I/usr/lib/powerpc64le-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -Wall -Wstrict-prototypes -Wnested-externs -Werror=missing-prototypes -Werror=implicit-function-declaration -Werror=pointer-arith -Werror=init-self -Werror=format-security -Werror=format=2 -Werror=missing-include-dirs -g -O3 -fstack-protector-strong -Wformat -Werror=format-security -c -o alarm-list-window.o alarm-list-window.c In file included from /usr/include/gtk-2.0/gtk/gtk.h:234:0, from alarm-list-window.h:27, from alarm-list-window.c:26: /usr/include/gtk-2.0/gtk/gtkitemfactory.h:47:1: warning: function declaration isn't a prototype [-Wstrict-prototypes] typedef void (*GtkItemFactoryCallback) (); ^ gcc -DHAVE_CONFIG_H -I. -I.. -D_FORTIFY_SOURCE=2 -DALARM_CLOCK_DATADIR=\"/usr/share\" -DALARM_CLOCK_PKGDATADIR=\"/usr/share/alarm-clock-applet\" -pthread -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/powerpc64le-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -pthread -I/usr/include/gstreamer-1.0 -I/usr/lib/powerpc64le-linux-gnu/gstreamer-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -pthread -I/usr/include/gconf/2 -I/usr/include/dbus-1.0 -I/usr/lib/powerpc64le-linux-gnu/dbus-1.0/include -I/usr/include/libxml2 -I/usr/include/gtk-2.0 -I/usr/lib/powerpc64le-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -I/usr/include/unique-1.0 -pthread -I/usr/include/libappindicator-0.1 -I/usr/include/libdbusmenu-glib-0.4 -I/usr/include/gtk-2.0 -I/usr/lib/powerpc64le-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -Wall -Wstrict-prototypes -Wnested-externs -Werror=missing-prototypes -Werror=implicit-function-declaration -Werror=pointer-arith -Werror=init-self -Werror=format-security -Werror=format=2 -Werror=missing-include-dirs -g -O3 -fstack-protector-strong -Wformat -Werror=format-security -c -o alarm-settings.o alarm-settings.c In file included from /usr/include/gtk-2.0/gtk/gtk.h:234:0, from alarm-applet.h:32, from alarm-settings.h:32, from alarm-settings.c:24: /usr/include/gtk-2.0/gtk/gtkitemfactory.h:47:1: warning: function declaration isn't a prototype [-Wstrict-prototypes] typedef void (*GtkItemFactoryCallback) (); ^ gcc -DHAVE_CONFIG_H -I. -I.. -D_FORTIFY_SOURCE=2 -DALARM_CLOCK_DATADIR=\"/usr/share\" -DALARM_CLOCK_PKGDATADIR=\"/usr/share/alarm-clock-applet\" -pthread -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/powerpc64le-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -pthread -I/usr/include/gstreamer-1.0 -I/usr/lib/powerpc64le-linux-gnu/gstreamer-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -pthread -I/usr/include/gconf/2 -I/usr/include/dbus-1.0 -I/usr/lib/powerpc64le-linux-gnu/dbus-1.0/include -I/usr/include/libxml2 -I/usr/include/gtk-2.0 -I/usr/lib/powerpc64le-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -I/usr/include/unique-1.0 -pthread -I/usr/include/libappindicator-0.1 -I/usr/include/libdbusmenu-glib-0.4 -I/usr/include/gtk-2.0 -I/usr/lib/powerpc64le-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -Wall -Wstrict-prototypes -Wnested-externs -Werror=missing-prototypes -Werror=implicit-function-declaration -Werror=pointer-arith -Werror=init-self -Werror=format-security -Werror=format=2 -Werror=missing-include-dirs -g -O3 -fstack-protector-strong -Wformat -Werror=format-security -c -o prefs.o prefs.c In file included from /usr/include/gtk-2.0/gtk/gtk.h:234:0, from alarm-applet.h:32, from prefs.h:27, from prefs.c:28: /usr/include/gtk-2.0/gtk/gtkitemfactory.h:47:1: warning: function declaration isn't a prototype [-Wstrict-prototypes] typedef void (*GtkItemFactoryCallback) (); ^ prefs.c:129:1: warning: function declaration isn't a prototype [-Wstrict-prototypes] prefs_autostart_get_current () ^ prefs.c:219:1: warning: function declaration isn't a prototype [-Wstrict-prototypes] prefs_create_autostart_user_file() ^ gcc -DALARM_CLOCK_DATADIR=\"/usr/share\" -DALARM_CLOCK_PKGDATADIR=\"/usr/share/alarm-clock-applet\" -pthread -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/powerpc64le-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -pthread -I/usr/include/gstreamer-1.0 -I/usr/lib/powerpc64le-linux-gnu/gstreamer-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -pthread -I/usr/include/gconf/2 -I/usr/include/dbus-1.0 -I/usr/lib/powerpc64le-linux-gnu/dbus-1.0/include -I/usr/include/libxml2 -I/usr/include/gtk-2.0 -I/usr/lib/powerpc64le-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -I/usr/include/unique-1.0 -pthread -I/usr/include/libappindicator-0.1 -I/usr/include/libdbusmenu-glib-0.4 -I/usr/include/gtk-2.0 -I/usr/lib/powerpc64le-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -Wall -Wstrict-prototypes -Wnested-externs -Werror=missing-prototypes -Werror=implicit-function-declaration -Werror=pointer-arith -Werror=init-self -Werror=format-security -Werror=format=2 -Werror=missing-include-dirs -g -O3 -fstack-protector-strong -Wformat -Werror=format-security -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--as-needed -Wl,-z,defs -o alarm-clock-applet alarm-applet.o player.o util.o list-entry.o alarm.o alarm-gconf.o ui.o alarm-actions.o alarm-list-window.o alarm-settings.o prefs.o -Wl,--export-dynamic -lgmodule-2.0 -pthread -lglib-2.0 -lgtk-x11-2.0 -lgdk-x11-2.0 -lpangocairo-1.0 -latk-1.0 -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lpangoft2-1.0 -lpango-1.0 -lgobject-2.0 -lglib-2.0 -lfontconfig -lfreetype -lgstreamer-1.0 -lgobject-2.0 -lglib-2.0 -lgconf-2 -lnotify -lxml2 -lunique-1.0 -lgtk-x11-2.0 -lgdk-x11-2.0 -lpangocairo-1.0 -latk-1.0 -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lpangoft2-1.0 -lpango-1.0 -lgobject-2.0 -lglib-2.0 -lfontconfig -lfreetype -lappindicator -ldbusmenu-glib -lgtk-x11-2.0 -lgdk-x11-2.0 -lpangocairo-1.0 -latk-1.0 -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lpangoft2-1.0 -lpango-1.0 -lgobject-2.0 -lglib-2.0 -lfontconfig -lfreetype make[4]: Leaving directory '/«PKGBUILDDIR»/src' make[3]: Leaving directory '/«PKGBUILDDIR»/src' Making all in data make[3]: Entering directory '/«PKGBUILDDIR»/data' Making all in icons make[4]: Entering directory '/«PKGBUILDDIR»/data/icons' make[4]: Nothing to be done for 'all'. make[4]: Leaving directory '/«PKGBUILDDIR»/data/icons' make[4]: Entering directory '/«PKGBUILDDIR»/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 '/«PKGBUILDDIR»/data' make[3]: Leaving directory '/«PKGBUILDDIR»/data' Making all in po make[3]: Entering directory '/«PKGBUILDDIR»/po' file=`echo ar | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file ar.po file=`echo ast | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file ast.po file=`echo be | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file be.po file=`echo bg | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file bg.po file=`echo ca | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file ca.po file=`echo cs | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file cs.po file=`echo da | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file da.po file=`echo de | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file de.po file=`echo es | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file es.po file=`echo et | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file et.po file=`echo 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 it | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file it.po file=`echo ja | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file ja.po file=`echo ka | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file ka.po file=`echo la | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file la.po file=`echo ms | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file ms.po file=`echo nb | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file nb.po file=`echo nl | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file nl.po file=`echo 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 si | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file si.po file=`echo sv | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file sv.po file=`echo tr | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file tr.po file=`echo uk | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file uk.po file=`echo zh_CN | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file zh_CN.po file=`echo zh_TW | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file zh_TW.po make[3]: Leaving directory '/«PKGBUILDDIR»/po' make[3]: Entering directory '/«PKGBUILDDIR»' make[3]: Nothing to be done for 'all-am'. make[3]: Leaving directory '/«PKGBUILDDIR»' make[2]: Leaving directory '/«PKGBUILDDIR»' make[1]: Leaving directory '/«PKGBUILDDIR»' fakeroot debian/rules binary dh binary dh_testroot dh_prep dh_auto_install make -j1 install DESTDIR=/«PKGBUILDDIR»/debian/alarm-clock-applet AM_UPDATE_INFO_DIR=no make[1]: Entering directory '/«PKGBUILDDIR»' Making install in src make[2]: Entering directory '/«PKGBUILDDIR»/src' Making install in tests make[3]: Entering directory '/«PKGBUILDDIR»/src/tests' make[4]: Entering directory '/«PKGBUILDDIR»/src/tests' make[4]: Nothing to be done for 'install-exec-am'. make[4]: Nothing to be done for 'install-data-am'. make[4]: Leaving directory '/«PKGBUILDDIR»/src/tests' make[3]: Leaving directory '/«PKGBUILDDIR»/src/tests' make[3]: Entering directory '/«PKGBUILDDIR»/src' make[4]: Entering directory '/«PKGBUILDDIR»/src' /bin/mkdir -p '/«PKGBUILDDIR»/debian/alarm-clock-applet/usr/bin' /usr/bin/install -c alarm-clock-applet '/«PKGBUILDDIR»/debian/alarm-clock-applet/usr/bin' make[4]: Nothing to be done for 'install-data-am'. make[4]: Leaving directory '/«PKGBUILDDIR»/src' make[3]: Leaving directory '/«PKGBUILDDIR»/src' make[2]: Leaving directory '/«PKGBUILDDIR»/src' Making install in data make[2]: Entering directory '/«PKGBUILDDIR»/data' Making install in icons make[3]: Entering directory '/«PKGBUILDDIR»/data/icons' make[4]: Entering directory '/«PKGBUILDDIR»/data/icons' make[4]: 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-clock-triggered.16.png alarm-clock-triggered.22.png alarm-clock-triggered.24.png alarm-clock-triggered.32.png alarm-clock-triggered.36.png alarm-clock-triggered.48.png alarm-clock-triggered.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 /«PKGBUILDDIR»/debian/alarm-clock-applet/usr/share/icons/hicolor/$SIZE/apps/; \ /usr/bin/install -c -m 644 ./$icon /«PKGBUILDDIR»/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[4]: Leaving directory '/«PKGBUILDDIR»/data/icons' make[3]: Leaving directory '/«PKGBUILDDIR»/data/icons' make[3]: Entering directory '/«PKGBUILDDIR»/data' make[4]: Entering directory '/«PKGBUILDDIR»/data' make[4]: 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:7610): GConf-WARNING **: Client failed to connect to the D-BUS daemon: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11 Attached schema `/schemas/apps/alarm-clock/show_label' to key `/apps/alarm-clock/show_label' WARNING: failed to install schema `/schemas/apps/alarm-clock/show_label', locale `de': Unable to store a value at key '/schemas/apps/alarm-clock/show_label', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and 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/show_label', locale `ms': Unable to store a value at key '/schemas/apps/alarm-clock/show_label', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and 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/show_label', locale `pl': Unable to store a value at key '/schemas/apps/alarm-clock/show_label', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and 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/show_label', locale `pt_BR': Unable to store a value at key '/schemas/apps/alarm-clock/show_label', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and 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/show_label', locale `zh_CN': Unable to store a value at key '/schemas/apps/alarm-clock/show_label', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and 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/show_label', locale `si': Unable to store a value at key '/schemas/apps/alarm-clock/show_label', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and 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/show_label', locale `he': Unable to store a value at key '/schemas/apps/alarm-clock/show_label', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and 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/show_label', locale `C': Unable to store a value at key '/schemas/apps/alarm-clock/show_label', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and 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/show_label', locale `ast': Unable to store a value at key '/schemas/apps/alarm-clock/show_label', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and 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/show_label', locale `ka': Unable to store a value at key '/schemas/apps/alarm-clock/show_label', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and 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/show_label', locale `uk': Unable to store a value at key '/schemas/apps/alarm-clock/show_label', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and 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/show_label', locale `gl': Unable to store a value at key '/schemas/apps/alarm-clock/show_label', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and 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/show_label', locale `ru': Unable to store a value at key '/schemas/apps/alarm-clock/show_label', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and 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/show_label', locale `tr': Unable to store a value at key '/schemas/apps/alarm-clock/show_label', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and 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/show_label', locale `es': Unable to store a value at key '/schemas/apps/alarm-clock/show_label', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and 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/show_label', locale `fr': Unable to store a value at key '/schemas/apps/alarm-clock/show_label', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and 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/show_label', locale `nb': Unable to store a value at key '/schemas/apps/alarm-clock/show_label', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and 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/show_label', locale `sv': Unable to store a value at key '/schemas/apps/alarm-clock/show_label', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and 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/show_label', locale `zh_TW': Unable to store a value at key '/schemas/apps/alarm-clock/show_label', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and 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/show_label', locale `hu': Unable to store a value at key '/schemas/apps/alarm-clock/show_label', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and 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/show_label', locale `nl': Unable to store a value at key '/schemas/apps/alarm-clock/show_label', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and 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/show_label', locale `bg': Unable to store a value at key '/schemas/apps/alarm-clock/show_label', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and 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 `si': 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 `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 `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 `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 `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 `uk': 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 `sv': 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 `ca': 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 `nl': 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_TW': 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 `ar': 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 `ast': 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 `cs': 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 `ka': 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/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 `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 `et': 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 `tr': 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 `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 `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 `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 `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 `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 `fi': 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 `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 `si': 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 `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 `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 `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 `uk': 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 `fr': 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 `sv': 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 `ca': 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 `hu': 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 `nl': 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_TW': 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 `ar': 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 `pl': 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 `ast': 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 `ka': 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 `gl': 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 `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/timestamp', locale `tr': 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 `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 `bg': 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 `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 `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 `fi': 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 `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 `si': 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 `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 `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 `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 `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 `uk': 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 `sv': 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 `ca': 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 `nl': 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_TW': 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 `ar': 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 `ast': 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 `cs': 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 `ka': 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/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 `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 `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 `tr': 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 `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 `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 `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 `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 `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 `fi': 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 `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 `si': 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 `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 `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 `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 `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 `uk': 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 `sv': 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 `ca': 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 `nl': 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_TW': 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 `ar': 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 `ast': 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 `cs': 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 `ka': 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/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 `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 `et': 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 `tr': 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 `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 `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 `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 `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 `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 `fi': 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 `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 `si': 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 `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 `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 `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 `uk': 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 `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 `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 `sv': 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 `ca': 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 `hu': 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 `nl': 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_TW': 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 `ar': 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 `pl': 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 `ast': 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 `ka': 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 `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 `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 `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/active', locale `tr': 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 `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 `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 `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 `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 `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 `fi': 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 `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 `si': 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 `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 `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 `uk': 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 `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 `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 `sv': 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 `ca': 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 `nl': 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_TW': 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 `ar': 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 `ast': 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 `cs': 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 `ka': 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/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 `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 `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 `tr': 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 `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 `bg': 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 `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 `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 `fi': 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 `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 `si': 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 `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 `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 `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 `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 `uk': 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 `sv': 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 `ca': 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 `hu': 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 `nl': 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_TW': 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 `ar': 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 `ast': 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 `cs': 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 `ka': 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 `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 `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 `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/notify_type', locale `tr': 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 `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 `bg': 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 `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 `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 `fi': 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 `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 `si': 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 `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 `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 `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 `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 `uk': 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 `sv': 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 `ca': 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 `nl': 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_TW': 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 `ar': 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 `ast': 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 `cs': 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 `ka': 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_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 `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 `et': 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 `tr': 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 `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 `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 `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 `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 `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 `fi': 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 `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 `si': 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 `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 `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 `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 `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 `uk': 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 `sv': 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 `ca': 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 `hu': 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 `nl': 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_TW': 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 `ar': 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 `ast': 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 `cs': 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 `ka': 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 `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 `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 `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/sound_repeat', locale `tr': 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 `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 `bg': 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 `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 `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 `fi': 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 `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 `si': 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 `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 `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 `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 `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 `uk': 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 `sv': 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 `ca': 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 `nl': 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_TW': 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 `ar': 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 `ast': 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 `cs': 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 `ka': 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 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 `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 `et': 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 `tr': 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 `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 `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 `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 `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 `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 `fi': 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 /bin/mkdir -p '/«PKGBUILDDIR»/debian/alarm-clock-applet/usr/share/applications' /usr/bin/install -c -m 644 alarm-clock-applet.desktop '/«PKGBUILDDIR»/debian/alarm-clock-applet/usr/share/applications' /bin/mkdir -p '/«PKGBUILDDIR»/debian/alarm-clock-applet/etc/gconf/schemas' /usr/bin/install -c -m 644 alarm-clock.schemas '/«PKGBUILDDIR»/debian/alarm-clock-applet/etc/gconf/schemas' /bin/mkdir -p '/«PKGBUILDDIR»/debian/alarm-clock-applet/usr/share/alarm-clock-applet' /usr/bin/install -c -m 644 alarm-clock.ui '/«PKGBUILDDIR»/debian/alarm-clock-applet/usr/share/alarm-clock-applet' make[4]: Leaving directory '/«PKGBUILDDIR»/data' make[3]: Leaving directory '/«PKGBUILDDIR»/data' make[2]: Leaving directory '/«PKGBUILDDIR»/data' Making install in po make[2]: Entering directory '/«PKGBUILDDIR»/po' linguas="ar ast be bg ca cs da de es et fi fo fr gl he hi hu id it ja ka la ms nb nl nn pl pt_BR pt ru si sv tr uk zh_CN zh_TW "; \ for lang in $linguas; do \ dir=/«PKGBUILDDIR»/debian/alarm-clock-applet/usr/share/locale/$lang/LC_MESSAGES; \ /bin/bash /«PKGBUILDDIR»/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 /«PKGBUILDDIR»/debian/alarm-clock-applet/usr/share/locale/ar/LC_MESSAGES/alarm-clock-applet.mo installing ast.gmo as /«PKGBUILDDIR»/debian/alarm-clock-applet/usr/share/locale/ast/LC_MESSAGES/alarm-clock-applet.mo installing be.gmo as /«PKGBUILDDIR»/debian/alarm-clock-applet/usr/share/locale/be/LC_MESSAGES/alarm-clock-applet.mo installing bg.gmo as /«PKGBUILDDIR»/debian/alarm-clock-applet/usr/share/locale/bg/LC_MESSAGES/alarm-clock-applet.mo installing ca.gmo as /«PKGBUILDDIR»/debian/alarm-clock-applet/usr/share/locale/ca/LC_MESSAGES/alarm-clock-applet.mo installing cs.gmo as /«PKGBUILDDIR»/debian/alarm-clock-applet/usr/share/locale/cs/LC_MESSAGES/alarm-clock-applet.mo installing da.gmo as /«PKGBUILDDIR»/debian/alarm-clock-applet/usr/share/locale/da/LC_MESSAGES/alarm-clock-applet.mo installing de.gmo as /«PKGBUILDDIR»/debian/alarm-clock-applet/usr/share/locale/de/LC_MESSAGES/alarm-clock-applet.mo installing es.gmo as /«PKGBUILDDIR»/debian/alarm-clock-applet/usr/share/locale/es/LC_MESSAGES/alarm-clock-applet.mo installing et.gmo as /«PKGBUILDDIR»/debian/alarm-clock-applet/usr/share/locale/et/LC_MESSAGES/alarm-clock-applet.mo installing fi.gmo as /«PKGBUILDDIR»/debian/alarm-clock-applet/usr/share/locale/fi/LC_MESSAGES/alarm-clock-applet.mo installing fo.gmo as /«PKGBUILDDIR»/debian/alarm-clock-applet/usr/share/locale/fo/LC_MESSAGES/alarm-clock-applet.mo installing fr.gmo as /«PKGBUILDDIR»/debian/alarm-clock-applet/usr/share/locale/fr/LC_MESSAGES/alarm-clock-applet.mo installing gl.gmo as /«PKGBUILDDIR»/debian/alarm-clock-applet/usr/share/locale/gl/LC_MESSAGES/alarm-clock-applet.mo installing he.gmo as /«PKGBUILDDIR»/debian/alarm-clock-applet/usr/share/locale/he/LC_MESSAGES/alarm-clock-applet.mo installing hi.gmo as /«PKGBUILDDIR»/debian/alarm-clock-applet/usr/share/locale/hi/LC_MESSAGES/alarm-clock-applet.mo installing hu.gmo as /«PKGBUILDDIR»/debian/alarm-clock-applet/usr/share/locale/hu/LC_MESSAGES/alarm-clock-applet.mo installing id.gmo as /«PKGBUILDDIR»/debian/alarm-clock-applet/usr/share/locale/id/LC_MESSAGES/alarm-clock-applet.mo installing it.gmo as /«PKGBUILDDIR»/debian/alarm-clock-applet/usr/share/locale/it/LC_MESSAGES/alarm-clock-applet.mo installing ja.gmo as /«PKGBUILDDIR»/debian/alarm-clock-applet/usr/share/locale/ja/LC_MESSAGES/alarm-clock-applet.mo installing ka.gmo as /«PKGBUILDDIR»/debian/alarm-clock-applet/usr/share/locale/ka/LC_MESSAGES/alarm-clock-applet.mo installing la.gmo as /«PKGBUILDDIR»/debian/alarm-clock-applet/usr/share/locale/la/LC_MESSAGES/alarm-clock-applet.mo installing ms.gmo as /«PKGBUILDDIR»/debian/alarm-clock-applet/usr/share/locale/ms/LC_MESSAGES/alarm-clock-applet.mo installing nb.gmo as /«PKGBUILDDIR»/debian/alarm-clock-applet/usr/share/locale/nb/LC_MESSAGES/alarm-clock-applet.mo installing nl.gmo as /«PKGBUILDDIR»/debian/alarm-clock-applet/usr/share/locale/nl/LC_MESSAGES/alarm-clock-applet.mo installing nn.gmo as /«PKGBUILDDIR»/debian/alarm-clock-applet/usr/share/locale/nn/LC_MESSAGES/alarm-clock-applet.mo installing pl.gmo as /«PKGBUILDDIR»/debian/alarm-clock-applet/usr/share/locale/pl/LC_MESSAGES/alarm-clock-applet.mo installing pt_BR.gmo as /«PKGBUILDDIR»/debian/alarm-clock-applet/usr/share/locale/pt_BR/LC_MESSAGES/alarm-clock-applet.mo installing pt.gmo as /«PKGBUILDDIR»/debian/alarm-clock-applet/usr/share/locale/pt/LC_MESSAGES/alarm-clock-applet.mo installing ru.gmo as /«PKGBUILDDIR»/debian/alarm-clock-applet/usr/share/locale/ru/LC_MESSAGES/alarm-clock-applet.mo installing si.gmo as /«PKGBUILDDIR»/debian/alarm-clock-applet/usr/share/locale/si/LC_MESSAGES/alarm-clock-applet.mo installing sv.gmo as /«PKGBUILDDIR»/debian/alarm-clock-applet/usr/share/locale/sv/LC_MESSAGES/alarm-clock-applet.mo installing tr.gmo as /«PKGBUILDDIR»/debian/alarm-clock-applet/usr/share/locale/tr/LC_MESSAGES/alarm-clock-applet.mo installing uk.gmo as /«PKGBUILDDIR»/debian/alarm-clock-applet/usr/share/locale/uk/LC_MESSAGES/alarm-clock-applet.mo installing zh_CN.gmo as /«PKGBUILDDIR»/debian/alarm-clock-applet/usr/share/locale/zh_CN/LC_MESSAGES/alarm-clock-applet.mo installing zh_TW.gmo as /«PKGBUILDDIR»/debian/alarm-clock-applet/usr/share/locale/zh_TW/LC_MESSAGES/alarm-clock-applet.mo make[2]: Leaving directory '/«PKGBUILDDIR»/po' make[2]: Entering directory '/«PKGBUILDDIR»' make[3]: Entering directory '/«PKGBUILDDIR»' make[3]: Nothing to be done for 'install-exec-am'. make[3]: Nothing to be done for 'install-data-am'. make[3]: Leaving directory '/«PKGBUILDDIR»' make[2]: Leaving directory '/«PKGBUILDDIR»' make[1]: Leaving directory '/«PKGBUILDDIR»' debian/rules override_dh_install make[1]: Entering directory '/«PKGBUILDDIR»' awk '/^Exec=/ { $0 = $0 " --hidden"; } {print;}' \ debian/alarm-clock-applet/usr/share/applications/alarm-clock-applet.desktop > debian/alarm-clock-applet.desktop dh_install make[1]: Leaving directory '/«PKGBUILDDIR»' dh_installdocs debian/rules override_dh_installchangelogs make[1]: Entering directory '/«PKGBUILDDIR»' dh_installchangelogs ChangeLog make[1]: Leaving directory '/«PKGBUILDDIR»' dh_installman dh_gconf dh_icons dh_perl dh_link dh_compress dh_fixperms dh_strip dh_strip debug symbol extraction: not enabling -a because /CurrentlyBuilding exists dh_strip debug symbol extraction: all non-arch-all packages for this build platform ppc64el: alarm-clock-applet dh_strip debug symbol extraction: packages to act on: alarm-clock-applet dh_strip debug symbol extraction: ignored packages: Using buildid for compat level >= 9 dpkg-gencontrol: warning: -is is deprecated; it is without effect dpkg-gencontrol: warning: -ip is deprecated; it is without effect dpkg-gencontrol: warning: File::FcntlLock not available; using flock which is not NFS-safe dpkg-gencontrol: warning: package alarm-clock-applet: unused substitution variable ${misc:Depends} /usr/bin/pkg_create_dbgsym: deferring build of .ddeb to dh_gencontrol dh_makeshlibs dh_shlibdeps dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/alarm-clock-applet/usr/bin/alarm-clock-applet was not linked against libpthread.so.0 (it uses none of the library's symbols) dh_installdeb dh_gencontrol dpkg-gencontrol: warning: File::FcntlLock not available; using flock which is not NFS-safe dh_gencontrol debug symbol wrapper: all non-arch-all packages for this build platform ppc64el: alarm-clock-applet dh_gencontrol debug symbol wrapper: packages to act on: alarm-clock-applet dh_gencontrol debug symbol wrapper: ignored packages: dh_gencontrol debug symbol wrapper: processing package alarm-clock-applet (pkgdir debian/alarm-clock-applet, ddeb package dir debian/alarm-clock-applet-dbgsym) dh_gencontrol debug symbol wrapper: building alarm-clock-applet-dbgsym_0.3.4-1_ppc64el.ddeb dpkg-deb: building package 'alarm-clock-applet-dbgsym' in '../alarm-clock-applet-dbgsym_0.3.4-1_ppc64el.ddeb'. dh_md5sums dh_builddeb INFO: pkgstriptranslations version 121 pkgstriptranslations: processing alarm-clock-applet (in debian/alarm-clock-applet); do_strip: , oemstrip: debian/alarm-clock-applet/etc/xdg/autostart/alarm-clock-applet.desktop: stripping translations debian/alarm-clock-applet/usr/share/applications/alarm-clock-applet.desktop: stripping translations pkgmaintainermangler: Maintainer field overridden to "Ubuntu Developers " pkgstripfiles: processing control file: debian/alarm-clock-applet/DEBIAN/control, package alarm-clock-applet, directory debian/alarm-clock-applet .. removing usr/share/doc/alarm-clock-applet/changelog.gz pkgstripfiles: Truncating usr/share/doc/alarm-clock-applet/changelog.Debian.gz to topmost ten records ** Processing: ./usr/share/icons/hicolor/48x48/apps/alarm-clock-triggered.png 48x48 pixels, 4x8 bits/pixel, RGB+alpha Input IDAT size = 5227 bytes Input file size = 5358 bytes Trying: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 4932 zc = 9 zm = 8 zs = 1 f = 0 zc = 1 zm = 8 zs = 2 f = 0 zc = 9 zm = 8 zs = 3 f = 0 zc = 9 zm = 8 zs = 0 f = 1 zc = 9 zm = 8 zs = 1 f = 1 zc = 1 zm = 8 zs = 2 f = 1 zc = 9 zm = 8 zs = 3 f = 1 zc = 9 zm = 8 zs = 0 f = 2 IDAT size = 4807 zc = 9 zm = 8 zs = 1 f = 2 zc = 1 zm = 8 zs = 2 f = 2 zc = 9 zm = 8 zs = 3 f = 2 zc = 9 zm = 8 zs = 0 f = 3 zc = 9 zm = 8 zs = 1 f = 3 zc = 1 zm = 8 zs = 2 f = 3 zc = 9 zm = 8 zs = 3 f = 3 zc = 9 zm = 8 zs = 0 f = 4 zc = 9 zm = 8 zs = 1 f = 4 zc = 1 zm = 8 zs = 2 f = 4 zc = 9 zm = 8 zs = 3 f = 4 zc = 9 zm = 8 zs = 0 f = 5 zc = 9 zm = 8 zs = 1 f = 5 zc = 1 zm = 8 zs = 2 f = 5 zc = 9 zm = 8 zs = 3 f = 5 Selecting parameters: zc = 9 zm = 8 zs = 0 f = 2 IDAT size = 4807 Output IDAT size = 4807 bytes (420 bytes decrease) Output file size = 4938 bytes (420 bytes = 7.84% decrease) 4938 4827 97% ./usr/share/icons/hicolor/48x48/apps/alarm-clock-triggered.png 4938 4827 97% ** Processing: ./usr/share/icons/hicolor/48x48/apps/alarm-timer.png 48x48 pixels, 4x8 bits/pixel, RGB+alpha Input IDAT size = 2868 bytes Input file size = 2999 bytes Trying: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 2390 zc = 9 zm = 8 zs = 1 f = 0 zc = 1 zm = 8 zs = 2 f = 0 zc = 9 zm = 8 zs = 3 f = 0 zc = 9 zm = 8 zs = 0 f = 1 zc = 9 zm = 8 zs = 1 f = 1 zc = 1 zm = 8 zs = 2 f = 1 zc = 9 zm = 8 zs = 3 f = 1 zc = 9 zm = 8 zs = 0 f = 2 zc = 9 zm = 8 zs = 1 f = 2 zc = 1 zm = 8 zs = 2 f = 2 zc = 9 zm = 8 zs = 3 f = 2 zc = 9 zm = 8 zs = 0 f = 3 zc = 9 zm = 8 zs = 1 f = 3 zc = 1 zm = 8 zs = 2 f = 3 zc = 9 zm = 8 zs = 3 f = 3 zc = 9 zm = 8 zs = 0 f = 4 zc = 9 zm = 8 zs = 1 f = 4 zc = 1 zm = 8 zs = 2 f = 4 zc = 9 zm = 8 zs = 3 f = 4 zc = 9 zm = 8 zs = 0 f = 5 zc = 9 zm = 8 zs = 1 f = 5 zc = 1 zm = 8 zs = 2 f = 5 zc = 9 zm = 8 zs = 3 f = 5 Selecting parameters: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 2390 Output IDAT size = 2390 bytes (478 bytes decrease) Output file size = 2521 bytes (478 bytes = 15.94% decrease) 2521 2384 94% ./usr/share/icons/hicolor/48x48/apps/alarm-timer.png 2521 2384 94% ** Processing: ./usr/share/icons/hicolor/48x48/apps/alarm-clock.png 48x48 pixels, 4x8 bits/pixel, RGB+alpha Input IDAT size = 3322 bytes Input file size = 3453 bytes Trying: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 2534 zc = 9 zm = 8 zs = 1 f = 0 zc = 1 zm = 8 zs = 2 f = 0 zc = 9 zm = 8 zs = 3 f = 0 zc = 9 zm = 8 zs = 0 f = 1 zc = 9 zm = 8 zs = 1 f = 1 zc = 1 zm = 8 zs = 2 f = 1 zc = 9 zm = 8 zs = 3 f = 1 zc = 9 zm = 8 zs = 0 f = 2 zc = 9 zm = 8 zs = 1 f = 2 zc = 1 zm = 8 zs = 2 f = 2 zc = 9 zm = 8 zs = 3 f = 2 zc = 9 zm = 8 zs = 0 f = 3 zc = 9 zm = 8 zs = 1 f = 3 zc = 1 zm = 8 zs = 2 f = 3 zc = 9 zm = 8 zs = 3 f = 3 zc = 9 zm = 8 zs = 0 f = 4 zc = 9 zm = 8 zs = 1 f = 4 zc = 1 zm = 8 zs = 2 f = 4 zc = 9 zm = 8 zs = 3 f = 4 zc = 9 zm = 8 zs = 0 f = 5 zc = 9 zm = 8 zs = 1 f = 5 zc = 1 zm = 8 zs = 2 f = 5 zc = 9 zm = 8 zs = 3 f = 5 Selecting parameters: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 2534 Output IDAT size = 2534 bytes (788 bytes decrease) Output file size = 2665 bytes (788 bytes = 22.82% decrease) 2665 2533 95% ./usr/share/icons/hicolor/48x48/apps/alarm-clock.png 2665 2533 95% ** Processing: ./usr/share/icons/hicolor/24x24/apps/alarm-clock-triggered.png 24x24 pixels, 4x8 bits/pixel, RGB+alpha Input IDAT size = 1735 bytes Input file size = 1866 bytes Trying: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 1460 zc = 9 zm = 8 zs = 1 f = 0 zc = 1 zm = 8 zs = 2 f = 0 zc = 9 zm = 8 zs = 3 f = 0 zc = 9 zm = 8 zs = 0 f = 1 zc = 9 zm = 8 zs = 1 f = 1 zc = 1 zm = 8 zs = 2 f = 1 zc = 9 zm = 8 zs = 3 f = 1 zc = 9 zm = 8 zs = 0 f = 2 zc = 9 zm = 8 zs = 1 f = 2 zc = 1 zm = 8 zs = 2 f = 2 zc = 9 zm = 8 zs = 3 f = 2 zc = 9 zm = 8 zs = 0 f = 3 zc = 9 zm = 8 zs = 1 f = 3 zc = 1 zm = 8 zs = 2 f = 3 zc = 9 zm = 8 zs = 3 f = 3 zc = 9 zm = 8 zs = 0 f = 4 zc = 9 zm = 8 zs = 1 f = 4 zc = 1 zm = 8 zs = 2 f = 4 zc = 9 zm = 8 zs = 3 f = 4 zc = 9 zm = 8 zs = 0 f = 5 zc = 9 zm = 8 zs = 1 f = 5 zc = 1 zm = 8 zs = 2 f = 5 zc = 9 zm = 8 zs = 3 f = 5 Selecting parameters: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 1460 Output IDAT size = 1460 bytes (275 bytes decrease) Output file size = 1591 bytes (275 bytes = 14.74% decrease) 1591 1494 93% ./usr/share/icons/hicolor/24x24/apps/alarm-clock-triggered.png 1591 1494 93% ** Processing: ./usr/share/icons/hicolor/24x24/apps/alarm-timer.png 24x24 pixels, 4x8 bits/pixel, RGB+alpha Reducing image to 8 bits/pixel, 217 colors (66 transparent) in palette Input IDAT size = 1235 bytes Input file size = 1366 bytes Trying: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 411 zc = 9 zm = 8 zs = 1 f = 0 zc = 1 zm = 8 zs = 2 f = 0 zc = 9 zm = 8 zs = 3 f = 0 zc = 9 zm = 8 zs = 0 f = 1 zc = 9 zm = 8 zs = 1 f = 1 zc = 1 zm = 8 zs = 2 f = 1 zc = 9 zm = 8 zs = 3 f = 1 zc = 9 zm = 8 zs = 0 f = 2 zc = 9 zm = 8 zs = 1 f = 2 zc = 1 zm = 8 zs = 2 f = 2 zc = 9 zm = 8 zs = 3 f = 2 zc = 9 zm = 8 zs = 0 f = 3 zc = 9 zm = 8 zs = 1 f = 3 zc = 1 zm = 8 zs = 2 f = 3 zc = 9 zm = 8 zs = 3 f = 3 zc = 9 zm = 8 zs = 0 f = 4 zc = 9 zm = 8 zs = 1 f = 4 zc = 1 zm = 8 zs = 2 f = 4 zc = 9 zm = 8 zs = 3 f = 4 zc = 9 zm = 8 zs = 0 f = 5 zc = 9 zm = 8 zs = 1 f = 5 zc = 1 zm = 8 zs = 2 f = 5 zc = 9 zm = 8 zs = 3 f = 5 Selecting parameters: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 411 Output IDAT size = 411 bytes (824 bytes decrease) Output file size = 1282 bytes (84 bytes = 6.15% decrease) 1282 1207 94% ./usr/share/icons/hicolor/24x24/apps/alarm-timer.png 1282 1207 94% ** Processing: ./usr/share/icons/hicolor/24x24/apps/alarm-clock.png 24x24 pixels, 4x8 bits/pixel, RGB+alpha Reducing image to 8 bits/pixel, 172 colors (72 transparent) in palette Input IDAT size = 1387 bytes Input file size = 1518 bytes Trying: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 442 zc = 9 zm = 8 zs = 1 f = 0 zc = 1 zm = 8 zs = 2 f = 0 zc = 9 zm = 8 zs = 3 f = 0 zc = 9 zm = 8 zs = 0 f = 1 zc = 9 zm = 8 zs = 1 f = 1 zc = 1 zm = 8 zs = 2 f = 1 zc = 9 zm = 8 zs = 3 f = 1 zc = 9 zm = 8 zs = 0 f = 2 zc = 9 zm = 8 zs = 1 f = 2 zc = 1 zm = 8 zs = 2 f = 2 zc = 9 zm = 8 zs = 3 f = 2 zc = 9 zm = 8 zs = 0 f = 3 zc = 9 zm = 8 zs = 1 f = 3 zc = 1 zm = 8 zs = 2 f = 3 zc = 9 zm = 8 zs = 3 f = 3 zc = 9 zm = 8 zs = 0 f = 4 zc = 9 zm = 8 zs = 1 f = 4 IDAT size = 440 zc = 1 zm = 8 zs = 2 f = 4 zc = 9 zm = 8 zs = 3 f = 4 zc = 9 zm = 8 zs = 0 f = 5 zc = 9 zm = 8 zs = 1 f = 5 zc = 1 zm = 8 zs = 2 f = 5 zc = 9 zm = 8 zs = 3 f = 5 Selecting parameters: zc = 9 zm = 8 zs = 1 f = 4 IDAT size = 440 Output IDAT size = 440 bytes (947 bytes decrease) Output file size = 1182 bytes (336 bytes = 22.13% decrease) 1182 1109 93% ./usr/share/icons/hicolor/24x24/apps/alarm-clock.png 1182 1109 93% ** Processing: ./usr/share/icons/hicolor/16x16/apps/alarm-clock-triggered.png 16x16 pixels, 4x8 bits/pixel, RGB+alpha Reducing image to 8 bits/pixel, 137 colors (78 transparent) in palette Input IDAT size = 882 bytes Input file size = 1013 bytes Trying: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 273 zc = 9 zm = 8 zs = 1 f = 0 zc = 1 zm = 8 zs = 2 f = 0 zc = 9 zm = 8 zs = 3 f = 0 zc = 9 zm = 8 zs = 0 f = 1 IDAT size = 261 zc = 9 zm = 8 zs = 1 f = 1 IDAT size = 259 zc = 1 zm = 8 zs = 2 f = 1 IDAT size = 259 zc = 9 zm = 8 zs = 3 f = 1 IDAT size = 259 zc = 9 zm = 8 zs = 0 f = 2 IDAT size = 249 zc = 9 zm = 8 zs = 1 f = 2 IDAT size = 249 zc = 1 zm = 8 zs = 2 f = 2 IDAT size = 249 zc = 9 zm = 8 zs = 3 f = 2 IDAT size = 248 zc = 9 zm = 8 zs = 0 f = 3 IDAT size = 247 zc = 9 zm = 8 zs = 1 f = 3 IDAT size = 247 zc = 1 zm = 8 zs = 2 f = 3 IDAT size = 247 zc = 9 zm = 8 zs = 3 f = 3 IDAT size = 247 zc = 9 zm = 8 zs = 0 f = 4 IDAT size = 241 zc = 9 zm = 8 zs = 1 f = 4 IDAT size = 240 zc = 1 zm = 8 zs = 2 f = 4 IDAT size = 240 zc = 9 zm = 8 zs = 3 f = 4 IDAT size = 240 zc = 9 zm = 8 zs = 0 f = 5 zc = 9 zm = 8 zs = 1 f = 5 IDAT size = 237 zc = 1 zm = 8 zs = 2 f = 5 IDAT size = 237 zc = 9 zm = 8 zs = 3 f = 5 IDAT size = 237 Selecting parameters: zc = 1 zm = 8 zs = 2 f = 5 IDAT size = 237 Output IDAT size = 237 bytes (645 bytes decrease) Output file size = 880 bytes (133 bytes = 13.13% decrease) 880 842 95% ./usr/share/icons/hicolor/16x16/apps/alarm-clock-triggered.png 880 842 95% ** Processing: ./usr/share/icons/hicolor/16x16/apps/alarm-timer.png 16x16 pixels, 4x8 bits/pixel, RGB+alpha Reducing image to 8 bits/pixel, 58 colors (20 transparent) in palette Input IDAT size = 580 bytes Input file size = 711 bytes Trying: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 163 zc = 9 zm = 8 zs = 1 f = 0 IDAT size = 163 zc = 1 zm = 8 zs = 2 f = 0 zc = 9 zm = 8 zs = 3 f = 0 zc = 9 zm = 8 zs = 0 f = 1 zc = 9 zm = 8 zs = 1 f = 1 zc = 1 zm = 8 zs = 2 f = 1 zc = 9 zm = 8 zs = 3 f = 1 zc = 9 zm = 8 zs = 0 f = 2 zc = 9 zm = 8 zs = 1 f = 2 zc = 1 zm = 8 zs = 2 f = 2 zc = 9 zm = 8 zs = 3 f = 2 zc = 9 zm = 8 zs = 0 f = 3 zc = 9 zm = 8 zs = 1 f = 3 zc = 1 zm = 8 zs = 2 f = 3 zc = 9 zm = 8 zs = 3 f = 3 zc = 9 zm = 8 zs = 0 f = 4 zc = 9 zm = 8 zs = 1 f = 4 zc = 1 zm = 8 zs = 2 f = 4 zc = 9 zm = 8 zs = 3 f = 4 zc = 9 zm = 8 zs = 0 f = 5 zc = 9 zm = 8 zs = 1 f = 5 zc = 1 zm = 8 zs = 2 f = 5 zc = 9 zm = 8 zs = 3 f = 5 Selecting parameters: zc = 9 zm = 8 zs = 1 f = 0 IDAT size = 163 Output IDAT size = 163 bytes (417 bytes decrease) Output file size = 511 bytes (200 bytes = 28.13% decrease) 511 435 85% ./usr/share/icons/hicolor/16x16/apps/alarm-timer.png 511 435 85% ** Processing: ./usr/share/icons/hicolor/16x16/apps/alarm-clock.png 16x16 pixels, 4x8 bits/pixel, RGB+alpha Reducing image to 8 bits/pixel, 96 colors (48 transparent) in palette Input IDAT size = 773 bytes Input file size = 904 bytes Trying: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 223 zc = 9 zm = 8 zs = 1 f = 0 zc = 1 zm = 8 zs = 2 f = 0 IDAT size = 222 zc = 9 zm = 8 zs = 3 f = 0 IDAT size = 217 zc = 9 zm = 8 zs = 0 f = 1 zc = 9 zm = 8 zs = 1 f = 1 zc = 1 zm = 8 zs = 2 f = 1 zc = 9 zm = 8 zs = 3 f = 1 zc = 9 zm = 8 zs = 0 f = 2 zc = 9 zm = 8 zs = 1 f = 2 zc = 1 zm = 8 zs = 2 f = 2 zc = 9 zm = 8 zs = 3 f = 2 zc = 9 zm = 8 zs = 0 f = 3 zc = 9 zm = 8 zs = 1 f = 3 zc = 1 zm = 8 zs = 2 f = 3 IDAT size = 217 zc = 9 zm = 8 zs = 3 f = 3 zc = 9 zm = 8 zs = 0 f = 4 IDAT size = 217 zc = 9 zm = 8 zs = 1 f = 4 IDAT size = 214 zc = 1 zm = 8 zs = 2 f = 4 IDAT size = 212 zc = 9 zm = 8 zs = 3 f = 4 zc = 9 zm = 8 zs = 0 f = 5 zc = 9 zm = 8 zs = 1 f = 5 zc = 1 zm = 8 zs = 2 f = 5 IDAT size = 212 zc = 9 zm = 8 zs = 3 f = 5 Selecting parameters: zc = 1 zm = 8 zs = 2 f = 4 IDAT size = 212 Output IDAT size = 212 bytes (561 bytes decrease) Output file size = 702 bytes (202 bytes = 22.35% decrease) 702 639 91% ./usr/share/icons/hicolor/16x16/apps/alarm-clock.png 702 639 91% ** Processing: ./usr/share/icons/hicolor/36x36/apps/alarm-clock-triggered.png 36x36 pixels, 4x8 bits/pixel, RGB+alpha Input IDAT size = 3307 bytes Input file size = 3438 bytes Trying: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 2979 zc = 9 zm = 8 zs = 1 f = 0 zc = 1 zm = 8 zs = 2 f = 0 zc = 9 zm = 8 zs = 3 f = 0 zc = 9 zm = 8 zs = 0 f = 1 zc = 9 zm = 8 zs = 1 f = 1 zc = 1 zm = 8 zs = 2 f = 1 zc = 9 zm = 8 zs = 3 f = 1 zc = 9 zm = 8 zs = 0 f = 2 IDAT size = 2919 zc = 9 zm = 8 zs = 1 f = 2 zc = 1 zm = 8 zs = 2 f = 2 zc = 9 zm = 8 zs = 3 f = 2 zc = 9 zm = 8 zs = 0 f = 3 zc = 9 zm = 8 zs = 1 f = 3 zc = 1 zm = 8 zs = 2 f = 3 zc = 9 zm = 8 zs = 3 f = 3 zc = 9 zm = 8 zs = 0 f = 4 zc = 9 zm = 8 zs = 1 f = 4 zc = 1 zm = 8 zs = 2 f = 4 zc = 9 zm = 8 zs = 3 f = 4 zc = 9 zm = 8 zs = 0 f = 5 zc = 9 zm = 8 zs = 1 f = 5 zc = 1 zm = 8 zs = 2 f = 5 zc = 9 zm = 8 zs = 3 f = 5 Selecting parameters: zc = 9 zm = 8 zs = 0 f = 2 IDAT size = 2919 Output IDAT size = 2919 bytes (388 bytes decrease) Output file size = 3050 bytes (388 bytes = 11.29% decrease) 3050 2968 97% ./usr/share/icons/hicolor/36x36/apps/alarm-clock-triggered.png 3050 2968 97% ** Processing: ./usr/share/icons/hicolor/36x36/apps/alarm-timer.png 36x36 pixels, 4x8 bits/pixel, RGB+alpha Input IDAT size = 2126 bytes Input file size = 2257 bytes Trying: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 1772 zc = 9 zm = 8 zs = 1 f = 0 zc = 1 zm = 8 zs = 2 f = 0 zc = 9 zm = 8 zs = 3 f = 0 zc = 9 zm = 8 zs = 0 f = 1 zc = 9 zm = 8 zs = 1 f = 1 zc = 1 zm = 8 zs = 2 f = 1 zc = 9 zm = 8 zs = 3 f = 1 zc = 9 zm = 8 zs = 0 f = 2 zc = 9 zm = 8 zs = 1 f = 2 zc = 1 zm = 8 zs = 2 f = 2 zc = 9 zm = 8 zs = 3 f = 2 zc = 9 zm = 8 zs = 0 f = 3 zc = 9 zm = 8 zs = 1 f = 3 zc = 1 zm = 8 zs = 2 f = 3 zc = 9 zm = 8 zs = 3 f = 3 zc = 9 zm = 8 zs = 0 f = 4 zc = 9 zm = 8 zs = 1 f = 4 zc = 1 zm = 8 zs = 2 f = 4 zc = 9 zm = 8 zs = 3 f = 4 zc = 9 zm = 8 zs = 0 f = 5 zc = 9 zm = 8 zs = 1 f = 5 zc = 1 zm = 8 zs = 2 f = 5 zc = 9 zm = 8 zs = 3 f = 5 Selecting parameters: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 1772 Output IDAT size = 1772 bytes (354 bytes decrease) Output file size = 1903 bytes (354 bytes = 15.68% decrease) 1903 1797 94% ./usr/share/icons/hicolor/36x36/apps/alarm-timer.png 1903 1797 94% ** Processing: ./usr/share/icons/hicolor/36x36/apps/alarm-clock.png 36x36 pixels, 4x8 bits/pixel, RGB+alpha Input IDAT size = 2387 bytes Input file size = 2518 bytes Trying: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 1766 zc = 9 zm = 8 zs = 1 f = 0 zc = 1 zm = 8 zs = 2 f = 0 zc = 9 zm = 8 zs = 3 f = 0 zc = 9 zm = 8 zs = 0 f = 1 zc = 9 zm = 8 zs = 1 f = 1 zc = 1 zm = 8 zs = 2 f = 1 zc = 9 zm = 8 zs = 3 f = 1 zc = 9 zm = 8 zs = 0 f = 2 zc = 9 zm = 8 zs = 1 f = 2 zc = 1 zm = 8 zs = 2 f = 2 zc = 9 zm = 8 zs = 3 f = 2 zc = 9 zm = 8 zs = 0 f = 3 zc = 9 zm = 8 zs = 1 f = 3 zc = 1 zm = 8 zs = 2 f = 3 zc = 9 zm = 8 zs = 3 f = 3 zc = 9 zm = 8 zs = 0 f = 4 zc = 9 zm = 8 zs = 1 f = 4 zc = 1 zm = 8 zs = 2 f = 4 zc = 9 zm = 8 zs = 3 f = 4 zc = 9 zm = 8 zs = 0 f = 5 zc = 9 zm = 8 zs = 1 f = 5 zc = 1 zm = 8 zs = 2 f = 5 zc = 9 zm = 8 zs = 3 f = 5 Selecting parameters: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 1766 Output IDAT size = 1766 bytes (621 bytes decrease) Output file size = 1897 bytes (621 bytes = 24.66% decrease) 1897 1799 94% ./usr/share/icons/hicolor/36x36/apps/alarm-clock.png 1897 1799 94% ** Processing: ./usr/share/icons/hicolor/22x22/apps/alarm-clock-triggered.png 22x22 pixels, 4x8 bits/pixel, RGB+alpha Reducing image to 8 bits/pixel, 235 colors (115 transparent) in palette Input IDAT size = 1488 bytes Input file size = 1619 bytes Trying: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 511 zc = 9 zm = 8 zs = 1 f = 0 zc = 1 zm = 8 zs = 2 f = 0 zc = 9 zm = 8 zs = 3 f = 0 zc = 9 zm = 8 zs = 0 f = 1 IDAT size = 487 zc = 9 zm = 8 zs = 1 f = 1 IDAT size = 485 zc = 1 zm = 8 zs = 2 f = 1 IDAT size = 485 zc = 9 zm = 8 zs = 3 f = 1 IDAT size = 484 zc = 9 zm = 8 zs = 0 f = 2 IDAT size = 476 zc = 9 zm = 8 zs = 1 f = 2 IDAT size = 474 zc = 1 zm = 8 zs = 2 f = 2 IDAT size = 474 zc = 9 zm = 8 zs = 3 f = 2 IDAT size = 474 zc = 9 zm = 8 zs = 0 f = 3 IDAT size = 465 zc = 9 zm = 8 zs = 1 f = 3 IDAT size = 462 zc = 1 zm = 8 zs = 2 f = 3 IDAT size = 462 zc = 9 zm = 8 zs = 3 f = 3 IDAT size = 462 zc = 9 zm = 8 zs = 0 f = 4 IDAT size = 453 zc = 9 zm = 8 zs = 1 f = 4 IDAT size = 448 zc = 1 zm = 8 zs = 2 f = 4 IDAT size = 448 zc = 9 zm = 8 zs = 3 f = 4 IDAT size = 448 zc = 9 zm = 8 zs = 0 f = 5 zc = 9 zm = 8 zs = 1 f = 5 IDAT size = 442 zc = 1 zm = 8 zs = 2 f = 5 IDAT size = 442 zc = 9 zm = 8 zs = 3 f = 5 Selecting parameters: zc = 1 zm = 8 zs = 2 f = 5 IDAT size = 442 Output IDAT size = 442 bytes (1046 bytes decrease) Output file size = 1416 bytes (203 bytes = 12.54% decrease) 1416 1412 99% ./usr/share/icons/hicolor/22x22/apps/alarm-clock-triggered.png 1416 1412 99% ** Processing: ./usr/share/icons/hicolor/22x22/apps/alarm-timer.png 22x22 pixels, 4x8 bits/pixel, RGB+alpha Reducing image to 8 bits/pixel, 196 colors (64 transparent) in palette Input IDAT size = 1119 bytes Input file size = 1250 bytes Trying: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 357 zc = 9 zm = 8 zs = 1 f = 0 zc = 1 zm = 8 zs = 2 f = 0 zc = 9 zm = 8 zs = 3 f = 0 zc = 9 zm = 8 zs = 0 f = 1 zc = 9 zm = 8 zs = 1 f = 1 zc = 1 zm = 8 zs = 2 f = 1 zc = 9 zm = 8 zs = 3 f = 1 zc = 9 zm = 8 zs = 0 f = 2 zc = 9 zm = 8 zs = 1 f = 2 zc = 1 zm = 8 zs = 2 f = 2 zc = 9 zm = 8 zs = 3 f = 2 zc = 9 zm = 8 zs = 0 f = 3 zc = 9 zm = 8 zs = 1 f = 3 zc = 1 zm = 8 zs = 2 f = 3 zc = 9 zm = 8 zs = 3 f = 3 zc = 9 zm = 8 zs = 0 f = 4 zc = 9 zm = 8 zs = 1 f = 4 zc = 1 zm = 8 zs = 2 f = 4 zc = 9 zm = 8 zs = 3 f = 4 zc = 9 zm = 8 zs = 0 f = 5 zc = 9 zm = 8 zs = 1 f = 5 zc = 1 zm = 8 zs = 2 f = 5 zc = 9 zm = 8 zs = 3 f = 5 Selecting parameters: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 357 Output IDAT size = 357 bytes (762 bytes decrease) Output file size = 1163 bytes (87 bytes = 6.96% decrease) 1163 1089 93% ./usr/share/icons/hicolor/22x22/apps/alarm-timer.png 1163 1089 93% ** Processing: ./usr/share/icons/hicolor/22x22/apps/alarm-clock.png 22x22 pixels, 4x8 bits/pixel, RGB+alpha Reducing image to 8 bits/pixel, 138 colors (54 transparent) in palette Input IDAT size = 1146 bytes Input file size = 1277 bytes Trying: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 363 zc = 9 zm = 8 zs = 1 f = 0 zc = 1 zm = 8 zs = 2 f = 0 zc = 9 zm = 8 zs = 3 f = 0 IDAT size = 357 zc = 9 zm = 8 zs = 0 f = 1 zc = 9 zm = 8 zs = 1 f = 1 zc = 1 zm = 8 zs = 2 f = 1 zc = 9 zm = 8 zs = 3 f = 1 zc = 9 zm = 8 zs = 0 f = 2 zc = 9 zm = 8 zs = 1 f = 2 zc = 1 zm = 8 zs = 2 f = 2 zc = 9 zm = 8 zs = 3 f = 2 zc = 9 zm = 8 zs = 0 f = 3 zc = 9 zm = 8 zs = 1 f = 3 zc = 1 zm = 8 zs = 2 f = 3 zc = 9 zm = 8 zs = 3 f = 3 zc = 9 zm = 8 zs = 0 f = 4 zc = 9 zm = 8 zs = 1 f = 4 zc = 1 zm = 8 zs = 2 f = 4 zc = 9 zm = 8 zs = 3 f = 4 zc = 9 zm = 8 zs = 0 f = 5 zc = 9 zm = 8 zs = 1 f = 5 zc = 1 zm = 8 zs = 2 f = 5 zc = 9 zm = 8 zs = 3 f = 5 Selecting parameters: zc = 9 zm = 8 zs = 3 f = 0 IDAT size = 357 Output IDAT size = 357 bytes (789 bytes decrease) Output file size = 979 bytes (298 bytes = 23.34% decrease) 979 910 92% ./usr/share/icons/hicolor/22x22/apps/alarm-clock.png 979 910 92% ** Processing: ./usr/share/icons/hicolor/64x64/apps/alarm-clock-triggered.png 64x64 pixels, 4x8 bits/pixel, RGB+alpha Input IDAT size = 8261 bytes Input file size = 8404 bytes Trying: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 8046 zc = 9 zm = 8 zs = 1 f = 0 zc = 1 zm = 8 zs = 2 f = 0 zc = 9 zm = 8 zs = 3 f = 0 zc = 9 zm = 8 zs = 0 f = 1 zc = 9 zm = 8 zs = 1 f = 1 zc = 1 zm = 8 zs = 2 f = 1 zc = 9 zm = 8 zs = 3 f = 1 zc = 9 zm = 8 zs = 0 f = 2 IDAT size = 7557 zc = 9 zm = 8 zs = 1 f = 2 zc = 1 zm = 8 zs = 2 f = 2 zc = 9 zm = 8 zs = 3 f = 2 zc = 9 zm = 8 zs = 0 f = 3 zc = 9 zm = 8 zs = 1 f = 3 zc = 1 zm = 8 zs = 2 f = 3 zc = 9 zm = 8 zs = 3 f = 3 zc = 9 zm = 8 zs = 0 f = 4 zc = 9 zm = 8 zs = 1 f = 4 zc = 1 zm = 8 zs = 2 f = 4 zc = 9 zm = 8 zs = 3 f = 4 zc = 9 zm = 8 zs = 0 f = 5 zc = 9 zm = 8 zs = 1 f = 5 zc = 1 zm = 8 zs = 2 f = 5 zc = 9 zm = 8 zs = 3 f = 5 Selecting parameters: zc = 9 zm = 8 zs = 0 f = 2 IDAT size = 7557 Output IDAT size = 7557 bytes (704 bytes decrease) Output file size = 7688 bytes (716 bytes = 8.52% decrease) 7688 7688 100% ./usr/share/icons/hicolor/64x64/apps/alarm-clock-triggered.png (Bigger 7725) 7688 7688 100% ** Processing: ./usr/share/icons/hicolor/64x64/apps/alarm-timer.png 64x64 pixels, 4x8 bits/pixel, RGB+alpha Input IDAT size = 4229 bytes Input file size = 4360 bytes Trying: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 3538 zc = 9 zm = 8 zs = 1 f = 0 zc = 1 zm = 8 zs = 2 f = 0 zc = 9 zm = 8 zs = 3 f = 0 zc = 9 zm = 8 zs = 0 f = 1 zc = 9 zm = 8 zs = 1 f = 1 zc = 1 zm = 8 zs = 2 f = 1 zc = 9 zm = 8 zs = 3 f = 1 zc = 9 zm = 8 zs = 0 f = 2 zc = 9 zm = 8 zs = 1 f = 2 zc = 1 zm = 8 zs = 2 f = 2 zc = 9 zm = 8 zs = 3 f = 2 zc = 9 zm = 8 zs = 0 f = 3 zc = 9 zm = 8 zs = 1 f = 3 zc = 1 zm = 8 zs = 2 f = 3 zc = 9 zm = 8 zs = 3 f = 3 zc = 9 zm = 8 zs = 0 f = 4 zc = 9 zm = 8 zs = 1 f = 4 zc = 1 zm = 8 zs = 2 f = 4 zc = 9 zm = 8 zs = 3 f = 4 zc = 9 zm = 8 zs = 0 f = 5 zc = 9 zm = 8 zs = 1 f = 5 zc = 1 zm = 8 zs = 2 f = 5 zc = 9 zm = 8 zs = 3 f = 5 Selecting parameters: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 3538 Output IDAT size = 3538 bytes (691 bytes decrease) Output file size = 3669 bytes (691 bytes = 15.85% decrease) 3669 3489 95% ./usr/share/icons/hicolor/64x64/apps/alarm-timer.png 3669 3489 95% ** Processing: ./usr/share/icons/hicolor/64x64/apps/alarm-clock.png 64x64 pixels, 4x8 bits/pixel, RGB+alpha Input IDAT size = 4781 bytes Input file size = 4912 bytes Trying: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 3596 zc = 9 zm = 8 zs = 1 f = 0 zc = 1 zm = 8 zs = 2 f = 0 zc = 9 zm = 8 zs = 3 f = 0 zc = 9 zm = 8 zs = 0 f = 1 zc = 9 zm = 8 zs = 1 f = 1 zc = 1 zm = 8 zs = 2 f = 1 zc = 9 zm = 8 zs = 3 f = 1 zc = 9 zm = 8 zs = 0 f = 2 zc = 9 zm = 8 zs = 1 f = 2 zc = 1 zm = 8 zs = 2 f = 2 zc = 9 zm = 8 zs = 3 f = 2 zc = 9 zm = 8 zs = 0 f = 3 zc = 9 zm = 8 zs = 1 f = 3 zc = 1 zm = 8 zs = 2 f = 3 zc = 9 zm = 8 zs = 3 f = 3 zc = 9 zm = 8 zs = 0 f = 4 zc = 9 zm = 8 zs = 1 f = 4 zc = 1 zm = 8 zs = 2 f = 4 zc = 9 zm = 8 zs = 3 f = 4 zc = 9 zm = 8 zs = 0 f = 5 zc = 9 zm = 8 zs = 1 f = 5 zc = 1 zm = 8 zs = 2 f = 5 zc = 9 zm = 8 zs = 3 f = 5 Selecting parameters: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 3596 Output IDAT size = 3596 bytes (1185 bytes decrease) Output file size = 3727 bytes (1185 bytes = 24.12% decrease) 3727 3550 95% ./usr/share/icons/hicolor/64x64/apps/alarm-clock.png 3727 3550 95% ** Processing: ./usr/share/icons/hicolor/32x32/apps/alarm-clock-triggered.png 32x32 pixels, 4x8 bits/pixel, RGB+alpha Input IDAT size = 2733 bytes Input file size = 2864 bytes Trying: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 2411 zc = 9 zm = 8 zs = 1 f = 0 zc = 1 zm = 8 zs = 2 f = 0 zc = 9 zm = 8 zs = 3 f = 0 zc = 9 zm = 8 zs = 0 f = 1 zc = 9 zm = 8 zs = 1 f = 1 zc = 1 zm = 8 zs = 2 f = 1 zc = 9 zm = 8 zs = 3 f = 1 zc = 9 zm = 8 zs = 0 f = 2 zc = 9 zm = 8 zs = 1 f = 2 zc = 1 zm = 8 zs = 2 f = 2 zc = 9 zm = 8 zs = 3 f = 2 zc = 9 zm = 8 zs = 0 f = 3 zc = 9 zm = 8 zs = 1 f = 3 zc = 1 zm = 8 zs = 2 f = 3 zc = 9 zm = 8 zs = 3 f = 3 zc = 9 zm = 8 zs = 0 f = 4 zc = 9 zm = 8 zs = 1 f = 4 zc = 1 zm = 8 zs = 2 f = 4 zc = 9 zm = 8 zs = 3 f = 4 zc = 9 zm = 8 zs = 0 f = 5 zc = 9 zm = 8 zs = 1 f = 5 zc = 1 zm = 8 zs = 2 f = 5 zc = 9 zm = 8 zs = 3 f = 5 Selecting parameters: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 2411 Output IDAT size = 2411 bytes (322 bytes decrease) Output file size = 2542 bytes (322 bytes = 11.24% decrease) 2542 2429 95% ./usr/share/icons/hicolor/32x32/apps/alarm-clock-triggered.png 2542 2429 95% ** Processing: ./usr/share/icons/hicolor/32x32/apps/alarm-timer.png 32x32 pixels, 4x8 bits/pixel, RGB+alpha Input IDAT size = 1890 bytes Input file size = 2021 bytes Trying: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 1559 zc = 9 zm = 8 zs = 1 f = 0 zc = 1 zm = 8 zs = 2 f = 0 zc = 9 zm = 8 zs = 3 f = 0 zc = 9 zm = 8 zs = 0 f = 1 zc = 9 zm = 8 zs = 1 f = 1 zc = 1 zm = 8 zs = 2 f = 1 zc = 9 zm = 8 zs = 3 f = 1 zc = 9 zm = 8 zs = 0 f = 2 zc = 9 zm = 8 zs = 1 f = 2 zc = 1 zm = 8 zs = 2 f = 2 zc = 9 zm = 8 zs = 3 f = 2 zc = 9 zm = 8 zs = 0 f = 3 zc = 9 zm = 8 zs = 1 f = 3 zc = 1 zm = 8 zs = 2 f = 3 zc = 9 zm = 8 zs = 3 f = 3 zc = 9 zm = 8 zs = 0 f = 4 zc = 9 zm = 8 zs = 1 f = 4 zc = 1 zm = 8 zs = 2 f = 4 zc = 9 zm = 8 zs = 3 f = 4 zc = 9 zm = 8 zs = 0 f = 5 zc = 9 zm = 8 zs = 1 f = 5 zc = 1 zm = 8 zs = 2 f = 5 zc = 9 zm = 8 zs = 3 f = 5 Selecting parameters: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 1559 Output IDAT size = 1559 bytes (331 bytes decrease) Output file size = 1690 bytes (331 bytes = 16.38% decrease) 1690 1595 94% ./usr/share/icons/hicolor/32x32/apps/alarm-timer.png 1690 1595 94% ** Processing: ./usr/share/icons/hicolor/32x32/apps/alarm-clock.png 32x32 pixels, 4x8 bits/pixel, RGB+alpha Reducing image to 8 bits/pixel, 241 colors (94 transparent) in palette Input IDAT size = 2036 bytes Input file size = 2167 bytes Trying: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 721 zc = 9 zm = 8 zs = 1 f = 0 zc = 1 zm = 8 zs = 2 f = 0 zc = 9 zm = 8 zs = 3 f = 0 IDAT size = 718 zc = 9 zm = 8 zs = 0 f = 1 zc = 9 zm = 8 zs = 1 f = 1 zc = 1 zm = 8 zs = 2 f = 1 zc = 9 zm = 8 zs = 3 f = 1 zc = 9 zm = 8 zs = 0 f = 2 zc = 9 zm = 8 zs = 1 f = 2 zc = 1 zm = 8 zs = 2 f = 2 zc = 9 zm = 8 zs = 3 f = 2 zc = 9 zm = 8 zs = 0 f = 3 zc = 9 zm = 8 zs = 1 f = 3 zc = 1 zm = 8 zs = 2 f = 3 zc = 9 zm = 8 zs = 3 f = 3 zc = 9 zm = 8 zs = 0 f = 4 zc = 9 zm = 8 zs = 1 f = 4 IDAT size = 712 zc = 1 zm = 8 zs = 2 f = 4 zc = 9 zm = 8 zs = 3 f = 4 zc = 9 zm = 8 zs = 0 f = 5 zc = 9 zm = 8 zs = 1 f = 5 zc = 1 zm = 8 zs = 2 f = 5 zc = 9 zm = 8 zs = 3 f = 5 Selecting parameters: zc = 9 zm = 8 zs = 1 f = 4 IDAT size = 712 Output IDAT size = 712 bytes (1324 bytes decrease) Output file size = 1683 bytes (484 bytes = 22.34% decrease) 1683 1616 96% ./usr/share/icons/hicolor/32x32/apps/alarm-clock.png 1683 1616 96% pkgstripfiles: PNG optimization for package alarm-clock-applet took 1 s dpkg-deb: building package 'alarm-clock-applet' in '../alarm-clock-applet_0.3.4-1_ppc64el.deb'. dpkg-genchanges -b -mLaunchpad Build Daemon >../alarm-clock-applet_0.3.4-1_ppc64el.changes dpkg-genchanges: binary-only upload (no source code included) dpkg-source --after-build alarm-clock-applet-0.3.4 dpkg-buildpackage: binary-only upload (no source included) ──────────────────────────────────────────────────────────────────────────────── Build finished at 20150902-0948 Finished ──────── I: Built successfully ┌──────────────────────────────────────────────────────────────────────────────┐ │ Post Build Chroot │ └──────────────────────────────────────────────────────────────────────────────┘ ┌──────────────────────────────────────────────────────────────────────────────┐ │ Changes │ └──────────────────────────────────────────────────────────────────────────────┘ alarm-clock-applet_0.3.4-1_ppc64el.changes: ─────────────────────────────────────────── Format: 1.8 Date: Tue, 19 May 2015 13:51:08 +0800 Source: alarm-clock-applet Binary: alarm-clock-applet Architecture: ppc64el Version: 0.3.4-1 Distribution: wily Urgency: medium Maintainer: Launchpad Build Daemon Changed-By: Chow Loong Jin Description: alarm-clock-applet - alarm clock panel indicator Changes: alarm-clock-applet (0.3.4-1) unstable; urgency=medium . * [0499cae] Fix debian/watch. Launchpad URLs have changed again. * [3becb10] Imported Upstream version 0.3.4 * [9a0d479] Update gstreamer deps * [74a4d3e] No-change bump of Standards-Version to 3.9.6 * [6ddde20] Improve short description Checksums-Sha1: 45e44b7ed2d611c8db785009658382452d5d0196 139746 alarm-clock-applet_0.3.4-1_ppc64el.deb Checksums-Sha256: 76a611a909a934ab9309daa8b26f84ae1b34a828cc35623bffe14a10b626f5b7 139746 alarm-clock-applet_0.3.4-1_ppc64el.deb Files: cfdf94fddacbaaed403edaf075e323d7 139746 gnome optional alarm-clock-applet_0.3.4-1_ppc64el.deb ┌──────────────────────────────────────────────────────────────────────────────┐ │ Package contents │ └──────────────────────────────────────────────────────────────────────────────┘ alarm-clock-applet_0.3.4-1_ppc64el.deb ────────────────────────────────────── new debian package, version 2.0. size 139746 bytes: control archive=2685 bytes. 46 bytes, 1 lines conffiles 1026 bytes, 18 lines control 5751 bytes, 66 lines md5sums Package: alarm-clock-applet Version: 0.3.4-1 Architecture: ppc64el Maintainer: Ubuntu Developers Original-Maintainer: Chow Loong Jin Installed-Size: 732 Depends: gstreamer1.0-plugins-base, gstreamer1.0-plugins-good, gconf-service, libappindicator1 (>= 0.4.90), libc6 (>= 2.17), libgconf-2-4 (>= 3.2.5), libglib2.0-0 (>= 2.37.3), libgstreamer1.0-0 (>= 1.0.0), libgtk2.0-0 (>= 2.20.0), libnotify4 (>= 0.7.0), libunique-1.0-0 (>= 1.0.0), libxml2 (>= 2.7.4), gconf2 (>= 2.28.1-2) Section: gnome Priority: optional Homepage: http://alarm-clock.pseudoberries.com/ Description: alarm clock panel indicator 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. drwxr-xr-x root/root 0 2015-09-02 09:48 ./ drwxr-xr-x root/root 0 2015-09-02 09:48 ./etc/ drwxr-xr-x root/root 0 2015-09-02 09:48 ./etc/xdg/ drwxr-xr-x root/root 0 2015-09-02 09:48 ./etc/xdg/autostart/ -rw-r--r-- root/root 212 2015-09-02 09:48 ./etc/xdg/autostart/alarm-clock-applet.desktop drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/ drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/bin/ -rwxr-xr-x root/root 133632 2015-09-02 09:48 ./usr/bin/alarm-clock-applet drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/ drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/alarm-clock-applet/ -rw-r--r-- root/root 66257 2015-09-02 09:48 ./usr/share/alarm-clock-applet/alarm-clock.ui drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/applications/ -rw-r--r-- root/root 202 2015-09-02 09:48 ./usr/share/applications/alarm-clock-applet.desktop drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/doc/ drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/doc/alarm-clock-applet/ -rw-r--r-- root/root 2524 2015-09-02 09:48 ./usr/share/doc/alarm-clock-applet/changelog.Debian.gz -rw-r--r-- root/root 1390 2015-05-19 05:57 ./usr/share/doc/alarm-clock-applet/copyright drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/gconf/ drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/gconf/schemas/ -rw-r--r-- root/root 73207 2015-09-02 09:48 ./usr/share/gconf/schemas/alarm-clock.schemas drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/icons/ drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/icons/hicolor/ drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/icons/hicolor/16x16/ drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/icons/hicolor/16x16/apps/ -rw-r--r-- root/root 842 2015-09-02 09:48 ./usr/share/icons/hicolor/16x16/apps/alarm-clock-triggered.png -rw-r--r-- root/root 639 2015-09-02 09:48 ./usr/share/icons/hicolor/16x16/apps/alarm-clock.png -rw-r--r-- root/root 435 2015-09-02 09:48 ./usr/share/icons/hicolor/16x16/apps/alarm-timer.png drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/icons/hicolor/22x22/ drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/icons/hicolor/22x22/apps/ -rw-r--r-- root/root 1412 2015-09-02 09:48 ./usr/share/icons/hicolor/22x22/apps/alarm-clock-triggered.png -rw-r--r-- root/root 910 2015-09-02 09:48 ./usr/share/icons/hicolor/22x22/apps/alarm-clock.png -rw-r--r-- root/root 1089 2015-09-02 09:48 ./usr/share/icons/hicolor/22x22/apps/alarm-timer.png drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/icons/hicolor/24x24/ drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/icons/hicolor/24x24/apps/ -rw-r--r-- root/root 1494 2015-09-02 09:48 ./usr/share/icons/hicolor/24x24/apps/alarm-clock-triggered.png -rw-r--r-- root/root 1109 2015-09-02 09:48 ./usr/share/icons/hicolor/24x24/apps/alarm-clock.png -rw-r--r-- root/root 1207 2015-09-02 09:48 ./usr/share/icons/hicolor/24x24/apps/alarm-timer.png drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/icons/hicolor/32x32/ drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/icons/hicolor/32x32/apps/ -rw-r--r-- root/root 2429 2015-09-02 09:48 ./usr/share/icons/hicolor/32x32/apps/alarm-clock-triggered.png -rw-r--r-- root/root 1616 2015-09-02 09:48 ./usr/share/icons/hicolor/32x32/apps/alarm-clock.png -rw-r--r-- root/root 1595 2015-09-02 09:48 ./usr/share/icons/hicolor/32x32/apps/alarm-timer.png drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/icons/hicolor/36x36/ drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/icons/hicolor/36x36/apps/ -rw-r--r-- root/root 2968 2015-09-02 09:48 ./usr/share/icons/hicolor/36x36/apps/alarm-clock-triggered.png -rw-r--r-- root/root 1799 2015-09-02 09:48 ./usr/share/icons/hicolor/36x36/apps/alarm-clock.png -rw-r--r-- root/root 1797 2015-09-02 09:48 ./usr/share/icons/hicolor/36x36/apps/alarm-timer.png drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/icons/hicolor/48x48/ drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/icons/hicolor/48x48/apps/ -rw-r--r-- root/root 4827 2015-09-02 09:48 ./usr/share/icons/hicolor/48x48/apps/alarm-clock-triggered.png -rw-r--r-- root/root 2533 2015-09-02 09:48 ./usr/share/icons/hicolor/48x48/apps/alarm-clock.png -rw-r--r-- root/root 2384 2015-09-02 09:48 ./usr/share/icons/hicolor/48x48/apps/alarm-timer.png drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/icons/hicolor/64x64/ drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/icons/hicolor/64x64/apps/ -rw-r--r-- root/root 7688 2015-09-02 09:48 ./usr/share/icons/hicolor/64x64/apps/alarm-clock-triggered.png -rw-r--r-- root/root 3550 2015-09-02 09:48 ./usr/share/icons/hicolor/64x64/apps/alarm-clock.png -rw-r--r-- root/root 3489 2015-09-02 09:48 ./usr/share/icons/hicolor/64x64/apps/alarm-timer.png drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/icons/hicolor/scalable/ drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/icons/hicolor/scalable/apps/ -rw-r--r-- root/root 10076 2015-09-02 09:48 ./usr/share/icons/hicolor/scalable/apps/alarm-clock.svg -rw-r--r-- root/root 8970 2015-09-02 09:48 ./usr/share/icons/hicolor/scalable/apps/alarm-timer.svg drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/ drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/ar/ drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/ar/LC_MESSAGES/ -rw-r--r-- root/root 7864 2015-09-02 09:48 ./usr/share/locale/ar/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/ast/ drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/ast/LC_MESSAGES/ -rw-r--r-- root/root 7648 2015-09-02 09:48 ./usr/share/locale/ast/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/be/ drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/be/LC_MESSAGES/ -rw-r--r-- root/root 8928 2015-09-02 09:48 ./usr/share/locale/be/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/bg/ drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/bg/LC_MESSAGES/ -rw-r--r-- root/root 9639 2015-09-02 09:48 ./usr/share/locale/bg/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/ca/ drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/ca/LC_MESSAGES/ -rw-r--r-- root/root 7222 2015-09-02 09:48 ./usr/share/locale/ca/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/cs/ drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/cs/LC_MESSAGES/ -rw-r--r-- root/root 1923 2015-09-02 09:48 ./usr/share/locale/cs/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/da/ drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/da/LC_MESSAGES/ -rw-r--r-- root/root 6848 2015-09-02 09:48 ./usr/share/locale/da/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/de/ drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/de/LC_MESSAGES/ -rw-r--r-- root/root 7590 2015-09-02 09:48 ./usr/share/locale/de/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/es/ drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/es/LC_MESSAGES/ -rw-r--r-- root/root 7957 2015-09-02 09:48 ./usr/share/locale/es/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/et/ drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/et/LC_MESSAGES/ -rw-r--r-- root/root 3068 2015-09-02 09:48 ./usr/share/locale/et/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/fi/ drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/fi/LC_MESSAGES/ -rw-r--r-- root/root 5445 2015-09-02 09:48 ./usr/share/locale/fi/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/fo/ drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/fo/LC_MESSAGES/ -rw-r--r-- root/root 5709 2015-09-02 09:48 ./usr/share/locale/fo/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/fr/ drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/fr/LC_MESSAGES/ -rw-r--r-- root/root 7813 2015-09-02 09:48 ./usr/share/locale/fr/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/gl/ drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/gl/LC_MESSAGES/ -rw-r--r-- root/root 7629 2015-09-02 09:48 ./usr/share/locale/gl/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/he/ drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/he/LC_MESSAGES/ -rw-r--r-- root/root 7974 2015-09-02 09:48 ./usr/share/locale/he/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/hi/ drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/hi/LC_MESSAGES/ -rw-r--r-- root/root 5476 2015-09-02 09:48 ./usr/share/locale/hi/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/hu/ drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/hu/LC_MESSAGES/ -rw-r--r-- root/root 7822 2015-09-02 09:48 ./usr/share/locale/hu/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/id/ drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/id/LC_MESSAGES/ -rw-r--r-- root/root 5563 2015-09-02 09:48 ./usr/share/locale/id/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/it/ drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/it/LC_MESSAGES/ -rw-r--r-- root/root 459 2015-09-02 09:48 ./usr/share/locale/it/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/ja/ drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/ja/LC_MESSAGES/ -rw-r--r-- root/root 7389 2015-09-02 09:48 ./usr/share/locale/ja/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/ka/ drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/ka/LC_MESSAGES/ -rw-r--r-- root/root 11116 2015-09-02 09:48 ./usr/share/locale/ka/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/la/ drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/la/LC_MESSAGES/ -rw-r--r-- root/root 1076 2015-09-02 09:48 ./usr/share/locale/la/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/ms/ drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/ms/LC_MESSAGES/ -rw-r--r-- root/root 7407 2015-09-02 09:48 ./usr/share/locale/ms/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/nb/ drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/nb/LC_MESSAGES/ -rw-r--r-- root/root 7270 2015-09-02 09:48 ./usr/share/locale/nb/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/nl/ drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/nl/LC_MESSAGES/ -rw-r--r-- root/root 6482 2015-09-02 09:48 ./usr/share/locale/nl/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/nn/ drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/nn/LC_MESSAGES/ -rw-r--r-- root/root 3213 2015-09-02 09:48 ./usr/share/locale/nn/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/pl/ drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/pl/LC_MESSAGES/ -rw-r--r-- root/root 6879 2015-09-02 09:48 ./usr/share/locale/pl/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/pt/ drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/pt/LC_MESSAGES/ -rw-r--r-- root/root 1535 2015-09-02 09:48 ./usr/share/locale/pt/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/pt_BR/ drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/pt_BR/LC_MESSAGES/ -rw-r--r-- root/root 7938 2015-09-02 09:48 ./usr/share/locale/pt_BR/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/ru/ drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/ru/LC_MESSAGES/ -rw-r--r-- root/root 9462 2015-09-02 09:48 ./usr/share/locale/ru/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/si/ drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/si/LC_MESSAGES/ -rw-r--r-- root/root 11093 2015-09-02 09:48 ./usr/share/locale/si/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/sv/ drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/sv/LC_MESSAGES/ -rw-r--r-- root/root 3986 2015-09-02 09:48 ./usr/share/locale/sv/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/tr/ drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/tr/LC_MESSAGES/ -rw-r--r-- root/root 7668 2015-09-02 09:48 ./usr/share/locale/tr/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/uk/ drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/uk/LC_MESSAGES/ -rw-r--r-- root/root 9165 2015-09-02 09:48 ./usr/share/locale/uk/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/zh_CN/ drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/zh_CN/LC_MESSAGES/ -rw-r--r-- root/root 7161 2015-09-02 09:48 ./usr/share/locale/zh_CN/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/zh_TW/ drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/locale/zh_TW/LC_MESSAGES/ -rw-r--r-- root/root 7172 2015-09-02 09:48 ./usr/share/locale/zh_TW/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/man/ drwxr-xr-x root/root 0 2015-09-02 09:48 ./usr/share/man/man1/ -rw-r--r-- root/root 554 2015-09-02 09:48 ./usr/share/man/man1/alarm-clock-applet.1.gz ┌──────────────────────────────────────────────────────────────────────────────┐ │ Post Build │ └──────────────────────────────────────────────────────────────────────────────┘ ┌──────────────────────────────────────────────────────────────────────────────┐ │ Cleanup │ └──────────────────────────────────────────────────────────────────────────────┘ Not removing build depends: as requested Keeping session: ┌──────────────────────────────────────────────────────────────────────────────┐ │ Summary │ └──────────────────────────────────────────────────────────────────────────────┘ Build Architecture: ppc64el Build-Space: 5436 Build-Time: 17 Distribution: wily Host Architecture: ppc64el Install-Time: 82 Job: alarm-clock-applet_0.3.4-1.dsc Machine Architecture: ppc64el Package: alarm-clock-applet Package-Time: 100 Source-Version: 0.3.4-1 Space: 5436 Status: successful Version: 0.3.4-1 ──────────────────────────────────────────────────────────────────────────────── Finished at 20150902-0948 Build needed 00:01:40, 5436k disc space RUN: /usr/share/launchpad-buildd/slavebin/scan-for-processes ['scan-for-processes', 'PACKAGEBUILD-7857231'] Scanning for processes to kill in build /home/buildd/build-PACKAGEBUILD-7857231/chroot-autobuild... RUN: /usr/share/launchpad-buildd/slavebin/umount-chroot ['umount-chroot', 'PACKAGEBUILD-7857231'] Unmounting chroot for build PACKAGEBUILD-7857231... RUN: /usr/share/launchpad-buildd/slavebin/remove-build ['remove-build', 'PACKAGEBUILD-7857231'] Removing build PACKAGEBUILD-7857231