Wed May 10 10:22:06 UTC 2023 I: starting to build alarm-clock-applet/bookworm/armhf on jenkins on '2023-05-10 10:21' Wed May 10 10:22:06 UTC 2023 I: The jenkins build log is/was available at https://jenkins.debian.net/userContent/reproducible/debian/build_service/armhf_1/653/console.log Wed May 10 10:22:06 UTC 2023 I: Downloading source for bookworm/alarm-clock-applet=0.4.1-3 --2023-05-10 10:22:06-- http://cdn-fastly.deb.debian.org/debian/pool/main/a/alarm-clock-applet/alarm-clock-applet_0.4.1-3.dsc Connecting to 78.137.99.97:3128... connected. Proxy request sent, awaiting response... 200 OK Length: 2308 (2.3K) [text/prs.lines.tag] Saving to: ‘alarm-clock-applet_0.4.1-3.dsc’ 0K .. 100% 176M=0s 2023-05-10 10:22:06 (176 MB/s) - ‘alarm-clock-applet_0.4.1-3.dsc’ saved [2308/2308] Wed May 10 10:22:06 UTC 2023 I: alarm-clock-applet_0.4.1-3.dsc -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 3.0 (quilt) Source: alarm-clock-applet Binary: alarm-clock-applet, alarm-clock-applet-gconf-migration Architecture: any Version: 0.4.1-3 Maintainer: Chow Loong Jin Uploaders: Johannes H. Jensen Homepage: https://alarm-clock-applet.github.io Standards-Version: 4.4.1 Vcs-Browser: https://salsa.debian.org/debian/alarm-clock-applet Vcs-Git: https://salsa.debian.org/debian/alarm-clock-applet.git Build-Depends: debhelper-compat (= 12), cmake (>= 3.10), intltool (>= 0.40), libgtk-3-dev, libgstreamer1.0-dev, libnotify-dev, libayatana-appindicator3-dev, libglib2.0-dev, libgconf2-dev (>= 2.8.0), gnome-icon-theme (>= 2.15.91), libxml2-dev, gnome-common Package-List: alarm-clock-applet deb gnome optional arch=any alarm-clock-applet-gconf-migration deb gnome optional arch=any Checksums-Sha1: 4d46097df9f2ee213c44c8917e8a073227e76302 208601 alarm-clock-applet_0.4.1.orig.tar.gz e0cf93f55adf354081d48b065d073f3df833a34e 7048 alarm-clock-applet_0.4.1-3.debian.tar.xz Checksums-Sha256: 2483804fd6a2a3f6035f9eb4926ab9c74c2a95f68a904dde2df59765a252300b 208601 alarm-clock-applet_0.4.1.orig.tar.gz 12cc1c45859f354b41ba56df0632cd70a0353e9a8359387b17e23607dd83b53a 7048 alarm-clock-applet_0.4.1-3.debian.tar.xz Files: 5be11d3bc84be80c2a15f143a6920af7 208601 alarm-clock-applet_0.4.1.orig.tar.gz b3f50c3e2ff2b939412f632d7e032d78 7048 alarm-clock-applet_0.4.1-3.debian.tar.xz -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEEuDQnfs/9/dZ027Q+9UiW1iHUqEFAmPs1ncACgkQ+9UiW1iH UqFWWQ/+OB9JoiDzhQf4Um3rlAg66vN5t8amj+FdR2CJ+3+IASsN2CHd37YZtzMM vAuCHLJYbQgigdb9GCxjGeZjauBDqSeAAH6u02dZOIlruDz25kOpdxBwl9LVq+MS orpbNKhZuSIamd1i/ClwrRARrtHPYBlQ8eMG0Dgtog/1mFubDpnMHggWtl+GCDCK 1O9vGh3o0eOO0rJQZVN3vE3NscdUtP/qUr/tYOFF1b4sTThVD4ILxocaPo9NdSyr rMzD6HMSGtPls/OL/B0cYVBOC/PVGY7nSYHQZ5VIodt4VC8BuzhFUOsOBv2Fqb7l k+FVAfEBmJPUhPEBzy39Ti+v4iMyOn81r3Wz6RNR0RR5Q29lGJGjPpE/WTW332+M FvjDLeHCgGUXfZeCodRjF18ui/ltcDjXijUsNlcJA/tlx+JIzPLYNlIAeEXBNH+F 20EF1Ri7ThozudPCg4BALWqSERJId7BGYWCbQkdh297OdNLZMjcjXtlIdM+Gz1Pi /lP9u/8PFybgIx3CurKKG9eSir7JwuG9jf13grlEku5KPTC+5sXvZMcX9ktqmfbz agoJCh2Qim+XrSZ0Y2rdzdpVzzw3zUqH9sbFWVyGXox34JjWSQeyBlHrhaGlMPtk PFH18Xjh4HrcsXmE2mI5taH1VIRqLnNMz51B2ZCDh+oOmMsJZrg= =0jY1 -----END PGP SIGNATURE----- Wed May 10 10:22:06 UTC 2023 I: Checking whether the package is not for us Wed May 10 10:22:06 UTC 2023 I: Starting 1st build on remote node cbxi4a-armhf-rb.debian.net. Wed May 10 10:22:06 UTC 2023 I: Preparing to do remote build '1' on cbxi4a-armhf-rb.debian.net. Wed May 10 10:50:26 UTC 2023 I: Deleting $TMPDIR on cbxi4a-armhf-rb.debian.net. I: pbuilder: network access will be disabled during build I: Current time: Tue May 9 22:22:33 -12 2023 I: pbuilder-time-stamp: 1683714153 I: Building the build Environment I: extracting base tarball [/var/cache/pbuilder/bookworm-reproducible-base.tgz] I: copying local configuration W: --override-config is not set; not updating apt.conf Read the manpage for details. I: mounting /proc filesystem I: mounting /sys filesystem I: creating /{dev,run}/shm I: mounting /dev/pts filesystem I: redirecting /dev/ptmx to /dev/pts/ptmx I: policy-rc.d already exists I: Copying source file I: copying [alarm-clock-applet_0.4.1-3.dsc] I: copying [./alarm-clock-applet_0.4.1.orig.tar.gz] I: copying [./alarm-clock-applet_0.4.1-3.debian.tar.xz] I: Extracting source gpgv: Signature made Wed Feb 15 00:56:23 2023 -12 gpgv: using RSA key 12E0D09DFB3FF7F759D36ED0FBD5225B588752A1 gpgv: Can't check signature: No public key dpkg-source: warning: cannot verify inline signature for ./alarm-clock-applet_0.4.1-3.dsc: no acceptable signature found dpkg-source: info: extracting alarm-clock-applet in alarm-clock-applet-0.4.1 dpkg-source: info: unpacking alarm-clock-applet_0.4.1.orig.tar.gz dpkg-source: info: unpacking alarm-clock-applet_0.4.1-3.debian.tar.xz dpkg-source: info: using patch list from debian/patches/series dpkg-source: info: applying Drop-debian-subdirectory-from-cmake.patch dpkg-source: info: applying Move-gconf-schemas-into-usr-share-gconf-schemas.patch dpkg-source: info: applying Fix-assert-fail-when-no-vorbis-players-are-available.patch dpkg-source: info: applying Handle-default-player-not-being-in-app-list.patch I: using fakeroot in build. I: Installing the build-deps I: user script /srv/workspace/pbuilder/322/tmp/hooks/D02_print_environment starting I: set BUILDDIR='/build' BUILDUSERGECOS='first user,first room,first work-phone,first home-phone,first other' BUILDUSERNAME='pbuilder1' BUILD_ARCH='armhf' DEBIAN_FRONTEND='noninteractive' DEB_BUILD_OPTIONS='buildinfo=+all reproducible=+all parallel=3' DISTRIBUTION='bookworm' HOME='/root' HOST_ARCH='armhf' IFS=' ' INVOCATION_ID='cbab796db4554424acab6eaf0b676133' LANG='C' LANGUAGE='en_US:en' LC_ALL='C' MAIL='/var/mail/root' OPTIND='1' PATH='/usr/sbin:/usr/bin:/sbin:/bin:/usr/games' PBCURRENTCOMMANDLINEOPERATION='build' PBUILDER_OPERATION='build' PBUILDER_PKGDATADIR='/usr/share/pbuilder' PBUILDER_PKGLIBDIR='/usr/lib/pbuilder' PBUILDER_SYSCONFDIR='/etc' PPID='322' PS1='# ' PS2='> ' PS4='+ ' PWD='/' SHELL='/bin/bash' SHLVL='2' SUDO_COMMAND='/usr/bin/timeout -k 18.1h 18h /usr/bin/ionice -c 3 /usr/bin/nice /usr/sbin/pbuilder --build --configfile /srv/reproducible-results/rbuild-debian/r-b-build.OYK6mZEC/pbuilderrc_Ys01 --distribution bookworm --hookdir /etc/pbuilder/first-build-hooks --debbuildopts -b --basetgz /var/cache/pbuilder/bookworm-reproducible-base.tgz --buildresult /srv/reproducible-results/rbuild-debian/r-b-build.OYK6mZEC/b1 --logfile b1/build.log alarm-clock-applet_0.4.1-3.dsc' SUDO_GID='113' SUDO_UID='107' SUDO_USER='jenkins' TERM='unknown' TZ='/usr/share/zoneinfo/Etc/GMT+12' USER='root' _='/usr/bin/systemd-run' http_proxy='http://10.0.0.15:3142/' I: uname -a Linux cbxi4a 5.10.0-22-armmp #1 SMP Debian 5.10.178-3 (2023-04-22) armv7l GNU/Linux I: ls -l /bin total 5072 -rwxr-xr-x 1 root root 838488 Apr 23 09:24 bash -rwxr-xr-x 3 root root 67144 Sep 18 2022 bunzip2 -rwxr-xr-x 3 root root 67144 Sep 18 2022 bzcat lrwxrwxrwx 1 root root 6 Sep 18 2022 bzcmp -> bzdiff -rwxr-xr-x 1 root root 2225 Sep 18 2022 bzdiff lrwxrwxrwx 1 root root 6 Sep 18 2022 bzegrep -> bzgrep -rwxr-xr-x 1 root root 4893 Nov 27 2021 bzexe lrwxrwxrwx 1 root root 6 Sep 18 2022 bzfgrep -> bzgrep -rwxr-xr-x 1 root root 3775 Sep 18 2022 bzgrep -rwxr-xr-x 3 root root 67144 Sep 18 2022 bzip2 -rwxr-xr-x 1 root root 67112 Sep 18 2022 bzip2recover lrwxrwxrwx 1 root root 6 Sep 18 2022 bzless -> bzmore -rwxr-xr-x 1 root root 1297 Sep 18 2022 bzmore -rwxr-xr-x 1 root root 67632 Sep 20 2022 cat -rwxr-xr-x 1 root root 67676 Sep 20 2022 chgrp -rwxr-xr-x 1 root root 67644 Sep 20 2022 chmod -rwxr-xr-x 1 root root 67684 Sep 20 2022 chown -rwxr-xr-x 1 root root 133532 Sep 20 2022 cp -rwxr-xr-x 1 root root 132868 Jan 5 01:20 dash -rwxr-xr-x 1 root root 133220 Sep 20 2022 date -rwxr-xr-x 1 root root 67732 Sep 20 2022 dd -rwxr-xr-x 1 root root 68104 Sep 20 2022 df -rwxr-xr-x 1 root root 133632 Sep 20 2022 dir -rwxr-xr-x 1 root root 59128 Mar 22 21:02 dmesg lrwxrwxrwx 1 root root 8 Dec 19 01:33 dnsdomainname -> hostname lrwxrwxrwx 1 root root 8 Dec 19 01:33 domainname -> hostname -rwxr-xr-x 1 root root 67560 Sep 20 2022 echo -rwxr-xr-x 1 root root 41 Jan 24 02:43 egrep -rwxr-xr-x 1 root root 67548 Sep 20 2022 false -rwxr-xr-x 1 root root 41 Jan 24 02:43 fgrep -rwxr-xr-x 1 root root 55748 Mar 22 21:02 findmnt -rwsr-xr-x 1 root root 26208 Mar 22 20:15 fusermount -rwxr-xr-x 1 root root 128608 Jan 24 02:43 grep -rwxr-xr-x 2 root root 2346 Apr 9 2022 gunzip -rwxr-xr-x 1 root root 6447 Apr 9 2022 gzexe -rwxr-xr-x 1 root root 64220 Apr 9 2022 gzip -rwxr-xr-x 1 root root 67032 Dec 19 01:33 hostname -rwxr-xr-x 1 root root 67720 Sep 20 2022 ln -rwxr-xr-x 1 root root 35132 Mar 22 21:51 login -rwxr-xr-x 1 root root 133632 Sep 20 2022 ls -rwxr-xr-x 1 root root 136808 Mar 22 21:02 lsblk -rwxr-xr-x 1 root root 67800 Sep 20 2022 mkdir -rwxr-xr-x 1 root root 67764 Sep 20 2022 mknod -rwxr-xr-x 1 root root 67596 Sep 20 2022 mktemp -rwxr-xr-x 1 root root 38504 Mar 22 21:02 more -rwsr-xr-x 1 root root 38496 Mar 22 21:02 mount -rwxr-xr-x 1 root root 9824 Mar 22 21:02 mountpoint -rwxr-xr-x 1 root root 133532 Sep 20 2022 mv lrwxrwxrwx 1 root root 8 Dec 19 01:33 nisdomainname -> hostname lrwxrwxrwx 1 root root 14 Apr 2 18:25 pidof -> /sbin/killall5 -rwxr-xr-x 1 root root 67608 Sep 20 2022 pwd lrwxrwxrwx 1 root root 4 Apr 23 09:24 rbash -> bash -rwxr-xr-x 1 root root 67600 Sep 20 2022 readlink -rwxr-xr-x 1 root root 67672 Sep 20 2022 rm -rwxr-xr-x 1 root root 67600 Sep 20 2022 rmdir -rwxr-xr-x 1 root root 67400 Nov 2 2022 run-parts -rwxr-xr-x 1 root root 133372 Jan 5 07:55 sed lrwxrwxrwx 1 root root 4 Jan 5 01:20 sh -> dash -rwxr-xr-x 1 root root 67584 Sep 20 2022 sleep -rwxr-xr-x 1 root root 67644 Sep 20 2022 stty -rwsr-xr-x 1 root root 50800 Mar 22 21:02 su -rwxr-xr-x 1 root root 67584 Sep 20 2022 sync -rwxr-xr-x 1 root root 336764 Apr 6 02:25 tar -rwxr-xr-x 1 root root 67144 Nov 2 2022 tempfile -rwxr-xr-x 1 root root 133224 Sep 20 2022 touch -rwxr-xr-x 1 root root 67548 Sep 20 2022 true -rwxr-xr-x 1 root root 9768 Mar 22 20:15 ulockmgr_server -rwsr-xr-x 1 root root 22108 Mar 22 21:02 umount -rwxr-xr-x 1 root root 67572 Sep 20 2022 uname -rwxr-xr-x 2 root root 2346 Apr 9 2022 uncompress -rwxr-xr-x 1 root root 133632 Sep 20 2022 vdir -rwxr-xr-x 1 root root 42608 Mar 22 21:02 wdctl lrwxrwxrwx 1 root root 8 Dec 19 01:33 ypdomainname -> hostname -rwxr-xr-x 1 root root 1984 Apr 9 2022 zcat -rwxr-xr-x 1 root root 1678 Apr 9 2022 zcmp -rwxr-xr-x 1 root root 6460 Apr 9 2022 zdiff -rwxr-xr-x 1 root root 29 Apr 9 2022 zegrep -rwxr-xr-x 1 root root 29 Apr 9 2022 zfgrep -rwxr-xr-x 1 root root 2081 Apr 9 2022 zforce -rwxr-xr-x 1 root root 8103 Apr 9 2022 zgrep -rwxr-xr-x 1 root root 2206 Apr 9 2022 zless -rwxr-xr-x 1 root root 1842 Apr 9 2022 zmore -rwxr-xr-x 1 root root 4577 Apr 9 2022 znew I: user script /srv/workspace/pbuilder/322/tmp/hooks/D02_print_environment finished -> Attempting to satisfy build-dependencies -> Creating pbuilder-satisfydepends-dummy package Package: pbuilder-satisfydepends-dummy Version: 0.invalid.0 Architecture: armhf Maintainer: Debian Pbuilder Team Description: Dummy package to satisfy dependencies with aptitude - created by pbuilder This package was created automatically by pbuilder to satisfy the build-dependencies of the package being currently built. Depends: debhelper-compat (= 12), cmake (>= 3.10), intltool (>= 0.40), libgtk-3-dev, libgstreamer1.0-dev, libnotify-dev, libayatana-appindicator3-dev, libglib2.0-dev, libgconf2-dev (>= 2.8.0), gnome-icon-theme (>= 2.15.91), libxml2-dev, gnome-common dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in '/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'. Selecting previously unselected package pbuilder-satisfydepends-dummy. (Reading database ... 19329 files and directories currently installed.) Preparing to unpack .../pbuilder-satisfydepends-dummy.deb ... Unpacking pbuilder-satisfydepends-dummy (0.invalid.0) ... dpkg: pbuilder-satisfydepends-dummy: dependency problems, but configuring anyway as you requested: pbuilder-satisfydepends-dummy depends on debhelper-compat (= 12); however: Package debhelper-compat is not installed. pbuilder-satisfydepends-dummy depends on cmake (>= 3.10); however: Package cmake is not installed. pbuilder-satisfydepends-dummy depends on intltool (>= 0.40); however: Package intltool is not installed. pbuilder-satisfydepends-dummy depends on libgtk-3-dev; however: Package libgtk-3-dev is not installed. pbuilder-satisfydepends-dummy depends on libgstreamer1.0-dev; however: Package libgstreamer1.0-dev is not installed. pbuilder-satisfydepends-dummy depends on libnotify-dev; however: Package libnotify-dev is not installed. pbuilder-satisfydepends-dummy depends on libayatana-appindicator3-dev; however: Package libayatana-appindicator3-dev is not installed. pbuilder-satisfydepends-dummy depends on libglib2.0-dev; however: Package libglib2.0-dev is not installed. pbuilder-satisfydepends-dummy depends on libgconf2-dev (>= 2.8.0); however: Package libgconf2-dev is not installed. pbuilder-satisfydepends-dummy depends on gnome-icon-theme (>= 2.15.91); however: Package gnome-icon-theme is not installed. pbuilder-satisfydepends-dummy depends on libxml2-dev; however: Package libxml2-dev is not installed. pbuilder-satisfydepends-dummy depends on gnome-common; however: Package gnome-common is not installed. Setting up pbuilder-satisfydepends-dummy (0.invalid.0) ... Reading package lists... Building dependency tree... Reading state information... Initializing package states... Writing extended state information... Building tag database... pbuilder-satisfydepends-dummy is already installed at the requested version (0.invalid.0) pbuilder-satisfydepends-dummy is already installed at the requested version (0.invalid.0) The following NEW packages will be installed: adwaita-icon-theme{a} at-spi2-common{a} autoconf{a} autoconf-archive{a} automake{a} autopoint{a} autotools-dev{a} bsdextrautils{a} ca-certificates{a} cmake{a} cmake-data{a} dbus{a} dbus-bin{a} dbus-daemon{a} dbus-session-bus-common{a} dbus-system-bus-common{a} dbus-user-session{a} dconf-gsettings-backend{a} dconf-service{a} debhelper{a} dh-autoreconf{a} dh-strip-nondeterminism{a} dmsetup{a} dwz{a} file{a} fontconfig{a} fontconfig-config{a} fonts-dejavu-core{a} gconf-service{a} gconf2{a} gconf2-common{a} gettext{a} gettext-base{a} gir1.2-atk-1.0{a} gir1.2-atspi-2.0{a} gir1.2-ayatanaappindicator3-0.1{a} gir1.2-ayatanaido3-0.4{a} gir1.2-dbusmenu-glib-0.4{a} gir1.2-freedesktop{a} gir1.2-gconf-2.0{a} gir1.2-gdkpixbuf-2.0{a} gir1.2-glib-2.0{a} gir1.2-gstreamer-1.0{a} gir1.2-gtk-2.0{a} gir1.2-gtk-3.0{a} gir1.2-harfbuzz-0.0{a} gir1.2-notify-0.7{a} gir1.2-pango-1.0{a} gnome-common{a} gnome-icon-theme{a} groff-base{a} gtk-update-icon-cache{a} hicolor-icon-theme{a} icu-devtools{a} intltool{a} intltool-debian{a} libapparmor1{a} libarchive-zip-perl{a} libarchive13{a} libargon2-1{a} libatk-bridge2.0-0{a} libatk-bridge2.0-dev{a} libatk1.0-0{a} libatk1.0-dev{a} libatspi2.0-0{a} libatspi2.0-dev{a} libavahi-client3{a} libavahi-common-data{a} libavahi-common3{a} libayatana-appindicator3-1{a} libayatana-appindicator3-dev{a} libayatana-ido3-0.4-0{a} libayatana-ido3-dev{a} libayatana-indicator3-7{a} libayatana-indicator3-dev{a} libblkid-dev{a} libbrotli-dev{a} libbrotli1{a} libbsd0{a} libcairo-gobject2{a} libcairo-script-interpreter2{a} libcairo2{a} libcairo2-dev{a} libcap2-bin{a} libclone-perl{a} libcolord2{a} libcryptsetup12{a} libcups2{a} libcurl4{a} libdatrie-dev{a} libdatrie1{a} libdbus-1-3{a} libdbus-1-dev{a} libdbus-glib-1-2{a} libdbusmenu-glib-dev{a} libdbusmenu-glib4{a} libdbusmenu-gtk3-4{a} libdconf1{a} libdebhelper-perl{a} libdeflate-dev{a} libdeflate0{a} libdevmapper1.02.1{a} libdrm-amdgpu1{a} libdrm-common{a} libdrm-nouveau2{a} libdrm-radeon1{a} libdrm2{a} libdw-dev{a} libdw1{a} libedit2{a} libegl-dev{a} libegl-mesa0{a} libegl1{a} libegl1-mesa-dev{a} libelf-dev{a} libelf1{a} libencode-locale-perl{a} libepoxy-dev{a} libepoxy0{a} libexpat1{a} libexpat1-dev{a} libfdisk1{a} libffi-dev{a} libfile-listing-perl{a} libfile-stripnondeterminism-perl{a} libfontconfig-dev{a} libfontconfig1{a} libfreetype-dev{a} libfreetype6{a} libfribidi-dev{a} libfribidi0{a} libgbm1{a} libgconf-2-4{a} libgconf2-dev{a} libgdk-pixbuf-2.0-0{a} libgdk-pixbuf-2.0-dev{a} libgdk-pixbuf2.0-bin{a} libgdk-pixbuf2.0-common{a} libgirepository-1.0-1{a} libgl-dev{a} libgl1{a} libgl1-mesa-dri{a} libglapi-mesa{a} libgles-dev{a} libgles1{a} libgles2{a} libglib2.0-0{a} libglib2.0-bin{a} libglib2.0-data{a} libglib2.0-dev{a} libglib2.0-dev-bin{a} libglvnd-core-dev{a} libglvnd-dev{a} libglvnd0{a} libglx-dev{a} libglx-mesa0{a} libglx0{a} libgraphite2-3{a} libgraphite2-dev{a} libgstreamer1.0-0{a} libgstreamer1.0-dev{a} libgtk-3-0{a} libgtk-3-common{a} libgtk-3-dev{a} libgtk2.0-0{a} libgtk2.0-common{a} libgtk2.0-dev{a} libharfbuzz-dev{a} libharfbuzz-gobject0{a} libharfbuzz-icu0{a} libharfbuzz-subset0{a} libharfbuzz0b{a} libhtml-parser-perl{a} libhtml-tagset-perl{a} libhtml-tree-perl{a} libhttp-cookies-perl{a} libhttp-date-perl{a} libhttp-message-perl{a} libhttp-negotiate-perl{a} libice-dev{a} libice6{a} libicu-dev{a} libicu72{a} libio-html-perl{a} libio-socket-ssl-perl{a} libip4tc2{a} libjbig-dev{a} libjbig0{a} libjpeg-dev{a} libjpeg62-turbo{a} libjpeg62-turbo-dev{a} libjson-c5{a} libjsoncpp25{a} libkmod2{a} liblcms2-2{a} libldap-2.5-0{a} liblerc-dev{a} liblerc4{a} libllvm15{a} liblwp-mediatypes-perl{a} liblwp-protocol-https-perl{a} liblzma-dev{a} liblzo2-2{a} libmagic-mgc{a} libmagic1{a} libmount-dev{a} libnet-http-perl{a} libnet-ssleay-perl{a} libnghttp2-14{a} libnotify-dev{a} libnotify4{a} libopengl-dev{a} libopengl0{a} libpam-systemd{a} libpango-1.0-0{a} libpango1.0-dev{a} libpangocairo-1.0-0{a} libpangoft2-1.0-0{a} libpangoxft-1.0-0{a} libpcre2-16-0{a} libpcre2-32-0{a} libpcre2-dev{a} libpcre2-posix3{a} libpipeline1{a} libpixman-1-0{a} libpixman-1-dev{a} libpkgconf3{a} libpng-dev{a} libpng16-16{a} libproc2-0{a} libpsl5{a} libpthread-stubs0-dev{a} libpython3-stdlib{a} libpython3.11-minimal{a} libpython3.11-stdlib{a} libreadline8{a} libregexp-ipv6-perl{a} librhash0{a} librsvg2-2{a} librsvg2-common{a} librtmp1{a} libsasl2-2{a} libsasl2-modules-db{a} libselinux1-dev{a} libsensors-config{a} libsensors5{a} libsepol-dev{a} libsm-dev{a} libsm6{a} libssh2-1{a} libsub-override-perl{a} libsystemd-shared{a} libthai-data{a} libthai-dev{a} libthai0{a} libtiff-dev{a} libtiff6{a} libtiffxx6{a} libtimedate-perl{a} libtool{a} libtry-tiny-perl{a} libuchardet0{a} libunwind-dev{a} libunwind8{a} liburi-perl{a} libuv1{a} libwayland-bin{a} libwayland-client0{a} libwayland-cursor0{a} libwayland-dev{a} libwayland-egl1{a} libwayland-server0{a} libwebp-dev{a} libwebp7{a} libwebpdemux2{a} libwebpmux3{a} libwww-perl{a} libwww-robotrules-perl{a} libx11-6{a} libx11-data{a} libx11-dev{a} libx11-xcb1{a} libxau-dev{a} libxau6{a} libxcb-dri2-0{a} libxcb-dri3-0{a} libxcb-glx0{a} libxcb-present0{a} libxcb-randr0{a} libxcb-render0{a} libxcb-render0-dev{a} libxcb-shm0{a} libxcb-shm0-dev{a} libxcb-sync1{a} libxcb-xfixes0{a} libxcb1{a} libxcb1-dev{a} libxcomposite-dev{a} libxcomposite1{a} libxcursor-dev{a} libxcursor1{a} libxdamage-dev{a} libxdamage1{a} libxdmcp-dev{a} libxdmcp6{a} libxext-dev{a} libxext6{a} libxfixes-dev{a} libxfixes3{a} libxft-dev{a} libxft2{a} libxi-dev{a} libxi6{a} libxinerama-dev{a} libxinerama1{a} libxkbcommon-dev{a} libxkbcommon0{a} libxml-parser-perl{a} libxml2{a} libxml2-dev{a} libxml2-utils{a} libxrandr-dev{a} libxrandr2{a} libxrender-dev{a} libxrender1{a} libxshmfence1{a} libxtst-dev{a} libxtst6{a} libxxf86vm1{a} libz3-4{a} libzstd-dev{a} m4{a} man-db{a} media-types{a} netbase{a} openssl{a} pango1.0-tools{a} perl-openssl-defaults{a} pkg-config{a} pkgconf{a} pkgconf-bin{a} po-debconf{a} procps{a} psmisc{a} python3{a} python3-distutils{a} python3-lib2to3{a} python3-minimal{a} python3.11{a} python3.11-minimal{a} readline-common{a} sensible-utils{a} sgml-base{a} shared-mime-info{a} systemd{a} systemd-sysv{a} ucf{a} uuid-dev{a} wayland-protocols{a} x11-common{a} x11proto-dev{a} xkb-data{a} xml-core{a} xorg-sgml-doctools{a} xtrans-dev{a} zlib1g-dev{a} The following packages are RECOMMENDED but will NOT be installed: at-spi2-core chrony curl libarchive-cpio-perl libdata-dump-perl libgail-common libgconf2-doc libgtk-3-bin libgtk2.0-bin libhtml-form-perl libhtml-format-perl libhttp-daemon-perl libldap-common libltdl-dev libmail-sendmail-perl libmailtools-perl libnss-systemd libpam-cap libpng-tools libsasl2-modules lynx ntpsec openntpd publicsuffix systemd-timesyncd wget xdg-user-dirs 0 packages upgraded, 366 newly installed, 0 to remove and 0 not upgraded. Need to get 163 MB of archives. After unpacking 613 MB will be used. Writing extended state information... Get: 1 http://deb.debian.org/debian bookworm/main armhf libargon2-1 armhf 0~20171227-0.3+deb12u1 [19.6 kB] Get: 2 http://deb.debian.org/debian bookworm/main armhf dmsetup armhf 2:1.02.185-2 [81.9 kB] Get: 3 http://deb.debian.org/debian bookworm/main armhf libdevmapper1.02.1 armhf 2:1.02.185-2 [125 kB] Get: 4 http://deb.debian.org/debian bookworm/main armhf libjson-c5 armhf 0.16-2 [40.4 kB] Get: 5 http://deb.debian.org/debian bookworm/main armhf libcryptsetup12 armhf 2:2.6.1-4~deb12u1 [196 kB] Get: 6 http://deb.debian.org/debian bookworm/main armhf libfdisk1 armhf 2.38.1-5+b1 [178 kB] Get: 7 http://deb.debian.org/debian bookworm/main armhf libkmod2 armhf 30+20221128-1 [50.0 kB] Get: 8 http://deb.debian.org/debian bookworm/main armhf libapparmor1 armhf 3.0.8-3 [36.9 kB] Get: 9 http://deb.debian.org/debian bookworm/main armhf libip4tc2 armhf 1.8.9-2 [16.9 kB] Get: 10 http://deb.debian.org/debian bookworm/main armhf libsystemd-shared armhf 252.6-1 [1540 kB] Get: 11 http://deb.debian.org/debian bookworm/main armhf systemd armhf 252.6-1 [2923 kB] Get: 12 http://deb.debian.org/debian bookworm/main armhf systemd-sysv armhf 252.6-1 [41.5 kB] Get: 13 http://deb.debian.org/debian bookworm/main armhf libdbus-1-3 armhf 1.14.6-1 [177 kB] Get: 14 http://deb.debian.org/debian bookworm/main armhf dbus-bin armhf 1.14.6-1 [102 kB] Get: 15 http://deb.debian.org/debian bookworm/main armhf dbus-session-bus-common all 1.14.6-1 [76.6 kB] Get: 16 http://deb.debian.org/debian bookworm/main armhf libexpat1 armhf 2.5.0-1 [79.9 kB] Get: 17 http://deb.debian.org/debian bookworm/main armhf dbus-daemon armhf 1.14.6-1 [168 kB] Get: 18 http://deb.debian.org/debian bookworm/main armhf dbus-system-bus-common all 1.14.6-1 [77.7 kB] Get: 19 http://deb.debian.org/debian bookworm/main armhf dbus armhf 1.14.6-1 [93.1 kB] Get: 20 http://deb.debian.org/debian bookworm/main armhf autoconf-archive all 20220903-3 [775 kB] Get: 21 http://deb.debian.org/debian bookworm/main armhf libpython3.11-minimal armhf 3.11.2-6 [798 kB] Get: 22 http://deb.debian.org/debian bookworm/main armhf python3.11-minimal armhf 3.11.2-6 [1714 kB] Get: 23 http://deb.debian.org/debian bookworm/main armhf python3-minimal armhf 3.11.2-1+b1 [26.3 kB] Get: 24 http://deb.debian.org/debian bookworm/main armhf media-types all 10.0.0 [26.1 kB] Get: 25 http://deb.debian.org/debian bookworm/main armhf readline-common all 8.2-1.3 [69.0 kB] Get: 26 http://deb.debian.org/debian bookworm/main armhf libreadline8 armhf 8.2-1.3 [144 kB] Get: 27 http://deb.debian.org/debian bookworm/main armhf libpython3.11-stdlib armhf 3.11.2-6 [1678 kB] Get: 28 http://deb.debian.org/debian bookworm/main armhf python3.11 armhf 3.11.2-6 [572 kB] Get: 29 http://deb.debian.org/debian bookworm/main armhf libpython3-stdlib armhf 3.11.2-1+b1 [9296 B] Get: 30 http://deb.debian.org/debian bookworm/main armhf python3 armhf 3.11.2-1+b1 [26.3 kB] Get: 31 http://deb.debian.org/debian bookworm/main armhf sgml-base all 1.31 [15.4 kB] Get: 32 http://deb.debian.org/debian bookworm/main armhf netbase all 6.4 [12.8 kB] Get: 33 http://deb.debian.org/debian bookworm/main armhf libproc2-0 armhf 2:4.0.2-3 [54.2 kB] Get: 34 http://deb.debian.org/debian bookworm/main armhf procps armhf 2:4.0.2-3 [695 kB] Get: 35 http://deb.debian.org/debian bookworm/main armhf sensible-utils all 0.0.17+nmu1 [19.0 kB] Get: 36 http://deb.debian.org/debian bookworm/main armhf openssl armhf 3.0.8-1 [1373 kB] Get: 37 http://deb.debian.org/debian bookworm/main armhf ca-certificates all 20230311 [153 kB] Get: 38 http://deb.debian.org/debian bookworm/main armhf libmagic-mgc armhf 1:5.44-3 [305 kB] Get: 39 http://deb.debian.org/debian bookworm/main armhf libmagic1 armhf 1:5.44-3 [96.5 kB] Get: 40 http://deb.debian.org/debian bookworm/main armhf file armhf 1:5.44-3 [41.6 kB] Get: 41 http://deb.debian.org/debian bookworm/main armhf gettext-base armhf 0.21-12 [157 kB] Get: 42 http://deb.debian.org/debian bookworm/main armhf libuchardet0 armhf 0.0.7-1 [65.0 kB] Get: 43 http://deb.debian.org/debian bookworm/main armhf groff-base armhf 1.22.4-10 [825 kB] Get: 44 http://deb.debian.org/debian bookworm/main armhf libpam-systemd armhf 252.6-1 [200 kB] Get: 45 http://deb.debian.org/debian bookworm/main armhf bsdextrautils armhf 2.38.1-5+b1 [78.6 kB] Get: 46 http://deb.debian.org/debian bookworm/main armhf libpipeline1 armhf 1.5.7-1 [33.6 kB] Get: 47 http://deb.debian.org/debian bookworm/main armhf man-db armhf 2.11.2-2 [1351 kB] Get: 48 http://deb.debian.org/debian bookworm/main armhf ucf all 3.0043+nmu1 [55.2 kB] Get: 49 http://deb.debian.org/debian bookworm/main armhf hicolor-icon-theme all 0.17-2 [11.4 kB] Get: 50 http://deb.debian.org/debian bookworm/main armhf libgdk-pixbuf2.0-common all 2.42.10+dfsg-1 [306 kB] Get: 51 http://deb.debian.org/debian bookworm/main armhf libglib2.0-0 armhf 2.74.6-2 [1227 kB] Get: 52 http://deb.debian.org/debian bookworm/main armhf libicu72 armhf 72.1-3 [9048 kB] Get: 53 http://deb.debian.org/debian bookworm/main armhf libxml2 armhf 2.9.14+dfsg-1.2 [591 kB] Get: 54 http://deb.debian.org/debian bookworm/main armhf shared-mime-info armhf 2.2-1 [726 kB] Get: 55 http://deb.debian.org/debian bookworm/main armhf libjpeg62-turbo armhf 1:2.1.5-2 [143 kB] Get: 56 http://deb.debian.org/debian bookworm/main armhf libpng16-16 armhf 1.6.39-2 [260 kB] Get: 57 http://deb.debian.org/debian bookworm/main armhf libdeflate0 armhf 1.14-1 [52.2 kB] Get: 58 http://deb.debian.org/debian bookworm/main armhf libjbig0 armhf 2.1-6.1 [27.1 kB] Get: 59 http://deb.debian.org/debian bookworm/main armhf liblerc4 armhf 4.0.0+ds-2 [137 kB] Get: 60 http://deb.debian.org/debian bookworm/main armhf libwebp7 armhf 1.2.4-0.1 [242 kB] Get: 61 http://deb.debian.org/debian bookworm/main armhf libtiff6 armhf 4.5.0-5 [295 kB] Get: 62 http://deb.debian.org/debian bookworm/main armhf libgdk-pixbuf-2.0-0 armhf 2.42.10+dfsg-1+b1 [124 kB] Get: 63 http://deb.debian.org/debian bookworm/main armhf gtk-update-icon-cache armhf 3.24.37-2 [42.3 kB] Get: 64 http://deb.debian.org/debian bookworm/main armhf adwaita-icon-theme all 43-1 [5124 kB] Get: 65 http://deb.debian.org/debian bookworm/main armhf at-spi2-common all 2.46.0-5 [162 kB] Get: 66 http://deb.debian.org/debian bookworm/main armhf m4 armhf 1.4.19-3 [265 kB] Get: 67 http://deb.debian.org/debian bookworm/main armhf autoconf all 2.71-3 [332 kB] Get: 68 http://deb.debian.org/debian bookworm/main armhf autotools-dev all 20220109.1 [51.6 kB] Get: 69 http://deb.debian.org/debian bookworm/main armhf automake all 1:1.16.5-1.3 [823 kB] Get: 70 http://deb.debian.org/debian bookworm/main armhf autopoint all 0.21-12 [495 kB] Get: 71 http://deb.debian.org/debian bookworm/main armhf libarchive13 armhf 3.6.2-1 [299 kB] Get: 72 http://deb.debian.org/debian bookworm/main armhf libbrotli1 armhf 1.0.9-2+b6 [271 kB] Get: 73 http://deb.debian.org/debian bookworm/main armhf libsasl2-modules-db armhf 2.1.28+dfsg-10 [19.0 kB] Get: 74 http://deb.debian.org/debian bookworm/main armhf libsasl2-2 armhf 2.1.28+dfsg-10 [52.3 kB] Get: 75 http://deb.debian.org/debian bookworm/main armhf libldap-2.5-0 armhf 2.5.13+dfsg-5 [158 kB] Get: 76 http://deb.debian.org/debian bookworm/main armhf libnghttp2-14 armhf 1.52.0-1 [60.8 kB] Get: 77 http://deb.debian.org/debian bookworm/main armhf libpsl5 armhf 0.21.2-1 [57.5 kB] Get: 78 http://deb.debian.org/debian bookworm/main armhf librtmp1 armhf 2.4+20151223.gitfa8646d.1-2+b2 [55.2 kB] Get: 79 http://deb.debian.org/debian bookworm/main armhf libssh2-1 armhf 1.10.0-3+b1 [163 kB] Get: 80 http://deb.debian.org/debian bookworm/main armhf libcurl4 armhf 7.88.1-9 [347 kB] Get: 81 http://deb.debian.org/debian bookworm/main armhf libjsoncpp25 armhf 1.9.5-4 [68.6 kB] Get: 82 http://deb.debian.org/debian bookworm/main armhf librhash0 armhf 1.4.3-3 [146 kB] Get: 83 http://deb.debian.org/debian bookworm/main armhf libuv1 armhf 1.44.2-1 [126 kB] Get: 84 http://deb.debian.org/debian bookworm/main armhf cmake-data all 3.25.1-1 [2026 kB] Get: 85 http://deb.debian.org/debian bookworm/main armhf cmake armhf 3.25.1-1 [4263 kB] Get: 86 http://deb.debian.org/debian bookworm/main armhf dbus-user-session armhf 1.14.6-1 [76.5 kB] Get: 87 http://deb.debian.org/debian bookworm/main armhf libdconf1 armhf 0.40.0-4 [36.1 kB] Get: 88 http://deb.debian.org/debian bookworm/main armhf dconf-service armhf 0.40.0-4 [27.6 kB] Get: 89 http://deb.debian.org/debian bookworm/main armhf dconf-gsettings-backend armhf 0.40.0-4 [23.2 kB] Get: 90 http://deb.debian.org/debian bookworm/main armhf libdebhelper-perl all 13.11.4 [81.2 kB] Get: 91 http://deb.debian.org/debian bookworm/main armhf libtool all 2.4.7-5 [517 kB] Get: 92 http://deb.debian.org/debian bookworm/main armhf dh-autoreconf all 20 [17.1 kB] Get: 93 http://deb.debian.org/debian bookworm/main armhf libarchive-zip-perl all 1.68-1 [104 kB] Get: 94 http://deb.debian.org/debian bookworm/main armhf libsub-override-perl all 0.09-4 [9304 B] Get: 95 http://deb.debian.org/debian bookworm/main armhf libfile-stripnondeterminism-perl all 1.13.1-1 [19.4 kB] Get: 96 http://deb.debian.org/debian bookworm/main armhf dh-strip-nondeterminism all 1.13.1-1 [8620 B] Get: 97 http://deb.debian.org/debian bookworm/main armhf libelf1 armhf 0.188-2.1 [170 kB] Get: 98 http://deb.debian.org/debian bookworm/main armhf dwz armhf 0.15-1 [101 kB] Get: 99 http://deb.debian.org/debian bookworm/main armhf gettext armhf 0.21-12 [1229 kB] Get: 100 http://deb.debian.org/debian bookworm/main armhf intltool-debian all 0.35.0+20060710.6 [22.9 kB] Get: 101 http://deb.debian.org/debian bookworm/main armhf po-debconf all 1.0.21+nmu1 [248 kB] Get: 102 http://deb.debian.org/debian bookworm/main armhf debhelper all 13.11.4 [942 kB] Get: 103 http://deb.debian.org/debian bookworm/main armhf libfreetype6 armhf 2.12.1+dfsg-5 [332 kB] Get: 104 http://deb.debian.org/debian bookworm/main armhf fonts-dejavu-core all 2.37-6 [1068 kB] Get: 105 http://deb.debian.org/debian bookworm/main armhf fontconfig-config armhf 2.14.1-4 [315 kB] Get: 106 http://deb.debian.org/debian bookworm/main armhf libfontconfig1 armhf 2.14.1-4 [368 kB] Get: 107 http://deb.debian.org/debian bookworm/main armhf fontconfig armhf 2.14.1-4 [448 kB] Get: 108 http://deb.debian.org/debian bookworm/main armhf libdbus-glib-1-2 armhf 0.112-3 [49.2 kB] Get: 109 http://deb.debian.org/debian bookworm/main armhf gconf2-common all 3.2.6-8 [1025 kB] Get: 110 http://deb.debian.org/debian bookworm/main armhf libgconf-2-4 armhf 3.2.6-8 [403 kB] Get: 111 http://deb.debian.org/debian bookworm/main armhf gconf-service armhf 3.2.6-8 [393 kB] Get: 112 http://deb.debian.org/debian bookworm/main armhf psmisc armhf 23.6-1 [255 kB] Get: 113 http://deb.debian.org/debian bookworm/main armhf gconf2 armhf 3.2.6-8 [409 kB] Get: 114 http://deb.debian.org/debian bookworm/main armhf libgirepository-1.0-1 armhf 1.74.0-3 [88.2 kB] Get: 115 http://deb.debian.org/debian bookworm/main armhf gir1.2-glib-2.0 armhf 1.74.0-3 [159 kB] Get: 116 http://deb.debian.org/debian bookworm/main armhf libatk1.0-0 armhf 2.46.0-5 [42.4 kB] Get: 117 http://deb.debian.org/debian bookworm/main armhf gir1.2-atk-1.0 armhf 2.46.0-5 [23.6 kB] Get: 118 http://deb.debian.org/debian bookworm/main armhf gir1.2-freedesktop armhf 1.74.0-3 [37.2 kB] Get: 119 http://deb.debian.org/debian bookworm/main armhf libxau6 armhf 1:1.0.9-1 [19.0 kB] Get: 120 http://deb.debian.org/debian bookworm/main armhf libbsd0 armhf 0.11.7-2 [113 kB] Get: 121 http://deb.debian.org/debian bookworm/main armhf libxdmcp6 armhf 1:1.1.2-3 [24.9 kB] Get: 122 http://deb.debian.org/debian bookworm/main armhf libxcb1 armhf 1.15-1 [140 kB] Get: 123 http://deb.debian.org/debian bookworm/main armhf libx11-data all 2:1.8.4-2 [292 kB] Get: 124 http://deb.debian.org/debian bookworm/main armhf libx11-6 armhf 2:1.8.4-2 [695 kB] Get: 125 http://deb.debian.org/debian bookworm/main armhf libxext6 armhf 2:1.3.4-1+b1 [47.8 kB] Get: 126 http://deb.debian.org/debian bookworm/main armhf libxi6 armhf 2:1.8-1+b1 [78.6 kB] Get: 127 http://deb.debian.org/debian bookworm/main armhf libatspi2.0-0 armhf 2.46.0-5 [65.0 kB] Get: 128 http://deb.debian.org/debian bookworm/main armhf gir1.2-atspi-2.0 armhf 2.46.0-5 [20.6 kB] Get: 129 http://deb.debian.org/debian bookworm/main armhf gir1.2-gdkpixbuf-2.0 armhf 2.42.10+dfsg-1+b1 [13.5 kB] Get: 130 http://deb.debian.org/debian bookworm/main armhf gir1.2-harfbuzz-0.0 armhf 6.0.0+dfsg-3 [1579 kB] Get: 131 http://deb.debian.org/debian bookworm/main armhf libfribidi0 armhf 1.0.8-2.1 [63.1 kB] Get: 132 http://deb.debian.org/debian bookworm/main armhf libgraphite2-3 armhf 1.3.14-1 [70.5 kB] Get: 133 http://deb.debian.org/debian bookworm/main armhf libharfbuzz0b armhf 6.0.0+dfsg-3 [1893 kB] Get: 134 http://deb.debian.org/debian bookworm/main armhf libthai-data all 0.1.29-1 [176 kB] Get: 135 http://deb.debian.org/debian bookworm/main armhf libdatrie1 armhf 0.2.13-2+b1 [39.9 kB] Get: 136 http://deb.debian.org/debian bookworm/main armhf libthai0 armhf 0.1.29-1 [54.3 kB] Get: 137 http://deb.debian.org/debian bookworm/main armhf libpango-1.0-0 armhf 1.50.12+ds-1 [188 kB] Get: 138 http://deb.debian.org/debian bookworm/main armhf libpixman-1-0 armhf 0.42.2-1 [465 kB] Get: 139 http://deb.debian.org/debian bookworm/main armhf libxcb-render0 armhf 1.15-1 [114 kB] Get: 140 http://deb.debian.org/debian bookworm/main armhf libxcb-shm0 armhf 1.15-1 [106 kB] Get: 141 http://deb.debian.org/debian bookworm/main armhf libxrender1 armhf 1:0.9.10-1.1 [30.1 kB] Get: 142 http://deb.debian.org/debian bookworm/main armhf libcairo2 armhf 1.16.0-7 [493 kB] Get: 143 http://deb.debian.org/debian bookworm/main armhf libpangoft2-1.0-0 armhf 1.50.12+ds-1 [40.9 kB] Get: 144 http://deb.debian.org/debian bookworm/main armhf libpangocairo-1.0-0 armhf 1.50.12+ds-1 [30.3 kB] Get: 145 http://deb.debian.org/debian bookworm/main armhf libxft2 armhf 2.3.6-1 [53.8 kB] Get: 146 http://deb.debian.org/debian bookworm/main armhf libpangoxft-1.0-0 armhf 1.50.12+ds-1 [24.3 kB] Get: 147 http://deb.debian.org/debian bookworm/main armhf gir1.2-pango-1.0 armhf 1.50.12+ds-1 [37.4 kB] Get: 148 http://deb.debian.org/debian bookworm/main armhf libatk-bridge2.0-0 armhf 2.46.0-5 [56.5 kB] Get: 149 http://deb.debian.org/debian bookworm/main armhf libcairo-gobject2 armhf 1.16.0-7 [111 kB] Get: 150 http://deb.debian.org/debian bookworm/main armhf liblcms2-2 armhf 2.14-2 [125 kB] Get: 151 http://deb.debian.org/debian bookworm/main armhf libcolord2 armhf 1.4.6-2.2 [118 kB] Get: 152 http://deb.debian.org/debian bookworm/main armhf libavahi-common-data armhf 0.8-10 [107 kB] Get: 153 http://deb.debian.org/debian bookworm/main armhf libavahi-common3 armhf 0.8-10 [38.3 kB] Get: 154 http://deb.debian.org/debian bookworm/main armhf libavahi-client3 armhf 0.8-10 [41.6 kB] Get: 155 http://deb.debian.org/debian bookworm/main armhf libcups2 armhf 2.4.2-3 [209 kB] Get: 156 http://deb.debian.org/debian bookworm/main armhf libepoxy0 armhf 1.5.10-1 [164 kB] Get: 157 http://deb.debian.org/debian bookworm/main armhf libwayland-client0 armhf 1.21.0-1 [23.3 kB] Get: 158 http://deb.debian.org/debian bookworm/main armhf libwayland-cursor0 armhf 1.21.0-1 [13.4 kB] Get: 159 http://deb.debian.org/debian bookworm/main armhf libwayland-egl1 armhf 1.21.0-1 [8528 B] Get: 160 http://deb.debian.org/debian bookworm/main armhf libxcomposite1 armhf 1:0.4.5-1 [16.1 kB] Get: 161 http://deb.debian.org/debian bookworm/main armhf libxfixes3 armhf 1:6.0.0-2 [21.1 kB] Get: 162 http://deb.debian.org/debian bookworm/main armhf libxcursor1 armhf 1:1.2.1-1 [37.9 kB] Get: 163 http://deb.debian.org/debian bookworm/main armhf libxdamage1 armhf 1:1.1.6-1 [14.6 kB] Get: 164 http://deb.debian.org/debian bookworm/main armhf libxinerama1 armhf 2:1.1.4-3 [17.4 kB] Get: 165 http://deb.debian.org/debian bookworm/main armhf xkb-data all 2.35.1-1 [764 kB] Get: 166 http://deb.debian.org/debian bookworm/main armhf libxkbcommon0 armhf 1.5.0-1 [94.0 kB] Get: 167 http://deb.debian.org/debian bookworm/main armhf libxrandr2 armhf 2:1.5.2-2+b1 [36.0 kB] Get: 168 http://deb.debian.org/debian bookworm/main armhf libgtk-3-common all 3.24.37-2 [3891 kB] Get: 169 http://deb.debian.org/debian bookworm/main armhf libgtk-3-0 armhf 3.24.37-2 [2421 kB] Get: 170 http://deb.debian.org/debian bookworm/main armhf gir1.2-gtk-3.0 armhf 3.24.37-2 [219 kB] Get: 171 http://deb.debian.org/debian bookworm/main armhf libayatana-ido3-0.4-0 armhf 0.9.3-1 [48.1 kB] Get: 172 http://deb.debian.org/debian bookworm/main armhf libayatana-indicator3-7 armhf 0.9.3-1 [28.6 kB] Get: 173 http://deb.debian.org/debian bookworm/main armhf libdbusmenu-glib4 armhf 18.10.20180917~bzr492+repack1-3 [36.0 kB] Get: 174 http://deb.debian.org/debian bookworm/main armhf libdbusmenu-gtk3-4 armhf 18.10.20180917~bzr492+repack1-3 [24.1 kB] Get: 175 http://deb.debian.org/debian bookworm/main armhf libayatana-appindicator3-1 armhf 0.5.92-1 [22.4 kB] Get: 176 http://deb.debian.org/debian bookworm/main armhf gir1.2-ayatanaappindicator3-0.1 armhf 0.5.92-1 [9032 B] Get: 177 http://deb.debian.org/debian bookworm/main armhf gir1.2-ayatanaido3-0.4 armhf 0.9.3-1 [9116 B] Get: 178 http://deb.debian.org/debian bookworm/main armhf gir1.2-dbusmenu-glib-0.4 armhf 18.10.20180917~bzr492+repack1-3 [7636 B] Get: 179 http://deb.debian.org/debian bookworm/main armhf gir1.2-gconf-2.0 armhf 3.2.6-8 [349 kB] Get: 180 http://deb.debian.org/debian bookworm/main armhf libdw1 armhf 0.188-2.1 [215 kB] Get: 181 http://deb.debian.org/debian bookworm/main armhf libunwind8 armhf 1.6.2-3 [43.3 kB] Get: 182 http://deb.debian.org/debian bookworm/main armhf libcap2-bin armhf 1:2.66-3 [33.1 kB] Get: 183 http://deb.debian.org/debian bookworm/main armhf libgstreamer1.0-0 armhf 1.22.0-2 [1097 kB] Get: 184 http://deb.debian.org/debian bookworm/main armhf gir1.2-gstreamer-1.0 armhf 1.22.0-2 [105 kB] Get: 185 http://deb.debian.org/debian bookworm/main armhf libgtk2.0-common all 2.24.33-2 [2700 kB] Get: 186 http://deb.debian.org/debian bookworm/main armhf librsvg2-2 armhf 2.54.5+dfsg-1 [2194 kB] Get: 187 http://deb.debian.org/debian bookworm/main armhf librsvg2-common armhf 2.54.5+dfsg-1 [33.8 kB] Get: 188 http://deb.debian.org/debian bookworm/main armhf gnome-icon-theme all 3.12.0-5 [9867 kB] Get: 189 http://deb.debian.org/debian bookworm/main armhf libgtk2.0-0 armhf 2.24.33-2 [1588 kB] Get: 190 http://deb.debian.org/debian bookworm/main armhf gir1.2-gtk-2.0 armhf 2.24.33-2 [215 kB] Get: 191 http://deb.debian.org/debian bookworm/main armhf libnotify4 armhf 0.8.1-1 [27.7 kB] Get: 192 http://deb.debian.org/debian bookworm/main armhf gir1.2-notify-0.7 armhf 0.8.1-1 [11.6 kB] Get: 193 http://deb.debian.org/debian bookworm/main armhf libpkgconf3 armhf 1.8.1-1 [31.3 kB] Get: 194 http://deb.debian.org/debian bookworm/main armhf pkgconf-bin armhf 1.8.1-1 [28.5 kB] Get: 195 http://deb.debian.org/debian bookworm/main armhf pkgconf armhf 1.8.1-1 [25.9 kB] Get: 196 http://deb.debian.org/debian bookworm/main armhf pkg-config armhf 1.8.1-1 [13.7 kB] Get: 197 http://deb.debian.org/debian bookworm/main armhf libregexp-ipv6-perl all 0.03-3 [5212 B] Get: 198 http://deb.debian.org/debian bookworm/main armhf liburi-perl all 5.17-1 [90.4 kB] Get: 199 http://deb.debian.org/debian bookworm/main armhf libencode-locale-perl all 1.05-3 [12.9 kB] Get: 200 http://deb.debian.org/debian bookworm/main armhf libtimedate-perl all 2.3300-2 [39.3 kB] Get: 201 http://deb.debian.org/debian bookworm/main armhf libhttp-date-perl all 6.05-2 [10.5 kB] Get: 202 http://deb.debian.org/debian bookworm/main armhf libfile-listing-perl all 6.15-1 [12.6 kB] Get: 203 http://deb.debian.org/debian bookworm/main armhf libhtml-tagset-perl all 3.20-6 [11.7 kB] Get: 204 http://deb.debian.org/debian bookworm/main armhf libhtml-parser-perl armhf 3.81-1 [97.4 kB] Get: 205 http://deb.debian.org/debian bookworm/main armhf libhtml-tree-perl all 5.07-3 [211 kB] Get: 206 http://deb.debian.org/debian bookworm/main armhf libclone-perl armhf 0.46-1 [13.1 kB] Get: 207 http://deb.debian.org/debian bookworm/main armhf libio-html-perl all 1.004-3 [16.2 kB] Get: 208 http://deb.debian.org/debian bookworm/main armhf liblwp-mediatypes-perl all 6.04-2 [20.2 kB] Get: 209 http://deb.debian.org/debian bookworm/main armhf libhttp-message-perl all 6.44-1 [81.7 kB] Get: 210 http://deb.debian.org/debian bookworm/main armhf libhttp-cookies-perl all 6.10-1 [19.6 kB] Get: 211 http://deb.debian.org/debian bookworm/main armhf libhttp-negotiate-perl all 6.01-2 [13.1 kB] Get: 212 http://deb.debian.org/debian bookworm/main armhf perl-openssl-defaults armhf 7+b1 [7916 B] Get: 213 http://deb.debian.org/debian bookworm/main armhf libnet-ssleay-perl armhf 1.92-2+b1 [298 kB] Get: 214 http://deb.debian.org/debian bookworm/main armhf libio-socket-ssl-perl all 2.081-2 [219 kB] Get: 215 http://deb.debian.org/debian bookworm/main armhf libnet-http-perl all 6.22-1 [25.3 kB] Get: 216 http://deb.debian.org/debian bookworm/main armhf liblwp-protocol-https-perl all 6.10-1 [12.2 kB] Get: 217 http://deb.debian.org/debian bookworm/main armhf libtry-tiny-perl all 0.31-2 [22.6 kB] Get: 218 http://deb.debian.org/debian bookworm/main armhf libwww-robotrules-perl all 6.02-1 [12.9 kB] Get: 219 http://deb.debian.org/debian bookworm/main armhf libwww-perl all 6.68-1 [186 kB] Get: 220 http://deb.debian.org/debian bookworm/main armhf libxml-parser-perl armhf 2.46-4 [197 kB] Get: 221 http://deb.debian.org/debian bookworm/main armhf intltool all 0.51.0-6 [50.8 kB] Get: 222 http://deb.debian.org/debian bookworm/main armhf gnome-common all 3.18.0-4 [134 kB] Get: 223 http://deb.debian.org/debian bookworm/main armhf icu-devtools armhf 72.1-3 [183 kB] Get: 224 http://deb.debian.org/debian bookworm/main armhf libffi-dev armhf 3.4.4-1 [55.0 kB] Get: 225 http://deb.debian.org/debian bookworm/main armhf libglib2.0-data all 2.74.6-2 [1207 kB] Get: 226 http://deb.debian.org/debian bookworm/main armhf libglib2.0-bin armhf 2.74.6-2 [103 kB] Get: 227 http://deb.debian.org/debian bookworm/main armhf python3-lib2to3 all 3.11.2-3 [76.3 kB] Get: 228 http://deb.debian.org/debian bookworm/main armhf python3-distutils all 3.11.2-3 [131 kB] Get: 229 http://deb.debian.org/debian bookworm/main armhf libglib2.0-dev-bin armhf 2.74.6-2 [147 kB] Get: 230 http://deb.debian.org/debian bookworm/main armhf uuid-dev armhf 2.38.1-5+b1 [38.5 kB] Get: 231 http://deb.debian.org/debian bookworm/main armhf libblkid-dev armhf 2.38.1-5+b1 [169 kB] Get: 232 http://deb.debian.org/debian bookworm/main armhf libsepol-dev armhf 3.4-2 [329 kB] Get: 233 http://deb.debian.org/debian bookworm/main armhf libpcre2-16-0 armhf 10.42-1 [211 kB] Get: 234 http://deb.debian.org/debian bookworm/main armhf libpcre2-32-0 armhf 10.42-1 [203 kB] Get: 235 http://deb.debian.org/debian bookworm/main armhf libpcre2-posix3 armhf 10.42-1 [55.0 kB] Get: 236 http://deb.debian.org/debian bookworm/main armhf libpcre2-dev armhf 10.42-1 [666 kB] Get: 237 http://deb.debian.org/debian bookworm/main armhf libselinux1-dev armhf 3.4-1+b5 [150 kB] Get: 238 http://deb.debian.org/debian bookworm/main armhf libmount-dev armhf 2.38.1-5+b1 [22.5 kB] Get: 239 http://deb.debian.org/debian bookworm/main armhf zlib1g-dev armhf 1:1.2.13.dfsg-1 [902 kB] Get: 240 http://deb.debian.org/debian bookworm/main armhf libglib2.0-dev armhf 2.74.6-2 [1479 kB] Get: 241 http://deb.debian.org/debian bookworm/main armhf libatk1.0-dev armhf 2.46.0-5 [103 kB] Get: 242 http://deb.debian.org/debian bookworm/main armhf xml-core all 0.18+nmu1 [23.8 kB] Get: 243 http://deb.debian.org/debian bookworm/main armhf libdbus-1-dev armhf 1.14.6-1 [219 kB] Get: 244 http://deb.debian.org/debian bookworm/main armhf x11-common all 1:7.7+23 [252 kB] Get: 245 http://deb.debian.org/debian bookworm/main armhf libxtst6 armhf 2:1.2.3-1.1 [26.2 kB] Get: 246 http://deb.debian.org/debian bookworm/main armhf xorg-sgml-doctools all 1:1.11-1.1 [22.1 kB] Get: 247 http://deb.debian.org/debian bookworm/main armhf x11proto-dev all 2022.1-1 [599 kB] Get: 248 http://deb.debian.org/debian bookworm/main armhf libxau-dev armhf 1:1.0.9-1 [22.4 kB] Get: 249 http://deb.debian.org/debian bookworm/main armhf libxdmcp-dev armhf 1:1.1.2-3 [40.7 kB] Get: 250 http://deb.debian.org/debian bookworm/main armhf xtrans-dev all 1.4.0-1 [98.7 kB] Get: 251 http://deb.debian.org/debian bookworm/main armhf libpthread-stubs0-dev armhf 0.4-1 [5344 B] Get: 252 http://deb.debian.org/debian bookworm/main armhf libxcb1-dev armhf 1.15-1 [179 kB] Get: 253 http://deb.debian.org/debian bookworm/main armhf libx11-dev armhf 2:1.8.4-2 [777 kB] Get: 254 http://deb.debian.org/debian bookworm/main armhf libxext-dev armhf 2:1.3.4-1+b1 [103 kB] Get: 255 http://deb.debian.org/debian bookworm/main armhf libxfixes-dev armhf 1:6.0.0-2 [23.3 kB] Get: 256 http://deb.debian.org/debian bookworm/main armhf libxi-dev armhf 2:1.8-1+b1 [239 kB] Get: 257 http://deb.debian.org/debian bookworm/main armhf libxtst-dev armhf 2:1.2.3-1.1 [30.8 kB] Get: 258 http://deb.debian.org/debian bookworm/main armhf libatspi2.0-dev armhf 2.46.0-5 [76.3 kB] Get: 259 http://deb.debian.org/debian bookworm/main armhf libatk-bridge2.0-dev armhf 2.46.0-5 [8224 B] Get: 260 http://deb.debian.org/debian bookworm/main armhf liblzo2-2 armhf 2.10-2 [50.7 kB] Get: 261 http://deb.debian.org/debian bookworm/main armhf libcairo-script-interpreter2 armhf 1.16.0-7 [140 kB] Get: 262 http://deb.debian.org/debian bookworm/main armhf libexpat1-dev armhf 2.5.0-1 [134 kB] Get: 263 http://deb.debian.org/debian bookworm/main armhf libbrotli-dev armhf 1.0.9-2+b6 [268 kB] Get: 264 http://deb.debian.org/debian bookworm/main armhf libpng-dev armhf 1.6.39-2 [343 kB] Get: 265 http://deb.debian.org/debian bookworm/main armhf libfreetype-dev armhf 2.12.1+dfsg-5 [506 kB] Get: 266 http://deb.debian.org/debian bookworm/main armhf libfontconfig-dev armhf 2.14.1-4 [392 kB] Get: 267 http://deb.debian.org/debian bookworm/main armhf libpixman-1-dev armhf 0.42.2-1 [487 kB] Get: 268 http://deb.debian.org/debian bookworm/main armhf libice6 armhf 2:1.0.10-1 [51.9 kB] Get: 269 http://deb.debian.org/debian bookworm/main armhf libsm6 armhf 2:1.2.3-1 [33.0 kB] Get: 270 http://deb.debian.org/debian bookworm/main armhf libice-dev armhf 2:1.0.10-1 [61.9 kB] Get: 271 http://deb.debian.org/debian bookworm/main armhf libsm-dev armhf 2:1.2.3-1 [36.1 kB] Get: 272 http://deb.debian.org/debian bookworm/main armhf libxcb-render0-dev armhf 1.15-1 [118 kB] Get: 273 http://deb.debian.org/debian bookworm/main armhf libxcb-shm0-dev armhf 1.15-1 [107 kB] Get: 274 http://deb.debian.org/debian bookworm/main armhf libxrender-dev armhf 1:0.9.10-1.1 [38.1 kB] Get: 275 http://deb.debian.org/debian bookworm/main armhf libcairo2-dev armhf 1.16.0-7 [643 kB] Get: 276 http://deb.debian.org/debian bookworm/main armhf libglvnd0 armhf 1.6.0-1 [51.9 kB] Get: 277 http://deb.debian.org/debian bookworm/main armhf libdrm-common all 2.4.114-1 [7112 B] Get: 278 http://deb.debian.org/debian bookworm/main armhf libdrm2 armhf 2.4.114-1+b1 [33.0 kB] Get: 279 http://deb.debian.org/debian bookworm/main armhf libwayland-server0 armhf 1.21.0-1 [29.3 kB] Get: 280 http://deb.debian.org/debian bookworm/main armhf libgbm1 armhf 22.3.6-1+deb12u1 [34.3 kB] Get: 281 http://deb.debian.org/debian bookworm/main armhf libglapi-mesa armhf 22.3.6-1+deb12u1 [41.0 kB] Get: 282 http://deb.debian.org/debian bookworm/main armhf libx11-xcb1 armhf 2:1.8.4-2 [192 kB] Get: 283 http://deb.debian.org/debian bookworm/main armhf libxcb-dri2-0 armhf 1.15-1 [107 kB] Get: 284 http://deb.debian.org/debian bookworm/main armhf libxcb-dri3-0 armhf 1.15-1 [107 kB] Get: 285 http://deb.debian.org/debian bookworm/main armhf libxcb-present0 armhf 1.15-1 [105 kB] Get: 286 http://deb.debian.org/debian bookworm/main armhf libxcb-randr0 armhf 1.15-1 [116 kB] Get: 287 http://deb.debian.org/debian bookworm/main armhf libxcb-sync1 armhf 1.15-1 [108 kB] Get: 288 http://deb.debian.org/debian bookworm/main armhf libxcb-xfixes0 armhf 1.15-1 [110 kB] Get: 289 http://deb.debian.org/debian bookworm/main armhf libxshmfence1 armhf 1.3-1 [8592 B] Get: 290 http://deb.debian.org/debian bookworm/main armhf libegl-mesa0 armhf 22.3.6-1+deb12u1 [93.9 kB] Get: 291 http://deb.debian.org/debian bookworm/main armhf libegl1 armhf 1.6.0-1 [28.5 kB] Get: 292 http://deb.debian.org/debian bookworm/main armhf libxcb-glx0 armhf 1.15-1 [120 kB] Get: 293 http://deb.debian.org/debian bookworm/main armhf libxxf86vm1 armhf 1:1.1.4-1+b2 [20.2 kB] Get: 294 http://deb.debian.org/debian bookworm/main armhf libdrm-amdgpu1 armhf 2.4.114-1+b1 [19.3 kB] Get: 295 http://deb.debian.org/debian bookworm/main armhf libdrm-nouveau2 armhf 2.4.114-1+b1 [16.7 kB] Get: 296 http://deb.debian.org/debian bookworm/main armhf libdrm-radeon1 armhf 2.4.114-1+b1 [19.3 kB] Get: 297 http://deb.debian.org/debian bookworm/main armhf libedit2 armhf 3.1-20221030-2 [77.0 kB] Get: 298 http://deb.debian.org/debian bookworm/main armhf libz3-4 armhf 4.8.12-3.1 [6061 kB] Get: 299 http://deb.debian.org/debian bookworm/main armhf libllvm15 armhf 1:15.0.6-4+b1 [20.5 MB] Get: 300 http://deb.debian.org/debian bookworm/main armhf libsensors-config all 1:3.6.0-7.1 [14.3 kB] Get: 301 http://deb.debian.org/debian bookworm/main armhf libsensors5 armhf 1:3.6.0-7.1 [31.6 kB] Get: 302 http://deb.debian.org/debian bookworm/main armhf libgl1-mesa-dri armhf 22.3.6-1+deb12u1 [5792 kB] Get: 303 http://deb.debian.org/debian bookworm/main armhf libglx-mesa0 armhf 22.3.6-1+deb12u1 [126 kB] Get: 304 http://deb.debian.org/debian bookworm/main armhf libglx0 armhf 1.6.0-1 [32.0 kB] Get: 305 http://deb.debian.org/debian bookworm/main armhf libgl1 armhf 1.6.0-1 [90.6 kB] Get: 306 http://deb.debian.org/debian bookworm/main armhf libglx-dev armhf 1.6.0-1 [15.3 kB] Get: 307 http://deb.debian.org/debian bookworm/main armhf libgl-dev armhf 1.6.0-1 [100 kB] Get: 308 http://deb.debian.org/debian bookworm/main armhf libegl-dev armhf 1.6.0-1 [19.1 kB] Get: 309 http://deb.debian.org/debian bookworm/main armhf libglvnd-core-dev armhf 1.6.0-1 [12.9 kB] Get: 310 http://deb.debian.org/debian bookworm/main armhf libgles1 armhf 1.6.0-1 [11.8 kB] Get: 311 http://deb.debian.org/debian bookworm/main armhf libgles2 armhf 1.6.0-1 [17.3 kB] Get: 312 http://deb.debian.org/debian bookworm/main armhf libgles-dev armhf 1.6.0-1 [50.4 kB] Get: 313 http://deb.debian.org/debian bookworm/main armhf libopengl0 armhf 1.6.0-1 [31.7 kB] Get: 314 http://deb.debian.org/debian bookworm/main armhf libopengl-dev armhf 1.6.0-1 [4932 B] Get: 315 http://deb.debian.org/debian bookworm/main armhf libglvnd-dev armhf 1.6.0-1 [4692 B] Get: 316 http://deb.debian.org/debian bookworm/main armhf libegl1-mesa-dev armhf 22.3.6-1+deb12u1 [18.5 kB] Get: 317 http://deb.debian.org/debian bookworm/main armhf libepoxy-dev armhf 1.5.10-1 [128 kB] Get: 318 http://deb.debian.org/debian bookworm/main armhf libfribidi-dev armhf 1.0.8-2.1 [103 kB] Get: 319 http://deb.debian.org/debian bookworm/main armhf libgdk-pixbuf2.0-bin armhf 2.42.10+dfsg-1+b1 [17.4 kB] Get: 320 http://deb.debian.org/debian bookworm/main armhf libjpeg62-turbo-dev armhf 1:2.1.5-2 [260 kB] Get: 321 http://deb.debian.org/debian bookworm/main armhf libjpeg-dev armhf 1:2.1.5-2 [71.8 kB] Get: 322 http://deb.debian.org/debian bookworm/main armhf libjbig-dev armhf 2.1-6.1 [27.5 kB] Get: 323 http://deb.debian.org/debian bookworm/main armhf liblzma-dev armhf 5.4.1-0.2 [248 kB] Get: 324 http://deb.debian.org/debian bookworm/main armhf libzstd-dev armhf 1.5.4+dfsg2-5 [314 kB] Get: 325 http://deb.debian.org/debian bookworm/main armhf libwebpmux3 armhf 1.2.4-0.1 [105 kB] Get: 326 http://deb.debian.org/debian bookworm/main armhf libwebpdemux2 armhf 1.2.4-0.1 [98.2 kB] Get: 327 http://deb.debian.org/debian bookworm/main armhf libwebp-dev armhf 1.2.4-0.1 [348 kB] Get: 328 http://deb.debian.org/debian bookworm/main armhf libtiffxx6 armhf 4.5.0-5 [144 kB] Get: 329 http://deb.debian.org/debian bookworm/main armhf libdeflate-dev armhf 1.14-1 [48.7 kB] Get: 330 http://deb.debian.org/debian bookworm/main armhf liblerc-dev armhf 4.0.0+ds-2 [154 kB] Get: 331 http://deb.debian.org/debian bookworm/main armhf libtiff-dev armhf 4.5.0-5 [434 kB] Get: 332 http://deb.debian.org/debian bookworm/main armhf libgdk-pixbuf-2.0-dev armhf 2.42.10+dfsg-1+b1 [51.7 kB] Get: 333 http://deb.debian.org/debian bookworm/main armhf libharfbuzz-icu0 armhf 6.0.0+dfsg-3 [1556 kB] Get: 334 http://deb.debian.org/debian bookworm/main armhf libharfbuzz-gobject0 armhf 6.0.0+dfsg-3 [1569 kB] Get: 335 http://deb.debian.org/debian bookworm/main armhf libharfbuzz-subset0 armhf 6.0.0+dfsg-3 [1889 kB] Get: 336 http://deb.debian.org/debian bookworm/main armhf libgraphite2-dev armhf 1.3.14-1 [24.0 kB] Get: 337 http://deb.debian.org/debian bookworm/main armhf libicu-dev armhf 72.1-3 [10.1 MB] Get: 338 http://deb.debian.org/debian bookworm/main armhf libharfbuzz-dev armhf 6.0.0+dfsg-3 [1668 kB] Get: 339 http://deb.debian.org/debian bookworm/main armhf libdatrie-dev armhf 0.2.13-2+b1 [15.1 kB] Get: 340 http://deb.debian.org/debian bookworm/main armhf libthai-dev armhf 0.1.29-1 [21.3 kB] Get: 341 http://deb.debian.org/debian bookworm/main armhf libxft-dev armhf 2.3.6-1 [73.2 kB] Get: 342 http://deb.debian.org/debian bookworm/main armhf pango1.0-tools armhf 1.50.12+ds-1 [36.8 kB] Get: 343 http://deb.debian.org/debian bookworm/main armhf libpango1.0-dev armhf 1.50.12+ds-1 [152 kB] Get: 344 http://deb.debian.org/debian bookworm/main armhf libwayland-bin armhf 1.21.0-1 [20.9 kB] Get: 345 http://deb.debian.org/debian bookworm/main armhf libwayland-dev armhf 1.21.0-1 [72.6 kB] Get: 346 http://deb.debian.org/debian bookworm/main armhf libxcomposite-dev armhf 1:0.4.5-1 [19.8 kB] Get: 347 http://deb.debian.org/debian bookworm/main armhf libxcursor-dev armhf 1:1.2.1-1 [49.3 kB] Get: 348 http://deb.debian.org/debian bookworm/main armhf libxdamage-dev armhf 1:1.1.6-1 [14.5 kB] Get: 349 http://deb.debian.org/debian bookworm/main armhf libxinerama-dev armhf 2:1.1.4-3 [19.8 kB] Get: 350 http://deb.debian.org/debian bookworm/main armhf libxkbcommon-dev armhf 1.5.0-1 [51.0 kB] Get: 351 http://deb.debian.org/debian bookworm/main armhf libxrandr-dev armhf 2:1.5.2-2+b1 [44.3 kB] Get: 352 http://deb.debian.org/debian bookworm/main armhf wayland-protocols all 1.31-1 [74.6 kB] Get: 353 http://deb.debian.org/debian bookworm/main armhf libgtk-3-dev armhf 3.24.37-2 [1115 kB] Get: 354 http://deb.debian.org/debian bookworm/main armhf libayatana-ido3-dev armhf 0.9.3-1 [17.1 kB] Get: 355 http://deb.debian.org/debian bookworm/main armhf libayatana-indicator3-dev armhf 0.9.3-1 [10.8 kB] Get: 356 http://deb.debian.org/debian bookworm/main armhf libxml2-utils armhf 2.9.14+dfsg-1.2 [97.4 kB] Get: 357 http://deb.debian.org/debian bookworm/main armhf libgtk2.0-dev armhf 2.24.33-2 [827 kB] Get: 358 http://deb.debian.org/debian bookworm/main armhf libdbusmenu-glib-dev armhf 18.10.20180917~bzr492+repack1-3 [64.2 kB] Get: 359 http://deb.debian.org/debian bookworm/main armhf libayatana-appindicator3-dev armhf 0.5.92-1 [18.2 kB] Get: 360 http://deb.debian.org/debian bookworm/main armhf libelf-dev armhf 0.188-2.1 [68.7 kB] Get: 361 http://deb.debian.org/debian bookworm/main armhf libdw-dev armhf 0.188-2.1 [292 kB] Get: 362 http://deb.debian.org/debian bookworm/main armhf libgconf2-dev armhf 3.2.6-8 [434 kB] Get: 363 http://deb.debian.org/debian bookworm/main armhf libunwind-dev armhf 1.6.2-3 [443 kB] Get: 364 http://deb.debian.org/debian bookworm/main armhf libgstreamer1.0-dev armhf 1.22.0-2 [548 kB] Get: 365 http://deb.debian.org/debian bookworm/main armhf libnotify-dev armhf 0.8.1-1 [17.5 kB] Get: 366 http://deb.debian.org/debian bookworm/main armhf libxml2-dev armhf 2.9.14+dfsg-1.2 [709 kB] Fetched 163 MB in 60s (2728 kB/s) debconf: delaying package configuration, since apt-utils is not installed Selecting previously unselected package libargon2-1:armhf. (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 19329 files and directories currently installed.) Preparing to unpack .../00-libargon2-1_0~20171227-0.3+deb12u1_armhf.deb ... Unpacking libargon2-1:armhf (0~20171227-0.3+deb12u1) ... Selecting previously unselected package dmsetup. Preparing to unpack .../01-dmsetup_2%3a1.02.185-2_armhf.deb ... Unpacking dmsetup (2:1.02.185-2) ... Selecting previously unselected package libdevmapper1.02.1:armhf. Preparing to unpack .../02-libdevmapper1.02.1_2%3a1.02.185-2_armhf.deb ... Unpacking libdevmapper1.02.1:armhf (2:1.02.185-2) ... Selecting previously unselected package libjson-c5:armhf. Preparing to unpack .../03-libjson-c5_0.16-2_armhf.deb ... Unpacking libjson-c5:armhf (0.16-2) ... Selecting previously unselected package libcryptsetup12:armhf. Preparing to unpack .../04-libcryptsetup12_2%3a2.6.1-4~deb12u1_armhf.deb ... Unpacking libcryptsetup12:armhf (2:2.6.1-4~deb12u1) ... Selecting previously unselected package libfdisk1:armhf. Preparing to unpack .../05-libfdisk1_2.38.1-5+b1_armhf.deb ... Unpacking libfdisk1:armhf (2.38.1-5+b1) ... Selecting previously unselected package libkmod2:armhf. Preparing to unpack .../06-libkmod2_30+20221128-1_armhf.deb ... Unpacking libkmod2:armhf (30+20221128-1) ... Selecting previously unselected package libapparmor1:armhf. Preparing to unpack .../07-libapparmor1_3.0.8-3_armhf.deb ... Unpacking libapparmor1:armhf (3.0.8-3) ... Selecting previously unselected package libip4tc2:armhf. Preparing to unpack .../08-libip4tc2_1.8.9-2_armhf.deb ... Unpacking libip4tc2:armhf (1.8.9-2) ... Selecting previously unselected package libsystemd-shared:armhf. Preparing to unpack .../09-libsystemd-shared_252.6-1_armhf.deb ... Unpacking libsystemd-shared:armhf (252.6-1) ... Selecting previously unselected package systemd. Preparing to unpack .../10-systemd_252.6-1_armhf.deb ... Unpacking systemd (252.6-1) ... Setting up libargon2-1:armhf (0~20171227-0.3+deb12u1) ... Setting up libjson-c5:armhf (0.16-2) ... Setting up libfdisk1:armhf (2.38.1-5+b1) ... Setting up libkmod2:armhf (30+20221128-1) ... Setting up libapparmor1:armhf (3.0.8-3) ... Setting up libip4tc2:armhf (1.8.9-2) ... Setting up libsystemd-shared:armhf (252.6-1) ... Setting up libdevmapper1.02.1:armhf (2:1.02.185-2) ... Setting up libcryptsetup12:armhf (2:2.6.1-4~deb12u1) ... Setting up systemd (252.6-1) ... Created symlink /etc/systemd/system/getty.target.wants/getty@tty1.service -> /lib/systemd/system/getty@.service. Created symlink /etc/systemd/system/multi-user.target.wants/remote-fs.target -> /lib/systemd/system/remote-fs.target. Created symlink /etc/systemd/system/sysinit.target.wants/systemd-pstore.service -> /lib/systemd/system/systemd-pstore.service. Initializing machine ID from random generator. Creating group 'systemd-journal' with GID 999. Creating group 'systemd-network' with GID 998. Creating user 'systemd-network' (systemd Network Management) with UID 998 and GID 998. Setting up dmsetup (2:1.02.185-2) ... Selecting previously unselected package systemd-sysv. (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 20244 files and directories currently installed.) Preparing to unpack .../00-systemd-sysv_252.6-1_armhf.deb ... Unpacking systemd-sysv (252.6-1) ... Selecting previously unselected package libdbus-1-3:armhf. Preparing to unpack .../01-libdbus-1-3_1.14.6-1_armhf.deb ... Unpacking libdbus-1-3:armhf (1.14.6-1) ... Selecting previously unselected package dbus-bin. Preparing to unpack .../02-dbus-bin_1.14.6-1_armhf.deb ... Unpacking dbus-bin (1.14.6-1) ... Selecting previously unselected package dbus-session-bus-common. Preparing to unpack .../03-dbus-session-bus-common_1.14.6-1_all.deb ... Unpacking dbus-session-bus-common (1.14.6-1) ... Selecting previously unselected package libexpat1:armhf. Preparing to unpack .../04-libexpat1_2.5.0-1_armhf.deb ... Unpacking libexpat1:armhf (2.5.0-1) ... Selecting previously unselected package dbus-daemon. Preparing to unpack .../05-dbus-daemon_1.14.6-1_armhf.deb ... Unpacking dbus-daemon (1.14.6-1) ... Selecting previously unselected package dbus-system-bus-common. Preparing to unpack .../06-dbus-system-bus-common_1.14.6-1_all.deb ... Unpacking dbus-system-bus-common (1.14.6-1) ... Selecting previously unselected package dbus. Preparing to unpack .../07-dbus_1.14.6-1_armhf.deb ... Unpacking dbus (1.14.6-1) ... Selecting previously unselected package autoconf-archive. Preparing to unpack .../08-autoconf-archive_20220903-3_all.deb ... Unpacking autoconf-archive (20220903-3) ... Selecting previously unselected package libpython3.11-minimal:armhf. Preparing to unpack .../09-libpython3.11-minimal_3.11.2-6_armhf.deb ... Unpacking libpython3.11-minimal:armhf (3.11.2-6) ... Selecting previously unselected package python3.11-minimal. Preparing to unpack .../10-python3.11-minimal_3.11.2-6_armhf.deb ... Unpacking python3.11-minimal (3.11.2-6) ... Setting up libpython3.11-minimal:armhf (3.11.2-6) ... Setting up libexpat1:armhf (2.5.0-1) ... Setting up python3.11-minimal (3.11.2-6) ... Selecting previously unselected package python3-minimal. (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 21833 files and directories currently installed.) Preparing to unpack .../0-python3-minimal_3.11.2-1+b1_armhf.deb ... Unpacking python3-minimal (3.11.2-1+b1) ... Selecting previously unselected package media-types. Preparing to unpack .../1-media-types_10.0.0_all.deb ... Unpacking media-types (10.0.0) ... Selecting previously unselected package readline-common. Preparing to unpack .../2-readline-common_8.2-1.3_all.deb ... Unpacking readline-common (8.2-1.3) ... Selecting previously unselected package libreadline8:armhf. Preparing to unpack .../3-libreadline8_8.2-1.3_armhf.deb ... Unpacking libreadline8:armhf (8.2-1.3) ... Selecting previously unselected package libpython3.11-stdlib:armhf. Preparing to unpack .../4-libpython3.11-stdlib_3.11.2-6_armhf.deb ... Unpacking libpython3.11-stdlib:armhf (3.11.2-6) ... Selecting previously unselected package python3.11. Preparing to unpack .../5-python3.11_3.11.2-6_armhf.deb ... Unpacking python3.11 (3.11.2-6) ... Selecting previously unselected package libpython3-stdlib:armhf. Preparing to unpack .../6-libpython3-stdlib_3.11.2-1+b1_armhf.deb ... Unpacking libpython3-stdlib:armhf (3.11.2-1+b1) ... Setting up python3-minimal (3.11.2-1+b1) ... Selecting previously unselected package python3. (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 22267 files and directories currently installed.) Preparing to unpack .../000-python3_3.11.2-1+b1_armhf.deb ... Unpacking python3 (3.11.2-1+b1) ... Selecting previously unselected package sgml-base. Preparing to unpack .../001-sgml-base_1.31_all.deb ... Unpacking sgml-base (1.31) ... Selecting previously unselected package netbase. Preparing to unpack .../002-netbase_6.4_all.deb ... Unpacking netbase (6.4) ... Selecting previously unselected package libproc2-0:armhf. Preparing to unpack .../003-libproc2-0_2%3a4.0.2-3_armhf.deb ... Unpacking libproc2-0:armhf (2:4.0.2-3) ... Selecting previously unselected package procps. Preparing to unpack .../004-procps_2%3a4.0.2-3_armhf.deb ... Unpacking procps (2:4.0.2-3) ... Selecting previously unselected package sensible-utils. Preparing to unpack .../005-sensible-utils_0.0.17+nmu1_all.deb ... Unpacking sensible-utils (0.0.17+nmu1) ... Selecting previously unselected package openssl. Preparing to unpack .../006-openssl_3.0.8-1_armhf.deb ... Unpacking openssl (3.0.8-1) ... Selecting previously unselected package ca-certificates. Preparing to unpack .../007-ca-certificates_20230311_all.deb ... Unpacking ca-certificates (20230311) ... Selecting previously unselected package libmagic-mgc. Preparing to unpack .../008-libmagic-mgc_1%3a5.44-3_armhf.deb ... Unpacking libmagic-mgc (1:5.44-3) ... Selecting previously unselected package libmagic1:armhf. Preparing to unpack .../009-libmagic1_1%3a5.44-3_armhf.deb ... Unpacking libmagic1:armhf (1:5.44-3) ... Selecting previously unselected package file. Preparing to unpack .../010-file_1%3a5.44-3_armhf.deb ... Unpacking file (1:5.44-3) ... Selecting previously unselected package gettext-base. Preparing to unpack .../011-gettext-base_0.21-12_armhf.deb ... Unpacking gettext-base (0.21-12) ... Selecting previously unselected package libuchardet0:armhf. Preparing to unpack .../012-libuchardet0_0.0.7-1_armhf.deb ... Unpacking libuchardet0:armhf (0.0.7-1) ... Selecting previously unselected package groff-base. Preparing to unpack .../013-groff-base_1.22.4-10_armhf.deb ... Unpacking groff-base (1.22.4-10) ... Selecting previously unselected package libpam-systemd:armhf. Preparing to unpack .../014-libpam-systemd_252.6-1_armhf.deb ... Unpacking libpam-systemd:armhf (252.6-1) ... Selecting previously unselected package bsdextrautils. Preparing to unpack .../015-bsdextrautils_2.38.1-5+b1_armhf.deb ... Unpacking bsdextrautils (2.38.1-5+b1) ... Selecting previously unselected package libpipeline1:armhf. Preparing to unpack .../016-libpipeline1_1.5.7-1_armhf.deb ... Unpacking libpipeline1:armhf (1.5.7-1) ... Selecting previously unselected package man-db. Preparing to unpack .../017-man-db_2.11.2-2_armhf.deb ... Unpacking man-db (2.11.2-2) ... Selecting previously unselected package ucf. Preparing to unpack .../018-ucf_3.0043+nmu1_all.deb ... Moving old data out of the way Unpacking ucf (3.0043+nmu1) ... Selecting previously unselected package hicolor-icon-theme. Preparing to unpack .../019-hicolor-icon-theme_0.17-2_all.deb ... Unpacking hicolor-icon-theme (0.17-2) ... Selecting previously unselected package libgdk-pixbuf2.0-common. Preparing to unpack .../020-libgdk-pixbuf2.0-common_2.42.10+dfsg-1_all.deb ... Unpacking libgdk-pixbuf2.0-common (2.42.10+dfsg-1) ... Selecting previously unselected package libglib2.0-0:armhf. Preparing to unpack .../021-libglib2.0-0_2.74.6-2_armhf.deb ... Unpacking libglib2.0-0:armhf (2.74.6-2) ... Selecting previously unselected package libicu72:armhf. Preparing to unpack .../022-libicu72_72.1-3_armhf.deb ... Unpacking libicu72:armhf (72.1-3) ... Selecting previously unselected package libxml2:armhf. Preparing to unpack .../023-libxml2_2.9.14+dfsg-1.2_armhf.deb ... Unpacking libxml2:armhf (2.9.14+dfsg-1.2) ... Selecting previously unselected package shared-mime-info. Preparing to unpack .../024-shared-mime-info_2.2-1_armhf.deb ... Unpacking shared-mime-info (2.2-1) ... Selecting previously unselected package libjpeg62-turbo:armhf. Preparing to unpack .../025-libjpeg62-turbo_1%3a2.1.5-2_armhf.deb ... Unpacking libjpeg62-turbo:armhf (1:2.1.5-2) ... Selecting previously unselected package libpng16-16:armhf. Preparing to unpack .../026-libpng16-16_1.6.39-2_armhf.deb ... Unpacking libpng16-16:armhf (1.6.39-2) ... Selecting previously unselected package libdeflate0:armhf. Preparing to unpack .../027-libdeflate0_1.14-1_armhf.deb ... Unpacking libdeflate0:armhf (1.14-1) ... Selecting previously unselected package libjbig0:armhf. Preparing to unpack .../028-libjbig0_2.1-6.1_armhf.deb ... Unpacking libjbig0:armhf (2.1-6.1) ... Selecting previously unselected package liblerc4:armhf. Preparing to unpack .../029-liblerc4_4.0.0+ds-2_armhf.deb ... Unpacking liblerc4:armhf (4.0.0+ds-2) ... Selecting previously unselected package libwebp7:armhf. Preparing to unpack .../030-libwebp7_1.2.4-0.1_armhf.deb ... Unpacking libwebp7:armhf (1.2.4-0.1) ... Selecting previously unselected package libtiff6:armhf. Preparing to unpack .../031-libtiff6_4.5.0-5_armhf.deb ... Unpacking libtiff6:armhf (4.5.0-5) ... Selecting previously unselected package libgdk-pixbuf-2.0-0:armhf. Preparing to unpack .../032-libgdk-pixbuf-2.0-0_2.42.10+dfsg-1+b1_armhf.deb ... Unpacking libgdk-pixbuf-2.0-0:armhf (2.42.10+dfsg-1+b1) ... Selecting previously unselected package gtk-update-icon-cache. Preparing to unpack .../033-gtk-update-icon-cache_3.24.37-2_armhf.deb ... Unpacking gtk-update-icon-cache (3.24.37-2) ... Selecting previously unselected package adwaita-icon-theme. Preparing to unpack .../034-adwaita-icon-theme_43-1_all.deb ... Unpacking adwaita-icon-theme (43-1) ... Selecting previously unselected package at-spi2-common. Preparing to unpack .../035-at-spi2-common_2.46.0-5_all.deb ... Unpacking at-spi2-common (2.46.0-5) ... Selecting previously unselected package m4. Preparing to unpack .../036-m4_1.4.19-3_armhf.deb ... Unpacking m4 (1.4.19-3) ... Selecting previously unselected package autoconf. Preparing to unpack .../037-autoconf_2.71-3_all.deb ... Unpacking autoconf (2.71-3) ... Selecting previously unselected package autotools-dev. Preparing to unpack .../038-autotools-dev_20220109.1_all.deb ... Unpacking autotools-dev (20220109.1) ... Selecting previously unselected package automake. Preparing to unpack .../039-automake_1%3a1.16.5-1.3_all.deb ... Unpacking automake (1:1.16.5-1.3) ... Selecting previously unselected package autopoint. Preparing to unpack .../040-autopoint_0.21-12_all.deb ... Unpacking autopoint (0.21-12) ... Selecting previously unselected package libarchive13:armhf. Preparing to unpack .../041-libarchive13_3.6.2-1_armhf.deb ... Unpacking libarchive13:armhf (3.6.2-1) ... Selecting previously unselected package libbrotli1:armhf. Preparing to unpack .../042-libbrotli1_1.0.9-2+b6_armhf.deb ... Unpacking libbrotli1:armhf (1.0.9-2+b6) ... Selecting previously unselected package libsasl2-modules-db:armhf. Preparing to unpack .../043-libsasl2-modules-db_2.1.28+dfsg-10_armhf.deb ... Unpacking libsasl2-modules-db:armhf (2.1.28+dfsg-10) ... Selecting previously unselected package libsasl2-2:armhf. Preparing to unpack .../044-libsasl2-2_2.1.28+dfsg-10_armhf.deb ... Unpacking libsasl2-2:armhf (2.1.28+dfsg-10) ... Selecting previously unselected package libldap-2.5-0:armhf. Preparing to unpack .../045-libldap-2.5-0_2.5.13+dfsg-5_armhf.deb ... Unpacking libldap-2.5-0:armhf (2.5.13+dfsg-5) ... Selecting previously unselected package libnghttp2-14:armhf. Preparing to unpack .../046-libnghttp2-14_1.52.0-1_armhf.deb ... Unpacking libnghttp2-14:armhf (1.52.0-1) ... Selecting previously unselected package libpsl5:armhf. Preparing to unpack .../047-libpsl5_0.21.2-1_armhf.deb ... Unpacking libpsl5:armhf (0.21.2-1) ... Selecting previously unselected package librtmp1:armhf. Preparing to unpack .../048-librtmp1_2.4+20151223.gitfa8646d.1-2+b2_armhf.deb ... Unpacking librtmp1:armhf (2.4+20151223.gitfa8646d.1-2+b2) ... Selecting previously unselected package libssh2-1:armhf. Preparing to unpack .../049-libssh2-1_1.10.0-3+b1_armhf.deb ... Unpacking libssh2-1:armhf (1.10.0-3+b1) ... Selecting previously unselected package libcurl4:armhf. Preparing to unpack .../050-libcurl4_7.88.1-9_armhf.deb ... Unpacking libcurl4:armhf (7.88.1-9) ... Selecting previously unselected package libjsoncpp25:armhf. Preparing to unpack .../051-libjsoncpp25_1.9.5-4_armhf.deb ... Unpacking libjsoncpp25:armhf (1.9.5-4) ... Selecting previously unselected package librhash0:armhf. Preparing to unpack .../052-librhash0_1.4.3-3_armhf.deb ... Unpacking librhash0:armhf (1.4.3-3) ... Selecting previously unselected package libuv1:armhf. Preparing to unpack .../053-libuv1_1.44.2-1_armhf.deb ... Unpacking libuv1:armhf (1.44.2-1) ... Selecting previously unselected package cmake-data. Preparing to unpack .../054-cmake-data_3.25.1-1_all.deb ... Unpacking cmake-data (3.25.1-1) ... Selecting previously unselected package cmake. Preparing to unpack .../055-cmake_3.25.1-1_armhf.deb ... Unpacking cmake (3.25.1-1) ... Selecting previously unselected package dbus-user-session. Preparing to unpack .../056-dbus-user-session_1.14.6-1_armhf.deb ... Unpacking dbus-user-session (1.14.6-1) ... Selecting previously unselected package libdconf1:armhf. Preparing to unpack .../057-libdconf1_0.40.0-4_armhf.deb ... Unpacking libdconf1:armhf (0.40.0-4) ... Selecting previously unselected package dconf-service. Preparing to unpack .../058-dconf-service_0.40.0-4_armhf.deb ... Unpacking dconf-service (0.40.0-4) ... Selecting previously unselected package dconf-gsettings-backend:armhf. Preparing to unpack .../059-dconf-gsettings-backend_0.40.0-4_armhf.deb ... Unpacking dconf-gsettings-backend:armhf (0.40.0-4) ... Selecting previously unselected package libdebhelper-perl. Preparing to unpack .../060-libdebhelper-perl_13.11.4_all.deb ... Unpacking libdebhelper-perl (13.11.4) ... Selecting previously unselected package libtool. Preparing to unpack .../061-libtool_2.4.7-5_all.deb ... Unpacking libtool (2.4.7-5) ... Selecting previously unselected package dh-autoreconf. Preparing to unpack .../062-dh-autoreconf_20_all.deb ... Unpacking dh-autoreconf (20) ... Selecting previously unselected package libarchive-zip-perl. Preparing to unpack .../063-libarchive-zip-perl_1.68-1_all.deb ... Unpacking libarchive-zip-perl (1.68-1) ... Selecting previously unselected package libsub-override-perl. Preparing to unpack .../064-libsub-override-perl_0.09-4_all.deb ... Unpacking libsub-override-perl (0.09-4) ... Selecting previously unselected package libfile-stripnondeterminism-perl. Preparing to unpack .../065-libfile-stripnondeterminism-perl_1.13.1-1_all.deb ... Unpacking libfile-stripnondeterminism-perl (1.13.1-1) ... Selecting previously unselected package dh-strip-nondeterminism. Preparing to unpack .../066-dh-strip-nondeterminism_1.13.1-1_all.deb ... Unpacking dh-strip-nondeterminism (1.13.1-1) ... Selecting previously unselected package libelf1:armhf. Preparing to unpack .../067-libelf1_0.188-2.1_armhf.deb ... Unpacking libelf1:armhf (0.188-2.1) ... Selecting previously unselected package dwz. Preparing to unpack .../068-dwz_0.15-1_armhf.deb ... Unpacking dwz (0.15-1) ... Selecting previously unselected package gettext. Preparing to unpack .../069-gettext_0.21-12_armhf.deb ... Unpacking gettext (0.21-12) ... Selecting previously unselected package intltool-debian. Preparing to unpack .../070-intltool-debian_0.35.0+20060710.6_all.deb ... Unpacking intltool-debian (0.35.0+20060710.6) ... Selecting previously unselected package po-debconf. Preparing to unpack .../071-po-debconf_1.0.21+nmu1_all.deb ... Unpacking po-debconf (1.0.21+nmu1) ... Selecting previously unselected package debhelper. Preparing to unpack .../072-debhelper_13.11.4_all.deb ... Unpacking debhelper (13.11.4) ... Selecting previously unselected package libfreetype6:armhf. Preparing to unpack .../073-libfreetype6_2.12.1+dfsg-5_armhf.deb ... Unpacking libfreetype6:armhf (2.12.1+dfsg-5) ... Selecting previously unselected package fonts-dejavu-core. Preparing to unpack .../074-fonts-dejavu-core_2.37-6_all.deb ... Unpacking fonts-dejavu-core (2.37-6) ... Selecting previously unselected package fontconfig-config. Preparing to unpack .../075-fontconfig-config_2.14.1-4_armhf.deb ... Unpacking fontconfig-config (2.14.1-4) ... Selecting previously unselected package libfontconfig1:armhf. Preparing to unpack .../076-libfontconfig1_2.14.1-4_armhf.deb ... Unpacking libfontconfig1:armhf (2.14.1-4) ... Selecting previously unselected package fontconfig. Preparing to unpack .../077-fontconfig_2.14.1-4_armhf.deb ... Unpacking fontconfig (2.14.1-4) ... Selecting previously unselected package libdbus-glib-1-2:armhf. Preparing to unpack .../078-libdbus-glib-1-2_0.112-3_armhf.deb ... Unpacking libdbus-glib-1-2:armhf (0.112-3) ... Selecting previously unselected package gconf2-common. Preparing to unpack .../079-gconf2-common_3.2.6-8_all.deb ... Unpacking gconf2-common (3.2.6-8) ... Selecting previously unselected package libgconf-2-4:armhf. Preparing to unpack .../080-libgconf-2-4_3.2.6-8_armhf.deb ... Unpacking libgconf-2-4:armhf (3.2.6-8) ... Selecting previously unselected package gconf-service. Preparing to unpack .../081-gconf-service_3.2.6-8_armhf.deb ... Unpacking gconf-service (3.2.6-8) ... Selecting previously unselected package psmisc. Preparing to unpack .../082-psmisc_23.6-1_armhf.deb ... Unpacking psmisc (23.6-1) ... Selecting previously unselected package gconf2. Preparing to unpack .../083-gconf2_3.2.6-8_armhf.deb ... Unpacking gconf2 (3.2.6-8) ... Selecting previously unselected package libgirepository-1.0-1:armhf. Preparing to unpack .../084-libgirepository-1.0-1_1.74.0-3_armhf.deb ... Unpacking libgirepository-1.0-1:armhf (1.74.0-3) ... Selecting previously unselected package gir1.2-glib-2.0:armhf. Preparing to unpack .../085-gir1.2-glib-2.0_1.74.0-3_armhf.deb ... Unpacking gir1.2-glib-2.0:armhf (1.74.0-3) ... Selecting previously unselected package libatk1.0-0:armhf. Preparing to unpack .../086-libatk1.0-0_2.46.0-5_armhf.deb ... Unpacking libatk1.0-0:armhf (2.46.0-5) ... Selecting previously unselected package gir1.2-atk-1.0:armhf. Preparing to unpack .../087-gir1.2-atk-1.0_2.46.0-5_armhf.deb ... Unpacking gir1.2-atk-1.0:armhf (2.46.0-5) ... Selecting previously unselected package gir1.2-freedesktop:armhf. Preparing to unpack .../088-gir1.2-freedesktop_1.74.0-3_armhf.deb ... Unpacking gir1.2-freedesktop:armhf (1.74.0-3) ... Selecting previously unselected package libxau6:armhf. Preparing to unpack .../089-libxau6_1%3a1.0.9-1_armhf.deb ... Unpacking libxau6:armhf (1:1.0.9-1) ... Selecting previously unselected package libbsd0:armhf. Preparing to unpack .../090-libbsd0_0.11.7-2_armhf.deb ... Unpacking libbsd0:armhf (0.11.7-2) ... Selecting previously unselected package libxdmcp6:armhf. Preparing to unpack .../091-libxdmcp6_1%3a1.1.2-3_armhf.deb ... Unpacking libxdmcp6:armhf (1:1.1.2-3) ... Selecting previously unselected package libxcb1:armhf. Preparing to unpack .../092-libxcb1_1.15-1_armhf.deb ... Unpacking libxcb1:armhf (1.15-1) ... Selecting previously unselected package libx11-data. Preparing to unpack .../093-libx11-data_2%3a1.8.4-2_all.deb ... Unpacking libx11-data (2:1.8.4-2) ... Selecting previously unselected package libx11-6:armhf. Preparing to unpack .../094-libx11-6_2%3a1.8.4-2_armhf.deb ... Unpacking libx11-6:armhf (2:1.8.4-2) ... Selecting previously unselected package libxext6:armhf. Preparing to unpack .../095-libxext6_2%3a1.3.4-1+b1_armhf.deb ... Unpacking libxext6:armhf (2:1.3.4-1+b1) ... Selecting previously unselected package libxi6:armhf. Preparing to unpack .../096-libxi6_2%3a1.8-1+b1_armhf.deb ... Unpacking libxi6:armhf (2:1.8-1+b1) ... Selecting previously unselected package libatspi2.0-0:armhf. Preparing to unpack .../097-libatspi2.0-0_2.46.0-5_armhf.deb ... Unpacking libatspi2.0-0:armhf (2.46.0-5) ... Selecting previously unselected package gir1.2-atspi-2.0:armhf. Preparing to unpack .../098-gir1.2-atspi-2.0_2.46.0-5_armhf.deb ... Unpacking gir1.2-atspi-2.0:armhf (2.46.0-5) ... Selecting previously unselected package gir1.2-gdkpixbuf-2.0:armhf. Preparing to unpack .../099-gir1.2-gdkpixbuf-2.0_2.42.10+dfsg-1+b1_armhf.deb ... Unpacking gir1.2-gdkpixbuf-2.0:armhf (2.42.10+dfsg-1+b1) ... Selecting previously unselected package gir1.2-harfbuzz-0.0:armhf. Preparing to unpack .../100-gir1.2-harfbuzz-0.0_6.0.0+dfsg-3_armhf.deb ... Unpacking gir1.2-harfbuzz-0.0:armhf (6.0.0+dfsg-3) ... Selecting previously unselected package libfribidi0:armhf. Preparing to unpack .../101-libfribidi0_1.0.8-2.1_armhf.deb ... Unpacking libfribidi0:armhf (1.0.8-2.1) ... Selecting previously unselected package libgraphite2-3:armhf. Preparing to unpack .../102-libgraphite2-3_1.3.14-1_armhf.deb ... Unpacking libgraphite2-3:armhf (1.3.14-1) ... Selecting previously unselected package libharfbuzz0b:armhf. Preparing to unpack .../103-libharfbuzz0b_6.0.0+dfsg-3_armhf.deb ... Unpacking libharfbuzz0b:armhf (6.0.0+dfsg-3) ... Selecting previously unselected package libthai-data. Preparing to unpack .../104-libthai-data_0.1.29-1_all.deb ... Unpacking libthai-data (0.1.29-1) ... Selecting previously unselected package libdatrie1:armhf. Preparing to unpack .../105-libdatrie1_0.2.13-2+b1_armhf.deb ... Unpacking libdatrie1:armhf (0.2.13-2+b1) ... Selecting previously unselected package libthai0:armhf. Preparing to unpack .../106-libthai0_0.1.29-1_armhf.deb ... Unpacking libthai0:armhf (0.1.29-1) ... Selecting previously unselected package libpango-1.0-0:armhf. Preparing to unpack .../107-libpango-1.0-0_1.50.12+ds-1_armhf.deb ... Unpacking libpango-1.0-0:armhf (1.50.12+ds-1) ... Selecting previously unselected package libpixman-1-0:armhf. Preparing to unpack .../108-libpixman-1-0_0.42.2-1_armhf.deb ... Unpacking libpixman-1-0:armhf (0.42.2-1) ... Selecting previously unselected package libxcb-render0:armhf. Preparing to unpack .../109-libxcb-render0_1.15-1_armhf.deb ... Unpacking libxcb-render0:armhf (1.15-1) ... Selecting previously unselected package libxcb-shm0:armhf. Preparing to unpack .../110-libxcb-shm0_1.15-1_armhf.deb ... Unpacking libxcb-shm0:armhf (1.15-1) ... Selecting previously unselected package libxrender1:armhf. Preparing to unpack .../111-libxrender1_1%3a0.9.10-1.1_armhf.deb ... Unpacking libxrender1:armhf (1:0.9.10-1.1) ... Selecting previously unselected package libcairo2:armhf. Preparing to unpack .../112-libcairo2_1.16.0-7_armhf.deb ... Unpacking libcairo2:armhf (1.16.0-7) ... Selecting previously unselected package libpangoft2-1.0-0:armhf. Preparing to unpack .../113-libpangoft2-1.0-0_1.50.12+ds-1_armhf.deb ... Unpacking libpangoft2-1.0-0:armhf (1.50.12+ds-1) ... Selecting previously unselected package libpangocairo-1.0-0:armhf. Preparing to unpack .../114-libpangocairo-1.0-0_1.50.12+ds-1_armhf.deb ... Unpacking libpangocairo-1.0-0:armhf (1.50.12+ds-1) ... Selecting previously unselected package libxft2:armhf. Preparing to unpack .../115-libxft2_2.3.6-1_armhf.deb ... Unpacking libxft2:armhf (2.3.6-1) ... Selecting previously unselected package libpangoxft-1.0-0:armhf. Preparing to unpack .../116-libpangoxft-1.0-0_1.50.12+ds-1_armhf.deb ... Unpacking libpangoxft-1.0-0:armhf (1.50.12+ds-1) ... Selecting previously unselected package gir1.2-pango-1.0:armhf. Preparing to unpack .../117-gir1.2-pango-1.0_1.50.12+ds-1_armhf.deb ... Unpacking gir1.2-pango-1.0:armhf (1.50.12+ds-1) ... Selecting previously unselected package libatk-bridge2.0-0:armhf. Preparing to unpack .../118-libatk-bridge2.0-0_2.46.0-5_armhf.deb ... Unpacking libatk-bridge2.0-0:armhf (2.46.0-5) ... Selecting previously unselected package libcairo-gobject2:armhf. Preparing to unpack .../119-libcairo-gobject2_1.16.0-7_armhf.deb ... Unpacking libcairo-gobject2:armhf (1.16.0-7) ... Selecting previously unselected package liblcms2-2:armhf. Preparing to unpack .../120-liblcms2-2_2.14-2_armhf.deb ... Unpacking liblcms2-2:armhf (2.14-2) ... Selecting previously unselected package libcolord2:armhf. Preparing to unpack .../121-libcolord2_1.4.6-2.2_armhf.deb ... Unpacking libcolord2:armhf (1.4.6-2.2) ... Selecting previously unselected package libavahi-common-data:armhf. Preparing to unpack .../122-libavahi-common-data_0.8-10_armhf.deb ... Unpacking libavahi-common-data:armhf (0.8-10) ... Selecting previously unselected package libavahi-common3:armhf. Preparing to unpack .../123-libavahi-common3_0.8-10_armhf.deb ... Unpacking libavahi-common3:armhf (0.8-10) ... Selecting previously unselected package libavahi-client3:armhf. Preparing to unpack .../124-libavahi-client3_0.8-10_armhf.deb ... Unpacking libavahi-client3:armhf (0.8-10) ... Selecting previously unselected package libcups2:armhf. Preparing to unpack .../125-libcups2_2.4.2-3_armhf.deb ... Unpacking libcups2:armhf (2.4.2-3) ... Selecting previously unselected package libepoxy0:armhf. Preparing to unpack .../126-libepoxy0_1.5.10-1_armhf.deb ... Unpacking libepoxy0:armhf (1.5.10-1) ... Selecting previously unselected package libwayland-client0:armhf. Preparing to unpack .../127-libwayland-client0_1.21.0-1_armhf.deb ... Unpacking libwayland-client0:armhf (1.21.0-1) ... Selecting previously unselected package libwayland-cursor0:armhf. Preparing to unpack .../128-libwayland-cursor0_1.21.0-1_armhf.deb ... Unpacking libwayland-cursor0:armhf (1.21.0-1) ... Selecting previously unselected package libwayland-egl1:armhf. Preparing to unpack .../129-libwayland-egl1_1.21.0-1_armhf.deb ... Unpacking libwayland-egl1:armhf (1.21.0-1) ... Selecting previously unselected package libxcomposite1:armhf. Preparing to unpack .../130-libxcomposite1_1%3a0.4.5-1_armhf.deb ... Unpacking libxcomposite1:armhf (1:0.4.5-1) ... Selecting previously unselected package libxfixes3:armhf. Preparing to unpack .../131-libxfixes3_1%3a6.0.0-2_armhf.deb ... Unpacking libxfixes3:armhf (1:6.0.0-2) ... Selecting previously unselected package libxcursor1:armhf. Preparing to unpack .../132-libxcursor1_1%3a1.2.1-1_armhf.deb ... Unpacking libxcursor1:armhf (1:1.2.1-1) ... Selecting previously unselected package libxdamage1:armhf. Preparing to unpack .../133-libxdamage1_1%3a1.1.6-1_armhf.deb ... Unpacking libxdamage1:armhf (1:1.1.6-1) ... Selecting previously unselected package libxinerama1:armhf. Preparing to unpack .../134-libxinerama1_2%3a1.1.4-3_armhf.deb ... Unpacking libxinerama1:armhf (2:1.1.4-3) ... Selecting previously unselected package xkb-data. Preparing to unpack .../135-xkb-data_2.35.1-1_all.deb ... Unpacking xkb-data (2.35.1-1) ... Selecting previously unselected package libxkbcommon0:armhf. Preparing to unpack .../136-libxkbcommon0_1.5.0-1_armhf.deb ... Unpacking libxkbcommon0:armhf (1.5.0-1) ... Selecting previously unselected package libxrandr2:armhf. Preparing to unpack .../137-libxrandr2_2%3a1.5.2-2+b1_armhf.deb ... Unpacking libxrandr2:armhf (2:1.5.2-2+b1) ... Selecting previously unselected package libgtk-3-common. Preparing to unpack .../138-libgtk-3-common_3.24.37-2_all.deb ... Unpacking libgtk-3-common (3.24.37-2) ... Selecting previously unselected package libgtk-3-0:armhf. Preparing to unpack .../139-libgtk-3-0_3.24.37-2_armhf.deb ... Unpacking libgtk-3-0:armhf (3.24.37-2) ... Selecting previously unselected package gir1.2-gtk-3.0:armhf. Preparing to unpack .../140-gir1.2-gtk-3.0_3.24.37-2_armhf.deb ... Unpacking gir1.2-gtk-3.0:armhf (3.24.37-2) ... Selecting previously unselected package libayatana-ido3-0.4-0:armhf. Preparing to unpack .../141-libayatana-ido3-0.4-0_0.9.3-1_armhf.deb ... Unpacking libayatana-ido3-0.4-0:armhf (0.9.3-1) ... Selecting previously unselected package libayatana-indicator3-7:armhf. Preparing to unpack .../142-libayatana-indicator3-7_0.9.3-1_armhf.deb ... Unpacking libayatana-indicator3-7:armhf (0.9.3-1) ... Selecting previously unselected package libdbusmenu-glib4:armhf. Preparing to unpack .../143-libdbusmenu-glib4_18.10.20180917~bzr492+repack1-3_armhf.deb ... Unpacking libdbusmenu-glib4:armhf (18.10.20180917~bzr492+repack1-3) ... Selecting previously unselected package libdbusmenu-gtk3-4:armhf. Preparing to unpack .../144-libdbusmenu-gtk3-4_18.10.20180917~bzr492+repack1-3_armhf.deb ... Unpacking libdbusmenu-gtk3-4:armhf (18.10.20180917~bzr492+repack1-3) ... Selecting previously unselected package libayatana-appindicator3-1. Preparing to unpack .../145-libayatana-appindicator3-1_0.5.92-1_armhf.deb ... Unpacking libayatana-appindicator3-1 (0.5.92-1) ... Selecting previously unselected package gir1.2-ayatanaappindicator3-0.1. Preparing to unpack .../146-gir1.2-ayatanaappindicator3-0.1_0.5.92-1_armhf.deb ... Unpacking gir1.2-ayatanaappindicator3-0.1 (0.5.92-1) ... Selecting previously unselected package gir1.2-ayatanaido3-0.4:armhf. Preparing to unpack .../147-gir1.2-ayatanaido3-0.4_0.9.3-1_armhf.deb ... Unpacking gir1.2-ayatanaido3-0.4:armhf (0.9.3-1) ... Selecting previously unselected package gir1.2-dbusmenu-glib-0.4:armhf. Preparing to unpack .../148-gir1.2-dbusmenu-glib-0.4_18.10.20180917~bzr492+repack1-3_armhf.deb ... Unpacking gir1.2-dbusmenu-glib-0.4:armhf (18.10.20180917~bzr492+repack1-3) ... Selecting previously unselected package gir1.2-gconf-2.0. Preparing to unpack .../149-gir1.2-gconf-2.0_3.2.6-8_armhf.deb ... Unpacking gir1.2-gconf-2.0 (3.2.6-8) ... Selecting previously unselected package libdw1:armhf. Preparing to unpack .../150-libdw1_0.188-2.1_armhf.deb ... Unpacking libdw1:armhf (0.188-2.1) ... Selecting previously unselected package libunwind8:armhf. Preparing to unpack .../151-libunwind8_1.6.2-3_armhf.deb ... Unpacking libunwind8:armhf (1.6.2-3) ... Selecting previously unselected package libcap2-bin. Preparing to unpack .../152-libcap2-bin_1%3a2.66-3_armhf.deb ... Unpacking libcap2-bin (1:2.66-3) ... Selecting previously unselected package libgstreamer1.0-0:armhf. Preparing to unpack .../153-libgstreamer1.0-0_1.22.0-2_armhf.deb ... Unpacking libgstreamer1.0-0:armhf (1.22.0-2) ... Selecting previously unselected package gir1.2-gstreamer-1.0:armhf. Preparing to unpack .../154-gir1.2-gstreamer-1.0_1.22.0-2_armhf.deb ... Unpacking gir1.2-gstreamer-1.0:armhf (1.22.0-2) ... Selecting previously unselected package libgtk2.0-common. Preparing to unpack .../155-libgtk2.0-common_2.24.33-2_all.deb ... Unpacking libgtk2.0-common (2.24.33-2) ... Selecting previously unselected package librsvg2-2:armhf. Preparing to unpack .../156-librsvg2-2_2.54.5+dfsg-1_armhf.deb ... Unpacking librsvg2-2:armhf (2.54.5+dfsg-1) ... Selecting previously unselected package librsvg2-common:armhf. Preparing to unpack .../157-librsvg2-common_2.54.5+dfsg-1_armhf.deb ... Unpacking librsvg2-common:armhf (2.54.5+dfsg-1) ... Selecting previously unselected package gnome-icon-theme. Preparing to unpack .../158-gnome-icon-theme_3.12.0-5_all.deb ... Unpacking gnome-icon-theme (3.12.0-5) ... Selecting previously unselected package libgtk2.0-0:armhf. Preparing to unpack .../159-libgtk2.0-0_2.24.33-2_armhf.deb ... Unpacking libgtk2.0-0:armhf (2.24.33-2) ... Selecting previously unselected package gir1.2-gtk-2.0:armhf. Preparing to unpack .../160-gir1.2-gtk-2.0_2.24.33-2_armhf.deb ... Unpacking gir1.2-gtk-2.0:armhf (2.24.33-2) ... Selecting previously unselected package libnotify4:armhf. Preparing to unpack .../161-libnotify4_0.8.1-1_armhf.deb ... Unpacking libnotify4:armhf (0.8.1-1) ... Selecting previously unselected package gir1.2-notify-0.7:armhf. Preparing to unpack .../162-gir1.2-notify-0.7_0.8.1-1_armhf.deb ... Unpacking gir1.2-notify-0.7:armhf (0.8.1-1) ... Selecting previously unselected package libpkgconf3:armhf. Preparing to unpack .../163-libpkgconf3_1.8.1-1_armhf.deb ... Unpacking libpkgconf3:armhf (1.8.1-1) ... Selecting previously unselected package pkgconf-bin. Preparing to unpack .../164-pkgconf-bin_1.8.1-1_armhf.deb ... Unpacking pkgconf-bin (1.8.1-1) ... Selecting previously unselected package pkgconf:armhf. Preparing to unpack .../165-pkgconf_1.8.1-1_armhf.deb ... Unpacking pkgconf:armhf (1.8.1-1) ... Selecting previously unselected package pkg-config:armhf. Preparing to unpack .../166-pkg-config_1.8.1-1_armhf.deb ... Unpacking pkg-config:armhf (1.8.1-1) ... Selecting previously unselected package libregexp-ipv6-perl. Preparing to unpack .../167-libregexp-ipv6-perl_0.03-3_all.deb ... Unpacking libregexp-ipv6-perl (0.03-3) ... Selecting previously unselected package liburi-perl. Preparing to unpack .../168-liburi-perl_5.17-1_all.deb ... Unpacking liburi-perl (5.17-1) ... Selecting previously unselected package libencode-locale-perl. Preparing to unpack .../169-libencode-locale-perl_1.05-3_all.deb ... Unpacking libencode-locale-perl (1.05-3) ... Selecting previously unselected package libtimedate-perl. Preparing to unpack .../170-libtimedate-perl_2.3300-2_all.deb ... Unpacking libtimedate-perl (2.3300-2) ... Selecting previously unselected package libhttp-date-perl. Preparing to unpack .../171-libhttp-date-perl_6.05-2_all.deb ... Unpacking libhttp-date-perl (6.05-2) ... Selecting previously unselected package libfile-listing-perl. Preparing to unpack .../172-libfile-listing-perl_6.15-1_all.deb ... Unpacking libfile-listing-perl (6.15-1) ... Selecting previously unselected package libhtml-tagset-perl. Preparing to unpack .../173-libhtml-tagset-perl_3.20-6_all.deb ... Unpacking libhtml-tagset-perl (3.20-6) ... Selecting previously unselected package libhtml-parser-perl:armhf. Preparing to unpack .../174-libhtml-parser-perl_3.81-1_armhf.deb ... Unpacking libhtml-parser-perl:armhf (3.81-1) ... Selecting previously unselected package libhtml-tree-perl. Preparing to unpack .../175-libhtml-tree-perl_5.07-3_all.deb ... Unpacking libhtml-tree-perl (5.07-3) ... Selecting previously unselected package libclone-perl:armhf. Preparing to unpack .../176-libclone-perl_0.46-1_armhf.deb ... Unpacking libclone-perl:armhf (0.46-1) ... Selecting previously unselected package libio-html-perl. Preparing to unpack .../177-libio-html-perl_1.004-3_all.deb ... Unpacking libio-html-perl (1.004-3) ... Selecting previously unselected package liblwp-mediatypes-perl. Preparing to unpack .../178-liblwp-mediatypes-perl_6.04-2_all.deb ... Unpacking liblwp-mediatypes-perl (6.04-2) ... Selecting previously unselected package libhttp-message-perl. Preparing to unpack .../179-libhttp-message-perl_6.44-1_all.deb ... Unpacking libhttp-message-perl (6.44-1) ... Selecting previously unselected package libhttp-cookies-perl. Preparing to unpack .../180-libhttp-cookies-perl_6.10-1_all.deb ... Unpacking libhttp-cookies-perl (6.10-1) ... Selecting previously unselected package libhttp-negotiate-perl. Preparing to unpack .../181-libhttp-negotiate-perl_6.01-2_all.deb ... Unpacking libhttp-negotiate-perl (6.01-2) ... Selecting previously unselected package perl-openssl-defaults:armhf. Preparing to unpack .../182-perl-openssl-defaults_7+b1_armhf.deb ... Unpacking perl-openssl-defaults:armhf (7+b1) ... Selecting previously unselected package libnet-ssleay-perl:armhf. Preparing to unpack .../183-libnet-ssleay-perl_1.92-2+b1_armhf.deb ... Unpacking libnet-ssleay-perl:armhf (1.92-2+b1) ... Selecting previously unselected package libio-socket-ssl-perl. Preparing to unpack .../184-libio-socket-ssl-perl_2.081-2_all.deb ... Unpacking libio-socket-ssl-perl (2.081-2) ... Selecting previously unselected package libnet-http-perl. Preparing to unpack .../185-libnet-http-perl_6.22-1_all.deb ... Unpacking libnet-http-perl (6.22-1) ... Selecting previously unselected package liblwp-protocol-https-perl. Preparing to unpack .../186-liblwp-protocol-https-perl_6.10-1_all.deb ... Unpacking liblwp-protocol-https-perl (6.10-1) ... Selecting previously unselected package libtry-tiny-perl. Preparing to unpack .../187-libtry-tiny-perl_0.31-2_all.deb ... Unpacking libtry-tiny-perl (0.31-2) ... Selecting previously unselected package libwww-robotrules-perl. Preparing to unpack .../188-libwww-robotrules-perl_6.02-1_all.deb ... Unpacking libwww-robotrules-perl (6.02-1) ... Selecting previously unselected package libwww-perl. Preparing to unpack .../189-libwww-perl_6.68-1_all.deb ... Unpacking libwww-perl (6.68-1) ... Selecting previously unselected package libxml-parser-perl. Preparing to unpack .../190-libxml-parser-perl_2.46-4_armhf.deb ... Unpacking libxml-parser-perl (2.46-4) ... Selecting previously unselected package intltool. Preparing to unpack .../191-intltool_0.51.0-6_all.deb ... Unpacking intltool (0.51.0-6) ... Selecting previously unselected package gnome-common. Preparing to unpack .../192-gnome-common_3.18.0-4_all.deb ... Unpacking gnome-common (3.18.0-4) ... Selecting previously unselected package icu-devtools. Preparing to unpack .../193-icu-devtools_72.1-3_armhf.deb ... Unpacking icu-devtools (72.1-3) ... Selecting previously unselected package libffi-dev:armhf. Preparing to unpack .../194-libffi-dev_3.4.4-1_armhf.deb ... Unpacking libffi-dev:armhf (3.4.4-1) ... Selecting previously unselected package libglib2.0-data. Preparing to unpack .../195-libglib2.0-data_2.74.6-2_all.deb ... Unpacking libglib2.0-data (2.74.6-2) ... Selecting previously unselected package libglib2.0-bin. Preparing to unpack .../196-libglib2.0-bin_2.74.6-2_armhf.deb ... Unpacking libglib2.0-bin (2.74.6-2) ... Selecting previously unselected package python3-lib2to3. Preparing to unpack .../197-python3-lib2to3_3.11.2-3_all.deb ... Unpacking python3-lib2to3 (3.11.2-3) ... Selecting previously unselected package python3-distutils. Preparing to unpack .../198-python3-distutils_3.11.2-3_all.deb ... Unpacking python3-distutils (3.11.2-3) ... Selecting previously unselected package libglib2.0-dev-bin. Preparing to unpack .../199-libglib2.0-dev-bin_2.74.6-2_armhf.deb ... Unpacking libglib2.0-dev-bin (2.74.6-2) ... Selecting previously unselected package uuid-dev:armhf. Preparing to unpack .../200-uuid-dev_2.38.1-5+b1_armhf.deb ... Unpacking uuid-dev:armhf (2.38.1-5+b1) ... Selecting previously unselected package libblkid-dev:armhf. Preparing to unpack .../201-libblkid-dev_2.38.1-5+b1_armhf.deb ... Unpacking libblkid-dev:armhf (2.38.1-5+b1) ... Selecting previously unselected package libsepol-dev:armhf. Preparing to unpack .../202-libsepol-dev_3.4-2_armhf.deb ... Unpacking libsepol-dev:armhf (3.4-2) ... Selecting previously unselected package libpcre2-16-0:armhf. Preparing to unpack .../203-libpcre2-16-0_10.42-1_armhf.deb ... Unpacking libpcre2-16-0:armhf (10.42-1) ... Selecting previously unselected package libpcre2-32-0:armhf. Preparing to unpack .../204-libpcre2-32-0_10.42-1_armhf.deb ... Unpacking libpcre2-32-0:armhf (10.42-1) ... Selecting previously unselected package libpcre2-posix3:armhf. Preparing to unpack .../205-libpcre2-posix3_10.42-1_armhf.deb ... Unpacking libpcre2-posix3:armhf (10.42-1) ... Selecting previously unselected package libpcre2-dev:armhf. Preparing to unpack .../206-libpcre2-dev_10.42-1_armhf.deb ... Unpacking libpcre2-dev:armhf (10.42-1) ... Selecting previously unselected package libselinux1-dev:armhf. Preparing to unpack .../207-libselinux1-dev_3.4-1+b5_armhf.deb ... Unpacking libselinux1-dev:armhf (3.4-1+b5) ... Selecting previously unselected package libmount-dev:armhf. Preparing to unpack .../208-libmount-dev_2.38.1-5+b1_armhf.deb ... Unpacking libmount-dev:armhf (2.38.1-5+b1) ... Selecting previously unselected package zlib1g-dev:armhf. Preparing to unpack .../209-zlib1g-dev_1%3a1.2.13.dfsg-1_armhf.deb ... Unpacking zlib1g-dev:armhf (1:1.2.13.dfsg-1) ... Selecting previously unselected package libglib2.0-dev:armhf. Preparing to unpack .../210-libglib2.0-dev_2.74.6-2_armhf.deb ... Unpacking libglib2.0-dev:armhf (2.74.6-2) ... Selecting previously unselected package libatk1.0-dev:armhf. Preparing to unpack .../211-libatk1.0-dev_2.46.0-5_armhf.deb ... Unpacking libatk1.0-dev:armhf (2.46.0-5) ... Selecting previously unselected package xml-core. Preparing to unpack .../212-xml-core_0.18+nmu1_all.deb ... Unpacking xml-core (0.18+nmu1) ... Selecting previously unselected package libdbus-1-dev:armhf. Preparing to unpack .../213-libdbus-1-dev_1.14.6-1_armhf.deb ... Unpacking libdbus-1-dev:armhf (1.14.6-1) ... Selecting previously unselected package x11-common. Preparing to unpack .../214-x11-common_1%3a7.7+23_all.deb ... Unpacking x11-common (1:7.7+23) ... Selecting previously unselected package libxtst6:armhf. Preparing to unpack .../215-libxtst6_2%3a1.2.3-1.1_armhf.deb ... Unpacking libxtst6:armhf (2:1.2.3-1.1) ... Selecting previously unselected package xorg-sgml-doctools. Preparing to unpack .../216-xorg-sgml-doctools_1%3a1.11-1.1_all.deb ... Unpacking xorg-sgml-doctools (1:1.11-1.1) ... Selecting previously unselected package x11proto-dev. Preparing to unpack .../217-x11proto-dev_2022.1-1_all.deb ... Unpacking x11proto-dev (2022.1-1) ... Selecting previously unselected package libxau-dev:armhf. Preparing to unpack .../218-libxau-dev_1%3a1.0.9-1_armhf.deb ... Unpacking libxau-dev:armhf (1:1.0.9-1) ... Selecting previously unselected package libxdmcp-dev:armhf. Preparing to unpack .../219-libxdmcp-dev_1%3a1.1.2-3_armhf.deb ... Unpacking libxdmcp-dev:armhf (1:1.1.2-3) ... Selecting previously unselected package xtrans-dev. Preparing to unpack .../220-xtrans-dev_1.4.0-1_all.deb ... Unpacking xtrans-dev (1.4.0-1) ... Selecting previously unselected package libpthread-stubs0-dev:armhf. Preparing to unpack .../221-libpthread-stubs0-dev_0.4-1_armhf.deb ... Unpacking libpthread-stubs0-dev:armhf (0.4-1) ... Selecting previously unselected package libxcb1-dev:armhf. Preparing to unpack .../222-libxcb1-dev_1.15-1_armhf.deb ... Unpacking libxcb1-dev:armhf (1.15-1) ... Selecting previously unselected package libx11-dev:armhf. Preparing to unpack .../223-libx11-dev_2%3a1.8.4-2_armhf.deb ... Unpacking libx11-dev:armhf (2:1.8.4-2) ... Selecting previously unselected package libxext-dev:armhf. Preparing to unpack .../224-libxext-dev_2%3a1.3.4-1+b1_armhf.deb ... Unpacking libxext-dev:armhf (2:1.3.4-1+b1) ... Selecting previously unselected package libxfixes-dev:armhf. Preparing to unpack .../225-libxfixes-dev_1%3a6.0.0-2_armhf.deb ... Unpacking libxfixes-dev:armhf (1:6.0.0-2) ... Selecting previously unselected package libxi-dev:armhf. Preparing to unpack .../226-libxi-dev_2%3a1.8-1+b1_armhf.deb ... Unpacking libxi-dev:armhf (2:1.8-1+b1) ... Selecting previously unselected package libxtst-dev:armhf. Preparing to unpack .../227-libxtst-dev_2%3a1.2.3-1.1_armhf.deb ... Unpacking libxtst-dev:armhf (2:1.2.3-1.1) ... Selecting previously unselected package libatspi2.0-dev:armhf. Preparing to unpack .../228-libatspi2.0-dev_2.46.0-5_armhf.deb ... Unpacking libatspi2.0-dev:armhf (2.46.0-5) ... Selecting previously unselected package libatk-bridge2.0-dev:armhf. Preparing to unpack .../229-libatk-bridge2.0-dev_2.46.0-5_armhf.deb ... Unpacking libatk-bridge2.0-dev:armhf (2.46.0-5) ... Selecting previously unselected package liblzo2-2:armhf. Preparing to unpack .../230-liblzo2-2_2.10-2_armhf.deb ... Unpacking liblzo2-2:armhf (2.10-2) ... Selecting previously unselected package libcairo-script-interpreter2:armhf. Preparing to unpack .../231-libcairo-script-interpreter2_1.16.0-7_armhf.deb ... Unpacking libcairo-script-interpreter2:armhf (1.16.0-7) ... Selecting previously unselected package libexpat1-dev:armhf. Preparing to unpack .../232-libexpat1-dev_2.5.0-1_armhf.deb ... Unpacking libexpat1-dev:armhf (2.5.0-1) ... Selecting previously unselected package libbrotli-dev:armhf. Preparing to unpack .../233-libbrotli-dev_1.0.9-2+b6_armhf.deb ... Unpacking libbrotli-dev:armhf (1.0.9-2+b6) ... Selecting previously unselected package libpng-dev:armhf. Preparing to unpack .../234-libpng-dev_1.6.39-2_armhf.deb ... Unpacking libpng-dev:armhf (1.6.39-2) ... Selecting previously unselected package libfreetype-dev:armhf. Preparing to unpack .../235-libfreetype-dev_2.12.1+dfsg-5_armhf.deb ... Unpacking libfreetype-dev:armhf (2.12.1+dfsg-5) ... Selecting previously unselected package libfontconfig-dev:armhf. Preparing to unpack .../236-libfontconfig-dev_2.14.1-4_armhf.deb ... Unpacking libfontconfig-dev:armhf (2.14.1-4) ... Selecting previously unselected package libpixman-1-dev:armhf. Preparing to unpack .../237-libpixman-1-dev_0.42.2-1_armhf.deb ... Unpacking libpixman-1-dev:armhf (0.42.2-1) ... Selecting previously unselected package libice6:armhf. Preparing to unpack .../238-libice6_2%3a1.0.10-1_armhf.deb ... Unpacking libice6:armhf (2:1.0.10-1) ... Selecting previously unselected package libsm6:armhf. Preparing to unpack .../239-libsm6_2%3a1.2.3-1_armhf.deb ... Unpacking libsm6:armhf (2:1.2.3-1) ... Selecting previously unselected package libice-dev:armhf. Preparing to unpack .../240-libice-dev_2%3a1.0.10-1_armhf.deb ... Unpacking libice-dev:armhf (2:1.0.10-1) ... Selecting previously unselected package libsm-dev:armhf. Preparing to unpack .../241-libsm-dev_2%3a1.2.3-1_armhf.deb ... Unpacking libsm-dev:armhf (2:1.2.3-1) ... Selecting previously unselected package libxcb-render0-dev:armhf. Preparing to unpack .../242-libxcb-render0-dev_1.15-1_armhf.deb ... Unpacking libxcb-render0-dev:armhf (1.15-1) ... Selecting previously unselected package libxcb-shm0-dev:armhf. Preparing to unpack .../243-libxcb-shm0-dev_1.15-1_armhf.deb ... Unpacking libxcb-shm0-dev:armhf (1.15-1) ... Selecting previously unselected package libxrender-dev:armhf. Preparing to unpack .../244-libxrender-dev_1%3a0.9.10-1.1_armhf.deb ... Unpacking libxrender-dev:armhf (1:0.9.10-1.1) ... Selecting previously unselected package libcairo2-dev:armhf. Preparing to unpack .../245-libcairo2-dev_1.16.0-7_armhf.deb ... Unpacking libcairo2-dev:armhf (1.16.0-7) ... Selecting previously unselected package libglvnd0:armhf. Preparing to unpack .../246-libglvnd0_1.6.0-1_armhf.deb ... Unpacking libglvnd0:armhf (1.6.0-1) ... Selecting previously unselected package libdrm-common. Preparing to unpack .../247-libdrm-common_2.4.114-1_all.deb ... Unpacking libdrm-common (2.4.114-1) ... Selecting previously unselected package libdrm2:armhf. Preparing to unpack .../248-libdrm2_2.4.114-1+b1_armhf.deb ... Unpacking libdrm2:armhf (2.4.114-1+b1) ... Selecting previously unselected package libwayland-server0:armhf. Preparing to unpack .../249-libwayland-server0_1.21.0-1_armhf.deb ... Unpacking libwayland-server0:armhf (1.21.0-1) ... Selecting previously unselected package libgbm1:armhf. Preparing to unpack .../250-libgbm1_22.3.6-1+deb12u1_armhf.deb ... Unpacking libgbm1:armhf (22.3.6-1+deb12u1) ... Selecting previously unselected package libglapi-mesa:armhf. Preparing to unpack .../251-libglapi-mesa_22.3.6-1+deb12u1_armhf.deb ... Unpacking libglapi-mesa:armhf (22.3.6-1+deb12u1) ... Selecting previously unselected package libx11-xcb1:armhf. Preparing to unpack .../252-libx11-xcb1_2%3a1.8.4-2_armhf.deb ... Unpacking libx11-xcb1:armhf (2:1.8.4-2) ... Selecting previously unselected package libxcb-dri2-0:armhf. Preparing to unpack .../253-libxcb-dri2-0_1.15-1_armhf.deb ... Unpacking libxcb-dri2-0:armhf (1.15-1) ... Selecting previously unselected package libxcb-dri3-0:armhf. Preparing to unpack .../254-libxcb-dri3-0_1.15-1_armhf.deb ... Unpacking libxcb-dri3-0:armhf (1.15-1) ... Selecting previously unselected package libxcb-present0:armhf. Preparing to unpack .../255-libxcb-present0_1.15-1_armhf.deb ... Unpacking libxcb-present0:armhf (1.15-1) ... Selecting previously unselected package libxcb-randr0:armhf. Preparing to unpack .../256-libxcb-randr0_1.15-1_armhf.deb ... Unpacking libxcb-randr0:armhf (1.15-1) ... Selecting previously unselected package libxcb-sync1:armhf. Preparing to unpack .../257-libxcb-sync1_1.15-1_armhf.deb ... Unpacking libxcb-sync1:armhf (1.15-1) ... Selecting previously unselected package libxcb-xfixes0:armhf. Preparing to unpack .../258-libxcb-xfixes0_1.15-1_armhf.deb ... Unpacking libxcb-xfixes0:armhf (1.15-1) ... Selecting previously unselected package libxshmfence1:armhf. Preparing to unpack .../259-libxshmfence1_1.3-1_armhf.deb ... Unpacking libxshmfence1:armhf (1.3-1) ... Selecting previously unselected package libegl-mesa0:armhf. Preparing to unpack .../260-libegl-mesa0_22.3.6-1+deb12u1_armhf.deb ... Unpacking libegl-mesa0:armhf (22.3.6-1+deb12u1) ... Selecting previously unselected package libegl1:armhf. Preparing to unpack .../261-libegl1_1.6.0-1_armhf.deb ... Unpacking libegl1:armhf (1.6.0-1) ... Selecting previously unselected package libxcb-glx0:armhf. Preparing to unpack .../262-libxcb-glx0_1.15-1_armhf.deb ... Unpacking libxcb-glx0:armhf (1.15-1) ... Selecting previously unselected package libxxf86vm1:armhf. Preparing to unpack .../263-libxxf86vm1_1%3a1.1.4-1+b2_armhf.deb ... Unpacking libxxf86vm1:armhf (1:1.1.4-1+b2) ... Selecting previously unselected package libdrm-amdgpu1:armhf. Preparing to unpack .../264-libdrm-amdgpu1_2.4.114-1+b1_armhf.deb ... Unpacking libdrm-amdgpu1:armhf (2.4.114-1+b1) ... Selecting previously unselected package libdrm-nouveau2:armhf. Preparing to unpack .../265-libdrm-nouveau2_2.4.114-1+b1_armhf.deb ... Unpacking libdrm-nouveau2:armhf (2.4.114-1+b1) ... Selecting previously unselected package libdrm-radeon1:armhf. Preparing to unpack .../266-libdrm-radeon1_2.4.114-1+b1_armhf.deb ... Unpacking libdrm-radeon1:armhf (2.4.114-1+b1) ... Selecting previously unselected package libedit2:armhf. Preparing to unpack .../267-libedit2_3.1-20221030-2_armhf.deb ... Unpacking libedit2:armhf (3.1-20221030-2) ... Selecting previously unselected package libz3-4:armhf. Preparing to unpack .../268-libz3-4_4.8.12-3.1_armhf.deb ... Unpacking libz3-4:armhf (4.8.12-3.1) ... Selecting previously unselected package libllvm15:armhf. Preparing to unpack .../269-libllvm15_1%3a15.0.6-4+b1_armhf.deb ... Unpacking libllvm15:armhf (1:15.0.6-4+b1) ... Selecting previously unselected package libsensors-config. Preparing to unpack .../270-libsensors-config_1%3a3.6.0-7.1_all.deb ... Unpacking libsensors-config (1:3.6.0-7.1) ... Selecting previously unselected package libsensors5:armhf. Preparing to unpack .../271-libsensors5_1%3a3.6.0-7.1_armhf.deb ... Unpacking libsensors5:armhf (1:3.6.0-7.1) ... Selecting previously unselected package libgl1-mesa-dri:armhf. Preparing to unpack .../272-libgl1-mesa-dri_22.3.6-1+deb12u1_armhf.deb ... Unpacking libgl1-mesa-dri:armhf (22.3.6-1+deb12u1) ... Selecting previously unselected package libglx-mesa0:armhf. Preparing to unpack .../273-libglx-mesa0_22.3.6-1+deb12u1_armhf.deb ... Unpacking libglx-mesa0:armhf (22.3.6-1+deb12u1) ... Selecting previously unselected package libglx0:armhf. Preparing to unpack .../274-libglx0_1.6.0-1_armhf.deb ... Unpacking libglx0:armhf (1.6.0-1) ... Selecting previously unselected package libgl1:armhf. Preparing to unpack .../275-libgl1_1.6.0-1_armhf.deb ... Unpacking libgl1:armhf (1.6.0-1) ... Selecting previously unselected package libglx-dev:armhf. Preparing to unpack .../276-libglx-dev_1.6.0-1_armhf.deb ... Unpacking libglx-dev:armhf (1.6.0-1) ... Selecting previously unselected package libgl-dev:armhf. Preparing to unpack .../277-libgl-dev_1.6.0-1_armhf.deb ... Unpacking libgl-dev:armhf (1.6.0-1) ... Selecting previously unselected package libegl-dev:armhf. Preparing to unpack .../278-libegl-dev_1.6.0-1_armhf.deb ... Unpacking libegl-dev:armhf (1.6.0-1) ... Selecting previously unselected package libglvnd-core-dev:armhf. Preparing to unpack .../279-libglvnd-core-dev_1.6.0-1_armhf.deb ... Unpacking libglvnd-core-dev:armhf (1.6.0-1) ... Selecting previously unselected package libgles1:armhf. Preparing to unpack .../280-libgles1_1.6.0-1_armhf.deb ... Unpacking libgles1:armhf (1.6.0-1) ... Selecting previously unselected package libgles2:armhf. Preparing to unpack .../281-libgles2_1.6.0-1_armhf.deb ... Unpacking libgles2:armhf (1.6.0-1) ... Selecting previously unselected package libgles-dev:armhf. Preparing to unpack .../282-libgles-dev_1.6.0-1_armhf.deb ... Unpacking libgles-dev:armhf (1.6.0-1) ... Selecting previously unselected package libopengl0:armhf. Preparing to unpack .../283-libopengl0_1.6.0-1_armhf.deb ... Unpacking libopengl0:armhf (1.6.0-1) ... Selecting previously unselected package libopengl-dev:armhf. Preparing to unpack .../284-libopengl-dev_1.6.0-1_armhf.deb ... Unpacking libopengl-dev:armhf (1.6.0-1) ... Selecting previously unselected package libglvnd-dev:armhf. Preparing to unpack .../285-libglvnd-dev_1.6.0-1_armhf.deb ... Unpacking libglvnd-dev:armhf (1.6.0-1) ... Selecting previously unselected package libegl1-mesa-dev:armhf. Preparing to unpack .../286-libegl1-mesa-dev_22.3.6-1+deb12u1_armhf.deb ... Unpacking libegl1-mesa-dev:armhf (22.3.6-1+deb12u1) ... Selecting previously unselected package libepoxy-dev:armhf. Preparing to unpack .../287-libepoxy-dev_1.5.10-1_armhf.deb ... Unpacking libepoxy-dev:armhf (1.5.10-1) ... Selecting previously unselected package libfribidi-dev:armhf. Preparing to unpack .../288-libfribidi-dev_1.0.8-2.1_armhf.deb ... Unpacking libfribidi-dev:armhf (1.0.8-2.1) ... Selecting previously unselected package libgdk-pixbuf2.0-bin. Preparing to unpack .../289-libgdk-pixbuf2.0-bin_2.42.10+dfsg-1+b1_armhf.deb ... Unpacking libgdk-pixbuf2.0-bin (2.42.10+dfsg-1+b1) ... Selecting previously unselected package libjpeg62-turbo-dev:armhf. Preparing to unpack .../290-libjpeg62-turbo-dev_1%3a2.1.5-2_armhf.deb ... Unpacking libjpeg62-turbo-dev:armhf (1:2.1.5-2) ... Selecting previously unselected package libjpeg-dev:armhf. Preparing to unpack .../291-libjpeg-dev_1%3a2.1.5-2_armhf.deb ... Unpacking libjpeg-dev:armhf (1:2.1.5-2) ... Selecting previously unselected package libjbig-dev:armhf. Preparing to unpack .../292-libjbig-dev_2.1-6.1_armhf.deb ... Unpacking libjbig-dev:armhf (2.1-6.1) ... Selecting previously unselected package liblzma-dev:armhf. Preparing to unpack .../293-liblzma-dev_5.4.1-0.2_armhf.deb ... Unpacking liblzma-dev:armhf (5.4.1-0.2) ... Selecting previously unselected package libzstd-dev:armhf. Preparing to unpack .../294-libzstd-dev_1.5.4+dfsg2-5_armhf.deb ... Unpacking libzstd-dev:armhf (1.5.4+dfsg2-5) ... Selecting previously unselected package libwebpmux3:armhf. Preparing to unpack .../295-libwebpmux3_1.2.4-0.1_armhf.deb ... Unpacking libwebpmux3:armhf (1.2.4-0.1) ... Selecting previously unselected package libwebpdemux2:armhf. Preparing to unpack .../296-libwebpdemux2_1.2.4-0.1_armhf.deb ... Unpacking libwebpdemux2:armhf (1.2.4-0.1) ... Selecting previously unselected package libwebp-dev:armhf. Preparing to unpack .../297-libwebp-dev_1.2.4-0.1_armhf.deb ... Unpacking libwebp-dev:armhf (1.2.4-0.1) ... Selecting previously unselected package libtiffxx6:armhf. Preparing to unpack .../298-libtiffxx6_4.5.0-5_armhf.deb ... Unpacking libtiffxx6:armhf (4.5.0-5) ... Selecting previously unselected package libdeflate-dev:armhf. Preparing to unpack .../299-libdeflate-dev_1.14-1_armhf.deb ... Unpacking libdeflate-dev:armhf (1.14-1) ... Selecting previously unselected package liblerc-dev:armhf. Preparing to unpack .../300-liblerc-dev_4.0.0+ds-2_armhf.deb ... Unpacking liblerc-dev:armhf (4.0.0+ds-2) ... Selecting previously unselected package libtiff-dev:armhf. Preparing to unpack .../301-libtiff-dev_4.5.0-5_armhf.deb ... Unpacking libtiff-dev:armhf (4.5.0-5) ... Selecting previously unselected package libgdk-pixbuf-2.0-dev:armhf. Preparing to unpack .../302-libgdk-pixbuf-2.0-dev_2.42.10+dfsg-1+b1_armhf.deb ... Unpacking libgdk-pixbuf-2.0-dev:armhf (2.42.10+dfsg-1+b1) ... Selecting previously unselected package libharfbuzz-icu0:armhf. Preparing to unpack .../303-libharfbuzz-icu0_6.0.0+dfsg-3_armhf.deb ... Unpacking libharfbuzz-icu0:armhf (6.0.0+dfsg-3) ... Selecting previously unselected package libharfbuzz-gobject0:armhf. Preparing to unpack .../304-libharfbuzz-gobject0_6.0.0+dfsg-3_armhf.deb ... Unpacking libharfbuzz-gobject0:armhf (6.0.0+dfsg-3) ... Selecting previously unselected package libharfbuzz-subset0:armhf. Preparing to unpack .../305-libharfbuzz-subset0_6.0.0+dfsg-3_armhf.deb ... Unpacking libharfbuzz-subset0:armhf (6.0.0+dfsg-3) ... Selecting previously unselected package libgraphite2-dev:armhf. Preparing to unpack .../306-libgraphite2-dev_1.3.14-1_armhf.deb ... Unpacking libgraphite2-dev:armhf (1.3.14-1) ... Selecting previously unselected package libicu-dev:armhf. Preparing to unpack .../307-libicu-dev_72.1-3_armhf.deb ... Unpacking libicu-dev:armhf (72.1-3) ... Selecting previously unselected package libharfbuzz-dev:armhf. Preparing to unpack .../308-libharfbuzz-dev_6.0.0+dfsg-3_armhf.deb ... Unpacking libharfbuzz-dev:armhf (6.0.0+dfsg-3) ... Selecting previously unselected package libdatrie-dev:armhf. Preparing to unpack .../309-libdatrie-dev_0.2.13-2+b1_armhf.deb ... Unpacking libdatrie-dev:armhf (0.2.13-2+b1) ... Selecting previously unselected package libthai-dev:armhf. Preparing to unpack .../310-libthai-dev_0.1.29-1_armhf.deb ... Unpacking libthai-dev:armhf (0.1.29-1) ... Selecting previously unselected package libxft-dev:armhf. Preparing to unpack .../311-libxft-dev_2.3.6-1_armhf.deb ... Unpacking libxft-dev:armhf (2.3.6-1) ... Selecting previously unselected package pango1.0-tools. Preparing to unpack .../312-pango1.0-tools_1.50.12+ds-1_armhf.deb ... Unpacking pango1.0-tools (1.50.12+ds-1) ... Selecting previously unselected package libpango1.0-dev:armhf. Preparing to unpack .../313-libpango1.0-dev_1.50.12+ds-1_armhf.deb ... Unpacking libpango1.0-dev:armhf (1.50.12+ds-1) ... Selecting previously unselected package libwayland-bin. Preparing to unpack .../314-libwayland-bin_1.21.0-1_armhf.deb ... Unpacking libwayland-bin (1.21.0-1) ... Selecting previously unselected package libwayland-dev:armhf. Preparing to unpack .../315-libwayland-dev_1.21.0-1_armhf.deb ... Unpacking libwayland-dev:armhf (1.21.0-1) ... Selecting previously unselected package libxcomposite-dev:armhf. Preparing to unpack .../316-libxcomposite-dev_1%3a0.4.5-1_armhf.deb ... Unpacking libxcomposite-dev:armhf (1:0.4.5-1) ... Selecting previously unselected package libxcursor-dev:armhf. Preparing to unpack .../317-libxcursor-dev_1%3a1.2.1-1_armhf.deb ... Unpacking libxcursor-dev:armhf (1:1.2.1-1) ... Selecting previously unselected package libxdamage-dev:armhf. Preparing to unpack .../318-libxdamage-dev_1%3a1.1.6-1_armhf.deb ... Unpacking libxdamage-dev:armhf (1:1.1.6-1) ... Selecting previously unselected package libxinerama-dev:armhf. Preparing to unpack .../319-libxinerama-dev_2%3a1.1.4-3_armhf.deb ... Unpacking libxinerama-dev:armhf (2:1.1.4-3) ... Selecting previously unselected package libxkbcommon-dev:armhf. Preparing to unpack .../320-libxkbcommon-dev_1.5.0-1_armhf.deb ... Unpacking libxkbcommon-dev:armhf (1.5.0-1) ... Selecting previously unselected package libxrandr-dev:armhf. Preparing to unpack .../321-libxrandr-dev_2%3a1.5.2-2+b1_armhf.deb ... Unpacking libxrandr-dev:armhf (2:1.5.2-2+b1) ... Selecting previously unselected package wayland-protocols. Preparing to unpack .../322-wayland-protocols_1.31-1_all.deb ... Unpacking wayland-protocols (1.31-1) ... Selecting previously unselected package libgtk-3-dev:armhf. Preparing to unpack .../323-libgtk-3-dev_3.24.37-2_armhf.deb ... Unpacking libgtk-3-dev:armhf (3.24.37-2) ... Selecting previously unselected package libayatana-ido3-dev. Preparing to unpack .../324-libayatana-ido3-dev_0.9.3-1_armhf.deb ... Unpacking libayatana-ido3-dev (0.9.3-1) ... Selecting previously unselected package libayatana-indicator3-dev. Preparing to unpack .../325-libayatana-indicator3-dev_0.9.3-1_armhf.deb ... Unpacking libayatana-indicator3-dev (0.9.3-1) ... Selecting previously unselected package libxml2-utils. Preparing to unpack .../326-libxml2-utils_2.9.14+dfsg-1.2_armhf.deb ... Unpacking libxml2-utils (2.9.14+dfsg-1.2) ... Selecting previously unselected package libgtk2.0-dev:armhf. Preparing to unpack .../327-libgtk2.0-dev_2.24.33-2_armhf.deb ... Unpacking libgtk2.0-dev:armhf (2.24.33-2) ... Selecting previously unselected package libdbusmenu-glib-dev:armhf. Preparing to unpack .../328-libdbusmenu-glib-dev_18.10.20180917~bzr492+repack1-3_armhf.deb ... Unpacking libdbusmenu-glib-dev:armhf (18.10.20180917~bzr492+repack1-3) ... Selecting previously unselected package libayatana-appindicator3-dev. Preparing to unpack .../329-libayatana-appindicator3-dev_0.5.92-1_armhf.deb ... Unpacking libayatana-appindicator3-dev (0.5.92-1) ... Selecting previously unselected package libelf-dev:armhf. Preparing to unpack .../330-libelf-dev_0.188-2.1_armhf.deb ... Unpacking libelf-dev:armhf (0.188-2.1) ... Selecting previously unselected package libdw-dev:armhf. Preparing to unpack .../331-libdw-dev_0.188-2.1_armhf.deb ... Unpacking libdw-dev:armhf (0.188-2.1) ... Selecting previously unselected package libgconf2-dev. Preparing to unpack .../332-libgconf2-dev_3.2.6-8_armhf.deb ... Unpacking libgconf2-dev (3.2.6-8) ... Selecting previously unselected package libunwind-dev:armhf. Preparing to unpack .../333-libunwind-dev_1.6.2-3_armhf.deb ... Unpacking libunwind-dev:armhf (1.6.2-3) ... Selecting previously unselected package libgstreamer1.0-dev:armhf. Preparing to unpack .../334-libgstreamer1.0-dev_1.22.0-2_armhf.deb ... Unpacking libgstreamer1.0-dev:armhf (1.22.0-2) ... Selecting previously unselected package libnotify-dev:armhf. Preparing to unpack .../335-libnotify-dev_0.8.1-1_armhf.deb ... Unpacking libnotify-dev:armhf (0.8.1-1) ... Selecting previously unselected package libxml2-dev:armhf. Preparing to unpack .../336-libxml2-dev_2.9.14+dfsg-1.2_armhf.deb ... Unpacking libxml2-dev:armhf (2.9.14+dfsg-1.2) ... Setting up media-types (10.0.0) ... Setting up libpipeline1:armhf (1.5.7-1) ... Setting up libgraphite2-3:armhf (1.3.14-1) ... Setting up liblcms2-2:armhf (2.14-2) ... Setting up libpixman-1-0:armhf (0.42.2-1) ... Setting up libwayland-server0:armhf (1.21.0-1) ... Setting up systemd-sysv (252.6-1) ... Setting up libxau6:armhf (1:1.0.9-1) ... Setting up libpsl5:armhf (0.21.2-1) ... Setting up libpixman-1-dev:armhf (0.42.2-1) ... Setting up libicu72:armhf (72.1-3) ... Setting up liblerc4:armhf (4.0.0+ds-2) ... Setting up libzstd-dev:armhf (1.5.4+dfsg2-5) ... Setting up bsdextrautils (2.38.1-5+b1) ... Setting up libglvnd-core-dev:armhf (1.6.0-1) ... Setting up hicolor-icon-theme (0.17-2) ... Setting up libdatrie1:armhf (0.2.13-2+b1) ... Setting up libmagic-mgc (1:5.44-3) ... Setting up psmisc (23.6-1) ... Setting up libclone-perl:armhf (0.46-1) ... Setting up libarchive-zip-perl (1.68-1) ... Setting up libglib2.0-0:armhf (2.74.6-2) ... Setting up libglvnd0:armhf (1.6.0-1) ... Setting up libhtml-tagset-perl (3.20-6) ... Setting up libdbusmenu-glib4:armhf (18.10.20180917~bzr492+repack1-3) ... Setting up libdebhelper-perl (13.11.4) ... Setting up libbrotli1:armhf (1.0.9-2+b6) ... Setting up liblwp-mediatypes-perl (6.04-2) ... Setting up libgdk-pixbuf2.0-common (2.42.10+dfsg-1) ... Setting up x11-common (1:7.7+23) ... Running in chroot, ignoring request. Setting up X socket directories... /tmp/.X11-unix /tmp/.ICE-unix. Setting up libtry-tiny-perl (0.31-2) ... Setting up libsensors-config (1:3.6.0-7.1) ... Setting up libnghttp2-14:armhf (1.52.0-1) ... Setting up libmagic1:armhf (1:5.44-3) ... Setting up libdeflate0:armhf (1.14-1) ... Setting up perl-openssl-defaults:armhf (7+b1) ... Setting up gettext-base (0.21-12) ... Setting up m4 (1.4.19-3) ... Setting up xkb-data (2.35.1-1) ... Setting up liblzo2-2:armhf (2.10-2) ... Setting up libencode-locale-perl (1.05-3) ... Setting up autoconf-archive (20220903-3) ... Setting up file (1:5.44-3) ... Setting up libffi-dev:armhf (3.4.4-1) ... Setting up libunwind8:armhf (1.6.2-3) ... Setting up libpthread-stubs0-dev:armhf (0.4-1) ... Setting up libjbig0:armhf (2.1-6.1) ... Setting up libpcre2-16-0:armhf (10.42-1) ... Setting up libcolord2:armhf (1.4.6-2.2) ... Setting up libopengl0:armhf (1.6.0-1) ... Setting up libsasl2-modules-db:armhf (2.1.28+dfsg-10) ... Setting up libcap2-bin (1:2.66-3) ... Setting up libdconf1:armhf (0.40.0-4) ... Setting up xtrans-dev (1.4.0-1) ... Setting up libgraphite2-dev:armhf (1.3.14-1) ... Setting up autotools-dev (20220109.1) ... Setting up libz3-4:armhf (4.8.12-3.1) ... Setting up libpcre2-32-0:armhf (10.42-1) ... Setting up libglib2.0-data (2.74.6-2) ... Setting up libpkgconf3:armhf (1.8.1-1) ... Setting up libuv1:armhf (1.44.2-1) ... Setting up libgles2:armhf (1.6.0-1) ... Setting up libexpat1-dev:armhf (2.5.0-1) ... Setting up libjpeg62-turbo:armhf (1:2.1.5-2) ... Setting up libx11-data (2:1.8.4-2) ... Setting up libjpeg62-turbo-dev:armhf (1:2.1.5-2) ... Setting up libepoxy0:armhf (1.5.10-1) ... Setting up librtmp1:armhf (2.4+20151223.gitfa8646d.1-2+b2) ... Setting up uuid-dev:armhf (2.38.1-5+b1) ... Setting up libavahi-common-data:armhf (0.8-10) ... Setting up libgles1:armhf (1.6.0-1) ... Setting up libdbus-1-3:armhf (1.14.6-1) ... Setting up libfribidi0:armhf (1.0.8-2.1) ... Setting up libproc2-0:armhf (2:4.0.2-3) ... Setting up libpng16-16:armhf (1.6.39-2) ... Setting up libio-html-perl (1.004-3) ... Setting up autopoint (0.21-12) ... Setting up libjsoncpp25:armhf (1.9.5-4) ... Setting up icu-devtools (72.1-3) ... Setting up fonts-dejavu-core (2.37-6) ... Setting up libsepol-dev:armhf (3.4-2) ... Setting up pkgconf-bin (1.8.1-1) ... Setting up libsensors5:armhf (1:3.6.0-7.1) ... Setting up liblerc-dev:armhf (4.0.0+ds-2) ... Setting up libglapi-mesa:armhf (22.3.6-1+deb12u1) ... Setting up libsasl2-2:armhf (2.1.28+dfsg-10) ... Setting up autoconf (2.71-3) ... Setting up libwebp7:armhf (1.2.4-0.1) ... Setting up libtimedate-perl (2.3300-2) ... Setting up libregexp-ipv6-perl (0.03-3) ... Setting up liblzma-dev:armhf (5.4.1-0.2) ... Setting up zlib1g-dev:armhf (1:1.2.13.dfsg-1) ... Setting up libpcre2-posix3:armhf (10.42-1) ... Setting up wayland-protocols (1.31-1) ... Setting up sensible-utils (0.0.17+nmu1) ... Setting up libxshmfence1:armhf (1.3-1) ... Setting up at-spi2-common (2.46.0-5) ... Setting up librhash0:armhf (1.4.3-3) ... Setting up libtiff6:armhf (4.5.0-5) ... Setting up dbus-session-bus-common (1.14.6-1) ... Setting up libuchardet0:armhf (0.0.7-1) ... Setting up procps (2:4.0.2-3) ... Setting up libsub-override-perl (0.09-4) ... Setting up libthai-data (0.1.29-1) ... Setting up libgirepository-1.0-1:armhf (1.74.0-3) ... Setting up libssh2-1:armhf (1.10.0-3+b1) ... Setting up xorg-sgml-doctools (1:1.11-1.1) ... Setting up netbase (6.4) ... Setting up sgml-base (1.31) ... Setting up libgtk2.0-common (2.24.33-2) ... Setting up cmake-data (3.25.1-1) ... Setting up libatk1.0-0:armhf (2.46.0-5) ... Setting up libwayland-egl1:armhf (1.21.0-1) ... Setting up libopengl-dev:armhf (1.6.0-1) ... Setting up dbus-system-bus-common (1.14.6-1) ... Setting up openssl (3.0.8-1) ... Setting up libwebpmux3:armhf (1.2.4-0.1) ... Setting up libbsd0:armhf (0.11.7-2) ... Setting up libtiffxx6:armhf (4.5.0-5) ... Setting up libdeflate-dev:armhf (1.14-1) ... Setting up libdrm-common (2.4.114-1) ... Setting up libelf1:armhf (0.188-2.1) ... Setting up readline-common (8.2-1.3) ... Setting up libicu-dev:armhf (72.1-3) ... Setting up libxml2:armhf (2.9.14+dfsg-1.2) ... Setting up liburi-perl (5.17-1) ... Setting up dbus-bin (1.14.6-1) ... Setting up libbrotli-dev:armhf (1.0.9-2+b6) ... Setting up libxkbcommon0:armhf (1.5.0-1) ... Setting up libwayland-client0:armhf (1.21.0-1) ... Setting up libnet-ssleay-perl:armhf (1.92-2+b1) ... Setting up automake (1:1.16.5-1.3) ... update-alternatives: using /usr/bin/automake-1.16 to provide /usr/bin/automake (automake) in auto mode Setting up x11proto-dev (2022.1-1) ... Setting up libfile-stripnondeterminism-perl (1.13.1-1) ... Setting up libblkid-dev:armhf (2.38.1-5+b1) ... Setting up libice6:armhf (2:1.0.10-1) ... Setting up libhttp-date-perl (6.05-2) ... Setting up libdw1:armhf (0.188-2.1) ... Setting up libxdmcp6:armhf (1:1.1.2-3) ... Setting up libxcb1:armhf (1.15-1) ... Setting up gettext (0.21-12) ... Setting up libxcb-xfixes0:armhf (1.15-1) ... Setting up libfile-listing-perl (6.15-1) ... Setting up libxau-dev:armhf (1:1.0.9-1) ... Setting up libunwind-dev:armhf (1.6.2-3) ... Setting up libpcre2-dev:armhf (10.42-1) ... Setting up libice-dev:armhf (2:1.0.10-1) ... Setting up libtool (2.4.7-5) ... Setting up libarchive13:armhf (3.6.2-1) ... Setting up libxcb-render0:armhf (1.15-1) ... Setting up libselinux1-dev:armhf (3.4-1+b5) ... Setting up fontconfig-config (2.14.1-4) ... Setting up libfribidi-dev:armhf (1.0.8-2.1) ... Setting up libxcb-glx0:armhf (1.15-1) ... Setting up libwebpdemux2:armhf (1.2.4-0.1) ... Setting up libxkbcommon-dev:armhf (1.5.0-1) ... Setting up libedit2:armhf (3.1-20221030-2) ... Setting up libreadline8:armhf (8.2-1.3) ... Setting up libpng-dev:armhf (1.6.39-2) ... Setting up libavahi-common3:armhf (0.8-10) ... Setting up libjpeg-dev:armhf (1:2.1.5-2) ... Setting up libjbig-dev:armhf (2.1-6.1) ... Setting up libglib2.0-bin (2.74.6-2) ... Setting up libnet-http-perl (6.22-1) ... Setting up libxcb-shm0:armhf (1.15-1) ... Setting up dbus-daemon (1.14.6-1) ... Setting up libldap-2.5-0:armhf (2.5.13+dfsg-5) ... Setting up pkgconf:armhf (1.8.1-1) ... Setting up intltool-debian (0.35.0+20060710.6) ... Setting up libxcb-present0:armhf (1.15-1) ... Setting up dh-autoreconf (20) ... Setting up libthai0:armhf (0.1.29-1) ... Setting up ca-certificates (20230311) ... Updating certificates in /etc/ssl/certs... 140 added, 0 removed; done. Setting up libxdmcp-dev:armhf (1:1.1.2-3) ... Setting up libwayland-bin (1.21.0-1) ... Setting up libxml2-dev:armhf (2.9.14+dfsg-1.2) ... Setting up libwebp-dev:armhf (1.2.4-0.1) ... Setting up libfreetype6:armhf (2.12.1+dfsg-5) ... Setting up libtiff-dev:armhf (4.5.0-5) ... Setting up libxcb-sync1:armhf (1.15-1) ... Setting up libdbus-glib-1-2:armhf (0.112-3) ... Setting up dbus (1.14.6-1) ... Running in chroot, ignoring request. invoke-rc.d: policy-rc.d denied execution of start. Setting up shared-mime-info (2.2-1) ... Setting up libelf-dev:armhf (0.188-2.1) ... Setting up pkg-config:armhf (1.8.1-1) ... Setting up ucf (3.0043+nmu1) ... Setting up gir1.2-glib-2.0:armhf (1.74.0-3) ... Setting up libxcb-dri2-0:armhf (1.15-1) ... Setting up dh-strip-nondeterminism (1.13.1-1) ... Setting up libwww-robotrules-perl (6.02-1) ... Setting up libdrm2:armhf (2.4.114-1+b1) ... Setting up dwz (0.15-1) ... Setting up libdatrie-dev:armhf (0.2.13-2+b1) ... Setting up groff-base (1.22.4-10) ... Setting up libwayland-cursor0:armhf (1.21.0-1) ... Setting up libxcb-randr0:armhf (1.15-1) ... Setting up xml-core (0.18+nmu1) ... Setting up libhtml-parser-perl:armhf (3.81-1) ... Setting up libllvm15:armhf (1:15.0.6-4+b1) ... Setting up libpam-systemd:armhf (252.6-1) ... Setting up libcurl4:armhf (7.88.1-9) ... Setting up libx11-6:armhf (2:1.8.4-2) ... Setting up libharfbuzz0b:armhf (6.0.0+dfsg-3) ... Setting up libgdk-pixbuf-2.0-0:armhf (2.42.10+dfsg-1+b1) ... Setting up libfontconfig1:armhf (2.14.1-4) ... Setting up libxml2-utils (2.9.14+dfsg-1.2) ... Setting up libxcomposite1:armhf (1:0.4.5-1) ... Setting up libsm6:armhf (2:1.2.3-1) ... Setting up libavahi-client3:armhf (0.8-10) ... Setting up libmount-dev:armhf (2.38.1-5+b1) ... Setting up libio-socket-ssl-perl (2.081-2) ... Setting up libgstreamer1.0-0:armhf (1.22.0-2) ... Setcap worked! gst-ptp-helper is not suid! Setting up libhttp-message-perl (6.44-1) ... Setting up libdrm-amdgpu1:armhf (2.4.114-1+b1) ... Setting up libxcb-dri3-0:armhf (1.15-1) ... Setting up gtk-update-icon-cache (3.24.37-2) ... Setting up libx11-xcb1:armhf (2:1.8.4-2) ... Setting up gir1.2-gstreamer-1.0:armhf (1.22.0-2) ... Setting up libhttp-negotiate-perl (6.01-2) ... Setting up fontconfig (2.14.1-4) ... Regenerating fonts cache... done. Setting up libdrm-nouveau2:armhf (2.4.114-1+b1) ... Setting up gir1.2-freedesktop:armhf (1.74.0-3) ... Setting up libharfbuzz-icu0:armhf (6.0.0+dfsg-3) ... Setting up libxdamage1:armhf (1:1.1.6-1) ... Setting up libxcb1-dev:armhf (1.15-1) ... Setting up gir1.2-dbusmenu-glib-0.4:armhf (18.10.20180917~bzr492+repack1-3) ... Setting up libxrender1:armhf (1:0.9.10-1.1) ... Setting up gir1.2-gdkpixbuf-2.0:armhf (2.42.10+dfsg-1+b1) ... Setting up libgbm1:armhf (22.3.6-1+deb12u1) ... Setting up libhttp-cookies-perl (6.10-1) ... Setting up gir1.2-atk-1.0:armhf (2.46.0-5) ... Setting up libsm-dev:armhf (2:1.2.3-1) ... Setting up libdrm-radeon1:armhf (2.4.114-1+b1) ... Setting up po-debconf (1.0.21+nmu1) ... Setting up libhtml-tree-perl (5.07-3) ... Setting up libpython3.11-stdlib:armhf (3.11.2-6) ... Setting up libpango-1.0-0:armhf (1.50.12+ds-1) ... Setting up libgl1-mesa-dri:armhf (22.3.6-1+deb12u1) ... Setting up libx11-dev:armhf (2:1.8.4-2) ... Setting up libxext6:armhf (2:1.3.4-1+b1) ... Setting up libharfbuzz-gobject0:armhf (6.0.0+dfsg-3) ... Setting up man-db (2.11.2-2) ... Not building database; man-db/auto-update is not 'true'. Created symlink /etc/systemd/system/timers.target.wants/man-db.timer -> /lib/systemd/system/man-db.timer. Setting up libwayland-dev:armhf (1.21.0-1) ... Setting up gir1.2-harfbuzz-0.0:armhf (6.0.0+dfsg-3) ... Setting up libdw-dev:armhf (0.188-2.1) ... Setting up libcairo2:armhf (1.16.0-7) ... Setting up libxxf86vm1:armhf (1:1.1.4-1+b2) ... Setting up libfreetype-dev:armhf (2.12.1+dfsg-5) ... Setting up libxcb-shm0-dev:armhf (1.15-1) ... Setting up dbus-user-session (1.14.6-1) ... Setting up libegl-mesa0:armhf (22.3.6-1+deb12u1) ... Setting up gconf2-common (3.2.6-8) ... Creating config file /etc/gconf/2/path with new version Setting up adwaita-icon-theme (43-1) ... 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 libxfixes3:armhf (1:6.0.0-2) ... Setting up libnotify4:armhf (0.8.1-1) ... Setting up libxinerama1:armhf (2:1.1.4-3) ... Setting up libxrandr2:armhf (2:1.5.2-2+b1) ... Setting up libxcb-render0-dev:armhf (1.15-1) ... Setting up libxext-dev:armhf (2:1.3.4-1+b1) ... Setting up libthai-dev:armhf (0.1.29-1) ... Setting up libcups2:armhf (2.4.2-3) ... Setting up gir1.2-notify-0.7:armhf (0.8.1-1) ... Setting up libgdk-pixbuf2.0-bin (2.42.10+dfsg-1+b1) ... Setting up libegl1:armhf (1.6.0-1) ... Setting up libharfbuzz-subset0:armhf (6.0.0+dfsg-3) ... Setting up cmake (3.25.1-1) ... Setting up libcairo-gobject2:armhf (1.16.0-7) ... Setting up libpangoft2-1.0-0:armhf (1.50.12+ds-1) ... Setting up libxrender-dev:armhf (1:0.9.10-1.1) ... Setting up libpangocairo-1.0-0:armhf (1.50.12+ds-1) ... Setting up libpython3-stdlib:armhf (3.11.2-1+b1) ... Setting up libcairo-script-interpreter2:armhf (1.16.0-7) ... Setting up python3.11 (3.11.2-6) ... Setting up libxft2:armhf (2.3.6-1) ... Setting up libdbusmenu-gtk3-4:armhf (18.10.20180917~bzr492+repack1-3) ... Setting up libglx-mesa0:armhf (22.3.6-1+deb12u1) ... Setting up libpangoxft-1.0-0:armhf (1.50.12+ds-1) ... Setting up libxi6:armhf (2:1.8-1+b1) ... Setting up libglx0:armhf (1.6.0-1) ... Setting up libgconf-2-4:armhf (3.2.6-8) ... Setting up libfontconfig-dev:armhf (2.14.1-4) ... Setting up libxtst6:armhf (2:1.2.3-1.1) ... Setting up libxcursor1:armhf (1:1.2.1-1) ... Setting up pango1.0-tools (1.50.12+ds-1) ... Setting up debhelper (13.11.4) ... Setting up dconf-service (0.40.0-4) ... Setting up python3 (3.11.2-1+b1) ... Setting up libatspi2.0-0:armhf (2.46.0-5) ... Setting up librsvg2-2:armhf (2.54.5+dfsg-1) ... Setting up libxfixes-dev:armhf (1:6.0.0-2) ... Setting up libatk-bridge2.0-0:armhf (2.46.0-5) ... Setting up gir1.2-pango-1.0:armhf (1.50.12+ds-1) ... Setting up libxrandr-dev:armhf (2:1.5.2-2+b1) ... Setting up libgl1:armhf (1.6.0-1) ... Setting up libxinerama-dev:armhf (2:1.1.4-3) ... Setting up librsvg2-common:armhf (2.54.5+dfsg-1) ... Setting up gconf-service (3.2.6-8) ... Setting up libglx-dev:armhf (1.6.0-1) ... Setting up libxi-dev:armhf (2:1.8-1+b1) ... Setting up python3-lib2to3 (3.11.2-3) ... Setting up libgl-dev:armhf (1.6.0-1) ... Setting up libxft-dev:armhf (2.3.6-1) ... Setting up libxtst-dev:armhf (2:1.2.3-1.1) ... Setting up python3-distutils (3.11.2-3) ... Setting up libxdamage-dev:armhf (1:1.1.6-1) ... Setting up gir1.2-gconf-2.0 (3.2.6-8) ... Setting up libglib2.0-dev-bin (2.74.6-2) ... Setting up dconf-gsettings-backend:armhf (0.40.0-4) ... Setting up libegl-dev:armhf (1.6.0-1) ... Setting up libxcomposite-dev:armhf (1:0.4.5-1) ... Setting up libxcursor-dev:armhf (1:1.2.1-1) ... Setting up libgtk2.0-0:armhf (2.24.33-2) ... Setting up libepoxy-dev:armhf (1.5.10-1) ... Setting up gir1.2-atspi-2.0:armhf (2.46.0-5) ... Setting up gconf2 (3.2.6-8) ... Setting up gnome-icon-theme (3.12.0-5) ... 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 libglib2.0-dev:armhf (2.74.6-2) ... Setting up gir1.2-gtk-2.0:armhf (2.24.33-2) ... Setting up libcairo2-dev:armhf (1.16.0-7) ... Setting up libgles-dev:armhf (1.6.0-1) ... Setting up libgtk-3-common (3.24.37-2) ... Setting up libatk1.0-dev:armhf (2.46.0-5) ... Setting up libgdk-pixbuf-2.0-dev:armhf (2.42.10+dfsg-1+b1) ... Setting up libharfbuzz-dev:armhf (6.0.0+dfsg-3) ... Setting up libnotify-dev:armhf (0.8.1-1) ... Setting up libgstreamer1.0-dev:armhf (1.22.0-2) ... Setting up libgtk-3-0:armhf (3.24.37-2) ... Setting up gir1.2-gtk-3.0:armhf (3.24.37-2) ... Setting up libglvnd-dev:armhf (1.6.0-1) ... Setting up libayatana-ido3-0.4-0:armhf (0.9.3-1) ... Setting up libpango1.0-dev:armhf (1.50.12+ds-1) ... Setting up gir1.2-ayatanaido3-0.4:armhf (0.9.3-1) ... Setting up libgtk2.0-dev:armhf (2.24.33-2) ... Setting up libayatana-indicator3-7:armhf (0.9.3-1) ... Setting up libegl1-mesa-dev:armhf (22.3.6-1+deb12u1) ... Setting up libayatana-appindicator3-1 (0.5.92-1) ... Setting up libdbusmenu-glib-dev:armhf (18.10.20180917~bzr492+repack1-3) ... Setting up gir1.2-ayatanaappindicator3-0.1 (0.5.92-1) ... Setting up liblwp-protocol-https-perl (6.10-1) ... Setting up libwww-perl (6.68-1) ... Setting up libxml-parser-perl (2.46-4) ... Setting up intltool (0.51.0-6) ... Setting up gnome-common (3.18.0-4) ... Processing triggers for libc-bin (2.36-9) ... Processing triggers for systemd (252.6-1) ... Processing triggers for sgml-base (1.31) ... Setting up libdbus-1-dev:armhf (1.14.6-1) ... Setting up libatspi2.0-dev:armhf (2.46.0-5) ... Setting up libgconf2-dev (3.2.6-8) ... Setting up libatk-bridge2.0-dev:armhf (2.46.0-5) ... Setting up libgtk-3-dev:armhf (3.24.37-2) ... Setting up libayatana-ido3-dev (0.9.3-1) ... Setting up libayatana-indicator3-dev (0.9.3-1) ... Setting up libayatana-appindicator3-dev (0.5.92-1) ... Processing triggers for ca-certificates (20230311) ... Updating certificates in /etc/ssl/certs... 0 added, 0 removed; done. Running hooks in /etc/ca-certificates/update.d... done. Processing triggers for libgdk-pixbuf-2.0-0:armhf (2.42.10+dfsg-1+b1) ... Reading package lists... Building dependency tree... Reading state information... Reading extended state information... Initializing package states... Writing extended state information... Building tag database... -> Finished parsing the build-deps Reading package lists... Building dependency tree... Reading state information... fakeroot is already the newest version (1.31-1.2). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. I: Building the package I: Running cd /build/alarm-clock-applet-0.4.1/ && env PATH="/usr/sbin:/usr/bin:/sbin:/bin:/usr/games" HOME="/nonexistent/first-build" dpkg-buildpackage -us -uc -b && env PATH="/usr/sbin:/usr/bin:/sbin:/bin:/usr/games" HOME="/nonexistent/first-build" dpkg-genchanges -S > ../alarm-clock-applet_0.4.1-3_source.changes dpkg-buildpackage: info: source package alarm-clock-applet dpkg-buildpackage: info: source version 0.4.1-3 dpkg-buildpackage: info: source distribution unstable dpkg-buildpackage: info: source changed by Chow Loong Jin dpkg-source --before-build . dpkg-buildpackage: info: host architecture armhf fakeroot debian/rules clean dh clean dh_clean debian/rules build dh build dh_update_autotools_config dh_autoreconf dh_auto_configure cd obj-arm-linux-gnueabihf && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/arm-linux-gnueabihf .. -- The C compiler identification is GNU 12.2.0 -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working C compiler: /usr/bin/cc - skipped -- Detecting C compile features -- Detecting C compile features - done -- Found PkgConfig: /usr/bin/pkg-config (found version "1.8.1") -- Found Gettext: /usr/bin/msgmerge (found version "0.21") -- Checking for module 'gio-2.0' -- Found gio-2.0, version 2.74.6 -- Checking for module 'gconf-2.0' -- Found gconf-2.0, version 3.2.6 -- Checking for module 'gtk+-3.0' -- Found gtk+-3.0, version 3.24.37 -- Checking for module 'gstreamer-1.0' -- Found gstreamer-1.0, version 1.22.0 -- Checking for module 'libnotify' -- Found libnotify, version 0.8.1 -- Checking for module 'ayatana-appindicator3-0.1' -- Found ayatana-appindicator3-0.1, version 0.5.90 -- Configuring done -- Generating done CMake Warning: Manually-specified variables were not used by the project: CMAKE_EXPORT_NO_PACKAGE_REGISTRY CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY FETCHCONTENT_FULLY_DISCONNECTED -- Build files have been written to: /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf dh_auto_build cd obj-arm-linux-gnueabihf && make -j3 "INSTALL=install --strip-program=true" VERBOSE=1 make[1]: Entering directory '/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf' /usr/bin/cmake -S/build/alarm-clock-applet-0.4.1 -B/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf --check-build-system CMakeFiles/Makefile.cmake 0 /usr/bin/cmake -E cmake_progress_start /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/CMakeFiles /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf//CMakeFiles/progress.marks make -f CMakeFiles/Makefile2 all make[2]: Entering directory '/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf' make -f gconf-migration/CMakeFiles/alarm-clock-applet-gconf-migration.dir/build.make gconf-migration/CMakeFiles/alarm-clock-applet-gconf-migration.dir/depend make -f po/CMakeFiles/translations_1.dir/build.make po/CMakeFiles/translations_1.dir/depend make -f po/CMakeFiles/linguas.dir/build.make po/CMakeFiles/linguas.dir/depend make[3]: Entering directory '/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf' cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /build/alarm-clock-applet-0.4.1 /build/alarm-clock-applet-0.4.1/gconf-migration /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/gconf-migration /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/gconf-migration/CMakeFiles/alarm-clock-applet-gconf-migration.dir/DependInfo.cmake --color= make[3]: Entering directory '/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf' cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /build/alarm-clock-applet-0.4.1 /build/alarm-clock-applet-0.4.1/po /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po/CMakeFiles/linguas.dir/DependInfo.cmake --color= make[3]: Entering directory '/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf' cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /build/alarm-clock-applet-0.4.1 /build/alarm-clock-applet-0.4.1/po /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po/CMakeFiles/translations_1.dir/DependInfo.cmake --color= make[3]: Leaving directory '/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf' make -f po/CMakeFiles/translations_1.dir/build.make po/CMakeFiles/translations_1.dir/build make[3]: Entering directory '/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf' make[3]: Leaving directory '/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf' make -f po/CMakeFiles/linguas.dir/build.make po/CMakeFiles/linguas.dir/build make[3]: Entering directory '/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf' make[3]: Nothing to be done for 'po/CMakeFiles/linguas.dir/build'. make[3]: Leaving directory '/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf' make[3]: Leaving directory '/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf' make -f gconf-migration/CMakeFiles/alarm-clock-applet-gconf-migration.dir/build.make gconf-migration/CMakeFiles/alarm-clock-applet-gconf-migration.dir/build make[3]: Entering directory '/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf' [ 1%] Generating ar.gmo cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgmerge --quiet --update --backup=none -s /build/alarm-clock-applet-0.4.1/po/ar.po /build/alarm-clock-applet-0.4.1/po/alarm-clock-applet.pot [ 3%] Building C object gconf-migration/CMakeFiles/alarm-clock-applet-gconf-migration.dir/alarm-clock-gconf-migration.c.o cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po/ar.gmo /build/alarm-clock-applet-0.4.1/po/ar.po cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/gconf-migration && /usr/bin/cc -I/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf -I/usr/include/gconf/2 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/dbus-1.0 -I/usr/lib/arm-linux-gnueabihf/dbus-1.0/include -I/usr/include/libmount -I/usr/include/blkid -g -O2 -ffile-prefix-map=/build/alarm-clock-applet-0.4.1=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=gnu11 -MD -MT gconf-migration/CMakeFiles/alarm-clock-applet-gconf-migration.dir/alarm-clock-gconf-migration.c.o -MF CMakeFiles/alarm-clock-applet-gconf-migration.dir/alarm-clock-gconf-migration.c.o.d -o CMakeFiles/alarm-clock-applet-gconf-migration.dir/alarm-clock-gconf-migration.c.o -c /build/alarm-clock-applet-0.4.1/gconf-migration/alarm-clock-gconf-migration.c [ 3%] Built target linguas make -f src/CMakeFiles/man-alarm-clock-applet.dir/build.make src/CMakeFiles/man-alarm-clock-applet.dir/depend make[3]: Entering directory '/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf' cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /build/alarm-clock-applet-0.4.1 /build/alarm-clock-applet-0.4.1/src /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/src /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/src/CMakeFiles/man-alarm-clock-applet.dir/DependInfo.cmake --color= make[3]: Leaving directory '/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf' make -f src/CMakeFiles/man-alarm-clock-applet.dir/build.make src/CMakeFiles/man-alarm-clock-applet.dir/build make[3]: Entering directory '/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf' [ 5%] Generating ast.gmo cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgmerge --quiet --update --backup=none -s /build/alarm-clock-applet-0.4.1/po/ast.po /build/alarm-clock-applet-0.4.1/po/alarm-clock-applet.pot cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po/ast.gmo /build/alarm-clock-applet-0.4.1/po/ast.po [ 6%] Generating alarm-clock-applet.1 cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/src && /usr/bin/pod2man --utf8 --section="1" --center="General\ Commands\ Manual" --release="0.4.1" --name="ALARM-CLOCK-APPLET" /build/alarm-clock-applet-0.4.1/src/alarm-clock-applet.pod /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/src/alarm-clock-applet.1 [ 8%] Generating be.gmo cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgmerge --quiet --update --backup=none -s /build/alarm-clock-applet-0.4.1/po/be.po /build/alarm-clock-applet-0.4.1/po/alarm-clock-applet.pot cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po/be.gmo /build/alarm-clock-applet-0.4.1/po/be.po [ 10%] Generating bg.gmo cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgmerge --quiet --update --backup=none -s /build/alarm-clock-applet-0.4.1/po/bg.po /build/alarm-clock-applet-0.4.1/po/alarm-clock-applet.pot cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po/bg.gmo /build/alarm-clock-applet-0.4.1/po/bg.po [ 11%] Generating ca.gmo cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgmerge --quiet --update --backup=none -s /build/alarm-clock-applet-0.4.1/po/ca.po /build/alarm-clock-applet-0.4.1/po/alarm-clock-applet.pot cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po/ca.gmo /build/alarm-clock-applet-0.4.1/po/ca.po [ 13%] Generating cs.gmo cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgmerge --quiet --update --backup=none -s /build/alarm-clock-applet-0.4.1/po/cs.po /build/alarm-clock-applet-0.4.1/po/alarm-clock-applet.pot cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po/cs.gmo /build/alarm-clock-applet-0.4.1/po/cs.po [ 15%] Generating alarm-clock-applet.1.gz [ 16%] Generating da.gmo cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/src && /bin/gzip -f -k --best -n /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/src/alarm-clock-applet.1 cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgmerge --quiet --update --backup=none -s /build/alarm-clock-applet-0.4.1/po/da.po /build/alarm-clock-applet-0.4.1/po/alarm-clock-applet.pot make[3]: Leaving directory '/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf' cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po/da.gmo /build/alarm-clock-applet-0.4.1/po/da.po [ 16%] Built target man-alarm-clock-applet [ 18%] Generating de.gmo cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgmerge --quiet --update --backup=none -s /build/alarm-clock-applet-0.4.1/po/de.po /build/alarm-clock-applet-0.4.1/po/alarm-clock-applet.pot cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po/de.gmo /build/alarm-clock-applet-0.4.1/po/de.po [ 20%] Generating el.gmo cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgmerge --quiet --update --backup=none -s /build/alarm-clock-applet-0.4.1/po/el.po /build/alarm-clock-applet-0.4.1/po/alarm-clock-applet.pot cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po/el.gmo /build/alarm-clock-applet-0.4.1/po/el.po [ 22%] Generating es.gmo cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgmerge --quiet --update --backup=none -s /build/alarm-clock-applet-0.4.1/po/es.po /build/alarm-clock-applet-0.4.1/po/alarm-clock-applet.pot cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po/es.gmo /build/alarm-clock-applet-0.4.1/po/es.po [ 23%] Generating et.gmo cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgmerge --quiet --update --backup=none -s /build/alarm-clock-applet-0.4.1/po/et.po /build/alarm-clock-applet-0.4.1/po/alarm-clock-applet.pot cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po/et.gmo /build/alarm-clock-applet-0.4.1/po/et.po [ 25%] Generating fi.gmo cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgmerge --quiet --update --backup=none -s /build/alarm-clock-applet-0.4.1/po/fi.po /build/alarm-clock-applet-0.4.1/po/alarm-clock-applet.pot cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po/fi.gmo /build/alarm-clock-applet-0.4.1/po/fi.po [ 27%] Generating fo.gmo cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgmerge --quiet --update --backup=none -s /build/alarm-clock-applet-0.4.1/po/fo.po /build/alarm-clock-applet-0.4.1/po/alarm-clock-applet.pot cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po/fo.gmo /build/alarm-clock-applet-0.4.1/po/fo.po [ 28%] Generating fr.gmo cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgmerge --quiet --update --backup=none -s /build/alarm-clock-applet-0.4.1/po/fr.po /build/alarm-clock-applet-0.4.1/po/alarm-clock-applet.pot cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po/fr.gmo /build/alarm-clock-applet-0.4.1/po/fr.po [ 30%] Generating gl.gmo cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgmerge --quiet --update --backup=none -s /build/alarm-clock-applet-0.4.1/po/gl.po /build/alarm-clock-applet-0.4.1/po/alarm-clock-applet.pot cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po/gl.gmo /build/alarm-clock-applet-0.4.1/po/gl.po [ 32%] Generating he.gmo cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgmerge --quiet --update --backup=none -s /build/alarm-clock-applet-0.4.1/po/he.po /build/alarm-clock-applet-0.4.1/po/alarm-clock-applet.pot cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po/he.gmo /build/alarm-clock-applet-0.4.1/po/he.po [ 33%] Generating hi.gmo cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgmerge --quiet --update --backup=none -s /build/alarm-clock-applet-0.4.1/po/hi.po /build/alarm-clock-applet-0.4.1/po/alarm-clock-applet.pot cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po/hi.gmo /build/alarm-clock-applet-0.4.1/po/hi.po [ 35%] Generating hu.gmo cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgmerge --quiet --update --backup=none -s /build/alarm-clock-applet-0.4.1/po/hu.po /build/alarm-clock-applet-0.4.1/po/alarm-clock-applet.pot cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po/hu.gmo /build/alarm-clock-applet-0.4.1/po/hu.po [ 37%] Generating id.gmo cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgmerge --quiet --update --backup=none -s /build/alarm-clock-applet-0.4.1/po/id.po /build/alarm-clock-applet-0.4.1/po/alarm-clock-applet.pot cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po/id.gmo /build/alarm-clock-applet-0.4.1/po/id.po [ 38%] Generating it.gmo cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgmerge --quiet --update --backup=none -s /build/alarm-clock-applet-0.4.1/po/it.po /build/alarm-clock-applet-0.4.1/po/alarm-clock-applet.pot cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po/it.gmo /build/alarm-clock-applet-0.4.1/po/it.po [ 40%] Generating ja.gmo cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgmerge --quiet --update --backup=none -s /build/alarm-clock-applet-0.4.1/po/ja.po /build/alarm-clock-applet-0.4.1/po/alarm-clock-applet.pot cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po/ja.gmo /build/alarm-clock-applet-0.4.1/po/ja.po [ 42%] Generating ka.gmo cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgmerge --quiet --update --backup=none -s /build/alarm-clock-applet-0.4.1/po/ka.po /build/alarm-clock-applet-0.4.1/po/alarm-clock-applet.pot cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po/ka.gmo /build/alarm-clock-applet-0.4.1/po/ka.po [ 44%] Generating la.gmo cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgmerge --quiet --update --backup=none -s /build/alarm-clock-applet-0.4.1/po/la.po /build/alarm-clock-applet-0.4.1/po/alarm-clock-applet.pot [ 45%] Generating ms.gmo cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgmerge --quiet --update --backup=none -s /build/alarm-clock-applet-0.4.1/po/ms.po /build/alarm-clock-applet-0.4.1/po/alarm-clock-applet.pot cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po/la.gmo /build/alarm-clock-applet-0.4.1/po/la.po cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po/ms.gmo /build/alarm-clock-applet-0.4.1/po/ms.po [ 47%] Generating nb.gmo cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgmerge --quiet --update --backup=none -s /build/alarm-clock-applet-0.4.1/po/nb.po /build/alarm-clock-applet-0.4.1/po/alarm-clock-applet.pot cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po/nb.gmo /build/alarm-clock-applet-0.4.1/po/nb.po [ 49%] Generating nl.gmo cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgmerge --quiet --update --backup=none -s /build/alarm-clock-applet-0.4.1/po/nl.po /build/alarm-clock-applet-0.4.1/po/alarm-clock-applet.pot [ 50%] Linking C executable alarm-clock-applet-gconf-migration cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/gconf-migration && /usr/bin/cmake -E cmake_link_script CMakeFiles/alarm-clock-applet-gconf-migration.dir/link.txt --verbose=1 cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po/nl.gmo /build/alarm-clock-applet-0.4.1/po/nl.po [ 52%] Generating nn.gmo /usr/bin/cc -g -O2 -ffile-prefix-map=/build/alarm-clock-applet-0.4.1=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,--as-needed -Wl,-z,defs "CMakeFiles/alarm-clock-applet-gconf-migration.dir/alarm-clock-gconf-migration.c.o" -o alarm-clock-applet-gconf-migration -lgconf-2 -lglib-2.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0 -lgio-2.0 -lgobject-2.0 cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgmerge --quiet --update --backup=none -s /build/alarm-clock-applet-0.4.1/po/nn.po /build/alarm-clock-applet-0.4.1/po/alarm-clock-applet.pot cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po/nn.gmo /build/alarm-clock-applet-0.4.1/po/nn.po [ 54%] Generating pl.gmo cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgmerge --quiet --update --backup=none -s /build/alarm-clock-applet-0.4.1/po/pl.po /build/alarm-clock-applet-0.4.1/po/alarm-clock-applet.pot cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po/pl.gmo /build/alarm-clock-applet-0.4.1/po/pl.po [ 55%] Generating pt_BR.gmo cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgmerge --quiet --update --backup=none -s /build/alarm-clock-applet-0.4.1/po/pt_BR.po /build/alarm-clock-applet-0.4.1/po/alarm-clock-applet.pot cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po/pt_BR.gmo /build/alarm-clock-applet-0.4.1/po/pt_BR.po [ 57%] Generating pt.gmo cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgmerge --quiet --update --backup=none -s /build/alarm-clock-applet-0.4.1/po/pt.po /build/alarm-clock-applet-0.4.1/po/alarm-clock-applet.pot cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po/pt.gmo /build/alarm-clock-applet-0.4.1/po/pt.po [ 59%] Generating ru.gmo cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgmerge --quiet --update --backup=none -s /build/alarm-clock-applet-0.4.1/po/ru.po /build/alarm-clock-applet-0.4.1/po/alarm-clock-applet.pot cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po/ru.gmo /build/alarm-clock-applet-0.4.1/po/ru.po [ 61%] Generating si.gmo cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgmerge --quiet --update --backup=none -s /build/alarm-clock-applet-0.4.1/po/si.po /build/alarm-clock-applet-0.4.1/po/alarm-clock-applet.pot make[3]: Leaving directory '/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf' cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po/si.gmo /build/alarm-clock-applet-0.4.1/po/si.po [ 62%] Generating sv.gmo cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgmerge --quiet --update --backup=none -s /build/alarm-clock-applet-0.4.1/po/sv.po /build/alarm-clock-applet-0.4.1/po/alarm-clock-applet.pot cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po/sv.gmo /build/alarm-clock-applet-0.4.1/po/sv.po [ 62%] Built target alarm-clock-applet-gconf-migration [ 64%] Generating uk.gmo cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgmerge --quiet --update --backup=none -s /build/alarm-clock-applet-0.4.1/po/uk.po /build/alarm-clock-applet-0.4.1/po/alarm-clock-applet.pot [ 66%] Generating tr.gmo [ 67%] Generating zh_CN.gmo cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgmerge --quiet --update --backup=none -s /build/alarm-clock-applet-0.4.1/po/tr.po /build/alarm-clock-applet-0.4.1/po/alarm-clock-applet.pot cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgmerge --quiet --update --backup=none -s /build/alarm-clock-applet-0.4.1/po/zh_CN.po /build/alarm-clock-applet-0.4.1/po/alarm-clock-applet.pot cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po/uk.gmo /build/alarm-clock-applet-0.4.1/po/uk.po cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po/zh_CN.gmo /build/alarm-clock-applet-0.4.1/po/zh_CN.po cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po/tr.gmo /build/alarm-clock-applet-0.4.1/po/tr.po [ 69%] Generating zh_TW.gmo cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgmerge --quiet --update --backup=none -s /build/alarm-clock-applet-0.4.1/po/zh_TW.po /build/alarm-clock-applet-0.4.1/po/alarm-clock-applet.pot cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po/zh_TW.gmo /build/alarm-clock-applet-0.4.1/po/zh_TW.po make[3]: Leaving directory '/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf' [ 69%] Built target translations_1 make -f po/CMakeFiles/translations.dir/build.make po/CMakeFiles/translations.dir/depend make[3]: Entering directory '/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf' cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /build/alarm-clock-applet-0.4.1 /build/alarm-clock-applet-0.4.1/po /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po/CMakeFiles/translations.dir/DependInfo.cmake --color= make[3]: Leaving directory '/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf' make -f po/CMakeFiles/translations.dir/build.make po/CMakeFiles/translations.dir/build make[3]: Entering directory '/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf' make[3]: Nothing to be done for 'po/CMakeFiles/translations.dir/build'. make[3]: Leaving directory '/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf' [ 69%] Built target translations make -f src/CMakeFiles/alarm-clock-applet.dir/build.make src/CMakeFiles/alarm-clock-applet.dir/depend make[3]: Entering directory '/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf' [ 71%] Generating io.github.alarm-clock-applet.enums.gschema.xml cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/src && /usr/bin/glib-mkenums --comments "" --fhead "" --vhead " <@type@ id=\"io.github.alarm-clock-applet.@EnumName@\">" --vprod " " --vtail " " --ftail "" /build/alarm-clock-applet-0.4.1/src/alarm-enums.h --output io.github.alarm-clock-applet.enums.gschema.xml [ 72%] Generating alarm-glib-enums.c cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/src && /usr/bin/glib-mkenums --template /build/alarm-clock-applet-0.4.1/src/alarm-glib-enums.c.etemplate --output alarm-glib-enums.c /build/alarm-clock-applet-0.4.1/src/alarm-enums.h [ 74%] Generating alarm-clock-applet.desktop cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/src && /usr/bin/msgfmt --desktop --template /build/alarm-clock-applet-0.4.1/data/alarm-clock-applet.desktop.in --output alarm-clock-applet.desktop -d /build/alarm-clock-applet-0.4.1/po/ [ 76%] Generating alarm-glib-enums.h cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/src && /usr/bin/glib-mkenums --template /build/alarm-clock-applet-0.4.1/src/alarm-glib-enums.h.etemplate --output alarm-glib-enums.h /build/alarm-clock-applet-0.4.1/src/alarm-enums.h [ 77%] Generating autostart/alarm-clock-applet.desktop cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/src/autostart && /usr/bin/msgfmt --desktop --template /build/alarm-clock-applet-0.4.1/data/alarm-clock-applet_autostart.desktop.in --output alarm-clock-applet.desktop -d /build/alarm-clock-applet-0.4.1/po/ cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /build/alarm-clock-applet-0.4.1 /build/alarm-clock-applet-0.4.1/src /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/src /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/src/CMakeFiles/alarm-clock-applet.dir/DependInfo.cmake --color= make[3]: Leaving directory '/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf' make -f src/CMakeFiles/alarm-clock-applet.dir/build.make src/CMakeFiles/alarm-clock-applet.dir/build make[3]: Entering directory '/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf' [ 79%] Building C object src/CMakeFiles/alarm-clock-applet.dir/player.c.o cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/src && /usr/bin/cc -DG_LOG_DOMAIN=\"alarm-clock-applet\" -I/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/gio-unix-2.0 -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/arm-linux-gnueabihf/dbus-1.0/include -I/usr/include/gstreamer-1.0 -I/usr/include/libayatana-appindicator3-0.1 -I/usr/include/libayatana-indicator3-0.4 -I/usr/include/libayatana-ido3-0.4 -I/usr/include/libdbusmenu-glib-0.4 -I/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/src -g -O2 -ffile-prefix-map=/build/alarm-clock-applet-0.4.1=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wshadow -Werror=return-type -pthread -std=gnu11 -MD -MT src/CMakeFiles/alarm-clock-applet.dir/player.c.o -MF CMakeFiles/alarm-clock-applet.dir/player.c.o.d -o CMakeFiles/alarm-clock-applet.dir/player.c.o -c /build/alarm-clock-applet-0.4.1/src/player.c [ 81%] Building C object src/CMakeFiles/alarm-clock-applet.dir/alarm-applet.c.o cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/src && /usr/bin/cc -DG_LOG_DOMAIN=\"alarm-clock-applet\" -I/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/gio-unix-2.0 -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/arm-linux-gnueabihf/dbus-1.0/include -I/usr/include/gstreamer-1.0 -I/usr/include/libayatana-appindicator3-0.1 -I/usr/include/libayatana-indicator3-0.4 -I/usr/include/libayatana-ido3-0.4 -I/usr/include/libdbusmenu-glib-0.4 -I/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/src -g -O2 -ffile-prefix-map=/build/alarm-clock-applet-0.4.1=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wshadow -Werror=return-type -pthread -std=gnu11 -MD -MT src/CMakeFiles/alarm-clock-applet.dir/alarm-applet.c.o -MF CMakeFiles/alarm-clock-applet.dir/alarm-applet.c.o.d -o CMakeFiles/alarm-clock-applet.dir/alarm-applet.c.o -c /build/alarm-clock-applet-0.4.1/src/alarm-applet.c [ 83%] Building C object src/CMakeFiles/alarm-clock-applet.dir/util.c.o cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/src && /usr/bin/cc -DG_LOG_DOMAIN=\"alarm-clock-applet\" -I/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/gio-unix-2.0 -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/arm-linux-gnueabihf/dbus-1.0/include -I/usr/include/gstreamer-1.0 -I/usr/include/libayatana-appindicator3-0.1 -I/usr/include/libayatana-indicator3-0.4 -I/usr/include/libayatana-ido3-0.4 -I/usr/include/libdbusmenu-glib-0.4 -I/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/src -g -O2 -ffile-prefix-map=/build/alarm-clock-applet-0.4.1=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wshadow -Werror=return-type -pthread -std=gnu11 -MD -MT src/CMakeFiles/alarm-clock-applet.dir/util.c.o -MF CMakeFiles/alarm-clock-applet.dir/util.c.o.d -o CMakeFiles/alarm-clock-applet.dir/util.c.o -c /build/alarm-clock-applet-0.4.1/src/util.c [ 84%] Building C object src/CMakeFiles/alarm-clock-applet.dir/list-entry.c.o cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/src && /usr/bin/cc -DG_LOG_DOMAIN=\"alarm-clock-applet\" -I/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/gio-unix-2.0 -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/arm-linux-gnueabihf/dbus-1.0/include -I/usr/include/gstreamer-1.0 -I/usr/include/libayatana-appindicator3-0.1 -I/usr/include/libayatana-indicator3-0.4 -I/usr/include/libayatana-ido3-0.4 -I/usr/include/libdbusmenu-glib-0.4 -I/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/src -g -O2 -ffile-prefix-map=/build/alarm-clock-applet-0.4.1=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wshadow -Werror=return-type -pthread -std=gnu11 -MD -MT src/CMakeFiles/alarm-clock-applet.dir/list-entry.c.o -MF CMakeFiles/alarm-clock-applet.dir/list-entry.c.o.d -o CMakeFiles/alarm-clock-applet.dir/list-entry.c.o -c /build/alarm-clock-applet-0.4.1/src/list-entry.c [ 86%] Building C object src/CMakeFiles/alarm-clock-applet.dir/alarm.c.o cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/src && /usr/bin/cc -DG_LOG_DOMAIN=\"alarm-clock-applet\" -I/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/gio-unix-2.0 -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/arm-linux-gnueabihf/dbus-1.0/include -I/usr/include/gstreamer-1.0 -I/usr/include/libayatana-appindicator3-0.1 -I/usr/include/libayatana-indicator3-0.4 -I/usr/include/libayatana-ido3-0.4 -I/usr/include/libdbusmenu-glib-0.4 -I/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/src -g -O2 -ffile-prefix-map=/build/alarm-clock-applet-0.4.1=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wshadow -Werror=return-type -pthread -std=gnu11 -MD -MT src/CMakeFiles/alarm-clock-applet.dir/alarm.c.o -MF CMakeFiles/alarm-clock-applet.dir/alarm.c.o.d -o CMakeFiles/alarm-clock-applet.dir/alarm.c.o -c /build/alarm-clock-applet-0.4.1/src/alarm.c [ 88%] Building C object src/CMakeFiles/alarm-clock-applet.dir/alarm-gsettings.c.o cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/src && /usr/bin/cc -DG_LOG_DOMAIN=\"alarm-clock-applet\" -I/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/gio-unix-2.0 -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/arm-linux-gnueabihf/dbus-1.0/include -I/usr/include/gstreamer-1.0 -I/usr/include/libayatana-appindicator3-0.1 -I/usr/include/libayatana-indicator3-0.4 -I/usr/include/libayatana-ido3-0.4 -I/usr/include/libdbusmenu-glib-0.4 -I/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/src -g -O2 -ffile-prefix-map=/build/alarm-clock-applet-0.4.1=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wshadow -Werror=return-type -pthread -std=gnu11 -MD -MT src/CMakeFiles/alarm-clock-applet.dir/alarm-gsettings.c.o -MF CMakeFiles/alarm-clock-applet.dir/alarm-gsettings.c.o.d -o CMakeFiles/alarm-clock-applet.dir/alarm-gsettings.c.o -c /build/alarm-clock-applet-0.4.1/src/alarm-gsettings.c [ 89%] Building C object src/CMakeFiles/alarm-clock-applet.dir/ui.c.o cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/src && /usr/bin/cc -DG_LOG_DOMAIN=\"alarm-clock-applet\" -I/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/gio-unix-2.0 -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/arm-linux-gnueabihf/dbus-1.0/include -I/usr/include/gstreamer-1.0 -I/usr/include/libayatana-appindicator3-0.1 -I/usr/include/libayatana-indicator3-0.4 -I/usr/include/libayatana-ido3-0.4 -I/usr/include/libdbusmenu-glib-0.4 -I/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/src -g -O2 -ffile-prefix-map=/build/alarm-clock-applet-0.4.1=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wshadow -Werror=return-type -pthread -std=gnu11 -MD -MT src/CMakeFiles/alarm-clock-applet.dir/ui.c.o -MF CMakeFiles/alarm-clock-applet.dir/ui.c.o.d -o CMakeFiles/alarm-clock-applet.dir/ui.c.o -c /build/alarm-clock-applet-0.4.1/src/ui.c [ 91%] Building C object src/CMakeFiles/alarm-clock-applet.dir/alarm-actions.c.o cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/src && /usr/bin/cc -DG_LOG_DOMAIN=\"alarm-clock-applet\" -I/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/gio-unix-2.0 -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/arm-linux-gnueabihf/dbus-1.0/include -I/usr/include/gstreamer-1.0 -I/usr/include/libayatana-appindicator3-0.1 -I/usr/include/libayatana-indicator3-0.4 -I/usr/include/libayatana-ido3-0.4 -I/usr/include/libdbusmenu-glib-0.4 -I/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/src -g -O2 -ffile-prefix-map=/build/alarm-clock-applet-0.4.1=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wshadow -Werror=return-type -pthread -std=gnu11 -MD -MT src/CMakeFiles/alarm-clock-applet.dir/alarm-actions.c.o -MF CMakeFiles/alarm-clock-applet.dir/alarm-actions.c.o.d -o CMakeFiles/alarm-clock-applet.dir/alarm-actions.c.o -c /build/alarm-clock-applet-0.4.1/src/alarm-actions.c [ 93%] Building C object src/CMakeFiles/alarm-clock-applet.dir/alarm-list-window.c.o cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/src && /usr/bin/cc -DG_LOG_DOMAIN=\"alarm-clock-applet\" -I/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/gio-unix-2.0 -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/arm-linux-gnueabihf/dbus-1.0/include -I/usr/include/gstreamer-1.0 -I/usr/include/libayatana-appindicator3-0.1 -I/usr/include/libayatana-indicator3-0.4 -I/usr/include/libayatana-ido3-0.4 -I/usr/include/libdbusmenu-glib-0.4 -I/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/src -g -O2 -ffile-prefix-map=/build/alarm-clock-applet-0.4.1=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wshadow -Werror=return-type -pthread -std=gnu11 -MD -MT src/CMakeFiles/alarm-clock-applet.dir/alarm-list-window.c.o -MF CMakeFiles/alarm-clock-applet.dir/alarm-list-window.c.o.d -o CMakeFiles/alarm-clock-applet.dir/alarm-list-window.c.o -c /build/alarm-clock-applet-0.4.1/src/alarm-list-window.c [ 94%] Building C object src/CMakeFiles/alarm-clock-applet.dir/alarm-settings.c.o cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/src && /usr/bin/cc -DG_LOG_DOMAIN=\"alarm-clock-applet\" -I/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/gio-unix-2.0 -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/arm-linux-gnueabihf/dbus-1.0/include -I/usr/include/gstreamer-1.0 -I/usr/include/libayatana-appindicator3-0.1 -I/usr/include/libayatana-indicator3-0.4 -I/usr/include/libayatana-ido3-0.4 -I/usr/include/libdbusmenu-glib-0.4 -I/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/src -g -O2 -ffile-prefix-map=/build/alarm-clock-applet-0.4.1=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wshadow -Werror=return-type -pthread -std=gnu11 -MD -MT src/CMakeFiles/alarm-clock-applet.dir/alarm-settings.c.o -MF CMakeFiles/alarm-clock-applet.dir/alarm-settings.c.o.d -o CMakeFiles/alarm-clock-applet.dir/alarm-settings.c.o -c /build/alarm-clock-applet-0.4.1/src/alarm-settings.c [ 96%] Building C object src/CMakeFiles/alarm-clock-applet.dir/prefs.c.o cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/src && /usr/bin/cc -DG_LOG_DOMAIN=\"alarm-clock-applet\" -I/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/gio-unix-2.0 -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/arm-linux-gnueabihf/dbus-1.0/include -I/usr/include/gstreamer-1.0 -I/usr/include/libayatana-appindicator3-0.1 -I/usr/include/libayatana-indicator3-0.4 -I/usr/include/libayatana-ido3-0.4 -I/usr/include/libdbusmenu-glib-0.4 -I/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/src -g -O2 -ffile-prefix-map=/build/alarm-clock-applet-0.4.1=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wshadow -Werror=return-type -pthread -std=gnu11 -MD -MT src/CMakeFiles/alarm-clock-applet.dir/prefs.c.o -MF CMakeFiles/alarm-clock-applet.dir/prefs.c.o.d -o CMakeFiles/alarm-clock-applet.dir/prefs.c.o -c /build/alarm-clock-applet-0.4.1/src/prefs.c [ 98%] Building C object src/CMakeFiles/alarm-clock-applet.dir/alarm-glib-enums.c.o cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/src && /usr/bin/cc -DG_LOG_DOMAIN=\"alarm-clock-applet\" -I/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/gio-unix-2.0 -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/arm-linux-gnueabihf/dbus-1.0/include -I/usr/include/gstreamer-1.0 -I/usr/include/libayatana-appindicator3-0.1 -I/usr/include/libayatana-indicator3-0.4 -I/usr/include/libayatana-ido3-0.4 -I/usr/include/libdbusmenu-glib-0.4 -I/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/src -g -O2 -ffile-prefix-map=/build/alarm-clock-applet-0.4.1=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wshadow -Werror=return-type -pthread -std=gnu11 -MD -MT src/CMakeFiles/alarm-clock-applet.dir/alarm-glib-enums.c.o -MF CMakeFiles/alarm-clock-applet.dir/alarm-glib-enums.c.o.d -o CMakeFiles/alarm-clock-applet.dir/alarm-glib-enums.c.o -c /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/src/alarm-glib-enums.c [100%] Linking C executable alarm-clock-applet cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/src && /usr/bin/cmake -E cmake_link_script CMakeFiles/alarm-clock-applet.dir/link.txt --verbose=1 /usr/bin/cc -g -O2 -ffile-prefix-map=/build/alarm-clock-applet-0.4.1=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,--as-needed -Wl,-z,defs -rdynamic "CMakeFiles/alarm-clock-applet.dir/alarm-applet.c.o" "CMakeFiles/alarm-clock-applet.dir/player.c.o" "CMakeFiles/alarm-clock-applet.dir/util.c.o" "CMakeFiles/alarm-clock-applet.dir/list-entry.c.o" "CMakeFiles/alarm-clock-applet.dir/alarm.c.o" "CMakeFiles/alarm-clock-applet.dir/alarm-gsettings.c.o" "CMakeFiles/alarm-clock-applet.dir/ui.c.o" "CMakeFiles/alarm-clock-applet.dir/alarm-actions.c.o" "CMakeFiles/alarm-clock-applet.dir/alarm-list-window.c.o" "CMakeFiles/alarm-clock-applet.dir/alarm-settings.c.o" "CMakeFiles/alarm-clock-applet.dir/prefs.c.o" "CMakeFiles/alarm-clock-applet.dir/alarm-glib-enums.c.o" -o alarm-clock-applet -lgtk-3 -lgdk-3 -lz -lpangocairo-1.0 -lpango-1.0 -lharfbuzz -latk-1.0 -lcairo-gobject -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0 -lgstreamer-1.0 -lgobject-2.0 -lglib-2.0 -lnotify -lgdk_pixbuf-2.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0 -layatana-appindicator3 -layatana-indicator3 -layatana-ido3-0.4 -ldbusmenu-glib -lgtk-3 -lgdk-3 -lz -lpangocairo-1.0 -lpango-1.0 -lharfbuzz -latk-1.0 -lcairo-gobject -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0 -lgstreamer-1.0 -lnotify -layatana-appindicator3 -layatana-indicator3 -layatana-ido3-0.4 -ldbusmenu-glib make[3]: Leaving directory '/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf' [100%] Built target alarm-clock-applet make[2]: Leaving directory '/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf' /usr/bin/cmake -E cmake_progress_start /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/CMakeFiles 0 make[1]: Leaving directory '/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf' create-stamp debian/debhelper-build-stamp fakeroot debian/rules binary dh binary dh_testroot dh_prep dh_auto_install cd obj-arm-linux-gnueabihf && make -j3 install DESTDIR=/build/alarm-clock-applet-0.4.1/debian/tmp AM_UPDATE_INFO_DIR=no "INSTALL=install --strip-program=true" make[1]: Entering directory '/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf' /usr/bin/cmake -S/build/alarm-clock-applet-0.4.1 -B/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf --check-build-system CMakeFiles/Makefile.cmake 0 /usr/bin/cmake -E cmake_progress_start /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/CMakeFiles /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf//CMakeFiles/progress.marks make -f CMakeFiles/Makefile2 all make[2]: Entering directory '/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf' make -f gconf-migration/CMakeFiles/alarm-clock-applet-gconf-migration.dir/build.make gconf-migration/CMakeFiles/alarm-clock-applet-gconf-migration.dir/depend make -f po/CMakeFiles/translations_1.dir/build.make po/CMakeFiles/translations_1.dir/depend make -f po/CMakeFiles/linguas.dir/build.make po/CMakeFiles/linguas.dir/depend make[3]: Entering directory '/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf' cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /build/alarm-clock-applet-0.4.1 /build/alarm-clock-applet-0.4.1/gconf-migration /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/gconf-migration /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/gconf-migration/CMakeFiles/alarm-clock-applet-gconf-migration.dir/DependInfo.cmake --color= make[3]: Entering directory '/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf' cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /build/alarm-clock-applet-0.4.1 /build/alarm-clock-applet-0.4.1/po /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po/CMakeFiles/translations_1.dir/DependInfo.cmake --color= make[3]: Entering directory '/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf' cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /build/alarm-clock-applet-0.4.1 /build/alarm-clock-applet-0.4.1/po /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po/CMakeFiles/linguas.dir/DependInfo.cmake --color= make[3]: Leaving directory '/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf' make -f po/CMakeFiles/translations_1.dir/build.make po/CMakeFiles/translations_1.dir/build make[3]: Leaving directory '/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf' make -f po/CMakeFiles/linguas.dir/build.make po/CMakeFiles/linguas.dir/build make[3]: Leaving directory '/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf' make -f gconf-migration/CMakeFiles/alarm-clock-applet-gconf-migration.dir/build.make gconf-migration/CMakeFiles/alarm-clock-applet-gconf-migration.dir/build make[3]: Entering directory '/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf' make[3]: Nothing to be done for 'po/CMakeFiles/linguas.dir/build'. make[3]: Leaving directory '/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf' [ 0%] Built target linguas make -f src/CMakeFiles/man-alarm-clock-applet.dir/build.make src/CMakeFiles/man-alarm-clock-applet.dir/depend make[3]: Entering directory '/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf' cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /build/alarm-clock-applet-0.4.1 /build/alarm-clock-applet-0.4.1/src /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/src /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/src/CMakeFiles/man-alarm-clock-applet.dir/DependInfo.cmake --color= make[3]: Leaving directory '/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf' make -f src/CMakeFiles/man-alarm-clock-applet.dir/build.make src/CMakeFiles/man-alarm-clock-applet.dir/build make[3]: Entering directory '/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf' make[3]: Nothing to be done for 'src/CMakeFiles/man-alarm-clock-applet.dir/build'. make[3]: Leaving directory '/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf' make[3]: Entering directory '/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf' make[3]: Nothing to be done for 'po/CMakeFiles/translations_1.dir/build'. make[3]: Leaving directory '/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf' [ 3%] Built target man-alarm-clock-applet [ 66%] Built target translations_1 make -f po/CMakeFiles/translations.dir/build.make po/CMakeFiles/translations.dir/depend make[3]: Entering directory '/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf' cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /build/alarm-clock-applet-0.4.1 /build/alarm-clock-applet-0.4.1/po /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/po/CMakeFiles/translations.dir/DependInfo.cmake --color= make[3]: Leaving directory '/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf' make -f po/CMakeFiles/translations.dir/build.make po/CMakeFiles/translations.dir/build make[3]: Entering directory '/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf' make[3]: Nothing to be done for 'po/CMakeFiles/translations.dir/build'. make[3]: Leaving directory '/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf' [ 66%] Built target translations make[3]: Entering directory '/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf' make[3]: Nothing to be done for 'gconf-migration/CMakeFiles/alarm-clock-applet-gconf-migration.dir/build'. make[3]: Leaving directory '/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf' [ 69%] Built target alarm-clock-applet-gconf-migration make -f src/CMakeFiles/alarm-clock-applet.dir/build.make src/CMakeFiles/alarm-clock-applet.dir/depend make[3]: Entering directory '/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf' cd /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /build/alarm-clock-applet-0.4.1 /build/alarm-clock-applet-0.4.1/src /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/src /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/src/CMakeFiles/alarm-clock-applet.dir/DependInfo.cmake --color= make[3]: Leaving directory '/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf' make -f src/CMakeFiles/alarm-clock-applet.dir/build.make src/CMakeFiles/alarm-clock-applet.dir/build make[3]: Entering directory '/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf' make[3]: Nothing to be done for 'src/CMakeFiles/alarm-clock-applet.dir/build'. make[3]: Leaving directory '/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf' [100%] Built target alarm-clock-applet make[2]: Leaving directory '/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf' /usr/bin/cmake -E cmake_progress_start /build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf/CMakeFiles 0 make -f CMakeFiles/Makefile2 preinstall make[2]: Entering directory '/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf' make[2]: Nothing to be done for 'preinstall'. make[2]: Leaving directory '/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf' Install the project... /usr/bin/cmake -P cmake_install.cmake -- Install configuration: "None" -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/bin/alarm-clock-applet-gconf-migration -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/gconf/schemas/alarm-clock.schemas (gconftool-2:22326): GConf-WARNING **: 22:47:08.841: 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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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/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 `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 `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 `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 `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 `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 `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/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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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/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 `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 `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 `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 `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/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 `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 `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 `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 `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 `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 `ja': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/timestamp', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/timestamp', locale `be': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/timestamp', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/timestamp', locale `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 `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 `ms': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/timestamp', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/timestamp', locale `ru': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/timestamp', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/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 `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 `da': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/timestamp', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/timestamp', locale `C': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/timestamp', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/timestamp', locale `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 `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 `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 `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 `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 `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 `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 `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 `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/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 `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 `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 `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/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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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/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 `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 `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 `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/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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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/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 `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 `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 `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 `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/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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `da': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/active', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/active', locale `C': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/active', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/active', locale `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 `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 `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 `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 `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 `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 `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 `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 `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/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 `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 `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 `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/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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `da': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/repeat', locale `C': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/repeat', locale `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 `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 `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 `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 `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 `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 `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 `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/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 `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 `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 `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/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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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/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 `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 `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 `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/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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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_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 `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 `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 `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 `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_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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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/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 `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 `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 `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/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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 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 `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 `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 `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 `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 -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/locale/ar/LC_MESSAGES/alarm-clock-applet.mo -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/locale/ast/LC_MESSAGES/alarm-clock-applet.mo -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/locale/be/LC_MESSAGES/alarm-clock-applet.mo -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/locale/bg/LC_MESSAGES/alarm-clock-applet.mo -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/locale/ca/LC_MESSAGES/alarm-clock-applet.mo -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/locale/cs/LC_MESSAGES/alarm-clock-applet.mo -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/locale/da/LC_MESSAGES/alarm-clock-applet.mo -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/locale/de/LC_MESSAGES/alarm-clock-applet.mo -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/locale/el/LC_MESSAGES/alarm-clock-applet.mo -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/locale/es/LC_MESSAGES/alarm-clock-applet.mo -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/locale/et/LC_MESSAGES/alarm-clock-applet.mo -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/locale/fi/LC_MESSAGES/alarm-clock-applet.mo -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/locale/fo/LC_MESSAGES/alarm-clock-applet.mo -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/locale/fr/LC_MESSAGES/alarm-clock-applet.mo -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/locale/gl/LC_MESSAGES/alarm-clock-applet.mo -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/locale/he/LC_MESSAGES/alarm-clock-applet.mo -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/locale/hi/LC_MESSAGES/alarm-clock-applet.mo -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/locale/hu/LC_MESSAGES/alarm-clock-applet.mo -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/locale/id/LC_MESSAGES/alarm-clock-applet.mo -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/locale/it/LC_MESSAGES/alarm-clock-applet.mo -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/locale/ja/LC_MESSAGES/alarm-clock-applet.mo -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/locale/ka/LC_MESSAGES/alarm-clock-applet.mo -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/locale/la/LC_MESSAGES/alarm-clock-applet.mo -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/locale/ms/LC_MESSAGES/alarm-clock-applet.mo -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/locale/nb/LC_MESSAGES/alarm-clock-applet.mo -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/locale/nl/LC_MESSAGES/alarm-clock-applet.mo -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/locale/nn/LC_MESSAGES/alarm-clock-applet.mo -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/locale/pl/LC_MESSAGES/alarm-clock-applet.mo -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/locale/pt_BR/LC_MESSAGES/alarm-clock-applet.mo -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/locale/pt/LC_MESSAGES/alarm-clock-applet.mo -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/locale/ru/LC_MESSAGES/alarm-clock-applet.mo -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/locale/si/LC_MESSAGES/alarm-clock-applet.mo -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/locale/sv/LC_MESSAGES/alarm-clock-applet.mo -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/locale/tr/LC_MESSAGES/alarm-clock-applet.mo -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/locale/uk/LC_MESSAGES/alarm-clock-applet.mo -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/locale/zh_CN/LC_MESSAGES/alarm-clock-applet.mo -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/locale/zh_TW/LC_MESSAGES/alarm-clock-applet.mo -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/bin/alarm-clock-applet -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/alarm-clock-applet/alarm-clock.ui -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/alarm-clock-applet/alarm-clock.css -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/applications/alarm-clock-applet.desktop -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/etc/xdg/autostart/alarm-clock-applet.desktop -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/glib-2.0/schemas/io.github.alarm-clock-applet.gschema.xml -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/glib-2.0/schemas/io.github.alarm-clock-applet.enums.gschema.xml Failed to create file “/usr/share/glib-2.0/schemas/gschemas.compiled.DEPE41”: Permission denied -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/icons -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/icons/hicolor -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/icons/hicolor/64x64 -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/icons/hicolor/64x64/apps -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/icons/hicolor/64x64/apps/alarm-timer.png -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/icons/hicolor/64x64/apps/alarm-clock-triggered.png -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/icons/hicolor/64x64/apps/alarm-clock.png -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/icons/hicolor/24x24 -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/icons/hicolor/24x24/apps -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/icons/hicolor/24x24/apps/alarm-timer.png -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/icons/hicolor/24x24/apps/alarm-clock-triggered.png -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/icons/hicolor/24x24/apps/alarm-clock.png -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/icons/hicolor/scalable -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/icons/hicolor/scalable/apps -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/icons/hicolor/scalable/apps/alarm-timer.svg -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/icons/hicolor/scalable/apps/alarm-clock.svg -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/icons/hicolor/scalable/apps/alarm-clock-triggered.svg -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/icons/hicolor/48x48 -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/icons/hicolor/48x48/apps -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/icons/hicolor/48x48/apps/alarm-timer.png -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/icons/hicolor/48x48/apps/alarm-clock-triggered.png -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/icons/hicolor/48x48/apps/alarm-clock.png -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/icons/hicolor/32x32 -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/icons/hicolor/32x32/apps -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/icons/hicolor/32x32/apps/alarm-timer.png -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/icons/hicolor/32x32/apps/alarm-clock-triggered.png -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/icons/hicolor/32x32/apps/alarm-clock.png -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/icons/hicolor/16x16 -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/icons/hicolor/16x16/apps -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/icons/hicolor/16x16/apps/alarm-timer.png -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/icons/hicolor/16x16/apps/alarm-clock-triggered.png -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/icons/hicolor/16x16/apps/alarm-clock.png -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/icons/hicolor/22x22 -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/icons/hicolor/22x22/apps -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/icons/hicolor/22x22/apps/alarm-timer.png -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/icons/hicolor/22x22/apps/alarm-clock-triggered.png -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/icons/hicolor/22x22/apps/alarm-clock.png -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/icons/hicolor/36x36 -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/icons/hicolor/36x36/apps -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/icons/hicolor/36x36/apps/alarm-timer.png -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/icons/hicolor/36x36/apps/alarm-clock-triggered.png -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/icons/hicolor/36x36/apps/alarm-clock.png -- Installing: /build/alarm-clock-applet-0.4.1/debian/tmp/usr/share/man/man1/alarm-clock-applet.1.gz make[1]: Leaving directory '/build/alarm-clock-applet-0.4.1/obj-arm-linux-gnueabihf' dh_install dh_installdocs debian/rules override_dh_installchangelogs make[1]: Entering directory '/build/alarm-clock-applet-0.4.1' dh_installchangelogs ChangeLog make[1]: Leaving directory '/build/alarm-clock-applet-0.4.1' dh_installman dh_installgsettings dh_icons dh_perl dh_link dh_strip_nondeterminism Normalized debian/alarm-clock-applet/usr/share/locale/hi/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/ja/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/pt_BR/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/fi/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/pt/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/gl/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/et/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/sv/LC_MESSAGES/alarm-clock-applet.mo Normalized debian/alarm-clock-applet/usr/share/locale/el/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/da/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/nb/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/hu/LC_MESSAGES/alarm-clock-applet.mo Normalized debian/alarm-clock-applet/usr/share/locale/ka/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/zh_CN/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/cs/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/la/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/he/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/es/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/ru/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/pl/LC_MESSAGES/alarm-clock-applet.mo dh_compress dh_fixperms dh_missing dh_dwz dh_strip dh_makeshlibs dh_shlibdeps dh_installdeb dh_gencontrol dh_md5sums dh_builddeb dpkg-deb: building package 'alarm-clock-applet-gconf-migration' in '../alarm-clock-applet-gconf-migration_0.4.1-3_armhf.deb'. dpkg-deb: building package 'alarm-clock-applet' in '../alarm-clock-applet_0.4.1-3_armhf.deb'. dpkg-deb: building package 'alarm-clock-applet-gconf-migration-dbgsym' in '../alarm-clock-applet-gconf-migration-dbgsym_0.4.1-3_armhf.deb'. dpkg-deb: building package 'alarm-clock-applet-dbgsym' in '../alarm-clock-applet-dbgsym_0.4.1-3_armhf.deb'. dpkg-genbuildinfo --build=binary -O../alarm-clock-applet_0.4.1-3_armhf.buildinfo dpkg-genchanges --build=binary -O../alarm-clock-applet_0.4.1-3_armhf.changes dpkg-genchanges: info: binary-only upload (no source code included) dpkg-source --after-build . dpkg-buildpackage: info: binary-only upload (no source included) dpkg-genchanges: info: not including original source code in upload I: copying local configuration I: unmounting dev/ptmx filesystem I: unmounting dev/pts filesystem I: unmounting dev/shm filesystem I: unmounting proc filesystem I: unmounting sys filesystem I: cleaning the build env I: removing directory /srv/workspace/pbuilder/322 and its subdirectories I: Current time: Tue May 9 22:50:20 -12 2023 I: pbuilder-time-stamp: 1683715820 Wed May 10 10:50:28 UTC 2023 I: 1st build successful. Starting 2nd build on remote node jtx1a-armhf-rb.debian.net. Wed May 10 10:50:28 UTC 2023 I: Preparing to do remote build '2' on jtx1a-armhf-rb.debian.net. Wed May 10 10:55:09 UTC 2023 I: Deleting $TMPDIR on jtx1a-armhf-rb.debian.net. Wed May 10 10:55:12 UTC 2023 I: alarm-clock-applet_0.4.1-3_armhf.changes: Format: 1.8 Date: Wed, 15 Feb 2023 20:56:06 +0800 Source: alarm-clock-applet Binary: alarm-clock-applet alarm-clock-applet-dbgsym alarm-clock-applet-gconf-migration alarm-clock-applet-gconf-migration-dbgsym Architecture: armhf Version: 0.4.1-3 Distribution: unstable Urgency: medium Maintainer: Chow Loong Jin Changed-By: Chow Loong Jin Description: alarm-clock-applet - alarm clock panel indicator alarm-clock-applet-gconf-migration - alarm clock panel indicator - gconf migration Changes: alarm-clock-applet (0.4.1-3) unstable; urgency=medium . * [03c7bb1] Add suggests: playerctl Checksums-Sha1: 6bd04207c1794cab0ea4c1dc5c866736fc852f50 108372 alarm-clock-applet-dbgsym_0.4.1-3_armhf.deb 1ea53bd577cba2526f048f1a4e85fc19a49b7dfb 8560 alarm-clock-applet-gconf-migration-dbgsym_0.4.1-3_armhf.deb 94d692a78faaa00500a9eab9dc75c4c55aae30e9 22348 alarm-clock-applet-gconf-migration_0.4.1-3_armhf.deb b823b4d50bf13ef8ec13c280cb891958141eeed0 16393 alarm-clock-applet_0.4.1-3_armhf.buildinfo e8c7e10d6623cbb3f01d87d34d7f064bd9237b8f 126624 alarm-clock-applet_0.4.1-3_armhf.deb Checksums-Sha256: 56c38cca6da68c54c95f00d2a078943d572ad17c381d5ed2bdaa3ddf4f6c22f4 108372 alarm-clock-applet-dbgsym_0.4.1-3_armhf.deb f8ddd0fb9e870598a486fd9dd38841d555a1ff6184e445f42fb2d953650e23eb 8560 alarm-clock-applet-gconf-migration-dbgsym_0.4.1-3_armhf.deb 3fc73fe68f9ce11dcf9a940e5afee5df18052e37a4e6dac3fbbc151a2a047946 22348 alarm-clock-applet-gconf-migration_0.4.1-3_armhf.deb 382f054221625c102033d8a8a1a4d0a8d38edf9289f2e3f259189ef8d6dfd37b 16393 alarm-clock-applet_0.4.1-3_armhf.buildinfo 1098e5d4d7b1678faf47e3489f900987610aa3a3c21c82c2ee7048cbceb12093 126624 alarm-clock-applet_0.4.1-3_armhf.deb Files: 5fe8e84ca33f5e67999a8d9d762e52b7 108372 debug optional alarm-clock-applet-dbgsym_0.4.1-3_armhf.deb fa709182b7e961c446ad8dbfdecdfd27 8560 debug optional alarm-clock-applet-gconf-migration-dbgsym_0.4.1-3_armhf.deb df008f932a11fcdc211555cda2ad403e 22348 gnome optional alarm-clock-applet-gconf-migration_0.4.1-3_armhf.deb a88e2ac4d81336fcf7f9bce286e5dbbd 16393 gnome optional alarm-clock-applet_0.4.1-3_armhf.buildinfo 60f7b8c1fb6e269c3ee4487f5198f6c3 126624 gnome optional alarm-clock-applet_0.4.1-3_armhf.deb Wed May 10 10:55:14 UTC 2023 I: diffoscope 242 will be used to compare the two builds: # Profiling output for: /usr/bin/diffoscope --timeout 7200 --html /srv/reproducible-results/rbuild-debian/r-b-build.OYK6mZEC/alarm-clock-applet_0.4.1-3.diffoscope.html --text /srv/reproducible-results/rbuild-debian/r-b-build.OYK6mZEC/alarm-clock-applet_0.4.1-3.diffoscope.txt --json /srv/reproducible-results/rbuild-debian/r-b-build.OYK6mZEC/alarm-clock-applet_0.4.1-3.diffoscope.json --profile=- /srv/reproducible-results/rbuild-debian/r-b-build.OYK6mZEC/b1/alarm-clock-applet_0.4.1-3_armhf.changes /srv/reproducible-results/rbuild-debian/r-b-build.OYK6mZEC/b2/alarm-clock-applet_0.4.1-3_armhf.changes ## command (total time: 0.000s) 0.000s 1 call cmp (internal) ## has_same_content_as (total time: 0.000s) 0.000s 1 call abc.DotChangesFile ## main (total time: 0.328s) 0.328s 2 calls outputs 0.000s 1 call cleanup ## recognizes (total time: 0.020s) 0.019s 12 calls diffoscope.comparators.binary.FilesystemFile 0.000s 10 calls abc.DotChangesFile ## specialize (total time: 0.001s) 0.001s 1 call specialize Wed May 10 10:55:16 UTC 2023 I: diffoscope 242 found no differences in the changes files, and a .buildinfo file also exists. Wed May 10 10:55:16 UTC 2023 I: alarm-clock-applet from bookworm built successfully and reproducibly on armhf. Wed May 10 10:55:17 UTC 2023 I: Submitting .buildinfo files to external archives: Wed May 10 10:55:17 UTC 2023 I: Submitting 20K b1/alarm-clock-applet_0.4.1-3_armhf.buildinfo.asc Wed May 10 10:55:19 UTC 2023 I: Submitting 20K b2/alarm-clock-applet_0.4.1-3_armhf.buildinfo.asc Wed May 10 10:55:20 UTC 2023 I: Done submitting .buildinfo files to http://buildinfo.debian.net/api/submit. Wed May 10 10:55:20 UTC 2023 I: Done submitting .buildinfo files. Wed May 10 10:55:20 UTC 2023 I: Removing signed alarm-clock-applet_0.4.1-3_armhf.buildinfo.asc files: removed './b1/alarm-clock-applet_0.4.1-3_armhf.buildinfo.asc' removed './b2/alarm-clock-applet_0.4.1-3_armhf.buildinfo.asc'