RUN: /usr/share/launchpad-buildd/slavebin/slave-prep Forking launchpad-buildd slave process... Kernel version: Linux bos02-s390x-020 4.4.0-104-generic #127-Ubuntu SMP Mon Dec 11 12:16:43 UTC 2017 s390x Buildd toolchain package versions: launchpad-buildd_157 python-lpbuildd_157 sbuild_0.67.0-2ubuntu7.1 bzr-builder_0.7.3+bzr174~ppa13~ubuntu14.10.1 bzr_2.7.0-2ubuntu3.1 git-build-recipe_0.3.4~git201611291343.dcee459~ubuntu16.04.1 git_1:2.7.4-0ubuntu1.3 dpkg-dev_1.18.4ubuntu1.3 python-debian_0.1.27ubuntu2. Syncing the system clock with the buildd NTP service... 23 Dec 10:53:48 ntpdate[1755]: adjust time server 10.211.37.1 offset 0.000184 sec RUN: /usr/share/launchpad-buildd/slavebin/in-target unpack-chroot --backend=chroot --series=bionic --arch=s390x PACKAGEBUILD-13886866 /home/buildd/filecache-default/c63540de4962374dad549ddd7685c5c502845718 Creating target for build PACKAGEBUILD-13886866 RUN: /usr/share/launchpad-buildd/slavebin/in-target mount-chroot --backend=chroot --series=bionic --arch=s390x PACKAGEBUILD-13886866 Starting target for build PACKAGEBUILD-13886866 RUN: /usr/share/launchpad-buildd/slavebin/in-target override-sources-list --backend=chroot --series=bionic --arch=s390x PACKAGEBUILD-13886866 'deb http://ftpmaster.internal/ubuntu bionic main restricted universe multiverse' 'deb http://ftpmaster.internal/ubuntu bionic-security main restricted universe multiverse' 'deb http://ftpmaster.internal/ubuntu bionic-updates main restricted universe multiverse' Overriding sources.list in build-PACKAGEBUILD-13886866 RUN: /usr/share/launchpad-buildd/slavebin/in-target update-debian-chroot --backend=chroot --series=bionic --arch=s390x PACKAGEBUILD-13886866 Updating target for build PACKAGEBUILD-13886866 Get:1 http://ftpmaster.internal/ubuntu bionic InRelease [235 kB] Get:2 http://ftpmaster.internal/ubuntu bionic-security InRelease [65.4 kB] Get:3 http://ftpmaster.internal/ubuntu bionic-updates InRelease [65.4 kB] Get:4 http://ftpmaster.internal/ubuntu bionic/main s390x Packages [943 kB] Get:5 http://ftpmaster.internal/ubuntu bionic/main Translation-en [517 kB] Get:6 http://ftpmaster.internal/ubuntu bionic/restricted Translation-en [2788 B] Get:7 http://ftpmaster.internal/ubuntu bionic/universe s390x Packages [8034 kB] Get:8 http://ftpmaster.internal/ubuntu bionic/universe Translation-en [4917 kB] Get:9 http://ftpmaster.internal/ubuntu bionic/multiverse s390x Packages [124 kB] Get:10 http://ftpmaster.internal/ubuntu bionic/multiverse Translation-en [109 kB] Fetched 15.0 MB in 3s (4534 kB/s) Reading package lists... Reading package lists... Building dependency tree... Reading state information... Calculating upgrade... The following packages were automatically installed and are no longer required: libasn1-8-heimdal libcurl3-gnutls libgssapi-krb5-2 libgssapi3-heimdal libhcrypto4-heimdal libheimbase1-heimdal libheimntlm0-heimdal libhx509-5-heimdal libidn2-0 libk5crypto3 libkeyutils1 libkrb5-26-heimdal libkrb5-3 libkrb5support0 libldap-2.4-2 libldap-common libnghttp2-14 libpsl5 libroken18-heimdal librtmp1 libsasl2-2 libsasl2-modules-db libunistring0 libwind0-heimdal Use 'sudo apt autoremove' to remove them. The following NEW packages will be installed: libnghttp2-14 The following packages will be upgraded: adduser apt apt-transport-https base-files base-passwd binutils binutils-common binutils-s390x-linux-gnu bsdutils build-essential coreutils cpp-7 debconf debianutils dpkg dpkg-dev e2fslibs e2fsprogs fdisk findutils g++-7 gcc-7 gcc-7-base gnupg gnupg-agent gpgv libapparmor1 libapt-pkg5.0 libasn1-8-heimdal libassuan0 libatomic1 libbinutils libblkid1 libc-bin libc-dev-bin libc6 libc6-dev libcap-ng0 libcap2 libcc1-0 libcomerr2 libcurl3-gnutls libdpkg-perl libfdisk1 libgcc-7-dev libgcc1 libgcrypt20 libgomp1 libgpg-error0 libgssapi3-heimdal libhcrypto4-heimdal libheimbase1-heimdal libheimntlm0-heimdal libhogweed4 libhx509-5-heimdal libidn11 libidn2-0 libip4tc0 libitm1 libkeyutils1 libkrb5-26-heimdal liblockfile-bin liblockfile1 libmount1 libnettle6 libnpth0 libp11-kit0 libpcre3 libperl5.26 libpng16-16 libpsl5 libroken18-heimdal libseccomp2 libselinux1 libsemanage-common libsemanage1 libsmartcols1 libsqlite3-0 libss2 libssl1.0.0 libstdc++-7-dev libstdc++6 libsystemd0 libtasn1-6 libudev1 libuuid1 libwind0-heimdal linux-libc-dev lsb-base mount multiarch-support openssl optipng perl perl-base perl-modules-5.26 pinentry-curses sensible-utils systemd systemd-sysv sysvinit-utils tzdata util-linux 103 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 51.7 MB of archives. After this operation, 845 kB of additional disk space will be used. Get:1 http://ftpmaster.internal/ubuntu bionic/main s390x base-files s390x 10ubuntu1 [55.9 kB] Get:2 http://ftpmaster.internal/ubuntu bionic/main s390x bsdutils s390x 1:2.30.2-0.1ubuntu1 [57.9 kB] Get:3 http://ftpmaster.internal/ubuntu bionic/main s390x coreutils s390x 8.26-3ubuntu4 [1197 kB] Get:4 http://ftpmaster.internal/ubuntu bionic/main s390x debianutils s390x 4.8.3 [85.4 kB] Get:5 http://ftpmaster.internal/ubuntu bionic/main s390x dpkg s390x 1.19.0.4ubuntu1 [1122 kB] Get:6 http://ftpmaster.internal/ubuntu bionic/main s390x libc6-dev s390x 2.26-0ubuntu2 [2022 kB] Get:7 http://ftpmaster.internal/ubuntu bionic/main s390x libc-dev-bin s390x 2.26-0ubuntu2 [62.8 kB] Get:8 http://ftpmaster.internal/ubuntu bionic/main s390x linux-libc-dev s390x 4.13.0-17.20 [957 kB] Get:9 http://ftpmaster.internal/ubuntu bionic/main s390x libgomp1 s390x 7.2.0-18ubuntu2 [70.0 kB] Get:10 http://ftpmaster.internal/ubuntu bionic/main s390x libitm1 s390x 7.2.0-18ubuntu2 [26.9 kB] Get:11 http://ftpmaster.internal/ubuntu bionic/main s390x gcc-7-base s390x 7.2.0-18ubuntu2 [19.1 kB] Get:12 http://ftpmaster.internal/ubuntu bionic/main s390x libgcc1 s390x 1:7.2.0-18ubuntu2 [25.2 kB] Get:13 http://ftpmaster.internal/ubuntu bionic/main s390x libatomic1 s390x 7.2.0-18ubuntu2 [8240 B] Get:14 http://ftpmaster.internal/ubuntu bionic/main s390x cpp-7 s390x 7.2.0-18ubuntu2 [5175 kB] Get:15 http://ftpmaster.internal/ubuntu bionic/main s390x libcc1-0 s390x 7.2.0-18ubuntu2 [37.7 kB] Get:16 http://ftpmaster.internal/ubuntu bionic/main s390x g++-7 s390x 7.2.0-18ubuntu2 [5971 kB] Get:17 http://ftpmaster.internal/ubuntu bionic/main s390x gcc-7 s390x 7.2.0-18ubuntu2 [5845 kB] Get:18 http://ftpmaster.internal/ubuntu bionic/main s390x libgcc-7-dev s390x 7.2.0-18ubuntu2 [279 kB] Get:19 http://ftpmaster.internal/ubuntu bionic/main s390x libstdc++-7-dev s390x 7.2.0-18ubuntu2 [1447 kB] Get:20 http://ftpmaster.internal/ubuntu bionic/main s390x libstdc++6 s390x 7.2.0-18ubuntu2 [398 kB] Get:21 http://ftpmaster.internal/ubuntu bionic/main s390x libbinutils s390x 2.29.1-12ubuntu1 [304 kB] Get:22 http://ftpmaster.internal/ubuntu bionic/main s390x binutils s390x 2.29.1-12ubuntu1 [3360 B] Get:23 http://ftpmaster.internal/ubuntu bionic/main s390x binutils-common s390x 2.29.1-12ubuntu1 [190 kB] Get:24 http://ftpmaster.internal/ubuntu bionic/main s390x binutils-s390x-linux-gnu s390x 2.29.1-12ubuntu1 [1696 kB] Get:25 http://ftpmaster.internal/ubuntu bionic/main s390x libc6 s390x 2.26-0ubuntu2 [2342 kB] Get:26 http://ftpmaster.internal/ubuntu bionic/main s390x e2fslibs s390x 1.43.7-1 [153 kB] Get:27 http://ftpmaster.internal/ubuntu bionic/main s390x e2fsprogs s390x 1.43.7-1 [477 kB] Get:28 http://ftpmaster.internal/ubuntu bionic/main s390x findutils s390x 4.6.0+git+20170828-2 [287 kB] Get:29 http://ftpmaster.internal/ubuntu bionic/main s390x perl-modules-5.26 all 5.26.1-3 [2761 kB] Get:30 http://ftpmaster.internal/ubuntu bionic/main s390x libperl5.26 s390x 5.26.1-3 [3372 kB] Get:31 http://ftpmaster.internal/ubuntu bionic/main s390x perl s390x 5.26.1-3 [201 kB] Get:32 http://ftpmaster.internal/ubuntu bionic/main s390x perl-base s390x 5.26.1-3 [1310 kB] Get:33 http://ftpmaster.internal/ubuntu bionic/main s390x libuuid1 s390x 2.30.2-0.1ubuntu1 [14.9 kB] Get:34 http://ftpmaster.internal/ubuntu bionic/main s390x libblkid1 s390x 2.30.2-0.1ubuntu1 [112 kB] Get:35 http://ftpmaster.internal/ubuntu bionic/main s390x libsmartcols1 s390x 2.30.2-0.1ubuntu1 [74.9 kB] Get:36 http://ftpmaster.internal/ubuntu bionic/main s390x libfdisk1 s390x 2.30.2-0.1ubuntu1 [145 kB] Get:37 http://ftpmaster.internal/ubuntu bionic/main s390x libpcre3 s390x 2:8.39-8 [154 kB] Get:38 http://ftpmaster.internal/ubuntu bionic/main s390x libselinux1 s390x 2.7-2 [64.0 kB] Get:39 http://ftpmaster.internal/ubuntu bionic/main s390x libmount1 s390x 2.30.2-0.1ubuntu1 [122 kB] Get:40 http://ftpmaster.internal/ubuntu bionic/main s390x fdisk s390x 2.30.2-0.1ubuntu1 [100 kB] Get:41 http://ftpmaster.internal/ubuntu bionic/main s390x util-linux s390x 2.30.2-0.1ubuntu1 [845 kB] Get:42 http://ftpmaster.internal/ubuntu bionic/main s390x base-passwd s390x 3.5.44 [46.2 kB] Get:43 http://ftpmaster.internal/ubuntu bionic/main s390x libc-bin s390x 2.26-0ubuntu2 [540 kB] Get:44 http://ftpmaster.internal/ubuntu bionic/main s390x sysvinit-utils s390x 2.88dsf-59.10ubuntu1 [18.2 kB] Get:45 http://ftpmaster.internal/ubuntu bionic/main s390x libudev1 s390x 235-3ubuntu2 [51.4 kB] Get:46 http://ftpmaster.internal/ubuntu bionic/main s390x libapt-pkg5.0 s390x 1.6~alpha5 [724 kB] Get:47 http://ftpmaster.internal/ubuntu bionic/main s390x debconf all 1.5.65 [124 kB] Get:48 http://ftpmaster.internal/ubuntu bionic/main s390x adduser all 3.116ubuntu1 [163 kB] Get:49 http://ftpmaster.internal/ubuntu bionic/main s390x libgpg-error0 s390x 1.27-5 [35.4 kB] Get:50 http://ftpmaster.internal/ubuntu bionic/main s390x libgcrypt20 s390x 1.8.1-4 [350 kB] Get:51 http://ftpmaster.internal/ubuntu bionic/main s390x gpgv s390x 2.1.15-1ubuntu8 [171 kB] Get:52 http://ftpmaster.internal/ubuntu bionic/main s390x libseccomp2 s390x 2.3.1-2.1ubuntu3 [40.8 kB] Get:53 http://ftpmaster.internal/ubuntu bionic/main s390x apt s390x 1.6~alpha5 [1111 kB] Get:54 http://ftpmaster.internal/ubuntu bionic/main s390x libapparmor1 s390x 2.11.0-2ubuntu18 [27.8 kB] Get:55 http://ftpmaster.internal/ubuntu bionic/main s390x libcap2 s390x 1:2.25-1.2 [13.2 kB] Get:56 http://ftpmaster.internal/ubuntu bionic/main s390x libidn11 s390x 1.33-2.1 [44.3 kB] Get:57 http://ftpmaster.internal/ubuntu bionic/main s390x libip4tc0 s390x 1.6.1-2ubuntu2 [19.3 kB] Get:58 http://ftpmaster.internal/ubuntu bionic/main s390x mount s390x 2.30.2-0.1ubuntu1 [106 kB] Get:59 http://ftpmaster.internal/ubuntu bionic/main s390x systemd s390x 235-3ubuntu2 [2569 kB] Get:60 http://ftpmaster.internal/ubuntu bionic/main s390x libsystemd0 s390x 235-3ubuntu2 [180 kB] Get:61 http://ftpmaster.internal/ubuntu bionic/main s390x systemd-sysv s390x 235-3ubuntu2 [13.1 kB] Get:62 http://ftpmaster.internal/ubuntu bionic/main s390x libcap-ng0 s390x 0.7.7-3.1 [10.7 kB] Get:63 http://ftpmaster.internal/ubuntu bionic/main s390x libcomerr2 s390x 1.43.7-1 [11.3 kB] Get:64 http://ftpmaster.internal/ubuntu bionic/main s390x libsemanage-common all 2.7-2 [6916 B] Get:65 http://ftpmaster.internal/ubuntu bionic/main s390x libsemanage1 s390x 2.7-2 [78.6 kB] Get:66 http://ftpmaster.internal/ubuntu bionic/main s390x libss2 s390x 1.43.7-1 [10.7 kB] Get:67 http://ftpmaster.internal/ubuntu bionic/main s390x libnettle6 s390x 3.3-2 [103 kB] Get:68 http://ftpmaster.internal/ubuntu bionic/main s390x libhogweed4 s390x 3.3-2 [134 kB] Get:69 http://ftpmaster.internal/ubuntu bionic/main s390x libp11-kit0 s390x 0.23.9-2 [188 kB] Get:70 http://ftpmaster.internal/ubuntu bionic/main s390x libtasn1-6 s390x 4.12-3 [34.2 kB] Get:71 http://ftpmaster.internal/ubuntu bionic/main s390x lsb-base all 9.20170808ubuntu1 [12.5 kB] Get:72 http://ftpmaster.internal/ubuntu bionic/main s390x sensible-utils all 0.0.11 [14.8 kB] Get:73 http://ftpmaster.internal/ubuntu bionic/main s390x libassuan0 s390x 2.5.1-1 [32.0 kB] Get:74 http://ftpmaster.internal/ubuntu bionic/main s390x pinentry-curses s390x 1.0.0-3 [33.3 kB] Get:75 http://ftpmaster.internal/ubuntu bionic/main s390x libnpth0 s390x 1.5-3 [7512 B] Get:76 http://ftpmaster.internal/ubuntu bionic/main s390x gnupg s390x 2.1.15-1ubuntu8 [733 kB] Get:77 http://ftpmaster.internal/ubuntu bionic/main s390x gnupg-agent s390x 2.1.15-1ubuntu8 [233 kB] Get:78 http://ftpmaster.internal/ubuntu bionic/main s390x libsqlite3-0 s390x 3.21.0-1 [460 kB] Get:79 http://ftpmaster.internal/ubuntu bionic/main s390x libroken18-heimdal s390x 7.5.0+dfsg-1 [39.4 kB] Get:80 http://ftpmaster.internal/ubuntu bionic/main s390x libasn1-8-heimdal s390x 7.5.0+dfsg-1 [147 kB] Get:81 http://ftpmaster.internal/ubuntu bionic/main s390x libheimbase1-heimdal s390x 7.5.0+dfsg-1 [27.5 kB] Get:82 http://ftpmaster.internal/ubuntu bionic/main s390x libhcrypto4-heimdal s390x 7.5.0+dfsg-1 [82.4 kB] Get:83 http://ftpmaster.internal/ubuntu bionic/main s390x libwind0-heimdal s390x 7.5.0+dfsg-1 [47.7 kB] Get:84 http://ftpmaster.internal/ubuntu bionic/main s390x libhx509-5-heimdal s390x 7.5.0+dfsg-1 [98.3 kB] Get:85 http://ftpmaster.internal/ubuntu bionic/main s390x libkrb5-26-heimdal s390x 7.5.0+dfsg-1 [190 kB] Get:86 http://ftpmaster.internal/ubuntu bionic/main s390x libheimntlm0-heimdal s390x 7.5.0+dfsg-1 [14.1 kB] Get:87 http://ftpmaster.internal/ubuntu bionic/main s390x libgssapi3-heimdal s390x 7.5.0+dfsg-1 [86.9 kB] Get:88 http://ftpmaster.internal/ubuntu bionic/main s390x libssl1.0.0 s390x 1.0.2g-1ubuntu14 [771 kB] Get:89 http://ftpmaster.internal/ubuntu bionic/main s390x multiarch-support s390x 2.26-0ubuntu2 [6832 B] Get:90 http://ftpmaster.internal/ubuntu bionic/main s390x openssl s390x 1.0.2g-1ubuntu14 [477 kB] Get:91 http://ftpmaster.internal/ubuntu bionic/main s390x tzdata all 2017c-1 [188 kB] Get:92 http://ftpmaster.internal/ubuntu bionic/main s390x libidn2-0 s390x 2.0.4-1 [91.2 kB] Get:93 http://ftpmaster.internal/ubuntu bionic/main s390x libkeyutils1 s390x 1.5.9-9.2ubuntu1 [9092 B] Get:94 http://ftpmaster.internal/ubuntu bionic/main s390x libpng16-16 s390x 1.6.34-1 [171 kB] Get:95 http://ftpmaster.internal/ubuntu bionic/universe s390x apt-transport-https all 1.6~alpha5 [1692 B] Get:96 http://ftpmaster.internal/ubuntu bionic/main s390x dpkg-dev all 1.19.0.4ubuntu1 [607 kB] Get:97 http://ftpmaster.internal/ubuntu bionic/main s390x libdpkg-perl all 1.19.0.4ubuntu1 [211 kB] Get:98 http://ftpmaster.internal/ubuntu bionic/main s390x build-essential s390x 12.4ubuntu1 [4754 B] Get:99 http://ftpmaster.internal/ubuntu bionic/main s390x libnghttp2-14 s390x 1.28.0-1 [74.1 kB] Get:100 http://ftpmaster.internal/ubuntu bionic/main s390x libpsl5 s390x 0.19.1-4 [40.9 kB] Get:101 http://ftpmaster.internal/ubuntu bionic/main s390x libcurl3-gnutls s390x 7.57.0-1ubuntu1 [193 kB] Get:102 http://ftpmaster.internal/ubuntu bionic/main s390x liblockfile-bin s390x 1.14-1.1 [11.8 kB] Get:103 http://ftpmaster.internal/ubuntu bionic/main s390x liblockfile1 s390x 1.14-1.1 [6532 B] Get:104 http://ftpmaster.internal/ubuntu bionic/main s390x optipng s390x 0.7.6-1.1 [82.0 kB] debconf: delaying package configuration, since apt-utils is not installed Fetched 51.7 MB in 1s (33.7 MB/s) (Reading database ... 12436 files and directories currently installed.) Preparing to unpack .../base-files_10ubuntu1_s390x.deb ... Unpacking base-files (10ubuntu1) over (9.6ubuntu101) ... Setting up base-files (10ubuntu1) ... Installing new version of config file /etc/debian_version ... Installing new version of config file /etc/issue ... Installing new version of config file /etc/issue.net ... Installing new version of config file /etc/lsb-release ... (Reading database ... 12436 files and directories currently installed.) Preparing to unpack .../bsdutils_1%3a2.30.2-0.1ubuntu1_s390x.deb ... Unpacking bsdutils (1:2.30.2-0.1ubuntu1) over (1:2.30.1-0ubuntu4) ... Setting up bsdutils (1:2.30.2-0.1ubuntu1) ... (Reading database ... 12436 files and directories currently installed.) Preparing to unpack .../coreutils_8.26-3ubuntu4_s390x.deb ... Unpacking coreutils (8.26-3ubuntu4) over (8.26-3ubuntu3) ... Setting up coreutils (8.26-3ubuntu4) ... (Reading database ... 12436 files and directories currently installed.) Preparing to unpack .../debianutils_4.8.3_s390x.deb ... Unpacking debianutils (4.8.3) over (4.8.2) ... Setting up debianutils (4.8.3) ... (Reading database ... 12436 files and directories currently installed.) Preparing to unpack .../dpkg_1.19.0.4ubuntu1_s390x.deb ... Unpacking dpkg (1.19.0.4ubuntu1) over (1.18.24ubuntu1) ... Setting up dpkg (1.19.0.4ubuntu1) ... Installing new version of config file /etc/alternatives/README ... Installing new version of config file /etc/cron.daily/dpkg ... Installing new version of config file /etc/logrotate.d/dpkg ... (Reading database ... 12438 files and directories currently installed.) Preparing to unpack .../0-libc6-dev_2.26-0ubuntu2_s390x.deb ... Unpacking libc6-dev:s390x (2.26-0ubuntu2) over (2.26-0ubuntu1) ... Preparing to unpack .../1-libc-dev-bin_2.26-0ubuntu2_s390x.deb ... Unpacking libc-dev-bin (2.26-0ubuntu2) over (2.26-0ubuntu1) ... Preparing to unpack .../2-linux-libc-dev_4.13.0-17.20_s390x.deb ... Unpacking linux-libc-dev:s390x (4.13.0-17.20) over (4.13.0-11.12) ... Preparing to unpack .../3-libgomp1_7.2.0-18ubuntu2_s390x.deb ... Unpacking libgomp1:s390x (7.2.0-18ubuntu2) over (7.2.0-6ubuntu1) ... Preparing to unpack .../4-libitm1_7.2.0-18ubuntu2_s390x.deb ... Unpacking libitm1:s390x (7.2.0-18ubuntu2) over (7.2.0-6ubuntu1) ... Preparing to unpack .../5-gcc-7-base_7.2.0-18ubuntu2_s390x.deb ... Unpacking gcc-7-base:s390x (7.2.0-18ubuntu2) over (7.2.0-6ubuntu1) ... Setting up gcc-7-base:s390x (7.2.0-18ubuntu2) ... (Reading database ... 12438 files and directories currently installed.) Preparing to unpack .../libgcc1_1%3a7.2.0-18ubuntu2_s390x.deb ... Unpacking libgcc1:s390x (1:7.2.0-18ubuntu2) over (1:7.2.0-6ubuntu1) ... Setting up libgcc1:s390x (1:7.2.0-18ubuntu2) ... (Reading database ... 12438 files and directories currently installed.) Preparing to unpack .../0-libatomic1_7.2.0-18ubuntu2_s390x.deb ... Unpacking libatomic1:s390x (7.2.0-18ubuntu2) over (7.2.0-6ubuntu1) ... Preparing to unpack .../1-cpp-7_7.2.0-18ubuntu2_s390x.deb ... Unpacking cpp-7 (7.2.0-18ubuntu2) over (7.2.0-6ubuntu1) ... Preparing to unpack .../2-libcc1-0_7.2.0-18ubuntu2_s390x.deb ... Unpacking libcc1-0:s390x (7.2.0-18ubuntu2) over (7.2.0-6ubuntu1) ... Preparing to unpack .../3-g++-7_7.2.0-18ubuntu2_s390x.deb ... Unpacking g++-7 (7.2.0-18ubuntu2) over (7.2.0-6ubuntu1) ... Preparing to unpack .../4-gcc-7_7.2.0-18ubuntu2_s390x.deb ... Unpacking gcc-7 (7.2.0-18ubuntu2) over (7.2.0-6ubuntu1) ... Preparing to unpack .../5-libgcc-7-dev_7.2.0-18ubuntu2_s390x.deb ... Unpacking libgcc-7-dev:s390x (7.2.0-18ubuntu2) over (7.2.0-6ubuntu1) ... Preparing to unpack .../6-libstdc++-7-dev_7.2.0-18ubuntu2_s390x.deb ... Unpacking libstdc++-7-dev:s390x (7.2.0-18ubuntu2) over (7.2.0-6ubuntu1) ... Preparing to unpack .../7-libstdc++6_7.2.0-18ubuntu2_s390x.deb ... Unpacking libstdc++6:s390x (7.2.0-18ubuntu2) over (7.2.0-6ubuntu1) ... Setting up libstdc++6:s390x (7.2.0-18ubuntu2) ... (Reading database ... 12442 files and directories currently installed.) Preparing to unpack .../libbinutils_2.29.1-12ubuntu1_s390x.deb ... Unpacking libbinutils:s390x (2.29.1-12ubuntu1) over (2.29.1-1ubuntu1) ... Preparing to unpack .../binutils_2.29.1-12ubuntu1_s390x.deb ... Unpacking binutils (2.29.1-12ubuntu1) over (2.29.1-1ubuntu1) ... Preparing to unpack .../binutils-common_2.29.1-12ubuntu1_s390x.deb ... Unpacking binutils-common:s390x (2.29.1-12ubuntu1) over (2.29.1-1ubuntu1) ... Preparing to unpack .../binutils-s390x-linux-gnu_2.29.1-12ubuntu1_s390x.deb ... Unpacking binutils-s390x-linux-gnu (2.29.1-12ubuntu1) over (2.29.1-1ubuntu1) ... Preparing to unpack .../libc6_2.26-0ubuntu2_s390x.deb ... Unpacking libc6:s390x (2.26-0ubuntu2) over (2.26-0ubuntu1) ... Setting up libc6:s390x (2.26-0ubuntu2) ... (Reading database ... 12442 files and directories currently installed.) Preparing to unpack .../e2fslibs_1.43.7-1_s390x.deb ... Unpacking e2fslibs:s390x (1.43.7-1) over (1.43.5-1) ... Setting up e2fslibs:s390x (1.43.7-1) ... (Reading database ... 12442 files and directories currently installed.) Preparing to unpack .../e2fsprogs_1.43.7-1_s390x.deb ... Unpacking e2fsprogs (1.43.7-1) over (1.43.5-1) ... Setting up e2fsprogs (1.43.7-1) ... Installing new version of config file /etc/mke2fs.conf ... (Reading database ... 12442 files and directories currently installed.) Preparing to unpack .../findutils_4.6.0+git+20170828-2_s390x.deb ... Unpacking findutils (4.6.0+git+20170828-2) over (4.6.0+git+20170729-2) ... Setting up findutils (4.6.0+git+20170828-2) ... (Reading database ... 12442 files and directories currently installed.) Preparing to unpack .../perl_5.26.1-3_s390x.deb ... Unpacking perl (5.26.1-3) over (5.26.0-8ubuntu1) ... Preparing to unpack .../perl-modules-5.26_5.26.1-3_all.deb ... Unpacking perl-modules-5.26 (5.26.1-3) over (5.26.0-8ubuntu1) ... Preparing to unpack .../libperl5.26_5.26.1-3_s390x.deb ... Unpacking libperl5.26:s390x (5.26.1-3) over (5.26.0-8ubuntu1) ... Preparing to unpack .../perl-base_5.26.1-3_s390x.deb ... Unpacking perl-base (5.26.1-3) over (5.26.0-8ubuntu1) ... Setting up perl-base (5.26.1-3) ... (Reading database ... 12442 files and directories currently installed.) Preparing to unpack .../libuuid1_2.30.2-0.1ubuntu1_s390x.deb ... Unpacking libuuid1:s390x (2.30.2-0.1ubuntu1) over (2.30.1-0ubuntu4) ... Setting up libuuid1:s390x (2.30.2-0.1ubuntu1) ... (Reading database ... 12442 files and directories currently installed.) Preparing to unpack .../libblkid1_2.30.2-0.1ubuntu1_s390x.deb ... Unpacking libblkid1:s390x (2.30.2-0.1ubuntu1) over (2.30.1-0ubuntu4) ... Setting up libblkid1:s390x (2.30.2-0.1ubuntu1) ... (Reading database ... 12442 files and directories currently installed.) Preparing to unpack .../libsmartcols1_2.30.2-0.1ubuntu1_s390x.deb ... Unpacking libsmartcols1:s390x (2.30.2-0.1ubuntu1) over (2.30.1-0ubuntu4) ... Setting up libsmartcols1:s390x (2.30.2-0.1ubuntu1) ... (Reading database ... 12442 files and directories currently installed.) Preparing to unpack .../libfdisk1_2.30.2-0.1ubuntu1_s390x.deb ... Unpacking libfdisk1:s390x (2.30.2-0.1ubuntu1) over (2.30.1-0ubuntu4) ... Setting up libfdisk1:s390x (2.30.2-0.1ubuntu1) ... (Reading database ... 12442 files and directories currently installed.) Preparing to unpack .../libpcre3_2%3a8.39-8_s390x.deb ... Unpacking libpcre3:s390x (2:8.39-8) over (2:8.39-4) ... Setting up libpcre3:s390x (2:8.39-8) ... (Reading database ... 12442 files and directories currently installed.) Preparing to unpack .../libselinux1_2.7-2_s390x.deb ... Unpacking libselinux1:s390x (2.7-2) over (2.7-1) ... Setting up libselinux1:s390x (2.7-2) ... (Reading database ... 12442 files and directories currently installed.) Preparing to unpack .../libmount1_2.30.2-0.1ubuntu1_s390x.deb ... Unpacking libmount1:s390x (2.30.2-0.1ubuntu1) over (2.30.1-0ubuntu4) ... Setting up libmount1:s390x (2.30.2-0.1ubuntu1) ... (Reading database ... 12442 files and directories currently installed.) Preparing to unpack .../fdisk_2.30.2-0.1ubuntu1_s390x.deb ... Unpacking fdisk (2.30.2-0.1ubuntu1) over (2.30.1-0ubuntu4) ... Setting up fdisk (2.30.2-0.1ubuntu1) ... (Reading database ... 12442 files and directories currently installed.) Preparing to unpack .../util-linux_2.30.2-0.1ubuntu1_s390x.deb ... Unpacking util-linux (2.30.2-0.1ubuntu1) over (2.30.1-0ubuntu4) ... Setting up util-linux (2.30.2-0.1ubuntu1) ... (Reading database ... 12443 files and directories currently installed.) Preparing to unpack .../base-passwd_3.5.44_s390x.deb ... Unpacking base-passwd (3.5.44) over (3.5.43) ... Setting up base-passwd (3.5.44) ... (Reading database ... 12443 files and directories currently installed.) Preparing to unpack .../libc-bin_2.26-0ubuntu2_s390x.deb ... Unpacking libc-bin (2.26-0ubuntu2) over (2.26-0ubuntu1) ... Setting up libc-bin (2.26-0ubuntu2) ... (Reading database ... 12443 files and directories currently installed.) Preparing to unpack .../sysvinit-utils_2.88dsf-59.10ubuntu1_s390x.deb ... Unpacking sysvinit-utils (2.88dsf-59.10ubuntu1) over (2.88dsf-59.8git1) ... Setting up sysvinit-utils (2.88dsf-59.10ubuntu1) ... (Reading database ... 12443 files and directories currently installed.) Preparing to unpack .../libudev1_235-3ubuntu2_s390x.deb ... Unpacking libudev1:s390x (235-3ubuntu2) over (234-2ubuntu10) ... Setting up libudev1:s390x (235-3ubuntu2) ... (Reading database ... 12443 files and directories currently installed.) Preparing to unpack .../libapt-pkg5.0_1.6~alpha5_s390x.deb ... Unpacking libapt-pkg5.0:s390x (1.6~alpha5) over (1.5~rc4) ... Setting up libapt-pkg5.0:s390x (1.6~alpha5) ... (Reading database ... 12443 files and directories currently installed.) Preparing to unpack .../debconf_1.5.65_all.deb ... Unpacking debconf (1.5.65) over (1.5.63) ... Setting up debconf (1.5.65) ... (Reading database ... 12437 files and directories currently installed.) Preparing to unpack .../adduser_3.116ubuntu1_all.deb ... Unpacking adduser (3.116ubuntu1) over (3.113+nmu3ubuntu5) ... Setting up adduser (3.116ubuntu1) ... (Reading database ... 12435 files and directories currently installed.) Preparing to unpack .../libgpg-error0_1.27-5_s390x.deb ... Unpacking libgpg-error0:s390x (1.27-5) over (1.27-3) ... Setting up libgpg-error0:s390x (1.27-5) ... (Reading database ... 12435 files and directories currently installed.) Preparing to unpack .../libgcrypt20_1.8.1-4_s390x.deb ... Unpacking libgcrypt20:s390x (1.8.1-4) over (1.7.8-2ubuntu1) ... Setting up libgcrypt20:s390x (1.8.1-4) ... (Reading database ... 12435 files and directories currently installed.) Preparing to unpack .../gpgv_2.1.15-1ubuntu8_s390x.deb ... Unpacking gpgv (2.1.15-1ubuntu8) over (2.1.15-1ubuntu7) ... Setting up gpgv (2.1.15-1ubuntu8) ... (Reading database ... 12435 files and directories currently installed.) Preparing to unpack .../libseccomp2_2.3.1-2.1ubuntu3_s390x.deb ... Unpacking libseccomp2:s390x (2.3.1-2.1ubuntu3) over (2.3.1-2.1ubuntu2) ... Setting up libseccomp2:s390x (2.3.1-2.1ubuntu3) ... (Reading database ... 12435 files and directories currently installed.) Preparing to unpack .../apt_1.6~alpha5_s390x.deb ... Unpacking apt (1.6~alpha5) over (1.5~rc4) ... Setting up apt (1.6~alpha5) ... (Reading database ... 12431 files and directories currently installed.) Preparing to unpack .../libapparmor1_2.11.0-2ubuntu18_s390x.deb ... Unpacking libapparmor1:s390x (2.11.0-2ubuntu18) over (2.11.0-2ubuntu17) ... Preparing to unpack .../libcap2_1%3a2.25-1.2_s390x.deb ... Unpacking libcap2:s390x (1:2.25-1.2) over (1:2.25-1) ... Preparing to unpack .../libidn11_1.33-2.1_s390x.deb ... Unpacking libidn11:s390x (1.33-2.1) over (1.33-2) ... Setting up libidn11:s390x (1.33-2.1) ... (Reading database ... 12431 files and directories currently installed.) Preparing to unpack .../libip4tc0_1.6.1-2ubuntu2_s390x.deb ... Unpacking libip4tc0:s390x (1.6.1-2ubuntu2) over (1.6.1-2ubuntu1) ... Preparing to unpack .../mount_2.30.2-0.1ubuntu1_s390x.deb ... Unpacking mount (2.30.2-0.1ubuntu1) over (2.30.1-0ubuntu4) ... Preparing to unpack .../systemd_235-3ubuntu2_s390x.deb ... Unpacking systemd (235-3ubuntu2) over (234-2ubuntu10) ... Preparing to unpack .../libsystemd0_235-3ubuntu2_s390x.deb ... Unpacking libsystemd0:s390x (235-3ubuntu2) over (234-2ubuntu10) ... Setting up libsystemd0:s390x (235-3ubuntu2) ... Setting up libapparmor1:s390x (2.11.0-2ubuntu18) ... Setting up libcap2:s390x (1:2.25-1.2) ... Setting up libip4tc0:s390x (1.6.1-2ubuntu2) ... Setting up mount (2.30.2-0.1ubuntu1) ... Setting up systemd (235-3ubuntu2) ... Installing new version of config file /etc/systemd/journald.conf ... Installing new version of config file /etc/systemd/system.conf ... Removing empty /etc/rc.local Removed /etc/systemd/system/network-online.target.wants/systemd-networkd-wait-online.service. Removing user `systemd-bus-proxy' ... Warning: group `systemd-bus-proxy' has no more members. Done. (Reading database ... 12437 files and directories currently installed.) Preparing to unpack .../systemd-sysv_235-3ubuntu2_s390x.deb ... Unpacking systemd-sysv (235-3ubuntu2) over (234-2ubuntu10) ... Preparing to unpack .../libcap-ng0_0.7.7-3.1_s390x.deb ... Unpacking libcap-ng0:s390x (0.7.7-3.1) over (0.7.7-3build1) ... Setting up libcap-ng0:s390x (0.7.7-3.1) ... (Reading database ... 12437 files and directories currently installed.) Preparing to unpack .../libcomerr2_1.43.7-1_s390x.deb ... Unpacking libcomerr2:s390x (1.43.7-1) over (1.43.5-1) ... Setting up libcomerr2:s390x (1.43.7-1) ... (Reading database ... 12437 files and directories currently installed.) Preparing to unpack .../libsemanage-common_2.7-2_all.deb ... Unpacking libsemanage-common (2.7-2) over (2.7-1) ... Setting up libsemanage-common (2.7-2) ... (Reading database ... 12437 files and directories currently installed.) Preparing to unpack .../libsemanage1_2.7-2_s390x.deb ... Unpacking libsemanage1:s390x (2.7-2) over (2.7-1) ... Setting up libsemanage1:s390x (2.7-2) ... (Reading database ... 12437 files and directories currently installed.) Preparing to unpack .../libss2_1.43.7-1_s390x.deb ... Unpacking libss2:s390x (1.43.7-1) over (1.43.5-1) ... Setting up libss2:s390x (1.43.7-1) ... (Reading database ... 12437 files and directories currently installed.) Preparing to unpack .../libnettle6_3.3-2_s390x.deb ... Unpacking libnettle6:s390x (3.3-2) over (3.3-1) ... Setting up libnettle6:s390x (3.3-2) ... (Reading database ... 12437 files and directories currently installed.) Preparing to unpack .../libhogweed4_3.3-2_s390x.deb ... Unpacking libhogweed4:s390x (3.3-2) over (3.3-1) ... Setting up libhogweed4:s390x (3.3-2) ... (Reading database ... 12437 files and directories currently installed.) Preparing to unpack .../libp11-kit0_0.23.9-2_s390x.deb ... Unpacking libp11-kit0:s390x (0.23.9-2) over (0.23.7-3) ... Setting up libp11-kit0:s390x (0.23.9-2) ... (Reading database ... 12437 files and directories currently installed.) Preparing to unpack .../libtasn1-6_4.12-3_s390x.deb ... Unpacking libtasn1-6:s390x (4.12-3) over (4.12-2.1) ... Setting up libtasn1-6:s390x (4.12-3) ... (Reading database ... 12437 files and directories currently installed.) Preparing to unpack .../00-lsb-base_9.20170808ubuntu1_all.deb ... Unpacking lsb-base (9.20170808ubuntu1) over (9.20160110ubuntu5) ... Preparing to unpack .../01-sensible-utils_0.0.11_all.deb ... Unpacking sensible-utils (0.0.11) over (0.0.10) ... Preparing to unpack .../02-libassuan0_2.5.1-1_s390x.deb ... Unpacking libassuan0:s390x (2.5.1-1) over (2.4.3-3) ... Preparing to unpack .../03-pinentry-curses_1.0.0-3_s390x.deb ... Unpacking pinentry-curses (1.0.0-3) over (1.0.0-2) ... Preparing to unpack .../04-libnpth0_1.5-3_s390x.deb ... Unpacking libnpth0:s390x (1.5-3) over (1.5-2) ... Preparing to unpack .../05-gnupg_2.1.15-1ubuntu8_s390x.deb ... Unpacking gnupg (2.1.15-1ubuntu8) over (2.1.15-1ubuntu7) ... Preparing to unpack .../06-gnupg-agent_2.1.15-1ubuntu8_s390x.deb ... Unpacking gnupg-agent (2.1.15-1ubuntu8) over (2.1.15-1ubuntu7) ... Preparing to unpack .../07-libsqlite3-0_3.21.0-1_s390x.deb ... Unpacking libsqlite3-0:s390x (3.21.0-1) over (3.19.3-3) ... Preparing to unpack .../08-libroken18-heimdal_7.5.0+dfsg-1_s390x.deb ... Unpacking libroken18-heimdal:s390x (7.5.0+dfsg-1) over (7.4.0.dfsg.1-2) ... Preparing to unpack .../09-libasn1-8-heimdal_7.5.0+dfsg-1_s390x.deb ... Unpacking libasn1-8-heimdal:s390x (7.5.0+dfsg-1) over (7.4.0.dfsg.1-2) ... Preparing to unpack .../10-libheimbase1-heimdal_7.5.0+dfsg-1_s390x.deb ... Unpacking libheimbase1-heimdal:s390x (7.5.0+dfsg-1) over (7.4.0.dfsg.1-2) ... Preparing to unpack .../11-libhcrypto4-heimdal_7.5.0+dfsg-1_s390x.deb ... Unpacking libhcrypto4-heimdal:s390x (7.5.0+dfsg-1) over (7.4.0.dfsg.1-2) ... Preparing to unpack .../12-libwind0-heimdal_7.5.0+dfsg-1_s390x.deb ... Unpacking libwind0-heimdal:s390x (7.5.0+dfsg-1) over (7.4.0.dfsg.1-2) ... Preparing to unpack .../13-libhx509-5-heimdal_7.5.0+dfsg-1_s390x.deb ... Unpacking libhx509-5-heimdal:s390x (7.5.0+dfsg-1) over (7.4.0.dfsg.1-2) ... Preparing to unpack .../14-libkrb5-26-heimdal_7.5.0+dfsg-1_s390x.deb ... Unpacking libkrb5-26-heimdal:s390x (7.5.0+dfsg-1) over (7.4.0.dfsg.1-2) ... Preparing to unpack .../15-libheimntlm0-heimdal_7.5.0+dfsg-1_s390x.deb ... Unpacking libheimntlm0-heimdal:s390x (7.5.0+dfsg-1) over (7.4.0.dfsg.1-2) ... Preparing to unpack .../16-libgssapi3-heimdal_7.5.0+dfsg-1_s390x.deb ... Unpacking libgssapi3-heimdal:s390x (7.5.0+dfsg-1) over (7.4.0.dfsg.1-2) ... Preparing to unpack .../17-libssl1.0.0_1.0.2g-1ubuntu14_s390x.deb ... Unpacking libssl1.0.0:s390x (1.0.2g-1ubuntu14) over (1.0.2g-1ubuntu13) ... Preparing to unpack .../18-multiarch-support_2.26-0ubuntu2_s390x.deb ... Unpacking multiarch-support (2.26-0ubuntu2) over (2.26-0ubuntu1) ... Preparing to unpack .../19-openssl_1.0.2g-1ubuntu14_s390x.deb ... Unpacking openssl (1.0.2g-1ubuntu14) over (1.0.2g-1ubuntu13) ... Preparing to unpack .../20-tzdata_2017c-1_all.deb ... Unpacking tzdata (2017c-1) over (2017b-2) ... Preparing to unpack .../21-libidn2-0_2.0.4-1_s390x.deb ... Unpacking libidn2-0:s390x (2.0.4-1) over (2.0.2-5) ... Preparing to unpack .../22-libkeyutils1_1.5.9-9.2ubuntu1_s390x.deb ... Unpacking libkeyutils1:s390x (1.5.9-9.2ubuntu1) over (1.5.9-9ubuntu1) ... Preparing to unpack .../23-libpng16-16_1.6.34-1_s390x.deb ... Unpacking libpng16-16:s390x (1.6.34-1) over (1.6.32-2) ... Preparing to unpack .../24-apt-transport-https_1.6~alpha5_all.deb ... Unpacking apt-transport-https (1.6~alpha5) over (1.5~rc4) ... Preparing to unpack .../25-dpkg-dev_1.19.0.4ubuntu1_all.deb ... Unpacking dpkg-dev (1.19.0.4ubuntu1) over (1.18.24ubuntu1) ... Preparing to unpack .../26-libdpkg-perl_1.19.0.4ubuntu1_all.deb ... Unpacking libdpkg-perl (1.19.0.4ubuntu1) over (1.18.24ubuntu1) ... Preparing to unpack .../27-build-essential_12.4ubuntu1_s390x.deb ... Unpacking build-essential (12.4ubuntu1) over (12.1ubuntu2) ... Selecting previously unselected package libnghttp2-14:s390x. Preparing to unpack .../28-libnghttp2-14_1.28.0-1_s390x.deb ... Unpacking libnghttp2-14:s390x (1.28.0-1) ... Preparing to unpack .../29-libpsl5_0.19.1-4_s390x.deb ... Unpacking libpsl5:s390x (0.19.1-4) over (0.18.0-2) ... Preparing to unpack .../30-libcurl3-gnutls_7.57.0-1ubuntu1_s390x.deb ... Unpacking libcurl3-gnutls:s390x (7.57.0-1ubuntu1) over (7.55.1-1ubuntu1) ... Preparing to unpack .../31-liblockfile-bin_1.14-1.1_s390x.deb ... Unpacking liblockfile-bin (1.14-1.1) over (1.14-1) ... Preparing to unpack .../32-liblockfile1_1.14-1.1_s390x.deb ... Unpacking liblockfile1:s390x (1.14-1.1) over (1.14-1) ... Preparing to unpack .../33-optipng_0.7.6-1.1_s390x.deb ... Unpacking optipng (0.7.6-1.1) over (0.7.6-1build1) ... Setting up libnpth0:s390x (1.5-3) ... Setting up libgomp1:s390x (7.2.0-18ubuntu2) ... Setting up libatomic1:s390x (7.2.0-18ubuntu2) ... Setting up liblockfile-bin (1.14-1.1) ... Setting up libcc1-0:s390x (7.2.0-18ubuntu2) ... Setting up apt-transport-https (1.6~alpha5) ... Setting up libidn2-0:s390x (2.0.4-1) ... Setting up libssl1.0.0:s390x (1.0.2g-1ubuntu14) ... Setting up libnghttp2-14:s390x (1.28.0-1) ... Setting up libpng16-16:s390x (1.6.34-1) ... Setting up libpsl5:s390x (0.19.1-4) ... Setting up multiarch-support (2.26-0ubuntu2) ... Setting up tzdata (2017c-1) ... Current default time zone: 'Etc/UTC' Local time is now: Sat Dec 23 10:54:07 UTC 2017. Universal Time is now: Sat Dec 23 10:54:07 UTC 2017. Run 'dpkg-reconfigure tzdata' if you wish to change it. Setting up systemd-sysv (235-3ubuntu2) ... Setting up liblockfile1:s390x (1.14-1.1) ... Setting up linux-libc-dev:s390x (4.13.0-17.20) ... Setting up libroken18-heimdal:s390x (7.5.0+dfsg-1) ... Setting up perl-modules-5.26 (5.26.1-3) ... Setting up optipng (0.7.6-1.1) ... Setting up cpp-7 (7.2.0-18ubuntu2) ... Setting up lsb-base (9.20170808ubuntu1) ... Setting up binutils-common:s390x (2.29.1-12ubuntu1) ... Setting up sensible-utils (0.0.11) ... Processing triggers for libc-bin (2.26-0ubuntu2) ... Setting up libperl5.26:s390x (5.26.1-3) ... Setting up libheimbase1-heimdal:s390x (7.5.0+dfsg-1) ... Setting up openssl (1.0.2g-1ubuntu14) ... Setting up libsqlite3-0:s390x (3.21.0-1) ... Setting up libc-dev-bin (2.26-0ubuntu2) ... Setting up libkeyutils1:s390x (1.5.9-9.2ubuntu1) ... Setting up libc6-dev:s390x (2.26-0ubuntu2) ... Setting up libassuan0:s390x (2.5.1-1) ... Setting up libitm1:s390x (7.2.0-18ubuntu2) ... Setting up libwind0-heimdal:s390x (7.5.0+dfsg-1) ... Setting up libbinutils:s390x (2.29.1-12ubuntu1) ... Setting up libcurl3-gnutls:s390x (7.57.0-1ubuntu1) ... Setting up libasn1-8-heimdal:s390x (7.5.0+dfsg-1) ... Setting up binutils-s390x-linux-gnu (2.29.1-12ubuntu1) ... Setting up libhcrypto4-heimdal:s390x (7.5.0+dfsg-1) ... Setting up libhx509-5-heimdal:s390x (7.5.0+dfsg-1) ... Setting up libgcc-7-dev:s390x (7.2.0-18ubuntu2) ... Setting up libstdc++-7-dev:s390x (7.2.0-18ubuntu2) ... Setting up perl (5.26.1-3) ... Setting up pinentry-curses (1.0.0-3) ... Setting up binutils (2.29.1-12ubuntu1) ... Setting up libkrb5-26-heimdal:s390x (7.5.0+dfsg-1) ... Setting up gnupg-agent (2.1.15-1ubuntu8) ... Setting up libheimntlm0-heimdal:s390x (7.5.0+dfsg-1) ... Setting up gcc-7 (7.2.0-18ubuntu2) ... Setting up g++-7 (7.2.0-18ubuntu2) ... Setting up gnupg (2.1.15-1ubuntu8) ... Setting up libdpkg-perl (1.19.0.4ubuntu1) ... Setting up dpkg-dev (1.19.0.4ubuntu1) ... Setting up libgssapi3-heimdal:s390x (7.5.0+dfsg-1) ... Setting up build-essential (12.4ubuntu1) ... Processing triggers for libc-bin (2.26-0ubuntu2) ... RUN: /usr/share/launchpad-buildd/slavebin/sbuild-package PACKAGEBUILD-13886866 s390x bionic -c chroot:build-PACKAGEBUILD-13886866 --arch=s390x --dist=bionic --nolog alarm-clock-applet_0.3.4-1.dsc Initiating build PACKAGEBUILD-13886866 with 4 jobs across 4 processor cores. Kernel reported to sbuild: 4.4.0-104-generic #127-Ubuntu SMP Mon Dec 11 12:16:43 UTC 2017 s390x sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on bos02-s390x-020.buildd +==============================================================================+ | alarm-clock-applet 0.3.4-1 (s390x) 23 Dec 2017 10:54 | +==============================================================================+ Package: alarm-clock-applet Version: 0.3.4-1 Source Version: 0.3.4-1 Distribution: bionic Machine Architecture: s390x Host Architecture: s390x Build Architecture: s390x I: NOTICE: Log filtering will replace 'build/alarm-clock-applet-jCfkDl/alarm-clock-applet-0.3.4' with '<>' I: NOTICE: Log filtering will replace 'build/alarm-clock-applet-jCfkDl' with '<>' I: NOTICE: Log filtering will replace 'home/buildd/build-PACKAGEBUILD-13886866/chroot-autobuild' with '<>' +------------------------------------------------------------------------------+ | 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 '/<>/resolver-EwK96P/apt_archive/sbuild-build-depends-core-dummy.deb'. Ign:1 copy:/<>/resolver-EwK96P/apt_archive ./ InRelease Get:2 copy:/<>/resolver-EwK96P/apt_archive ./ Release [2119 B] Ign:3 copy:/<>/resolver-EwK96P/apt_archive ./ Release.gpg Get:4 copy:/<>/resolver-EwK96P/apt_archive ./ Sources [214 B] Get:5 copy:/<>/resolver-EwK96P/apt_archive ./ Packages [526 B] Fetched 2859 B in 0s (210 kB/s) 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 packages were automatically installed and are no longer required: libasn1-8-heimdal libcurl3-gnutls libgssapi-krb5-2 libgssapi3-heimdal libhcrypto4-heimdal libheimbase1-heimdal libheimntlm0-heimdal libhx509-5-heimdal libidn2-0 libk5crypto3 libkeyutils1 libkrb5-26-heimdal libkrb5-3 libkrb5support0 libldap-2.4-2 libldap-common libnghttp2-14 libpsl5 libroken18-heimdal librtmp1 libsasl2-2 libsasl2-modules-db libunistring0 libwind0-heimdal Use 'apt autoremove' to remove them. 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 852 B of archives. After this operation, 0 B of additional disk space will be used. Get:1 copy:/<>/resolver-EwK96P/apt_archive ./ sbuild-build-depends-core-dummy 0.invalid.0 [852 B] debconf: delaying package configuration, since apt-utils is not installed Fetched 852 B in 0s (0 B/s) Selecting previously unselected package sbuild-build-depends-core-dummy. (Reading database ... 12441 files and directories currently installed.) Preparing to unpack .../sbuild-build-depends-core-dummy_0.invalid.0_s390x.deb ... Unpacking sbuild-build-depends-core-dummy (0.invalid.0) ... Setting up sbuild-build-depends-core-dummy (0.invalid.0) ... Merged Build-Depends: 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: 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 '/<>/resolver-KxGQRF/apt_archive/sbuild-build-depends-alarm-clock-applet-dummy.deb'. Ign:1 copy:/<>/resolver-KxGQRF/apt_archive ./ InRelease Get:2 copy:/<>/resolver-KxGQRF/apt_archive ./ Release [2119 B] Ign:3 copy:/<>/resolver-KxGQRF/apt_archive ./ Release.gpg Get:4 copy:/<>/resolver-KxGQRF/apt_archive ./ Sources [327 B] Get:5 copy:/<>/resolver-KxGQRF/apt_archive ./ Packages [651 B] Fetched 3097 B in 0s (212 kB/s) 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 packages were automatically installed and are no longer required: libcurl3-gnutls libidn2-0 libnghttp2-14 libpsl5 librtmp1 Use 'apt autoremove' to remove them. The following additional packages will be installed: adwaita-icon-theme autoconf automake autopoint autotools-dev bsdmainutils dbus dbus-user-session debhelper dh-autoreconf dh-python dh-strip-nondeterminism 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-harfbuzz-0.0 gir1.2-notify-0.7 gir1.2-pango-1.0 gnome-icon-theme groff-base gtk-update-icon-cache hicolor-icon-theme humanity-icon-theme icu-devtools intltool intltool-debian libappindicator-dev libappindicator1 libarchive-zip-perl libatk1.0-0 libatk1.0-data libatk1.0-dev libavahi-client3 libavahi-common-data libavahi-common3 libbsd0 libcairo-gobject2 libcairo-script-interpreter2 libcairo2 libcairo2-dev libcap2-bin libcroco3 libcups2 libdatrie1 libdbus-1-3 libdbus-1-dev libdbus-glib-1-2 libdbus-glib-1-dev libdbusmenu-glib-dev libdbusmenu-glib4 libdbusmenu-gtk4 libelf1 libencode-locale-perl libexpat1 libexpat1-dev libfile-listing-perl libfile-stripnondeterminism-perl libfontconfig1 libfontconfig1-dev libfreetype6 libfreetype6-dev libgconf-2-4 libgconf2-dev libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-common libgdk-pixbuf2.0-dev libgirepository-1.0-1 libglib2.0-0 libglib2.0-bin libglib2.0-data libglib2.0-dev libglib2.0-dev-bin libgraphite2-3 libgraphite2-dev libgstreamer1.0-0 libgstreamer1.0-dev 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 libicu-le-hb-dev libicu-le-hb0 libicu60 libindicator7 libio-html-perl libio-socket-ssl-perl libjbig0 libjpeg-turbo8 libjpeg8 liblwp-mediatypes-perl liblwp-protocol-https-perl liblzo2-2 libmagic-mgc libmagic1 libmpdec2 libnet-http-perl libnet-ssleay-perl libnotify-dev libnotify4 libpam-systemd 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 libpng-dev libpthread-stubs0-dev libpython3-stdlib libpython3.6-minimal libpython3.6-stdlib librsvg2-2 librsvg2-common libsigsegv2 libsm-dev libsm6 libthai-data libthai0 libtiff5 libtimedate-perl libtool libtry-tiny-perl libunique-1.0-0 libunique-dev liburi-perl libwww-perl libwww-robotrules-perl libx11-6 libx11-data libx11-dev libxau-dev libxau6 libxcb-render0 libxcb-render0-dev libxcb-shm0 libxcb-shm0-dev libxcb1 libxcb1-dev libxcomposite-dev libxcomposite1 libxcursor-dev libxcursor1 libxdamage-dev libxdamage1 libxdmcp-dev libxdmcp6 libxext-dev libxext6 libxfixes-dev libxfixes3 libxft-dev libxft2 libxi-dev libxi6 libxinerama-dev libxinerama1 libxml-parser-perl libxml2 libxml2-dev libxml2-utils libxrandr-dev libxrandr2 libxrender-dev libxrender1 m4 man-db mime-support netbase perl-openssl-defaults pkg-config po-debconf psmisc python3 python3-distutils python3-minimal python3.6 python3.6-2to3 python3.6-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 xorg-sgml-doctools xtrans-dev zlib1g-dev Suggested packages: autoconf-archive gnu-standards autoconf-doc wamerican | wordlist whois vacation dh-make dwz gconf-defaults-service gettext-doc libasprintf-dev libgettextpo-dev groff indicator-application libcairo2-doc cups-common libglib2.0-doc libgraphite2-utils gstreamer1.0-tools gstreamer1.0-doc gvfs libgtk2.0-doc libdata-dump-perl libice-doc icu-doc libcrypt-ssleay-perl imagemagick libpango1.0-doc librsvg2-bin libsm-doc libtool-doc gfortran | fortran95-compiler gcj-jdk libunique-doc libauthen-ntlm-perl libxcb-doc libxext-doc m4-doc less www-browser apparmor libmail-box-perl python3-doc python3-tk python3-venv python3.6-venv python3.6-doc binfmt-support Recommended packages: curl | wget | lynx libpam-cap libarchive-cpio-perl libgconf2-doc libgdk-pixbuf2.0-bin xdg-user-dirs libgail-common libgtk2.0-bin python libhtml-format-perl notification-daemon libpng-tools libltdl-dev libdata-dump-perl libhtml-form-perl libhttp-daemon-perl libmailtools-perl libx11-doc libmail-sendmail-perl The following packages will be REMOVED: pkg-create-dbgsym* The following NEW packages will be installed: adwaita-icon-theme autoconf automake autopoint autotools-dev bsdmainutils dbus dbus-user-session debhelper dh-autoreconf dh-python dh-strip-nondeterminism 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-harfbuzz-0.0 gir1.2-notify-0.7 gir1.2-pango-1.0 gnome-icon-theme groff-base gtk-update-icon-cache hicolor-icon-theme humanity-icon-theme icu-devtools intltool intltool-debian libappindicator-dev libappindicator1 libarchive-zip-perl libatk1.0-0 libatk1.0-data libatk1.0-dev libavahi-client3 libavahi-common-data libavahi-common3 libbsd0 libcairo-gobject2 libcairo-script-interpreter2 libcairo2 libcairo2-dev libcap2-bin libcroco3 libcups2 libdatrie1 libdbus-1-3 libdbus-1-dev libdbus-glib-1-2 libdbus-glib-1-dev libdbusmenu-glib-dev libdbusmenu-glib4 libdbusmenu-gtk4 libelf1 libencode-locale-perl libexpat1 libexpat1-dev libfile-listing-perl libfile-stripnondeterminism-perl libfontconfig1 libfontconfig1-dev libfreetype6 libfreetype6-dev libgconf-2-4 libgconf2-dev libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-common libgdk-pixbuf2.0-dev libgirepository-1.0-1 libglib2.0-0 libglib2.0-bin libglib2.0-data libglib2.0-dev libglib2.0-dev-bin libgraphite2-3 libgraphite2-dev libgstreamer1.0-0 libgstreamer1.0-dev 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 libicu-le-hb-dev libicu-le-hb0 libicu60 libindicator7 libio-html-perl libio-socket-ssl-perl libjbig0 libjpeg-turbo8 libjpeg8 liblwp-mediatypes-perl liblwp-protocol-https-perl liblzo2-2 libmagic-mgc libmagic1 libmpdec2 libnet-http-perl libnet-ssleay-perl libnotify-dev libnotify4 libpam-systemd 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 libpng-dev libpthread-stubs0-dev libpython3-stdlib libpython3.6-minimal libpython3.6-stdlib librsvg2-2 librsvg2-common libsigsegv2 libsm-dev libsm6 libthai-data libthai0 libtiff5 libtimedate-perl libtool libtry-tiny-perl libunique-1.0-0 libunique-dev liburi-perl libwww-perl libwww-robotrules-perl libx11-6 libx11-data libx11-dev libxau-dev libxau6 libxcb-render0 libxcb-render0-dev libxcb-shm0 libxcb-shm0-dev libxcb1 libxcb1-dev libxcomposite-dev libxcomposite1 libxcursor-dev libxcursor1 libxdamage-dev libxdamage1 libxdmcp-dev libxdmcp6 libxext-dev libxext6 libxfixes-dev libxfixes3 libxft-dev libxft2 libxi-dev libxi6 libxinerama-dev libxinerama1 libxml-parser-perl libxml2 libxml2-dev libxml2-utils libxrandr-dev libxrandr2 libxrender-dev libxrender1 m4 man-db mime-support netbase perl-openssl-defaults pkg-config po-debconf psmisc python3 python3-distutils python3-minimal python3.6 python3.6-2to3 python3.6-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 xorg-sgml-doctools xtrans-dev zlib1g-dev 0 upgraded, 231 newly installed, 1 to remove and 0 not upgraded. Need to get 69.4 MB of archives. After this operation, 308 MB of additional disk space will be used. Get:1 copy:/<>/resolver-KxGQRF/apt_archive ./ sbuild-build-depends-alarm-clock-applet-dummy 0.invalid.0 [980 B] Get:2 http://ftpmaster.internal/ubuntu bionic/main s390x libpython3.6-minimal s390x 3.6.4-1 [526 kB] Get:3 http://ftpmaster.internal/ubuntu bionic/main s390x libexpat1 s390x 2.2.5-3 [79.3 kB] Get:4 http://ftpmaster.internal/ubuntu bionic/main s390x python3.6-minimal s390x 3.6.4-1 [1330 kB] Get:5 http://ftpmaster.internal/ubuntu bionic/main s390x python3-minimal s390x 3.6.3-0ubuntu2 [23.3 kB] Get:6 http://ftpmaster.internal/ubuntu bionic/main s390x mime-support all 3.60ubuntu1 [30.1 kB] Get:7 http://ftpmaster.internal/ubuntu bionic/main s390x libmpdec2 s390x 2.4.2-1 [81.5 kB] Get:8 http://ftpmaster.internal/ubuntu bionic/main s390x libpython3.6-stdlib s390x 3.6.4-1 [1613 kB] Get:9 http://ftpmaster.internal/ubuntu bionic/main s390x python3.6-2to3 all 3.6.4-1 [81.2 kB] Get:10 http://ftpmaster.internal/ubuntu bionic/main s390x python3-distutils all 3.6.4~rc1-6 [145 kB] Get:11 http://ftpmaster.internal/ubuntu bionic/main s390x python3.6 s390x 3.6.4-1 [181 kB] Get:12 http://ftpmaster.internal/ubuntu bionic/main s390x libpython3-stdlib s390x 3.6.3-0ubuntu2 [6822 B] Get:13 http://ftpmaster.internal/ubuntu bionic/main s390x dh-python all 2.20170125 [83.7 kB] Get:14 http://ftpmaster.internal/ubuntu bionic/main s390x python3 s390x 3.6.3-0ubuntu2 [8712 B] Get:15 http://ftpmaster.internal/ubuntu bionic/main s390x groff-base s390x 1.22.3-9 [1174 kB] Get:16 http://ftpmaster.internal/ubuntu bionic/main s390x libbsd0 s390x 0.8.6-3 [40.2 kB] Get:17 http://ftpmaster.internal/ubuntu bionic/main s390x bsdmainutils s390x 9.0.14ubuntu1 [178 kB] Get:18 http://ftpmaster.internal/ubuntu bionic/main s390x libpipeline1 s390x 1.5.0-1 [24.1 kB] Get:19 http://ftpmaster.internal/ubuntu bionic/main s390x man-db s390x 2.7.6.1-4 [886 kB] Get:20 http://ftpmaster.internal/ubuntu bionic/main s390x libfreetype6 s390x 2.8-0.2ubuntu2 [313 kB] Get:21 http://ftpmaster.internal/ubuntu bionic/main s390x ucf all 3.0036 [52.9 kB] Get:22 http://ftpmaster.internal/ubuntu bionic/main s390x fonts-dejavu-core all 2.37-1 [1041 kB] Get:23 http://ftpmaster.internal/ubuntu bionic/main s390x fontconfig-config all 2.12.6-0ubuntu1 [55.5 kB] Get:24 http://ftpmaster.internal/ubuntu bionic/main s390x libfontconfig1 s390x 2.12.6-0ubuntu1 [132 kB] Get:25 http://ftpmaster.internal/ubuntu bionic/main s390x fontconfig s390x 2.12.6-0ubuntu1 [168 kB] Get:26 http://ftpmaster.internal/ubuntu bionic/main s390x libdbusmenu-glib4 s390x 16.04.1+18.04.20171206-0ubuntu1 [37.5 kB] Get:27 http://ftpmaster.internal/ubuntu bionic/main s390x libglib2.0-0 s390x 2.54.1-1ubuntu1 [1075 kB] Get:28 http://ftpmaster.internal/ubuntu bionic/main s390x libatk1.0-data all 2.26.1-2 [3008 B] Get:29 http://ftpmaster.internal/ubuntu bionic/main s390x libatk1.0-0 s390x 2.26.1-2 [41.6 kB] Get:30 http://ftpmaster.internal/ubuntu bionic/main s390x libjpeg-turbo8 s390x 1.5.2-0ubuntu5 [100 kB] Get:31 http://ftpmaster.internal/ubuntu bionic/main s390x libjpeg8 s390x 8c-2ubuntu8 [2142 B] Get:32 http://ftpmaster.internal/ubuntu bionic/main s390x libjbig0 s390x 2.1-3.1 [26.6 kB] Get:33 http://ftpmaster.internal/ubuntu bionic/main s390x libtiff5 s390x 4.0.9-2 [142 kB] Get:34 http://ftpmaster.internal/ubuntu bionic/main s390x libxau6 s390x 1:1.0.8-1 [7420 B] Get:35 http://ftpmaster.internal/ubuntu bionic/main s390x libxdmcp6 s390x 1:1.1.2-3 [10.7 kB] Get:36 http://ftpmaster.internal/ubuntu bionic/main s390x libxcb1 s390x 1.12-1ubuntu1 [43.3 kB] Get:37 http://ftpmaster.internal/ubuntu bionic/main s390x libx11-data all 2:1.6.4-3 [114 kB] Get:38 http://ftpmaster.internal/ubuntu bionic/main s390x libx11-6 s390x 2:1.6.4-3 [546 kB] Get:39 http://ftpmaster.internal/ubuntu bionic/main s390x libgraphite2-3 s390x 1.3.10-8 [70.3 kB] Get:40 http://ftpmaster.internal/ubuntu bionic/main s390x libharfbuzz0b s390x 1.7.2-1 [218 kB] Get:41 http://ftpmaster.internal/ubuntu bionic/main s390x libicu-le-hb0 s390x 1.0.3+git161113-4 [14.5 kB] Get:42 http://ftpmaster.internal/ubuntu bionic/main s390x libicu60 s390x 60.2-1ubuntu1 [7846 kB] Get:43 http://ftpmaster.internal/ubuntu bionic/main s390x libxml2 s390x 2.9.4+dfsg1-5.2ubuntu1 [593 kB] Get:44 http://ftpmaster.internal/ubuntu bionic/main s390x shared-mime-info s390x 1.9-2 [425 kB] Get:45 http://ftpmaster.internal/ubuntu bionic/main s390x libgdk-pixbuf2.0-common all 2.36.11-1 [4260 B] Get:46 http://ftpmaster.internal/ubuntu bionic/main s390x libgdk-pixbuf2.0-0 s390x 2.36.11-1 [156 kB] Get:47 http://ftpmaster.internal/ubuntu bionic/main s390x libthai-data all 0.1.27-1 [133 kB] Get:48 http://ftpmaster.internal/ubuntu bionic/main s390x libdatrie1 s390x 0.2.10-5 [17.4 kB] Get:49 http://ftpmaster.internal/ubuntu bionic/main s390x libthai0 s390x 0.1.27-1 [18.0 kB] Get:50 http://ftpmaster.internal/ubuntu bionic/main s390x libpango-1.0-0 s390x 1.40.14-1 [148 kB] Get:51 http://ftpmaster.internal/ubuntu bionic/main s390x libdbusmenu-gtk4 s390x 16.04.1+18.04.20171206-0ubuntu1 [24.7 kB] Get:52 http://ftpmaster.internal/ubuntu bionic/main s390x libgtk2.0-common all 2.24.31-4ubuntu1 [124 kB] Get:53 http://ftpmaster.internal/ubuntu bionic/main s390x libpixman-1-0 s390x 0.34.0-2 [135 kB] Get:54 http://ftpmaster.internal/ubuntu bionic/main s390x libxcb-render0 s390x 1.12-1ubuntu1 [14.7 kB] Get:55 http://ftpmaster.internal/ubuntu bionic/main s390x libxcb-shm0 s390x 1.12-1ubuntu1 [5420 B] Get:56 http://ftpmaster.internal/ubuntu bionic/main s390x libxext6 s390x 2:1.3.3-1 [27.8 kB] Get:57 http://ftpmaster.internal/ubuntu bionic/main s390x libxrender1 s390x 1:0.9.10-1 [17.8 kB] Get:58 http://ftpmaster.internal/ubuntu bionic/main s390x libcairo2 s390x 1.15.8-3 [528 kB] Get:59 http://ftpmaster.internal/ubuntu bionic/main s390x libavahi-common-data s390x 0.6.32-1ubuntu1 [22.0 kB] Get:60 http://ftpmaster.internal/ubuntu bionic/main s390x libavahi-common3 s390x 0.6.32-1ubuntu1 [20.3 kB] Get:61 http://ftpmaster.internal/ubuntu bionic/main s390x libdbus-1-3 s390x 1.12.2-1ubuntu1 [168 kB] Get:62 http://ftpmaster.internal/ubuntu bionic/main s390x libavahi-client3 s390x 0.6.32-1ubuntu1 [22.7 kB] Get:63 http://ftpmaster.internal/ubuntu bionic/main s390x libcups2 s390x 2.2.6-3 [192 kB] Get:64 http://ftpmaster.internal/ubuntu bionic/main s390x libpangoft2-1.0-0 s390x 1.40.14-1 [31.5 kB] Get:65 http://ftpmaster.internal/ubuntu bionic/main s390x libpangocairo-1.0-0 s390x 1.40.14-1 [19.2 kB] Get:66 http://ftpmaster.internal/ubuntu bionic/main s390x libxcomposite1 s390x 1:0.4.4-2 [6894 B] Get:67 http://ftpmaster.internal/ubuntu bionic/main s390x libxfixes3 s390x 1:5.0.3-1 [10.4 kB] Get:68 http://ftpmaster.internal/ubuntu bionic/main s390x libxcursor1 s390x 1:1.1.15-1 [19.7 kB] Get:69 http://ftpmaster.internal/ubuntu bionic/main s390x libxdamage1 s390x 1:1.1.4-3 [6740 B] Get:70 http://ftpmaster.internal/ubuntu bionic/main s390x libxi6 s390x 2:1.7.9-1 [27.5 kB] Get:71 http://ftpmaster.internal/ubuntu bionic/main s390x libxinerama1 s390x 2:1.1.3-1 [7002 B] Get:72 http://ftpmaster.internal/ubuntu bionic/main s390x libxrandr2 s390x 2:1.5.1-1 [17.7 kB] Get:73 http://ftpmaster.internal/ubuntu bionic/main s390x hicolor-icon-theme all 0.17-1 [10.3 kB] Get:74 http://ftpmaster.internal/ubuntu bionic/main s390x gtk-update-icon-cache s390x 3.22.26-2ubuntu1 [27.3 kB] Get:75 http://ftpmaster.internal/ubuntu bionic/main s390x libcroco3 s390x 0.6.12-2 [74.2 kB] Get:76 http://ftpmaster.internal/ubuntu bionic/main s390x librsvg2-2 s390x 2.40.18-2 [87.8 kB] Get:77 http://ftpmaster.internal/ubuntu bionic/main s390x librsvg2-common s390x 2.40.18-2 [5056 B] Get:78 http://ftpmaster.internal/ubuntu bionic/main s390x humanity-icon-theme all 0.6.13 [1288 kB] Get:79 http://ftpmaster.internal/ubuntu bionic/main s390x ubuntu-mono all 16.10+18.04.20171115.1-0ubuntu1 [151 kB] Get:80 http://ftpmaster.internal/ubuntu bionic/main s390x adwaita-icon-theme all 3.26.1-1ubuntu1 [3447 kB] Get:81 http://ftpmaster.internal/ubuntu bionic/universe s390x gnome-icon-theme all 3.12.0-2 [9618 kB] Get:82 http://ftpmaster.internal/ubuntu bionic/main s390x libgtk2.0-0 s390x 2.24.31-4ubuntu1 [1615 kB] Get:83 http://ftpmaster.internal/ubuntu bionic/universe s390x libindicator7 s390x 16.10.0+18.04.20171205.1-0ubuntu1 [20.1 kB] Get:84 http://ftpmaster.internal/ubuntu bionic/universe s390x libappindicator1 s390x 12.10.1+17.04.20170215-0ubuntu2 [17.7 kB] Get:85 http://ftpmaster.internal/ubuntu bionic/main s390x dbus s390x 1.12.2-1ubuntu1 [140 kB] Get:86 http://ftpmaster.internal/ubuntu bionic/main s390x libmagic-mgc s390x 1:5.32-1 [185 kB] Get:87 http://ftpmaster.internal/ubuntu bionic/main s390x libmagic1 s390x 1:5.32-1 [66.9 kB] Get:88 http://ftpmaster.internal/ubuntu bionic/main s390x file s390x 1:5.32-1 [21.8 kB] Get:89 http://ftpmaster.internal/ubuntu bionic/main s390x libcap2-bin s390x 1:2.25-1.2 [20.2 kB] Get:90 http://ftpmaster.internal/ubuntu bionic/main s390x libelf1 s390x 0.170-0.1 [42.7 kB] Get:91 http://ftpmaster.internal/ubuntu bionic/main s390x libglib2.0-data all 2.54.1-1ubuntu1 [4250 B] Get:92 http://ftpmaster.internal/ubuntu bionic/main s390x libpam-systemd s390x 235-3ubuntu2 [92.8 kB] Get:93 http://ftpmaster.internal/ubuntu bionic/main s390x netbase all 5.4 [12.7 kB] Get:94 http://ftpmaster.internal/ubuntu bionic/main s390x gettext-base s390x 0.19.8.1-4ubuntu2 [47.9 kB] Get:95 http://ftpmaster.internal/ubuntu bionic/main s390x libgirepository-1.0-1 s390x 1.54.1-4 [79.4 kB] Get:96 http://ftpmaster.internal/ubuntu bionic/main s390x gir1.2-glib-2.0 s390x 1.54.1-4 [129 kB] Get:97 http://ftpmaster.internal/ubuntu bionic/main s390x libdbus-glib-1-2 s390x 0.108-3 [65.4 kB] Get:98 http://ftpmaster.internal/ubuntu bionic/main s390x psmisc s390x 23.1-1 [47.6 kB] Get:99 http://ftpmaster.internal/ubuntu bionic/main s390x libsigsegv2 s390x 2.11-1 [12.6 kB] Get:100 http://ftpmaster.internal/ubuntu bionic/main s390x m4 s390x 1.4.18-1 [195 kB] Get:101 http://ftpmaster.internal/ubuntu bionic/main s390x autoconf all 2.69-11 [322 kB] Get:102 http://ftpmaster.internal/ubuntu bionic/main s390x autotools-dev all 20171216.1 [39.7 kB] Get:103 http://ftpmaster.internal/ubuntu bionic/main s390x automake all 1:1.15.1-3ubuntu1 [509 kB] Get:104 http://ftpmaster.internal/ubuntu bionic/main s390x autopoint all 0.19.8.1-4ubuntu2 [412 kB] Get:105 http://ftpmaster.internal/ubuntu bionic/main s390x dbus-user-session s390x 1.12.2-1ubuntu1 [9380 B] Get:106 http://ftpmaster.internal/ubuntu bionic/main s390x libtool all 2.4.6-2 [194 kB] Get:107 http://ftpmaster.internal/ubuntu bionic/main s390x dh-autoreconf all 15 [15.8 kB] Get:108 http://ftpmaster.internal/ubuntu bionic/main s390x libarchive-zip-perl all 1.60-1 [83.9 kB] Get:109 http://ftpmaster.internal/ubuntu bionic/main s390x libfile-stripnondeterminism-perl all 0.040-1 [13.9 kB] Get:110 http://ftpmaster.internal/ubuntu bionic/main s390x libtimedate-perl all 2.3000-2 [37.5 kB] Get:111 http://ftpmaster.internal/ubuntu bionic/main s390x dh-strip-nondeterminism all 0.040-1 [5196 B] Get:112 http://ftpmaster.internal/ubuntu bionic/main s390x gettext s390x 0.19.8.1-4ubuntu2 [1045 kB] Get:113 http://ftpmaster.internal/ubuntu bionic/main s390x intltool-debian all 0.35.0+20060710.4 [24.9 kB] Get:114 http://ftpmaster.internal/ubuntu bionic/main s390x po-debconf all 1.0.20 [232 kB] Get:115 http://ftpmaster.internal/ubuntu bionic/main s390x debhelper all 11ubuntu1 [887 kB] Get:116 http://ftpmaster.internal/ubuntu bionic/universe s390x gconf2-common all 3.2.6-4ubuntu1 [700 kB] Get:117 http://ftpmaster.internal/ubuntu bionic/universe s390x libgconf-2-4 s390x 3.2.6-4ubuntu1 [78.7 kB] Get:118 http://ftpmaster.internal/ubuntu bionic/universe s390x gconf-service-backend s390x 3.2.6-4ubuntu1 [52.9 kB] Get:119 http://ftpmaster.internal/ubuntu bionic/universe s390x gconf-service s390x 3.2.6-4ubuntu1 [2038 B] Get:120 http://ftpmaster.internal/ubuntu bionic/universe s390x gconf2 s390x 3.2.6-4ubuntu1 [64.8 kB] Get:121 http://ftpmaster.internal/ubuntu bionic/main s390x gir1.2-atk-1.0 s390x 2.26.1-2 [17.8 kB] Get:122 http://ftpmaster.internal/ubuntu bionic/main s390x gir1.2-freedesktop s390x 1.54.1-4 [8960 B] Get:123 http://ftpmaster.internal/ubuntu bionic/main s390x gir1.2-gdkpixbuf-2.0 s390x 2.36.11-1 [7582 B] Get:124 http://ftpmaster.internal/ubuntu bionic/main s390x libxft2 s390x 2.3.2-1 [36.7 kB] Get:125 http://ftpmaster.internal/ubuntu bionic/main s390x libpangoxft-1.0-0 s390x 1.40.14-1 [14.3 kB] Get:126 http://ftpmaster.internal/ubuntu bionic/main s390x gir1.2-pango-1.0 s390x 1.40.14-1 [21.5 kB] Get:127 http://ftpmaster.internal/ubuntu bionic/main s390x gir1.2-gtk-2.0 s390x 2.24.31-4ubuntu1 [168 kB] Get:128 http://ftpmaster.internal/ubuntu bionic/universe s390x gir1.2-appindicator-0.1 s390x 12.10.1+17.04.20170215-0ubuntu2 [3304 B] Get:129 http://ftpmaster.internal/ubuntu bionic/main s390x gir1.2-dbusmenu-glib-0.4 s390x 16.04.1+18.04.20171206-0ubuntu1 [6140 B] Get:130 http://ftpmaster.internal/ubuntu bionic/universe s390x gir1.2-gconf-2.0 s390x 3.2.6-4ubuntu1 [6106 B] Get:131 http://ftpmaster.internal/ubuntu bionic/main s390x libgstreamer1.0-0 s390x 1.12.4-1 [741 kB] Get:132 http://ftpmaster.internal/ubuntu bionic/main s390x gir1.2-gstreamer-1.0 s390x 1.12.4-1 [68.9 kB] Get:133 http://ftpmaster.internal/ubuntu bionic/main s390x gir1.2-harfbuzz-0.0 s390x 1.7.2-1 [18.2 kB] Get:134 http://ftpmaster.internal/ubuntu bionic/main s390x libnotify4 s390x 0.7.7-3 [16.5 kB] Get:135 http://ftpmaster.internal/ubuntu bionic/main s390x gir1.2-notify-0.7 s390x 0.7.7-3 [3540 B] Get:136 http://ftpmaster.internal/ubuntu bionic/main s390x icu-devtools s390x 60.2-1ubuntu1 [171 kB] Get:137 http://ftpmaster.internal/ubuntu bionic/main s390x liburi-perl all 1.72-2 [76.6 kB] Get:138 http://ftpmaster.internal/ubuntu bionic/main s390x libencode-locale-perl all 1.05-1 [12.3 kB] Get:139 http://ftpmaster.internal/ubuntu bionic/main s390x libhttp-date-perl all 6.02-1 [10.4 kB] Get:140 http://ftpmaster.internal/ubuntu bionic/main s390x libfile-listing-perl all 6.04-1 [9774 B] Get:141 http://ftpmaster.internal/ubuntu bionic/main s390x libhtml-tagset-perl all 3.20-3 [12.1 kB] Get:142 http://ftpmaster.internal/ubuntu bionic/main s390x libhtml-parser-perl s390x 3.72-3build1 [85.1 kB] Get:143 http://ftpmaster.internal/ubuntu bionic/main s390x libhtml-tree-perl all 5.07-1 [200 kB] Get:144 http://ftpmaster.internal/ubuntu bionic/main s390x libio-html-perl all 1.001-1 [14.9 kB] Get:145 http://ftpmaster.internal/ubuntu bionic/main s390x liblwp-mediatypes-perl all 6.02-1 [21.7 kB] Get:146 http://ftpmaster.internal/ubuntu bionic/main s390x libhttp-message-perl all 6.13-1 [69.7 kB] Get:147 http://ftpmaster.internal/ubuntu bionic/main s390x libhttp-cookies-perl all 6.04-1 [17.2 kB] Get:148 http://ftpmaster.internal/ubuntu bionic/main s390x libhttp-negotiate-perl all 6.00-2 [13.4 kB] Get:149 http://ftpmaster.internal/ubuntu bionic/main s390x perl-openssl-defaults s390x 3 [6816 B] Get:150 http://ftpmaster.internal/ubuntu bionic/main s390x libnet-ssleay-perl s390x 1.80-1build1 [254 kB] Get:151 http://ftpmaster.internal/ubuntu bionic/main s390x libio-socket-ssl-perl all 2.052-1 [168 kB] Get:152 http://ftpmaster.internal/ubuntu bionic/main s390x libnet-http-perl all 6.17-1 [22.7 kB] Get:153 http://ftpmaster.internal/ubuntu bionic/main s390x liblwp-protocol-https-perl all 6.07-2 [8284 B] Get:154 http://ftpmaster.internal/ubuntu bionic/main s390x libtry-tiny-perl all 0.30-1 [20.5 kB] Get:155 http://ftpmaster.internal/ubuntu bionic/main s390x libwww-robotrules-perl all 6.01-1 [14.1 kB] Get:156 http://ftpmaster.internal/ubuntu bionic/main s390x libwww-perl all 6.29-1 [137 kB] Get:157 http://ftpmaster.internal/ubuntu bionic/main s390x libxml-parser-perl s390x 2.44-2build3 [197 kB] Get:158 http://ftpmaster.internal/ubuntu bionic/universe s390x intltool all 0.51.0-5 [44.3 kB] Get:159 http://ftpmaster.internal/ubuntu bionic/main s390x pkg-config s390x 0.29.1-0ubuntu2 [44.0 kB] Get:160 http://ftpmaster.internal/ubuntu bionic/main s390x libdbus-1-dev s390x 1.12.2-1ubuntu1 [160 kB] Get:161 http://ftpmaster.internal/ubuntu bionic/main s390x libglib2.0-bin s390x 2.54.1-1ubuntu1 [65.3 kB] Get:162 http://ftpmaster.internal/ubuntu bionic/main s390x libglib2.0-dev-bin s390x 2.54.1-1ubuntu1 [84.1 kB] Get:163 http://ftpmaster.internal/ubuntu bionic/main s390x libpcre16-3 s390x 2:8.39-8 [79.5 kB] Get:164 http://ftpmaster.internal/ubuntu bionic/main s390x libpcre32-3 s390x 2:8.39-8 [73.9 kB] Get:165 http://ftpmaster.internal/ubuntu bionic/main s390x libpcrecpp0v5 s390x 2:8.39-8 [14.5 kB] Get:166 http://ftpmaster.internal/ubuntu bionic/main s390x libpcre3-dev s390x 2:8.39-8 [373 kB] Get:167 http://ftpmaster.internal/ubuntu bionic/main s390x zlib1g-dev s390x 1:1.2.11.dfsg-0ubuntu2 [173 kB] Get:168 http://ftpmaster.internal/ubuntu bionic/main s390x libglib2.0-dev s390x 2.54.1-1ubuntu1 [1312 kB] Get:169 http://ftpmaster.internal/ubuntu bionic/main s390x libdbus-glib-1-dev s390x 0.108-3 [91.8 kB] Get:170 http://ftpmaster.internal/ubuntu bionic/main s390x libdbusmenu-glib-dev s390x 16.04.1+18.04.20171206-0ubuntu1 [60.8 kB] Get:171 http://ftpmaster.internal/ubuntu bionic/universe s390x libappindicator-dev s390x 12.10.1+17.04.20170215-0ubuntu2 [10.8 kB] Get:172 http://ftpmaster.internal/ubuntu bionic/main s390x libatk1.0-dev s390x 2.26.1-2 [79.9 kB] Get:173 http://ftpmaster.internal/ubuntu bionic/main s390x libcairo-gobject2 s390x 1.15.8-3 [16.9 kB] Get:174 http://ftpmaster.internal/ubuntu bionic/main s390x liblzo2-2 s390x 2.08-1.2 [44.6 kB] Get:175 http://ftpmaster.internal/ubuntu bionic/main s390x libcairo-script-interpreter2 s390x 1.15.8-3 [50.9 kB] Get:176 http://ftpmaster.internal/ubuntu bionic/main s390x libexpat1-dev s390x 2.2.5-3 [224 kB] Get:177 http://ftpmaster.internal/ubuntu bionic/main s390x libpng-dev s390x 1.6.34-1 [173 kB] Get:178 http://ftpmaster.internal/ubuntu bionic/main s390x libfreetype6-dev s390x 2.8-0.2ubuntu2 [2516 kB] Get:179 http://ftpmaster.internal/ubuntu bionic/main s390x libfontconfig1-dev s390x 2.12.6-0ubuntu1 [686 kB] Get:180 http://ftpmaster.internal/ubuntu bionic/main s390x xorg-sgml-doctools all 1:1.11-1 [12.9 kB] Get:181 http://ftpmaster.internal/ubuntu bionic/main s390x x11proto-core-dev all 7.0.31-1 [700 kB] Get:182 http://ftpmaster.internal/ubuntu bionic/main s390x libxau-dev s390x 1:1.0.8-1 [9352 B] Get:183 http://ftpmaster.internal/ubuntu bionic/main s390x libxdmcp-dev s390x 1:1.1.2-3 [25.1 kB] Get:184 http://ftpmaster.internal/ubuntu bionic/main s390x x11proto-input-dev all 2.3.2-1 [118 kB] Get:185 http://ftpmaster.internal/ubuntu bionic/main s390x x11proto-kb-dev all 1.0.7-1 [226 kB] Get:186 http://ftpmaster.internal/ubuntu bionic/main s390x xtrans-dev all 1.3.5-1 [70.5 kB] Get:187 http://ftpmaster.internal/ubuntu bionic/main s390x libpthread-stubs0-dev s390x 0.3-4 [3892 B] Get:188 http://ftpmaster.internal/ubuntu bionic/main s390x libxcb1-dev s390x 1.12-1ubuntu1 [78.2 kB] Get:189 http://ftpmaster.internal/ubuntu bionic/main s390x libx11-dev s390x 2:1.6.4-3 [608 kB] Get:190 http://ftpmaster.internal/ubuntu bionic/main s390x x11proto-render-dev all 2:0.11.1-2 [20.1 kB] Get:191 http://ftpmaster.internal/ubuntu bionic/main s390x libxrender-dev s390x 1:0.9.10-1 [24.1 kB] Get:192 http://ftpmaster.internal/ubuntu bionic/main s390x x11proto-xext-dev all 7.3.0-1 [212 kB] Get:193 http://ftpmaster.internal/ubuntu bionic/main s390x libxext-dev s390x 2:1.3.3-1 [81.1 kB] Get:194 http://ftpmaster.internal/ubuntu bionic/main s390x x11-common all 1:7.7+19ubuntu3 [22.0 kB] Get:195 http://ftpmaster.internal/ubuntu bionic/main s390x libice6 s390x 2:1.0.9-2 [36.9 kB] Get:196 http://ftpmaster.internal/ubuntu bionic/main s390x libsm6 s390x 2:1.2.2-1 [15.3 kB] Get:197 http://ftpmaster.internal/ubuntu bionic/main s390x libice-dev s390x 2:1.0.9-2 [44.3 kB] Get:198 http://ftpmaster.internal/ubuntu bionic/main s390x libsm-dev s390x 2:1.2.2-1 [16.5 kB] Get:199 http://ftpmaster.internal/ubuntu bionic/main s390x libpixman-1-dev s390x 0.34.0-2 [149 kB] Get:200 http://ftpmaster.internal/ubuntu bionic/main s390x libxcb-render0-dev s390x 1.12-1ubuntu1 [18.3 kB] Get:201 http://ftpmaster.internal/ubuntu bionic/main s390x libxcb-shm0-dev s390x 1.12-1ubuntu1 [6564 B] Get:202 http://ftpmaster.internal/ubuntu bionic/main s390x libcairo2-dev s390x 1.15.8-3 [571 kB] Get:203 http://ftpmaster.internal/ubuntu bionic/universe s390x libgconf2-dev s390x 3.2.6-4ubuntu1 [90.6 kB] Get:204 http://ftpmaster.internal/ubuntu bionic/main s390x libgdk-pixbuf2.0-dev s390x 2.36.11-1 [46.3 kB] Get:205 http://ftpmaster.internal/ubuntu bionic/main s390x libgraphite2-dev s390x 1.3.10-8 [14.5 kB] Get:206 http://ftpmaster.internal/ubuntu bionic/main s390x libgstreamer1.0-dev s390x 1.12.4-1 [385 kB] Get:207 http://ftpmaster.internal/ubuntu bionic/main s390x libharfbuzz-icu0 s390x 1.7.2-1 [5604 B] Get:208 http://ftpmaster.internal/ubuntu bionic/main s390x libharfbuzz-gobject0 s390x 1.7.2-1 [13.2 kB] Get:209 http://ftpmaster.internal/ubuntu bionic/main s390x libicu-le-hb-dev s390x 1.0.3+git161113-4 [29.8 kB] Get:210 http://ftpmaster.internal/ubuntu bionic/main s390x libicu-dev s390x 60.2-1ubuntu1 [8681 kB] Get:211 http://ftpmaster.internal/ubuntu bionic/main s390x libharfbuzz-dev s390x 1.7.2-1 [287 kB] Get:212 http://ftpmaster.internal/ubuntu bionic/main s390x libxft-dev s390x 2.3.2-1 [47.5 kB] Get:213 http://ftpmaster.internal/ubuntu bionic/main s390x libpango1.0-dev s390x 1.40.14-1 [280 kB] Get:214 http://ftpmaster.internal/ubuntu bionic/main s390x x11proto-xinerama-dev all 1.2.1-2 [4966 B] Get:215 http://ftpmaster.internal/ubuntu bionic/main s390x libxinerama-dev s390x 2:1.1.3-1 [7660 B] Get:216 http://ftpmaster.internal/ubuntu bionic/main s390x x11proto-fixes-dev all 1:5.0-2ubuntu2 [14.2 kB] Get:217 http://ftpmaster.internal/ubuntu bionic/main s390x libxfixes-dev s390x 1:5.0.3-1 [10.7 kB] Get:218 http://ftpmaster.internal/ubuntu bionic/main s390x libxi-dev s390x 2:1.7.9-1 [184 kB] Get:219 http://ftpmaster.internal/ubuntu bionic/main s390x x11proto-randr-dev all 1.5.0-1 [33.7 kB] Get:220 http://ftpmaster.internal/ubuntu bionic/main s390x libxrandr-dev s390x 2:1.5.1-1 [23.9 kB] Get:221 http://ftpmaster.internal/ubuntu bionic/main s390x libxcursor-dev s390x 1:1.1.15-1 [26.7 kB] Get:222 http://ftpmaster.internal/ubuntu bionic/main s390x x11proto-composite-dev all 1:0.4.2-2 [10.5 kB] Get:223 http://ftpmaster.internal/ubuntu bionic/main s390x libxcomposite-dev s390x 1:0.4.4-2 [9096 B] Get:224 http://ftpmaster.internal/ubuntu bionic/main s390x x11proto-damage-dev all 1:1.2.1-2 [8286 B] Get:225 http://ftpmaster.internal/ubuntu bionic/main s390x libxdamage-dev s390x 1:1.1.4-3 [4876 B] Get:226 http://ftpmaster.internal/ubuntu bionic/main s390x libxml2-utils s390x 2.9.4+dfsg1-5.2ubuntu1 [34.1 kB] Get:227 http://ftpmaster.internal/ubuntu bionic/main s390x libgtk2.0-dev s390x 2.24.31-4ubuntu1 [2535 kB] Get:228 http://ftpmaster.internal/ubuntu bionic/main s390x libnotify-dev s390x 0.7.7-3 [16.9 kB] Get:229 http://ftpmaster.internal/ubuntu bionic/universe s390x libunique-1.0-0 s390x 1.1.6-6 [20.9 kB] Get:230 http://ftpmaster.internal/ubuntu bionic/universe s390x libunique-dev s390x 1.1.6-6 [22.6 kB] Get:231 http://ftpmaster.internal/ubuntu bionic/main s390x libxml2-dev s390x 2.9.4+dfsg1-5.2ubuntu1 [694 kB] debconf: delaying package configuration, since apt-utils is not installed Fetched 69.4 MB in 2s (27.2 MB/s) (Reading database ... 12441 files and directories currently installed.) Removing pkg-create-dbgsym (0.73) ... Selecting previously unselected package libpython3.6-minimal:s390x. (Reading database ... 12432 files and directories currently installed.) Preparing to unpack .../00-libpython3.6-minimal_3.6.4-1_s390x.deb ... Unpacking libpython3.6-minimal:s390x (3.6.4-1) ... Selecting previously unselected package libexpat1:s390x. Preparing to unpack .../01-libexpat1_2.2.5-3_s390x.deb ... Unpacking libexpat1:s390x (2.2.5-3) ... Selecting previously unselected package python3.6-minimal. Preparing to unpack .../02-python3.6-minimal_3.6.4-1_s390x.deb ... Unpacking python3.6-minimal (3.6.4-1) ... Selecting previously unselected package python3-minimal. Preparing to unpack .../03-python3-minimal_3.6.3-0ubuntu2_s390x.deb ... Unpacking python3-minimal (3.6.3-0ubuntu2) ... Selecting previously unselected package mime-support. Preparing to unpack .../04-mime-support_3.60ubuntu1_all.deb ... Unpacking mime-support (3.60ubuntu1) ... Selecting previously unselected package libmpdec2:s390x. Preparing to unpack .../05-libmpdec2_2.4.2-1_s390x.deb ... Unpacking libmpdec2:s390x (2.4.2-1) ... Selecting previously unselected package libpython3.6-stdlib:s390x. Preparing to unpack .../06-libpython3.6-stdlib_3.6.4-1_s390x.deb ... Unpacking libpython3.6-stdlib:s390x (3.6.4-1) ... Selecting previously unselected package python3.6-2to3. Preparing to unpack .../07-python3.6-2to3_3.6.4-1_all.deb ... Unpacking python3.6-2to3 (3.6.4-1) ... Selecting previously unselected package python3-distutils. Preparing to unpack .../08-python3-distutils_3.6.4~rc1-6_all.deb ... Unpacking python3-distutils (3.6.4~rc1-6) ... Selecting previously unselected package python3.6. Preparing to unpack .../09-python3.6_3.6.4-1_s390x.deb ... Unpacking python3.6 (3.6.4-1) ... Selecting previously unselected package libpython3-stdlib:s390x. Preparing to unpack .../10-libpython3-stdlib_3.6.3-0ubuntu2_s390x.deb ... Unpacking libpython3-stdlib:s390x (3.6.3-0ubuntu2) ... Selecting previously unselected package dh-python. Preparing to unpack .../11-dh-python_2.20170125_all.deb ... Unpacking dh-python (2.20170125) ... Setting up libpython3.6-minimal:s390x (3.6.4-1) ... Setting up libexpat1:s390x (2.2.5-3) ... Setting up python3.6-minimal (3.6.4-1) ... Setting up python3-minimal (3.6.3-0ubuntu2) ... Selecting previously unselected package python3. (Reading database ... 13353 files and directories currently installed.) Preparing to unpack .../000-python3_3.6.3-0ubuntu2_s390x.deb ... Unpacking python3 (3.6.3-0ubuntu2) ... Selecting previously unselected package groff-base. Preparing to unpack .../001-groff-base_1.22.3-9_s390x.deb ... Unpacking groff-base (1.22.3-9) ... Selecting previously unselected package libbsd0:s390x. Preparing to unpack .../002-libbsd0_0.8.6-3_s390x.deb ... Unpacking libbsd0:s390x (0.8.6-3) ... Selecting previously unselected package bsdmainutils. Preparing to unpack .../003-bsdmainutils_9.0.14ubuntu1_s390x.deb ... Unpacking bsdmainutils (9.0.14ubuntu1) ... Selecting previously unselected package libpipeline1:s390x. Preparing to unpack .../004-libpipeline1_1.5.0-1_s390x.deb ... Unpacking libpipeline1:s390x (1.5.0-1) ... Selecting previously unselected package man-db. Preparing to unpack .../005-man-db_2.7.6.1-4_s390x.deb ... Unpacking man-db (2.7.6.1-4) ... Selecting previously unselected package libfreetype6:s390x. Preparing to unpack .../006-libfreetype6_2.8-0.2ubuntu2_s390x.deb ... Unpacking libfreetype6:s390x (2.8-0.2ubuntu2) ... Selecting previously unselected package ucf. Preparing to unpack .../007-ucf_3.0036_all.deb ... Moving old data out of the way Unpacking ucf (3.0036) ... Selecting previously unselected package fonts-dejavu-core. Preparing to unpack .../008-fonts-dejavu-core_2.37-1_all.deb ... Unpacking fonts-dejavu-core (2.37-1) ... Selecting previously unselected package fontconfig-config. Preparing to unpack .../009-fontconfig-config_2.12.6-0ubuntu1_all.deb ... Unpacking fontconfig-config (2.12.6-0ubuntu1) ... Selecting previously unselected package libfontconfig1:s390x. Preparing to unpack .../010-libfontconfig1_2.12.6-0ubuntu1_s390x.deb ... Unpacking libfontconfig1:s390x (2.12.6-0ubuntu1) ... Selecting previously unselected package fontconfig. Preparing to unpack .../011-fontconfig_2.12.6-0ubuntu1_s390x.deb ... Unpacking fontconfig (2.12.6-0ubuntu1) ... Selecting previously unselected package libdbusmenu-glib4:s390x. Preparing to unpack .../012-libdbusmenu-glib4_16.04.1+18.04.20171206-0ubuntu1_s390x.deb ... Unpacking libdbusmenu-glib4:s390x (16.04.1+18.04.20171206-0ubuntu1) ... Selecting previously unselected package libglib2.0-0:s390x. Preparing to unpack .../013-libglib2.0-0_2.54.1-1ubuntu1_s390x.deb ... Unpacking libglib2.0-0:s390x (2.54.1-1ubuntu1) ... Selecting previously unselected package libatk1.0-data. Preparing to unpack .../014-libatk1.0-data_2.26.1-2_all.deb ... Unpacking libatk1.0-data (2.26.1-2) ... Selecting previously unselected package libatk1.0-0:s390x. Preparing to unpack .../015-libatk1.0-0_2.26.1-2_s390x.deb ... Unpacking libatk1.0-0:s390x (2.26.1-2) ... Selecting previously unselected package libjpeg-turbo8:s390x. Preparing to unpack .../016-libjpeg-turbo8_1.5.2-0ubuntu5_s390x.deb ... Unpacking libjpeg-turbo8:s390x (1.5.2-0ubuntu5) ... Selecting previously unselected package libjpeg8:s390x. Preparing to unpack .../017-libjpeg8_8c-2ubuntu8_s390x.deb ... Unpacking libjpeg8:s390x (8c-2ubuntu8) ... Selecting previously unselected package libjbig0:s390x. Preparing to unpack .../018-libjbig0_2.1-3.1_s390x.deb ... Unpacking libjbig0:s390x (2.1-3.1) ... Selecting previously unselected package libtiff5:s390x. Preparing to unpack .../019-libtiff5_4.0.9-2_s390x.deb ... Unpacking libtiff5:s390x (4.0.9-2) ... Selecting previously unselected package libxau6:s390x. Preparing to unpack .../020-libxau6_1%3a1.0.8-1_s390x.deb ... Unpacking libxau6:s390x (1:1.0.8-1) ... Selecting previously unselected package libxdmcp6:s390x. Preparing to unpack .../021-libxdmcp6_1%3a1.1.2-3_s390x.deb ... Unpacking libxdmcp6:s390x (1:1.1.2-3) ... Selecting previously unselected package libxcb1:s390x. Preparing to unpack .../022-libxcb1_1.12-1ubuntu1_s390x.deb ... Unpacking libxcb1:s390x (1.12-1ubuntu1) ... Selecting previously unselected package libx11-data. Preparing to unpack .../023-libx11-data_2%3a1.6.4-3_all.deb ... Unpacking libx11-data (2:1.6.4-3) ... Selecting previously unselected package libx11-6:s390x. Preparing to unpack .../024-libx11-6_2%3a1.6.4-3_s390x.deb ... Unpacking libx11-6:s390x (2:1.6.4-3) ... Selecting previously unselected package libgraphite2-3:s390x. Preparing to unpack .../025-libgraphite2-3_1.3.10-8_s390x.deb ... Unpacking libgraphite2-3:s390x (1.3.10-8) ... Selecting previously unselected package libharfbuzz0b:s390x. Preparing to unpack .../026-libharfbuzz0b_1.7.2-1_s390x.deb ... Unpacking libharfbuzz0b:s390x (1.7.2-1) ... Selecting previously unselected package libicu-le-hb0:s390x. Preparing to unpack .../027-libicu-le-hb0_1.0.3+git161113-4_s390x.deb ... Unpacking libicu-le-hb0:s390x (1.0.3+git161113-4) ... Selecting previously unselected package libicu60:s390x. Preparing to unpack .../028-libicu60_60.2-1ubuntu1_s390x.deb ... Unpacking libicu60:s390x (60.2-1ubuntu1) ... Selecting previously unselected package libxml2:s390x. Preparing to unpack .../029-libxml2_2.9.4+dfsg1-5.2ubuntu1_s390x.deb ... Unpacking libxml2:s390x (2.9.4+dfsg1-5.2ubuntu1) ... Selecting previously unselected package shared-mime-info. Preparing to unpack .../030-shared-mime-info_1.9-2_s390x.deb ... Unpacking shared-mime-info (1.9-2) ... Selecting previously unselected package libgdk-pixbuf2.0-common. Preparing to unpack .../031-libgdk-pixbuf2.0-common_2.36.11-1_all.deb ... Unpacking libgdk-pixbuf2.0-common (2.36.11-1) ... Selecting previously unselected package libgdk-pixbuf2.0-0:s390x. Preparing to unpack .../032-libgdk-pixbuf2.0-0_2.36.11-1_s390x.deb ... Unpacking libgdk-pixbuf2.0-0:s390x (2.36.11-1) ... Selecting previously unselected package libthai-data. Preparing to unpack .../033-libthai-data_0.1.27-1_all.deb ... Unpacking libthai-data (0.1.27-1) ... Selecting previously unselected package libdatrie1:s390x. Preparing to unpack .../034-libdatrie1_0.2.10-5_s390x.deb ... Unpacking libdatrie1:s390x (0.2.10-5) ... Selecting previously unselected package libthai0:s390x. Preparing to unpack .../035-libthai0_0.1.27-1_s390x.deb ... Unpacking libthai0:s390x (0.1.27-1) ... Selecting previously unselected package libpango-1.0-0:s390x. Preparing to unpack .../036-libpango-1.0-0_1.40.14-1_s390x.deb ... Unpacking libpango-1.0-0:s390x (1.40.14-1) ... Selecting previously unselected package libdbusmenu-gtk4:s390x. Preparing to unpack .../037-libdbusmenu-gtk4_16.04.1+18.04.20171206-0ubuntu1_s390x.deb ... Unpacking libdbusmenu-gtk4:s390x (16.04.1+18.04.20171206-0ubuntu1) ... Selecting previously unselected package libgtk2.0-common. Preparing to unpack .../038-libgtk2.0-common_2.24.31-4ubuntu1_all.deb ... Unpacking libgtk2.0-common (2.24.31-4ubuntu1) ... Selecting previously unselected package libpixman-1-0:s390x. Preparing to unpack .../039-libpixman-1-0_0.34.0-2_s390x.deb ... Unpacking libpixman-1-0:s390x (0.34.0-2) ... Selecting previously unselected package libxcb-render0:s390x. Preparing to unpack .../040-libxcb-render0_1.12-1ubuntu1_s390x.deb ... Unpacking libxcb-render0:s390x (1.12-1ubuntu1) ... Selecting previously unselected package libxcb-shm0:s390x. Preparing to unpack .../041-libxcb-shm0_1.12-1ubuntu1_s390x.deb ... Unpacking libxcb-shm0:s390x (1.12-1ubuntu1) ... Selecting previously unselected package libxext6:s390x. Preparing to unpack .../042-libxext6_2%3a1.3.3-1_s390x.deb ... Unpacking libxext6:s390x (2:1.3.3-1) ... Selecting previously unselected package libxrender1:s390x. Preparing to unpack .../043-libxrender1_1%3a0.9.10-1_s390x.deb ... Unpacking libxrender1:s390x (1:0.9.10-1) ... Selecting previously unselected package libcairo2:s390x. Preparing to unpack .../044-libcairo2_1.15.8-3_s390x.deb ... Unpacking libcairo2:s390x (1.15.8-3) ... Selecting previously unselected package libavahi-common-data:s390x. Preparing to unpack .../045-libavahi-common-data_0.6.32-1ubuntu1_s390x.deb ... Unpacking libavahi-common-data:s390x (0.6.32-1ubuntu1) ... Selecting previously unselected package libavahi-common3:s390x. Preparing to unpack .../046-libavahi-common3_0.6.32-1ubuntu1_s390x.deb ... Unpacking libavahi-common3:s390x (0.6.32-1ubuntu1) ... Selecting previously unselected package libdbus-1-3:s390x. Preparing to unpack .../047-libdbus-1-3_1.12.2-1ubuntu1_s390x.deb ... Unpacking libdbus-1-3:s390x (1.12.2-1ubuntu1) ... Selecting previously unselected package libavahi-client3:s390x. Preparing to unpack .../048-libavahi-client3_0.6.32-1ubuntu1_s390x.deb ... Unpacking libavahi-client3:s390x (0.6.32-1ubuntu1) ... Selecting previously unselected package libcups2:s390x. Preparing to unpack .../049-libcups2_2.2.6-3_s390x.deb ... Unpacking libcups2:s390x (2.2.6-3) ... Selecting previously unselected package libpangoft2-1.0-0:s390x. Preparing to unpack .../050-libpangoft2-1.0-0_1.40.14-1_s390x.deb ... Unpacking libpangoft2-1.0-0:s390x (1.40.14-1) ... Selecting previously unselected package libpangocairo-1.0-0:s390x. Preparing to unpack .../051-libpangocairo-1.0-0_1.40.14-1_s390x.deb ... Unpacking libpangocairo-1.0-0:s390x (1.40.14-1) ... Selecting previously unselected package libxcomposite1:s390x. Preparing to unpack .../052-libxcomposite1_1%3a0.4.4-2_s390x.deb ... Unpacking libxcomposite1:s390x (1:0.4.4-2) ... Selecting previously unselected package libxfixes3:s390x. Preparing to unpack .../053-libxfixes3_1%3a5.0.3-1_s390x.deb ... Unpacking libxfixes3:s390x (1:5.0.3-1) ... Selecting previously unselected package libxcursor1:s390x. Preparing to unpack .../054-libxcursor1_1%3a1.1.15-1_s390x.deb ... Unpacking libxcursor1:s390x (1:1.1.15-1) ... Selecting previously unselected package libxdamage1:s390x. Preparing to unpack .../055-libxdamage1_1%3a1.1.4-3_s390x.deb ... Unpacking libxdamage1:s390x (1:1.1.4-3) ... Selecting previously unselected package libxi6:s390x. Preparing to unpack .../056-libxi6_2%3a1.7.9-1_s390x.deb ... Unpacking libxi6:s390x (2:1.7.9-1) ... Selecting previously unselected package libxinerama1:s390x. Preparing to unpack .../057-libxinerama1_2%3a1.1.3-1_s390x.deb ... Unpacking libxinerama1:s390x (2:1.1.3-1) ... Selecting previously unselected package libxrandr2:s390x. Preparing to unpack .../058-libxrandr2_2%3a1.5.1-1_s390x.deb ... Unpacking libxrandr2:s390x (2:1.5.1-1) ... Selecting previously unselected package hicolor-icon-theme. Preparing to unpack .../059-hicolor-icon-theme_0.17-1_all.deb ... Unpacking hicolor-icon-theme (0.17-1) ... Selecting previously unselected package gtk-update-icon-cache. Preparing to unpack .../060-gtk-update-icon-cache_3.22.26-2ubuntu1_s390x.deb ... No diversion 'diversion of /usr/sbin/update-icon-caches to /usr/sbin/update-icon-caches.gtk2 by libgtk-3-bin', none removed. No diversion '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', none removed. Unpacking gtk-update-icon-cache (3.22.26-2ubuntu1) ... Selecting previously unselected package libcroco3:s390x. Preparing to unpack .../061-libcroco3_0.6.12-2_s390x.deb ... Unpacking libcroco3:s390x (0.6.12-2) ... Selecting previously unselected package librsvg2-2:s390x. Preparing to unpack .../062-librsvg2-2_2.40.18-2_s390x.deb ... Unpacking librsvg2-2:s390x (2.40.18-2) ... Selecting previously unselected package librsvg2-common:s390x. Preparing to unpack .../063-librsvg2-common_2.40.18-2_s390x.deb ... Unpacking librsvg2-common:s390x (2.40.18-2) ... Selecting previously unselected package humanity-icon-theme. Preparing to unpack .../064-humanity-icon-theme_0.6.13_all.deb ... Unpacking humanity-icon-theme (0.6.13) ... Selecting previously unselected package ubuntu-mono. Preparing to unpack .../065-ubuntu-mono_16.10+18.04.20171115.1-0ubuntu1_all.deb ... Unpacking ubuntu-mono (16.10+18.04.20171115.1-0ubuntu1) ... Selecting previously unselected package adwaita-icon-theme. Preparing to unpack .../066-adwaita-icon-theme_3.26.1-1ubuntu1_all.deb ... Unpacking adwaita-icon-theme (3.26.1-1ubuntu1) ... Selecting previously unselected package gnome-icon-theme. Preparing to unpack .../067-gnome-icon-theme_3.12.0-2_all.deb ... Unpacking gnome-icon-theme (3.12.0-2) ... Selecting previously unselected package libgtk2.0-0:s390x. Preparing to unpack .../068-libgtk2.0-0_2.24.31-4ubuntu1_s390x.deb ... Unpacking libgtk2.0-0:s390x (2.24.31-4ubuntu1) ... Selecting previously unselected package libindicator7. Preparing to unpack .../069-libindicator7_16.10.0+18.04.20171205.1-0ubuntu1_s390x.deb ... Unpacking libindicator7 (16.10.0+18.04.20171205.1-0ubuntu1) ... Selecting previously unselected package libappindicator1. Preparing to unpack .../070-libappindicator1_12.10.1+17.04.20170215-0ubuntu2_s390x.deb ... Unpacking libappindicator1 (12.10.1+17.04.20170215-0ubuntu2) ... Selecting previously unselected package dbus. Preparing to unpack .../071-dbus_1.12.2-1ubuntu1_s390x.deb ... Unpacking dbus (1.12.2-1ubuntu1) ... Selecting previously unselected package libmagic-mgc. Preparing to unpack .../072-libmagic-mgc_1%3a5.32-1_s390x.deb ... Unpacking libmagic-mgc (1:5.32-1) ... Selecting previously unselected package libmagic1:s390x. Preparing to unpack .../073-libmagic1_1%3a5.32-1_s390x.deb ... Unpacking libmagic1:s390x (1:5.32-1) ... Selecting previously unselected package file. Preparing to unpack .../074-file_1%3a5.32-1_s390x.deb ... Unpacking file (1:5.32-1) ... Selecting previously unselected package libcap2-bin. Preparing to unpack .../075-libcap2-bin_1%3a2.25-1.2_s390x.deb ... Unpacking libcap2-bin (1:2.25-1.2) ... Selecting previously unselected package libelf1:s390x. Preparing to unpack .../076-libelf1_0.170-0.1_s390x.deb ... Unpacking libelf1:s390x (0.170-0.1) ... Selecting previously unselected package libglib2.0-data. Preparing to unpack .../077-libglib2.0-data_2.54.1-1ubuntu1_all.deb ... Unpacking libglib2.0-data (2.54.1-1ubuntu1) ... Selecting previously unselected package libpam-systemd:s390x. Preparing to unpack .../078-libpam-systemd_235-3ubuntu2_s390x.deb ... Unpacking libpam-systemd:s390x (235-3ubuntu2) ... Selecting previously unselected package netbase. Preparing to unpack .../079-netbase_5.4_all.deb ... Unpacking netbase (5.4) ... Selecting previously unselected package gettext-base. Preparing to unpack .../080-gettext-base_0.19.8.1-4ubuntu2_s390x.deb ... Unpacking gettext-base (0.19.8.1-4ubuntu2) ... Selecting previously unselected package libgirepository-1.0-1:s390x. Preparing to unpack .../081-libgirepository-1.0-1_1.54.1-4_s390x.deb ... Unpacking libgirepository-1.0-1:s390x (1.54.1-4) ... Selecting previously unselected package gir1.2-glib-2.0:s390x. Preparing to unpack .../082-gir1.2-glib-2.0_1.54.1-4_s390x.deb ... Unpacking gir1.2-glib-2.0:s390x (1.54.1-4) ... Selecting previously unselected package libdbus-glib-1-2:s390x. Preparing to unpack .../083-libdbus-glib-1-2_0.108-3_s390x.deb ... Unpacking libdbus-glib-1-2:s390x (0.108-3) ... Selecting previously unselected package psmisc. Preparing to unpack .../084-psmisc_23.1-1_s390x.deb ... Unpacking psmisc (23.1-1) ... Selecting previously unselected package libsigsegv2:s390x. Preparing to unpack .../085-libsigsegv2_2.11-1_s390x.deb ... Unpacking libsigsegv2:s390x (2.11-1) ... Selecting previously unselected package m4. Preparing to unpack .../086-m4_1.4.18-1_s390x.deb ... Unpacking m4 (1.4.18-1) ... Selecting previously unselected package autoconf. Preparing to unpack .../087-autoconf_2.69-11_all.deb ... Unpacking autoconf (2.69-11) ... Selecting previously unselected package autotools-dev. Preparing to unpack .../088-autotools-dev_20171216.1_all.deb ... Unpacking autotools-dev (20171216.1) ... Selecting previously unselected package automake. Preparing to unpack .../089-automake_1%3a1.15.1-3ubuntu1_all.deb ... Unpacking automake (1:1.15.1-3ubuntu1) ... Selecting previously unselected package autopoint. Preparing to unpack .../090-autopoint_0.19.8.1-4ubuntu2_all.deb ... Unpacking autopoint (0.19.8.1-4ubuntu2) ... Selecting previously unselected package dbus-user-session. Preparing to unpack .../091-dbus-user-session_1.12.2-1ubuntu1_s390x.deb ... Unpacking dbus-user-session (1.12.2-1ubuntu1) ... Selecting previously unselected package libtool. Preparing to unpack .../092-libtool_2.4.6-2_all.deb ... Unpacking libtool (2.4.6-2) ... Selecting previously unselected package dh-autoreconf. Preparing to unpack .../093-dh-autoreconf_15_all.deb ... Unpacking dh-autoreconf (15) ... Selecting previously unselected package libarchive-zip-perl. Preparing to unpack .../094-libarchive-zip-perl_1.60-1_all.deb ... Unpacking libarchive-zip-perl (1.60-1) ... Selecting previously unselected package libfile-stripnondeterminism-perl. Preparing to unpack .../095-libfile-stripnondeterminism-perl_0.040-1_all.deb ... Unpacking libfile-stripnondeterminism-perl (0.040-1) ... Selecting previously unselected package libtimedate-perl. Preparing to unpack .../096-libtimedate-perl_2.3000-2_all.deb ... Unpacking libtimedate-perl (2.3000-2) ... Selecting previously unselected package dh-strip-nondeterminism. Preparing to unpack .../097-dh-strip-nondeterminism_0.040-1_all.deb ... Unpacking dh-strip-nondeterminism (0.040-1) ... Selecting previously unselected package gettext. Preparing to unpack .../098-gettext_0.19.8.1-4ubuntu2_s390x.deb ... Unpacking gettext (0.19.8.1-4ubuntu2) ... Selecting previously unselected package intltool-debian. Preparing to unpack .../099-intltool-debian_0.35.0+20060710.4_all.deb ... Unpacking intltool-debian (0.35.0+20060710.4) ... Selecting previously unselected package po-debconf. Preparing to unpack .../100-po-debconf_1.0.20_all.deb ... Unpacking po-debconf (1.0.20) ... Selecting previously unselected package debhelper. Preparing to unpack .../101-debhelper_11ubuntu1_all.deb ... Unpacking debhelper (11ubuntu1) ... Selecting previously unselected package gconf2-common. Preparing to unpack .../102-gconf2-common_3.2.6-4ubuntu1_all.deb ... Unpacking gconf2-common (3.2.6-4ubuntu1) ... Selecting previously unselected package libgconf-2-4:s390x. Preparing to unpack .../103-libgconf-2-4_3.2.6-4ubuntu1_s390x.deb ... Unpacking libgconf-2-4:s390x (3.2.6-4ubuntu1) ... Selecting previously unselected package gconf-service-backend. Preparing to unpack .../104-gconf-service-backend_3.2.6-4ubuntu1_s390x.deb ... Unpacking gconf-service-backend (3.2.6-4ubuntu1) ... Selecting previously unselected package gconf-service. Preparing to unpack .../105-gconf-service_3.2.6-4ubuntu1_s390x.deb ... Unpacking gconf-service (3.2.6-4ubuntu1) ... Selecting previously unselected package gconf2. Preparing to unpack .../106-gconf2_3.2.6-4ubuntu1_s390x.deb ... Unpacking gconf2 (3.2.6-4ubuntu1) ... Selecting previously unselected package gir1.2-atk-1.0:s390x. Preparing to unpack .../107-gir1.2-atk-1.0_2.26.1-2_s390x.deb ... Unpacking gir1.2-atk-1.0:s390x (2.26.1-2) ... Selecting previously unselected package gir1.2-freedesktop:s390x. Preparing to unpack .../108-gir1.2-freedesktop_1.54.1-4_s390x.deb ... Unpacking gir1.2-freedesktop:s390x (1.54.1-4) ... Selecting previously unselected package gir1.2-gdkpixbuf-2.0:s390x. Preparing to unpack .../109-gir1.2-gdkpixbuf-2.0_2.36.11-1_s390x.deb ... Unpacking gir1.2-gdkpixbuf-2.0:s390x (2.36.11-1) ... Selecting previously unselected package libxft2:s390x. Preparing to unpack .../110-libxft2_2.3.2-1_s390x.deb ... Unpacking libxft2:s390x (2.3.2-1) ... Selecting previously unselected package libpangoxft-1.0-0:s390x. Preparing to unpack .../111-libpangoxft-1.0-0_1.40.14-1_s390x.deb ... Unpacking libpangoxft-1.0-0:s390x (1.40.14-1) ... Selecting previously unselected package gir1.2-pango-1.0:s390x. Preparing to unpack .../112-gir1.2-pango-1.0_1.40.14-1_s390x.deb ... Unpacking gir1.2-pango-1.0:s390x (1.40.14-1) ... Selecting previously unselected package gir1.2-gtk-2.0. Preparing to unpack .../113-gir1.2-gtk-2.0_2.24.31-4ubuntu1_s390x.deb ... Unpacking gir1.2-gtk-2.0 (2.24.31-4ubuntu1) ... Selecting previously unselected package gir1.2-appindicator-0.1. Preparing to unpack .../114-gir1.2-appindicator-0.1_12.10.1+17.04.20170215-0ubuntu2_s390x.deb ... Unpacking gir1.2-appindicator-0.1 (12.10.1+17.04.20170215-0ubuntu2) ... Selecting previously unselected package gir1.2-dbusmenu-glib-0.4:s390x. Preparing to unpack .../115-gir1.2-dbusmenu-glib-0.4_16.04.1+18.04.20171206-0ubuntu1_s390x.deb ... Unpacking gir1.2-dbusmenu-glib-0.4:s390x (16.04.1+18.04.20171206-0ubuntu1) ... Selecting previously unselected package gir1.2-gconf-2.0. Preparing to unpack .../116-gir1.2-gconf-2.0_3.2.6-4ubuntu1_s390x.deb ... Unpacking gir1.2-gconf-2.0 (3.2.6-4ubuntu1) ... Selecting previously unselected package libgstreamer1.0-0:s390x. Preparing to unpack .../117-libgstreamer1.0-0_1.12.4-1_s390x.deb ... Unpacking libgstreamer1.0-0:s390x (1.12.4-1) ... Selecting previously unselected package gir1.2-gstreamer-1.0. Preparing to unpack .../118-gir1.2-gstreamer-1.0_1.12.4-1_s390x.deb ... Unpacking gir1.2-gstreamer-1.0 (1.12.4-1) ... Selecting previously unselected package gir1.2-harfbuzz-0.0:s390x. Preparing to unpack .../119-gir1.2-harfbuzz-0.0_1.7.2-1_s390x.deb ... Unpacking gir1.2-harfbuzz-0.0:s390x (1.7.2-1) ... Selecting previously unselected package libnotify4:s390x. Preparing to unpack .../120-libnotify4_0.7.7-3_s390x.deb ... Unpacking libnotify4:s390x (0.7.7-3) ... Selecting previously unselected package gir1.2-notify-0.7:s390x. Preparing to unpack .../121-gir1.2-notify-0.7_0.7.7-3_s390x.deb ... Unpacking gir1.2-notify-0.7:s390x (0.7.7-3) ... Selecting previously unselected package icu-devtools. Preparing to unpack .../122-icu-devtools_60.2-1ubuntu1_s390x.deb ... Unpacking icu-devtools (60.2-1ubuntu1) ... Selecting previously unselected package liburi-perl. Preparing to unpack .../123-liburi-perl_1.72-2_all.deb ... Unpacking liburi-perl (1.72-2) ... Selecting previously unselected package libencode-locale-perl. Preparing to unpack .../124-libencode-locale-perl_1.05-1_all.deb ... Unpacking libencode-locale-perl (1.05-1) ... Selecting previously unselected package libhttp-date-perl. Preparing to unpack .../125-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 .../126-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 .../127-libhtml-tagset-perl_3.20-3_all.deb ... Unpacking libhtml-tagset-perl (3.20-3) ... Selecting previously unselected package libhtml-parser-perl. Preparing to unpack .../128-libhtml-parser-perl_3.72-3build1_s390x.deb ... Unpacking libhtml-parser-perl (3.72-3build1) ... Selecting previously unselected package libhtml-tree-perl. Preparing to unpack .../129-libhtml-tree-perl_5.07-1_all.deb ... Unpacking libhtml-tree-perl (5.07-1) ... Selecting previously unselected package libio-html-perl. Preparing to unpack .../130-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 .../131-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 .../132-libhttp-message-perl_6.13-1_all.deb ... Unpacking libhttp-message-perl (6.13-1) ... Selecting previously unselected package libhttp-cookies-perl. Preparing to unpack .../133-libhttp-cookies-perl_6.04-1_all.deb ... Unpacking libhttp-cookies-perl (6.04-1) ... Selecting previously unselected package libhttp-negotiate-perl. Preparing to unpack .../134-libhttp-negotiate-perl_6.00-2_all.deb ... Unpacking libhttp-negotiate-perl (6.00-2) ... Selecting previously unselected package perl-openssl-defaults:s390x. Preparing to unpack .../135-perl-openssl-defaults_3_s390x.deb ... Unpacking perl-openssl-defaults:s390x (3) ... Selecting previously unselected package libnet-ssleay-perl. Preparing to unpack .../136-libnet-ssleay-perl_1.80-1build1_s390x.deb ... Unpacking libnet-ssleay-perl (1.80-1build1) ... Selecting previously unselected package libio-socket-ssl-perl. Preparing to unpack .../137-libio-socket-ssl-perl_2.052-1_all.deb ... Unpacking libio-socket-ssl-perl (2.052-1) ... Selecting previously unselected package libnet-http-perl. Preparing to unpack .../138-libnet-http-perl_6.17-1_all.deb ... Unpacking libnet-http-perl (6.17-1) ... Selecting previously unselected package liblwp-protocol-https-perl. Preparing to unpack .../139-liblwp-protocol-https-perl_6.07-2_all.deb ... Unpacking liblwp-protocol-https-perl (6.07-2) ... Selecting previously unselected package libtry-tiny-perl. Preparing to unpack .../140-libtry-tiny-perl_0.30-1_all.deb ... Unpacking libtry-tiny-perl (0.30-1) ... Selecting previously unselected package libwww-robotrules-perl. Preparing to unpack .../141-libwww-robotrules-perl_6.01-1_all.deb ... Unpacking libwww-robotrules-perl (6.01-1) ... Selecting previously unselected package libwww-perl. Preparing to unpack .../142-libwww-perl_6.29-1_all.deb ... Unpacking libwww-perl (6.29-1) ... Selecting previously unselected package libxml-parser-perl. Preparing to unpack .../143-libxml-parser-perl_2.44-2build3_s390x.deb ... Unpacking libxml-parser-perl (2.44-2build3) ... Selecting previously unselected package intltool. Preparing to unpack .../144-intltool_0.51.0-5_all.deb ... Unpacking intltool (0.51.0-5) ... Selecting previously unselected package pkg-config. Preparing to unpack .../145-pkg-config_0.29.1-0ubuntu2_s390x.deb ... Unpacking pkg-config (0.29.1-0ubuntu2) ... Selecting previously unselected package libdbus-1-dev:s390x. Preparing to unpack .../146-libdbus-1-dev_1.12.2-1ubuntu1_s390x.deb ... Unpacking libdbus-1-dev:s390x (1.12.2-1ubuntu1) ... Selecting previously unselected package libglib2.0-bin. Preparing to unpack .../147-libglib2.0-bin_2.54.1-1ubuntu1_s390x.deb ... Unpacking libglib2.0-bin (2.54.1-1ubuntu1) ... Selecting previously unselected package libglib2.0-dev-bin. Preparing to unpack .../148-libglib2.0-dev-bin_2.54.1-1ubuntu1_s390x.deb ... Unpacking libglib2.0-dev-bin (2.54.1-1ubuntu1) ... Selecting previously unselected package libpcre16-3:s390x. Preparing to unpack .../149-libpcre16-3_2%3a8.39-8_s390x.deb ... Unpacking libpcre16-3:s390x (2:8.39-8) ... Selecting previously unselected package libpcre32-3:s390x. Preparing to unpack .../150-libpcre32-3_2%3a8.39-8_s390x.deb ... Unpacking libpcre32-3:s390x (2:8.39-8) ... Selecting previously unselected package libpcrecpp0v5:s390x. Preparing to unpack .../151-libpcrecpp0v5_2%3a8.39-8_s390x.deb ... Unpacking libpcrecpp0v5:s390x (2:8.39-8) ... Selecting previously unselected package libpcre3-dev:s390x. Preparing to unpack .../152-libpcre3-dev_2%3a8.39-8_s390x.deb ... Unpacking libpcre3-dev:s390x (2:8.39-8) ... Selecting previously unselected package zlib1g-dev:s390x. Preparing to unpack .../153-zlib1g-dev_1%3a1.2.11.dfsg-0ubuntu2_s390x.deb ... Unpacking zlib1g-dev:s390x (1:1.2.11.dfsg-0ubuntu2) ... Selecting previously unselected package libglib2.0-dev:s390x. Preparing to unpack .../154-libglib2.0-dev_2.54.1-1ubuntu1_s390x.deb ... Unpacking libglib2.0-dev:s390x (2.54.1-1ubuntu1) ... Selecting previously unselected package libdbus-glib-1-dev. Preparing to unpack .../155-libdbus-glib-1-dev_0.108-3_s390x.deb ... Unpacking libdbus-glib-1-dev (0.108-3) ... Selecting previously unselected package libdbusmenu-glib-dev:s390x. Preparing to unpack .../156-libdbusmenu-glib-dev_16.04.1+18.04.20171206-0ubuntu1_s390x.deb ... Unpacking libdbusmenu-glib-dev:s390x (16.04.1+18.04.20171206-0ubuntu1) ... Selecting previously unselected package libappindicator-dev. Preparing to unpack .../157-libappindicator-dev_12.10.1+17.04.20170215-0ubuntu2_s390x.deb ... Unpacking libappindicator-dev (12.10.1+17.04.20170215-0ubuntu2) ... Selecting previously unselected package libatk1.0-dev:s390x. Preparing to unpack .../158-libatk1.0-dev_2.26.1-2_s390x.deb ... Unpacking libatk1.0-dev:s390x (2.26.1-2) ... Selecting previously unselected package libcairo-gobject2:s390x. Preparing to unpack .../159-libcairo-gobject2_1.15.8-3_s390x.deb ... Unpacking libcairo-gobject2:s390x (1.15.8-3) ... Selecting previously unselected package liblzo2-2:s390x. Preparing to unpack .../160-liblzo2-2_2.08-1.2_s390x.deb ... Unpacking liblzo2-2:s390x (2.08-1.2) ... Selecting previously unselected package libcairo-script-interpreter2:s390x. Preparing to unpack .../161-libcairo-script-interpreter2_1.15.8-3_s390x.deb ... Unpacking libcairo-script-interpreter2:s390x (1.15.8-3) ... Selecting previously unselected package libexpat1-dev:s390x. Preparing to unpack .../162-libexpat1-dev_2.2.5-3_s390x.deb ... Unpacking libexpat1-dev:s390x (2.2.5-3) ... Selecting previously unselected package libpng-dev:s390x. Preparing to unpack .../163-libpng-dev_1.6.34-1_s390x.deb ... Unpacking libpng-dev:s390x (1.6.34-1) ... Selecting previously unselected package libfreetype6-dev:s390x. Preparing to unpack .../164-libfreetype6-dev_2.8-0.2ubuntu2_s390x.deb ... Unpacking libfreetype6-dev:s390x (2.8-0.2ubuntu2) ... Selecting previously unselected package libfontconfig1-dev:s390x. Preparing to unpack .../165-libfontconfig1-dev_2.12.6-0ubuntu1_s390x.deb ... Unpacking libfontconfig1-dev:s390x (2.12.6-0ubuntu1) ... Selecting previously unselected package xorg-sgml-doctools. Preparing to unpack .../166-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 .../167-x11proto-core-dev_7.0.31-1_all.deb ... Unpacking x11proto-core-dev (7.0.31-1) ... Selecting previously unselected package libxau-dev:s390x. Preparing to unpack .../168-libxau-dev_1%3a1.0.8-1_s390x.deb ... Unpacking libxau-dev:s390x (1:1.0.8-1) ... Selecting previously unselected package libxdmcp-dev:s390x. Preparing to unpack .../169-libxdmcp-dev_1%3a1.1.2-3_s390x.deb ... Unpacking libxdmcp-dev:s390x (1:1.1.2-3) ... Selecting previously unselected package x11proto-input-dev. Preparing to unpack .../170-x11proto-input-dev_2.3.2-1_all.deb ... Unpacking x11proto-input-dev (2.3.2-1) ... Selecting previously unselected package x11proto-kb-dev. Preparing to unpack .../171-x11proto-kb-dev_1.0.7-1_all.deb ... Unpacking x11proto-kb-dev (1.0.7-1) ... Selecting previously unselected package xtrans-dev. Preparing to unpack .../172-xtrans-dev_1.3.5-1_all.deb ... Unpacking xtrans-dev (1.3.5-1) ... Selecting previously unselected package libpthread-stubs0-dev:s390x. Preparing to unpack .../173-libpthread-stubs0-dev_0.3-4_s390x.deb ... Unpacking libpthread-stubs0-dev:s390x (0.3-4) ... Selecting previously unselected package libxcb1-dev:s390x. Preparing to unpack .../174-libxcb1-dev_1.12-1ubuntu1_s390x.deb ... Unpacking libxcb1-dev:s390x (1.12-1ubuntu1) ... Selecting previously unselected package libx11-dev:s390x. Preparing to unpack .../175-libx11-dev_2%3a1.6.4-3_s390x.deb ... Unpacking libx11-dev:s390x (2:1.6.4-3) ... Selecting previously unselected package x11proto-render-dev. Preparing to unpack .../176-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:s390x. Preparing to unpack .../177-libxrender-dev_1%3a0.9.10-1_s390x.deb ... Unpacking libxrender-dev:s390x (1:0.9.10-1) ... Selecting previously unselected package x11proto-xext-dev. Preparing to unpack .../178-x11proto-xext-dev_7.3.0-1_all.deb ... Unpacking x11proto-xext-dev (7.3.0-1) ... Selecting previously unselected package libxext-dev:s390x. Preparing to unpack .../179-libxext-dev_2%3a1.3.3-1_s390x.deb ... Unpacking libxext-dev:s390x (2:1.3.3-1) ... Selecting previously unselected package x11-common. Preparing to unpack .../180-x11-common_1%3a7.7+19ubuntu3_all.deb ... Unpacking x11-common (1:7.7+19ubuntu3) ... Selecting previously unselected package libice6:s390x. Preparing to unpack .../181-libice6_2%3a1.0.9-2_s390x.deb ... Unpacking libice6:s390x (2:1.0.9-2) ... Selecting previously unselected package libsm6:s390x. Preparing to unpack .../182-libsm6_2%3a1.2.2-1_s390x.deb ... Unpacking libsm6:s390x (2:1.2.2-1) ... Selecting previously unselected package libice-dev:s390x. Preparing to unpack .../183-libice-dev_2%3a1.0.9-2_s390x.deb ... Unpacking libice-dev:s390x (2:1.0.9-2) ... Selecting previously unselected package libsm-dev:s390x. Preparing to unpack .../184-libsm-dev_2%3a1.2.2-1_s390x.deb ... Unpacking libsm-dev:s390x (2:1.2.2-1) ... Selecting previously unselected package libpixman-1-dev:s390x. Preparing to unpack .../185-libpixman-1-dev_0.34.0-2_s390x.deb ... Unpacking libpixman-1-dev:s390x (0.34.0-2) ... Selecting previously unselected package libxcb-render0-dev:s390x. Preparing to unpack .../186-libxcb-render0-dev_1.12-1ubuntu1_s390x.deb ... Unpacking libxcb-render0-dev:s390x (1.12-1ubuntu1) ... Selecting previously unselected package libxcb-shm0-dev:s390x. Preparing to unpack .../187-libxcb-shm0-dev_1.12-1ubuntu1_s390x.deb ... Unpacking libxcb-shm0-dev:s390x (1.12-1ubuntu1) ... Selecting previously unselected package libcairo2-dev. Preparing to unpack .../188-libcairo2-dev_1.15.8-3_s390x.deb ... Unpacking libcairo2-dev (1.15.8-3) ... Selecting previously unselected package libgconf2-dev. Preparing to unpack .../189-libgconf2-dev_3.2.6-4ubuntu1_s390x.deb ... Unpacking libgconf2-dev (3.2.6-4ubuntu1) ... Selecting previously unselected package libgdk-pixbuf2.0-dev. Preparing to unpack .../190-libgdk-pixbuf2.0-dev_2.36.11-1_s390x.deb ... Unpacking libgdk-pixbuf2.0-dev (2.36.11-1) ... Selecting previously unselected package libgraphite2-dev:s390x. Preparing to unpack .../191-libgraphite2-dev_1.3.10-8_s390x.deb ... Unpacking libgraphite2-dev:s390x (1.3.10-8) ... Selecting previously unselected package libgstreamer1.0-dev. Preparing to unpack .../192-libgstreamer1.0-dev_1.12.4-1_s390x.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.12.4-1) ... Selecting previously unselected package libharfbuzz-icu0:s390x. Preparing to unpack .../193-libharfbuzz-icu0_1.7.2-1_s390x.deb ... Unpacking libharfbuzz-icu0:s390x (1.7.2-1) ... Selecting previously unselected package libharfbuzz-gobject0:s390x. Preparing to unpack .../194-libharfbuzz-gobject0_1.7.2-1_s390x.deb ... Unpacking libharfbuzz-gobject0:s390x (1.7.2-1) ... Selecting previously unselected package libicu-le-hb-dev:s390x. Preparing to unpack .../195-libicu-le-hb-dev_1.0.3+git161113-4_s390x.deb ... Unpacking libicu-le-hb-dev:s390x (1.0.3+git161113-4) ... Selecting previously unselected package libicu-dev. Preparing to unpack .../196-libicu-dev_60.2-1ubuntu1_s390x.deb ... Unpacking libicu-dev (60.2-1ubuntu1) ... Selecting previously unselected package libharfbuzz-dev:s390x. Preparing to unpack .../197-libharfbuzz-dev_1.7.2-1_s390x.deb ... Unpacking libharfbuzz-dev:s390x (1.7.2-1) ... Selecting previously unselected package libxft-dev. Preparing to unpack .../198-libxft-dev_2.3.2-1_s390x.deb ... Unpacking libxft-dev (2.3.2-1) ... Selecting previously unselected package libpango1.0-dev. Preparing to unpack .../199-libpango1.0-dev_1.40.14-1_s390x.deb ... Unpacking libpango1.0-dev (1.40.14-1) ... Selecting previously unselected package x11proto-xinerama-dev. Preparing to unpack .../200-x11proto-xinerama-dev_1.2.1-2_all.deb ... Unpacking x11proto-xinerama-dev (1.2.1-2) ... Selecting previously unselected package libxinerama-dev:s390x. Preparing to unpack .../201-libxinerama-dev_2%3a1.1.3-1_s390x.deb ... Unpacking libxinerama-dev:s390x (2:1.1.3-1) ... Selecting previously unselected package x11proto-fixes-dev. Preparing to unpack .../202-x11proto-fixes-dev_1%3a5.0-2ubuntu2_all.deb ... Unpacking x11proto-fixes-dev (1:5.0-2ubuntu2) ... Selecting previously unselected package libxfixes-dev:s390x. Preparing to unpack .../203-libxfixes-dev_1%3a5.0.3-1_s390x.deb ... Unpacking libxfixes-dev:s390x (1:5.0.3-1) ... Selecting previously unselected package libxi-dev:s390x. Preparing to unpack .../204-libxi-dev_2%3a1.7.9-1_s390x.deb ... Unpacking libxi-dev:s390x (2:1.7.9-1) ... Selecting previously unselected package x11proto-randr-dev. Preparing to unpack .../205-x11proto-randr-dev_1.5.0-1_all.deb ... Unpacking x11proto-randr-dev (1.5.0-1) ... Selecting previously unselected package libxrandr-dev:s390x. Preparing to unpack .../206-libxrandr-dev_2%3a1.5.1-1_s390x.deb ... Unpacking libxrandr-dev:s390x (2:1.5.1-1) ... Selecting previously unselected package libxcursor-dev:s390x. Preparing to unpack .../207-libxcursor-dev_1%3a1.1.15-1_s390x.deb ... Unpacking libxcursor-dev:s390x (1:1.1.15-1) ... Selecting previously unselected package x11proto-composite-dev. Preparing to unpack .../208-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:s390x. Preparing to unpack .../209-libxcomposite-dev_1%3a0.4.4-2_s390x.deb ... Unpacking libxcomposite-dev:s390x (1:0.4.4-2) ... Selecting previously unselected package x11proto-damage-dev. Preparing to unpack .../210-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:s390x. Preparing to unpack .../211-libxdamage-dev_1%3a1.1.4-3_s390x.deb ... Unpacking libxdamage-dev:s390x (1:1.1.4-3) ... Selecting previously unselected package libxml2-utils. Preparing to unpack .../212-libxml2-utils_2.9.4+dfsg1-5.2ubuntu1_s390x.deb ... Unpacking libxml2-utils (2.9.4+dfsg1-5.2ubuntu1) ... Selecting previously unselected package libgtk2.0-dev. Preparing to unpack .../213-libgtk2.0-dev_2.24.31-4ubuntu1_s390x.deb ... Unpacking libgtk2.0-dev (2.24.31-4ubuntu1) ... Selecting previously unselected package libnotify-dev:s390x. Preparing to unpack .../214-libnotify-dev_0.7.7-3_s390x.deb ... Unpacking libnotify-dev:s390x (0.7.7-3) ... Selecting previously unselected package libunique-1.0-0. Preparing to unpack .../215-libunique-1.0-0_1.1.6-6_s390x.deb ... Unpacking libunique-1.0-0 (1.1.6-6) ... Selecting previously unselected package libunique-dev. Preparing to unpack .../216-libunique-dev_1.1.6-6_s390x.deb ... Unpacking libunique-dev (1.1.6-6) ... Selecting previously unselected package libxml2-dev:s390x. Preparing to unpack .../217-libxml2-dev_2.9.4+dfsg1-5.2ubuntu1_s390x.deb ... Unpacking libxml2-dev:s390x (2.9.4+dfsg1-5.2ubuntu1) ... Selecting previously unselected package sbuild-build-depends-alarm-clock-applet-dummy. Preparing to unpack .../218-sbuild-build-depends-alarm-clock-applet-dummy_0.invalid.0_s390x.deb ... Unpacking sbuild-build-depends-alarm-clock-applet-dummy (0.invalid.0) ... Setting up libhtml-tagset-perl (3.20-3) ... Setting up libtry-tiny-perl (0.30-1) ... Setting up libgtk2.0-common (2.24.31-4ubuntu1) ... Setting up libarchive-zip-perl (1.60-1) ... Setting up psmisc (23.1-1) ... Setting up mime-support (3.60ubuntu1) ... Setting up libencode-locale-perl (1.05-1) ... Setting up libtimedate-perl (2.3000-2) ... Setting up libjbig0:s390x (2.1-3.1) ... Setting up libsigsegv2:s390x (2.11-1) ... Setting up libpthread-stubs0-dev:s390x (0.3-4) ... Setting up fonts-dejavu-core (2.37-1) ... Setting up libcap2-bin (1:2.25-1.2) ... Setting up perl-openssl-defaults:s390x (3) ... Setting up libelf1:s390x (0.170-0.1) ... Setting up groff-base (1.22.3-9) ... Setting up libglib2.0-0:s390x (2.54.1-1ubuntu1) ... No schema files found: doing nothing. Setting up xorg-sgml-doctools (1:1.11-1) ... Setting up libio-html-perl (1.001-1) ... Setting up libgdk-pixbuf2.0-common (2.36.11-1) ... Setting up libdatrie1:s390x (0.2.10-5) ... Setting up gettext-base (0.19.8.1-4ubuntu2) ... Setting up libjpeg-turbo8:s390x (1.5.2-0ubuntu5) ... Setting up libpipeline1:s390x (1.5.0-1) ... Setting up x11proto-kb-dev (1.0.7-1) ... Setting up m4 (1.4.18-1) ... Setting up libbsd0:s390x (0.8.6-3) ... Setting up ucf (3.0036) ... Setting up libgirepository-1.0-1:s390x (1.54.1-4) ... Setting up libfreetype6:s390x (2.8-0.2ubuntu2) ... Setting up libmagic-mgc (1:5.32-1) ... Setting up libmagic1:s390x (1:5.32-1) ... Setting up libgraphite2-3:s390x (1.3.10-8) ... Setting up libatk1.0-data (2.26.1-2) ... Setting up pkg-config (0.29.1-0ubuntu2) ... Setting up libpixman-1-0:s390x (0.34.0-2) ... Setting up xtrans-dev (1.3.5-1) ... Setting up gir1.2-glib-2.0:s390x (1.54.1-4) ... Setting up libglib2.0-data (2.54.1-1ubuntu1) ... Setting up libdbusmenu-glib4:s390x (16.04.1+18.04.20171206-0ubuntu1) ... Setting up liblwp-mediatypes-perl (6.02-1) ... Processing triggers for libc-bin (2.26-0ubuntu2) ... Setting up x11proto-xinerama-dev (1.2.1-2) ... Setting up autotools-dev (20171216.1) ... Setting up libpixman-1-dev:s390x (0.34.0-2) ... Setting up liburi-perl (1.72-2) ... Setting up libatk1.0-0:s390x (2.26.1-2) ... Setting up x11proto-randr-dev (1.5.0-1) ... Processing triggers for systemd (235-3ubuntu2) ... Setting up libhtml-parser-perl (3.72-3build1) ... Setting up libexpat1-dev:s390x (2.2.5-3) ... Setting up libpcrecpp0v5:s390x (2:8.39-8) ... Setting up libpcre32-3:s390x (2:8.39-8) ... Setting up libnet-http-perl (6.17-1) ... Setting up libpcre16-3:s390x (2:8.39-8) ... Setting up libthai-data (0.1.27-1) ... Setting up libxdmcp6:s390x (1:1.1.2-3) ... Setting up bsdmainutils (9.0.14ubuntu1) ... 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 x11-common (1:7.7+19ubuntu3) ... update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults Running in chroot, ignoring request. invoke-rc.d: policy-rc.d denied execution of start. Setting up hicolor-icon-theme (0.17-1) ... Setting up libglib2.0-bin (2.54.1-1ubuntu1) ... Setting up libgraphite2-dev:s390x (1.3.10-8) ... Setting up libwww-robotrules-perl (6.01-1) ... Setting up libx11-data (2:1.6.4-3) ... Setting up libxau6:s390x (1:1.0.8-1) ... Setting up autopoint (0.19.8.1-4ubuntu2) ... Setting up libmpdec2:s390x (2.4.2-1) ... Setting up libdbus-1-3:s390x (1.12.2-1ubuntu1) ... Setting up liblzo2-2:s390x (2.08-1.2) ... Setting up libavahi-common-data:s390x (0.6.32-1ubuntu1) ... Setting up netbase (5.4) ... Setting up zlib1g-dev:s390x (1:1.2.11.dfsg-0ubuntu2) ... Setting up libfile-stripnondeterminism-perl (0.040-1) ... Setting up libjpeg8:s390x (8c-2ubuntu8) ... Setting up libpython3.6-stdlib:s390x (3.6.4-1) ... Setting up gconf2-common (3.2.6-4ubuntu1) ... Creating config file /etc/gconf/2/path with new version Setting up libdbus-1-dev:s390x (1.12.2-1ubuntu1) ... Setting up libpcre3-dev:s390x (2:8.39-8) ... Setting up gir1.2-atk-1.0:s390x (2.26.1-2) ... Setting up fontconfig-config (2.12.6-0ubuntu1) ... Setting up libhttp-date-perl (6.02-1) ... Setting up libgstreamer1.0-0:s390x (1.12.4-1) ... Setcap worked! gst-ptp-helper is not suid! Setting up x11proto-core-dev (7.0.31-1) ... Setting up libnet-ssleay-perl (1.80-1build1) ... Setting up libdbus-glib-1-2:s390x (0.108-3) ... Setting up gir1.2-freedesktop:s390x (1.54.1-4) ... Setting up libgconf-2-4:s390x (3.2.6-4ubuntu1) ... Setting up libharfbuzz0b:s390x (1.7.2-1) ... Setting up libtiff5:s390x (4.0.9-2) ... Setting up libxau-dev:s390x (1:1.0.8-1) ... Setting up autoconf (2.69-11) ... Setting up libthai0:s390x (0.1.27-1) ... Setting up file (1:5.32-1) ... Setting up libio-socket-ssl-perl (2.052-1) ... Setting up libhtml-tree-perl (5.07-1) ... Setting up gir1.2-dbusmenu-glib-0.4:s390x (16.04.1+18.04.20171206-0ubuntu1) ... Setting up libxdmcp-dev:s390x (1:1.1.2-3) ... Setting up gir1.2-harfbuzz-0.0:s390x (1.7.2-1) ... Setting up automake (1:1.15.1-3ubuntu1) ... update-alternatives: using /usr/bin/automake-1.15 to provide /usr/bin/automake (automake) in auto mode Setting up libice6:s390x (2:1.0.9-2) ... Setting up libfile-listing-perl (6.04-1) ... Setting up man-db (2.7.6.1-4) ... Not building database; man-db/auto-update is not 'true'. Setting up libhttp-message-perl (6.13-1) ... Setting up libavahi-common3:s390x (0.6.32-1ubuntu1) ... Setting up libpng-dev:s390x (1.6.34-1) ... Setting up x11proto-render-dev (2:0.11.1-2) ... Setting up dbus (1.12.2-1ubuntu1) ... Setting up gir1.2-gstreamer-1.0 (1.12.4-1) ... Setting up libxcb1:s390x (1.12-1ubuntu1) ... Setting up x11proto-input-dev (2.3.2-1) ... Setting up libharfbuzz-gobject0:s390x (1.7.2-1) ... Setting up libhttp-negotiate-perl (6.00-2) ... Setting up libtool (2.4.6-2) ... Setting up libpython3-stdlib:s390x (3.6.3-0ubuntu2) ... Setting up libfontconfig1:s390x (2.12.6-0ubuntu1) ... Setting up libsm6:s390x (2:1.2.2-1) ... Setting up libxcb-render0:s390x (1.12-1ubuntu1) ... Setting up libpam-systemd:s390x (235-3ubuntu2) ... Setting up libhttp-cookies-perl (6.04-1) ... Setting up libx11-6:s390x (2:1.6.4-3) ... Setting up dbus-user-session (1.12.2-1ubuntu1) ... Setting up x11proto-xext-dev (7.3.0-1) ... Setting up libfreetype6-dev:s390x (2.8-0.2ubuntu2) ... Setting up libice-dev:s390x (2:1.0.9-2) ... Setting up libxcomposite1:s390x (1:0.4.4-2) ... Setting up libxcb-shm0:s390x (1.12-1ubuntu1) ... Setting up libxrender1:s390x (1:0.9.10-1) ... Setting up libxcb1-dev:s390x (1.12-1ubuntu1) ... Setting up libavahi-client3:s390x (0.6.32-1ubuntu1) ... Setting up libx11-dev:s390x (2:1.6.4-3) ... Setting up libxft2:s390x (2.3.2-1) ... Setting up fontconfig (2.12.6-0ubuntu1) ... Regenerating fonts cache... done. Setting up libcups2:s390x (2.2.6-3) ... Setting up libfontconfig1-dev:s390x (2.12.6-0ubuntu1) ... Setting up libsm-dev:s390x (2:1.2.2-1) ... Setting up libxdamage1:s390x (1:1.1.4-3) ... Setting up libxext6:s390x (2:1.3.3-1) ... Setting up libxfixes3:s390x (1:5.0.3-1) ... Setting up x11proto-fixes-dev (1:5.0-2ubuntu2) ... Setting up libxcb-shm0-dev:s390x (1.12-1ubuntu1) ... Setting up libxrender-dev:s390x (1:0.9.10-1) ... Setting up libxcb-render0-dev:s390x (1.12-1ubuntu1) ... Setting up x11proto-damage-dev (1:1.2.1-2) ... Setting up libxft-dev (2.3.2-1) ... Setting up libxcursor1:s390x (1:1.1.15-1) ... Setting up libxext-dev:s390x (2:1.3.3-1) ... Setting up libpango-1.0-0:s390x (1.40.14-1) ... Setting up libxfixes-dev:s390x (1:5.0.3-1) ... Setting up x11proto-composite-dev (1:0.4.2-2) ... Setting up libxrandr2:s390x (2:1.5.1-1) ... Setting up libxi6:s390x (2:1.7.9-1) ... Setting up libcairo2:s390x (1.15.8-3) ... Setting up libxinerama1:s390x (2:1.1.3-1) ... Setting up libxcursor-dev:s390x (1:1.1.15-1) ... Setting up libxrandr-dev:s390x (2:1.5.1-1) ... Setting up libxcomposite-dev:s390x (1:0.4.4-2) ... Setting up libcairo-script-interpreter2:s390x (1.15.8-3) ... Setting up libcairo-gobject2:s390x (1.15.8-3) ... Setting up libxdamage-dev:s390x (1:1.1.4-3) ... Setting up libpangoft2-1.0-0:s390x (1.40.14-1) ... Setting up libxinerama-dev:s390x (2:1.1.3-1) ... Setting up libxi-dev:s390x (2:1.7.9-1) ... Setting up libpangoxft-1.0-0:s390x (1.40.14-1) ... Setting up libpangocairo-1.0-0:s390x (1.40.14-1) ... Setting up gir1.2-pango-1.0:s390x (1.40.14-1) ... Setting up dh-autoreconf (15) ... Setting up python3 (3.6.3-0ubuntu2) ... Setting up libglib2.0-dev-bin (2.54.1-1ubuntu1) ... Setting up libicu-le-hb0:s390x (1.0.3+git161113-4) ... Setting up liblwp-protocol-https-perl (6.07-2) ... Setting up libglib2.0-dev:s390x (2.54.1-1ubuntu1) ... Setting up dh-strip-nondeterminism (0.040-1) ... Setting up dh-python (2.20170125) ... Setting up libgstreamer1.0-dev (1.12.4-1) ... Setting up python3-distutils (3.6.4~rc1-6) ... Setting up libwww-perl (6.29-1) ... Setting up libicu60:s390x (60.2-1ubuntu1) ... Setting up python3.6 (3.6.4-1) ... Setting up libharfbuzz-icu0:s390x (1.7.2-1) ... Setting up libicu-le-hb-dev:s390x (1.0.3+git161113-4) ... Setting up libcairo2-dev (1.15.8-3) ... Setting up python3.6-2to3 (3.6.4-1) ... Setting up libatk1.0-dev:s390x (2.26.1-2) ... Setting up libdbus-glib-1-dev (0.108-3) ... Setting up libxml2:s390x (2.9.4+dfsg1-5.2ubuntu1) ... Setting up libcroco3:s390x (0.6.12-2) ... Setting up libxml-parser-perl (2.44-2build3) ... Setting up shared-mime-info (1.9-2) ... Setting up icu-devtools (60.2-1ubuntu1) ... Setting up gconf-service-backend (3.2.6-4ubuntu1) ... Setting up libdbusmenu-glib-dev:s390x (16.04.1+18.04.20171206-0ubuntu1) ... Setting up gettext (0.19.8.1-4ubuntu2) ... Setting up intltool (0.51.0-5) ... Setting up libgdk-pixbuf2.0-0:s390x (2.36.11-1) ... Setting up libxml2-utils (2.9.4+dfsg1-5.2ubuntu1) ... Setting up gir1.2-gdkpixbuf-2.0:s390x (2.36.11-1) ... Setting up libicu-dev (60.2-1ubuntu1) ... Setting up libxml2-dev:s390x (2.9.4+dfsg1-5.2ubuntu1) ... Setting up gconf-service (3.2.6-4ubuntu1) ... Setting up intltool-debian (0.35.0+20060710.4) ... Setting up gtk-update-icon-cache (3.22.26-2ubuntu1) ... Setting up libgdk-pixbuf2.0-dev (2.36.11-1) ... Setting up libdbusmenu-gtk4:s390x (16.04.1+18.04.20171206-0ubuntu1) ... Setting up libharfbuzz-dev:s390x (1.7.2-1) ... Setting up libnotify4:s390x (0.7.7-3) ... Setting up gir1.2-notify-0.7:s390x (0.7.7-3) ... Setting up gconf2 (3.2.6-4ubuntu1) ... Setting up librsvg2-2:s390x (2.40.18-2) ... Setting up po-debconf (1.0.20) ... Setting up libnotify-dev:s390x (0.7.7-3) ... Setting up librsvg2-common:s390x (2.40.18-2) ... Setting up gir1.2-gconf-2.0 (3.2.6-4ubuntu1) ... Setting up libpango1.0-dev (1.40.14-1) ... Setting up adwaita-icon-theme (3.26.1-1ubuntu1) ... update-alternatives: using /usr/share/icons/Adwaita/cursor.theme to provide /usr/share/icons/default/index.theme (x-cursor-theme) in auto mode Setting up debhelper (11ubuntu1) ... Setting up libgconf2-dev (3.2.6-4ubuntu1) ... Setting up libgtk2.0-0:s390x (2.24.31-4ubuntu1) ... Setting up libindicator7 (16.10.0+18.04.20171205.1-0ubuntu1) ... Setting up humanity-icon-theme (0.6.13) ... Setting up gnome-icon-theme (3.12.0-2) ... update-alternatives: using /usr/share/icons/gnome/scalable/places/debian-swirl.svg to provide /usr/share/icons/gnome/scalable/places/start-here.svg (start-here.svg) in auto mode Setting up libunique-1.0-0 (1.1.6-6) ... Setting up libappindicator1 (12.10.1+17.04.20170215-0ubuntu2) ... Setting up gir1.2-gtk-2.0 (2.24.31-4ubuntu1) ... Setting up ubuntu-mono (16.10+18.04.20171115.1-0ubuntu1) ... Setting up libgtk2.0-dev (2.24.31-4ubuntu1) ... Setting up libunique-dev (1.1.6-6) ... Setting up gir1.2-appindicator-0.1 (12.10.1+17.04.20170215-0ubuntu2) ... Setting up libappindicator-dev (12.10.1+17.04.20170215-0ubuntu2) ... Setting up sbuild-build-depends-alarm-clock-applet-dummy (0.invalid.0) ... (Reading database ... 39070 files and directories currently installed.) Purging configuration files for pkg-create-dbgsym (0.73) ... Processing triggers for libgdk-pixbuf2.0-0:s390x (2.36.11-1) ... Processing triggers for libc-bin (2.26-0ubuntu2) ... Processing triggers for systemd (235-3ubuntu2) ... +------------------------------------------------------------------------------+ | Build environment | +------------------------------------------------------------------------------+ Kernel: Linux 4.4.0-104-generic s390x (s390x) Toolchain package versions: binutils_2.29.1-12ubuntu1 dpkg-dev_1.19.0.4ubuntu1 g++-7_7.2.0-18ubuntu2 gcc-7_7.2.0-18ubuntu2 libc6-dev_2.26-0ubuntu2 libstdc++-7-dev_7.2.0-18ubuntu2 libstdc++6_7.2.0-18ubuntu2 linux-libc-dev_4.13.0-17.20 Package versions: adduser_3.116ubuntu1 advancecomp_2.0-1 adwaita-icon-theme_3.26.1-1ubuntu1 apt_1.6~alpha5 apt-transport-https_1.6~alpha5 autoconf_2.69-11 automake_1:1.15.1-3ubuntu1 autopoint_0.19.8.1-4ubuntu2 autotools-dev_20171216.1 base-files_10ubuntu1 base-passwd_3.5.44 bash_4.4-5ubuntu1 binutils_2.29.1-12ubuntu1 binutils-common_2.29.1-12ubuntu1 binutils-s390x-linux-gnu_2.29.1-12ubuntu1 bsdmainutils_9.0.14ubuntu1 bsdutils_1:2.30.2-0.1ubuntu1 build-essential_12.4ubuntu1 bzip2_1.0.6-8.1 ca-certificates_20170717 coreutils_8.26-3ubuntu4 cpp_4:7.2.0-1ubuntu1 cpp-7_7.2.0-18ubuntu2 dash_0.5.8-2.3ubuntu1 dbus_1.12.2-1ubuntu1 dbus-user-session_1.12.2-1ubuntu1 debconf_1.5.65 debhelper_11ubuntu1 debianutils_4.8.3 dh-autoreconf_15 dh-python_2.20170125 dh-strip-nondeterminism_0.040-1 diffutils_1:3.6-1 dmsetup_2:1.02.137-2ubuntu3 dpkg_1.19.0.4ubuntu1 dpkg-dev_1.19.0.4ubuntu1 e2fslibs_1.43.7-1 e2fsprogs_1.43.7-1 fakeroot_1.21-1ubuntu2 fdisk_2.30.2-0.1ubuntu1 file_1:5.32-1 findutils_4.6.0+git+20170828-2 fontconfig_2.12.6-0ubuntu1 fontconfig-config_2.12.6-0ubuntu1 fonts-dejavu-core_2.37-1 g++_4:7.2.0-1ubuntu1 g++-7_7.2.0-18ubuntu2 gcc_4:7.2.0-1ubuntu1 gcc-7_7.2.0-18ubuntu2 gcc-7-base_7.2.0-18ubuntu2 gconf-service_3.2.6-4ubuntu1 gconf-service-backend_3.2.6-4ubuntu1 gconf2_3.2.6-4ubuntu1 gconf2-common_3.2.6-4ubuntu1 gettext_0.19.8.1-4ubuntu2 gettext-base_0.19.8.1-4ubuntu2 gir1.2-appindicator-0.1_12.10.1+17.04.20170215-0ubuntu2 gir1.2-atk-1.0_2.26.1-2 gir1.2-dbusmenu-glib-0.4_16.04.1+18.04.20171206-0ubuntu1 gir1.2-freedesktop_1.54.1-4 gir1.2-gconf-2.0_3.2.6-4ubuntu1 gir1.2-gdkpixbuf-2.0_2.36.11-1 gir1.2-glib-2.0_1.54.1-4 gir1.2-gstreamer-1.0_1.12.4-1 gir1.2-gtk-2.0_2.24.31-4ubuntu1 gir1.2-harfbuzz-0.0_1.7.2-1 gir1.2-notify-0.7_0.7.7-3 gir1.2-pango-1.0_1.40.14-1 gnome-icon-theme_3.12.0-2 gnupg_2.1.15-1ubuntu8 gnupg-agent_2.1.15-1ubuntu8 gpgv_2.1.15-1ubuntu8 grep_3.1-2 groff-base_1.22.3-9 gtk-update-icon-cache_3.22.26-2ubuntu1 gzip_1.6-5ubuntu1 hicolor-icon-theme_0.17-1 hostname_3.18 humanity-icon-theme_0.6.13 icu-devtools_60.2-1ubuntu1 init_1.49ubuntu1 init-system-helpers_1.49ubuntu1 initscripts_2.88dsf-59.3ubuntu2 insserv_1.14.0-5ubuntu3 intltool_0.51.0-5 intltool-debian_0.35.0+20060710.4 libacl1_2.2.52-3build1 libapparmor1_2.11.0-2ubuntu18 libappindicator-dev_12.10.1+17.04.20170215-0ubuntu2 libappindicator1_12.10.1+17.04.20170215-0ubuntu2 libapt-pkg5.0_1.6~alpha5 libarchive-zip-perl_1.60-1 libasn1-8-heimdal_7.5.0+dfsg-1 libassuan0_2.5.1-1 libatk1.0-0_2.26.1-2 libatk1.0-data_2.26.1-2 libatk1.0-dev_2.26.1-2 libatomic1_7.2.0-18ubuntu2 libattr1_1:2.4.47-2build1 libaudit-common_1:2.7.7-1ubuntu2 libaudit1_1:2.7.7-1ubuntu2 libavahi-client3_0.6.32-1ubuntu1 libavahi-common-data_0.6.32-1ubuntu1 libavahi-common3_0.6.32-1ubuntu1 libbinutils_2.29.1-12ubuntu1 libblkid1_2.30.2-0.1ubuntu1 libbsd0_0.8.6-3 libbz2-1.0_1.0.6-8.1 libc-bin_2.26-0ubuntu2 libc-dev-bin_2.26-0ubuntu2 libc6_2.26-0ubuntu2 libc6-dev_2.26-0ubuntu2 libcairo-gobject2_1.15.8-3 libcairo-script-interpreter2_1.15.8-3 libcairo2_1.15.8-3 libcairo2-dev_1.15.8-3 libcap-ng0_0.7.7-3.1 libcap2_1:2.25-1.2 libcap2-bin_1:2.25-1.2 libcc1-0_7.2.0-18ubuntu2 libcomerr2_1.43.7-1 libcroco3_0.6.12-2 libcryptsetup4_2:1.7.3-4ubuntu1 libcups2_2.2.6-3 libcurl3-gnutls_7.57.0-1ubuntu1 libdatrie1_0.2.10-5 libdb5.3_5.3.28-13.1 libdbus-1-3_1.12.2-1ubuntu1 libdbus-1-dev_1.12.2-1ubuntu1 libdbus-glib-1-2_0.108-3 libdbus-glib-1-dev_0.108-3 libdbusmenu-glib-dev_16.04.1+18.04.20171206-0ubuntu1 libdbusmenu-glib4_16.04.1+18.04.20171206-0ubuntu1 libdbusmenu-gtk4_16.04.1+18.04.20171206-0ubuntu1 libdebconfclient0_0.213ubuntu1 libdevmapper1.02.1_2:1.02.137-2ubuntu3 libdpkg-perl_1.19.0.4ubuntu1 libelf1_0.170-0.1 libencode-locale-perl_1.05-1 libexpat1_2.2.5-3 libexpat1-dev_2.2.5-3 libfakeroot_1.21-1ubuntu2 libfdisk1_2.30.2-0.1ubuntu1 libffi6_3.2.1-6 libfile-listing-perl_6.04-1 libfile-stripnondeterminism-perl_0.040-1 libfontconfig1_2.12.6-0ubuntu1 libfontconfig1-dev_2.12.6-0ubuntu1 libfreetype6_2.8-0.2ubuntu2 libfreetype6-dev_2.8-0.2ubuntu2 libgcc-7-dev_7.2.0-18ubuntu2 libgcc1_1:7.2.0-18ubuntu2 libgconf-2-4_3.2.6-4ubuntu1 libgconf2-dev_3.2.6-4ubuntu1 libgcrypt20_1.8.1-4 libgdbm3_1.8.3-14 libgdk-pixbuf2.0-0_2.36.11-1 libgdk-pixbuf2.0-common_2.36.11-1 libgdk-pixbuf2.0-dev_2.36.11-1 libgirepository-1.0-1_1.54.1-4 libglib2.0-0_2.54.1-1ubuntu1 libglib2.0-bin_2.54.1-1ubuntu1 libglib2.0-data_2.54.1-1ubuntu1 libglib2.0-dev_2.54.1-1ubuntu1 libglib2.0-dev-bin_2.54.1-1ubuntu1 libgmp10_2:6.1.2+dfsg-1 libgnutls30_3.5.8-6ubuntu3 libgomp1_7.2.0-18ubuntu2 libgpg-error0_1.27-5 libgraphite2-3_1.3.10-8 libgraphite2-dev_1.3.10-8 libgssapi-krb5-2_1.15.1-2 libgssapi3-heimdal_7.5.0+dfsg-1 libgstreamer1.0-0_1.12.4-1 libgstreamer1.0-dev_1.12.4-1 libgtk2.0-0_2.24.31-4ubuntu1 libgtk2.0-common_2.24.31-4ubuntu1 libgtk2.0-dev_2.24.31-4ubuntu1 libharfbuzz-dev_1.7.2-1 libharfbuzz-gobject0_1.7.2-1 libharfbuzz-icu0_1.7.2-1 libharfbuzz0b_1.7.2-1 libhcrypto4-heimdal_7.5.0+dfsg-1 libheimbase1-heimdal_7.5.0+dfsg-1 libheimntlm0-heimdal_7.5.0+dfsg-1 libhogweed4_3.3-2 libhtml-parser-perl_3.72-3build1 libhtml-tagset-perl_3.20-3 libhtml-tree-perl_5.07-1 libhttp-cookies-perl_6.04-1 libhttp-date-perl_6.02-1 libhttp-message-perl_6.13-1 libhttp-negotiate-perl_6.00-2 libhx509-5-heimdal_7.5.0+dfsg-1 libice-dev_2:1.0.9-2 libice6_2:1.0.9-2 libicu-dev_60.2-1ubuntu1 libicu-le-hb-dev_1.0.3+git161113-4 libicu-le-hb0_1.0.3+git161113-4 libicu60_60.2-1ubuntu1 libidn11_1.33-2.1 libidn2-0_2.0.4-1 libindicator7_16.10.0+18.04.20171205.1-0ubuntu1 libio-html-perl_1.001-1 libio-socket-ssl-perl_2.052-1 libip4tc0_1.6.1-2ubuntu2 libisl15_0.18-1 libitm1_7.2.0-18ubuntu2 libjbig0_2.1-3.1 libjpeg-turbo8_1.5.2-0ubuntu5 libjpeg8_8c-2ubuntu8 libk5crypto3_1.15.1-2 libkeyutils1_1.5.9-9.2ubuntu1 libkmod2_24-1ubuntu2 libkrb5-26-heimdal_7.5.0+dfsg-1 libkrb5-3_1.15.1-2 libkrb5support0_1.15.1-2 libksba8_1.3.5-2 libldap-2.4-2_2.4.45+dfsg-1ubuntu1 libldap-common_2.4.45+dfsg-1ubuntu1 liblockfile-bin_1.14-1.1 liblockfile1_1.14-1.1 liblwp-mediatypes-perl_6.02-1 liblwp-protocol-https-perl_6.07-2 liblz4-1_0.0~r131-2ubuntu2 liblzma5_5.2.2-1.3 liblzo2-2_2.08-1.2 libmagic-mgc_1:5.32-1 libmagic1_1:5.32-1 libmount1_2.30.2-0.1ubuntu1 libmpc3_1.0.3-2 libmpdec2_2.4.2-1 libmpfr4_3.1.6-1 libncurses5_6.0+20160625-1ubuntu1 libncursesw5_6.0+20160625-1ubuntu1 libnet-http-perl_6.17-1 libnet-ssleay-perl_1.80-1build1 libnettle6_3.3-2 libnghttp2-14_1.28.0-1 libnotify-dev_0.7.7-3 libnotify4_0.7.7-3 libnpth0_1.5-3 libp11-kit0_0.23.9-2 libpam-modules_1.1.8-3.2ubuntu3 libpam-modules-bin_1.1.8-3.2ubuntu3 libpam-runtime_1.1.8-3.2ubuntu3 libpam-systemd_235-3ubuntu2 libpam0g_1.1.8-3.2ubuntu3 libpango-1.0-0_1.40.14-1 libpango1.0-dev_1.40.14-1 libpangocairo-1.0-0_1.40.14-1 libpangoft2-1.0-0_1.40.14-1 libpangoxft-1.0-0_1.40.14-1 libpcre16-3_2:8.39-8 libpcre3_2:8.39-8 libpcre3-dev_2:8.39-8 libpcre32-3_2:8.39-8 libpcrecpp0v5_2:8.39-8 libperl5.26_5.26.1-3 libpipeline1_1.5.0-1 libpixman-1-0_0.34.0-2 libpixman-1-dev_0.34.0-2 libpng-dev_1.6.34-1 libpng16-16_1.6.34-1 libprocps6_2:3.3.12-1ubuntu2 libpsl5_0.19.1-4 libpthread-stubs0-dev_0.3-4 libpython3-stdlib_3.6.3-0ubuntu2 libpython3.6-minimal_3.6.4-1 libpython3.6-stdlib_3.6.4-1 libreadline7_7.0-0ubuntu2 libroken18-heimdal_7.5.0+dfsg-1 librsvg2-2_2.40.18-2 librsvg2-common_2.40.18-2 librtmp1_2.4+20151223.gitfa8646d.1-1 libsasl2-2_2.1.27~101-g0780600+dfsg-3ubuntu1 libsasl2-modules-db_2.1.27~101-g0780600+dfsg-3ubuntu1 libseccomp2_2.3.1-2.1ubuntu3 libselinux1_2.7-2 libsemanage-common_2.7-2 libsemanage1_2.7-2 libsepol1_2.7-1 libsigsegv2_2.11-1 libslang2_2.3.1-5ubuntu1 libsm-dev_2:1.2.2-1 libsm6_2:1.2.2-1 libsmartcols1_2.30.2-0.1ubuntu1 libsqlite3-0_3.21.0-1 libss2_1.43.7-1 libssl1.0.0_1.0.2g-1ubuntu14 libstdc++-7-dev_7.2.0-18ubuntu2 libstdc++6_7.2.0-18ubuntu2 libsystemd0_235-3ubuntu2 libtasn1-6_4.12-3 libthai-data_0.1.27-1 libthai0_0.1.27-1 libtiff5_4.0.9-2 libtimedate-perl_2.3000-2 libtinfo5_6.0+20160625-1ubuntu1 libtool_2.4.6-2 libtry-tiny-perl_0.30-1 libudev1_235-3ubuntu2 libunique-1.0-0_1.1.6-6 libunique-dev_1.1.6-6 libunistring0_0.9.3-5.2ubuntu1 liburi-perl_1.72-2 libusb-0.1-4_2:0.1.12-31 libustr-1.0-1_1.0.4-6 libuuid1_2.30.2-0.1ubuntu1 libwind0-heimdal_7.5.0+dfsg-1 libwww-perl_6.29-1 libwww-robotrules-perl_6.01-1 libx11-6_2:1.6.4-3 libx11-data_2:1.6.4-3 libx11-dev_2:1.6.4-3 libxau-dev_1:1.0.8-1 libxau6_1:1.0.8-1 libxcb-render0_1.12-1ubuntu1 libxcb-render0-dev_1.12-1ubuntu1 libxcb-shm0_1.12-1ubuntu1 libxcb-shm0-dev_1.12-1ubuntu1 libxcb1_1.12-1ubuntu1 libxcb1-dev_1.12-1ubuntu1 libxcomposite-dev_1:0.4.4-2 libxcomposite1_1:0.4.4-2 libxcursor-dev_1:1.1.15-1 libxcursor1_1:1.1.15-1 libxdamage-dev_1:1.1.4-3 libxdamage1_1:1.1.4-3 libxdmcp-dev_1:1.1.2-3 libxdmcp6_1:1.1.2-3 libxext-dev_2:1.3.3-1 libxext6_2:1.3.3-1 libxfixes-dev_1:5.0.3-1 libxfixes3_1:5.0.3-1 libxft-dev_2.3.2-1 libxft2_2.3.2-1 libxi-dev_2:1.7.9-1 libxi6_2:1.7.9-1 libxinerama-dev_2:1.1.3-1 libxinerama1_2:1.1.3-1 libxml-parser-perl_2.44-2build3 libxml2_2.9.4+dfsg1-5.2ubuntu1 libxml2-dev_2.9.4+dfsg1-5.2ubuntu1 libxml2-utils_2.9.4+dfsg1-5.2ubuntu1 libxrandr-dev_2:1.5.1-1 libxrandr2_2:1.5.1-1 libxrender-dev_1:0.9.10-1 libxrender1_1:0.9.10-1 linux-libc-dev_4.13.0-17.20 lockfile-progs_0.1.17build1 login_1:4.2-3.2ubuntu4 lsb-base_9.20170808ubuntu1 m4_1.4.18-1 make_4.1-9.1 man-db_2.7.6.1-4 mawk_1.3.3-17ubuntu2 mime-support_3.60ubuntu1 mount_2.30.2-0.1ubuntu1 multiarch-support_2.26-0ubuntu2 ncurses-base_6.0+20160625-1ubuntu1 ncurses-bin_6.0+20160625-1ubuntu1 netbase_5.4 openssl_1.0.2g-1ubuntu14 optipng_0.7.6-1.1 passwd_1:4.2-3.2ubuntu4 patch_2.7.5-1build1 perl_5.26.1-3 perl-base_5.26.1-3 perl-modules-5.26_5.26.1-3 perl-openssl-defaults_3 pinentry-curses_1.0.0-3 pkg-config_0.29.1-0ubuntu2 pkgbinarymangler_131 po-debconf_1.0.20 policyrcd-script-zg2_0.1-3 procps_2:3.3.12-1ubuntu2 psmisc_23.1-1 python3_3.6.3-0ubuntu2 python3-distutils_3.6.4~rc1-6 python3-minimal_3.6.3-0ubuntu2 python3.6_3.6.4-1 python3.6-2to3_3.6.4-1 python3.6-minimal_3.6.4-1 readline-common_7.0-0ubuntu2 sbuild-build-depends-alarm-clock-applet-dummy_0.invalid.0 sbuild-build-depends-core-dummy_0.invalid.0 sed_4.4-1 sensible-utils_0.0.11 shared-mime-info_1.9-2 systemd_235-3ubuntu2 systemd-sysv_235-3ubuntu2 sysv-rc_2.88dsf-59.3ubuntu2 sysvinit-utils_2.88dsf-59.10ubuntu1 tar_1.29b-2 tzdata_2017c-1 ubuntu-keyring_2016.10.27 ubuntu-mono_16.10+18.04.20171115.1-0ubuntu1 ucf_3.0036 util-linux_2.30.2-0.1ubuntu1 x11-common_1:7.7+19ubuntu3 x11proto-composite-dev_1:0.4.2-2 x11proto-core-dev_7.0.31-1 x11proto-damage-dev_1:1.2.1-2 x11proto-fixes-dev_1:5.0-2ubuntu2 x11proto-input-dev_2.3.2-1 x11proto-kb-dev_1.0.7-1 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 xorg-sgml-doctools_1:1.11-1 xtrans-dev_1.3.5-1 xz-utils_5.2.2-1.3 zlib1g_1:1.2.11.dfsg-0ubuntu2 zlib1g-dev_1:1.2.11.dfsg-0ubuntu2 +------------------------------------------------------------------------------+ | Build | +------------------------------------------------------------------------------+ Unpack source ------------- gpgv: Signature made Tue May 19 05:58:59 2015 UTC gpgv: using RSA key gpgv: Can't check signature: No public key 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 ---------------- APT_CONFIG=/var/lib/sbuild/apt.conf DEB_BUILD_OPTIONS=noautodbgsym parallel=4 HOME=/sbuild-nonexistent LANG=C.UTF-8 LC_ALL=C.UTF-8 LOGNAME=buildd PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games SCHROOT_ALIAS_NAME=build-PACKAGEBUILD-13886866 SCHROOT_CHROOT_NAME=build-PACKAGEBUILD-13886866 SCHROOT_COMMAND=env SCHROOT_GID=2501 SCHROOT_GROUP=buildd SCHROOT_SESSION_ID=build-PACKAGEBUILD-13886866 SCHROOT_UID=2001 SCHROOT_USER=buildd SHELL=/bin/sh TERM=unknown USER=buildd V=1 dpkg-buildpackage ----------------- dpkg-buildpackage: info: source package alarm-clock-applet dpkg-buildpackage: info: source version 0.3.4-1 dpkg-buildpackage: info: source distribution unstable dpkg-source --before-build alarm-clock-applet-0.3.4 dpkg-buildpackage: info: host architecture s390x fakeroot debian/rules clean dh clean dh_clean debian/rules build-arch dh build-arch dh_update_autotools_config -a debian/rules override_dh_auto_configure make[1]: Entering directory '/<>' dh_auto_configure -- \ --enable-appindicator ./configure --build=s390x-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/s390x-linux-gnu --libexecdir=\${prefix}/lib/s390x-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.26.1 checking for XML::Parser... ok checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking locale.h usability... yes checking locale.h presence... yes checking for locale.h... yes checking for LC_MESSAGES... yes checking libintl.h usability... yes checking libintl.h presence... yes checking for libintl.h... yes checking for ngettext in libc... yes checking for dgettext in libc... yes checking for bind_textdomain_codeset... yes checking for msgfmt... (cached) /usr/bin/msgfmt checking for dcgettext... yes checking if msgfmt accepts -c... yes checking for gmsgfmt... (cached) /usr/bin/msgfmt checking for xgettext... (cached) /usr/bin/xgettext checking 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 '/<>' dh_auto_build -a make -j1 make[1]: Entering directory '/<>' make all-recursive make[2]: Entering directory '/<>' Making all in src make[3]: Entering directory '/<>/src' Making all in tests make[4]: Entering directory '/<>/src/tests' make[4]: Nothing to be done for 'all'. make[4]: Leaving directory '/<>/src/tests' make[4]: Entering directory '/<>/src' gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -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/s390x-linux-gnu/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/s390x-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/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -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/s390x-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -pthread -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 -I/usr/lib/s390x-linux-gnu/glib-2.0/include -pthread -I/usr/include/gconf/2 -I/usr/include/dbus-1.0 -I/usr/lib/s390x-linux-gnu/dbus-1.0/include -I/usr/include/libxml2 -I/usr/include/unique-1.0 -I/usr/include/gtk-2.0 -I/usr/lib/s390x-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/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -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/s390x-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -pthread -I/usr/include/libappindicator-0.1 -I/usr/include/libdbusmenu-glib-0.4 -I/usr/include/gtk-2.0 -I/usr/lib/s390x-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/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -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/s390x-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 -O2 -fdebug-prefix-map=/<>=. -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.. -Wdate-time -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/s390x-linux-gnu/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/s390x-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/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -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/s390x-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -pthread -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 -I/usr/lib/s390x-linux-gnu/glib-2.0/include -pthread -I/usr/include/gconf/2 -I/usr/include/dbus-1.0 -I/usr/lib/s390x-linux-gnu/dbus-1.0/include -I/usr/include/libxml2 -I/usr/include/unique-1.0 -I/usr/include/gtk-2.0 -I/usr/lib/s390x-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/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -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/s390x-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -pthread -I/usr/include/libappindicator-0.1 -I/usr/include/libdbusmenu-glib-0.4 -I/usr/include/gtk-2.0 -I/usr/lib/s390x-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/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -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/s390x-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 -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o player.o player.c gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -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/s390x-linux-gnu/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/s390x-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/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -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/s390x-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -pthread -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 -I/usr/lib/s390x-linux-gnu/glib-2.0/include -pthread -I/usr/include/gconf/2 -I/usr/include/dbus-1.0 -I/usr/lib/s390x-linux-gnu/dbus-1.0/include -I/usr/include/libxml2 -I/usr/include/unique-1.0 -I/usr/include/gtk-2.0 -I/usr/lib/s390x-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/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -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/s390x-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -pthread -I/usr/include/libappindicator-0.1 -I/usr/include/libdbusmenu-glib-0.4 -I/usr/include/gtk-2.0 -I/usr/lib/s390x-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/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -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/s390x-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 -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o util.o util.c gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -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/s390x-linux-gnu/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/s390x-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/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -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/s390x-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -pthread -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 -I/usr/lib/s390x-linux-gnu/glib-2.0/include -pthread -I/usr/include/gconf/2 -I/usr/include/dbus-1.0 -I/usr/lib/s390x-linux-gnu/dbus-1.0/include -I/usr/include/libxml2 -I/usr/include/unique-1.0 -I/usr/include/gtk-2.0 -I/usr/lib/s390x-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/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -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/s390x-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -pthread -I/usr/include/libappindicator-0.1 -I/usr/include/libdbusmenu-glib-0.4 -I/usr/include/gtk-2.0 -I/usr/lib/s390x-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/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -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/s390x-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 -O2 -fdebug-prefix-map=/<>=. -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.. -Wdate-time -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/s390x-linux-gnu/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/s390x-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/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -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/s390x-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -pthread -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 -I/usr/lib/s390x-linux-gnu/glib-2.0/include -pthread -I/usr/include/gconf/2 -I/usr/include/dbus-1.0 -I/usr/lib/s390x-linux-gnu/dbus-1.0/include -I/usr/include/libxml2 -I/usr/include/unique-1.0 -I/usr/include/gtk-2.0 -I/usr/lib/s390x-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/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -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/s390x-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -pthread -I/usr/include/libappindicator-0.1 -I/usr/include/libdbusmenu-glib-0.4 -I/usr/include/gtk-2.0 -I/usr/lib/s390x-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/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -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/s390x-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 -O2 -fdebug-prefix-map=/<>=. -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.. -Wdate-time -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/s390x-linux-gnu/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/s390x-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/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -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/s390x-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -pthread -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 -I/usr/lib/s390x-linux-gnu/glib-2.0/include -pthread -I/usr/include/gconf/2 -I/usr/include/dbus-1.0 -I/usr/lib/s390x-linux-gnu/dbus-1.0/include -I/usr/include/libxml2 -I/usr/include/unique-1.0 -I/usr/include/gtk-2.0 -I/usr/lib/s390x-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/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -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/s390x-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -pthread -I/usr/include/libappindicator-0.1 -I/usr/include/libdbusmenu-glib-0.4 -I/usr/include/gtk-2.0 -I/usr/lib/s390x-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/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -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/s390x-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 -O2 -fdebug-prefix-map=/<>=. -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.. -Wdate-time -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/s390x-linux-gnu/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/s390x-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/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -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/s390x-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -pthread -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 -I/usr/lib/s390x-linux-gnu/glib-2.0/include -pthread -I/usr/include/gconf/2 -I/usr/include/dbus-1.0 -I/usr/lib/s390x-linux-gnu/dbus-1.0/include -I/usr/include/libxml2 -I/usr/include/unique-1.0 -I/usr/include/gtk-2.0 -I/usr/lib/s390x-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/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -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/s390x-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -pthread -I/usr/include/libappindicator-0.1 -I/usr/include/libdbusmenu-glib-0.4 -I/usr/include/gtk-2.0 -I/usr/lib/s390x-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/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -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/s390x-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 -O2 -fdebug-prefix-map=/<>=. -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.. -Wdate-time -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/s390x-linux-gnu/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/s390x-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/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -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/s390x-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -pthread -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 -I/usr/lib/s390x-linux-gnu/glib-2.0/include -pthread -I/usr/include/gconf/2 -I/usr/include/dbus-1.0 -I/usr/lib/s390x-linux-gnu/dbus-1.0/include -I/usr/include/libxml2 -I/usr/include/unique-1.0 -I/usr/include/gtk-2.0 -I/usr/lib/s390x-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/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -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/s390x-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -pthread -I/usr/include/libappindicator-0.1 -I/usr/include/libdbusmenu-glib-0.4 -I/usr/include/gtk-2.0 -I/usr/lib/s390x-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/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -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/s390x-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 -O2 -fdebug-prefix-map=/<>=. -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.. -Wdate-time -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/s390x-linux-gnu/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/s390x-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/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -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/s390x-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -pthread -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 -I/usr/lib/s390x-linux-gnu/glib-2.0/include -pthread -I/usr/include/gconf/2 -I/usr/include/dbus-1.0 -I/usr/lib/s390x-linux-gnu/dbus-1.0/include -I/usr/include/libxml2 -I/usr/include/unique-1.0 -I/usr/include/gtk-2.0 -I/usr/lib/s390x-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/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -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/s390x-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -pthread -I/usr/include/libappindicator-0.1 -I/usr/include/libdbusmenu-glib-0.4 -I/usr/include/gtk-2.0 -I/usr/lib/s390x-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/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -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/s390x-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 -O2 -fdebug-prefix-map=/<>=. -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.. -Wdate-time -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/s390x-linux-gnu/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/s390x-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/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -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/s390x-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -pthread -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 -I/usr/lib/s390x-linux-gnu/glib-2.0/include -pthread -I/usr/include/gconf/2 -I/usr/include/dbus-1.0 -I/usr/lib/s390x-linux-gnu/dbus-1.0/include -I/usr/include/libxml2 -I/usr/include/unique-1.0 -I/usr/include/gtk-2.0 -I/usr/lib/s390x-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/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -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/s390x-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -pthread -I/usr/include/libappindicator-0.1 -I/usr/include/libdbusmenu-glib-0.4 -I/usr/include/gtk-2.0 -I/usr/lib/s390x-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/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -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/s390x-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 -O2 -fdebug-prefix-map=/<>=. -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.. -Wdate-time -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/s390x-linux-gnu/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/s390x-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/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -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/s390x-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -pthread -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 -I/usr/lib/s390x-linux-gnu/glib-2.0/include -pthread -I/usr/include/gconf/2 -I/usr/include/dbus-1.0 -I/usr/lib/s390x-linux-gnu/dbus-1.0/include -I/usr/include/libxml2 -I/usr/include/unique-1.0 -I/usr/include/gtk-2.0 -I/usr/lib/s390x-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/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -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/s390x-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -pthread -I/usr/include/libappindicator-0.1 -I/usr/include/libdbusmenu-glib-0.4 -I/usr/include/gtk-2.0 -I/usr/lib/s390x-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/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -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/s390x-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 -O2 -fdebug-prefix-map=/<>=. -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/s390x-linux-gnu/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/s390x-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/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -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/s390x-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -pthread -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 -I/usr/lib/s390x-linux-gnu/glib-2.0/include -pthread -I/usr/include/gconf/2 -I/usr/include/dbus-1.0 -I/usr/lib/s390x-linux-gnu/dbus-1.0/include -I/usr/include/libxml2 -I/usr/include/unique-1.0 -I/usr/include/gtk-2.0 -I/usr/lib/s390x-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/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -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/s390x-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -pthread -I/usr/include/libappindicator-0.1 -I/usr/include/libdbusmenu-glib-0.4 -I/usr/include/gtk-2.0 -I/usr/lib/s390x-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/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -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/s390x-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 -O2 -fdebug-prefix-map=/<>=. -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 '/<>/src' make[3]: Leaving directory '/<>/src' Making all in data make[3]: Entering directory '/<>/data' Making all in icons make[4]: Entering directory '/<>/data/icons' make[4]: Nothing to be done for 'all'. make[4]: Leaving directory '/<>/data/icons' make[4]: Entering directory '/<>/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 '/<>/data' make[3]: Leaving directory '/<>/data' Making all in po make[3]: Entering directory '/<>/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 '/<>/po' make[3]: Entering directory '/<>' make[3]: Nothing to be done for 'all-am'. make[3]: Leaving directory '/<>' make[2]: Leaving directory '/<>' make[1]: Leaving directory '/<>' fakeroot debian/rules binary-arch dh binary-arch dh_testroot -a dh_prep -a dh_auto_install -a make -j1 install DESTDIR=/<>/debian/alarm-clock-applet AM_UPDATE_INFO_DIR=no make[1]: Entering directory '/<>' Making install in src make[2]: Entering directory '/<>/src' Making install in tests make[3]: Entering directory '/<>/src/tests' make[4]: Entering directory '/<>/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 '/<>/src/tests' make[3]: Leaving directory '/<>/src/tests' make[3]: Entering directory '/<>/src' make[4]: Entering directory '/<>/src' /bin/mkdir -p '/<>/debian/alarm-clock-applet/usr/bin' /usr/bin/install -c alarm-clock-applet '/<>/debian/alarm-clock-applet/usr/bin' make[4]: Nothing to be done for 'install-data-am'. make[4]: Leaving directory '/<>/src' make[3]: Leaving directory '/<>/src' make[2]: Leaving directory '/<>/src' Making install in data make[2]: Entering directory '/<>/data' Making install in icons make[3]: Entering directory '/<>/data/icons' make[4]: Entering directory '/<>/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 /<>/debian/alarm-clock-applet/usr/share/icons/hicolor/$SIZE/apps/; \ /usr/bin/install -c -m 644 ./$icon /<>/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 '/<>/data/icons' make[3]: Leaving directory '/<>/data/icons' make[3]: Entering directory '/<>/data' make[4]: Entering directory '/<>/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:7870): 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 '/<>/debian/alarm-clock-applet/usr/share/applications' /usr/bin/install -c -m 644 alarm-clock-applet.desktop '/<>/debian/alarm-clock-applet/usr/share/applications' /bin/mkdir -p '/<>/debian/alarm-clock-applet/etc/gconf/schemas' /usr/bin/install -c -m 644 alarm-clock.schemas '/<>/debian/alarm-clock-applet/etc/gconf/schemas' /bin/mkdir -p '/<>/debian/alarm-clock-applet/usr/share/alarm-clock-applet' /usr/bin/install -c -m 644 alarm-clock.ui '/<>/debian/alarm-clock-applet/usr/share/alarm-clock-applet' make[4]: Leaving directory '/<>/data' make[3]: Leaving directory '/<>/data' make[2]: Leaving directory '/<>/data' Making install in po make[2]: Entering directory '/<>/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=/<>/debian/alarm-clock-applet/usr/share/locale/$lang/LC_MESSAGES; \ /bin/bash /<>/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 /<>/debian/alarm-clock-applet/usr/share/locale/ar/LC_MESSAGES/alarm-clock-applet.mo installing ast.gmo as /<>/debian/alarm-clock-applet/usr/share/locale/ast/LC_MESSAGES/alarm-clock-applet.mo installing be.gmo as /<>/debian/alarm-clock-applet/usr/share/locale/be/LC_MESSAGES/alarm-clock-applet.mo installing bg.gmo as /<>/debian/alarm-clock-applet/usr/share/locale/bg/LC_MESSAGES/alarm-clock-applet.mo installing ca.gmo as /<>/debian/alarm-clock-applet/usr/share/locale/ca/LC_MESSAGES/alarm-clock-applet.mo installing cs.gmo as /<>/debian/alarm-clock-applet/usr/share/locale/cs/LC_MESSAGES/alarm-clock-applet.mo installing da.gmo as /<>/debian/alarm-clock-applet/usr/share/locale/da/LC_MESSAGES/alarm-clock-applet.mo installing de.gmo as /<>/debian/alarm-clock-applet/usr/share/locale/de/LC_MESSAGES/alarm-clock-applet.mo installing es.gmo as /<>/debian/alarm-clock-applet/usr/share/locale/es/LC_MESSAGES/alarm-clock-applet.mo installing et.gmo as /<>/debian/alarm-clock-applet/usr/share/locale/et/LC_MESSAGES/alarm-clock-applet.mo installing fi.gmo as /<>/debian/alarm-clock-applet/usr/share/locale/fi/LC_MESSAGES/alarm-clock-applet.mo installing fo.gmo as /<>/debian/alarm-clock-applet/usr/share/locale/fo/LC_MESSAGES/alarm-clock-applet.mo installing fr.gmo as /<>/debian/alarm-clock-applet/usr/share/locale/fr/LC_MESSAGES/alarm-clock-applet.mo installing gl.gmo as /<>/debian/alarm-clock-applet/usr/share/locale/gl/LC_MESSAGES/alarm-clock-applet.mo installing he.gmo as /<>/debian/alarm-clock-applet/usr/share/locale/he/LC_MESSAGES/alarm-clock-applet.mo installing hi.gmo as /<>/debian/alarm-clock-applet/usr/share/locale/hi/LC_MESSAGES/alarm-clock-applet.mo installing hu.gmo as /<>/debian/alarm-clock-applet/usr/share/locale/hu/LC_MESSAGES/alarm-clock-applet.mo installing id.gmo as /<>/debian/alarm-clock-applet/usr/share/locale/id/LC_MESSAGES/alarm-clock-applet.mo installing it.gmo as /<>/debian/alarm-clock-applet/usr/share/locale/it/LC_MESSAGES/alarm-clock-applet.mo installing ja.gmo as /<>/debian/alarm-clock-applet/usr/share/locale/ja/LC_MESSAGES/alarm-clock-applet.mo installing ka.gmo as /<>/debian/alarm-clock-applet/usr/share/locale/ka/LC_MESSAGES/alarm-clock-applet.mo installing la.gmo as /<>/debian/alarm-clock-applet/usr/share/locale/la/LC_MESSAGES/alarm-clock-applet.mo installing ms.gmo as /<>/debian/alarm-clock-applet/usr/share/locale/ms/LC_MESSAGES/alarm-clock-applet.mo installing nb.gmo as /<>/debian/alarm-clock-applet/usr/share/locale/nb/LC_MESSAGES/alarm-clock-applet.mo installing nl.gmo as /<>/debian/alarm-clock-applet/usr/share/locale/nl/LC_MESSAGES/alarm-clock-applet.mo installing nn.gmo as /<>/debian/alarm-clock-applet/usr/share/locale/nn/LC_MESSAGES/alarm-clock-applet.mo installing pl.gmo as /<>/debian/alarm-clock-applet/usr/share/locale/pl/LC_MESSAGES/alarm-clock-applet.mo installing pt_BR.gmo as /<>/debian/alarm-clock-applet/usr/share/locale/pt_BR/LC_MESSAGES/alarm-clock-applet.mo installing pt.gmo as /<>/debian/alarm-clock-applet/usr/share/locale/pt/LC_MESSAGES/alarm-clock-applet.mo installing ru.gmo as /<>/debian/alarm-clock-applet/usr/share/locale/ru/LC_MESSAGES/alarm-clock-applet.mo installing si.gmo as /<>/debian/alarm-clock-applet/usr/share/locale/si/LC_MESSAGES/alarm-clock-applet.mo installing sv.gmo as /<>/debian/alarm-clock-applet/usr/share/locale/sv/LC_MESSAGES/alarm-clock-applet.mo installing tr.gmo as /<>/debian/alarm-clock-applet/usr/share/locale/tr/LC_MESSAGES/alarm-clock-applet.mo installing uk.gmo as /<>/debian/alarm-clock-applet/usr/share/locale/uk/LC_MESSAGES/alarm-clock-applet.mo installing zh_CN.gmo as /<>/debian/alarm-clock-applet/usr/share/locale/zh_CN/LC_MESSAGES/alarm-clock-applet.mo installing zh_TW.gmo as /<>/debian/alarm-clock-applet/usr/share/locale/zh_TW/LC_MESSAGES/alarm-clock-applet.mo make[2]: Leaving directory '/<>/po' make[2]: Entering directory '/<>' make[3]: Entering directory '/<>' make[3]: Nothing to be done for 'install-exec-am'. make[3]: Nothing to be done for 'install-data-am'. make[3]: Leaving directory '/<>' make[2]: Leaving directory '/<>' make[1]: Leaving directory '/<>' debian/rules override_dh_install make[1]: Entering directory '/<>' 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 '/<>' dh_installdocs -a debian/rules override_dh_installchangelogs make[1]: Entering directory '/<>' dh_installchangelogs ChangeLog make[1]: Leaving directory '/<>' dh_installman -a dh_gconf -a dh_icons -a dh_perl -a dh_link -a dh_strip_nondeterminism -a Normalized debian/alarm-clock-applet/usr/share/locale/fi/LC_MESSAGES/alarm-clock-applet.mo Normalized debian/alarm-clock-applet/usr/share/locale/cs/LC_MESSAGES/alarm-clock-applet.mo Normalized debian/alarm-clock-applet/usr/share/locale/ms/LC_MESSAGES/alarm-clock-applet.mo Normalized debian/alarm-clock-applet/usr/share/locale/zh_CN/LC_MESSAGES/alarm-clock-applet.mo Normalized debian/alarm-clock-applet/usr/share/locale/nb/LC_MESSAGES/alarm-clock-applet.mo Normalized debian/alarm-clock-applet/usr/share/locale/nn/LC_MESSAGES/alarm-clock-applet.mo Normalized debian/alarm-clock-applet/usr/share/locale/bg/LC_MESSAGES/alarm-clock-applet.mo Normalized debian/alarm-clock-applet/usr/share/locale/fr/LC_MESSAGES/alarm-clock-applet.mo Normalized debian/alarm-clock-applet/usr/share/locale/be/LC_MESSAGES/alarm-clock-applet.mo Normalized debian/alarm-clock-applet/usr/share/locale/gl/LC_MESSAGES/alarm-clock-applet.mo Normalized debian/alarm-clock-applet/usr/share/locale/hu/LC_MESSAGES/alarm-clock-applet.mo Normalized debian/alarm-clock-applet/usr/share/locale/da/LC_MESSAGES/alarm-clock-applet.mo Normalized debian/alarm-clock-applet/usr/share/locale/nl/LC_MESSAGES/alarm-clock-applet.mo Normalized debian/alarm-clock-applet/usr/share/locale/pl/LC_MESSAGES/alarm-clock-applet.mo Normalized debian/alarm-clock-applet/usr/share/locale/fo/LC_MESSAGES/alarm-clock-applet.mo Normalized debian/alarm-clock-applet/usr/share/locale/sv/LC_MESSAGES/alarm-clock-applet.mo Normalized debian/alarm-clock-applet/usr/share/locale/ru/LC_MESSAGES/alarm-clock-applet.mo Normalized debian/alarm-clock-applet/usr/share/locale/he/LC_MESSAGES/alarm-clock-applet.mo Normalized debian/alarm-clock-applet/usr/share/locale/ca/LC_MESSAGES/alarm-clock-applet.mo Normalized debian/alarm-clock-applet/usr/share/locale/pt_BR/LC_MESSAGES/alarm-clock-applet.mo Normalized debian/alarm-clock-applet/usr/share/locale/hi/LC_MESSAGES/alarm-clock-applet.mo Normalized debian/alarm-clock-applet/usr/share/locale/pt/LC_MESSAGES/alarm-clock-applet.mo Normalized debian/alarm-clock-applet/usr/share/locale/et/LC_MESSAGES/alarm-clock-applet.mo Normalized debian/alarm-clock-applet/usr/share/locale/zh_TW/LC_MESSAGES/alarm-clock-applet.mo Normalized debian/alarm-clock-applet/usr/share/locale/ja/LC_MESSAGES/alarm-clock-applet.mo Normalized debian/alarm-clock-applet/usr/share/locale/ast/LC_MESSAGES/alarm-clock-applet.mo Normalized debian/alarm-clock-applet/usr/share/locale/es/LC_MESSAGES/alarm-clock-applet.mo Normalized debian/alarm-clock-applet/usr/share/locale/tr/LC_MESSAGES/alarm-clock-applet.mo Normalized debian/alarm-clock-applet/usr/share/locale/uk/LC_MESSAGES/alarm-clock-applet.mo Normalized debian/alarm-clock-applet/usr/share/locale/de/LC_MESSAGES/alarm-clock-applet.mo Normalized debian/alarm-clock-applet/usr/share/locale/la/LC_MESSAGES/alarm-clock-applet.mo Normalized debian/alarm-clock-applet/usr/share/locale/id/LC_MESSAGES/alarm-clock-applet.mo Normalized debian/alarm-clock-applet/usr/share/locale/ar/LC_MESSAGES/alarm-clock-applet.mo Normalized debian/alarm-clock-applet/usr/share/locale/si/LC_MESSAGES/alarm-clock-applet.mo Normalized debian/alarm-clock-applet/usr/share/locale/it/LC_MESSAGES/alarm-clock-applet.mo Normalized debian/alarm-clock-applet/usr/share/locale/ka/LC_MESSAGES/alarm-clock-applet.mo dh_compress -a dh_fixperms -a dh_missing -a dh_strip -a dh_makeshlibs -a dh_shlibdeps -a 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 -a dh_gencontrol -a dh_md5sums -a dh_builddeb -a INFO: pkgstriptranslations version 131 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 pkgstripfiles: Running PNG optimization (using 4 cpus) for package alarm-clock-applet ... ooooooooooooooooooooo pkgstripfiles: PNG optimization (21/0) for package alarm-clock-applet took 0 s dpkg-deb: building package 'alarm-clock-applet' in '../alarm-clock-applet_0.3.4-1_s390x.deb'. dpkg-genbuildinfo --build=any dpkg-genchanges --build=any -mLaunchpad Build Daemon >../alarm-clock-applet_0.3.4-1_s390x.changes dpkg-genchanges: info: binary-only arch-specific upload (source code and arch-indep packages not included) dpkg-source --after-build alarm-clock-applet-0.3.4 dpkg-buildpackage: info: binary-only upload (no source included) -------------------------------------------------------------------------------- Build finished at 20171223-1054 Finished -------- I: Built successfully +------------------------------------------------------------------------------+ | Post Build Chroot | +------------------------------------------------------------------------------+ +------------------------------------------------------------------------------+ | Changes | +------------------------------------------------------------------------------+ alarm-clock-applet_0.3.4-1_s390x.changes: ----------------------------------------- Format: 1.8 Date: Tue, 19 May 2015 13:51:08 +0800 Source: alarm-clock-applet Binary: alarm-clock-applet Architecture: s390x Version: 0.3.4-1 Distribution: bionic 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: bcb58df62161eed058b3a4a51139ae8064f0142e 12848 alarm-clock-applet_0.3.4-1_s390x.buildinfo 19ba27f99e7233162a70723e8a6d9f298af2c29e 136792 alarm-clock-applet_0.3.4-1_s390x.deb Checksums-Sha256: 7c9d358c76bdcb7a2aa983e076732f88159e696863f079f67341ae5354f32ce5 12848 alarm-clock-applet_0.3.4-1_s390x.buildinfo 236e8b3e18620142bf75f37bb86d09c2ebafd5dbfc637abd9b2b16f9c3a3d3f4 136792 alarm-clock-applet_0.3.4-1_s390x.deb Files: c134bfe607370bbe993824b496eda559 12848 gnome optional alarm-clock-applet_0.3.4-1_s390x.buildinfo dc5c1d3f44525393803398d6b73f50a4 136792 gnome optional alarm-clock-applet_0.3.4-1_s390x.deb +------------------------------------------------------------------------------+ | Package contents | +------------------------------------------------------------------------------+ alarm-clock-applet_0.3.4-1_s390x.deb ------------------------------------ new debian package, version 2.0. size 136792 bytes: control archive=2492 bytes. 46 bytes, 1 lines conffiles 1024 bytes, 18 lines control 5751 bytes, 66 lines md5sums Package: alarm-clock-applet Version: 0.3.4-1 Architecture: s390x Maintainer: Ubuntu Developers Original-Maintainer: Chow Loong Jin Installed-Size: 715 Depends: gstreamer1.0-plugins-base, gstreamer1.0-plugins-good, gconf-service, libappindicator1 (>= 0.4.90), libc6 (>= 2.7), libgconf-2-4 (>= 3.2.5), libglib2.0-0 (>= 2.37.3), libgstreamer1.0-0 (>= 1.0.0), libgtk2.0-0 (>= 2.24.31), 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-05-19 05:51 ./ drwxr-xr-x root/root 0 2015-05-19 05:51 ./etc/ drwxr-xr-x root/root 0 2015-05-19 05:51 ./etc/xdg/ drwxr-xr-x root/root 0 2015-05-19 05:51 ./etc/xdg/autostart/ -rw-r--r-- root/root 212 2015-05-19 05:51 ./etc/xdg/autostart/alarm-clock-applet.desktop drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/ drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/bin/ -rwxr-xr-x root/root 116920 2015-05-19 05:51 ./usr/bin/alarm-clock-applet drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/ drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/alarm-clock-applet/ -rw-r--r-- root/root 66257 2015-05-19 05:51 ./usr/share/alarm-clock-applet/alarm-clock.ui drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/applications/ -rw-r--r-- root/root 202 2015-05-19 05:51 ./usr/share/applications/alarm-clock-applet.desktop drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/doc/ drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/doc/alarm-clock-applet/ -rw-r--r-- root/root 2524 2015-05-19 05:51 ./usr/share/doc/alarm-clock-applet/changelog.Debian.gz -rw-r--r-- root/root 1390 2015-05-19 05:51 ./usr/share/doc/alarm-clock-applet/copyright drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/gconf/ drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/gconf/schemas/ -rw-r--r-- root/root 73207 2015-05-19 05:51 ./usr/share/gconf/schemas/alarm-clock.schemas drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/icons/ drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/icons/hicolor/ drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/icons/hicolor/16x16/ drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/icons/hicolor/16x16/apps/ -rw-r--r-- root/root 834 2015-05-19 05:51 ./usr/share/icons/hicolor/16x16/apps/alarm-clock-triggered.png -rw-r--r-- root/root 626 2015-05-19 05:51 ./usr/share/icons/hicolor/16x16/apps/alarm-clock.png -rw-r--r-- root/root 428 2015-05-19 05:51 ./usr/share/icons/hicolor/16x16/apps/alarm-timer.png drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/icons/hicolor/22x22/ drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/icons/hicolor/22x22/apps/ -rw-r--r-- root/root 1403 2015-05-19 05:51 ./usr/share/icons/hicolor/22x22/apps/alarm-clock-triggered.png -rw-r--r-- root/root 901 2015-05-19 05:51 ./usr/share/icons/hicolor/22x22/apps/alarm-clock.png -rw-r--r-- root/root 1089 2015-05-19 05:51 ./usr/share/icons/hicolor/22x22/apps/alarm-timer.png drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/icons/hicolor/24x24/ drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/icons/hicolor/24x24/apps/ -rw-r--r-- root/root 1472 2015-05-19 05:51 ./usr/share/icons/hicolor/24x24/apps/alarm-clock-triggered.png -rw-r--r-- root/root 1095 2015-05-19 05:51 ./usr/share/icons/hicolor/24x24/apps/alarm-clock.png -rw-r--r-- root/root 1207 2015-05-19 05:51 ./usr/share/icons/hicolor/24x24/apps/alarm-timer.png drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/icons/hicolor/32x32/ drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/icons/hicolor/32x32/apps/ -rw-r--r-- root/root 2403 2015-05-19 05:51 ./usr/share/icons/hicolor/32x32/apps/alarm-clock-triggered.png -rw-r--r-- root/root 1597 2015-05-19 05:51 ./usr/share/icons/hicolor/32x32/apps/alarm-clock.png -rw-r--r-- root/root 1567 2015-05-19 05:51 ./usr/share/icons/hicolor/32x32/apps/alarm-timer.png drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/icons/hicolor/36x36/ drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/icons/hicolor/36x36/apps/ -rw-r--r-- root/root 2942 2015-05-19 05:51 ./usr/share/icons/hicolor/36x36/apps/alarm-clock-triggered.png -rw-r--r-- root/root 1768 2015-05-19 05:51 ./usr/share/icons/hicolor/36x36/apps/alarm-clock.png -rw-r--r-- root/root 1759 2015-05-19 05:51 ./usr/share/icons/hicolor/36x36/apps/alarm-timer.png drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/icons/hicolor/48x48/ drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/icons/hicolor/48x48/apps/ -rw-r--r-- root/root 4787 2015-05-19 05:51 ./usr/share/icons/hicolor/48x48/apps/alarm-clock-triggered.png -rw-r--r-- root/root 2499 2015-05-19 05:51 ./usr/share/icons/hicolor/48x48/apps/alarm-clock.png -rw-r--r-- root/root 2351 2015-05-19 05:51 ./usr/share/icons/hicolor/48x48/apps/alarm-timer.png drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/icons/hicolor/64x64/ drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/icons/hicolor/64x64/apps/ -rw-r--r-- root/root 7687 2015-05-19 05:51 ./usr/share/icons/hicolor/64x64/apps/alarm-clock-triggered.png -rw-r--r-- root/root 3505 2015-05-19 05:51 ./usr/share/icons/hicolor/64x64/apps/alarm-clock.png -rw-r--r-- root/root 3458 2015-05-19 05:51 ./usr/share/icons/hicolor/64x64/apps/alarm-timer.png drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/icons/hicolor/scalable/ drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/icons/hicolor/scalable/apps/ -rw-r--r-- root/root 10076 2015-05-19 05:51 ./usr/share/icons/hicolor/scalable/apps/alarm-clock.svg -rw-r--r-- root/root 8970 2015-05-19 05:51 ./usr/share/icons/hicolor/scalable/apps/alarm-timer.svg drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/ drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/ar/ drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/ar/LC_MESSAGES/ -rw-r--r-- root/root 7823 2015-05-19 05:51 ./usr/share/locale/ar/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/ast/ drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/ast/LC_MESSAGES/ -rw-r--r-- root/root 7607 2015-05-19 05:51 ./usr/share/locale/ast/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/be/ drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/be/LC_MESSAGES/ -rw-r--r-- root/root 8887 2015-05-19 05:51 ./usr/share/locale/be/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/bg/ drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/bg/LC_MESSAGES/ -rw-r--r-- root/root 9598 2015-05-19 05:51 ./usr/share/locale/bg/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/ca/ drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/ca/LC_MESSAGES/ -rw-r--r-- root/root 7181 2015-05-19 05:51 ./usr/share/locale/ca/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/cs/ drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/cs/LC_MESSAGES/ -rw-r--r-- root/root 1882 2015-05-19 05:51 ./usr/share/locale/cs/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/da/ drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/da/LC_MESSAGES/ -rw-r--r-- root/root 6807 2015-05-19 05:51 ./usr/share/locale/da/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/de/ drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/de/LC_MESSAGES/ -rw-r--r-- root/root 7549 2015-05-19 05:51 ./usr/share/locale/de/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/es/ drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/es/LC_MESSAGES/ -rw-r--r-- root/root 7916 2015-05-19 05:51 ./usr/share/locale/es/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/et/ drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/et/LC_MESSAGES/ -rw-r--r-- root/root 3027 2015-05-19 05:51 ./usr/share/locale/et/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/fi/ drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/fi/LC_MESSAGES/ -rw-r--r-- root/root 5404 2015-05-19 05:51 ./usr/share/locale/fi/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/fo/ drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/fo/LC_MESSAGES/ -rw-r--r-- root/root 5668 2015-05-19 05:51 ./usr/share/locale/fo/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/fr/ drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/fr/LC_MESSAGES/ -rw-r--r-- root/root 7772 2015-05-19 05:51 ./usr/share/locale/fr/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/gl/ drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/gl/LC_MESSAGES/ -rw-r--r-- root/root 7588 2015-05-19 05:51 ./usr/share/locale/gl/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/he/ drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/he/LC_MESSAGES/ -rw-r--r-- root/root 7933 2015-05-19 05:51 ./usr/share/locale/he/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/hi/ drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/hi/LC_MESSAGES/ -rw-r--r-- root/root 5435 2015-05-19 05:51 ./usr/share/locale/hi/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/hu/ drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/hu/LC_MESSAGES/ -rw-r--r-- root/root 7781 2015-05-19 05:51 ./usr/share/locale/hu/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/id/ drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/id/LC_MESSAGES/ -rw-r--r-- root/root 5522 2015-05-19 05:51 ./usr/share/locale/id/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/it/ drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/it/LC_MESSAGES/ -rw-r--r-- root/root 418 2015-05-19 05:51 ./usr/share/locale/it/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/ja/ drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/ja/LC_MESSAGES/ -rw-r--r-- root/root 7348 2015-05-19 05:51 ./usr/share/locale/ja/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/ka/ drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/ka/LC_MESSAGES/ -rw-r--r-- root/root 11075 2015-05-19 05:51 ./usr/share/locale/ka/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/la/ drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/la/LC_MESSAGES/ -rw-r--r-- root/root 1035 2015-05-19 05:51 ./usr/share/locale/la/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/ms/ drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/ms/LC_MESSAGES/ -rw-r--r-- root/root 7366 2015-05-19 05:51 ./usr/share/locale/ms/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/nb/ drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/nb/LC_MESSAGES/ -rw-r--r-- root/root 7229 2015-05-19 05:51 ./usr/share/locale/nb/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/nl/ drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/nl/LC_MESSAGES/ -rw-r--r-- root/root 6441 2015-05-19 05:51 ./usr/share/locale/nl/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/nn/ drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/nn/LC_MESSAGES/ -rw-r--r-- root/root 3172 2015-05-19 05:51 ./usr/share/locale/nn/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/pl/ drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/pl/LC_MESSAGES/ -rw-r--r-- root/root 6838 2015-05-19 05:51 ./usr/share/locale/pl/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/pt/ drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/pt/LC_MESSAGES/ -rw-r--r-- root/root 1494 2015-05-19 05:51 ./usr/share/locale/pt/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/pt_BR/ drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/pt_BR/LC_MESSAGES/ -rw-r--r-- root/root 7897 2015-05-19 05:51 ./usr/share/locale/pt_BR/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/ru/ drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/ru/LC_MESSAGES/ -rw-r--r-- root/root 9421 2015-05-19 05:51 ./usr/share/locale/ru/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/si/ drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/si/LC_MESSAGES/ -rw-r--r-- root/root 11052 2015-05-19 05:51 ./usr/share/locale/si/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/sv/ drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/sv/LC_MESSAGES/ -rw-r--r-- root/root 3945 2015-05-19 05:51 ./usr/share/locale/sv/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/tr/ drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/tr/LC_MESSAGES/ -rw-r--r-- root/root 7627 2015-05-19 05:51 ./usr/share/locale/tr/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/uk/ drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/uk/LC_MESSAGES/ -rw-r--r-- root/root 9124 2015-05-19 05:51 ./usr/share/locale/uk/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/zh_CN/ drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/zh_CN/LC_MESSAGES/ -rw-r--r-- root/root 7120 2015-05-19 05:51 ./usr/share/locale/zh_CN/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/zh_TW/ drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/locale/zh_TW/LC_MESSAGES/ -rw-r--r-- root/root 7131 2015-05-19 05:51 ./usr/share/locale/zh_TW/LC_MESSAGES/alarm-clock-applet.mo drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/man/ drwxr-xr-x root/root 0 2015-05-19 05:51 ./usr/share/man/man1/ -rw-r--r-- root/root 554 2015-05-19 05:51 ./usr/share/man/man1/alarm-clock-applet.1.gz +------------------------------------------------------------------------------+ | Post Build | +------------------------------------------------------------------------------+ +------------------------------------------------------------------------------+ | Cleanup | +------------------------------------------------------------------------------+ Purging /<> Not removing build depends: as requested +------------------------------------------------------------------------------+ | Summary | +------------------------------------------------------------------------------+ Build Architecture: s390x Build-Space: 5372 Build-Time: 10 Distribution: bionic Host Architecture: s390x Install-Time: 25 Job: alarm-clock-applet_0.3.4-1.dsc Machine Architecture: s390x Package: alarm-clock-applet Package-Time: 35 Source-Version: 0.3.4-1 Space: 5372 Status: successful Version: 0.3.4-1 -------------------------------------------------------------------------------- Finished at 20171223-1054 Build needed 00:00:35, 5372k disc space RUN: /usr/share/launchpad-buildd/slavebin/in-target scan-for-processes --backend=chroot --series=bionic --arch=s390x PACKAGEBUILD-13886866 Scanning for processes to kill in build PACKAGEBUILD-13886866 RUN: /usr/share/launchpad-buildd/slavebin/in-target umount-chroot --backend=chroot --series=bionic --arch=s390x PACKAGEBUILD-13886866 Stopping target for build PACKAGEBUILD-13886866 RUN: /usr/share/launchpad-buildd/slavebin/in-target remove-build --backend=chroot --series=bionic --arch=s390x PACKAGEBUILD-13886866 Removing build PACKAGEBUILD-13886866