I: pbuilder: network access will be disabled during build I: Current time: Mon Apr 17 06:27:14 +14 2023 I: pbuilder-time-stamp: 1681662434 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: using eatmydata during job 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 Thu Feb 16 02:56:23 2023 +14 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/651/tmp/hooks/D01_modify_environment starting debug: Running on ionos12-i386. I: Changing host+domainname to test build reproducibility I: Adding a custom variable just for the fun of it... I: Changing /bin/sh to bash '/bin/sh' -> '/bin/bash' lrwxrwxrwx 1 root root 9 Apr 17 06:27 /bin/sh -> /bin/bash I: Setting pbuilder2's login shell to /bin/bash I: Setting pbuilder2's GECOS to second user,second room,second work-phone,second home-phone,second other I: user script /srv/workspace/pbuilder/651/tmp/hooks/D01_modify_environment finished I: user script /srv/workspace/pbuilder/651/tmp/hooks/D02_print_environment starting I: set BASH=/bin/sh BASHOPTS=checkwinsize:cmdhist:complete_fullquote:extquote:force_fignore:globasciiranges:globskipdots:hostcomplete:interactive_comments:patsub_replacement:progcomp:promptvars:sourcepath BASH_ALIASES=() BASH_ARGC=() BASH_ARGV=() BASH_CMDS=() BASH_LINENO=([0]="12" [1]="0") BASH_LOADABLES_PATH=/usr/local/lib/bash:/usr/lib/bash:/opt/local/lib/bash:/usr/pkg/lib/bash:/opt/pkg/lib/bash:. BASH_SOURCE=([0]="/tmp/hooks/D02_print_environment" [1]="/tmp/hooks/D02_print_environment") BASH_VERSINFO=([0]="5" [1]="2" [2]="15" [3]="1" [4]="release" [5]="i686-pc-linux-gnu") BASH_VERSION='5.2.15(1)-release' BUILDDIR=/build BUILDUSERGECOS='second user,second room,second work-phone,second home-phone,second other' BUILDUSERNAME=pbuilder2 BUILD_ARCH=i386 DEBIAN_FRONTEND=noninteractive DEB_BUILD_OPTIONS='buildinfo=+all reproducible=+all parallel=7' DIRSTACK=() DISTRIBUTION=bookworm EUID=0 FUNCNAME=([0]="Echo" [1]="main") GROUPS=() HOME=/root HOSTNAME=i-capture-the-hostname HOSTTYPE=i686 HOST_ARCH=i386 IFS=' ' INVOCATION_ID=7551c63dfde14505ae410d8f04b1fe27 LANG=C LANGUAGE=de_CH:de LC_ALL=C LD_LIBRARY_PATH=/usr/lib/libeatmydata LD_PRELOAD=libeatmydata.so MACHTYPE=i686-pc-linux-gnu MAIL=/var/mail/root OPTERR=1 OPTIND=1 OSTYPE=linux-gnu PATH=/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/i/capture/the/path PBCURRENTCOMMANDLINEOPERATION=build PBUILDER_OPERATION=build PBUILDER_PKGDATADIR=/usr/share/pbuilder PBUILDER_PKGLIBDIR=/usr/lib/pbuilder PBUILDER_SYSCONFDIR=/etc PIPESTATUS=([0]="0") POSIXLY_CORRECT=y PPID=651 PS4='+ ' PWD=/ SHELL=/bin/bash SHELLOPTS=braceexpand:errexit:hashall:interactive-comments:posix SHLVL=3 SUDO_COMMAND='/usr/bin/timeout -k 24.1h 24h /usr/bin/ionice -c 3 /usr/bin/nice -n 11 /usr/bin/unshare --uts -- /usr/sbin/pbuilder --build --configfile /srv/reproducible-results/rbuild-debian/r-b-build.ybBLzttT/pbuilderrc_l6CG --distribution bookworm --hookdir /etc/pbuilder/rebuild-hooks --debbuildopts -b --basetgz /var/cache/pbuilder/bookworm-reproducible-base.tgz --buildresult /srv/reproducible-results/rbuild-debian/r-b-build.ybBLzttT/b2 --logfile b2/build.log --extrapackages usrmerge alarm-clock-applet_0.4.1-3.dsc' SUDO_GID=112 SUDO_UID=107 SUDO_USER=jenkins TERM=unknown TZ=/usr/share/zoneinfo/Etc/GMT-14 UID=0 USER=root _='I: set' http_proxy=http://78.137.99.97:3128 I: uname -a Linux i-capture-the-hostname 5.10.0-21-686-pae #1 SMP Debian 5.10.162-1 (2023-01-21) i686 GNU/Linux I: ls -l /bin total 6036 -rwxr-xr-x 1 root root 1408088 Feb 13 10:21 bash -rwxr-xr-x 3 root root 38404 Sep 19 2022 bunzip2 -rwxr-xr-x 3 root root 38404 Sep 19 2022 bzcat lrwxrwxrwx 1 root root 6 Sep 19 2022 bzcmp -> bzdiff -rwxr-xr-x 1 root root 2225 Sep 19 2022 bzdiff lrwxrwxrwx 1 root root 6 Sep 19 2022 bzegrep -> bzgrep -rwxr-xr-x 1 root root 4893 Nov 28 2021 bzexe lrwxrwxrwx 1 root root 6 Sep 19 2022 bzfgrep -> bzgrep -rwxr-xr-x 1 root root 3775 Sep 19 2022 bzgrep -rwxr-xr-x 3 root root 38404 Sep 19 2022 bzip2 -rwxr-xr-x 1 root root 17892 Sep 19 2022 bzip2recover lrwxrwxrwx 1 root root 6 Sep 19 2022 bzless -> bzmore -rwxr-xr-x 1 root root 1297 Sep 19 2022 bzmore -rwxr-xr-x 1 root root 42920 Sep 21 2022 cat -rwxr-xr-x 1 root root 79816 Sep 21 2022 chgrp -rwxr-xr-x 1 root root 67496 Sep 21 2022 chmod -rwxr-xr-x 1 root root 79816 Sep 21 2022 chown -rwxr-xr-x 1 root root 162024 Sep 21 2022 cp -rwxr-xr-x 1 root root 136916 Jan 6 03:20 dash -rwxr-xr-x 1 root root 137160 Sep 21 2022 date -rwxr-xr-x 1 root root 100364 Sep 21 2022 dd -rwxr-xr-x 1 root root 108940 Sep 21 2022 df -rwxr-xr-x 1 root root 162152 Sep 21 2022 dir -rwxr-xr-x 1 root root 87760 Mar 24 00:20 dmesg lrwxrwxrwx 1 root root 8 Dec 20 03:33 dnsdomainname -> hostname lrwxrwxrwx 1 root root 8 Dec 20 03:33 domainname -> hostname -rwxr-xr-x 1 root root 38760 Sep 21 2022 echo -rwxr-xr-x 1 root root 41 Jan 25 04:43 egrep -rwxr-xr-x 1 root root 34664 Sep 21 2022 false -rwxr-xr-x 1 root root 41 Jan 25 04:43 fgrep -rwxr-xr-x 1 root root 84272 Mar 24 00:20 findmnt -rwsr-xr-x 1 root root 30240 Mar 23 22:38 fusermount -rwxr-xr-x 1 root root 218680 Jan 25 04:43 grep -rwxr-xr-x 2 root root 2346 Apr 10 2022 gunzip -rwxr-xr-x 1 root root 6447 Apr 10 2022 gzexe -rwxr-xr-x 1 root root 100952 Apr 10 2022 gzip -rwxr-xr-x 1 root root 21916 Dec 20 03:33 hostname -rwxr-xr-x 1 root root 75756 Sep 21 2022 ln -rwxr-xr-x 1 root root 55600 Mar 24 01:43 login -rwxr-xr-x 1 root root 162152 Sep 21 2022 ls -rwxr-xr-x 1 root root 214568 Mar 24 00:20 lsblk -rwxr-xr-x 1 root root 96328 Sep 21 2022 mkdir -rwxr-xr-x 1 root root 84008 Sep 21 2022 mknod -rwxr-xr-x 1 root root 38792 Sep 21 2022 mktemp -rwxr-xr-x 1 root root 63016 Mar 24 00:20 more -rwsr-xr-x 1 root root 58912 Mar 24 00:20 mount -rwxr-xr-x 1 root root 13856 Mar 24 00:20 mountpoint -rwxr-xr-x 1 root root 157932 Sep 21 2022 mv lrwxrwxrwx 1 root root 8 Dec 20 03:33 nisdomainname -> hostname lrwxrwxrwx 1 root root 14 Apr 3 20:25 pidof -> /sbin/killall5 -rwxr-xr-x 1 root root 38792 Sep 21 2022 pwd lrwxrwxrwx 1 root root 4 Feb 13 10:21 rbash -> bash -rwxr-xr-x 1 root root 51080 Sep 21 2022 readlink -rwxr-xr-x 1 root root 75720 Sep 21 2022 rm -rwxr-xr-x 1 root root 51080 Sep 21 2022 rmdir -rwxr-xr-x 1 root root 22308 Nov 3 06:31 run-parts -rwxr-xr-x 1 root root 133224 Jan 6 09:55 sed lrwxrwxrwx 1 root root 9 Apr 17 06:27 sh -> /bin/bash -rwxr-xr-x 1 root root 38760 Sep 21 2022 sleep -rwxr-xr-x 1 root root 87976 Sep 21 2022 stty -rwsr-xr-x 1 root root 83492 Mar 24 00:20 su -rwxr-xr-x 1 root root 38792 Sep 21 2022 sync -rwxr-xr-x 1 root root 598456 Apr 7 04:25 tar -rwxr-xr-x 1 root root 13860 Nov 3 06:31 tempfile -rwxr-xr-x 1 root root 120776 Sep 21 2022 touch -rwxr-xr-x 1 root root 34664 Sep 21 2022 true -rwxr-xr-x 1 root root 17892 Mar 23 22:38 ulockmgr_server -rwsr-xr-x 1 root root 30236 Mar 24 00:20 umount -rwxr-xr-x 1 root root 38760 Sep 21 2022 uname -rwxr-xr-x 2 root root 2346 Apr 10 2022 uncompress -rwxr-xr-x 1 root root 162152 Sep 21 2022 vdir -rwxr-xr-x 1 root root 71216 Mar 24 00:20 wdctl lrwxrwxrwx 1 root root 8 Dec 20 03:33 ypdomainname -> hostname -rwxr-xr-x 1 root root 1984 Apr 10 2022 zcat -rwxr-xr-x 1 root root 1678 Apr 10 2022 zcmp -rwxr-xr-x 1 root root 6460 Apr 10 2022 zdiff -rwxr-xr-x 1 root root 29 Apr 10 2022 zegrep -rwxr-xr-x 1 root root 29 Apr 10 2022 zfgrep -rwxr-xr-x 1 root root 2081 Apr 10 2022 zforce -rwxr-xr-x 1 root root 8103 Apr 10 2022 zgrep -rwxr-xr-x 1 root root 2206 Apr 10 2022 zless -rwxr-xr-x 1 root root 1842 Apr 10 2022 zmore -rwxr-xr-x 1 root root 4577 Apr 10 2022 znew I: user script /srv/workspace/pbuilder/651/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: i386 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 ... 19604 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-intel1{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} libpciaccess0{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, 368 newly installed, 0 to remove and 0 not upgraded. Need to get 186 MB of archives. After unpacking 719 MB will be used. Writing extended state information... Get: 1 http://deb.debian.org/debian bookworm/main i386 libargon2-1 i386 0~20171227-0.3 [24.1 kB] Get: 2 http://deb.debian.org/debian bookworm/main i386 dmsetup i386 2:1.02.185-2 [77.2 kB] Get: 3 http://deb.debian.org/debian bookworm/main i386 libdevmapper1.02.1 i386 2:1.02.185-2 [129 kB] Get: 4 http://deb.debian.org/debian bookworm/main i386 libjson-c5 i386 0.16-2 [46.4 kB] Get: 5 http://deb.debian.org/debian bookworm/main i386 libcryptsetup12 i386 2:2.6.1-3~deb12u1 [256 kB] Get: 6 http://deb.debian.org/debian bookworm/main i386 libfdisk1 i386 2.38.1-5+b1 [212 kB] Get: 7 http://deb.debian.org/debian bookworm/main i386 libkmod2 i386 30+20221128-1 [62.8 kB] Get: 8 http://deb.debian.org/debian bookworm/main i386 libapparmor1 i386 3.0.8-3 [42.2 kB] Get: 9 http://deb.debian.org/debian bookworm/main i386 libip4tc2 i386 1.8.9-2 [19.8 kB] Get: 10 http://deb.debian.org/debian bookworm/main i386 libsystemd-shared i386 252.6-1 [1753 kB] Get: 11 http://deb.debian.org/debian bookworm/main i386 systemd i386 252.6-1 [3025 kB] Get: 12 http://deb.debian.org/debian bookworm/main i386 systemd-sysv i386 252.6-1 [41.5 kB] Get: 13 http://deb.debian.org/debian bookworm/main i386 libdbus-1-3 i386 1.14.6-1 [213 kB] Get: 14 http://deb.debian.org/debian bookworm/main i386 dbus-bin i386 1.14.6-1 [104 kB] Get: 15 http://deb.debian.org/debian bookworm/main i386 dbus-session-bus-common all 1.14.6-1 [76.6 kB] Get: 16 http://deb.debian.org/debian bookworm/main i386 libexpat1 i386 2.5.0-1 [103 kB] Get: 17 http://deb.debian.org/debian bookworm/main i386 dbus-daemon i386 1.14.6-1 [192 kB] Get: 18 http://deb.debian.org/debian bookworm/main i386 dbus-system-bus-common all 1.14.6-1 [77.7 kB] Get: 19 http://deb.debian.org/debian bookworm/main i386 dbus i386 1.14.6-1 [97.9 kB] Get: 20 http://deb.debian.org/debian bookworm/main i386 autoconf-archive all 20220903-3 [775 kB] Get: 21 http://deb.debian.org/debian bookworm/main i386 libpython3.11-minimal i386 3.11.2-6 [813 kB] Get: 22 http://deb.debian.org/debian bookworm/main i386 python3.11-minimal i386 3.11.2-6 [2130 kB] Get: 23 http://deb.debian.org/debian bookworm/main i386 python3-minimal i386 3.11.2-1+b1 [26.3 kB] Get: 24 http://deb.debian.org/debian bookworm/main i386 media-types all 10.0.0 [26.1 kB] Get: 25 http://deb.debian.org/debian bookworm/main i386 readline-common all 8.2-1.3 [69.0 kB] Get: 26 http://deb.debian.org/debian bookworm/main i386 libreadline8 i386 8.2-1.3 [171 kB] Get: 27 http://deb.debian.org/debian bookworm/main i386 libpython3.11-stdlib i386 3.11.2-6 [1799 kB] Get: 28 http://deb.debian.org/debian bookworm/main i386 python3.11 i386 3.11.2-6 [572 kB] Get: 29 http://deb.debian.org/debian bookworm/main i386 libpython3-stdlib i386 3.11.2-1+b1 [9308 B] Get: 30 http://deb.debian.org/debian bookworm/main i386 python3 i386 3.11.2-1+b1 [26.3 kB] Get: 31 http://deb.debian.org/debian bookworm/main i386 sgml-base all 1.31 [15.4 kB] Get: 32 http://deb.debian.org/debian bookworm/main i386 netbase all 6.4 [12.8 kB] Get: 33 http://deb.debian.org/debian bookworm/main i386 libproc2-0 i386 2:4.0.2-3 [63.7 kB] Get: 34 http://deb.debian.org/debian bookworm/main i386 procps i386 2:4.0.2-3 [706 kB] Get: 35 http://deb.debian.org/debian bookworm/main i386 sensible-utils all 0.0.17+nmu1 [19.0 kB] Get: 36 http://deb.debian.org/debian bookworm/main i386 openssl i386 3.0.8-1 [1412 kB] Get: 37 http://deb.debian.org/debian bookworm/main i386 ca-certificates all 20230311 [153 kB] Get: 38 http://deb.debian.org/debian bookworm/main i386 libmagic-mgc i386 1:5.44-3 [305 kB] Get: 39 http://deb.debian.org/debian bookworm/main i386 libmagic1 i386 1:5.44-3 [114 kB] Get: 40 http://deb.debian.org/debian bookworm/main i386 file i386 1:5.44-3 [42.5 kB] Get: 41 http://deb.debian.org/debian bookworm/main i386 gettext-base i386 0.21-12 [162 kB] Get: 42 http://deb.debian.org/debian bookworm/main i386 libuchardet0 i386 0.0.7-1 [67.9 kB] Get: 43 http://deb.debian.org/debian bookworm/main i386 groff-base i386 1.22.4-10 [932 kB] Get: 44 http://deb.debian.org/debian bookworm/main i386 libpam-systemd i386 252.6-1 [231 kB] Get: 45 http://deb.debian.org/debian bookworm/main i386 bsdextrautils i386 2.38.1-5+b1 [90.3 kB] Get: 46 http://deb.debian.org/debian bookworm/main i386 libpipeline1 i386 1.5.7-1 [40.0 kB] Get: 47 http://deb.debian.org/debian bookworm/main i386 man-db i386 2.11.2-2 [1397 kB] Get: 48 http://deb.debian.org/debian bookworm/main i386 ucf all 3.0043+nmu1 [55.2 kB] Get: 49 http://deb.debian.org/debian bookworm/main i386 hicolor-icon-theme all 0.17-2 [11.4 kB] Get: 50 http://deb.debian.org/debian bookworm/main i386 libgdk-pixbuf2.0-common all 2.42.10+dfsg-1 [306 kB] Get: 51 http://deb.debian.org/debian bookworm/main i386 libglib2.0-0 i386 2.74.6-1 [1467 kB] Get: 52 http://deb.debian.org/debian bookworm/main i386 libicu72 i386 72.1-3 [9541 kB] Get: 53 http://deb.debian.org/debian bookworm/main i386 libxml2 i386 2.9.14+dfsg-1.1+b3 [720 kB] Get: 54 http://deb.debian.org/debian bookworm/main i386 shared-mime-info i386 2.2-1 [730 kB] Get: 55 http://deb.debian.org/debian bookworm/main i386 libjpeg62-turbo i386 1:2.1.5-2 [169 kB] Get: 56 http://deb.debian.org/debian bookworm/main i386 libpng16-16 i386 1.6.39-2 [283 kB] Get: 57 http://deb.debian.org/debian bookworm/main i386 libdeflate0 i386 1.14-1 [57.5 kB] Get: 58 http://deb.debian.org/debian bookworm/main i386 libjbig0 i386 2.1-6.1 [31.6 kB] Get: 59 http://deb.debian.org/debian bookworm/main i386 liblerc4 i386 4.0.0+ds-2 [181 kB] Get: 60 http://deb.debian.org/debian bookworm/main i386 libwebp7 i386 1.2.4-0.1 [293 kB] Get: 61 http://deb.debian.org/debian bookworm/main i386 libtiff6 i386 4.5.0-5 [332 kB] Get: 62 http://deb.debian.org/debian bookworm/main i386 libgdk-pixbuf-2.0-0 i386 2.42.10+dfsg-1+b1 [147 kB] Get: 63 http://deb.debian.org/debian bookworm/main i386 gtk-update-icon-cache i386 3.24.37-2 [43.9 kB] Get: 64 http://deb.debian.org/debian bookworm/main i386 adwaita-icon-theme all 43-1 [5124 kB] Get: 65 http://deb.debian.org/debian bookworm/main i386 at-spi2-common all 2.46.0-5 [162 kB] Get: 66 http://deb.debian.org/debian bookworm/main i386 m4 i386 1.4.19-3 [294 kB] Get: 67 http://deb.debian.org/debian bookworm/main i386 autoconf all 2.71-3 [332 kB] Get: 68 http://deb.debian.org/debian bookworm/main i386 autotools-dev all 20220109.1 [51.6 kB] Get: 69 http://deb.debian.org/debian bookworm/main i386 automake all 1:1.16.5-1.3 [823 kB] Get: 70 http://deb.debian.org/debian bookworm/main i386 autopoint all 0.21-12 [495 kB] Get: 71 http://deb.debian.org/debian bookworm/main i386 libarchive13 i386 3.6.2-1 [385 kB] Get: 72 http://deb.debian.org/debian bookworm/main i386 libbrotli1 i386 1.0.9-2+b6 [275 kB] Get: 73 http://deb.debian.org/debian bookworm/main i386 libsasl2-modules-db i386 2.1.28+dfsg-10 [21.4 kB] Get: 74 http://deb.debian.org/debian bookworm/main i386 libsasl2-2 i386 2.1.28+dfsg-10 [62.7 kB] Get: 75 http://deb.debian.org/debian bookworm/main i386 libldap-2.5-0 i386 2.5.13+dfsg-5 [196 kB] Get: 76 http://deb.debian.org/debian bookworm/main i386 libnghttp2-14 i386 1.52.0-1 [79.8 kB] Get: 77 http://deb.debian.org/debian bookworm/main i386 libpsl5 i386 0.21.2-1 [59.3 kB] Get: 78 http://deb.debian.org/debian bookworm/main i386 librtmp1 i386 2.4+20151223.gitfa8646d.1-2+b2 [64.3 kB] Get: 79 http://deb.debian.org/debian bookworm/main i386 libssh2-1 i386 1.10.0-3+b1 [187 kB] Get: 80 http://deb.debian.org/debian bookworm/main i386 libcurl4 i386 7.88.1-8 [419 kB] Get: 81 http://deb.debian.org/debian bookworm/main i386 libjsoncpp25 i386 1.9.5-4 [86.2 kB] Get: 82 http://deb.debian.org/debian bookworm/main i386 librhash0 i386 1.4.3-3 [149 kB] Get: 83 http://deb.debian.org/debian bookworm/main i386 libuv1 i386 1.44.2-1 [147 kB] Get: 84 http://deb.debian.org/debian bookworm/main i386 cmake-data all 3.25.1-1 [2026 kB] Get: 85 http://deb.debian.org/debian bookworm/main i386 cmake i386 3.25.1-1 [9767 kB] Get: 86 http://deb.debian.org/debian bookworm/main i386 dbus-user-session i386 1.14.6-1 [76.5 kB] Get: 87 http://deb.debian.org/debian bookworm/main i386 libdconf1 i386 0.40.0-4 [42.9 kB] Get: 88 http://deb.debian.org/debian bookworm/main i386 dconf-service i386 0.40.0-4 [34.3 kB] Get: 89 http://deb.debian.org/debian bookworm/main i386 dconf-gsettings-backend i386 0.40.0-4 [29.8 kB] Get: 90 http://deb.debian.org/debian bookworm/main i386 libdebhelper-perl all 13.11.4 [81.2 kB] Get: 91 http://deb.debian.org/debian bookworm/main i386 libtool all 2.4.7-5 [517 kB] Get: 92 http://deb.debian.org/debian bookworm/main i386 dh-autoreconf all 20 [17.1 kB] Get: 93 http://deb.debian.org/debian bookworm/main i386 libarchive-zip-perl all 1.68-1 [104 kB] Get: 94 http://deb.debian.org/debian bookworm/main i386 libsub-override-perl all 0.09-4 [9304 B] Get: 95 http://deb.debian.org/debian bookworm/main i386 libfile-stripnondeterminism-perl all 1.13.1-1 [19.4 kB] Get: 96 http://deb.debian.org/debian bookworm/main i386 dh-strip-nondeterminism all 1.13.1-1 [8620 B] Get: 97 http://deb.debian.org/debian bookworm/main i386 libelf1 i386 0.188-2.1 [179 kB] Get: 98 http://deb.debian.org/debian bookworm/main i386 dwz i386 0.15-1 [118 kB] Get: 99 http://deb.debian.org/debian bookworm/main i386 gettext i386 0.21-12 [1311 kB] Get: 100 http://deb.debian.org/debian bookworm/main i386 intltool-debian all 0.35.0+20060710.6 [22.9 kB] Get: 101 http://deb.debian.org/debian bookworm/main i386 po-debconf all 1.0.21+nmu1 [248 kB] Get: 102 http://deb.debian.org/debian bookworm/main i386 debhelper all 13.11.4 [942 kB] Get: 103 http://deb.debian.org/debian bookworm/main i386 libfreetype6 i386 2.12.1+dfsg-4 [410 kB] Get: 104 http://deb.debian.org/debian bookworm/main i386 fonts-dejavu-core all 2.37-6 [1068 kB] Get: 105 http://deb.debian.org/debian bookworm/main i386 fontconfig-config i386 2.14.1-4 [315 kB] Get: 106 http://deb.debian.org/debian bookworm/main i386 libfontconfig1 i386 2.14.1-4 [398 kB] Get: 107 http://deb.debian.org/debian bookworm/main i386 fontconfig i386 2.14.1-4 [450 kB] Get: 108 http://deb.debian.org/debian bookworm/main i386 libdbus-glib-1-2 i386 0.112-3 [64.5 kB] Get: 109 http://deb.debian.org/debian bookworm/main i386 gconf2-common all 3.2.6-8 [1025 kB] Get: 110 http://deb.debian.org/debian bookworm/main i386 libgconf-2-4 i386 3.2.6-8 [418 kB] Get: 111 http://deb.debian.org/debian bookworm/main i386 gconf-service i386 3.2.6-8 [406 kB] Get: 112 http://deb.debian.org/debian bookworm/main i386 psmisc i386 23.6-1 [260 kB] Get: 113 http://deb.debian.org/debian bookworm/main i386 gconf2 i386 3.2.6-8 [416 kB] Get: 114 http://deb.debian.org/debian bookworm/main i386 libgirepository-1.0-1 i386 1.74.0-3 [108 kB] Get: 115 http://deb.debian.org/debian bookworm/main i386 gir1.2-glib-2.0 i386 1.74.0-3 [159 kB] Get: 116 http://deb.debian.org/debian bookworm/main i386 libatk1.0-0 i386 2.46.0-5 [49.4 kB] Get: 117 http://deb.debian.org/debian bookworm/main i386 gir1.2-atk-1.0 i386 2.46.0-5 [23.7 kB] Get: 118 http://deb.debian.org/debian bookworm/main i386 gir1.2-freedesktop i386 1.74.0-3 [37.2 kB] Get: 119 http://deb.debian.org/debian bookworm/main i386 libxau6 i386 1:1.0.9-1 [20.0 kB] Get: 120 http://deb.debian.org/debian bookworm/main i386 libbsd0 i386 0.11.7-2 [121 kB] Get: 121 http://deb.debian.org/debian bookworm/main i386 libxdmcp6 i386 1:1.1.2-3 [26.7 kB] Get: 122 http://deb.debian.org/debian bookworm/main i386 libxcb1 i386 1.15-1 [148 kB] Get: 123 http://deb.debian.org/debian bookworm/main i386 libx11-data all 2:1.8.4-2 [292 kB] Get: 124 http://deb.debian.org/debian bookworm/main i386 libx11-6 i386 2:1.8.4-2 [782 kB] Get: 125 http://deb.debian.org/debian bookworm/main i386 libxext6 i386 2:1.3.4-1+b1 [55.3 kB] Get: 126 http://deb.debian.org/debian bookworm/main i386 libxi6 i386 2:1.8-1+b1 [86.2 kB] Get: 127 http://deb.debian.org/debian bookworm/main i386 libatspi2.0-0 i386 2.46.0-5 [79.1 kB] Get: 128 http://deb.debian.org/debian bookworm/main i386 gir1.2-atspi-2.0 i386 2.46.0-5 [20.6 kB] Get: 129 http://deb.debian.org/debian bookworm/main i386 gir1.2-gdkpixbuf-2.0 i386 2.42.10+dfsg-1+b1 [13.5 kB] Get: 130 http://deb.debian.org/debian bookworm/main i386 gir1.2-harfbuzz-0.0 i386 6.0.0+dfsg-3 [1579 kB] Get: 131 http://deb.debian.org/debian bookworm/main i386 libfribidi0 i386 1.0.8-2.1 [65.6 kB] Get: 132 http://deb.debian.org/debian bookworm/main i386 libgraphite2-3 i386 1.3.14-1 [84.0 kB] Get: 133 http://deb.debian.org/debian bookworm/main i386 libharfbuzz0b i386 6.0.0+dfsg-3 [1966 kB] Get: 134 http://deb.debian.org/debian bookworm/main i386 libthai-data all 0.1.29-1 [176 kB] Get: 135 http://deb.debian.org/debian bookworm/main i386 libdatrie1 i386 0.2.13-2+b1 [45.0 kB] Get: 136 http://deb.debian.org/debian bookworm/main i386 libthai0 i386 0.1.29-1 [58.6 kB] Get: 137 http://deb.debian.org/debian bookworm/main i386 libpango-1.0-0 i386 1.50.12+ds-1 [220 kB] Get: 138 http://deb.debian.org/debian bookworm/main i386 libpixman-1-0 i386 0.42.2-1 [548 kB] Get: 139 http://deb.debian.org/debian bookworm/main i386 libxcb-render0 i386 1.15-1 [116 kB] Get: 140 http://deb.debian.org/debian bookworm/main i386 libxcb-shm0 i386 1.15-1 [106 kB] Get: 141 http://deb.debian.org/debian bookworm/main i386 libxrender1 i386 1:0.9.10-1.1 [34.1 kB] Get: 142 http://deb.debian.org/debian bookworm/main i386 libcairo2 i386 1.16.0-7 [627 kB] Get: 143 http://deb.debian.org/debian bookworm/main i386 libpangoft2-1.0-0 i386 1.50.12+ds-1 [50.5 kB] Get: 144 http://deb.debian.org/debian bookworm/main i386 libpangocairo-1.0-0 i386 1.50.12+ds-1 [35.4 kB] Get: 145 http://deb.debian.org/debian bookworm/main i386 libxft2 i386 2.3.6-1 [62.8 kB] Get: 146 http://deb.debian.org/debian bookworm/main i386 libpangoxft-1.0-0 i386 1.50.12+ds-1 [27.4 kB] Get: 147 http://deb.debian.org/debian bookworm/main i386 gir1.2-pango-1.0 i386 1.50.12+ds-1 [37.4 kB] Get: 148 http://deb.debian.org/debian bookworm/main i386 libatk-bridge2.0-0 i386 2.46.0-5 [69.8 kB] Get: 149 http://deb.debian.org/debian bookworm/main i386 libcairo-gobject2 i386 1.16.0-7 [111 kB] Get: 150 http://deb.debian.org/debian bookworm/main i386 liblcms2-2 i386 2.14-2 [165 kB] Get: 151 http://deb.debian.org/debian bookworm/main i386 libcolord2 i386 1.4.6-2.2 [144 kB] Get: 152 http://deb.debian.org/debian bookworm/main i386 libavahi-common-data i386 0.8-9 [107 kB] Get: 153 http://deb.debian.org/debian bookworm/main i386 libavahi-common3 i386 0.8-9 [43.3 kB] Get: 154 http://deb.debian.org/debian bookworm/main i386 libavahi-client3 i386 0.8-9 [47.3 kB] Get: 155 http://deb.debian.org/debian bookworm/main i386 libcups2 i386 2.4.2-3 [261 kB] Get: 156 http://deb.debian.org/debian bookworm/main i386 libepoxy0 i386 1.5.10-1 [198 kB] Get: 157 http://deb.debian.org/debian bookworm/main i386 libwayland-client0 i386 1.21.0-1 [29.0 kB] Get: 158 http://deb.debian.org/debian bookworm/main i386 libwayland-cursor0 i386 1.21.0-1 [15.0 kB] Get: 159 http://deb.debian.org/debian bookworm/main i386 libwayland-egl1 i386 1.21.0-1 [8740 B] Get: 160 http://deb.debian.org/debian bookworm/main i386 libxcomposite1 i386 1:0.4.5-1 [16.9 kB] Get: 161 http://deb.debian.org/debian bookworm/main i386 libxfixes3 i386 1:6.0.0-2 [23.0 kB] Get: 162 http://deb.debian.org/debian bookworm/main i386 libxcursor1 i386 1:1.2.1-1 [42.4 kB] Get: 163 http://deb.debian.org/debian bookworm/main i386 libxdamage1 i386 1:1.1.6-1 [15.3 kB] Get: 164 http://deb.debian.org/debian bookworm/main i386 libxinerama1 i386 2:1.1.4-3 [18.1 kB] Get: 165 http://deb.debian.org/debian bookworm/main i386 xkb-data all 2.35.1-1 [764 kB] Get: 166 http://deb.debian.org/debian bookworm/main i386 libxkbcommon0 i386 1.5.0-1 [112 kB] Get: 167 http://deb.debian.org/debian bookworm/main i386 libxrandr2 i386 2:1.5.2-2+b1 [40.8 kB] Get: 168 http://deb.debian.org/debian bookworm/main i386 libgtk-3-common all 3.24.37-2 [3891 kB] Get: 169 http://deb.debian.org/debian bookworm/main i386 libgtk-3-0 i386 3.24.37-2 [3045 kB] Get: 170 http://deb.debian.org/debian bookworm/main i386 gir1.2-gtk-3.0 i386 3.24.37-2 [219 kB] Get: 171 http://deb.debian.org/debian bookworm/main i386 libayatana-ido3-0.4-0 i386 0.9.3-1 [61.1 kB] Get: 172 http://deb.debian.org/debian bookworm/main i386 libayatana-indicator3-7 i386 0.9.3-1 [34.5 kB] Get: 173 http://deb.debian.org/debian bookworm/main i386 libdbusmenu-glib4 i386 18.10.20180917~bzr492+repack1-3 [45.1 kB] Get: 174 http://deb.debian.org/debian bookworm/main i386 libdbusmenu-gtk3-4 i386 18.10.20180917~bzr492+repack1-3 [31.6 kB] Get: 175 http://deb.debian.org/debian bookworm/main i386 libayatana-appindicator3-1 i386 0.5.92-1 [25.1 kB] Get: 176 http://deb.debian.org/debian bookworm/main i386 gir1.2-ayatanaappindicator3-0.1 i386 0.5.92-1 [9024 B] Get: 177 http://deb.debian.org/debian bookworm/main i386 gir1.2-ayatanaido3-0.4 i386 0.9.3-1 [9108 B] Get: 178 http://deb.debian.org/debian bookworm/main i386 gir1.2-dbusmenu-glib-0.4 i386 18.10.20180917~bzr492+repack1-3 [7616 B] Get: 179 http://deb.debian.org/debian bookworm/main i386 gir1.2-gconf-2.0 i386 3.2.6-8 [349 kB] Get: 180 http://deb.debian.org/debian bookworm/main i386 libdw1 i386 0.188-2.1 [265 kB] Get: 181 http://deb.debian.org/debian bookworm/main i386 libunwind8 i386 1.6.2-3 [49.0 kB] Get: 182 http://deb.debian.org/debian bookworm/main i386 libcap2-bin i386 1:2.66-3 [34.6 kB] Get: 183 http://deb.debian.org/debian bookworm/main i386 libgstreamer1.0-0 i386 1.22.0-2 [1220 kB] Get: 184 http://deb.debian.org/debian bookworm/main i386 gir1.2-gstreamer-1.0 i386 1.22.0-2 [105 kB] Get: 185 http://deb.debian.org/debian bookworm/main i386 libgtk2.0-common all 2.24.33-2 [2700 kB] Get: 186 http://deb.debian.org/debian bookworm/main i386 librsvg2-2 i386 2.54.5+dfsg-1 [2753 kB] Get: 187 http://deb.debian.org/debian bookworm/main i386 librsvg2-common i386 2.54.5+dfsg-1 [34.2 kB] Get: 188 http://deb.debian.org/debian bookworm/main i386 gnome-icon-theme all 3.12.0-5 [9867 kB] Get: 189 http://deb.debian.org/debian bookworm/main i386 libgtk2.0-0 i386 2.24.33-2 [1970 kB] Get: 190 http://deb.debian.org/debian bookworm/main i386 gir1.2-gtk-2.0 i386 2.24.33-2 [215 kB] Get: 191 http://deb.debian.org/debian bookworm/main i386 libnotify4 i386 0.8.1-1 [30.9 kB] Get: 192 http://deb.debian.org/debian bookworm/main i386 gir1.2-notify-0.7 i386 0.8.1-1 [11.6 kB] Get: 193 http://deb.debian.org/debian bookworm/main i386 libpkgconf3 i386 1.8.1-1 [38.3 kB] Get: 194 http://deb.debian.org/debian bookworm/main i386 pkgconf-bin i386 1.8.1-1 [29.8 kB] Get: 195 http://deb.debian.org/debian bookworm/main i386 pkgconf i386 1.8.1-1 [25.9 kB] Get: 196 http://deb.debian.org/debian bookworm/main i386 pkg-config i386 1.8.1-1 [13.7 kB] Get: 197 http://deb.debian.org/debian bookworm/main i386 libregexp-ipv6-perl all 0.03-3 [5212 B] Get: 198 http://deb.debian.org/debian bookworm/main i386 liburi-perl all 5.17-1 [90.4 kB] Get: 199 http://deb.debian.org/debian bookworm/main i386 libencode-locale-perl all 1.05-3 [12.9 kB] Get: 200 http://deb.debian.org/debian bookworm/main i386 libtimedate-perl all 2.3300-2 [39.3 kB] Get: 201 http://deb.debian.org/debian bookworm/main i386 libhttp-date-perl all 6.05-2 [10.5 kB] Get: 202 http://deb.debian.org/debian bookworm/main i386 libfile-listing-perl all 6.15-1 [12.6 kB] Get: 203 http://deb.debian.org/debian bookworm/main i386 libhtml-tagset-perl all 3.20-6 [11.7 kB] Get: 204 http://deb.debian.org/debian bookworm/main i386 libhtml-parser-perl i386 3.81-1 [102 kB] Get: 205 http://deb.debian.org/debian bookworm/main i386 libhtml-tree-perl all 5.07-3 [211 kB] Get: 206 http://deb.debian.org/debian bookworm/main i386 libclone-perl i386 0.46-1 [13.8 kB] Get: 207 http://deb.debian.org/debian bookworm/main i386 libio-html-perl all 1.004-3 [16.2 kB] Get: 208 http://deb.debian.org/debian bookworm/main i386 liblwp-mediatypes-perl all 6.04-2 [20.2 kB] Get: 209 http://deb.debian.org/debian bookworm/main i386 libhttp-message-perl all 6.44-1 [81.7 kB] Get: 210 http://deb.debian.org/debian bookworm/main i386 libhttp-cookies-perl all 6.10-1 [19.6 kB] Get: 211 http://deb.debian.org/debian bookworm/main i386 libhttp-negotiate-perl all 6.01-2 [13.1 kB] Get: 212 http://deb.debian.org/debian bookworm/main i386 perl-openssl-defaults i386 7+b1 [7920 B] Get: 213 http://deb.debian.org/debian bookworm/main i386 libnet-ssleay-perl i386 1.92-2+b1 [318 kB] Get: 214 http://deb.debian.org/debian bookworm/main i386 libio-socket-ssl-perl all 2.081-2 [219 kB] Get: 215 http://deb.debian.org/debian bookworm/main i386 libnet-http-perl all 6.22-1 [25.3 kB] Get: 216 http://deb.debian.org/debian bookworm/main i386 liblwp-protocol-https-perl all 6.10-1 [12.2 kB] Get: 217 http://deb.debian.org/debian bookworm/main i386 libtry-tiny-perl all 0.31-2 [22.6 kB] Get: 218 http://deb.debian.org/debian bookworm/main i386 libwww-robotrules-perl all 6.02-1 [12.9 kB] Get: 219 http://deb.debian.org/debian bookworm/main i386 libwww-perl all 6.68-1 [186 kB] Get: 220 http://deb.debian.org/debian bookworm/main i386 libxml-parser-perl i386 2.46-4 [202 kB] Get: 221 http://deb.debian.org/debian bookworm/main i386 intltool all 0.51.0-6 [50.8 kB] Get: 222 http://deb.debian.org/debian bookworm/main i386 gnome-common all 3.18.0-4 [134 kB] Get: 223 http://deb.debian.org/debian bookworm/main i386 icu-devtools i386 72.1-3 [214 kB] Get: 224 http://deb.debian.org/debian bookworm/main i386 libffi-dev i386 3.4.4-1 [57.3 kB] Get: 225 http://deb.debian.org/debian bookworm/main i386 libglib2.0-data all 2.74.6-1 [1208 kB] Get: 226 http://deb.debian.org/debian bookworm/main i386 libglib2.0-bin i386 2.74.6-1 [113 kB] Get: 227 http://deb.debian.org/debian bookworm/main i386 python3-lib2to3 all 3.11.2-2 [76.2 kB] Get: 228 http://deb.debian.org/debian bookworm/main i386 python3-distutils all 3.11.2-2 [131 kB] Get: 229 http://deb.debian.org/debian bookworm/main i386 libglib2.0-dev-bin i386 2.74.6-1 [151 kB] Get: 230 http://deb.debian.org/debian bookworm/main i386 uuid-dev i386 2.38.1-5+b1 [40.2 kB] Get: 231 http://deb.debian.org/debian bookworm/main i386 libblkid-dev i386 2.38.1-5+b1 [202 kB] Get: 232 http://deb.debian.org/debian bookworm/main i386 libsepol-dev i386 3.4-2 [392 kB] Get: 233 http://deb.debian.org/debian bookworm/main i386 libpcre2-16-0 i386 10.42-1 [243 kB] Get: 234 http://deb.debian.org/debian bookworm/main i386 libpcre2-32-0 i386 10.42-1 [232 kB] Get: 235 http://deb.debian.org/debian bookworm/main i386 libpcre2-posix3 i386 10.42-1 [55.4 kB] Get: 236 http://deb.debian.org/debian bookworm/main i386 libpcre2-dev i386 10.42-1 [761 kB] Get: 237 http://deb.debian.org/debian bookworm/main i386 libselinux1-dev i386 3.4-1+b5 [165 kB] Get: 238 http://deb.debian.org/debian bookworm/main i386 libmount-dev i386 2.38.1-5+b1 [22.5 kB] Get: 239 http://deb.debian.org/debian bookworm/main i386 zlib1g-dev i386 1:1.2.13.dfsg-1 [913 kB] Get: 240 http://deb.debian.org/debian bookworm/main i386 libglib2.0-dev i386 2.74.6-1 [1718 kB] Get: 241 http://deb.debian.org/debian bookworm/main i386 libatk1.0-dev i386 2.46.0-5 [103 kB] Get: 242 http://deb.debian.org/debian bookworm/main i386 xml-core all 0.18+nmu1 [23.8 kB] Get: 243 http://deb.debian.org/debian bookworm/main i386 libdbus-1-dev i386 1.14.6-1 [257 kB] Get: 244 http://deb.debian.org/debian bookworm/main i386 x11-common all 1:7.7+23 [252 kB] Get: 245 http://deb.debian.org/debian bookworm/main i386 libxtst6 i386 2:1.2.3-1.1 [28.6 kB] Get: 246 http://deb.debian.org/debian bookworm/main i386 xorg-sgml-doctools all 1:1.11-1.1 [22.1 kB] Get: 247 http://deb.debian.org/debian bookworm/main i386 x11proto-dev all 2022.1-1 [599 kB] Get: 248 http://deb.debian.org/debian bookworm/main i386 libxau-dev i386 1:1.0.9-1 [23.3 kB] Get: 249 http://deb.debian.org/debian bookworm/main i386 libxdmcp-dev i386 1:1.1.2-3 [42.7 kB] Get: 250 http://deb.debian.org/debian bookworm/main i386 xtrans-dev all 1.4.0-1 [98.7 kB] Get: 251 http://deb.debian.org/debian bookworm/main i386 libpthread-stubs0-dev i386 0.4-1 [5340 B] Get: 252 http://deb.debian.org/debian bookworm/main i386 libxcb1-dev i386 1.15-1 [185 kB] Get: 253 http://deb.debian.org/debian bookworm/main i386 libx11-dev i386 2:1.8.4-2 [866 kB] Get: 254 http://deb.debian.org/debian bookworm/main i386 libxext-dev i386 2:1.3.4-1+b1 [110 kB] Get: 255 http://deb.debian.org/debian bookworm/main i386 libxfixes-dev i386 1:6.0.0-2 [25.3 kB] Get: 256 http://deb.debian.org/debian bookworm/main i386 libxi-dev i386 2:1.8-1+b1 [249 kB] Get: 257 http://deb.debian.org/debian bookworm/main i386 libxtst-dev i386 2:1.2.3-1.1 [32.9 kB] Get: 258 http://deb.debian.org/debian bookworm/main i386 libatspi2.0-dev i386 2.46.0-5 [76.3 kB] Get: 259 http://deb.debian.org/debian bookworm/main i386 libatk-bridge2.0-dev i386 2.46.0-5 [8212 B] Get: 260 http://deb.debian.org/debian bookworm/main i386 liblzo2-2 i386 2.10-2 [59.7 kB] Get: 261 http://deb.debian.org/debian bookworm/main i386 libcairo-script-interpreter2 i386 1.16.0-7 [153 kB] Get: 262 http://deb.debian.org/debian bookworm/main i386 libexpat1-dev i386 2.5.0-1 [158 kB] Get: 263 http://deb.debian.org/debian bookworm/main i386 libbrotli-dev i386 1.0.9-2+b6 [287 kB] Get: 264 http://deb.debian.org/debian bookworm/main i386 libpng-dev i386 1.6.39-2 [367 kB] Get: 265 http://deb.debian.org/debian bookworm/main i386 libfreetype-dev i386 2.12.1+dfsg-4 [585 kB] Get: 266 http://deb.debian.org/debian bookworm/main i386 libfontconfig-dev i386 2.14.1-4 [425 kB] Get: 267 http://deb.debian.org/debian bookworm/main i386 libpixman-1-dev i386 0.42.2-1 [573 kB] Get: 268 http://deb.debian.org/debian bookworm/main i386 libice6 i386 2:1.0.10-1 [60.8 kB] Get: 269 http://deb.debian.org/debian bookworm/main i386 libsm6 i386 2:1.2.3-1 [35.7 kB] Get: 270 http://deb.debian.org/debian bookworm/main i386 libice-dev i386 2:1.0.10-1 [70.5 kB] Get: 271 http://deb.debian.org/debian bookworm/main i386 libsm-dev i386 2:1.2.3-1 [38.8 kB] Get: 272 http://deb.debian.org/debian bookworm/main i386 libxcb-render0-dev i386 1.15-1 [119 kB] Get: 273 http://deb.debian.org/debian bookworm/main i386 libxcb-shm0-dev i386 1.15-1 [107 kB] Get: 274 http://deb.debian.org/debian bookworm/main i386 libxrender-dev i386 1:0.9.10-1.1 [42.3 kB] Get: 275 http://deb.debian.org/debian bookworm/main i386 libcairo2-dev i386 1.16.0-7 [800 kB] Get: 276 http://deb.debian.org/debian bookworm/main i386 libglvnd0 i386 1.6.0-1 [42.7 kB] Get: 277 http://deb.debian.org/debian bookworm/main i386 libdrm-common all 2.4.114-1 [7112 B] Get: 278 http://deb.debian.org/debian bookworm/main i386 libdrm2 i386 2.4.114-1+b1 [40.8 kB] Get: 279 http://deb.debian.org/debian bookworm/main i386 libwayland-server0 i386 1.21.0-1 [37.4 kB] Get: 280 http://deb.debian.org/debian bookworm/main i386 libgbm1 i386 22.3.6-1+deb12u1 [39.2 kB] Get: 281 http://deb.debian.org/debian bookworm/main i386 libglapi-mesa i386 22.3.6-1+deb12u1 [35.6 kB] Get: 282 http://deb.debian.org/debian bookworm/main i386 libx11-xcb1 i386 2:1.8.4-2 [192 kB] Get: 283 http://deb.debian.org/debian bookworm/main i386 libxcb-dri2-0 i386 1.15-1 [107 kB] Get: 284 http://deb.debian.org/debian bookworm/main i386 libxcb-dri3-0 i386 1.15-1 [107 kB] Get: 285 http://deb.debian.org/debian bookworm/main i386 libxcb-present0 i386 1.15-1 [106 kB] Get: 286 http://deb.debian.org/debian bookworm/main i386 libxcb-randr0 i386 1.15-1 [118 kB] Get: 287 http://deb.debian.org/debian bookworm/main i386 libxcb-sync1 i386 1.15-1 [109 kB] Get: 288 http://deb.debian.org/debian bookworm/main i386 libxcb-xfixes0 i386 1.15-1 [110 kB] Get: 289 http://deb.debian.org/debian bookworm/main i386 libxshmfence1 i386 1.3-1 [8976 B] Get: 290 http://deb.debian.org/debian bookworm/main i386 libegl-mesa0 i386 22.3.6-1+deb12u1 [124 kB] Get: 291 http://deb.debian.org/debian bookworm/main i386 libegl1 i386 1.6.0-1 [35.6 kB] Get: 292 http://deb.debian.org/debian bookworm/main i386 libxcb-glx0 i386 1.15-1 [124 kB] Get: 293 http://deb.debian.org/debian bookworm/main i386 libxxf86vm1 i386 1:1.1.4-1+b2 [21.7 kB] Get: 294 http://deb.debian.org/debian bookworm/main i386 libdrm-amdgpu1 i386 2.4.114-1+b1 [24.1 kB] Get: 295 http://deb.debian.org/debian bookworm/main i386 libpciaccess0 i386 0.17-2 [53.4 kB] Get: 296 http://deb.debian.org/debian bookworm/main i386 libdrm-intel1 i386 2.4.114-1+b1 [67.9 kB] Get: 297 http://deb.debian.org/debian bookworm/main i386 libdrm-nouveau2 i386 2.4.114-1+b1 [20.7 kB] Get: 298 http://deb.debian.org/debian bookworm/main i386 libdrm-radeon1 i386 2.4.114-1+b1 [22.8 kB] Get: 299 http://deb.debian.org/debian bookworm/main i386 libedit2 i386 3.1-20221030-2 [97.2 kB] Get: 300 http://deb.debian.org/debian bookworm/main i386 libz3-4 i386 4.8.12-3.1 [7853 kB] Get: 301 http://deb.debian.org/debian bookworm/main i386 libllvm15 i386 1:15.0.6-4+b1 [26.5 MB] Get: 302 http://deb.debian.org/debian bookworm/main i386 libsensors-config all 1:3.6.0-7.1 [14.3 kB] Get: 303 http://deb.debian.org/debian bookworm/main i386 libsensors5 i386 1:3.6.0-7.1 [35.1 kB] Get: 304 http://deb.debian.org/debian bookworm/main i386 libgl1-mesa-dri i386 22.3.6-1+deb12u1 [7417 kB] Get: 305 http://deb.debian.org/debian bookworm/main i386 libglx-mesa0 i386 22.3.6-1+deb12u1 [156 kB] Get: 306 http://deb.debian.org/debian bookworm/main i386 libglx0 i386 1.6.0-1 [36.6 kB] Get: 307 http://deb.debian.org/debian bookworm/main i386 libgl1 i386 1.6.0-1 [82.1 kB] Get: 308 http://deb.debian.org/debian bookworm/main i386 libglx-dev i386 1.6.0-1 [15.3 kB] Get: 309 http://deb.debian.org/debian bookworm/main i386 libgl-dev i386 1.6.0-1 [100 kB] Get: 310 http://deb.debian.org/debian bookworm/main i386 libegl-dev i386 1.6.0-1 [19.1 kB] Get: 311 http://deb.debian.org/debian bookworm/main i386 libglvnd-core-dev i386 1.6.0-1 [12.9 kB] Get: 312 http://deb.debian.org/debian bookworm/main i386 libgles1 i386 1.6.0-1 [11.6 kB] Get: 313 http://deb.debian.org/debian bookworm/main i386 libgles2 i386 1.6.0-1 [16.3 kB] Get: 314 http://deb.debian.org/debian bookworm/main i386 libgles-dev i386 1.6.0-1 [50.4 kB] Get: 315 http://deb.debian.org/debian bookworm/main i386 libopengl0 i386 1.6.0-1 [29.2 kB] Get: 316 http://deb.debian.org/debian bookworm/main i386 libopengl-dev i386 1.6.0-1 [4924 B] Get: 317 http://deb.debian.org/debian bookworm/main i386 libglvnd-dev i386 1.6.0-1 [4688 B] Get: 318 http://deb.debian.org/debian bookworm/main i386 libegl1-mesa-dev i386 22.3.6-1+deb12u1 [18.5 kB] Get: 319 http://deb.debian.org/debian bookworm/main i386 libepoxy-dev i386 1.5.10-1 [128 kB] Get: 320 http://deb.debian.org/debian bookworm/main i386 libfribidi-dev i386 1.0.8-2.1 [106 kB] Get: 321 http://deb.debian.org/debian bookworm/main i386 libgdk-pixbuf2.0-bin i386 2.42.10+dfsg-1+b1 [18.0 kB] Get: 322 http://deb.debian.org/debian bookworm/main i386 libjpeg62-turbo-dev i386 1:2.1.5-2 [304 kB] Get: 323 http://deb.debian.org/debian bookworm/main i386 libjpeg-dev i386 1:2.1.5-2 [71.8 kB] Get: 324 http://deb.debian.org/debian bookworm/main i386 libjbig-dev i386 2.1-6.1 [30.9 kB] Get: 325 http://deb.debian.org/debian bookworm/main i386 liblzma-dev i386 5.4.1-0.2 [272 kB] Get: 326 http://deb.debian.org/debian bookworm/main i386 libzstd-dev i386 1.5.4+dfsg2-5 [338 kB] Get: 327 http://deb.debian.org/debian bookworm/main i386 libwebpmux3 i386 1.2.4-0.1 [111 kB] Get: 328 http://deb.debian.org/debian bookworm/main i386 libwebpdemux2 i386 1.2.4-0.1 [99.7 kB] Get: 329 http://deb.debian.org/debian bookworm/main i386 libwebp-dev i386 1.2.4-0.1 [414 kB] Get: 330 http://deb.debian.org/debian bookworm/main i386 libtiffxx6 i386 4.5.0-5 [144 kB] Get: 331 http://deb.debian.org/debian bookworm/main i386 libdeflate-dev i386 1.14-1 [53.5 kB] Get: 332 http://deb.debian.org/debian bookworm/main i386 liblerc-dev i386 4.0.0+ds-2 [193 kB] Get: 333 http://deb.debian.org/debian bookworm/main i386 libtiff-dev i386 4.5.0-5 [479 kB] Get: 334 http://deb.debian.org/debian bookworm/main i386 libgdk-pixbuf-2.0-dev i386 2.42.10+dfsg-1+b1 [51.7 kB] Get: 335 http://deb.debian.org/debian bookworm/main i386 libharfbuzz-icu0 i386 6.0.0+dfsg-3 [1557 kB] Get: 336 http://deb.debian.org/debian bookworm/main i386 libharfbuzz-gobject0 i386 6.0.0+dfsg-3 [1570 kB] Get: 337 http://deb.debian.org/debian bookworm/main i386 libharfbuzz-subset0 i386 6.0.0+dfsg-3 [1956 kB] Get: 338 http://deb.debian.org/debian bookworm/main i386 libgraphite2-dev i386 1.3.14-1 [24.0 kB] Get: 339 http://deb.debian.org/debian bookworm/main i386 libicu-dev i386 72.1-3 [10.6 MB] Get: 340 http://deb.debian.org/debian bookworm/main i386 libharfbuzz-dev i386 6.0.0+dfsg-3 [1668 kB] Get: 341 http://deb.debian.org/debian bookworm/main i386 libdatrie-dev i386 0.2.13-2+b1 [20.5 kB] Get: 342 http://deb.debian.org/debian bookworm/main i386 libthai-dev i386 0.1.29-1 [25.7 kB] Get: 343 http://deb.debian.org/debian bookworm/main i386 libxft-dev i386 2.3.6-1 [82.3 kB] Get: 344 http://deb.debian.org/debian bookworm/main i386 pango1.0-tools i386 1.50.12+ds-1 [41.6 kB] Get: 345 http://deb.debian.org/debian bookworm/main i386 libpango1.0-dev i386 1.50.12+ds-1 [152 kB] Get: 346 http://deb.debian.org/debian bookworm/main i386 libwayland-bin i386 1.21.0-1 [24.9 kB] Get: 347 http://deb.debian.org/debian bookworm/main i386 libwayland-dev i386 1.21.0-1 [72.5 kB] Get: 348 http://deb.debian.org/debian bookworm/main i386 libxcomposite-dev i386 1:0.4.5-1 [20.5 kB] Get: 349 http://deb.debian.org/debian bookworm/main i386 libxcursor-dev i386 1:1.2.1-1 [54.1 kB] Get: 350 http://deb.debian.org/debian bookworm/main i386 libxdamage-dev i386 1:1.1.6-1 [15.3 kB] Get: 351 http://deb.debian.org/debian bookworm/main i386 libxinerama-dev i386 2:1.1.4-3 [20.4 kB] Get: 352 http://deb.debian.org/debian bookworm/main i386 libxkbcommon-dev i386 1.5.0-1 [51.0 kB] Get: 353 http://deb.debian.org/debian bookworm/main i386 libxrandr-dev i386 2:1.5.2-2+b1 [48.8 kB] Get: 354 http://deb.debian.org/debian bookworm/main i386 wayland-protocols all 1.31-1 [74.6 kB] Get: 355 http://deb.debian.org/debian bookworm/main i386 libgtk-3-dev i386 3.24.37-2 [1115 kB] Get: 356 http://deb.debian.org/debian bookworm/main i386 libayatana-ido3-dev i386 0.9.3-1 [17.1 kB] Get: 357 http://deb.debian.org/debian bookworm/main i386 libayatana-indicator3-dev i386 0.9.3-1 [10.8 kB] Get: 358 http://deb.debian.org/debian bookworm/main i386 libxml2-utils i386 2.9.14+dfsg-1.1+b3 [99.1 kB] Get: 359 http://deb.debian.org/debian bookworm/main i386 libgtk2.0-dev i386 2.24.33-2 [827 kB] Get: 360 http://deb.debian.org/debian bookworm/main i386 libdbusmenu-glib-dev i386 18.10.20180917~bzr492+repack1-3 [72.9 kB] Get: 361 http://deb.debian.org/debian bookworm/main i386 libayatana-appindicator3-dev i386 0.5.92-1 [18.2 kB] Get: 362 http://deb.debian.org/debian bookworm/main i386 libelf-dev i386 0.188-2.1 [80.0 kB] Get: 363 http://deb.debian.org/debian bookworm/main i386 libdw-dev i386 0.188-2.1 [353 kB] Get: 364 http://deb.debian.org/debian bookworm/main i386 libgconf2-dev i386 3.2.6-8 [448 kB] Get: 365 http://deb.debian.org/debian bookworm/main i386 libunwind-dev i386 1.6.2-3 [404 kB] Get: 366 http://deb.debian.org/debian bookworm/main i386 libgstreamer1.0-dev i386 1.22.0-2 [549 kB] Get: 367 http://deb.debian.org/debian bookworm/main i386 libnotify-dev i386 0.8.1-1 [17.5 kB] Get: 368 http://deb.debian.org/debian bookworm/main i386 libxml2-dev i386 2.9.14+dfsg-1.1+b3 [845 kB] Fetched 186 MB in 6s (33.2 MB/s) debconf: delaying package configuration, since apt-utils is not installed Selecting previously unselected package libargon2-1:i386. (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 ... 19604 files and directories currently installed.) Preparing to unpack .../00-libargon2-1_0~20171227-0.3_i386.deb ... Unpacking libargon2-1:i386 (0~20171227-0.3) ... Selecting previously unselected package dmsetup. Preparing to unpack .../01-dmsetup_2%3a1.02.185-2_i386.deb ... Unpacking dmsetup (2:1.02.185-2) ... Selecting previously unselected package libdevmapper1.02.1:i386. Preparing to unpack .../02-libdevmapper1.02.1_2%3a1.02.185-2_i386.deb ... Unpacking libdevmapper1.02.1:i386 (2:1.02.185-2) ... Selecting previously unselected package libjson-c5:i386. Preparing to unpack .../03-libjson-c5_0.16-2_i386.deb ... Unpacking libjson-c5:i386 (0.16-2) ... Selecting previously unselected package libcryptsetup12:i386. Preparing to unpack .../04-libcryptsetup12_2%3a2.6.1-3~deb12u1_i386.deb ... Unpacking libcryptsetup12:i386 (2:2.6.1-3~deb12u1) ... Selecting previously unselected package libfdisk1:i386. Preparing to unpack .../05-libfdisk1_2.38.1-5+b1_i386.deb ... Unpacking libfdisk1:i386 (2.38.1-5+b1) ... Selecting previously unselected package libkmod2:i386. Preparing to unpack .../06-libkmod2_30+20221128-1_i386.deb ... Unpacking libkmod2:i386 (30+20221128-1) ... Selecting previously unselected package libapparmor1:i386. Preparing to unpack .../07-libapparmor1_3.0.8-3_i386.deb ... Unpacking libapparmor1:i386 (3.0.8-3) ... Selecting previously unselected package libip4tc2:i386. Preparing to unpack .../08-libip4tc2_1.8.9-2_i386.deb ... Unpacking libip4tc2:i386 (1.8.9-2) ... Selecting previously unselected package libsystemd-shared:i386. Preparing to unpack .../09-libsystemd-shared_252.6-1_i386.deb ... Unpacking libsystemd-shared:i386 (252.6-1) ... Selecting previously unselected package systemd. Preparing to unpack .../10-systemd_252.6-1_i386.deb ... Unpacking systemd (252.6-1) ... Setting up libargon2-1:i386 (0~20171227-0.3) ... Setting up libjson-c5:i386 (0.16-2) ... Setting up libfdisk1:i386 (2.38.1-5+b1) ... Setting up libkmod2:i386 (30+20221128-1) ... Setting up libapparmor1:i386 (3.0.8-3) ... Setting up libip4tc2:i386 (1.8.9-2) ... Setting up libsystemd-shared:i386 (252.6-1) ... Setting up libdevmapper1.02.1:i386 (2:1.02.185-2) ... Setting up libcryptsetup12:i386 (2:2.6.1-3~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 ... 20519 files and directories currently installed.) Preparing to unpack .../00-systemd-sysv_252.6-1_i386.deb ... Unpacking systemd-sysv (252.6-1) ... Selecting previously unselected package libdbus-1-3:i386. Preparing to unpack .../01-libdbus-1-3_1.14.6-1_i386.deb ... Unpacking libdbus-1-3:i386 (1.14.6-1) ... Selecting previously unselected package dbus-bin. Preparing to unpack .../02-dbus-bin_1.14.6-1_i386.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:i386. Preparing to unpack .../04-libexpat1_2.5.0-1_i386.deb ... Unpacking libexpat1:i386 (2.5.0-1) ... Selecting previously unselected package dbus-daemon. Preparing to unpack .../05-dbus-daemon_1.14.6-1_i386.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_i386.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:i386. Preparing to unpack .../09-libpython3.11-minimal_3.11.2-6_i386.deb ... Unpacking libpython3.11-minimal:i386 (3.11.2-6) ... Selecting previously unselected package python3.11-minimal. Preparing to unpack .../10-python3.11-minimal_3.11.2-6_i386.deb ... Unpacking python3.11-minimal (3.11.2-6) ... Setting up libpython3.11-minimal:i386 (3.11.2-6) ... Setting up libexpat1:i386 (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 ... 22108 files and directories currently installed.) Preparing to unpack .../0-python3-minimal_3.11.2-1+b1_i386.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:i386. Preparing to unpack .../3-libreadline8_8.2-1.3_i386.deb ... Unpacking libreadline8:i386 (8.2-1.3) ... Selecting previously unselected package libpython3.11-stdlib:i386. Preparing to unpack .../4-libpython3.11-stdlib_3.11.2-6_i386.deb ... Unpacking libpython3.11-stdlib:i386 (3.11.2-6) ... Selecting previously unselected package python3.11. Preparing to unpack .../5-python3.11_3.11.2-6_i386.deb ... Unpacking python3.11 (3.11.2-6) ... Selecting previously unselected package libpython3-stdlib:i386. Preparing to unpack .../6-libpython3-stdlib_3.11.2-1+b1_i386.deb ... Unpacking libpython3-stdlib:i386 (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 ... 22542 files and directories currently installed.) Preparing to unpack .../000-python3_3.11.2-1+b1_i386.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:i386. Preparing to unpack .../003-libproc2-0_2%3a4.0.2-3_i386.deb ... Unpacking libproc2-0:i386 (2:4.0.2-3) ... Selecting previously unselected package procps. Preparing to unpack .../004-procps_2%3a4.0.2-3_i386.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_i386.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_i386.deb ... Unpacking libmagic-mgc (1:5.44-3) ... Selecting previously unselected package libmagic1:i386. Preparing to unpack .../009-libmagic1_1%3a5.44-3_i386.deb ... Unpacking libmagic1:i386 (1:5.44-3) ... Selecting previously unselected package file. Preparing to unpack .../010-file_1%3a5.44-3_i386.deb ... Unpacking file (1:5.44-3) ... Selecting previously unselected package gettext-base. Preparing to unpack .../011-gettext-base_0.21-12_i386.deb ... Unpacking gettext-base (0.21-12) ... Selecting previously unselected package libuchardet0:i386. Preparing to unpack .../012-libuchardet0_0.0.7-1_i386.deb ... Unpacking libuchardet0:i386 (0.0.7-1) ... Selecting previously unselected package groff-base. Preparing to unpack .../013-groff-base_1.22.4-10_i386.deb ... Unpacking groff-base (1.22.4-10) ... Selecting previously unselected package libpam-systemd:i386. Preparing to unpack .../014-libpam-systemd_252.6-1_i386.deb ... Unpacking libpam-systemd:i386 (252.6-1) ... Selecting previously unselected package bsdextrautils. Preparing to unpack .../015-bsdextrautils_2.38.1-5+b1_i386.deb ... Unpacking bsdextrautils (2.38.1-5+b1) ... Selecting previously unselected package libpipeline1:i386. Preparing to unpack .../016-libpipeline1_1.5.7-1_i386.deb ... Unpacking libpipeline1:i386 (1.5.7-1) ... Selecting previously unselected package man-db. Preparing to unpack .../017-man-db_2.11.2-2_i386.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:i386. Preparing to unpack .../021-libglib2.0-0_2.74.6-1_i386.deb ... Unpacking libglib2.0-0:i386 (2.74.6-1) ... Selecting previously unselected package libicu72:i386. Preparing to unpack .../022-libicu72_72.1-3_i386.deb ... Unpacking libicu72:i386 (72.1-3) ... Selecting previously unselected package libxml2:i386. Preparing to unpack .../023-libxml2_2.9.14+dfsg-1.1+b3_i386.deb ... Unpacking libxml2:i386 (2.9.14+dfsg-1.1+b3) ... Selecting previously unselected package shared-mime-info. Preparing to unpack .../024-shared-mime-info_2.2-1_i386.deb ... Unpacking shared-mime-info (2.2-1) ... Selecting previously unselected package libjpeg62-turbo:i386. Preparing to unpack .../025-libjpeg62-turbo_1%3a2.1.5-2_i386.deb ... Unpacking libjpeg62-turbo:i386 (1:2.1.5-2) ... Selecting previously unselected package libpng16-16:i386. Preparing to unpack .../026-libpng16-16_1.6.39-2_i386.deb ... Unpacking libpng16-16:i386 (1.6.39-2) ... Selecting previously unselected package libdeflate0:i386. Preparing to unpack .../027-libdeflate0_1.14-1_i386.deb ... Unpacking libdeflate0:i386 (1.14-1) ... Selecting previously unselected package libjbig0:i386. Preparing to unpack .../028-libjbig0_2.1-6.1_i386.deb ... Unpacking libjbig0:i386 (2.1-6.1) ... Selecting previously unselected package liblerc4:i386. Preparing to unpack .../029-liblerc4_4.0.0+ds-2_i386.deb ... Unpacking liblerc4:i386 (4.0.0+ds-2) ... Selecting previously unselected package libwebp7:i386. Preparing to unpack .../030-libwebp7_1.2.4-0.1_i386.deb ... Unpacking libwebp7:i386 (1.2.4-0.1) ... Selecting previously unselected package libtiff6:i386. Preparing to unpack .../031-libtiff6_4.5.0-5_i386.deb ... Unpacking libtiff6:i386 (4.5.0-5) ... Selecting previously unselected package libgdk-pixbuf-2.0-0:i386. Preparing to unpack .../032-libgdk-pixbuf-2.0-0_2.42.10+dfsg-1+b1_i386.deb ... Unpacking libgdk-pixbuf-2.0-0:i386 (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_i386.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_i386.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:i386. Preparing to unpack .../041-libarchive13_3.6.2-1_i386.deb ... Unpacking libarchive13:i386 (3.6.2-1) ... Selecting previously unselected package libbrotli1:i386. Preparing to unpack .../042-libbrotli1_1.0.9-2+b6_i386.deb ... Unpacking libbrotli1:i386 (1.0.9-2+b6) ... Selecting previously unselected package libsasl2-modules-db:i386. Preparing to unpack .../043-libsasl2-modules-db_2.1.28+dfsg-10_i386.deb ... Unpacking libsasl2-modules-db:i386 (2.1.28+dfsg-10) ... Selecting previously unselected package libsasl2-2:i386. Preparing to unpack .../044-libsasl2-2_2.1.28+dfsg-10_i386.deb ... Unpacking libsasl2-2:i386 (2.1.28+dfsg-10) ... Selecting previously unselected package libldap-2.5-0:i386. Preparing to unpack .../045-libldap-2.5-0_2.5.13+dfsg-5_i386.deb ... Unpacking libldap-2.5-0:i386 (2.5.13+dfsg-5) ... Selecting previously unselected package libnghttp2-14:i386. Preparing to unpack .../046-libnghttp2-14_1.52.0-1_i386.deb ... Unpacking libnghttp2-14:i386 (1.52.0-1) ... Selecting previously unselected package libpsl5:i386. Preparing to unpack .../047-libpsl5_0.21.2-1_i386.deb ... Unpacking libpsl5:i386 (0.21.2-1) ... Selecting previously unselected package librtmp1:i386. Preparing to unpack .../048-librtmp1_2.4+20151223.gitfa8646d.1-2+b2_i386.deb ... Unpacking librtmp1:i386 (2.4+20151223.gitfa8646d.1-2+b2) ... Selecting previously unselected package libssh2-1:i386. Preparing to unpack .../049-libssh2-1_1.10.0-3+b1_i386.deb ... Unpacking libssh2-1:i386 (1.10.0-3+b1) ... Selecting previously unselected package libcurl4:i386. Preparing to unpack .../050-libcurl4_7.88.1-8_i386.deb ... Unpacking libcurl4:i386 (7.88.1-8) ... Selecting previously unselected package libjsoncpp25:i386. Preparing to unpack .../051-libjsoncpp25_1.9.5-4_i386.deb ... Unpacking libjsoncpp25:i386 (1.9.5-4) ... Selecting previously unselected package librhash0:i386. Preparing to unpack .../052-librhash0_1.4.3-3_i386.deb ... Unpacking librhash0:i386 (1.4.3-3) ... Selecting previously unselected package libuv1:i386. Preparing to unpack .../053-libuv1_1.44.2-1_i386.deb ... Unpacking libuv1:i386 (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_i386.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_i386.deb ... Unpacking dbus-user-session (1.14.6-1) ... Selecting previously unselected package libdconf1:i386. Preparing to unpack .../057-libdconf1_0.40.0-4_i386.deb ... Unpacking libdconf1:i386 (0.40.0-4) ... Selecting previously unselected package dconf-service. Preparing to unpack .../058-dconf-service_0.40.0-4_i386.deb ... Unpacking dconf-service (0.40.0-4) ... Selecting previously unselected package dconf-gsettings-backend:i386. Preparing to unpack .../059-dconf-gsettings-backend_0.40.0-4_i386.deb ... Unpacking dconf-gsettings-backend:i386 (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:i386. Preparing to unpack .../067-libelf1_0.188-2.1_i386.deb ... Unpacking libelf1:i386 (0.188-2.1) ... Selecting previously unselected package dwz. Preparing to unpack .../068-dwz_0.15-1_i386.deb ... Unpacking dwz (0.15-1) ... Selecting previously unselected package gettext. Preparing to unpack .../069-gettext_0.21-12_i386.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:i386. Preparing to unpack .../073-libfreetype6_2.12.1+dfsg-4_i386.deb ... Unpacking libfreetype6:i386 (2.12.1+dfsg-4) ... 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_i386.deb ... Unpacking fontconfig-config (2.14.1-4) ... Selecting previously unselected package libfontconfig1:i386. Preparing to unpack .../076-libfontconfig1_2.14.1-4_i386.deb ... Unpacking libfontconfig1:i386 (2.14.1-4) ... Selecting previously unselected package fontconfig. Preparing to unpack .../077-fontconfig_2.14.1-4_i386.deb ... Unpacking fontconfig (2.14.1-4) ... Selecting previously unselected package libdbus-glib-1-2:i386. Preparing to unpack .../078-libdbus-glib-1-2_0.112-3_i386.deb ... Unpacking libdbus-glib-1-2:i386 (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:i386. Preparing to unpack .../080-libgconf-2-4_3.2.6-8_i386.deb ... Unpacking libgconf-2-4:i386 (3.2.6-8) ... Selecting previously unselected package gconf-service. Preparing to unpack .../081-gconf-service_3.2.6-8_i386.deb ... Unpacking gconf-service (3.2.6-8) ... Selecting previously unselected package psmisc. Preparing to unpack .../082-psmisc_23.6-1_i386.deb ... Unpacking psmisc (23.6-1) ... Selecting previously unselected package gconf2. Preparing to unpack .../083-gconf2_3.2.6-8_i386.deb ... Unpacking gconf2 (3.2.6-8) ... Selecting previously unselected package libgirepository-1.0-1:i386. Preparing to unpack .../084-libgirepository-1.0-1_1.74.0-3_i386.deb ... Unpacking libgirepository-1.0-1:i386 (1.74.0-3) ... Selecting previously unselected package gir1.2-glib-2.0:i386. Preparing to unpack .../085-gir1.2-glib-2.0_1.74.0-3_i386.deb ... Unpacking gir1.2-glib-2.0:i386 (1.74.0-3) ... Selecting previously unselected package libatk1.0-0:i386. Preparing to unpack .../086-libatk1.0-0_2.46.0-5_i386.deb ... Unpacking libatk1.0-0:i386 (2.46.0-5) ... Selecting previously unselected package gir1.2-atk-1.0:i386. Preparing to unpack .../087-gir1.2-atk-1.0_2.46.0-5_i386.deb ... Unpacking gir1.2-atk-1.0:i386 (2.46.0-5) ... Selecting previously unselected package gir1.2-freedesktop:i386. Preparing to unpack .../088-gir1.2-freedesktop_1.74.0-3_i386.deb ... Unpacking gir1.2-freedesktop:i386 (1.74.0-3) ... Selecting previously unselected package libxau6:i386. Preparing to unpack .../089-libxau6_1%3a1.0.9-1_i386.deb ... Unpacking libxau6:i386 (1:1.0.9-1) ... Selecting previously unselected package libbsd0:i386. Preparing to unpack .../090-libbsd0_0.11.7-2_i386.deb ... Unpacking libbsd0:i386 (0.11.7-2) ... Selecting previously unselected package libxdmcp6:i386. Preparing to unpack .../091-libxdmcp6_1%3a1.1.2-3_i386.deb ... Unpacking libxdmcp6:i386 (1:1.1.2-3) ... Selecting previously unselected package libxcb1:i386. Preparing to unpack .../092-libxcb1_1.15-1_i386.deb ... Unpacking libxcb1:i386 (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:i386. Preparing to unpack .../094-libx11-6_2%3a1.8.4-2_i386.deb ... Unpacking libx11-6:i386 (2:1.8.4-2) ... Selecting previously unselected package libxext6:i386. Preparing to unpack .../095-libxext6_2%3a1.3.4-1+b1_i386.deb ... Unpacking libxext6:i386 (2:1.3.4-1+b1) ... Selecting previously unselected package libxi6:i386. Preparing to unpack .../096-libxi6_2%3a1.8-1+b1_i386.deb ... Unpacking libxi6:i386 (2:1.8-1+b1) ... Selecting previously unselected package libatspi2.0-0:i386. Preparing to unpack .../097-libatspi2.0-0_2.46.0-5_i386.deb ... Unpacking libatspi2.0-0:i386 (2.46.0-5) ... Selecting previously unselected package gir1.2-atspi-2.0:i386. Preparing to unpack .../098-gir1.2-atspi-2.0_2.46.0-5_i386.deb ... Unpacking gir1.2-atspi-2.0:i386 (2.46.0-5) ... Selecting previously unselected package gir1.2-gdkpixbuf-2.0:i386. Preparing to unpack .../099-gir1.2-gdkpixbuf-2.0_2.42.10+dfsg-1+b1_i386.deb ... Unpacking gir1.2-gdkpixbuf-2.0:i386 (2.42.10+dfsg-1+b1) ... Selecting previously unselected package gir1.2-harfbuzz-0.0:i386. Preparing to unpack .../100-gir1.2-harfbuzz-0.0_6.0.0+dfsg-3_i386.deb ... Unpacking gir1.2-harfbuzz-0.0:i386 (6.0.0+dfsg-3) ... Selecting previously unselected package libfribidi0:i386. Preparing to unpack .../101-libfribidi0_1.0.8-2.1_i386.deb ... Unpacking libfribidi0:i386 (1.0.8-2.1) ... Selecting previously unselected package libgraphite2-3:i386. Preparing to unpack .../102-libgraphite2-3_1.3.14-1_i386.deb ... Unpacking libgraphite2-3:i386 (1.3.14-1) ... Selecting previously unselected package libharfbuzz0b:i386. Preparing to unpack .../103-libharfbuzz0b_6.0.0+dfsg-3_i386.deb ... Unpacking libharfbuzz0b:i386 (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:i386. Preparing to unpack .../105-libdatrie1_0.2.13-2+b1_i386.deb ... Unpacking libdatrie1:i386 (0.2.13-2+b1) ... Selecting previously unselected package libthai0:i386. Preparing to unpack .../106-libthai0_0.1.29-1_i386.deb ... Unpacking libthai0:i386 (0.1.29-1) ... Selecting previously unselected package libpango-1.0-0:i386. Preparing to unpack .../107-libpango-1.0-0_1.50.12+ds-1_i386.deb ... Unpacking libpango-1.0-0:i386 (1.50.12+ds-1) ... Selecting previously unselected package libpixman-1-0:i386. Preparing to unpack .../108-libpixman-1-0_0.42.2-1_i386.deb ... Unpacking libpixman-1-0:i386 (0.42.2-1) ... Selecting previously unselected package libxcb-render0:i386. Preparing to unpack .../109-libxcb-render0_1.15-1_i386.deb ... Unpacking libxcb-render0:i386 (1.15-1) ... Selecting previously unselected package libxcb-shm0:i386. Preparing to unpack .../110-libxcb-shm0_1.15-1_i386.deb ... Unpacking libxcb-shm0:i386 (1.15-1) ... Selecting previously unselected package libxrender1:i386. Preparing to unpack .../111-libxrender1_1%3a0.9.10-1.1_i386.deb ... Unpacking libxrender1:i386 (1:0.9.10-1.1) ... Selecting previously unselected package libcairo2:i386. Preparing to unpack .../112-libcairo2_1.16.0-7_i386.deb ... Unpacking libcairo2:i386 (1.16.0-7) ... Selecting previously unselected package libpangoft2-1.0-0:i386. Preparing to unpack .../113-libpangoft2-1.0-0_1.50.12+ds-1_i386.deb ... Unpacking libpangoft2-1.0-0:i386 (1.50.12+ds-1) ... Selecting previously unselected package libpangocairo-1.0-0:i386. Preparing to unpack .../114-libpangocairo-1.0-0_1.50.12+ds-1_i386.deb ... Unpacking libpangocairo-1.0-0:i386 (1.50.12+ds-1) ... Selecting previously unselected package libxft2:i386. Preparing to unpack .../115-libxft2_2.3.6-1_i386.deb ... Unpacking libxft2:i386 (2.3.6-1) ... Selecting previously unselected package libpangoxft-1.0-0:i386. Preparing to unpack .../116-libpangoxft-1.0-0_1.50.12+ds-1_i386.deb ... Unpacking libpangoxft-1.0-0:i386 (1.50.12+ds-1) ... Selecting previously unselected package gir1.2-pango-1.0:i386. Preparing to unpack .../117-gir1.2-pango-1.0_1.50.12+ds-1_i386.deb ... Unpacking gir1.2-pango-1.0:i386 (1.50.12+ds-1) ... Selecting previously unselected package libatk-bridge2.0-0:i386. Preparing to unpack .../118-libatk-bridge2.0-0_2.46.0-5_i386.deb ... Unpacking libatk-bridge2.0-0:i386 (2.46.0-5) ... Selecting previously unselected package libcairo-gobject2:i386. Preparing to unpack .../119-libcairo-gobject2_1.16.0-7_i386.deb ... Unpacking libcairo-gobject2:i386 (1.16.0-7) ... Selecting previously unselected package liblcms2-2:i386. Preparing to unpack .../120-liblcms2-2_2.14-2_i386.deb ... Unpacking liblcms2-2:i386 (2.14-2) ... Selecting previously unselected package libcolord2:i386. Preparing to unpack .../121-libcolord2_1.4.6-2.2_i386.deb ... Unpacking libcolord2:i386 (1.4.6-2.2) ... Selecting previously unselected package libavahi-common-data:i386. Preparing to unpack .../122-libavahi-common-data_0.8-9_i386.deb ... Unpacking libavahi-common-data:i386 (0.8-9) ... Selecting previously unselected package libavahi-common3:i386. Preparing to unpack .../123-libavahi-common3_0.8-9_i386.deb ... Unpacking libavahi-common3:i386 (0.8-9) ... Selecting previously unselected package libavahi-client3:i386. Preparing to unpack .../124-libavahi-client3_0.8-9_i386.deb ... Unpacking libavahi-client3:i386 (0.8-9) ... Selecting previously unselected package libcups2:i386. Preparing to unpack .../125-libcups2_2.4.2-3_i386.deb ... Unpacking libcups2:i386 (2.4.2-3) ... Selecting previously unselected package libepoxy0:i386. Preparing to unpack .../126-libepoxy0_1.5.10-1_i386.deb ... Unpacking libepoxy0:i386 (1.5.10-1) ... Selecting previously unselected package libwayland-client0:i386. Preparing to unpack .../127-libwayland-client0_1.21.0-1_i386.deb ... Unpacking libwayland-client0:i386 (1.21.0-1) ... Selecting previously unselected package libwayland-cursor0:i386. Preparing to unpack .../128-libwayland-cursor0_1.21.0-1_i386.deb ... Unpacking libwayland-cursor0:i386 (1.21.0-1) ... Selecting previously unselected package libwayland-egl1:i386. Preparing to unpack .../129-libwayland-egl1_1.21.0-1_i386.deb ... Unpacking libwayland-egl1:i386 (1.21.0-1) ... Selecting previously unselected package libxcomposite1:i386. Preparing to unpack .../130-libxcomposite1_1%3a0.4.5-1_i386.deb ... Unpacking libxcomposite1:i386 (1:0.4.5-1) ... Selecting previously unselected package libxfixes3:i386. Preparing to unpack .../131-libxfixes3_1%3a6.0.0-2_i386.deb ... Unpacking libxfixes3:i386 (1:6.0.0-2) ... Selecting previously unselected package libxcursor1:i386. Preparing to unpack .../132-libxcursor1_1%3a1.2.1-1_i386.deb ... Unpacking libxcursor1:i386 (1:1.2.1-1) ... Selecting previously unselected package libxdamage1:i386. Preparing to unpack .../133-libxdamage1_1%3a1.1.6-1_i386.deb ... Unpacking libxdamage1:i386 (1:1.1.6-1) ... Selecting previously unselected package libxinerama1:i386. Preparing to unpack .../134-libxinerama1_2%3a1.1.4-3_i386.deb ... Unpacking libxinerama1:i386 (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:i386. Preparing to unpack .../136-libxkbcommon0_1.5.0-1_i386.deb ... Unpacking libxkbcommon0:i386 (1.5.0-1) ... Selecting previously unselected package libxrandr2:i386. Preparing to unpack .../137-libxrandr2_2%3a1.5.2-2+b1_i386.deb ... Unpacking libxrandr2:i386 (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:i386. Preparing to unpack .../139-libgtk-3-0_3.24.37-2_i386.deb ... Unpacking libgtk-3-0:i386 (3.24.37-2) ... Selecting previously unselected package gir1.2-gtk-3.0:i386. Preparing to unpack .../140-gir1.2-gtk-3.0_3.24.37-2_i386.deb ... Unpacking gir1.2-gtk-3.0:i386 (3.24.37-2) ... Selecting previously unselected package libayatana-ido3-0.4-0:i386. Preparing to unpack .../141-libayatana-ido3-0.4-0_0.9.3-1_i386.deb ... Unpacking libayatana-ido3-0.4-0:i386 (0.9.3-1) ... Selecting previously unselected package libayatana-indicator3-7:i386. Preparing to unpack .../142-libayatana-indicator3-7_0.9.3-1_i386.deb ... Unpacking libayatana-indicator3-7:i386 (0.9.3-1) ... Selecting previously unselected package libdbusmenu-glib4:i386. Preparing to unpack .../143-libdbusmenu-glib4_18.10.20180917~bzr492+repack1-3_i386.deb ... Unpacking libdbusmenu-glib4:i386 (18.10.20180917~bzr492+repack1-3) ... Selecting previously unselected package libdbusmenu-gtk3-4:i386. Preparing to unpack .../144-libdbusmenu-gtk3-4_18.10.20180917~bzr492+repack1-3_i386.deb ... Unpacking libdbusmenu-gtk3-4:i386 (18.10.20180917~bzr492+repack1-3) ... Selecting previously unselected package libayatana-appindicator3-1. Preparing to unpack .../145-libayatana-appindicator3-1_0.5.92-1_i386.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_i386.deb ... Unpacking gir1.2-ayatanaappindicator3-0.1 (0.5.92-1) ... Selecting previously unselected package gir1.2-ayatanaido3-0.4:i386. Preparing to unpack .../147-gir1.2-ayatanaido3-0.4_0.9.3-1_i386.deb ... Unpacking gir1.2-ayatanaido3-0.4:i386 (0.9.3-1) ... Selecting previously unselected package gir1.2-dbusmenu-glib-0.4:i386. Preparing to unpack .../148-gir1.2-dbusmenu-glib-0.4_18.10.20180917~bzr492+repack1-3_i386.deb ... Unpacking gir1.2-dbusmenu-glib-0.4:i386 (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_i386.deb ... Unpacking gir1.2-gconf-2.0 (3.2.6-8) ... Selecting previously unselected package libdw1:i386. Preparing to unpack .../150-libdw1_0.188-2.1_i386.deb ... Unpacking libdw1:i386 (0.188-2.1) ... Selecting previously unselected package libunwind8:i386. Preparing to unpack .../151-libunwind8_1.6.2-3_i386.deb ... Unpacking libunwind8:i386 (1.6.2-3) ... Selecting previously unselected package libcap2-bin. Preparing to unpack .../152-libcap2-bin_1%3a2.66-3_i386.deb ... Unpacking libcap2-bin (1:2.66-3) ... Selecting previously unselected package libgstreamer1.0-0:i386. Preparing to unpack .../153-libgstreamer1.0-0_1.22.0-2_i386.deb ... Unpacking libgstreamer1.0-0:i386 (1.22.0-2) ... Selecting previously unselected package gir1.2-gstreamer-1.0:i386. Preparing to unpack .../154-gir1.2-gstreamer-1.0_1.22.0-2_i386.deb ... Unpacking gir1.2-gstreamer-1.0:i386 (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:i386. Preparing to unpack .../156-librsvg2-2_2.54.5+dfsg-1_i386.deb ... Unpacking librsvg2-2:i386 (2.54.5+dfsg-1) ... Selecting previously unselected package librsvg2-common:i386. Preparing to unpack .../157-librsvg2-common_2.54.5+dfsg-1_i386.deb ... Unpacking librsvg2-common:i386 (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:i386. Preparing to unpack .../159-libgtk2.0-0_2.24.33-2_i386.deb ... Unpacking libgtk2.0-0:i386 (2.24.33-2) ... Selecting previously unselected package gir1.2-gtk-2.0:i386. Preparing to unpack .../160-gir1.2-gtk-2.0_2.24.33-2_i386.deb ... Unpacking gir1.2-gtk-2.0:i386 (2.24.33-2) ... Selecting previously unselected package libnotify4:i386. Preparing to unpack .../161-libnotify4_0.8.1-1_i386.deb ... Unpacking libnotify4:i386 (0.8.1-1) ... Selecting previously unselected package gir1.2-notify-0.7:i386. Preparing to unpack .../162-gir1.2-notify-0.7_0.8.1-1_i386.deb ... Unpacking gir1.2-notify-0.7:i386 (0.8.1-1) ... Selecting previously unselected package libpkgconf3:i386. Preparing to unpack .../163-libpkgconf3_1.8.1-1_i386.deb ... Unpacking libpkgconf3:i386 (1.8.1-1) ... Selecting previously unselected package pkgconf-bin. Preparing to unpack .../164-pkgconf-bin_1.8.1-1_i386.deb ... Unpacking pkgconf-bin (1.8.1-1) ... Selecting previously unselected package pkgconf:i386. Preparing to unpack .../165-pkgconf_1.8.1-1_i386.deb ... Unpacking pkgconf:i386 (1.8.1-1) ... Selecting previously unselected package pkg-config:i386. Preparing to unpack .../166-pkg-config_1.8.1-1_i386.deb ... Unpacking pkg-config:i386 (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:i386. Preparing to unpack .../174-libhtml-parser-perl_3.81-1_i386.deb ... Unpacking libhtml-parser-perl:i386 (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:i386. Preparing to unpack .../176-libclone-perl_0.46-1_i386.deb ... Unpacking libclone-perl:i386 (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:i386. Preparing to unpack .../182-perl-openssl-defaults_7+b1_i386.deb ... Unpacking perl-openssl-defaults:i386 (7+b1) ... Selecting previously unselected package libnet-ssleay-perl:i386. Preparing to unpack .../183-libnet-ssleay-perl_1.92-2+b1_i386.deb ... Unpacking libnet-ssleay-perl:i386 (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_i386.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_i386.deb ... Unpacking icu-devtools (72.1-3) ... Selecting previously unselected package libffi-dev:i386. Preparing to unpack .../194-libffi-dev_3.4.4-1_i386.deb ... Unpacking libffi-dev:i386 (3.4.4-1) ... Selecting previously unselected package libglib2.0-data. Preparing to unpack .../195-libglib2.0-data_2.74.6-1_all.deb ... Unpacking libglib2.0-data (2.74.6-1) ... Selecting previously unselected package libglib2.0-bin. Preparing to unpack .../196-libglib2.0-bin_2.74.6-1_i386.deb ... Unpacking libglib2.0-bin (2.74.6-1) ... Selecting previously unselected package python3-lib2to3. Preparing to unpack .../197-python3-lib2to3_3.11.2-2_all.deb ... Unpacking python3-lib2to3 (3.11.2-2) ... Selecting previously unselected package python3-distutils. Preparing to unpack .../198-python3-distutils_3.11.2-2_all.deb ... Unpacking python3-distutils (3.11.2-2) ... Selecting previously unselected package libglib2.0-dev-bin. Preparing to unpack .../199-libglib2.0-dev-bin_2.74.6-1_i386.deb ... Unpacking libglib2.0-dev-bin (2.74.6-1) ... Selecting previously unselected package uuid-dev:i386. Preparing to unpack .../200-uuid-dev_2.38.1-5+b1_i386.deb ... Unpacking uuid-dev:i386 (2.38.1-5+b1) ... Selecting previously unselected package libblkid-dev:i386. Preparing to unpack .../201-libblkid-dev_2.38.1-5+b1_i386.deb ... Unpacking libblkid-dev:i386 (2.38.1-5+b1) ... Selecting previously unselected package libsepol-dev:i386. Preparing to unpack .../202-libsepol-dev_3.4-2_i386.deb ... Unpacking libsepol-dev:i386 (3.4-2) ... Selecting previously unselected package libpcre2-16-0:i386. Preparing to unpack .../203-libpcre2-16-0_10.42-1_i386.deb ... Unpacking libpcre2-16-0:i386 (10.42-1) ... Selecting previously unselected package libpcre2-32-0:i386. Preparing to unpack .../204-libpcre2-32-0_10.42-1_i386.deb ... Unpacking libpcre2-32-0:i386 (10.42-1) ... Selecting previously unselected package libpcre2-posix3:i386. Preparing to unpack .../205-libpcre2-posix3_10.42-1_i386.deb ... Unpacking libpcre2-posix3:i386 (10.42-1) ... Selecting previously unselected package libpcre2-dev:i386. Preparing to unpack .../206-libpcre2-dev_10.42-1_i386.deb ... Unpacking libpcre2-dev:i386 (10.42-1) ... Selecting previously unselected package libselinux1-dev:i386. Preparing to unpack .../207-libselinux1-dev_3.4-1+b5_i386.deb ... Unpacking libselinux1-dev:i386 (3.4-1+b5) ... Selecting previously unselected package libmount-dev:i386. Preparing to unpack .../208-libmount-dev_2.38.1-5+b1_i386.deb ... Unpacking libmount-dev:i386 (2.38.1-5+b1) ... Selecting previously unselected package zlib1g-dev:i386. Preparing to unpack .../209-zlib1g-dev_1%3a1.2.13.dfsg-1_i386.deb ... Unpacking zlib1g-dev:i386 (1:1.2.13.dfsg-1) ... Selecting previously unselected package libglib2.0-dev:i386. Preparing to unpack .../210-libglib2.0-dev_2.74.6-1_i386.deb ... Unpacking libglib2.0-dev:i386 (2.74.6-1) ... Selecting previously unselected package libatk1.0-dev:i386. Preparing to unpack .../211-libatk1.0-dev_2.46.0-5_i386.deb ... Unpacking libatk1.0-dev:i386 (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:i386. Preparing to unpack .../213-libdbus-1-dev_1.14.6-1_i386.deb ... Unpacking libdbus-1-dev:i386 (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:i386. Preparing to unpack .../215-libxtst6_2%3a1.2.3-1.1_i386.deb ... Unpacking libxtst6:i386 (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:i386. Preparing to unpack .../218-libxau-dev_1%3a1.0.9-1_i386.deb ... Unpacking libxau-dev:i386 (1:1.0.9-1) ... Selecting previously unselected package libxdmcp-dev:i386. Preparing to unpack .../219-libxdmcp-dev_1%3a1.1.2-3_i386.deb ... Unpacking libxdmcp-dev:i386 (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:i386. Preparing to unpack .../221-libpthread-stubs0-dev_0.4-1_i386.deb ... Unpacking libpthread-stubs0-dev:i386 (0.4-1) ... Selecting previously unselected package libxcb1-dev:i386. Preparing to unpack .../222-libxcb1-dev_1.15-1_i386.deb ... Unpacking libxcb1-dev:i386 (1.15-1) ... Selecting previously unselected package libx11-dev:i386. Preparing to unpack .../223-libx11-dev_2%3a1.8.4-2_i386.deb ... Unpacking libx11-dev:i386 (2:1.8.4-2) ... Selecting previously unselected package libxext-dev:i386. Preparing to unpack .../224-libxext-dev_2%3a1.3.4-1+b1_i386.deb ... Unpacking libxext-dev:i386 (2:1.3.4-1+b1) ... Selecting previously unselected package libxfixes-dev:i386. Preparing to unpack .../225-libxfixes-dev_1%3a6.0.0-2_i386.deb ... Unpacking libxfixes-dev:i386 (1:6.0.0-2) ... Selecting previously unselected package libxi-dev:i386. Preparing to unpack .../226-libxi-dev_2%3a1.8-1+b1_i386.deb ... Unpacking libxi-dev:i386 (2:1.8-1+b1) ... Selecting previously unselected package libxtst-dev:i386. Preparing to unpack .../227-libxtst-dev_2%3a1.2.3-1.1_i386.deb ... Unpacking libxtst-dev:i386 (2:1.2.3-1.1) ... Selecting previously unselected package libatspi2.0-dev:i386. Preparing to unpack .../228-libatspi2.0-dev_2.46.0-5_i386.deb ... Unpacking libatspi2.0-dev:i386 (2.46.0-5) ... Selecting previously unselected package libatk-bridge2.0-dev:i386. Preparing to unpack .../229-libatk-bridge2.0-dev_2.46.0-5_i386.deb ... Unpacking libatk-bridge2.0-dev:i386 (2.46.0-5) ... Selecting previously unselected package liblzo2-2:i386. Preparing to unpack .../230-liblzo2-2_2.10-2_i386.deb ... Unpacking liblzo2-2:i386 (2.10-2) ... Selecting previously unselected package libcairo-script-interpreter2:i386. Preparing to unpack .../231-libcairo-script-interpreter2_1.16.0-7_i386.deb ... Unpacking libcairo-script-interpreter2:i386 (1.16.0-7) ... Selecting previously unselected package libexpat1-dev:i386. Preparing to unpack .../232-libexpat1-dev_2.5.0-1_i386.deb ... Unpacking libexpat1-dev:i386 (2.5.0-1) ... Selecting previously unselected package libbrotli-dev:i386. Preparing to unpack .../233-libbrotli-dev_1.0.9-2+b6_i386.deb ... Unpacking libbrotli-dev:i386 (1.0.9-2+b6) ... Selecting previously unselected package libpng-dev:i386. Preparing to unpack .../234-libpng-dev_1.6.39-2_i386.deb ... Unpacking libpng-dev:i386 (1.6.39-2) ... Selecting previously unselected package libfreetype-dev:i386. Preparing to unpack .../235-libfreetype-dev_2.12.1+dfsg-4_i386.deb ... Unpacking libfreetype-dev:i386 (2.12.1+dfsg-4) ... Selecting previously unselected package libfontconfig-dev:i386. Preparing to unpack .../236-libfontconfig-dev_2.14.1-4_i386.deb ... Unpacking libfontconfig-dev:i386 (2.14.1-4) ... Selecting previously unselected package libpixman-1-dev:i386. Preparing to unpack .../237-libpixman-1-dev_0.42.2-1_i386.deb ... Unpacking libpixman-1-dev:i386 (0.42.2-1) ... Selecting previously unselected package libice6:i386. Preparing to unpack .../238-libice6_2%3a1.0.10-1_i386.deb ... Unpacking libice6:i386 (2:1.0.10-1) ... Selecting previously unselected package libsm6:i386. Preparing to unpack .../239-libsm6_2%3a1.2.3-1_i386.deb ... Unpacking libsm6:i386 (2:1.2.3-1) ... Selecting previously unselected package libice-dev:i386. Preparing to unpack .../240-libice-dev_2%3a1.0.10-1_i386.deb ... Unpacking libice-dev:i386 (2:1.0.10-1) ... Selecting previously unselected package libsm-dev:i386. Preparing to unpack .../241-libsm-dev_2%3a1.2.3-1_i386.deb ... Unpacking libsm-dev:i386 (2:1.2.3-1) ... Selecting previously unselected package libxcb-render0-dev:i386. Preparing to unpack .../242-libxcb-render0-dev_1.15-1_i386.deb ... Unpacking libxcb-render0-dev:i386 (1.15-1) ... Selecting previously unselected package libxcb-shm0-dev:i386. Preparing to unpack .../243-libxcb-shm0-dev_1.15-1_i386.deb ... Unpacking libxcb-shm0-dev:i386 (1.15-1) ... Selecting previously unselected package libxrender-dev:i386. Preparing to unpack .../244-libxrender-dev_1%3a0.9.10-1.1_i386.deb ... Unpacking libxrender-dev:i386 (1:0.9.10-1.1) ... Selecting previously unselected package libcairo2-dev:i386. Preparing to unpack .../245-libcairo2-dev_1.16.0-7_i386.deb ... Unpacking libcairo2-dev:i386 (1.16.0-7) ... Selecting previously unselected package libglvnd0:i386. Preparing to unpack .../246-libglvnd0_1.6.0-1_i386.deb ... Unpacking libglvnd0:i386 (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:i386. Preparing to unpack .../248-libdrm2_2.4.114-1+b1_i386.deb ... Unpacking libdrm2:i386 (2.4.114-1+b1) ... Selecting previously unselected package libwayland-server0:i386. Preparing to unpack .../249-libwayland-server0_1.21.0-1_i386.deb ... Unpacking libwayland-server0:i386 (1.21.0-1) ... Selecting previously unselected package libgbm1:i386. Preparing to unpack .../250-libgbm1_22.3.6-1+deb12u1_i386.deb ... Unpacking libgbm1:i386 (22.3.6-1+deb12u1) ... Selecting previously unselected package libglapi-mesa:i386. Preparing to unpack .../251-libglapi-mesa_22.3.6-1+deb12u1_i386.deb ... Unpacking libglapi-mesa:i386 (22.3.6-1+deb12u1) ... Selecting previously unselected package libx11-xcb1:i386. Preparing to unpack .../252-libx11-xcb1_2%3a1.8.4-2_i386.deb ... Unpacking libx11-xcb1:i386 (2:1.8.4-2) ... Selecting previously unselected package libxcb-dri2-0:i386. Preparing to unpack .../253-libxcb-dri2-0_1.15-1_i386.deb ... Unpacking libxcb-dri2-0:i386 (1.15-1) ... Selecting previously unselected package libxcb-dri3-0:i386. Preparing to unpack .../254-libxcb-dri3-0_1.15-1_i386.deb ... Unpacking libxcb-dri3-0:i386 (1.15-1) ... Selecting previously unselected package libxcb-present0:i386. Preparing to unpack .../255-libxcb-present0_1.15-1_i386.deb ... Unpacking libxcb-present0:i386 (1.15-1) ... Selecting previously unselected package libxcb-randr0:i386. Preparing to unpack .../256-libxcb-randr0_1.15-1_i386.deb ... Unpacking libxcb-randr0:i386 (1.15-1) ... Selecting previously unselected package libxcb-sync1:i386. Preparing to unpack .../257-libxcb-sync1_1.15-1_i386.deb ... Unpacking libxcb-sync1:i386 (1.15-1) ... Selecting previously unselected package libxcb-xfixes0:i386. Preparing to unpack .../258-libxcb-xfixes0_1.15-1_i386.deb ... Unpacking libxcb-xfixes0:i386 (1.15-1) ... Selecting previously unselected package libxshmfence1:i386. Preparing to unpack .../259-libxshmfence1_1.3-1_i386.deb ... Unpacking libxshmfence1:i386 (1.3-1) ... Selecting previously unselected package libegl-mesa0:i386. Preparing to unpack .../260-libegl-mesa0_22.3.6-1+deb12u1_i386.deb ... Unpacking libegl-mesa0:i386 (22.3.6-1+deb12u1) ... Selecting previously unselected package libegl1:i386. Preparing to unpack .../261-libegl1_1.6.0-1_i386.deb ... Unpacking libegl1:i386 (1.6.0-1) ... Selecting previously unselected package libxcb-glx0:i386. Preparing to unpack .../262-libxcb-glx0_1.15-1_i386.deb ... Unpacking libxcb-glx0:i386 (1.15-1) ... Selecting previously unselected package libxxf86vm1:i386. Preparing to unpack .../263-libxxf86vm1_1%3a1.1.4-1+b2_i386.deb ... Unpacking libxxf86vm1:i386 (1:1.1.4-1+b2) ... Selecting previously unselected package libdrm-amdgpu1:i386. Preparing to unpack .../264-libdrm-amdgpu1_2.4.114-1+b1_i386.deb ... Unpacking libdrm-amdgpu1:i386 (2.4.114-1+b1) ... Selecting previously unselected package libpciaccess0:i386. Preparing to unpack .../265-libpciaccess0_0.17-2_i386.deb ... Unpacking libpciaccess0:i386 (0.17-2) ... Selecting previously unselected package libdrm-intel1:i386. Preparing to unpack .../266-libdrm-intel1_2.4.114-1+b1_i386.deb ... Unpacking libdrm-intel1:i386 (2.4.114-1+b1) ... Selecting previously unselected package libdrm-nouveau2:i386. Preparing to unpack .../267-libdrm-nouveau2_2.4.114-1+b1_i386.deb ... Unpacking libdrm-nouveau2:i386 (2.4.114-1+b1) ... Selecting previously unselected package libdrm-radeon1:i386. Preparing to unpack .../268-libdrm-radeon1_2.4.114-1+b1_i386.deb ... Unpacking libdrm-radeon1:i386 (2.4.114-1+b1) ... Selecting previously unselected package libedit2:i386. Preparing to unpack .../269-libedit2_3.1-20221030-2_i386.deb ... Unpacking libedit2:i386 (3.1-20221030-2) ... Selecting previously unselected package libz3-4:i386. Preparing to unpack .../270-libz3-4_4.8.12-3.1_i386.deb ... Unpacking libz3-4:i386 (4.8.12-3.1) ... Selecting previously unselected package libllvm15:i386. Preparing to unpack .../271-libllvm15_1%3a15.0.6-4+b1_i386.deb ... Unpacking libllvm15:i386 (1:15.0.6-4+b1) ... Selecting previously unselected package libsensors-config. Preparing to unpack .../272-libsensors-config_1%3a3.6.0-7.1_all.deb ... Unpacking libsensors-config (1:3.6.0-7.1) ... Selecting previously unselected package libsensors5:i386. Preparing to unpack .../273-libsensors5_1%3a3.6.0-7.1_i386.deb ... Unpacking libsensors5:i386 (1:3.6.0-7.1) ... Selecting previously unselected package libgl1-mesa-dri:i386. Preparing to unpack .../274-libgl1-mesa-dri_22.3.6-1+deb12u1_i386.deb ... Unpacking libgl1-mesa-dri:i386 (22.3.6-1+deb12u1) ... Selecting previously unselected package libglx-mesa0:i386. Preparing to unpack .../275-libglx-mesa0_22.3.6-1+deb12u1_i386.deb ... Unpacking libglx-mesa0:i386 (22.3.6-1+deb12u1) ... Selecting previously unselected package libglx0:i386. Preparing to unpack .../276-libglx0_1.6.0-1_i386.deb ... Unpacking libglx0:i386 (1.6.0-1) ... Selecting previously unselected package libgl1:i386. Preparing to unpack .../277-libgl1_1.6.0-1_i386.deb ... Unpacking libgl1:i386 (1.6.0-1) ... Selecting previously unselected package libglx-dev:i386. Preparing to unpack .../278-libglx-dev_1.6.0-1_i386.deb ... Unpacking libglx-dev:i386 (1.6.0-1) ... Selecting previously unselected package libgl-dev:i386. Preparing to unpack .../279-libgl-dev_1.6.0-1_i386.deb ... Unpacking libgl-dev:i386 (1.6.0-1) ... Selecting previously unselected package libegl-dev:i386. Preparing to unpack .../280-libegl-dev_1.6.0-1_i386.deb ... Unpacking libegl-dev:i386 (1.6.0-1) ... Selecting previously unselected package libglvnd-core-dev:i386. Preparing to unpack .../281-libglvnd-core-dev_1.6.0-1_i386.deb ... Unpacking libglvnd-core-dev:i386 (1.6.0-1) ... Selecting previously unselected package libgles1:i386. Preparing to unpack .../282-libgles1_1.6.0-1_i386.deb ... Unpacking libgles1:i386 (1.6.0-1) ... Selecting previously unselected package libgles2:i386. Preparing to unpack .../283-libgles2_1.6.0-1_i386.deb ... Unpacking libgles2:i386 (1.6.0-1) ... Selecting previously unselected package libgles-dev:i386. Preparing to unpack .../284-libgles-dev_1.6.0-1_i386.deb ... Unpacking libgles-dev:i386 (1.6.0-1) ... Selecting previously unselected package libopengl0:i386. Preparing to unpack .../285-libopengl0_1.6.0-1_i386.deb ... Unpacking libopengl0:i386 (1.6.0-1) ... Selecting previously unselected package libopengl-dev:i386. Preparing to unpack .../286-libopengl-dev_1.6.0-1_i386.deb ... Unpacking libopengl-dev:i386 (1.6.0-1) ... Selecting previously unselected package libglvnd-dev:i386. Preparing to unpack .../287-libglvnd-dev_1.6.0-1_i386.deb ... Unpacking libglvnd-dev:i386 (1.6.0-1) ... Selecting previously unselected package libegl1-mesa-dev:i386. Preparing to unpack .../288-libegl1-mesa-dev_22.3.6-1+deb12u1_i386.deb ... Unpacking libegl1-mesa-dev:i386 (22.3.6-1+deb12u1) ... Selecting previously unselected package libepoxy-dev:i386. Preparing to unpack .../289-libepoxy-dev_1.5.10-1_i386.deb ... Unpacking libepoxy-dev:i386 (1.5.10-1) ... Selecting previously unselected package libfribidi-dev:i386. Preparing to unpack .../290-libfribidi-dev_1.0.8-2.1_i386.deb ... Unpacking libfribidi-dev:i386 (1.0.8-2.1) ... Selecting previously unselected package libgdk-pixbuf2.0-bin. Preparing to unpack .../291-libgdk-pixbuf2.0-bin_2.42.10+dfsg-1+b1_i386.deb ... Unpacking libgdk-pixbuf2.0-bin (2.42.10+dfsg-1+b1) ... Selecting previously unselected package libjpeg62-turbo-dev:i386. Preparing to unpack .../292-libjpeg62-turbo-dev_1%3a2.1.5-2_i386.deb ... Unpacking libjpeg62-turbo-dev:i386 (1:2.1.5-2) ... Selecting previously unselected package libjpeg-dev:i386. Preparing to unpack .../293-libjpeg-dev_1%3a2.1.5-2_i386.deb ... Unpacking libjpeg-dev:i386 (1:2.1.5-2) ... Selecting previously unselected package libjbig-dev:i386. Preparing to unpack .../294-libjbig-dev_2.1-6.1_i386.deb ... Unpacking libjbig-dev:i386 (2.1-6.1) ... Selecting previously unselected package liblzma-dev:i386. Preparing to unpack .../295-liblzma-dev_5.4.1-0.2_i386.deb ... Unpacking liblzma-dev:i386 (5.4.1-0.2) ... Selecting previously unselected package libzstd-dev:i386. Preparing to unpack .../296-libzstd-dev_1.5.4+dfsg2-5_i386.deb ... Unpacking libzstd-dev:i386 (1.5.4+dfsg2-5) ... Selecting previously unselected package libwebpmux3:i386. Preparing to unpack .../297-libwebpmux3_1.2.4-0.1_i386.deb ... Unpacking libwebpmux3:i386 (1.2.4-0.1) ... Selecting previously unselected package libwebpdemux2:i386. Preparing to unpack .../298-libwebpdemux2_1.2.4-0.1_i386.deb ... Unpacking libwebpdemux2:i386 (1.2.4-0.1) ... Selecting previously unselected package libwebp-dev:i386. Preparing to unpack .../299-libwebp-dev_1.2.4-0.1_i386.deb ... Unpacking libwebp-dev:i386 (1.2.4-0.1) ... Selecting previously unselected package libtiffxx6:i386. Preparing to unpack .../300-libtiffxx6_4.5.0-5_i386.deb ... Unpacking libtiffxx6:i386 (4.5.0-5) ... Selecting previously unselected package libdeflate-dev:i386. Preparing to unpack .../301-libdeflate-dev_1.14-1_i386.deb ... Unpacking libdeflate-dev:i386 (1.14-1) ... Selecting previously unselected package liblerc-dev:i386. Preparing to unpack .../302-liblerc-dev_4.0.0+ds-2_i386.deb ... Unpacking liblerc-dev:i386 (4.0.0+ds-2) ... Selecting previously unselected package libtiff-dev:i386. Preparing to unpack .../303-libtiff-dev_4.5.0-5_i386.deb ... Unpacking libtiff-dev:i386 (4.5.0-5) ... Selecting previously unselected package libgdk-pixbuf-2.0-dev:i386. Preparing to unpack .../304-libgdk-pixbuf-2.0-dev_2.42.10+dfsg-1+b1_i386.deb ... Unpacking libgdk-pixbuf-2.0-dev:i386 (2.42.10+dfsg-1+b1) ... Selecting previously unselected package libharfbuzz-icu0:i386. Preparing to unpack .../305-libharfbuzz-icu0_6.0.0+dfsg-3_i386.deb ... Unpacking libharfbuzz-icu0:i386 (6.0.0+dfsg-3) ... Selecting previously unselected package libharfbuzz-gobject0:i386. Preparing to unpack .../306-libharfbuzz-gobject0_6.0.0+dfsg-3_i386.deb ... Unpacking libharfbuzz-gobject0:i386 (6.0.0+dfsg-3) ... Selecting previously unselected package libharfbuzz-subset0:i386. Preparing to unpack .../307-libharfbuzz-subset0_6.0.0+dfsg-3_i386.deb ... Unpacking libharfbuzz-subset0:i386 (6.0.0+dfsg-3) ... Selecting previously unselected package libgraphite2-dev:i386. Preparing to unpack .../308-libgraphite2-dev_1.3.14-1_i386.deb ... Unpacking libgraphite2-dev:i386 (1.3.14-1) ... Selecting previously unselected package libicu-dev:i386. Preparing to unpack .../309-libicu-dev_72.1-3_i386.deb ... Unpacking libicu-dev:i386 (72.1-3) ... Selecting previously unselected package libharfbuzz-dev:i386. Preparing to unpack .../310-libharfbuzz-dev_6.0.0+dfsg-3_i386.deb ... Unpacking libharfbuzz-dev:i386 (6.0.0+dfsg-3) ... Selecting previously unselected package libdatrie-dev:i386. Preparing to unpack .../311-libdatrie-dev_0.2.13-2+b1_i386.deb ... Unpacking libdatrie-dev:i386 (0.2.13-2+b1) ... Selecting previously unselected package libthai-dev:i386. Preparing to unpack .../312-libthai-dev_0.1.29-1_i386.deb ... Unpacking libthai-dev:i386 (0.1.29-1) ... Selecting previously unselected package libxft-dev:i386. Preparing to unpack .../313-libxft-dev_2.3.6-1_i386.deb ... Unpacking libxft-dev:i386 (2.3.6-1) ... Selecting previously unselected package pango1.0-tools. Preparing to unpack .../314-pango1.0-tools_1.50.12+ds-1_i386.deb ... Unpacking pango1.0-tools (1.50.12+ds-1) ... Selecting previously unselected package libpango1.0-dev:i386. Preparing to unpack .../315-libpango1.0-dev_1.50.12+ds-1_i386.deb ... Unpacking libpango1.0-dev:i386 (1.50.12+ds-1) ... Selecting previously unselected package libwayland-bin. Preparing to unpack .../316-libwayland-bin_1.21.0-1_i386.deb ... Unpacking libwayland-bin (1.21.0-1) ... Selecting previously unselected package libwayland-dev:i386. Preparing to unpack .../317-libwayland-dev_1.21.0-1_i386.deb ... Unpacking libwayland-dev:i386 (1.21.0-1) ... Selecting previously unselected package libxcomposite-dev:i386. Preparing to unpack .../318-libxcomposite-dev_1%3a0.4.5-1_i386.deb ... Unpacking libxcomposite-dev:i386 (1:0.4.5-1) ... Selecting previously unselected package libxcursor-dev:i386. Preparing to unpack .../319-libxcursor-dev_1%3a1.2.1-1_i386.deb ... Unpacking libxcursor-dev:i386 (1:1.2.1-1) ... Selecting previously unselected package libxdamage-dev:i386. Preparing to unpack .../320-libxdamage-dev_1%3a1.1.6-1_i386.deb ... Unpacking libxdamage-dev:i386 (1:1.1.6-1) ... Selecting previously unselected package libxinerama-dev:i386. Preparing to unpack .../321-libxinerama-dev_2%3a1.1.4-3_i386.deb ... Unpacking libxinerama-dev:i386 (2:1.1.4-3) ... Selecting previously unselected package libxkbcommon-dev:i386. Preparing to unpack .../322-libxkbcommon-dev_1.5.0-1_i386.deb ... Unpacking libxkbcommon-dev:i386 (1.5.0-1) ... Selecting previously unselected package libxrandr-dev:i386. Preparing to unpack .../323-libxrandr-dev_2%3a1.5.2-2+b1_i386.deb ... Unpacking libxrandr-dev:i386 (2:1.5.2-2+b1) ... Selecting previously unselected package wayland-protocols. Preparing to unpack .../324-wayland-protocols_1.31-1_all.deb ... Unpacking wayland-protocols (1.31-1) ... Selecting previously unselected package libgtk-3-dev:i386. Preparing to unpack .../325-libgtk-3-dev_3.24.37-2_i386.deb ... Unpacking libgtk-3-dev:i386 (3.24.37-2) ... Selecting previously unselected package libayatana-ido3-dev. Preparing to unpack .../326-libayatana-ido3-dev_0.9.3-1_i386.deb ... Unpacking libayatana-ido3-dev (0.9.3-1) ... Selecting previously unselected package libayatana-indicator3-dev. Preparing to unpack .../327-libayatana-indicator3-dev_0.9.3-1_i386.deb ... Unpacking libayatana-indicator3-dev (0.9.3-1) ... Selecting previously unselected package libxml2-utils. Preparing to unpack .../328-libxml2-utils_2.9.14+dfsg-1.1+b3_i386.deb ... Unpacking libxml2-utils (2.9.14+dfsg-1.1+b3) ... Selecting previously unselected package libgtk2.0-dev:i386. Preparing to unpack .../329-libgtk2.0-dev_2.24.33-2_i386.deb ... Unpacking libgtk2.0-dev:i386 (2.24.33-2) ... Selecting previously unselected package libdbusmenu-glib-dev:i386. Preparing to unpack .../330-libdbusmenu-glib-dev_18.10.20180917~bzr492+repack1-3_i386.deb ... Unpacking libdbusmenu-glib-dev:i386 (18.10.20180917~bzr492+repack1-3) ... Selecting previously unselected package libayatana-appindicator3-dev. Preparing to unpack .../331-libayatana-appindicator3-dev_0.5.92-1_i386.deb ... Unpacking libayatana-appindicator3-dev (0.5.92-1) ... Selecting previously unselected package libelf-dev:i386. Preparing to unpack .../332-libelf-dev_0.188-2.1_i386.deb ... Unpacking libelf-dev:i386 (0.188-2.1) ... Selecting previously unselected package libdw-dev:i386. Preparing to unpack .../333-libdw-dev_0.188-2.1_i386.deb ... Unpacking libdw-dev:i386 (0.188-2.1) ... Selecting previously unselected package libgconf2-dev. Preparing to unpack .../334-libgconf2-dev_3.2.6-8_i386.deb ... Unpacking libgconf2-dev (3.2.6-8) ... Selecting previously unselected package libunwind-dev:i386. Preparing to unpack .../335-libunwind-dev_1.6.2-3_i386.deb ... Unpacking libunwind-dev:i386 (1.6.2-3) ... Selecting previously unselected package libgstreamer1.0-dev:i386. Preparing to unpack .../336-libgstreamer1.0-dev_1.22.0-2_i386.deb ... Unpacking libgstreamer1.0-dev:i386 (1.22.0-2) ... Selecting previously unselected package libnotify-dev:i386. Preparing to unpack .../337-libnotify-dev_0.8.1-1_i386.deb ... Unpacking libnotify-dev:i386 (0.8.1-1) ... Selecting previously unselected package libxml2-dev:i386. Preparing to unpack .../338-libxml2-dev_2.9.14+dfsg-1.1+b3_i386.deb ... Unpacking libxml2-dev:i386 (2.9.14+dfsg-1.1+b3) ... Setting up media-types (10.0.0) ... Setting up libpipeline1:i386 (1.5.7-1) ... Setting up libgraphite2-3:i386 (1.3.14-1) ... Setting up liblcms2-2:i386 (2.14-2) ... Setting up libpixman-1-0:i386 (0.42.2-1) ... Setting up libwayland-server0:i386 (1.21.0-1) ... Setting up libpciaccess0:i386 (0.17-2) ... Setting up systemd-sysv (252.6-1) ... Setting up libxau6:i386 (1:1.0.9-1) ... Setting up libpsl5:i386 (0.21.2-1) ... Setting up libpixman-1-dev:i386 (0.42.2-1) ... Setting up libicu72:i386 (72.1-3) ... Setting up liblerc4:i386 (4.0.0+ds-2) ... Setting up libzstd-dev:i386 (1.5.4+dfsg2-5) ... Setting up bsdextrautils (2.38.1-5+b1) ... Setting up libglvnd-core-dev:i386 (1.6.0-1) ... Setting up hicolor-icon-theme (0.17-2) ... Setting up libdatrie1:i386 (0.2.13-2+b1) ... Setting up libmagic-mgc (1:5.44-3) ... Setting up psmisc (23.6-1) ... Setting up libclone-perl:i386 (0.46-1) ... Setting up libarchive-zip-perl (1.68-1) ... Setting up libglib2.0-0:i386 (2.74.6-1) ... Setting up libglvnd0:i386 (1.6.0-1) ... Setting up libhtml-tagset-perl (3.20-6) ... Setting up libdbusmenu-glib4:i386 (18.10.20180917~bzr492+repack1-3) ... Setting up libdebhelper-perl (13.11.4) ... Setting up libbrotli1:i386 (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:i386 (1.52.0-1) ... Setting up libmagic1:i386 (1:5.44-3) ... Setting up libdeflate0:i386 (1.14-1) ... Setting up perl-openssl-defaults:i386 (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:i386 (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:i386 (3.4.4-1) ... Setting up libunwind8:i386 (1.6.2-3) ... Setting up libpthread-stubs0-dev:i386 (0.4-1) ... Setting up libjbig0:i386 (2.1-6.1) ... Setting up libpcre2-16-0:i386 (10.42-1) ... Setting up libcolord2:i386 (1.4.6-2.2) ... Setting up libopengl0:i386 (1.6.0-1) ... Setting up libsasl2-modules-db:i386 (2.1.28+dfsg-10) ... Setting up libcap2-bin (1:2.66-3) ... Setting up libdconf1:i386 (0.40.0-4) ... Setting up xtrans-dev (1.4.0-1) ... Setting up libgraphite2-dev:i386 (1.3.14-1) ... Setting up autotools-dev (20220109.1) ... Setting up libz3-4:i386 (4.8.12-3.1) ... Setting up libpcre2-32-0:i386 (10.42-1) ... Setting up libglib2.0-data (2.74.6-1) ... Setting up libpkgconf3:i386 (1.8.1-1) ... Setting up libuv1:i386 (1.44.2-1) ... Setting up libgles2:i386 (1.6.0-1) ... Setting up libexpat1-dev:i386 (2.5.0-1) ... Setting up libjpeg62-turbo:i386 (1:2.1.5-2) ... Setting up libx11-data (2:1.8.4-2) ... Setting up libjpeg62-turbo-dev:i386 (1:2.1.5-2) ... Setting up libepoxy0:i386 (1.5.10-1) ... Setting up librtmp1:i386 (2.4+20151223.gitfa8646d.1-2+b2) ... Setting up uuid-dev:i386 (2.38.1-5+b1) ... Setting up libavahi-common-data:i386 (0.8-9) ... Setting up libgles1:i386 (1.6.0-1) ... Setting up libdbus-1-3:i386 (1.14.6-1) ... Setting up libfribidi0:i386 (1.0.8-2.1) ... Setting up libproc2-0:i386 (2:4.0.2-3) ... Setting up libpng16-16:i386 (1.6.39-2) ... Setting up libio-html-perl (1.004-3) ... Setting up autopoint (0.21-12) ... Setting up libjsoncpp25:i386 (1.9.5-4) ... Setting up icu-devtools (72.1-3) ... Setting up fonts-dejavu-core (2.37-6) ... Setting up libsepol-dev:i386 (3.4-2) ... Setting up pkgconf-bin (1.8.1-1) ... Setting up libsensors5:i386 (1:3.6.0-7.1) ... Setting up liblerc-dev:i386 (4.0.0+ds-2) ... Setting up libglapi-mesa:i386 (22.3.6-1+deb12u1) ... Setting up libsasl2-2:i386 (2.1.28+dfsg-10) ... Setting up autoconf (2.71-3) ... Setting up libwebp7:i386 (1.2.4-0.1) ... Setting up libtimedate-perl (2.3300-2) ... Setting up libregexp-ipv6-perl (0.03-3) ... Setting up liblzma-dev:i386 (5.4.1-0.2) ... Setting up zlib1g-dev:i386 (1:1.2.13.dfsg-1) ... Setting up libpcre2-posix3:i386 (10.42-1) ... Setting up wayland-protocols (1.31-1) ... Setting up sensible-utils (0.0.17+nmu1) ... Setting up libxshmfence1:i386 (1.3-1) ... Setting up at-spi2-common (2.46.0-5) ... Setting up librhash0:i386 (1.4.3-3) ... Setting up libtiff6:i386 (4.5.0-5) ... Setting up dbus-session-bus-common (1.14.6-1) ... Setting up libuchardet0:i386 (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:i386 (1.74.0-3) ... Setting up libssh2-1:i386 (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:i386 (2.46.0-5) ... Setting up libwayland-egl1:i386 (1.21.0-1) ... Setting up libopengl-dev:i386 (1.6.0-1) ... Setting up dbus-system-bus-common (1.14.6-1) ... Setting up openssl (3.0.8-1) ... Setting up libwebpmux3:i386 (1.2.4-0.1) ... Setting up libbsd0:i386 (0.11.7-2) ... Setting up libtiffxx6:i386 (4.5.0-5) ... Setting up libdeflate-dev:i386 (1.14-1) ... Setting up libdrm-common (2.4.114-1) ... Setting up libelf1:i386 (0.188-2.1) ... Setting up readline-common (8.2-1.3) ... Setting up libicu-dev:i386 (72.1-3) ... Setting up libxml2:i386 (2.9.14+dfsg-1.1+b3) ... Setting up liburi-perl (5.17-1) ... Setting up dbus-bin (1.14.6-1) ... Setting up libbrotli-dev:i386 (1.0.9-2+b6) ... Setting up libxkbcommon0:i386 (1.5.0-1) ... Setting up libwayland-client0:i386 (1.21.0-1) ... Setting up libnet-ssleay-perl:i386 (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:i386 (2.38.1-5+b1) ... Setting up libice6:i386 (2:1.0.10-1) ... Setting up libhttp-date-perl (6.05-2) ... Setting up libdw1:i386 (0.188-2.1) ... Setting up libxdmcp6:i386 (1:1.1.2-3) ... Setting up libxcb1:i386 (1.15-1) ... Setting up gettext (0.21-12) ... Setting up libxcb-xfixes0:i386 (1.15-1) ... Setting up libfile-listing-perl (6.15-1) ... Setting up libxau-dev:i386 (1:1.0.9-1) ... Setting up libunwind-dev:i386 (1.6.2-3) ... Setting up libpcre2-dev:i386 (10.42-1) ... Setting up libice-dev:i386 (2:1.0.10-1) ... Setting up libtool (2.4.7-5) ... Setting up libarchive13:i386 (3.6.2-1) ... Setting up libxcb-render0:i386 (1.15-1) ... Setting up libselinux1-dev:i386 (3.4-1+b5) ... Setting up fontconfig-config (2.14.1-4) ... Setting up libfribidi-dev:i386 (1.0.8-2.1) ... Setting up libxcb-glx0:i386 (1.15-1) ... Setting up libwebpdemux2:i386 (1.2.4-0.1) ... Setting up libxkbcommon-dev:i386 (1.5.0-1) ... Setting up libedit2:i386 (3.1-20221030-2) ... Setting up libreadline8:i386 (8.2-1.3) ... Setting up libpng-dev:i386 (1.6.39-2) ... Setting up libavahi-common3:i386 (0.8-9) ... Setting up libjpeg-dev:i386 (1:2.1.5-2) ... Setting up libjbig-dev:i386 (2.1-6.1) ... Setting up libglib2.0-bin (2.74.6-1) ... Setting up libnet-http-perl (6.22-1) ... Setting up libxcb-shm0:i386 (1.15-1) ... Setting up dbus-daemon (1.14.6-1) ... Setting up libldap-2.5-0:i386 (2.5.13+dfsg-5) ... Setting up pkgconf:i386 (1.8.1-1) ... Setting up intltool-debian (0.35.0+20060710.6) ... Setting up libxcb-present0:i386 (1.15-1) ... Setting up dh-autoreconf (20) ... Setting up libthai0:i386 (0.1.29-1) ... Setting up ca-certificates (20230311) ... Updating certificates in /etc/ssl/certs... 140 added, 0 removed; done. Setting up libxdmcp-dev:i386 (1:1.1.2-3) ... Setting up libwayland-bin (1.21.0-1) ... Setting up libxml2-dev:i386 (2.9.14+dfsg-1.1+b3) ... Setting up libwebp-dev:i386 (1.2.4-0.1) ... Setting up libfreetype6:i386 (2.12.1+dfsg-4) ... Setting up libtiff-dev:i386 (4.5.0-5) ... Setting up libxcb-sync1:i386 (1.15-1) ... Setting up libdbus-glib-1-2:i386 (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:i386 (0.188-2.1) ... Setting up pkg-config:i386 (1.8.1-1) ... Setting up ucf (3.0043+nmu1) ... Setting up gir1.2-glib-2.0:i386 (1.74.0-3) ... Setting up libxcb-dri2-0:i386 (1.15-1) ... Setting up dh-strip-nondeterminism (1.13.1-1) ... Setting up libwww-robotrules-perl (6.02-1) ... Setting up libdrm2:i386 (2.4.114-1+b1) ... Setting up dwz (0.15-1) ... Setting up libdatrie-dev:i386 (0.2.13-2+b1) ... Setting up groff-base (1.22.4-10) ... Setting up libwayland-cursor0:i386 (1.21.0-1) ... Setting up libxcb-randr0:i386 (1.15-1) ... Setting up xml-core (0.18+nmu1) ... Setting up libhtml-parser-perl:i386 (3.81-1) ... Setting up libllvm15:i386 (1:15.0.6-4+b1) ... Setting up libpam-systemd:i386 (252.6-1) ... Setting up libcurl4:i386 (7.88.1-8) ... Setting up libx11-6:i386 (2:1.8.4-2) ... Setting up libharfbuzz0b:i386 (6.0.0+dfsg-3) ... Setting up libgdk-pixbuf-2.0-0:i386 (2.42.10+dfsg-1+b1) ... Setting up libfontconfig1:i386 (2.14.1-4) ... Setting up libxml2-utils (2.9.14+dfsg-1.1+b3) ... Setting up libxcomposite1:i386 (1:0.4.5-1) ... Setting up libsm6:i386 (2:1.2.3-1) ... Setting up libavahi-client3:i386 (0.8-9) ... Setting up libmount-dev:i386 (2.38.1-5+b1) ... Setting up libio-socket-ssl-perl (2.081-2) ... Setting up libgstreamer1.0-0:i386 (1.22.0-2) ... Setcap worked! gst-ptp-helper is not suid! Setting up libhttp-message-perl (6.44-1) ... Setting up libdrm-amdgpu1:i386 (2.4.114-1+b1) ... Setting up libxcb-dri3-0:i386 (1.15-1) ... Setting up gtk-update-icon-cache (3.24.37-2) ... Setting up libx11-xcb1:i386 (2:1.8.4-2) ... Setting up gir1.2-gstreamer-1.0:i386 (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:i386 (2.4.114-1+b1) ... Setting up gir1.2-freedesktop:i386 (1.74.0-3) ... Setting up libharfbuzz-icu0:i386 (6.0.0+dfsg-3) ... Setting up libxdamage1:i386 (1:1.1.6-1) ... Setting up libxcb1-dev:i386 (1.15-1) ... Setting up gir1.2-dbusmenu-glib-0.4:i386 (18.10.20180917~bzr492+repack1-3) ... Setting up libxrender1:i386 (1:0.9.10-1.1) ... Setting up gir1.2-gdkpixbuf-2.0:i386 (2.42.10+dfsg-1+b1) ... Setting up libgbm1:i386 (22.3.6-1+deb12u1) ... Setting up libhttp-cookies-perl (6.10-1) ... Setting up gir1.2-atk-1.0:i386 (2.46.0-5) ... Setting up libsm-dev:i386 (2:1.2.3-1) ... Setting up libdrm-radeon1:i386 (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:i386 (3.11.2-6) ... Setting up libpango-1.0-0:i386 (1.50.12+ds-1) ... Setting up libdrm-intel1:i386 (2.4.114-1+b1) ... Setting up libgl1-mesa-dri:i386 (22.3.6-1+deb12u1) ... Setting up libx11-dev:i386 (2:1.8.4-2) ... Setting up libxext6:i386 (2:1.3.4-1+b1) ... Setting up libharfbuzz-gobject0:i386 (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:i386 (1.21.0-1) ... Setting up gir1.2-harfbuzz-0.0:i386 (6.0.0+dfsg-3) ... Setting up libdw-dev:i386 (0.188-2.1) ... Setting up libcairo2:i386 (1.16.0-7) ... Setting up libxxf86vm1:i386 (1:1.1.4-1+b2) ... Setting up libfreetype-dev:i386 (2.12.1+dfsg-4) ... Setting up libxcb-shm0-dev:i386 (1.15-1) ... Setting up dbus-user-session (1.14.6-1) ... Setting up libegl-mesa0:i386 (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:i386 (1:6.0.0-2) ... Setting up libnotify4:i386 (0.8.1-1) ... Setting up libxinerama1:i386 (2:1.1.4-3) ... Setting up libxrandr2:i386 (2:1.5.2-2+b1) ... Setting up libxcb-render0-dev:i386 (1.15-1) ... Setting up libxext-dev:i386 (2:1.3.4-1+b1) ... Setting up libthai-dev:i386 (0.1.29-1) ... Setting up libcups2:i386 (2.4.2-3) ... Setting up gir1.2-notify-0.7:i386 (0.8.1-1) ... Setting up libgdk-pixbuf2.0-bin (2.42.10+dfsg-1+b1) ... Setting up libegl1:i386 (1.6.0-1) ... Setting up libharfbuzz-subset0:i386 (6.0.0+dfsg-3) ... Setting up cmake (3.25.1-1) ... Setting up libcairo-gobject2:i386 (1.16.0-7) ... Setting up libpangoft2-1.0-0:i386 (1.50.12+ds-1) ... Setting up libxrender-dev:i386 (1:0.9.10-1.1) ... Setting up libpangocairo-1.0-0:i386 (1.50.12+ds-1) ... Setting up libpython3-stdlib:i386 (3.11.2-1+b1) ... Setting up libcairo-script-interpreter2:i386 (1.16.0-7) ... Setting up python3.11 (3.11.2-6) ... Setting up libxft2:i386 (2.3.6-1) ... Setting up libdbusmenu-gtk3-4:i386 (18.10.20180917~bzr492+repack1-3) ... Setting up libglx-mesa0:i386 (22.3.6-1+deb12u1) ... Setting up libpangoxft-1.0-0:i386 (1.50.12+ds-1) ... Setting up libxi6:i386 (2:1.8-1+b1) ... Setting up libglx0:i386 (1.6.0-1) ... Setting up libgconf-2-4:i386 (3.2.6-8) ... Setting up libfontconfig-dev:i386 (2.14.1-4) ... Setting up libxtst6:i386 (2:1.2.3-1.1) ... Setting up libxcursor1:i386 (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:i386 (2.46.0-5) ... Setting up librsvg2-2:i386 (2.54.5+dfsg-1) ... Setting up libxfixes-dev:i386 (1:6.0.0-2) ... Setting up libatk-bridge2.0-0:i386 (2.46.0-5) ... Setting up gir1.2-pango-1.0:i386 (1.50.12+ds-1) ... Setting up libxrandr-dev:i386 (2:1.5.2-2+b1) ... Setting up libgl1:i386 (1.6.0-1) ... Setting up libxinerama-dev:i386 (2:1.1.4-3) ... Setting up librsvg2-common:i386 (2.54.5+dfsg-1) ... Setting up gconf-service (3.2.6-8) ... Setting up libglx-dev:i386 (1.6.0-1) ... Setting up libxi-dev:i386 (2:1.8-1+b1) ... Setting up python3-lib2to3 (3.11.2-2) ... Setting up libgl-dev:i386 (1.6.0-1) ... Setting up libxft-dev:i386 (2.3.6-1) ... Setting up libxtst-dev:i386 (2:1.2.3-1.1) ... Setting up python3-distutils (3.11.2-2) ... Setting up libxdamage-dev:i386 (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-1) ... Setting up dconf-gsettings-backend:i386 (0.40.0-4) ... Setting up libegl-dev:i386 (1.6.0-1) ... Setting up libxcomposite-dev:i386 (1:0.4.5-1) ... Setting up libxcursor-dev:i386 (1:1.2.1-1) ... Setting up libgtk2.0-0:i386 (2.24.33-2) ... Setting up libepoxy-dev:i386 (1.5.10-1) ... Setting up gir1.2-atspi-2.0:i386 (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:i386 (2.74.6-1) ... Setting up gir1.2-gtk-2.0:i386 (2.24.33-2) ... Setting up libcairo2-dev:i386 (1.16.0-7) ... Setting up libgles-dev:i386 (1.6.0-1) ... Setting up libgtk-3-common (3.24.37-2) ... Setting up libatk1.0-dev:i386 (2.46.0-5) ... Setting up libgdk-pixbuf-2.0-dev:i386 (2.42.10+dfsg-1+b1) ... Setting up libharfbuzz-dev:i386 (6.0.0+dfsg-3) ... Setting up libnotify-dev:i386 (0.8.1-1) ... Setting up libgstreamer1.0-dev:i386 (1.22.0-2) ... Setting up libgtk-3-0:i386 (3.24.37-2) ... Setting up gir1.2-gtk-3.0:i386 (3.24.37-2) ... Setting up libglvnd-dev:i386 (1.6.0-1) ... Setting up libayatana-ido3-0.4-0:i386 (0.9.3-1) ... Setting up libpango1.0-dev:i386 (1.50.12+ds-1) ... Setting up gir1.2-ayatanaido3-0.4:i386 (0.9.3-1) ... Setting up libgtk2.0-dev:i386 (2.24.33-2) ... Setting up libayatana-indicator3-7:i386 (0.9.3-1) ... Setting up libegl1-mesa-dev:i386 (22.3.6-1+deb12u1) ... Setting up libayatana-appindicator3-1 (0.5.92-1) ... Setting up libdbusmenu-glib-dev:i386 (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-8) ... Processing triggers for systemd (252.6-1) ... Processing triggers for sgml-base (1.31) ... Setting up libdbus-1-dev:i386 (1.14.6-1) ... Setting up libatspi2.0-dev:i386 (2.46.0-5) ... Setting up libgconf2-dev (3.2.6-8) ... Setting up libatk-bridge2.0-dev:i386 (2.46.0-5) ... Setting up libgtk-3-dev:i386 (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:i386 (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... usrmerge is already the newest version (35). 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: user script /srv/workspace/pbuilder/651/tmp/hooks/A99_set_merged_usr starting Re-configuring usrmerge... removed '/etc/unsupported-skip-usrmerge-conversion' The system has been successfully converted. I: user script /srv/workspace/pbuilder/651/tmp/hooks/A99_set_merged_usr finished hostname: Name or service not known I: Running cd /build/alarm-clock-applet-0.4.1/ && env PATH="/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/i/capture/the/path" HOME="/nonexistent/second-build" dpkg-buildpackage -us -uc -b && env PATH="/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/i/capture/the/path" HOME="/nonexistent/second-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 i386 fakeroot debian/rules clean dh clean dh_clean debian/rules build dh build dh_update_autotools_config dh_autoreconf dh_auto_configure cd obj-i686-linux-gnu && 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/i386-linux-gnu .. -- 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-i686-linux-gnu dh_auto_build cd obj-i686-linux-gnu && make -j7 "INSTALL=install --strip-program=true" VERBOSE=1 make[1]: Entering directory '/build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu' /usr/bin/cmake -S/build/alarm-clock-applet-0.4.1 -B/build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu --check-build-system CMakeFiles/Makefile.cmake 0 /usr/bin/cmake -E cmake_progress_start /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/CMakeFiles /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu//CMakeFiles/progress.marks make -f CMakeFiles/Makefile2 all make[2]: Entering directory '/build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu' 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[3]: Entering directory '/build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu' cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu && /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-i686-linux-gnu /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/gconf-migration /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/gconf-migration/CMakeFiles/alarm-clock-applet-gconf-migration.dir/DependInfo.cmake --color= make[3]: Entering directory '/build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu' cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu && /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-i686-linux-gnu /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po/CMakeFiles/translations_1.dir/DependInfo.cmake --color= 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-i686-linux-gnu' cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu && /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-i686-linux-gnu /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po/CMakeFiles/linguas.dir/DependInfo.cmake --color= make -f src/CMakeFiles/man-alarm-clock-applet.dir/build.make src/CMakeFiles/man-alarm-clock-applet.dir/depend make[3]: Leaving directory '/build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu' make[3]: Leaving directory '/build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu' 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-i686-linux-gnu' cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu && /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-i686-linux-gnu /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/src /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/src/CMakeFiles/man-alarm-clock-applet.dir/DependInfo.cmake --color= 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-i686-linux-gnu' make[3]: Entering directory '/build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu' make[3]: Leaving directory '/build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu' [ 1%] Generating ar.gmo cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/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 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-i686-linux-gnu' make[3]: Leaving directory '/build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu' [ 3%] Generating ast.gmo make -f po/CMakeFiles/linguas.dir/build.make po/CMakeFiles/linguas.dir/build [ 5%] Building C object gconf-migration/CMakeFiles/alarm-clock-applet-gconf-migration.dir/alarm-clock-gconf-migration.c.o [ 6%] Generating be.gmo cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/gconf-migration && /usr/bin/cc -I/build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu -I/usr/include/gconf/2 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -I/usr/include/dbus-1.0 -I/usr/lib/i386-linux-gnu/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 make[3]: Entering directory '/build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu' make[3]: Nothing to be done for 'po/CMakeFiles/linguas.dir/build'. make[3]: Leaving directory '/build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu' cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/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 [ 8%] Generating alarm-clock-applet.1 cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/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-i686-linux-gnu/src/alarm-clock-applet.1 cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/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-i686-linux-gnu/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po/ar.gmo /build/alarm-clock-applet-0.4.1/po/ar.po [ 10%] Generating bg.gmo [ 10%] Built target linguas cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/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-i686-linux-gnu/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po/ast.gmo /build/alarm-clock-applet-0.4.1/po/ast.po cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po/be.gmo /build/alarm-clock-applet-0.4.1/po/be.po [ 11%] Generating ca.gmo cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po/bg.gmo /build/alarm-clock-applet-0.4.1/po/bg.po cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/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 [ 13%] Generating cs.gmo [ 15%] Generating da.gmo cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po/ca.gmo /build/alarm-clock-applet-0.4.1/po/ca.po cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/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 [ 16%] Generating de.gmo [ 18%] Generating el.gmo cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/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 cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/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-i686-linux-gnu/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-i686-linux-gnu/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po/cs.gmo /build/alarm-clock-applet-0.4.1/po/cs.po cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po/da.gmo /build/alarm-clock-applet-0.4.1/po/da.po cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po/de.gmo /build/alarm-clock-applet-0.4.1/po/de.po [ 20%] Generating es.gmo cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po/el.gmo /build/alarm-clock-applet-0.4.1/po/el.po cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/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 [ 22%] Generating alarm-clock-applet.1.gz cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/src && /usr/bin/gzip -f -k --best -n /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/src/alarm-clock-applet.1 make[3]: Leaving directory '/build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu' [ 23%] Generating et.gmo [ 25%] Generating fi.gmo cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po/es.gmo /build/alarm-clock-applet-0.4.1/po/es.po cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/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-i686-linux-gnu/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 [ 27%] Generating fr.gmo cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/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 [ 27%] Built target man-alarm-clock-applet [ 28%] Generating fo.gmo cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/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-i686-linux-gnu/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po/et.gmo /build/alarm-clock-applet-0.4.1/po/et.po [ 30%] Generating gl.gmo cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po/fi.gmo /build/alarm-clock-applet-0.4.1/po/fi.po cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/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-i686-linux-gnu/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po/fr.gmo /build/alarm-clock-applet-0.4.1/po/fr.po cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po/fo.gmo /build/alarm-clock-applet-0.4.1/po/fo.po [ 32%] Generating he.gmo cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/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 [ 33%] Generating hi.gmo [ 35%] Generating hu.gmo cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po/gl.gmo /build/alarm-clock-applet-0.4.1/po/gl.po cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/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-i686-linux-gnu/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 [ 37%] Generating id.gmo cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/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-i686-linux-gnu/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po/he.gmo /build/alarm-clock-applet-0.4.1/po/he.po cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po/hi.gmo /build/alarm-clock-applet-0.4.1/po/hi.po [ 38%] Generating it.gmo cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po/hu.gmo /build/alarm-clock-applet-0.4.1/po/hu.po [ 40%] Generating ja.gmo cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/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-i686-linux-gnu/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po/id.gmo /build/alarm-clock-applet-0.4.1/po/id.po cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/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-i686-linux-gnu/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po/it.gmo /build/alarm-clock-applet-0.4.1/po/it.po [ 42%] Generating ka.gmo cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/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 [ 44%] Generating la.gmo cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po/ja.gmo /build/alarm-clock-applet-0.4.1/po/ja.po cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/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 [ 47%] Generating nb.gmo cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/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-i686-linux-gnu/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po/ka.gmo /build/alarm-clock-applet-0.4.1/po/ka.po [ 49%] Generating nl.gmo cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/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-i686-linux-gnu/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 cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po/la.gmo /build/alarm-clock-applet-0.4.1/po/la.po cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po/ms.gmo /build/alarm-clock-applet-0.4.1/po/ms.po [ 50%] Generating nn.gmo cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po/nb.gmo /build/alarm-clock-applet-0.4.1/po/nb.po cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po/nl.gmo /build/alarm-clock-applet-0.4.1/po/nl.po cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/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 [ 52%] Generating pl.gmo cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/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 [ 54%] Generating pt_BR.gmo cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/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 [ 55%] Linking C executable alarm-clock-applet-gconf-migration cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/gconf-migration && /usr/bin/cmake -E cmake_link_script CMakeFiles/alarm-clock-applet-gconf-migration.dir/link.txt --verbose=1 [ 57%] Generating ru.gmo cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/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 [ 59%] Generating pt.gmo [ 61%] Generating si.gmo cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po/nn.gmo /build/alarm-clock-applet-0.4.1/po/nn.po /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-i686-linux-gnu/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-i686-linux-gnu/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po/pl.gmo /build/alarm-clock-applet-0.4.1/po/pl.po cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/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 cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po/pt_BR.gmo /build/alarm-clock-applet-0.4.1/po/pt_BR.po cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po/ru.gmo /build/alarm-clock-applet-0.4.1/po/ru.po cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po/pt.gmo /build/alarm-clock-applet-0.4.1/po/pt.po [ 62%] Generating sv.gmo cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po/si.gmo /build/alarm-clock-applet-0.4.1/po/si.po cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/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 [ 64%] Generating tr.gmo cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/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 [ 66%] Generating uk.gmo cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/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 cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po/sv.gmo /build/alarm-clock-applet-0.4.1/po/sv.po [ 67%] Generating zh_CN.gmo cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/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 make[3]: Leaving directory '/build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu' [ 69%] Generating zh_TW.gmo cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po/uk.gmo /build/alarm-clock-applet-0.4.1/po/uk.po cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po/tr.gmo /build/alarm-clock-applet-0.4.1/po/tr.po cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/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 [ 69%] Built target alarm-clock-applet-gconf-migration cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po/zh_CN.gmo /build/alarm-clock-applet-0.4.1/po/zh_CN.po cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po && /usr/bin/msgfmt -o /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/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-i686-linux-gnu' [ 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-i686-linux-gnu' cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu && /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-i686-linux-gnu /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po/CMakeFiles/translations.dir/DependInfo.cmake --color= make[3]: Leaving directory '/build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu' 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-i686-linux-gnu' make[3]: Nothing to be done for 'po/CMakeFiles/translations.dir/build'. make[3]: Leaving directory '/build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu' [ 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-i686-linux-gnu' [ 71%] Generating io.github.alarm-clock-applet.enums.gschema.xml cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/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-i686-linux-gnu/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-glib-enums.h [ 76%] Generating alarm-clock-applet.desktop cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/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 cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/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/ [ 77%] Generating autostart/alarm-clock-applet.desktop cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/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-i686-linux-gnu && /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-i686-linux-gnu /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/src /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/src/CMakeFiles/alarm-clock-applet.dir/DependInfo.cmake --color= make[3]: Leaving directory '/build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu' 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-i686-linux-gnu' [ 79%] Building C object src/CMakeFiles/alarm-clock-applet.dir/alarm-applet.c.o cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/src && /usr/bin/cc -DG_LOG_DOMAIN=\"alarm-clock-applet\" -I/build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/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/i386-linux-gnu/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-i686-linux-gnu/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 [ 81%] Building C object src/CMakeFiles/alarm-clock-applet.dir/player.c.o cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/src && /usr/bin/cc -DG_LOG_DOMAIN=\"alarm-clock-applet\" -I/build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/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/i386-linux-gnu/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-i686-linux-gnu/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 [ 84%] Building C object src/CMakeFiles/alarm-clock-applet.dir/util.c.o [ 84%] Building C object src/CMakeFiles/alarm-clock-applet.dir/list-entry.c.o cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/src && /usr/bin/cc -DG_LOG_DOMAIN=\"alarm-clock-applet\" -I/build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/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/i386-linux-gnu/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-i686-linux-gnu/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 [ 86%] Building C object src/CMakeFiles/alarm-clock-applet.dir/alarm.c.o cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/src && /usr/bin/cc -DG_LOG_DOMAIN=\"alarm-clock-applet\" -I/build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/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/i386-linux-gnu/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-i686-linux-gnu/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 [ 88%] Building C object src/CMakeFiles/alarm-clock-applet.dir/alarm-gsettings.c.o cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/src && /usr/bin/cc -DG_LOG_DOMAIN=\"alarm-clock-applet\" -I/build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/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/i386-linux-gnu/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-i686-linux-gnu/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 [ 89%] Building C object src/CMakeFiles/alarm-clock-applet.dir/ui.c.o cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/src && /usr/bin/cc -DG_LOG_DOMAIN=\"alarm-clock-applet\" -I/build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/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/i386-linux-gnu/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-i686-linux-gnu/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 cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/src && /usr/bin/cc -DG_LOG_DOMAIN=\"alarm-clock-applet\" -I/build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/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/i386-linux-gnu/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-i686-linux-gnu/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-i686-linux-gnu/src && /usr/bin/cc -DG_LOG_DOMAIN=\"alarm-clock-applet\" -I/build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/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/i386-linux-gnu/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-i686-linux-gnu/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-i686-linux-gnu/src && /usr/bin/cc -DG_LOG_DOMAIN=\"alarm-clock-applet\" -I/build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/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/i386-linux-gnu/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-i686-linux-gnu/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-i686-linux-gnu/src && /usr/bin/cc -DG_LOG_DOMAIN=\"alarm-clock-applet\" -I/build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/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/i386-linux-gnu/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-i686-linux-gnu/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-i686-linux-gnu/src && /usr/bin/cc -DG_LOG_DOMAIN=\"alarm-clock-applet\" -I/build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/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/i386-linux-gnu/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-i686-linux-gnu/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-i686-linux-gnu/src && /usr/bin/cc -DG_LOG_DOMAIN=\"alarm-clock-applet\" -I/build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/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/i386-linux-gnu/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-i686-linux-gnu/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-i686-linux-gnu/src/alarm-glib-enums.c [100%] Linking C executable alarm-clock-applet cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/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-i686-linux-gnu' [100%] Built target alarm-clock-applet make[2]: Leaving directory '/build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu' /usr/bin/cmake -E cmake_progress_start /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/CMakeFiles 0 make[1]: Leaving directory '/build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu' create-stamp debian/debhelper-build-stamp fakeroot debian/rules binary dh binary dh_testroot dh_prep dh_auto_install cd obj-i686-linux-gnu && make -j7 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-i686-linux-gnu' /usr/bin/cmake -S/build/alarm-clock-applet-0.4.1 -B/build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu --check-build-system CMakeFiles/Makefile.cmake 0 /usr/bin/cmake -E cmake_progress_start /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/CMakeFiles /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu//CMakeFiles/progress.marks make -f CMakeFiles/Makefile2 all make[2]: Entering directory '/build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu' 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 -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-i686-linux-gnu' cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu && /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-i686-linux-gnu /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po/CMakeFiles/translations_1.dir/DependInfo.cmake --color= make[3]: Entering directory '/build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu' cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu && /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-i686-linux-gnu /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po/CMakeFiles/linguas.dir/DependInfo.cmake --color= make[3]: Entering directory '/build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu' cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu && /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-i686-linux-gnu /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/gconf-migration /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/gconf-migration/CMakeFiles/alarm-clock-applet-gconf-migration.dir/DependInfo.cmake --color= make[3]: Entering directory '/build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu' cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu && /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-i686-linux-gnu /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/src /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/src/CMakeFiles/man-alarm-clock-applet.dir/DependInfo.cmake --color= make[3]: Leaving directory '/build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu' 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-i686-linux-gnu' 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-i686-linux-gnu' 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-i686-linux-gnu' make[3]: Nothing to be done for 'po/CMakeFiles/linguas.dir/build'. make[3]: Leaving directory '/build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu' make[3]: Leaving directory '/build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu' 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-i686-linux-gnu' 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-i686-linux-gnu' [ 0%] Built target linguas [ 3%] Built target man-alarm-clock-applet make[3]: Entering directory '/build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu' 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-i686-linux-gnu' [ 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-i686-linux-gnu' cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu && /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-i686-linux-gnu /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/po/CMakeFiles/translations.dir/DependInfo.cmake --color= make[3]: Entering directory '/build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu' 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-i686-linux-gnu' make[3]: Leaving directory '/build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu' 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-i686-linux-gnu' make[3]: Nothing to be done for 'po/CMakeFiles/translations.dir/build'. make[3]: Leaving directory '/build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu' [ 69%] Built target alarm-clock-applet-gconf-migration [ 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-i686-linux-gnu' cd /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu && /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-i686-linux-gnu /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/src /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/src/CMakeFiles/alarm-clock-applet.dir/DependInfo.cmake --color= make[3]: Leaving directory '/build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu' 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-i686-linux-gnu' 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-i686-linux-gnu' [100%] Built target alarm-clock-applet make[2]: Leaving directory '/build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu' /usr/bin/cmake -E cmake_progress_start /build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu/CMakeFiles 0 make -f CMakeFiles/Makefile2 preinstall make[2]: Entering directory '/build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu' make[2]: Nothing to be done for 'preinstall'. make[2]: Leaving directory '/build/alarm-clock-applet-0.4.1/obj-i686-linux-gnu' 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:15302): GConf-WARNING **: 06:28:53.378: 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.3FLG31”: 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/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-clock.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-timer.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-clock.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-timer.png -- 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-clock.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-timer.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-clock.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-timer.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/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-clock.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-timer.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-clock.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-timer.png -- 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-clock.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-timer.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-i686-linux-gnu' 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/be/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/ja/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/ms/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/gl/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/uk/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/fo/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/et/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/nb/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/es/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/zh_CN/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/la/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/hi/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/pt_BR/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/si/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/nn/LC_MESSAGES/alarm-clock-applet.mo Normalized debian/alarm-clock-applet/usr/share/locale/pl/LC_MESSAGES/alarm-clock-applet.mo Normalized debian/alarm-clock-applet/usr/share/locale/fr/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/cs/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/de/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/tr/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' in '../alarm-clock-applet_0.4.1-3_i386.deb'. dpkg-deb: building package 'alarm-clock-applet-dbgsym' in '../alarm-clock-applet-dbgsym_0.4.1-3_i386.deb'. dpkg-deb: building package 'alarm-clock-applet-gconf-migration-dbgsym' in '../alarm-clock-applet-gconf-migration-dbgsym_0.4.1-3_i386.deb'. dpkg-deb: building package 'alarm-clock-applet-gconf-migration' in '../alarm-clock-applet-gconf-migration_0.4.1-3_i386.deb'. dpkg-genbuildinfo --build=binary -O../alarm-clock-applet_0.4.1-3_i386.buildinfo dpkg-genchanges --build=binary -O../alarm-clock-applet_0.4.1-3_i386.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: user script /srv/workspace/pbuilder/651/tmp/hooks/B01_cleanup starting I: user script /srv/workspace/pbuilder/651/tmp/hooks/B01_cleanup finished 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/651 and its subdirectories I: Current time: Mon Apr 17 06:29:08 +14 2023 I: pbuilder-time-stamp: 1681662548