RUN: /bin/echo ['echo', 'Forking build subprocess...'] Forking build subprocess... RUN: /usr/share/launchpad-buildd/slavebin/unpack-chroot ['unpack-chroot', '1696413-3355640', '/home/buildd/filecache-default/eaac08078a73e63d557a7f0bd285a1dfd6423777'] Uncompressing the tarball... Synching the system clock with the buildd NTP service... 17 Apr 10:18:39 ntpdate[3303]: step time server 10.211.37.1 offset -2912.940773 sec Unpacking chroot for build 1696413-3355640 RUN: /usr/share/launchpad-buildd/slavebin/mount-chroot ['mount-chroot', '1696413-3355640'] Mounting chroot for build 1696413-3355640 RUN: /usr/share/launchpad-buildd/slavebin/apply-ogre-model ['apply-ogre-model', '1696413-3355640', 'main'] Attempting OGRE for main in build-1696413-3355640 No OGRE sources.list found. RUN: /usr/share/launchpad-buildd/slavebin/override-sources-list ['override-sources-list', '1696413-3355640', 'deb http://ppa.launchpad.net/awn-core/ppa/ubuntu jaunty main', 'deb http://ftpmaster.internal/ubuntu jaunty main restricted universe multiverse', 'deb http://ftpmaster.internal/ubuntu jaunty-security main restricted universe multiverse', 'deb http://ftpmaster.internal/ubuntu jaunty-updates main restricted universe multiverse'] Overriding sources.list in build-1696413-3355640 RUN: /usr/share/launchpad-buildd/slavebin/update-debian-chroot ['update-debian-chroot', '1696413-3355640'] Updating debian chroot for build 1696413-3355640 Get:1 http://ftpmaster.internal jaunty Release.gpg [189B] Get:2 http://ftpmaster.internal jaunty-security Release.gpg [189B] Get:3 http://ppa.launchpad.net jaunty Release.gpg [307B] Get:4 http://ftpmaster.internal jaunty-updates Release.gpg [189B] Get:5 http://ftpmaster.internal jaunty Release [74.6kB] Get:6 http://ppa.launchpad.net jaunty Release [74.7kB] Get:7 http://ftpmaster.internal jaunty-security Release [57.9kB] Ign http://ppa.launchpad.net jaunty Release Get:8 http://ftpmaster.internal jaunty-updates Release [57.9kB] Get:9 http://ppa.launchpad.net jaunty/main Packages [7866B] Get:10 http://ftpmaster.internal jaunty/main Packages [1251kB] Get:11 http://ftpmaster.internal jaunty/restricted Packages [8858B] Get:12 http://ftpmaster.internal jaunty/universe Packages [4732kB] Get:13 http://ftpmaster.internal jaunty/multiverse Packages [189kB] Get:14 http://ftpmaster.internal jaunty-security/main Packages [139kB] Get:15 http://ftpmaster.internal jaunty-security/restricted Packages [2614B] Get:16 http://ftpmaster.internal jaunty-security/universe Packages [83.6kB] Get:17 http://ftpmaster.internal jaunty-security/multiverse Packages [1534B] Get:18 http://ftpmaster.internal jaunty-updates/main Packages [226kB] Get:19 http://ftpmaster.internal jaunty-updates/restricted Packages [2614B] Get:20 http://ftpmaster.internal jaunty-updates/universe Packages [113kB] Get:21 http://ftpmaster.internal jaunty-updates/multiverse Packages [8511B] Fetched 7032kB in 2s (2443kB/s) Reading package lists... W: GPG error: http://ppa.launchpad.net jaunty Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 09266047CE9FDCA9 W: You may want to run apt-get update to correct these problems Reading package lists... Building dependency tree... Reading state information... The following packages will be upgraded: dpkg dpkg-dev gzip libc6 libc6-dev libcurl3-gnutls libgnutls26 libkrb53 libmpfr1ldbl libpam-modules libpam-runtime libpam0g libsasl2-2 libsasl2-modules libssl0.9.8 libvolume-id1 linux-libc-dev lsb-base openssl perl perl-base perl-modules tzdata 23 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 25.5MB of archives. After this operation, 61.4kB of additional disk space will be used. WARNING: The following packages cannot be authenticated! dpkg gzip perl-modules linux-libc-dev libc6-dev libc6 perl perl-base libpam-modules libpam-runtime libpam0g libvolume-id1 lsb-base tzdata libgnutls26 libssl0.9.8 libsasl2-2 libsasl2-modules libkrb53 dpkg-dev libcurl3-gnutls libmpfr1ldbl openssl Authentication warning overridden. Get:1 http://ftpmaster.internal jaunty-security/main dpkg 1.14.24ubuntu1.1 [2403kB] Get:2 http://ftpmaster.internal jaunty-security/main gzip 1.3.12-6ubuntu2.9.04.1 [107kB] Get:3 http://ftpmaster.internal jaunty-security/main perl-modules 5.10.0-19ubuntu1.1 [3182kB] Get:4 http://ftpmaster.internal jaunty-security/main linux-libc-dev 2.6.28-18.60 [766kB] Get:5 http://ftpmaster.internal jaunty-updates/main libc6-dev 2.9-4ubuntu6.1 [2612kB] Get:6 http://ftpmaster.internal jaunty-updates/main libc6 2.9-4ubuntu6.1 [4952kB] Get:7 http://ftpmaster.internal jaunty-security/main perl 5.10.0-19ubuntu1.1 [5225kB] Get:8 http://ftpmaster.internal jaunty-security/main perl-base 5.10.0-19ubuntu1.1 [1041kB] Get:9 http://ftpmaster.internal jaunty-security/main libpam-modules 1.0.1-9ubuntu1.1 [320kB] Get:10 http://ftpmaster.internal jaunty-security/main libpam-runtime 1.0.1-9ubuntu1.1 [96.5kB] Get:11 http://ftpmaster.internal jaunty-security/main libpam0g 1.0.1-9ubuntu1.1 [114kB] Get:12 http://ftpmaster.internal jaunty-updates/main libvolume-id1 141-1.2 [103kB] Get:13 http://ftpmaster.internal jaunty-updates/main lsb-base 4.0-0ubuntu0.9.04.1 [24.4kB] Get:14 http://ftpmaster.internal jaunty-updates/main tzdata 2010h~repack-0ubuntu0.9.04 [686kB] Get:15 http://ftpmaster.internal jaunty-security/main libgnutls26 2.4.2-6ubuntu0.1 [413kB] Get:16 http://ftpmaster.internal jaunty-security/main libssl0.9.8 0.9.8g-15ubuntu3.4 [961kB] Get:17 http://ftpmaster.internal jaunty-security/main libsasl2-2 2.1.22.dfsg1-23ubuntu3.1 [117kB] Get:18 http://ftpmaster.internal jaunty-security/main libsasl2-modules 2.1.22.dfsg1-23ubuntu3.1 [167kB] Get:19 http://ftpmaster.internal jaunty-security/main libkrb53 1.6.dfsg.4~beta1-5ubuntu2.3 [512kB] Get:20 http://ftpmaster.internal jaunty-security/main dpkg-dev 1.14.24ubuntu1.1 [644kB] Get:21 http://ftpmaster.internal jaunty-security/main libcurl3-gnutls 7.18.2-8ubuntu4.1 [217kB] Get:22 http://ftpmaster.internal jaunty-security/main libmpfr1ldbl 2.4.0-1ubuntu3.1 [418kB] Get:23 http://ftpmaster.internal jaunty-security/main openssl 0.9.8g-15ubuntu3.4 [402kB] debconf: delaying package configuration, since apt-utils is not installed Fetched 25.5MB in 0s (31.0MB/s) (Reading database ... 10425 files and directories currently installed.) Preparing to replace dpkg 1.14.24ubuntu1 (using .../dpkg_1.14.24ubuntu1.1_amd64.deb) ... Unpacking replacement dpkg ... Setting up dpkg (1.14.24ubuntu1.1) ... (Reading database ... 10425 files and directories currently installed.) Preparing to replace gzip 1.3.12-6ubuntu2 (using .../gzip_1.3.12-6ubuntu2.9.04.1_amd64.deb) ... Unpacking replacement gzip ... Setting up gzip (1.3.12-6ubuntu2.9.04.1) ... (Reading database ... 10425 files and directories currently installed.) Preparing to replace perl-modules 5.10.0-19ubuntu1 (using .../perl-modules_5.10.0-19ubuntu1.1_all.deb) ... Unpacking replacement perl-modules ... Preparing to replace linux-libc-dev 2.6.28-11.42 (using .../linux-libc-dev_2.6.28-18.60_amd64.deb) ... Unpacking replacement linux-libc-dev ... Preparing to replace libc6-dev 2.9-4ubuntu6 (using .../libc6-dev_2.9-4ubuntu6.1_amd64.deb) ... Unpacking replacement libc6-dev ... Preparing to replace libc6 2.9-4ubuntu6 (using .../libc6_2.9-4ubuntu6.1_amd64.deb) ... Unpacking replacement libc6 ... Setting up libc6 (2.9-4ubuntu6.1) ... Processing triggers for libc6 ... ldconfig deferred processing now taking place (Reading database ... 10425 files and directories currently installed.) Preparing to replace perl 5.10.0-19ubuntu1 (using .../perl_5.10.0-19ubuntu1.1_amd64.deb) ... Unpacking replacement perl ... Preparing to replace perl-base 5.10.0-19ubuntu1 (using .../perl-base_5.10.0-19ubuntu1.1_amd64.deb) ... Unpacking replacement perl-base ... Setting up perl-base (5.10.0-19ubuntu1.1) ... (Reading database ... 10425 files and directories currently installed.) Preparing to replace libpam-modules 1.0.1-9ubuntu1 (using .../libpam-modules_1.0.1-9ubuntu1.1_amd64.deb) ... Unpacking replacement libpam-modules ... Setting up libpam-modules (1.0.1-9ubuntu1.1) ... (Reading database ... 10425 files and directories currently installed.) Preparing to replace libpam-runtime 1.0.1-9ubuntu1 (using .../libpam-runtime_1.0.1-9ubuntu1.1_all.deb) ... Unpacking replacement libpam-runtime ... Setting up libpam-runtime (1.0.1-9ubuntu1.1) ... (Reading database ... 10425 files and directories currently installed.) Preparing to replace libpam0g 1.0.1-9ubuntu1 (using .../libpam0g_1.0.1-9ubuntu1.1_amd64.deb) ... Unpacking replacement libpam0g ... Setting up libpam0g (1.0.1-9ubuntu1.1) ... Processing triggers for libc6 ... ldconfig deferred processing now taking place (Reading database ... 10425 files and directories currently installed.) Preparing to replace libvolume-id1 141-1 (using .../libvolume-id1_141-1.2_amd64.deb) ... Unpacking replacement libvolume-id1 ... Setting up libvolume-id1 (141-1.2) ... (Reading database ... 10425 files and directories currently installed.) Preparing to replace lsb-base 3.2-20ubuntu4 (using .../lsb-base_4.0-0ubuntu0.9.04.1_all.deb) ... Unpacking replacement lsb-base ... Setting up lsb-base (4.0-0ubuntu0.9.04.1) ... (Reading database ... 10425 files and directories currently installed.) Preparing to replace tzdata 2009f-0ubuntu1 (using .../tzdata_2010h~repack-0ubuntu0.9.04_all.deb) ... Unpacking replacement tzdata ... Setting up tzdata (2010h~repack-0ubuntu0.9.04) ... Current default timezone: 'Etc/UTC' Local time is now: Sat Apr 17 09:30:54 UTC 2010. Universal Time is now: Sat Apr 17 09:30:54 UTC 2010. Run 'dpkg-reconfigure tzdata' if you wish to change it. (Reading database ... 10440 files and directories currently installed.) Preparing to replace libgnutls26 2.4.2-6 (using .../libgnutls26_2.4.2-6ubuntu0.1_amd64.deb) ... Unpacking replacement libgnutls26 ... Preparing to replace libssl0.9.8 0.9.8g-15ubuntu3 (using .../libssl0.9.8_0.9.8g-15ubuntu3.4_amd64.deb) ... Unpacking replacement libssl0.9.8 ... Preparing to replace libsasl2-2 2.1.22.dfsg1-23ubuntu3 (using .../libsasl2-2_2.1.22.dfsg1-23ubuntu3.1_amd64.deb) ... Unpacking replacement libsasl2-2 ... Preparing to replace libsasl2-modules 2.1.22.dfsg1-23ubuntu3 (using .../libsasl2-modules_2.1.22.dfsg1-23ubuntu3.1_amd64.deb) ... Unpacking replacement libsasl2-modules ... Preparing to replace libkrb53 1.6.dfsg.4~beta1-5ubuntu2 (using .../libkrb53_1.6.dfsg.4~beta1-5ubuntu2.3_amd64.deb) ... Unpacking replacement libkrb53 ... Preparing to replace dpkg-dev 1.14.24ubuntu1 (using .../dpkg-dev_1.14.24ubuntu1.1_all.deb) ... Unpacking replacement dpkg-dev ... Preparing to replace libcurl3-gnutls 7.18.2-8ubuntu4 (using .../libcurl3-gnutls_7.18.2-8ubuntu4.1_amd64.deb) ... Unpacking replacement libcurl3-gnutls ... Preparing to replace libmpfr1ldbl 2.4.0-1ubuntu3 (using .../libmpfr1ldbl_2.4.0-1ubuntu3.1_amd64.deb) ... Unpacking replacement libmpfr1ldbl ... Preparing to replace openssl 0.9.8g-15ubuntu3 (using .../openssl_0.9.8g-15ubuntu3.4_amd64.deb) ... Unpacking replacement openssl ... Setting up linux-libc-dev (2.6.28-18.60) ... Setting up libc6-dev (2.9-4ubuntu6.1) ... Setting up libgnutls26 (2.4.2-6ubuntu0.1) ... Setting up libssl0.9.8 (0.9.8g-15ubuntu3.4) ... Setting up libkrb53 (1.6.dfsg.4~beta1-5ubuntu2.3) ... Setting up libcurl3-gnutls (7.18.2-8ubuntu4.1) ... Setting up libmpfr1ldbl (2.4.0-1ubuntu3.1) ... Setting up openssl (0.9.8g-15ubuntu3.4) ... Setting up perl-modules (5.10.0-19ubuntu1.1) ... Setting up libsasl2-modules (2.1.22.dfsg1-23ubuntu3.1) ... Setting up libsasl2-2 (2.1.22.dfsg1-23ubuntu3.1) ... Setting up perl (5.10.0-19ubuntu1.1) ... Setting up dpkg-dev (1.14.24ubuntu1.1) ... Processing triggers for libc6 ... ldconfig deferred processing now taking place RUN: /usr/share/launchpad-buildd/slavebin/sbuild-package ['sbuild-package', '1696413-3355640', 'jaunty', '--nolog', '--batch', '--archive=ubuntu', '--dist=jaunty', '--purpose=PPA', '--comp=main', 'awn-extras-applets_0.4.0-0ubuntu1~ppa4.dsc'] Initiating build 1696413-3355640 with 2 processor cores. Automatic build of awn-extras-applets_0.4.0-0ubuntu1~ppa4 on actinium by sbuild/amd64 1.170.5 Build started at 20100417-0931 ****************************************************************************** awn-extras-applets_0.4.0-0ubuntu1~ppa4.dsc exists in cwd ** Using build dependencies supplied by package: Build-Depends: debhelper (>= 7), quilt, intltool, libgnome-menu-dev, libgconf2-dev, librsvg2-dev, libgtop2-dev, libdesktop-agnostic-bin, libawn-dev (>= 0.3.9~bzr1890), libwnck-dev, libsexy-dev, libnotify-dev, libvte-dev, python-support (>= 0.7.0), valac (>= 0.7.7), libwebkit-dev, vala-awn (>= 0.3.9~bzr1890) Checking for already installed source dependencies... debhelper: missing quilt: missing intltool: missing libgnome-menu-dev: missing libgconf2-dev: missing librsvg2-dev: missing libgtop2-dev: missing libdesktop-agnostic-bin: missing libawn-dev: missing libwnck-dev: missing libsexy-dev: missing libnotify-dev: missing libvte-dev: missing python-support: missing valac: missing libwebkit-dev: missing vala-awn: missing Checking for source dependency conflicts... /usr/bin/sudo /usr/bin/apt-get --purge $CHROOT_OPTIONS -q -y install debhelper quilt intltool libgnome-menu-dev libgconf2-dev librsvg2-dev libgtop2-dev libdesktop-agnostic-bin libawn-dev libwnck-dev libsexy-dev libnotify-dev libvte-dev python-support valac libwebkit-dev vala-awn Reading package lists... Building dependency tree... Reading state information... The following extra packages will be installed: autoconf automake autotools-dev bsdmainutils defoma diffstat file fontconfig fontconfig-config gconf2 gconf2-common gettext gettext-base groff-base html2text intltool-debian libaspell15 libatk1.0-0 libatk1.0-dev libawn1 libcairo2 libcairo2-dev libcroco3 libcups2 libdatrie0 libdbus-1-3 libdbus-1-dev libdbus-glib-1-2 libdbus-glib-1-dev libdesktop-agnostic-cfg-gconf libdesktop-agnostic-dev libdesktop-agnostic0 libdirectfb-1.0-0 libdirectfb-dev libdirectfb-extra libenchant1c2a libexpat1 libexpat1-dev libfontconfig1 libfontconfig1-dev libfreetype6 libfreetype6-dev libgconf2-4 libglib2.0-0 libglib2.0-dev libgnome-menu2 libgsf-1-114 libgsf-1-common libgtk2.0-0 libgtk2.0-common libgtk2.0-dev libgtop2-7 libgtop2-common libhtml-parser-perl libhtml-tagset-perl libhtml-tree-perl libhunspell-1.2-0 libice-dev libice6 libicu38 libidl-dev libidl0 libjasper1 libjpeg62 libjpeg62-dev libmagic1 libncurses5-dev libncursesw5 libnewt0.52 libnotify1 liborbit2 liborbit2-dev libpango1.0-0 libpango1.0-common libpango1.0-dev libpixman-1-0 libpixman-1-dev libpng12-0 libpng12-dev libpolkit-dbus2 libpolkit2 libpopt-dev libpopt0 libpthread-stubs0 libpthread-stubs0-dev librsvg2-2 libsexy2 libsm-dev libsm6 libsqlite3-0 libstartup-notification0 libstartup-notification0-dev libsysfs-dev libsysfs2 libthai-data libthai0 libtiff4 libts-0.0-0 liburi-perl libvala0 libvte-common libvte9 libwebkit-1.0-1 libwnck-common libwnck22 libwww-perl libx11-6 libx11-data libx11-dev libxau-dev libxau6 libxcb-render-util0 libxcb-render-util0-dev libxcb-render0 libxcb-render0-dev libxcb1 libxcb1-dev libxcomposite-dev libxcomposite1 libxcursor-dev libxcursor1 libxdamage-dev libxdamage1 libxdmcp-dev libxdmcp6 libxext-dev libxext6 libxfixes-dev libxfixes3 libxft-dev libxft2 libxi-dev libxi6 libxinerama-dev libxinerama1 libxml-parser-perl libxml2 libxml2-dev libxml2-utils libxrandr-dev libxrandr2 libxrender-dev libxrender1 libxres-dev libxres1 libxslt1.1 libxt6 m4 man-db mime-support pkg-config po-debconf psmisc python python2.6 shared-mime-info ttf-dejavu ttf-dejavu-core ttf-dejavu-extra ucf vala-desktop-agnostic whiptail x11-common x11proto-composite-dev x11proto-core-dev x11proto-damage-dev x11proto-fixes-dev x11proto-input-dev x11proto-kb-dev x11proto-randr-dev x11proto-render-dev x11proto-resource-dev x11proto-xext-dev x11proto-xinerama-dev xtrans-dev zlib1g-dev Suggested packages: autoconf2.13 autobook autoconf-archive gnu-standards autoconf-doc libtool wamerican wordlist whois vacation dh-make defoma-doc psfontmgr x-ttcidfont-conf dfontmgr libft-perl cvs gettext-doc groff aspell metacity xcompmgr compiz xfwm4 kde-window-manager mutter libcairo2-doc cups-common glade glade-3 libdesktop-agnostic-vfs libdesktop-agnostic-cfg libdesktop-agnostic-fdo libenchant-voikko libglib2.0-doc librsvg2-common gvfs libgtk2.0-doc libdata-dump-perl libjasper-runtime ttf-japanese-gothic ttf-japanese-mincho ttf-thryomanes ttf-baekmuk ttf-arphic-gbsn00lp ttf-arphic-bsmi00lp ttf-arphic-gkai00mp ttf-arphic-bkai00mp libpango1.0-doc imagemagick librsvg2-bin libio-socket-ssl-perl less www-browser libmail-box-perl python-doc python-tk python-profiler python2.6-doc python2.6-profiler procmail graphviz Recommended packages: curl wget lynx aspell-en aspell-dictionary aspell6a-dictionary libatk1.0-data dbus libglib2.0-data hicolor-icon-theme libgtk2.0-bin hunspell-en-us hunspell-dictionary myspell-dictionary libgpm2 libfribidi0 notification-daemon orbit2 libmailtools-perl libhtml-format-perl libcompress-zlib-perl xml-core libmail-sendmail-perl The following NEW packages will be installed: autoconf automake autotools-dev bsdmainutils debhelper defoma diffstat file fontconfig fontconfig-config gconf2 gconf2-common gettext gettext-base groff-base html2text intltool intltool-debian libaspell15 libatk1.0-0 libatk1.0-dev libawn-dev libawn1 libcairo2 libcairo2-dev libcroco3 libcups2 libdatrie0 libdbus-1-3 libdbus-1-dev libdbus-glib-1-2 libdbus-glib-1-dev libdesktop-agnostic-bin libdesktop-agnostic-cfg-gconf libdesktop-agnostic-dev libdesktop-agnostic0 libdirectfb-1.0-0 libdirectfb-dev libdirectfb-extra libenchant1c2a libexpat1 libexpat1-dev libfontconfig1 libfontconfig1-dev libfreetype6 libfreetype6-dev libgconf2-4 libgconf2-dev libglib2.0-0 libglib2.0-dev libgnome-menu-dev libgnome-menu2 libgsf-1-114 libgsf-1-common libgtk2.0-0 libgtk2.0-common libgtk2.0-dev libgtop2-7 libgtop2-common libgtop2-dev libhtml-parser-perl libhtml-tagset-perl libhtml-tree-perl libhunspell-1.2-0 libice-dev libice6 libicu38 libidl-dev libidl0 libjasper1 libjpeg62 libjpeg62-dev libmagic1 libncurses5-dev libncursesw5 libnewt0.52 libnotify-dev libnotify1 liborbit2 liborbit2-dev libpango1.0-0 libpango1.0-common libpango1.0-dev libpixman-1-0 libpixman-1-dev libpng12-0 libpng12-dev libpolkit-dbus2 libpolkit2 libpopt-dev libpopt0 libpthread-stubs0 libpthread-stubs0-dev librsvg2-2 librsvg2-dev libsexy-dev libsexy2 libsm-dev libsm6 libsqlite3-0 libstartup-notification0 libstartup-notification0-dev libsysfs-dev libsysfs2 libthai-data libthai0 libtiff4 libts-0.0-0 liburi-perl libvala0 libvte-common libvte-dev libvte9 libwebkit-1.0-1 libwebkit-dev libwnck-common libwnck-dev libwnck22 libwww-perl libx11-6 libx11-data libx11-dev libxau-dev libxau6 libxcb-render-util0 libxcb-render-util0-dev libxcb-render0 libxcb-render0-dev libxcb1 libxcb1-dev libxcomposite-dev libxcomposite1 libxcursor-dev libxcursor1 libxdamage-dev libxdamage1 libxdmcp-dev libxdmcp6 libxext-dev libxext6 libxfixes-dev libxfixes3 libxft-dev libxft2 libxi-dev libxi6 libxinerama-dev libxinerama1 libxml-parser-perl libxml2 libxml2-dev libxml2-utils libxrandr-dev libxrandr2 libxrender-dev libxrender1 libxres-dev libxres1 libxslt1.1 libxt6 m4 man-db mime-support pkg-config po-debconf psmisc python python-support python2.6 quilt shared-mime-info ttf-dejavu ttf-dejavu-core ttf-dejavu-extra ucf vala-awn vala-desktop-agnostic valac whiptail x11-common x11proto-composite-dev x11proto-core-dev x11proto-damage-dev x11proto-fixes-dev x11proto-input-dev x11proto-kb-dev x11proto-randr-dev x11proto-render-dev x11proto-resource-dev x11proto-xext-dev x11proto-xinerama-dev xtrans-dev zlib1g-dev 0 upgraded, 193 newly installed, 0 to remove and 0 not upgraded. Need to get 57.7MB of archives. After this operation, 225MB of additional disk space will be used. WARNING: The following packages cannot be authenticated! x11-common libice6 x11proto-core-dev libice-dev libsm6 libsm-dev libxau6 libxdmcp6 libxcb1 libx11-data libx11-6 libxau-dev libxdmcp-dev x11proto-input-dev x11proto-kb-dev xtrans-dev libpthread-stubs0 libpthread-stubs0-dev libxcb1-dev libx11-dev libxext6 libxfixes3 libxcomposite1 x11proto-xext-dev x11proto-fixes-dev libxfixes-dev x11proto-composite-dev libxext-dev libxcomposite-dev libxrender1 libxcursor1 x11proto-render-dev libxrender-dev libxcursor-dev libxdamage1 x11proto-damage-dev libxdamage-dev libexpat1 libfreetype6 ucf libnewt0.52 libpopt0 whiptail libmagic1 file defoma ttf-dejavu-core ttf-dejavu-extra ttf-dejavu fontconfig-config libfontconfig1 libxft2 libexpat1-dev zlib1g-dev libfreetype6-dev libglib2.0-0 pkg-config libfontconfig1-dev libxft-dev libxi6 libxi-dev libxinerama1 x11proto-xinerama-dev libxinerama-dev libxrandr2 x11proto-randr-dev libxrandr-dev libxres1 x11proto-resource-dev libxres-dev libxt6 libncursesw5 libsqlite3-0 mime-support python2.6 python bsdmainutils gettext-base groff-base libhtml-tagset-perl liburi-perl libhtml-parser-perl libhtml-tree-perl libwww-perl libxml-parser-perl man-db psmisc python-support m4 autoconf autotools-dev automake html2text libxml2 libcroco3 gettext intltool-debian po-debconf debhelper diffstat fontconfig libdbus-1-3 libdbus-glib-1-2 libidl0 liborbit2 libpolkit2 libpolkit-dbus2 gconf2-common libgconf2-4 gconf2 intltool libaspell15 libatk1.0-0 libglib2.0-dev libatk1.0-dev libsysfs2 libts-0.0-0 libdirectfb-1.0-0 libpixman-1-0 libpng12-0 libxcb-render0 libxcb-render-util0 libcairo2 libgtk2.0-common libcups2 libjpeg62 libjasper1 libpango1.0-common libdatrie0 libthai-data libthai0 libpango1.0-0 libtiff4 shared-mime-info libgtk2.0-0 libdesktop-agnostic0 libawn1 libpng12-dev libdirectfb-extra libjpeg62-dev libsysfs-dev libdirectfb-dev libpixman-1-dev libxcb-render0-dev libxcb-render-util0-dev libcairo2-dev libpango1.0-dev libxml2-utils libgtk2.0-dev libdesktop-agnostic-dev libdbus-1-dev libdbus-glib-1-dev libawn-dev libhunspell-1.2-0 libenchant1c2a libpopt-dev libidl-dev liborbit2-dev libgconf2-dev libgnome-menu2 libgnome-menu-dev libgsf-1-common libgsf-1-114 libgtop2-common libgtop2-7 libgtop2-dev libicu38 libncurses5-dev libnotify1 libnotify-dev librsvg2-2 librsvg2-dev libsexy2 libxml2-dev libsexy-dev libstartup-notification0 libstartup-notification0-dev libvala0 libvte-common libvte9 libvte-dev libxslt1.1 libwebkit-1.0-1 libwnck-common libwnck22 libwnck-dev quilt vala-desktop-agnostic vala-awn valac libdesktop-agnostic-cfg-gconf libdesktop-agnostic-bin libwebkit-dev Authentication warning overridden. Get:1 http://ppa.launchpad.net jaunty/main libdesktop-agnostic0 0.3.9~bzr394-0ubuntu0~ppa9 [97.3kB] Get:2 http://ftpmaster.internal jaunty/main x11-common 1:7.4~5ubuntu18 [366kB] Get:3 http://ftpmaster.internal jaunty/main libice6 2:1.0.4-1 [50.6kB] Get:4 http://ftpmaster.internal jaunty/main x11proto-core-dev 7.0.14-2 [92.4kB] Get:5 http://ftpmaster.internal jaunty/main libice-dev 2:1.0.4-1 [62.7kB] Get:6 http://ppa.launchpad.net jaunty/main libawn1 0.4.0-0ubuntu1~ppa7 [219kB] Get:7 http://ppa.launchpad.net jaunty/main libdesktop-agnostic-dev 0.3.9~bzr394-0ubuntu0~ppa9 [11.6kB] Get:8 http://ftpmaster.internal jaunty/main libsm6 2:1.1.0-1 [23.6kB] Get:9 http://ftpmaster.internal jaunty/main libsm-dev 2:1.1.0-1 [26.7kB] Get:10 http://ftpmaster.internal jaunty/main libxau6 1:1.0.4-1 [13.4kB] Get:11 http://ftpmaster.internal jaunty/main libxdmcp6 1:1.0.2-3 [17.7kB] Get:12 http://ppa.launchpad.net jaunty/main libawn-dev 0.4.0-0ubuntu1~ppa7 [119kB] Get:13 http://ftpmaster.internal jaunty-updates/main libxcb1 1.1.93-0ubuntu3.1 [48.4kB] Get:14 http://ftpmaster.internal jaunty/main libx11-data 2:1.1.99.2-1ubuntu2 [170kB] Get:15 http://ftpmaster.internal jaunty/main libx11-6 2:1.1.99.2-1ubuntu2 [654kB] Get:16 http://ppa.launchpad.net jaunty/main libvala0 0.7.10-1~ppa2 [916kB] Get:17 http://ftpmaster.internal jaunty/main libxau-dev 1:1.0.4-1 [17.0kB] Get:18 http://ftpmaster.internal jaunty/main libxdmcp-dev 1:1.0.2-3 [21.4kB] Get:19 http://ftpmaster.internal jaunty/main x11proto-input-dev 1.5.0-1ubuntu1 [12.0kB] Get:20 http://ppa.launchpad.net jaunty/main vala-desktop-agnostic 0.3.9~bzr394-0ubuntu0~ppa9 [7484B] Get:21 http://ftpmaster.internal jaunty/main x11proto-kb-dev 1.0.3-3ubuntu1 [27.4kB] Get:22 http://ftpmaster.internal jaunty/main xtrans-dev 1.2.3-1 [65.2kB] Get:23 http://ftpmaster.internal jaunty/main libpthread-stubs0 0.1-2 [2812B] Get:24 http://ftpmaster.internal jaunty/main libpthread-stubs0-dev 0.1-2 [3088B] Get:25 http://ftpmaster.internal jaunty-updates/main libxcb1-dev 1.1.93-0ubuntu3.1 [74.9kB] Get:26 http://ppa.launchpad.net jaunty/main vala-awn 0.4.0-0ubuntu1~ppa7 [111kB] Get:27 http://ftpmaster.internal jaunty/main libx11-dev 2:1.1.99.2-1ubuntu2 [1760kB] Get:28 http://ppa.launchpad.net jaunty/main valac 0.7.10-1~ppa2 [640kB] Get:29 http://ppa.launchpad.net jaunty/main libdesktop-agnostic-cfg-gconf 0.3.9~bzr394-0ubuntu0~ppa9 [19.7kB] Get:30 http://ftpmaster.internal jaunty/main libxext6 2:1.0.99.1-0ubuntu3 [32.4kB] Get:31 http://ppa.launchpad.net jaunty/main libdesktop-agnostic-bin 0.3.9~bzr394-0ubuntu0~ppa9 [11.8kB] Get:32 http://ftpmaster.internal jaunty/main libxfixes3 1:4.0.3-2 [10.9kB] Get:33 http://ftpmaster.internal jaunty/main libxcomposite1 1:0.4.0-3 [11.7kB] Get:34 http://ftpmaster.internal jaunty/main x11proto-xext-dev 7.0.4-1 [42.1kB] Get:35 http://ftpmaster.internal jaunty/main x11proto-fixes-dev 1:4.0-3 [13.9kB] Get:36 http://ftpmaster.internal jaunty/main libxfixes-dev 1:4.0.3-2 [13.5kB] Get:37 http://ftpmaster.internal jaunty/main x11proto-composite-dev 1:0.4-2 [12.4kB] Get:38 http://ftpmaster.internal jaunty/main libxext-dev 2:1.0.99.1-0ubuntu3 [84.8kB] Get:39 http://ftpmaster.internal jaunty/main libxcomposite-dev 1:0.4.0-3 [15.1kB] Get:40 http://ftpmaster.internal jaunty/main libxrender1 1:0.9.4-2 [28.1kB] Get:41 http://ftpmaster.internal jaunty/main libxcursor1 1:1.1.9-1 [25.9kB] Get:42 http://ftpmaster.internal jaunty/main x11proto-render-dev 2:0.9.3-2 [7096B] Get:43 http://ftpmaster.internal jaunty/main libxrender-dev 1:0.9.4-2 [31.4kB] Get:44 http://ftpmaster.internal jaunty/main libxcursor-dev 1:1.1.9-1 [33.7kB] Get:45 http://ftpmaster.internal jaunty/main libxdamage1 1:1.1.1-4 [10.6kB] Get:46 http://ftpmaster.internal jaunty/main x11proto-damage-dev 1:1.1.0-2build1 [9292B] Get:47 http://ftpmaster.internal jaunty/main libxdamage-dev 1:1.1.1-4 [10.3kB] Get:48 http://ftpmaster.internal jaunty-security/main libexpat1 2.0.1-4ubuntu0.9.04.1 [137kB] Get:49 http://ftpmaster.internal jaunty-security/main libfreetype6 2.3.9-4ubuntu0.1 [406kB] Get:50 http://ftpmaster.internal jaunty/main ucf 3.0014 [64.2kB] Get:51 http://ftpmaster.internal jaunty-security/main libnewt0.52 0.52.2-11.3ubuntu3.1 [62.9kB] Get:52 http://ftpmaster.internal jaunty/main libpopt0 1.14-4 [29.6kB] Get:53 http://ftpmaster.internal jaunty-security/main whiptail 0.52.2-11.3ubuntu3.1 [36.5kB] Get:54 http://ftpmaster.internal jaunty-updates/main libmagic1 4.26-2ubuntu4 [370kB] Get:55 http://ftpmaster.internal jaunty-updates/main file 4.26-2ubuntu4 [45.2kB] Get:56 http://ftpmaster.internal jaunty/main defoma 0.11.10-0.2ubuntu1 [101kB] Get:57 http://ftpmaster.internal jaunty/main ttf-dejavu-core 2.28-1 [1429kB] Get:58 http://ftpmaster.internal jaunty/main ttf-dejavu-extra 2.28-1 [3092kB] Get:59 http://ftpmaster.internal jaunty/main ttf-dejavu 2.28-1 [3104B] Get:60 http://ftpmaster.internal jaunty/main fontconfig-config 2.6.0-1ubuntu12 [51.6kB] Get:61 http://ftpmaster.internal jaunty/main libfontconfig1 2.6.0-1ubuntu12 [124kB] Get:62 http://ftpmaster.internal jaunty/main libxft2 2.1.13-3ubuntu1 [53.9kB] Get:63 http://ftpmaster.internal jaunty-security/main libexpat1-dev 2.0.1-4ubuntu0.9.04.1 [224kB] Get:64 http://ftpmaster.internal jaunty/main zlib1g-dev 1:1.2.3.3.dfsg-12ubuntu2 [166kB] Get:65 http://ftpmaster.internal jaunty-security/main libfreetype6-dev 2.3.9-4ubuntu0.1 [729kB] Get:66 http://ftpmaster.internal jaunty-security/main libglib2.0-0 2.20.1-0ubuntu2.1 [849kB] Get:67 http://ftpmaster.internal jaunty/main pkg-config 0.22-1 [55.3kB] Get:68 http://ftpmaster.internal jaunty/main libfontconfig1-dev 2.6.0-1ubuntu12 [590kB] Get:69 http://ftpmaster.internal jaunty/main libxft-dev 2.1.13-3ubuntu1 [69.8kB] Get:70 http://ftpmaster.internal jaunty-updates/main libxi6 2:1.2.0-1ubuntu1.1 [29.2kB] Get:71 http://ftpmaster.internal jaunty-updates/main libxi-dev 2:1.2.0-1ubuntu1.1 [85.4kB] Get:72 http://ftpmaster.internal jaunty/main libxinerama1 2:1.0.3-2 [10.6kB] Get:73 http://ftpmaster.internal jaunty/main x11proto-xinerama-dev 1.1.2-5ubuntu1 [5772B] Get:74 http://ftpmaster.internal jaunty/main libxinerama-dev 2:1.0.3-2 [12.1kB] Get:75 http://ftpmaster.internal jaunty/main libxrandr2 2:1.3.0-1build1 [28.2kB] Get:76 http://ftpmaster.internal jaunty/main x11proto-randr-dev 1.3.0-1 [37.7kB] Get:77 http://ftpmaster.internal jaunty/main libxrandr-dev 2:1.3.0-1build1 [35.8kB] Get:78 http://ftpmaster.internal jaunty/main libxres1 2:1.0.3-1 [10.0kB] Get:79 http://ftpmaster.internal jaunty/main x11proto-resource-dev 1.0.2-5ubuntu1 [4374B] Get:80 http://ftpmaster.internal jaunty/main libxres-dev 2:1.0.3-1 [12.0kB] Get:81 http://ftpmaster.internal jaunty/main libxt6 1:1.0.5-3ubuntu1 [190kB] Get:82 http://ftpmaster.internal jaunty/main libncursesw5 5.7+20090207-1ubuntu1 [228kB] Get:83 http://ftpmaster.internal jaunty-updates/main libsqlite3-0 3.6.10-1ubuntu0.2 [288kB] Get:84 http://ftpmaster.internal jaunty/main mime-support 3.44-1 [33.3kB] Get:85 http://ftpmaster.internal jaunty/main python2.6 2.6.2-0ubuntu1 [2527kB] Get:86 http://ftpmaster.internal jaunty/main python 2.6.2-0ubuntu1 [141kB] Get:87 http://ftpmaster.internal jaunty/main bsdmainutils 6.1.10ubuntu3 [181kB] Get:88 http://ftpmaster.internal jaunty/main gettext-base 0.17-6ubuntu2 [80.2kB] Get:89 http://ftpmaster.internal jaunty/main groff-base 1.18.1.1-22build1 [886kB] Get:90 http://ftpmaster.internal jaunty/main libhtml-tagset-perl 3.20-2 [13.5kB] Get:91 http://ftpmaster.internal jaunty/main liburi-perl 1.37+dfsg-1ubuntu1 [88.6kB] Get:92 http://ftpmaster.internal jaunty-security/main libhtml-parser-perl 3.59-1ubuntu1.1 [112kB] Get:93 http://ftpmaster.internal jaunty/main libhtml-tree-perl 3.23-1 [209kB] Get:94 http://ftpmaster.internal jaunty/main libwww-perl 5.820-1 [391kB] Get:95 http://ftpmaster.internal jaunty/main libxml-parser-perl 2.36-1.1build2 [324kB] Get:96 http://ftpmaster.internal jaunty/main man-db 2.5.5-1build1 [1285kB] Get:97 http://ftpmaster.internal jaunty/main psmisc 22.6-1 [59.4kB] Get:98 http://ftpmaster.internal jaunty/main python-support 0.8.7ubuntu4 [28.7kB] Get:99 http://ftpmaster.internal jaunty/main m4 1.4.11-1 [263kB] Get:100 http://ftpmaster.internal jaunty/main autoconf 2.63-2ubuntu1 [508kB] Get:101 http://ftpmaster.internal jaunty/main autotools-dev 20080123.2 [62.6kB] Get:102 http://ftpmaster.internal jaunty-updates/main automake 1:1.10.2-0ubuntu3.09.04 [527kB] Get:103 http://ftpmaster.internal jaunty/main html2text 1.3.2a-5 [95.6kB] Get:104 http://ftpmaster.internal jaunty-security/main libxml2 2.6.32.dfsg-5ubuntu4.2 [865kB] Get:105 http://ftpmaster.internal jaunty/main libcroco3 0.6.1-2 [100kB] Get:106 http://ftpmaster.internal jaunty/main gettext 0.17-6ubuntu2 [1992kB] Get:107 http://ftpmaster.internal jaunty/main intltool-debian 0.35.0+20060710.1 [31.6kB] Get:108 http://ftpmaster.internal jaunty/main po-debconf 1.0.15ubuntu1 [237kB] Get:109 http://ftpmaster.internal jaunty/main debhelper 7.0.17ubuntu4 [549kB] Get:110 http://ftpmaster.internal jaunty/main diffstat 1.46-1 [24.2kB] Get:111 http://ftpmaster.internal jaunty/main fontconfig 2.6.0-1ubuntu12 [138kB] Get:112 http://ftpmaster.internal jaunty-security/main libdbus-1-3 1.2.12-0ubuntu2.1 [139kB] Get:113 http://ftpmaster.internal jaunty/main libdbus-glib-1-2 0.80-3 [75.9kB] Get:114 http://ftpmaster.internal jaunty/main libidl0 0.8.13-0.1 [82.4kB] Get:115 http://ftpmaster.internal jaunty/main liborbit2 1:2.14.17-0.1 [195kB] Get:116 http://ftpmaster.internal jaunty/main libpolkit2 0.9-2ubuntu1 [56.4kB] Get:117 http://ftpmaster.internal jaunty/main libpolkit-dbus2 0.9-2ubuntu1 [24.8kB] Get:118 http://ftpmaster.internal jaunty/main gconf2-common 2.26.0-0ubuntu1 [32.4kB] Get:119 http://ftpmaster.internal jaunty/main libgconf2-4 2.26.0-0ubuntu1 [208kB] Get:120 http://ftpmaster.internal jaunty/main gconf2 2.26.0-0ubuntu1 [60.3kB] Get:121 http://ftpmaster.internal jaunty/main intltool 0.40.6-1 [61.7kB] Get:122 http://ftpmaster.internal jaunty/main libaspell15 0.60.6-1 [672kB] Get:123 http://ftpmaster.internal jaunty/main libatk1.0-0 1.26.0-0ubuntu2 [56.8kB] Get:124 http://ftpmaster.internal jaunty-security/main libglib2.0-dev 2.20.1-0ubuntu2.1 [1046kB] Get:125 http://ftpmaster.internal jaunty/main libatk1.0-dev 1.26.0-0ubuntu2 [85.2kB] Get:126 http://ftpmaster.internal jaunty/main libsysfs2 2.1.0-5 [23.7kB] Get:127 http://ftpmaster.internal jaunty/main libts-0.0-0 1.0-4ubuntu2 [29.6kB] Get:128 http://ftpmaster.internal jaunty/main libdirectfb-1.0-0 1.0.1-11ubuntu1 [716kB] Get:129 http://ftpmaster.internal jaunty/main libpixman-1-0 0.13.2-1 [115kB] Get:130 http://ftpmaster.internal jaunty-security/main libpng12-0 1.2.27-2ubuntu2.1 [168kB] Get:131 http://ftpmaster.internal jaunty-updates/main libxcb-render0 1.1.93-0ubuntu3.1 [11.2kB] Get:132 http://ftpmaster.internal jaunty/main libxcb-render-util0 0.2.1+git1-1 [9784B] Get:133 http://ftpmaster.internal jaunty/main libcairo2 1.8.6-1ubuntu2 [522kB] Get:134 http://ftpmaster.internal jaunty/main libgtk2.0-common 2.16.1-0ubuntu2 [150kB] Get:135 http://ftpmaster.internal jaunty-updates/main libcups2 1.3.9-17ubuntu3.7 [178kB] Get:136 http://ftpmaster.internal jaunty/main libjpeg62 6b-14 [90.2kB] Get:137 http://ftpmaster.internal jaunty/main libjasper1 1.900.1-5.1 [152kB] Get:138 http://ftpmaster.internal jaunty/main libpango1.0-common 1.24.1-0ubuntu1 [66.8kB] Get:139 http://ftpmaster.internal jaunty/main libdatrie0 0.1.3-2 [20.0kB] Get:140 http://ftpmaster.internal jaunty-security/main libthai-data 0.1.9-4ubuntu0.9.04.2 [162kB] Get:141 http://ftpmaster.internal jaunty-security/main libthai0 0.1.9-4ubuntu0.9.04.2 [33.1kB] Get:142 http://ftpmaster.internal jaunty/main libpango1.0-0 1.24.1-0ubuntu1 [324kB] Get:143 http://ftpmaster.internal jaunty-security/main libtiff4 3.8.2-11ubuntu0.9.04.3 [134kB] Get:144 http://ftpmaster.internal jaunty/main shared-mime-info 0.60-1 [362kB] Get:145 http://ftpmaster.internal jaunty/main libgtk2.0-0 2.16.1-0ubuntu2 [2301kB] Get:146 http://ftpmaster.internal jaunty-security/main libpng12-dev 1.2.27-2ubuntu2.1 [256kB] Get:147 http://ftpmaster.internal jaunty/main libdirectfb-extra 1.0.1-11ubuntu1 [32.2kB] Get:148 http://ftpmaster.internal jaunty/main libjpeg62-dev 6b-14 [196kB] Get:149 http://ftpmaster.internal jaunty/main libsysfs-dev 2.1.0-5 [37.3kB] Get:150 http://ftpmaster.internal jaunty/main libdirectfb-dev 1.0.1-11ubuntu1 [876kB] Get:151 http://ftpmaster.internal jaunty/main libpixman-1-dev 0.13.2-1 [142kB] Get:152 http://ftpmaster.internal jaunty-updates/main libxcb-render0-dev 1.1.93-0ubuntu3.1 [31.0kB] Get:153 http://ftpmaster.internal jaunty/main libxcb-render-util0-dev 0.2.1+git1-1 [7762B] Get:154 http://ftpmaster.internal jaunty/main libcairo2-dev 1.8.6-1ubuntu2 [624kB] Get:155 http://ftpmaster.internal jaunty/main libpango1.0-dev 1.24.1-0ubuntu1 [410kB] Get:156 http://ftpmaster.internal jaunty-security/main libxml2-utils 2.6.32.dfsg-5ubuntu4.2 [37.4kB] Get:157 http://ftpmaster.internal jaunty/main libgtk2.0-dev 2.16.1-0ubuntu2 [3202kB] Get:158 http://ftpmaster.internal jaunty-security/main libdbus-1-dev 1.2.12-0ubuntu2.1 [215kB] Get:159 http://ftpmaster.internal jaunty/main libdbus-glib-1-dev 0.80-3 [111kB] Get:160 http://ftpmaster.internal jaunty/main libhunspell-1.2-0 1.2.6-1ubuntu2 [143kB] Get:161 http://ftpmaster.internal jaunty/main libenchant1c2a 1.4.2-3.3ubuntu1 [91.4kB] Get:162 http://ftpmaster.internal jaunty/main libpopt-dev 1.14-4 [46.3kB] Get:163 http://ftpmaster.internal jaunty/main libidl-dev 0.8.13-0.1 [94.1kB] Get:164 http://ftpmaster.internal jaunty/main liborbit2-dev 1:2.14.17-0.1 [400kB] Get:165 http://ftpmaster.internal jaunty/main libgconf2-dev 2.26.0-0ubuntu1 [207kB] Get:166 http://ftpmaster.internal jaunty/main libgnome-menu2 2.26.0-0ubuntu1 [58.5kB] Get:167 http://ftpmaster.internal jaunty/main libgnome-menu-dev 2.26.0-0ubuntu1 [56.5kB] Get:168 http://ftpmaster.internal jaunty/main libgsf-1-common 1.14.11-2ubuntu1 [55.1kB] Get:169 http://ftpmaster.internal jaunty/main libgsf-1-114 1.14.11-2ubuntu1 [156kB] Get:170 http://ftpmaster.internal jaunty/main libgtop2-common 2.26.0-0ubuntu2 [12.0kB] Get:171 http://ftpmaster.internal jaunty/main libgtop2-7 2.26.0-0ubuntu2 [40.4kB] Get:172 http://ftpmaster.internal jaunty/main libgtop2-dev 2.26.0-0ubuntu2 [129kB] Get:173 http://ftpmaster.internal jaunty-security/main libicu38 3.8.1-3ubuntu1.1 [5938kB] Get:174 http://ftpmaster.internal jaunty/main libncurses5-dev 5.7+20090207-1ubuntu1 [1581kB] Get:175 http://ftpmaster.internal jaunty/main libnotify1 0.4.5-0ubuntu1 [21.3kB] Get:176 http://ftpmaster.internal jaunty/main libnotify-dev 0.4.5-0ubuntu1 [17.8kB] Get:177 http://ftpmaster.internal jaunty/main librsvg2-2 2.26.0-0ubuntu1 [110kB] Get:178 http://ftpmaster.internal jaunty/main librsvg2-dev 2.26.0-0ubuntu1 [141kB] Get:179 http://ftpmaster.internal jaunty/main libsexy2 0.1.11-2 [45.0kB] Get:180 http://ftpmaster.internal jaunty-security/main libxml2-dev 2.6.32.dfsg-5ubuntu4.2 [778kB] Get:181 http://ftpmaster.internal jaunty/main libsexy-dev 0.1.11-2 [49.9kB] Get:182 http://ftpmaster.internal jaunty/main libstartup-notification0 0.9-1 [23.3kB] Get:183 http://ftpmaster.internal jaunty/main libstartup-notification0-dev 0.9-1 [26.9kB] Get:184 http://ftpmaster.internal jaunty/main libvte-common 1:0.20.0-0ubuntu2 [34.0kB] Get:185 http://ftpmaster.internal jaunty/main libvte9 1:0.20.0-0ubuntu2 [599kB] Get:186 http://ftpmaster.internal jaunty/main libvte-dev 1:0.20.0-0ubuntu2 [381kB] Get:187 http://ftpmaster.internal jaunty/main libxslt1.1 1.1.24-2ubuntu2 [236kB] Get:188 http://ftpmaster.internal jaunty-security/main libwebkit-1.0-1 1.0.1-4ubuntu0.1 [3503kB] Get:189 http://ftpmaster.internal jaunty/main libwnck-common 2.26.0-0ubuntu1 [18.6kB] Get:190 http://ftpmaster.internal jaunty/main libwnck22 2.26.0-0ubuntu1 [118kB] Get:191 http://ftpmaster.internal jaunty/main libwnck-dev 2.26.0-0ubuntu1 [224kB] Get:192 http://ftpmaster.internal jaunty/main quilt 0.46-6 [305kB] Get:193 http://ftpmaster.internal jaunty-security/main libwebkit-dev 1.0.1-4ubuntu0.1 [34.7kB] debconf: delaying package configuration, since apt-utils is not installed Fetched 57.7MB in 2s (22.2MB/s) Selecting previously deselected package x11-common. (Reading database ... 10440 files and directories currently installed.) Unpacking x11-common (from .../x11-common_1%3a7.4~5ubuntu18_all.deb) ... Selecting previously deselected package libice6. Unpacking libice6 (from .../libice6_2%3a1.0.4-1_amd64.deb) ... Setting up x11-common (1:7.4~5ubuntu18) ... Selecting previously deselected package x11proto-core-dev. (Reading database ... 10522 files and directories currently installed.) Unpacking x11proto-core-dev (from .../x11proto-core-dev_7.0.14-2_all.deb) ... Selecting previously deselected package libice-dev. Unpacking libice-dev (from .../libice-dev_2%3a1.0.4-1_amd64.deb) ... Selecting previously deselected package libsm6. Unpacking libsm6 (from .../libsm6_2%3a1.1.0-1_amd64.deb) ... Selecting previously deselected package libsm-dev. Unpacking libsm-dev (from .../libsm-dev_2%3a1.1.0-1_amd64.deb) ... Selecting previously deselected package libxau6. Unpacking libxau6 (from .../libxau6_1%3a1.0.4-1_amd64.deb) ... Selecting previously deselected package libxdmcp6. Unpacking libxdmcp6 (from .../libxdmcp6_1%3a1.0.2-3_amd64.deb) ... Selecting previously deselected package libxcb1. Unpacking libxcb1 (from .../libxcb1_1.1.93-0ubuntu3.1_amd64.deb) ... Selecting previously deselected package libx11-data. Unpacking libx11-data (from .../libx11-data_2%3a1.1.99.2-1ubuntu2_all.deb) ... Selecting previously deselected package libx11-6. Unpacking libx11-6 (from .../libx11-6_2%3a1.1.99.2-1ubuntu2_amd64.deb) ... Selecting previously deselected package libxau-dev. Unpacking libxau-dev (from .../libxau-dev_1%3a1.0.4-1_amd64.deb) ... Selecting previously deselected package libxdmcp-dev. Unpacking libxdmcp-dev (from .../libxdmcp-dev_1%3a1.0.2-3_amd64.deb) ... Selecting previously deselected package x11proto-input-dev. Unpacking x11proto-input-dev (from .../x11proto-input-dev_1.5.0-1ubuntu1_all.deb) ... Selecting previously deselected package x11proto-kb-dev. Unpacking x11proto-kb-dev (from .../x11proto-kb-dev_1.0.3-3ubuntu1_all.deb) ... Selecting previously deselected package xtrans-dev. Unpacking xtrans-dev (from .../xtrans-dev_1.2.3-1_all.deb) ... Selecting previously deselected package libpthread-stubs0. Unpacking libpthread-stubs0 (from .../libpthread-stubs0_0.1-2_amd64.deb) ... Selecting previously deselected package libpthread-stubs0-dev. Unpacking libpthread-stubs0-dev (from .../libpthread-stubs0-dev_0.1-2_amd64.deb) ... Selecting previously deselected package libxcb1-dev. Unpacking libxcb1-dev (from .../libxcb1-dev_1.1.93-0ubuntu3.1_amd64.deb) ... Selecting previously deselected package libx11-dev. Unpacking libx11-dev (from .../libx11-dev_2%3a1.1.99.2-1ubuntu2_amd64.deb) ... Selecting previously deselected package libxext6. Unpacking libxext6 (from .../libxext6_2%3a1.0.99.1-0ubuntu3_amd64.deb) ... Selecting previously deselected package libxfixes3. Unpacking libxfixes3 (from .../libxfixes3_1%3a4.0.3-2_amd64.deb) ... Selecting previously deselected package libxcomposite1. Unpacking libxcomposite1 (from .../libxcomposite1_1%3a0.4.0-3_amd64.deb) ... Selecting previously deselected package x11proto-xext-dev. Unpacking x11proto-xext-dev (from .../x11proto-xext-dev_7.0.4-1_all.deb) ... Selecting previously deselected package x11proto-fixes-dev. Unpacking x11proto-fixes-dev (from .../x11proto-fixes-dev_1%3a4.0-3_all.deb) ... Selecting previously deselected package libxfixes-dev. Unpacking libxfixes-dev (from .../libxfixes-dev_1%3a4.0.3-2_amd64.deb) ... Selecting previously deselected package x11proto-composite-dev. Unpacking x11proto-composite-dev (from .../x11proto-composite-dev_1%3a0.4-2_all.deb) ... Selecting previously deselected package libxext-dev. Unpacking libxext-dev (from .../libxext-dev_2%3a1.0.99.1-0ubuntu3_amd64.deb) ... Selecting previously deselected package libxcomposite-dev. Unpacking libxcomposite-dev (from .../libxcomposite-dev_1%3a0.4.0-3_amd64.deb) ... Selecting previously deselected package libxrender1. Unpacking libxrender1 (from .../libxrender1_1%3a0.9.4-2_amd64.deb) ... Selecting previously deselected package libxcursor1. Unpacking libxcursor1 (from .../libxcursor1_1%3a1.1.9-1_amd64.deb) ... Selecting previously deselected package x11proto-render-dev. Unpacking x11proto-render-dev (from .../x11proto-render-dev_2%3a0.9.3-2_all.deb) ... Selecting previously deselected package libxrender-dev. Unpacking libxrender-dev (from .../libxrender-dev_1%3a0.9.4-2_amd64.deb) ... Selecting previously deselected package libxcursor-dev. Unpacking libxcursor-dev (from .../libxcursor-dev_1%3a1.1.9-1_amd64.deb) ... Selecting previously deselected package libxdamage1. Unpacking libxdamage1 (from .../libxdamage1_1%3a1.1.1-4_amd64.deb) ... Selecting previously deselected package x11proto-damage-dev. Unpacking x11proto-damage-dev (from .../x11proto-damage-dev_1%3a1.1.0-2build1_all.deb) ... Selecting previously deselected package libxdamage-dev. Unpacking libxdamage-dev (from .../libxdamage-dev_1%3a1.1.1-4_amd64.deb) ... Selecting previously deselected package libexpat1. Unpacking libexpat1 (from .../libexpat1_2.0.1-4ubuntu0.9.04.1_amd64.deb) ... Selecting previously deselected package libfreetype6. Unpacking libfreetype6 (from .../libfreetype6_2.3.9-4ubuntu0.1_amd64.deb) ... Selecting previously deselected package ucf. Unpacking ucf (from .../archives/ucf_3.0014_all.deb) ... Moving old data out of the way Selecting previously deselected package libnewt0.52. Unpacking libnewt0.52 (from .../libnewt0.52_0.52.2-11.3ubuntu3.1_amd64.deb) ... Selecting previously deselected package libpopt0. Unpacking libpopt0 (from .../libpopt0_1.14-4_amd64.deb) ... Selecting previously deselected package whiptail. Unpacking whiptail (from .../whiptail_0.52.2-11.3ubuntu3.1_amd64.deb) ... Selecting previously deselected package libmagic1. Unpacking libmagic1 (from .../libmagic1_4.26-2ubuntu4_amd64.deb) ... Selecting previously deselected package file. Unpacking file (from .../file_4.26-2ubuntu4_amd64.deb) ... Selecting previously deselected package defoma. Unpacking defoma (from .../defoma_0.11.10-0.2ubuntu1_all.deb) ... Selecting previously deselected package ttf-dejavu-core. Unpacking ttf-dejavu-core (from .../ttf-dejavu-core_2.28-1_all.deb) ... Selecting previously deselected package ttf-dejavu-extra. Unpacking ttf-dejavu-extra (from .../ttf-dejavu-extra_2.28-1_all.deb) ... Selecting previously deselected package ttf-dejavu. Unpacking ttf-dejavu (from .../ttf-dejavu_2.28-1_all.deb) ... Selecting previously deselected package fontconfig-config. Unpacking fontconfig-config (from .../fontconfig-config_2.6.0-1ubuntu12_all.deb) ... Selecting previously deselected package libfontconfig1. Unpacking libfontconfig1 (from .../libfontconfig1_2.6.0-1ubuntu12_amd64.deb) ... Selecting previously deselected package libxft2. Unpacking libxft2 (from .../libxft2_2.1.13-3ubuntu1_amd64.deb) ... Selecting previously deselected package libexpat1-dev. Unpacking libexpat1-dev (from .../libexpat1-dev_2.0.1-4ubuntu0.9.04.1_amd64.deb) ... Selecting previously deselected package zlib1g-dev. Unpacking zlib1g-dev (from .../zlib1g-dev_1%3a1.2.3.3.dfsg-12ubuntu2_amd64.deb) ... Selecting previously deselected package libfreetype6-dev. Unpacking libfreetype6-dev (from .../libfreetype6-dev_2.3.9-4ubuntu0.1_amd64.deb) ... Selecting previously deselected package libglib2.0-0. Unpacking libglib2.0-0 (from .../libglib2.0-0_2.20.1-0ubuntu2.1_amd64.deb) ... Selecting previously deselected package pkg-config. Unpacking pkg-config (from .../pkg-config_0.22-1_amd64.deb) ... Selecting previously deselected package libfontconfig1-dev. Unpacking libfontconfig1-dev (from .../libfontconfig1-dev_2.6.0-1ubuntu12_amd64.deb) ... Selecting previously deselected package libxft-dev. Unpacking libxft-dev (from .../libxft-dev_2.1.13-3ubuntu1_amd64.deb) ... Selecting previously deselected package libxi6. Unpacking libxi6 (from .../libxi6_2%3a1.2.0-1ubuntu1.1_amd64.deb) ... Selecting previously deselected package libxi-dev. Unpacking libxi-dev (from .../libxi-dev_2%3a1.2.0-1ubuntu1.1_amd64.deb) ... Selecting previously deselected package libxinerama1. Unpacking libxinerama1 (from .../libxinerama1_2%3a1.0.3-2_amd64.deb) ... Selecting previously deselected package x11proto-xinerama-dev. Unpacking x11proto-xinerama-dev (from .../x11proto-xinerama-dev_1.1.2-5ubuntu1_all.deb) ... Selecting previously deselected package libxinerama-dev. Unpacking libxinerama-dev (from .../libxinerama-dev_2%3a1.0.3-2_amd64.deb) ... Selecting previously deselected package libxrandr2. Unpacking libxrandr2 (from .../libxrandr2_2%3a1.3.0-1build1_amd64.deb) ... Selecting previously deselected package x11proto-randr-dev. Unpacking x11proto-randr-dev (from .../x11proto-randr-dev_1.3.0-1_all.deb) ... Selecting previously deselected package libxrandr-dev. Unpacking libxrandr-dev (from .../libxrandr-dev_2%3a1.3.0-1build1_amd64.deb) ... Selecting previously deselected package libxres1. Unpacking libxres1 (from .../libxres1_2%3a1.0.3-1_amd64.deb) ... Selecting previously deselected package x11proto-resource-dev. Unpacking x11proto-resource-dev (from .../x11proto-resource-dev_1.0.2-5ubuntu1_all.deb) ... Selecting previously deselected package libxres-dev. Unpacking libxres-dev (from .../libxres-dev_2%3a1.0.3-1_amd64.deb) ... Selecting previously deselected package libxt6. Unpacking libxt6 (from .../libxt6_1%3a1.0.5-3ubuntu1_amd64.deb) ... Selecting previously deselected package libncursesw5. Unpacking libncursesw5 (from .../libncursesw5_5.7+20090207-1ubuntu1_amd64.deb) ... Selecting previously deselected package libsqlite3-0. Unpacking libsqlite3-0 (from .../libsqlite3-0_3.6.10-1ubuntu0.2_amd64.deb) ... Selecting previously deselected package mime-support. Unpacking mime-support (from .../mime-support_3.44-1_all.deb) ... Selecting previously deselected package python2.6. Unpacking python2.6 (from .../python2.6_2.6.2-0ubuntu1_amd64.deb) ... Selecting previously deselected package python. Unpacking python (from .../python_2.6.2-0ubuntu1_all.deb) ... Selecting previously deselected package bsdmainutils. Unpacking bsdmainutils (from .../bsdmainutils_6.1.10ubuntu3_amd64.deb) ... Selecting previously deselected package gettext-base. Unpacking gettext-base (from .../gettext-base_0.17-6ubuntu2_amd64.deb) ... Selecting previously deselected package groff-base. Unpacking groff-base (from .../groff-base_1.18.1.1-22build1_amd64.deb) ... Selecting previously deselected package libhtml-tagset-perl. Unpacking libhtml-tagset-perl (from .../libhtml-tagset-perl_3.20-2_all.deb) ... Selecting previously deselected package liburi-perl. Unpacking liburi-perl (from .../liburi-perl_1.37+dfsg-1ubuntu1_all.deb) ... Selecting previously deselected package libhtml-parser-perl. Unpacking libhtml-parser-perl (from .../libhtml-parser-perl_3.59-1ubuntu1.1_amd64.deb) ... Selecting previously deselected package libhtml-tree-perl. Unpacking libhtml-tree-perl (from .../libhtml-tree-perl_3.23-1_all.deb) ... Selecting previously deselected package libwww-perl. Unpacking libwww-perl (from .../libwww-perl_5.820-1_all.deb) ... Selecting previously deselected package libxml-parser-perl. Unpacking libxml-parser-perl (from .../libxml-parser-perl_2.36-1.1build2_amd64.deb) ... Selecting previously deselected package man-db. Unpacking man-db (from .../man-db_2.5.5-1build1_amd64.deb) ... Selecting previously deselected package psmisc. Unpacking psmisc (from .../psmisc_22.6-1_amd64.deb) ... Selecting previously deselected package python-support. Unpacking python-support (from .../python-support_0.8.7ubuntu4_all.deb) ... Selecting previously deselected package m4. Unpacking m4 (from .../archives/m4_1.4.11-1_amd64.deb) ... Selecting previously deselected package autoconf. Unpacking autoconf (from .../autoconf_2.63-2ubuntu1_all.deb) ... Selecting previously deselected package autotools-dev. Unpacking autotools-dev (from .../autotools-dev_20080123.2_all.deb) ... Selecting previously deselected package automake. Unpacking automake (from .../automake_1%3a1.10.2-0ubuntu3.09.04_all.deb) ... Selecting previously deselected package html2text. Unpacking html2text (from .../html2text_1.3.2a-5_amd64.deb) ... Selecting previously deselected package libxml2. Unpacking libxml2 (from .../libxml2_2.6.32.dfsg-5ubuntu4.2_amd64.deb) ... Selecting previously deselected package libcroco3. Unpacking libcroco3 (from .../libcroco3_0.6.1-2_amd64.deb) ... Selecting previously deselected package gettext. Unpacking gettext (from .../gettext_0.17-6ubuntu2_amd64.deb) ... Selecting previously deselected package intltool-debian. Unpacking intltool-debian (from .../intltool-debian_0.35.0+20060710.1_all.deb) ... Selecting previously deselected package po-debconf. Unpacking po-debconf (from .../po-debconf_1.0.15ubuntu1_all.deb) ... Selecting previously deselected package debhelper. Unpacking debhelper (from .../debhelper_7.0.17ubuntu4_all.deb) ... Selecting previously deselected package diffstat. Unpacking diffstat (from .../diffstat_1.46-1_amd64.deb) ... Selecting previously deselected package fontconfig. Unpacking fontconfig (from .../fontconfig_2.6.0-1ubuntu12_amd64.deb) ... Selecting previously deselected package libdbus-1-3. Unpacking libdbus-1-3 (from .../libdbus-1-3_1.2.12-0ubuntu2.1_amd64.deb) ... Selecting previously deselected package libdbus-glib-1-2. Unpacking libdbus-glib-1-2 (from .../libdbus-glib-1-2_0.80-3_amd64.deb) ... Selecting previously deselected package libidl0. Unpacking libidl0 (from .../libidl0_0.8.13-0.1_amd64.deb) ... Selecting previously deselected package liborbit2. Unpacking liborbit2 (from .../liborbit2_1%3a2.14.17-0.1_amd64.deb) ... Selecting previously deselected package libpolkit2. Unpacking libpolkit2 (from .../libpolkit2_0.9-2ubuntu1_amd64.deb) ... Selecting previously deselected package libpolkit-dbus2. Unpacking libpolkit-dbus2 (from .../libpolkit-dbus2_0.9-2ubuntu1_amd64.deb) ... Selecting previously deselected package gconf2-common. Unpacking gconf2-common (from .../gconf2-common_2.26.0-0ubuntu1_all.deb) ... Selecting previously deselected package libgconf2-4. Unpacking libgconf2-4 (from .../libgconf2-4_2.26.0-0ubuntu1_amd64.deb) ... Selecting previously deselected package gconf2. Unpacking gconf2 (from .../gconf2_2.26.0-0ubuntu1_amd64.deb) ... Selecting previously deselected package intltool. Unpacking intltool (from .../intltool_0.40.6-1_all.deb) ... Selecting previously deselected package libaspell15. Unpacking libaspell15 (from .../libaspell15_0.60.6-1_amd64.deb) ... Selecting previously deselected package libatk1.0-0. Unpacking libatk1.0-0 (from .../libatk1.0-0_1.26.0-0ubuntu2_amd64.deb) ... Selecting previously deselected package libglib2.0-dev. Unpacking libglib2.0-dev (from .../libglib2.0-dev_2.20.1-0ubuntu2.1_amd64.deb) ... Selecting previously deselected package libatk1.0-dev. Unpacking libatk1.0-dev (from .../libatk1.0-dev_1.26.0-0ubuntu2_amd64.deb) ... Selecting previously deselected package libsysfs2. Unpacking libsysfs2 (from .../libsysfs2_2.1.0-5_amd64.deb) ... Selecting previously deselected package libts-0.0-0. Unpacking libts-0.0-0 (from .../libts-0.0-0_1.0-4ubuntu2_amd64.deb) ... Selecting previously deselected package libdirectfb-1.0-0. Unpacking libdirectfb-1.0-0 (from .../libdirectfb-1.0-0_1.0.1-11ubuntu1_amd64.deb) ... Selecting previously deselected package libpixman-1-0. Unpacking libpixman-1-0 (from .../libpixman-1-0_0.13.2-1_amd64.deb) ... Selecting previously deselected package libpng12-0. Unpacking libpng12-0 (from .../libpng12-0_1.2.27-2ubuntu2.1_amd64.deb) ... Selecting previously deselected package libxcb-render0. Unpacking libxcb-render0 (from .../libxcb-render0_1.1.93-0ubuntu3.1_amd64.deb) ... Selecting previously deselected package libxcb-render-util0. Unpacking libxcb-render-util0 (from .../libxcb-render-util0_0.2.1+git1-1_amd64.deb) ... Selecting previously deselected package libcairo2. Unpacking libcairo2 (from .../libcairo2_1.8.6-1ubuntu2_amd64.deb) ... Selecting previously deselected package libgtk2.0-common. Unpacking libgtk2.0-common (from .../libgtk2.0-common_2.16.1-0ubuntu2_all.deb) ... Selecting previously deselected package libcups2. Unpacking libcups2 (from .../libcups2_1.3.9-17ubuntu3.7_amd64.deb) ... Selecting previously deselected package libjpeg62. Unpacking libjpeg62 (from .../libjpeg62_6b-14_amd64.deb) ... Selecting previously deselected package libjasper1. Unpacking libjasper1 (from .../libjasper1_1.900.1-5.1_amd64.deb) ... Selecting previously deselected package libpango1.0-common. Unpacking libpango1.0-common (from .../libpango1.0-common_1.24.1-0ubuntu1_all.deb) ... Selecting previously deselected package libdatrie0. Unpacking libdatrie0 (from .../libdatrie0_0.1.3-2_amd64.deb) ... Selecting previously deselected package libthai-data. Unpacking libthai-data (from .../libthai-data_0.1.9-4ubuntu0.9.04.2_all.deb) ... Selecting previously deselected package libthai0. Unpacking libthai0 (from .../libthai0_0.1.9-4ubuntu0.9.04.2_amd64.deb) ... Selecting previously deselected package libpango1.0-0. Unpacking libpango1.0-0 (from .../libpango1.0-0_1.24.1-0ubuntu1_amd64.deb) ... Selecting previously deselected package libtiff4. Unpacking libtiff4 (from .../libtiff4_3.8.2-11ubuntu0.9.04.3_amd64.deb) ... Selecting previously deselected package shared-mime-info. Unpacking shared-mime-info (from .../shared-mime-info_0.60-1_amd64.deb) ... Selecting previously deselected package libgtk2.0-0. Unpacking libgtk2.0-0 (from .../libgtk2.0-0_2.16.1-0ubuntu2_amd64.deb) ... Selecting previously deselected package libdesktop-agnostic0. Unpacking libdesktop-agnostic0 (from .../libdesktop-agnostic0_0.3.9~bzr394-0ubuntu0~ppa9_amd64.deb) ... Selecting previously deselected package libawn1. Unpacking libawn1 (from .../libawn1_0.4.0-0ubuntu1~ppa7_amd64.deb) ... Selecting previously deselected package libpng12-dev. Unpacking libpng12-dev (from .../libpng12-dev_1.2.27-2ubuntu2.1_amd64.deb) ... Selecting previously deselected package libdirectfb-extra. Unpacking libdirectfb-extra (from .../libdirectfb-extra_1.0.1-11ubuntu1_amd64.deb) ... Selecting previously deselected package libjpeg62-dev. Unpacking libjpeg62-dev (from .../libjpeg62-dev_6b-14_amd64.deb) ... Selecting previously deselected package libsysfs-dev. Unpacking libsysfs-dev (from .../libsysfs-dev_2.1.0-5_amd64.deb) ... Selecting previously deselected package libdirectfb-dev. Unpacking libdirectfb-dev (from .../libdirectfb-dev_1.0.1-11ubuntu1_amd64.deb) ... Selecting previously deselected package libpixman-1-dev. Unpacking libpixman-1-dev (from .../libpixman-1-dev_0.13.2-1_amd64.deb) ... Selecting previously deselected package libxcb-render0-dev. Unpacking libxcb-render0-dev (from .../libxcb-render0-dev_1.1.93-0ubuntu3.1_amd64.deb) ... Selecting previously deselected package libxcb-render-util0-dev. Unpacking libxcb-render-util0-dev (from .../libxcb-render-util0-dev_0.2.1+git1-1_amd64.deb) ... Selecting previously deselected package libcairo2-dev. Unpacking libcairo2-dev (from .../libcairo2-dev_1.8.6-1ubuntu2_amd64.deb) ... Selecting previously deselected package libpango1.0-dev. Unpacking libpango1.0-dev (from .../libpango1.0-dev_1.24.1-0ubuntu1_amd64.deb) ... Selecting previously deselected package libxml2-utils. Unpacking libxml2-utils (from .../libxml2-utils_2.6.32.dfsg-5ubuntu4.2_amd64.deb) ... Selecting previously deselected package libgtk2.0-dev. Unpacking libgtk2.0-dev (from .../libgtk2.0-dev_2.16.1-0ubuntu2_amd64.deb) ... Selecting previously deselected package libdesktop-agnostic-dev. Unpacking libdesktop-agnostic-dev (from .../libdesktop-agnostic-dev_0.3.9~bzr394-0ubuntu0~ppa9_amd64.deb) ... Selecting previously deselected package libdbus-1-dev. Unpacking libdbus-1-dev (from .../libdbus-1-dev_1.2.12-0ubuntu2.1_amd64.deb) ... Selecting previously deselected package libdbus-glib-1-dev. Unpacking libdbus-glib-1-dev (from .../libdbus-glib-1-dev_0.80-3_amd64.deb) ... Selecting previously deselected package libawn-dev. Unpacking libawn-dev (from .../libawn-dev_0.4.0-0ubuntu1~ppa7_amd64.deb) ... Selecting previously deselected package libhunspell-1.2-0. Unpacking libhunspell-1.2-0 (from .../libhunspell-1.2-0_1.2.6-1ubuntu2_amd64.deb) ... Selecting previously deselected package libenchant1c2a. Unpacking libenchant1c2a (from .../libenchant1c2a_1.4.2-3.3ubuntu1_amd64.deb) ... Selecting previously deselected package libpopt-dev. Unpacking libpopt-dev (from .../libpopt-dev_1.14-4_amd64.deb) ... Selecting previously deselected package libidl-dev. Unpacking libidl-dev (from .../libidl-dev_0.8.13-0.1_amd64.deb) ... Selecting previously deselected package liborbit2-dev. Unpacking liborbit2-dev (from .../liborbit2-dev_1%3a2.14.17-0.1_amd64.deb) ... Selecting previously deselected package libgconf2-dev. Unpacking libgconf2-dev (from .../libgconf2-dev_2.26.0-0ubuntu1_amd64.deb) ... Selecting previously deselected package libgnome-menu2. Unpacking libgnome-menu2 (from .../libgnome-menu2_2.26.0-0ubuntu1_amd64.deb) ... Selecting previously deselected package libgnome-menu-dev. Unpacking libgnome-menu-dev (from .../libgnome-menu-dev_2.26.0-0ubuntu1_amd64.deb) ... Selecting previously deselected package libgsf-1-common. Unpacking libgsf-1-common (from .../libgsf-1-common_1.14.11-2ubuntu1_all.deb) ... Selecting previously deselected package libgsf-1-114. Unpacking libgsf-1-114 (from .../libgsf-1-114_1.14.11-2ubuntu1_amd64.deb) ... Selecting previously deselected package libgtop2-common. Unpacking libgtop2-common (from .../libgtop2-common_2.26.0-0ubuntu2_all.deb) ... Selecting previously deselected package libgtop2-7. Unpacking libgtop2-7 (from .../libgtop2-7_2.26.0-0ubuntu2_amd64.deb) ... Selecting previously deselected package libgtop2-dev. Unpacking libgtop2-dev (from .../libgtop2-dev_2.26.0-0ubuntu2_amd64.deb) ... Selecting previously deselected package libicu38. Unpacking libicu38 (from .../libicu38_3.8.1-3ubuntu1.1_amd64.deb) ... Selecting previously deselected package libncurses5-dev. Unpacking libncurses5-dev (from .../libncurses5-dev_5.7+20090207-1ubuntu1_amd64.deb) ... Selecting previously deselected package libnotify1. Unpacking libnotify1 (from .../libnotify1_0.4.5-0ubuntu1_amd64.deb) ... Selecting previously deselected package libnotify-dev. Unpacking libnotify-dev (from .../libnotify-dev_0.4.5-0ubuntu1_amd64.deb) ... Selecting previously deselected package librsvg2-2. Unpacking librsvg2-2 (from .../librsvg2-2_2.26.0-0ubuntu1_amd64.deb) ... Selecting previously deselected package librsvg2-dev. Unpacking librsvg2-dev (from .../librsvg2-dev_2.26.0-0ubuntu1_amd64.deb) ... Selecting previously deselected package libsexy2. Unpacking libsexy2 (from .../libsexy2_0.1.11-2_amd64.deb) ... Selecting previously deselected package libxml2-dev. Unpacking libxml2-dev (from .../libxml2-dev_2.6.32.dfsg-5ubuntu4.2_amd64.deb) ... Selecting previously deselected package libsexy-dev. Unpacking libsexy-dev (from .../libsexy-dev_0.1.11-2_amd64.deb) ... Selecting previously deselected package libstartup-notification0. Unpacking libstartup-notification0 (from .../libstartup-notification0_0.9-1_amd64.deb) ... Selecting previously deselected package libstartup-notification0-dev. Unpacking libstartup-notification0-dev (from .../libstartup-notification0-dev_0.9-1_amd64.deb) ... Selecting previously deselected package libvala0. Unpacking libvala0 (from .../libvala0_0.7.10-1~ppa2_amd64.deb) ... Selecting previously deselected package libvte-common. Unpacking libvte-common (from .../libvte-common_1%3a0.20.0-0ubuntu2_all.deb) ... Selecting previously deselected package libvte9. Unpacking libvte9 (from .../libvte9_1%3a0.20.0-0ubuntu2_amd64.deb) ... Selecting previously deselected package libvte-dev. Unpacking libvte-dev (from .../libvte-dev_1%3a0.20.0-0ubuntu2_amd64.deb) ... Selecting previously deselected package libxslt1.1. Unpacking libxslt1.1 (from .../libxslt1.1_1.1.24-2ubuntu2_amd64.deb) ... Selecting previously deselected package libwebkit-1.0-1. Unpacking libwebkit-1.0-1 (from .../libwebkit-1.0-1_1.0.1-4ubuntu0.1_amd64.deb) ... Selecting previously deselected package libwnck-common. Unpacking libwnck-common (from .../libwnck-common_2.26.0-0ubuntu1_all.deb) ... Selecting previously deselected package libwnck22. Unpacking libwnck22 (from .../libwnck22_2.26.0-0ubuntu1_amd64.deb) ... Selecting previously deselected package libwnck-dev. Unpacking libwnck-dev (from .../libwnck-dev_2.26.0-0ubuntu1_amd64.deb) ... Selecting previously deselected package quilt. Unpacking quilt (from .../archives/quilt_0.46-6_all.deb) ... Selecting previously deselected package vala-desktop-agnostic. Unpacking vala-desktop-agnostic (from .../vala-desktop-agnostic_0.3.9~bzr394-0ubuntu0~ppa9_all.deb) ... Selecting previously deselected package vala-awn. Unpacking vala-awn (from .../vala-awn_0.4.0-0ubuntu1~ppa7_all.deb) ... Selecting previously deselected package valac. Unpacking valac (from .../valac_0.7.10-1~ppa2_amd64.deb) ... Selecting previously deselected package libdesktop-agnostic-cfg-gconf. Unpacking libdesktop-agnostic-cfg-gconf (from .../libdesktop-agnostic-cfg-gconf_0.3.9~bzr394-0ubuntu0~ppa9_amd64.deb) ... Selecting previously deselected package libdesktop-agnostic-bin. Unpacking libdesktop-agnostic-bin (from .../libdesktop-agnostic-bin_0.3.9~bzr394-0ubuntu0~ppa9_amd64.deb) ... Selecting previously deselected package libwebkit-dev. Unpacking libwebkit-dev (from .../libwebkit-dev_1.0.1-4ubuntu0.1_all.deb) ... Setting up libice6 (2:1.0.4-1) ... Setting up x11proto-core-dev (7.0.14-2) ... Setting up libice-dev (2:1.0.4-1) ... Setting up libsm6 (2:1.1.0-1) ... Setting up libsm-dev (2:1.1.0-1) ... Setting up libxau6 (1:1.0.4-1) ... Setting up libxdmcp6 (1:1.0.2-3) ... Setting up libxcb1 (1.1.93-0ubuntu3.1) ... Setting up libx11-data (2:1.1.99.2-1ubuntu2) ... Setting up libx11-6 (2:1.1.99.2-1ubuntu2) ... Setting up libxau-dev (1:1.0.4-1) ... Setting up libxdmcp-dev (1:1.0.2-3) ... Setting up x11proto-input-dev (1.5.0-1ubuntu1) ... Setting up x11proto-kb-dev (1.0.3-3ubuntu1) ... Setting up xtrans-dev (1.2.3-1) ... Setting up libpthread-stubs0 (0.1-2) ... Setting up libpthread-stubs0-dev (0.1-2) ... Setting up libxcb1-dev (1.1.93-0ubuntu3.1) ... Setting up libx11-dev (2:1.1.99.2-1ubuntu2) ... Setting up libxext6 (2:1.0.99.1-0ubuntu3) ... Setting up libxfixes3 (1:4.0.3-2) ... Setting up libxcomposite1 (1:0.4.0-3) ... Setting up x11proto-xext-dev (7.0.4-1) ... Setting up x11proto-fixes-dev (1:4.0-3) ... Setting up libxfixes-dev (1:4.0.3-2) ... Setting up x11proto-composite-dev (1:0.4-2) ... Setting up libxext-dev (2:1.0.99.1-0ubuntu3) ... Setting up libxcomposite-dev (1:0.4.0-3) ... Setting up libxrender1 (1:0.9.4-2) ... Setting up libxcursor1 (1:1.1.9-1) ... Setting up x11proto-render-dev (2:0.9.3-2) ... Setting up libxrender-dev (1:0.9.4-2) ... Setting up libxcursor-dev (1:1.1.9-1) ... Setting up libxdamage1 (1:1.1.1-4) ... Setting up x11proto-damage-dev (1:1.1.0-2build1) ... Setting up libxdamage-dev (1:1.1.1-4) ... Setting up libexpat1 (2.0.1-4ubuntu0.9.04.1) ... Setting up libfreetype6 (2.3.9-4ubuntu0.1) ... Setting up ucf (3.0014) ... Setting up libnewt0.52 (0.52.2-11.3ubuntu3.1) ... Setting up libpopt0 (1.14-4) ... Setting up whiptail (0.52.2-11.3ubuntu3.1) ... Setting up libmagic1 (4.26-2ubuntu4) ... Setting up file (4.26-2ubuntu4) ... Setting up defoma (0.11.10-0.2ubuntu1) ... Setting up ttf-dejavu-core (2.28-1) ... Setting up ttf-dejavu-extra (2.28-1) ... Setting up ttf-dejavu (2.28-1) ... Setting up fontconfig-config (2.6.0-1ubuntu12) ... Setting up libfontconfig1 (2.6.0-1ubuntu12) ... Setting up libxft2 (2.1.13-3ubuntu1) ... Setting up libexpat1-dev (2.0.1-4ubuntu0.9.04.1) ... Setting up zlib1g-dev (1:1.2.3.3.dfsg-12ubuntu2) ... Setting up libfreetype6-dev (2.3.9-4ubuntu0.1) ... Setting up libglib2.0-0 (2.20.1-0ubuntu2.1) ... Setting up pkg-config (0.22-1) ... Setting up libfontconfig1-dev (2.6.0-1ubuntu12) ... Setting up libxft-dev (2.1.13-3ubuntu1) ... Setting up libxi6 (2:1.2.0-1ubuntu1.1) ... Setting up libxi-dev (2:1.2.0-1ubuntu1.1) ... Setting up libxinerama1 (2:1.0.3-2) ... Setting up x11proto-xinerama-dev (1.1.2-5ubuntu1) ... Setting up libxinerama-dev (2:1.0.3-2) ... Setting up libxrandr2 (2:1.3.0-1build1) ... Setting up x11proto-randr-dev (1.3.0-1) ... Setting up libxrandr-dev (2:1.3.0-1build1) ... Setting up libxres1 (2:1.0.3-1) ... Setting up x11proto-resource-dev (1.0.2-5ubuntu1) ... Setting up libxres-dev (2:1.0.3-1) ... Setting up libxt6 (1:1.0.5-3ubuntu1) ... Setting up libncursesw5 (5.7+20090207-1ubuntu1) ... Setting up libsqlite3-0 (3.6.10-1ubuntu0.2) ... Setting up mime-support (3.44-1) ... Setting up python2.6 (2.6.2-0ubuntu1) ... Setting up python (2.6.2-0ubuntu1) ... Setting up bsdmainutils (6.1.10ubuntu3) ... Setting up gettext-base (0.17-6ubuntu2) ... Setting up groff-base (1.18.1.1-22build1) ... Setting up libhtml-tagset-perl (3.20-2) ... Setting up liburi-perl (1.37+dfsg-1ubuntu1) ... Setting up libhtml-parser-perl (3.59-1ubuntu1.1) ... Setting up libhtml-tree-perl (3.23-1) ... Setting up libwww-perl (5.820-1) ... Setting up libxml-parser-perl (2.36-1.1build2) ... Setting up man-db (2.5.5-1build1) ... Building database of manual pages ... ... skipping, since this is a buildd Setting up psmisc (22.6-1) ... Setting up python-support (0.8.7ubuntu4) ... Setting up m4 (1.4.11-1) ... Setting up autoconf (2.63-2ubuntu1) ... Setting up autotools-dev (20080123.2) ... Setting up automake (1:1.10.2-0ubuntu3.09.04) ... Setting up html2text (1.3.2a-5) ... Setting up libxml2 (2.6.32.dfsg-5ubuntu4.2) ... Setting up libcroco3 (0.6.1-2) ... Setting up gettext (0.17-6ubuntu2) ... Setting up intltool-debian (0.35.0+20060710.1) ... Setting up po-debconf (1.0.15ubuntu1) ... Setting up debhelper (7.0.17ubuntu4) ... Setting up diffstat (1.46-1) ... Setting up fontconfig (2.6.0-1ubuntu12) ... Updating font configuration of fontconfig... Cleaning up category cid.. Cleaning up category truetype.. Cleaning up category type1.. Updating category type1.. Updating category truetype.. Updating category cid.. Updating fontconfig cache for /usr/share/fonts/truetype/ttf-dejavu Cleaning up old fontconfig caches... done. Regenerating fonts cache... done. Setting up libdbus-1-3 (1.2.12-0ubuntu2.1) ... Setting up libdbus-glib-1-2 (0.80-3) ... Setting up libidl0 (0.8.13-0.1) ... Setting up liborbit2 (1:2.14.17-0.1) ... Setting up libpolkit2 (0.9-2ubuntu1) ... Setting up libpolkit-dbus2 (0.9-2ubuntu1) ... Setting up gconf2-common (2.26.0-0ubuntu1) ... Creating config file /etc/gconf/2/path with new version Setting up libgconf2-4 (2.26.0-0ubuntu1) ... Setting up gconf2 (2.26.0-0ubuntu1) ... Setting up intltool (0.40.6-1) ... Setting up libaspell15 (0.60.6-1) ... Setting up libatk1.0-0 (1.26.0-0ubuntu2) ... Setting up libglib2.0-dev (2.20.1-0ubuntu2.1) ... Setting up libatk1.0-dev (1.26.0-0ubuntu2) ... Setting up libsysfs2 (2.1.0-5) ... Setting up libts-0.0-0 (1.0-4ubuntu2) ... Setting up libdirectfb-1.0-0 (1.0.1-11ubuntu1) ... Setting up libpixman-1-0 (0.13.2-1) ... Setting up libpng12-0 (1.2.27-2ubuntu2.1) ... Setting up libxcb-render0 (1.1.93-0ubuntu3.1) ... Setting up libxcb-render-util0 (0.2.1+git1-1) ... Setting up libcairo2 (1.8.6-1ubuntu2) ... Setting up libgtk2.0-common (2.16.1-0ubuntu2) ... Setting up libcups2 (1.3.9-17ubuntu3.7) ... Setting up libjpeg62 (6b-14) ... Setting up libjasper1 (1.900.1-5.1) ... Setting up libpango1.0-common (1.24.1-0ubuntu1) ... Cleaning up font configuration of pango... Updating font configuration of pango... Cleaning up category xfont.. Updating category xfont.. *** You don't have any defomized font packages. *** So we are trying to force to generate pangox.aliases... Setting up libdatrie0 (0.1.3-2) ... Setting up libthai-data (0.1.9-4ubuntu0.9.04.2) ... Setting up libthai0 (0.1.9-4ubuntu0.9.04.2) ... Setting up libpango1.0-0 (1.24.1-0ubuntu1) ... Setting up libtiff4 (3.8.2-11ubuntu0.9.04.3) ... Setting up shared-mime-info (0.60-1) ... Setting up libgtk2.0-0 (2.16.1-0ubuntu2) ... Setting up libdesktop-agnostic0 (0.3.9~bzr394-0ubuntu0~ppa9) ... Setting up libawn1 (0.4.0-0ubuntu1~ppa7) ... Setting up libpng12-dev (1.2.27-2ubuntu2.1) ... Setting up libdirectfb-extra (1.0.1-11ubuntu1) ... Setting up libjpeg62-dev (6b-14) ... Setting up libsysfs-dev (2.1.0-5) ... Setting up libdirectfb-dev (1.0.1-11ubuntu1) ... Setting up libpixman-1-dev (0.13.2-1) ... Setting up libxcb-render0-dev (1.1.93-0ubuntu3.1) ... Setting up libxcb-render-util0-dev (0.2.1+git1-1) ... Setting up libcairo2-dev (1.8.6-1ubuntu2) ... Setting up libpango1.0-dev (1.24.1-0ubuntu1) ... Setting up libxml2-utils (2.6.32.dfsg-5ubuntu4.2) ... Setting up libgtk2.0-dev (2.16.1-0ubuntu2) ... Setting up libdesktop-agnostic-dev (0.3.9~bzr394-0ubuntu0~ppa9) ... Setting up libdbus-1-dev (1.2.12-0ubuntu2.1) ... Setting up libdbus-glib-1-dev (0.80-3) ... Setting up libawn-dev (0.4.0-0ubuntu1~ppa7) ... Setting up libhunspell-1.2-0 (1.2.6-1ubuntu2) ... Setting up libenchant1c2a (1.4.2-3.3ubuntu1) ... Setting up libpopt-dev (1.14-4) ... Setting up libidl-dev (0.8.13-0.1) ... Setting up liborbit2-dev (1:2.14.17-0.1) ... Setting up libgconf2-dev (2.26.0-0ubuntu1) ... Setting up libgnome-menu2 (2.26.0-0ubuntu1) ... Setting up libgnome-menu-dev (2.26.0-0ubuntu1) ... Setting up libgsf-1-common (1.14.11-2ubuntu1) ... Setting up libgsf-1-114 (1.14.11-2ubuntu1) ... Setting up libgtop2-common (2.26.0-0ubuntu2) ... Setting up libgtop2-7 (2.26.0-0ubuntu2) ... Setting up libgtop2-dev (2.26.0-0ubuntu2) ... Setting up libicu38 (3.8.1-3ubuntu1.1) ... Setting up libncurses5-dev (5.7+20090207-1ubuntu1) ... Setting up libnotify1 (0.4.5-0ubuntu1) ... Setting up libnotify-dev (0.4.5-0ubuntu1) ... Setting up librsvg2-2 (2.26.0-0ubuntu1) ... Setting up librsvg2-dev (2.26.0-0ubuntu1) ... Setting up libsexy2 (0.1.11-2) ... Setting up libxml2-dev (2.6.32.dfsg-5ubuntu4.2) ... Setting up libsexy-dev (0.1.11-2) ... Setting up libstartup-notification0 (0.9-1) ... Setting up libstartup-notification0-dev (0.9-1) ... Setting up libvala0 (0.7.10-1~ppa2) ... Setting up libvte-common (1:0.20.0-0ubuntu2) ... Setting up libvte9 (1:0.20.0-0ubuntu2) ... Setting up libvte-dev (1:0.20.0-0ubuntu2) ... Setting up libxslt1.1 (1.1.24-2ubuntu2) ... Setting up libwebkit-1.0-1 (1.0.1-4ubuntu0.1) ... Setting up libwnck-common (2.26.0-0ubuntu1) ... Setting up libwnck22 (2.26.0-0ubuntu1) ... Setting up libwnck-dev (2.26.0-0ubuntu1) ... Setting up quilt (0.46-6) ... Setting up vala-desktop-agnostic (0.3.9~bzr394-0ubuntu0~ppa9) ... Setting up vala-awn (0.4.0-0ubuntu1~ppa7) ... Setting up valac (0.7.10-1~ppa2) ... Setting up libdesktop-agnostic-cfg-gconf (0.3.9~bzr394-0ubuntu0~ppa9) ... Setting up libdesktop-agnostic-bin (0.3.9~bzr394-0ubuntu0~ppa9) ... Setting up libwebkit-dev (1.0.1-4ubuntu0.1) ... Processing triggers for libc6 ... ldconfig deferred processing now taking place Checking correctness of source dependencies... Toolchain package versions: libc6-dev_2.9-4ubuntu6.1 make_3.81-5 dpkg-dev_1.14.24ubuntu1.1 g++-4.3_4.3.3-5ubuntu4 gcc-4.3_4.3.3-5ubuntu4 binutils_2.19.1-0ubuntu3 libstdc++6_4.3.3-5ubuntu4 libstdc++6-4.3-dev_4.3.3-5ubuntu4 ------------------------------------------------------------------------------ gpg: new configuration file `/home/buildd/.gnupg/gpg.conf' created gpg: WARNING: options in `/home/buildd/.gnupg/gpg.conf' are not yet active during this run gpg: Signature made Fri Apr 16 19:06:53 2010 UTC using DSA key ID 491E5389 gpg: Can't check signature: public key not found dpkg-source: extracting awn-extras-applets in awn-extras-applets-0.4.0 dpkg-source: info: unpacking awn-extras-applets_0.4.0.orig.tar.gz dpkg-source: info: applying awn-extras-applets_0.4.0-0ubuntu1~ppa4.diff.gz dpkg-buildpackage: set CFLAGS to default value: -g -O2 dpkg-buildpackage: set CPPFLAGS to default value: dpkg-buildpackage: set LDFLAGS to default value: -Wl,-Bsymbolic-functions dpkg-buildpackage: set FFLAGS to default value: -g -O2 dpkg-buildpackage: set CXXFLAGS to default value: -g -O2 dpkg-buildpackage: source package awn-extras-applets dpkg-buildpackage: source version 0.4.0-0ubuntu1~ppa4 dpkg-buildpackage: host architecture amd64 /usr/bin/fakeroot debian/rules clean QUILT_PATCHES=debian/patches quilt --quiltrc /dev/null pop -a -R || test $? = 2 No patch removed rm -rf .pc debian/stamp-patched dh clean dh_testdir dh_auto_clean dh_clean debian/rules build # quilt exits with 2 as return when there was nothing to do. # That's not an error here (but it's useful to break loops in crude scripts) QUILT_PATCHES=debian/patches quilt --quiltrc /dev/null push -a || test $? = 2 Applying patch 02-shinyswitcher-default-layout.patch patching file applets/maintained/shiny-switcher/awn-applet-shinyswitcher.schema-ini.in Now at patch 02-shinyswitcher-default-layout.patch touch debian/stamp-patched dh_testdir dh_auto_configure -- --prefix=/usr --disable-pymod-checks --with-gconf-schema-file-dir=/etc/gconf/schemas --with-webkit checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... no checking for mawk... mawk checking whether make sets $(MAKE)... yes checking how to create a ustar tar archive... gnutar checking whether to enable maintainer-specific portions of Makefiles... no checking for style of include used by make... GNU checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking dependency style of gcc... none checking for library containing strerror... none required checking for gcc... (cached) gcc checking whether we are using the GNU C compiler... (cached) yes checking whether gcc accepts -g... (cached) yes checking for gcc option to accept ISO C89... (cached) none needed checking dependency style of gcc... (cached) none checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking build system type... x86_64-pc-linux-gnu checking host system type... x86_64-pc-linux-gnu checking for a sed that does not truncate output... /bin/sed checking for fgrep... /bin/grep -F checking for ld used by gcc... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B checking the name lister (/usr/bin/nm -B) interface... BSD nm checking whether ln -s works... yes checking the maximum length of command line arguments... 3458764513820540925 checking whether the shell understands some XSI constructs... yes checking whether the shell understands "+="... yes checking for /usr/bin/ld option to reload object files... -r checking for objdump... objdump checking how to recognize dependent libraries... pass_all checking for ar... ar checking for strip... strip checking for ranlib... ranlib checking command to parse /usr/bin/nm -B output from gcc object... ok checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for dlfcn.h... yes checking for objdir... .libs checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC -DPIC checking if gcc PIC flag -fPIC -DPIC works... yes checking if gcc static flag -static works... yes checking if gcc supports -c -o file.o... yes checking if gcc supports -c -o file.o... (cached) yes checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes checking for bash... /bin/bash checking if dolt supports this host... yes, replacing libtool checking whether NLS is requested... yes checking for intltool >= 0.34... 0.40.6 found checking for intltool-update... /usr/bin/intltool-update checking for intltool-merge... /usr/bin/intltool-merge checking for intltool-extract... /usr/bin/intltool-extract checking for xgettext... /usr/bin/xgettext checking for msgmerge... /usr/bin/msgmerge checking for msgfmt... /usr/bin/msgfmt checking for gmsgfmt... /usr/bin/msgfmt checking for perl... /usr/bin/perl checking for perl >= 5.8.1... 5.10.0 checking for XML::Parser... ok checking locale.h usability... yes checking locale.h presence... yes checking for locale.h... yes checking for LC_MESSAGES... yes checking libintl.h usability... yes checking libintl.h presence... yes checking for libintl.h... yes checking for ngettext in libc... yes checking for dgettext in libc... yes checking for bind_textdomain_codeset... yes checking for msgfmt... (cached) /usr/bin/msgfmt checking for dcgettext... yes checking if msgfmt accepts -c... yes checking for gmsgfmt... (cached) /usr/bin/msgfmt checking for xgettext... (cached) /usr/bin/xgettext checking for catalogs to be installed... af ar ast bg ca cs csb da de en_CA en_GB en_US@piglatin es eu fi fr he hu id it ja ko lt ms nb nl nn pl pt pt_BR ru sk sv sv_SE th tr uk vi zh_CN zh_TW checking for a Python interpreter with version >= 2.5... python checking for python... /usr/bin/python checking for python version... 2.6 checking for python platform... linux2 checking for python script directory... ${prefix}/lib/python2.6/dist-packages checking for python extension module directory... ${exec_prefix}/lib/python2.6/dist-packages checking for round in -lm... yes checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for AWN... yes checking for GTOP... yes checking for LIBWNCK... yes checking for LIBX11... yes checking for COMPOSITE... yes checking for XRENDER... yes checking for LIBNOTIFY... yes checking for LIBSEXY... yes checking for VTE... yes checking for GCONF... yes checking for GNOME_MENU... yes checking for GSTREAMER... no checking for AWN_SYSTEM_MONITOR... yes checking for NOTIFICATION_DAEMON... yes checking for CAIRO_MENU_GNOME... yes checking for SHINY_SWITCHER... yes checking for WEBAPPLET... yes checking for valac... /usr/bin/valac checking valac is at least version 0.7.7... yes checking dbus version... 1.2.12 Using config source xml:merged:/etc/gconf/gconf.xml.defaults for schema installation Using /etc/gconf/schemas as install directory for schema files checking for gconftool-2... /usr/bin/gconftool-2 checking for sed... /bin/sed configure: creating ./config.status config.status: creating Makefile config.status: creating applets/Makefile config.status: creating applets/maintained/animal-farm/Makefile config.status: creating applets/maintained/awnterm/Makefile config.status: creating applets/maintained/awnterm/awnterm.desktop.in config.status: creating applets/maintained/bandwidth-monitor/Makefile config.status: creating applets/maintained/battery/Makefile config.status: creating applets/maintained/cairo-clock/Makefile config.status: creating applets/maintained/cairo-menu/Makefile config.status: creating applets/maintained/cairo-menu/cairo-menu.desktop.in config.status: creating applets/maintained/calendar/Makefile config.status: creating applets/maintained/comics/Makefile config.status: creating applets/maintained/cpufreq/Makefile config.status: creating applets/maintained/dialect/Makefile config.status: creating applets/maintained/digital-clock/Makefile config.status: creating applets/maintained/digital-clock/digital-clock.desktop.in config.status: creating applets/maintained/feeds/Makefile config.status: creating applets/maintained/file-browser-launcher/Makefile config.status: creating applets/maintained/garbage/Makefile config.status: creating applets/maintained/garbage/garbage.desktop.in config.status: creating applets/maintained/hardware-sensors/Makefile config.status: creating applets/maintained/mail/Makefile config.status: creating applets/maintained/media-control/Makefile config.status: creating applets/maintained/media-icons/Makefile config.status: creating applets/maintained/media-player/Makefile config.status: creating applets/maintained/mount/Makefile config.status: creating applets/maintained/notification-area/Makefile config.status: creating applets/maintained/notification-area/notification-area.desktop.in config.status: creating applets/maintained/notification-daemon/Makefile config.status: creating applets/maintained/notification-daemon/notification-daemon.desktop.in config.status: creating applets/maintained/places/Makefile config.status: creating applets/maintained/places/places.desktop.in config.status: creating applets/maintained/python-test/Makefile config.status: creating applets/maintained/quit/Makefile config.status: creating applets/maintained/shiny-switcher/Makefile config.status: creating applets/maintained/shiny-switcher/shinyswitcher.desktop.in config.status: creating applets/maintained/showdesktop/Makefile config.status: creating applets/maintained/showdesktop/showdesktop.desktop.in config.status: creating applets/maintained/slickswitcher/Makefile config.status: creating applets/maintained/sysmon/Makefile config.status: creating applets/maintained/sysmon/sysmon.desktop.in config.status: creating applets/maintained/thinkhdaps/Makefile config.status: creating applets/maintained/to-do/Makefile config.status: creating applets/maintained/tomboy-applet/Makefile config.status: creating applets/maintained/vala-test/Makefile config.status: creating applets/maintained/vala-test/vala-test.desktop.in config.status: creating applets/maintained/volume-control/Makefile config.status: creating applets/maintained/weather/Makefile config.status: creating applets/maintained/webapplet/Makefile config.status: creating applets/maintained/webapplet/webapplet.desktop.in config.status: creating applets/maintained/wobblyzini/Makefile config.status: creating applets/maintained/wobblyzini/wobblyzini.desktop.in config.status: creating applets/maintained/yama/Makefile config.status: creating applets/unmaintained/awnsystemmonitor/Makefile config.status: creating applets/unmaintained/awnsystemmonitor/awnsystemmonitor.desktop.in config.status: creating applets/unmaintained/dropper/Makefile config.status: creating applets/unmaintained/main-menu/Makefile config.status: creating applets/unmaintained/main-menu/main-menu.desktop.in config.status: creating applets/unmaintained/MiMenu/Makefile config.status: creating applets/unmaintained/pandora/Makefile config.status: creating applets/unmaintained/stacks/Makefile config.status: creating po/Makefile.in config.status: creating shared/python/__init__.py config.status: creating shared/python/Makefile config.status: creating shared/vala/Makefile config.status: creating shave/shave config.status: creating shave/shave-libtool config.status: creating config.h config.status: executing depfiles commands config.status: executing libtool commands config.status: executing default-1 commands config.status: executing po/stamp-it commands Avant Window Navigator Extras 0.4.0 =================================== prefix: /usr Vala Support: yes WebKit Support: webkit-1.0 XULRunner Support: no dh_auto_build make[1]: Entering directory `/build/buildd/awn-extras-applets-0.4.0' make[2]: Entering directory `/build/buildd/awn-extras-applets-0.4.0' Making all in applets make[3]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets' Making all in maintained/animal-farm make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/animal-farm' Generating and caching the translation database Merging translations into animal-farm.desktop. make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/animal-farm' Making all in maintained/awnterm make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/awnterm' make[5]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/awnterm' CC awn-terminal.o In file included from awn-terminal.c:41: /usr/include/glib-2.0/glib/gi18n.h:28:1: warning: "_" redefined In file included from awn-terminal.c:37: /usr/include/glib-2.0/glib/gi18n-lib.h:32:1: warning: this is the location of the previous definition In file included from awn-terminal.c:41: /usr/include/glib-2.0/glib/gi18n.h:29:1: warning: "Q_" redefined In file included from awn-terminal.c:37: /usr/include/glib-2.0/glib/gi18n-lib.h:33:1: warning: this is the location of the previous definition In file included from awn-terminal.c:41: /usr/include/glib-2.0/glib/gi18n.h:31:1: warning: "C_" redefined In file included from awn-terminal.c:37: /usr/include/glib-2.0/glib/gi18n-lib.h:35:1: warning: this is the location of the previous definition CC eggaccelerators.o CC keybinder.o LINK awnterm.la Found cached translation database Merging translations into awnterm.desktop. Found cached translation database Merging translations into awn-applet-awnterm.schema-ini. GEN awn-applet-awnterm.schemas make[5]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/awnterm' make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/awnterm' Making all in maintained/bandwidth-monitor make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/bandwidth-monitor' Found cached translation database Merging translations into bandwidth-monitor.desktop. Found cached translation database Merging translations into awn-applet-bandwidth-monitor.schema-ini. GEN awn-applet-bandwidth-monitor.schemas make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/bandwidth-monitor' Making all in maintained/battery make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/battery' Found cached translation database Merging translations into battery.desktop. Found cached translation database Merging translations into awn-applet-battery.schema-ini. GEN awn-applet-battery.schemas make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/battery' Making all in maintained/cairo-clock make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/cairo-clock' Found cached translation database Merging translations into cairo-clock.desktop. Found cached translation database Merging translations into awn-applet-cairo-clock.schema-ini. GEN awn-applet-cairo-clock.schemas make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/cairo-clock' Making all in maintained/comics make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/comics' Found cached translation database Merging translations into comics.desktop. Found cached translation database Merging translations into awn-applet-comics.schema-ini. GEN awn-applet-comics.schemas make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/comics' Making all in maintained/cpufreq make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/cpufreq' Found cached translation database Merging translations into cpufreq.desktop. Found cached translation database Merging translations into awn-applet-cpufreq.schema-ini. GEN awn-applet-cpufreq.schemas make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/cpufreq' Making all in maintained/dialect make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/dialect' Found cached translation database Merging translations into dialect.desktop. Found cached translation database Merging translations into awn-applet-dialect.schema-ini. GEN awn-applet-dialect.schemas make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/dialect' Making all in maintained/digital-clock make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/digital-clock' make[5]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/digital-clock' CC digital-clock.o CC dg-prefs.o LINK digital-clock.la Found cached translation database Merging translations into digital-clock.desktop. Found cached translation database Merging translations into awn-applet-digital-clock.schema-ini. GEN awn-applet-digital-clock.schemas make[5]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/digital-clock' make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/digital-clock' Making all in maintained/feeds make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/feeds' Found cached translation database Merging translations into feeds.desktop. Found cached translation database Merging translations into awn-applet-feeds.schema-ini. GEN awn-applet-feeds.schemas make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/feeds' Making all in maintained/file-browser-launcher make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/file-browser-launcher' Found cached translation database Merging translations into file-browser-launcher.desktop. Found cached translation database Merging translations into awn-applet-file-browser-launcher.schema-ini. GEN awn-applet-file-browser-launcher.schemas make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/file-browser-launcher' Making all in maintained/hardware-sensors make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/hardware-sensors' Found cached translation database Merging translations into hardware-sensors.desktop. Found cached translation database Merging translations into awn-applet-hardware-sensors.schema-ini. GEN awn-applet-hardware-sensors.schemas make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/hardware-sensors' Making all in maintained/mail make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/mail' Found cached translation database Merging translations into mail.desktop. Found cached translation database Merging translations into awn-applet-mail.schema-ini. GEN awn-applet-mail.schemas make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/mail' Making all in maintained/media-control make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/media-control' Found cached translation database Merging translations into media-control.desktop. Found cached translation database Merging translations into awn-applet-media-control.schema-ini. GEN awn-applet-media-control.schemas make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/media-control' Making all in maintained/media-icons make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/media-icons' Found cached translation database Merging translations into media-icons.desktop. Found cached translation database Merging translations into media-icon-next.desktop. Found cached translation database Merging translations into media-icon-previous.desktop. make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/media-icons' Making all in maintained/media-player make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/media-player' Found cached translation database Merging translations into media-player.desktop. Found cached translation database Merging translations into awn-applet-media-player.schema-ini. GEN awn-applet-media-player.schemas make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/media-player' Making all in maintained/mount make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/mount' Found cached translation database Merging translations into mount.desktop. Found cached translation database Merging translations into awn-applet-mount.schema-ini. GEN awn-applet-mount.schemas make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/mount' Making all in maintained/places make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/places' CC applet.o applet.c: In function '_button_clicked_event': applet.c:1207: warning: passing argument 1 of 'awn_utils_show_menu_images' from incompatible pointer type LINK places.la Found cached translation database Merging translations into places.desktop. Found cached translation database Merging translations into awn-applet-places.schema-ini. GEN awn-applet-places.schemas make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/places' Making all in maintained/quit make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/quit' Found cached translation database Merging translations into quit.desktop. Found cached translation database Merging translations into quit-lock-screen.desktop. Found cached translation database Merging translations into quit-log-out.desktop. Found cached translation database Merging translations into quit-shut-down.desktop. Found cached translation database Merging translations into awn-applet-quit.schema-ini. GEN awn-applet-quit.schemas make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/quit' Making all in maintained/slickswitcher make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/slickswitcher' Found cached translation database Merging translations into slickswitcher.desktop. Found cached translation database Merging translations into awn-applet-slickswitcher.schema-ini. GEN awn-applet-slickswitcher.schemas make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/slickswitcher' Making all in maintained/shiny-switcher make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/shiny-switcher' CC applet.o CC shinyswitcherapplet.o LINK shinyswitcher.la Found cached translation database Merging translations into shinyswitcher.desktop. Found cached translation database Merging translations into awn-applet-shinyswitcher.schema-ini. GEN awn-applet-shinyswitcher.schemas make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/shiny-switcher' Making all in maintained/sysmon make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/sysmon' CC applet.o CC areagraph.o CC bargraph.o CC circlegraph.o CC cpu-dialog.o CC cpuicon.o CC graph.o CC loadicon.o CC piegraph.o CC sysmon.o CC sysmonicon.o CC util.o LINK sysmon.la Found cached translation database Merging translations into sysmon.desktop. Found cached translation database Merging translations into awn-applet-sysmon.schema-ini. GEN awn-applet-sysmon.schemas make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/sysmon' Making all in maintained/thinkhdaps make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/thinkhdaps' Found cached translation database Merging translations into thinkhdaps.desktop. make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/thinkhdaps' Making all in maintained/to-do make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/to-do' Found cached translation database Merging translations into to-do.desktop. Found cached translation database Merging translations into awn-applet-to-do.schema-ini. GEN awn-applet-to-do.schemas make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/to-do' Making all in maintained/tomboy-applet make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/tomboy-applet' Found cached translation database Merging translations into tomboy-applet.desktop. make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/tomboy-applet' Making all in maintained/volume-control make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/volume-control' Found cached translation database Merging translations into volume-control.desktop. Found cached translation database Merging translations into awn-applet-volume-control.schema-ini. GEN awn-applet-volume-control.schemas make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/volume-control' Making all in maintained/weather make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/weather' Found cached translation database Merging translations into weather.desktop. Found cached translation database Merging translations into awn-applet-weather.schema-ini. GEN awn-applet-weather.schemas make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/weather' Making all in maintained/garbage make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/garbage' make[5]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/garbage' CC applet.o CC prefs.o LINK garbage.la Found cached translation database Merging translations into garbage.desktop. Found cached translation database Merging translations into awn-applet-garbage.schema-ini. GEN awn-applet-garbage.schemas make[5]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/garbage' make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/garbage' Making all in maintained/notification-area make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/notification-area' make[5]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/notification-area' CC notification-area.o CC na-prefs.o CC eggtraymanager.o CC egg-tray-child.o CC eggmarshalers.o LINK notification-area.la Found cached translation database Merging translations into notification-area.desktop. Found cached translation database Merging translations into awn-applet-notification-area.schema-ini. GEN awn-applet-notification-area.schemas make[5]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/notification-area' make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/notification-area' Making all in maintained/showdesktop make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/showdesktop' make[5]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/showdesktop' CC applet.o LINK showdesktop.la Found cached translation database Merging translations into showdesktop.desktop. make[5]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/showdesktop' make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/showdesktop' Making all in unmaintained/awnsystemmonitor make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/unmaintained/awnsystemmonitor' CC applet.o CC awnsystemmonitor.o CC awntop.o CC awntop_cairo_component.o CC cairo-utils.o CC cpumetergconf.o CC cpu_component.o CC dashboard.o CC dashboard_util.o CC date_time_component.o CC loadavg_component.o CC sysmem_component.o CC uptime_component.o LINK awnsystemmonitor.la Found cached translation database Merging translations into awnsystemmonitor.desktop. Found cached translation database Merging translations into awnsystemmonitor.schemas. make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/unmaintained/awnsystemmonitor' Making all in maintained/calendar make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/calendar' Found cached translation database Merging translations into calendar.desktop. Found cached translation database Merging translations into awn-applet-calendar.schema-ini. GEN awn-applet-calendar.schemas make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/calendar' Making all in maintained/notification-daemon make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/notification-daemon' make[5]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/notification-daemon' CC daemon.o CC engines.o CC sound.o CC stack.o LINK notification-daemon.la Found cached translation database Merging translations into notification-daemon.desktop. Found cached translation database Merging translations into awn-applet-notification-daemon.schema-ini. GEN awn-applet-notification-daemon.schemas make[5]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/notification-daemon' make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/notification-daemon' Making all in maintained/cairo-menu make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/cairo-menu' CC applet.o CC cairo-menu-applet.o CC cairo-menu.o CC cairo-menu-item.o CC cairo-main-icon.o CC cairo-aux-icon.o CC misc.o misc.c: In function '_get_recent_menu': misc.c:332: warning: passing argument 3 of 'gtk_recent_info_get_application_info' from incompatible pointer type LINK cairo-menu.la CC gnome-menu-builder.o LINK gnome-menu-builder.la Found cached translation database Merging translations into cairo-menu.desktop. Found cached translation database Merging translations into awn-applet-cairo-menu.schema-ini. GEN awn-applet-cairo-menu.schemas make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/cairo-menu' Making all in unmaintained/main-menu make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/unmaintained/main-menu' CC applet.o LINK main-menu.la Found cached translation database Merging translations into main-menu.desktop. make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/unmaintained/main-menu' Making all in unmaintained/MiMenu make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/unmaintained/MiMenu' Found cached translation database Merging translations into mimenu.desktop. make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/unmaintained/MiMenu' Making all in unmaintained/pandora make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/unmaintained/pandora' Found cached translation database Merging translations into pandora.desktop. Found cached translation database Merging translations into awn-applet-pandora.schema-ini. GEN awn-applet-pandora.schemas make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/unmaintained/pandora' Making all in unmaintained/stacks make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/unmaintained/stacks' Found cached translation database Merging translations into stacks.desktop. Found cached translation database Merging translations into awn-applet-stacks.schema-ini. GEN awn-applet-stacks.schemas make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/unmaintained/stacks' Making all in maintained/yama make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/yama' Found cached translation database Merging translations into yama.desktop. make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/yama' Making all in maintained/webapplet make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/webapplet' CC applet.o CC engine_html.o CC configuration.o CC engine_webkit.o LINK webapplet.la Found cached translation database Merging translations into webapplet.desktop. GEN awn-applet-webapplet.schemas make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/webapplet' make[3]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets' Making all in shared/python Making all in shared/vala Making all in po make[3]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/po' make[3]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/po' make[2]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0' make[1]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0' touch build-stamp /usr/bin/fakeroot debian/rules binary-arch dh_testroot dh install --before build dh_auto_build make[1]: Entering directory `/build/buildd/awn-extras-applets-0.4.0' make[2]: Entering directory `/build/buildd/awn-extras-applets-0.4.0' Making all in applets make[3]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets' Making all in maintained/animal-farm Making all in maintained/awnterm make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/awnterm' make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/awnterm' Making all in maintained/bandwidth-monitor Making all in maintained/battery Making all in maintained/cairo-clock Making all in maintained/comics Making all in maintained/cpufreq Making all in maintained/dialect Making all in maintained/digital-clock make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/digital-clock' make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/digital-clock' Making all in maintained/feeds Making all in maintained/file-browser-launcher Making all in maintained/hardware-sensors Making all in maintained/mail Making all in maintained/media-control Making all in maintained/media-icons Making all in maintained/media-player Making all in maintained/mount Making all in maintained/places Making all in maintained/quit Making all in maintained/slickswitcher Making all in maintained/shiny-switcher Making all in maintained/sysmon Making all in maintained/thinkhdaps Making all in maintained/to-do Making all in maintained/tomboy-applet Making all in maintained/volume-control Making all in maintained/weather Making all in maintained/garbage make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/garbage' make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/garbage' Making all in maintained/notification-area make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/notification-area' make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/notification-area' Making all in maintained/showdesktop make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/showdesktop' make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/showdesktop' Making all in unmaintained/awnsystemmonitor Making all in maintained/calendar Making all in maintained/notification-daemon make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/notification-daemon' make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/notification-daemon' Making all in maintained/cairo-menu Making all in unmaintained/main-menu Making all in unmaintained/MiMenu Making all in unmaintained/pandora Making all in unmaintained/stacks Making all in maintained/yama Making all in maintained/webapplet make[3]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets' Making all in shared/python Making all in shared/vala Making all in po make[2]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0' make[1]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0' dh install --after test dh_prep dh_installdirs dh_auto_install make[1]: Entering directory `/build/buildd/awn-extras-applets-0.4.0' Making install in applets make[2]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets' Making install in maintained/animal-farm make[3]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/animal-farm' make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/animal-farm' /usr/bin/install -c -m 644 animal-farm.desktop '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c -m 644 icons/lemmling-cartoon-bear.svg icons/lemmling-cartoon-beaver.svg icons/lemmling-cartoon-cat.svg icons/lemmling-cartoon-cow.svg icons/lemmling-cartoon-dog.svg icons/lemmling-cartoon-elephant.svg icons/lemmling-cartoon-elk.svg icons/lemmling-cartoon-giraffe.svg icons/lemmling-cartoon-gnu.svg icons/lemmling-cartoon-goat.svg icons/lemmling-cartoon-kangaroo.svg icons/lemmling-cartoon-owl.svg icons/lemmling-cartoon-penguin.svg icons/lemmling-cartoon-sheep.svg icons/lemmling-cartoon-squirrel.svg icons/lemmling-cartoon-turtle.svg icons/AUTHORS '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/animal-farm/icons' /usr/bin/install -c -m 644 COPYING '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/animal-farm' /usr/bin/install -c animal-farm.py '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/animal-farm' make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/animal-farm' make[3]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/animal-farm' Making install in maintained/awnterm make[3]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/awnterm' make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/awnterm' make[5]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/awnterm' /bin/bash /build/buildd/awn-extras-applets-0.4.0/shave/shave-libtool '../../../doltlibtool' --mode=install /usr/bin/install -c awnterm.la '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/lib/awn/applets/awnterm' libtool: install: warning: remember to run `libtool --finish /usr/lib/awn/applets/awnterm' (gconftool-2:14119): GConf-WARNING **: None of the resolved addresses are writable; saving configuration settings will not be possible Attached schema `/schemas/apps/awn-applet-awnterm/opacity' to key `/apps/awn-applet-awnterm/opacity' WARNING: failed to install schema `/schemas/apps/awn-applet-awnterm/opacity', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-awnterm/opacity', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-awnterm/hide_on_unfocus' to key `/apps/awn-applet-awnterm/hide_on_unfocus' WARNING: failed to install schema `/schemas/apps/awn-applet-awnterm/hide_on_unfocus', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-awnterm/hide_on_unfocus', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-awnterm/global_hotkey' to key `/apps/awn-applet-awnterm/global_hotkey' WARNING: failed to install schema `/schemas/apps/awn-applet-awnterm/global_hotkey', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-awnterm/global_hotkey', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-awnterm/bg_img' to key `/apps/awn-applet-awnterm/bg_img' WARNING: failed to install schema `/schemas/apps/awn-applet-awnterm/bg_img', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-awnterm/bg_img', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-awnterm/main_terminal' to key `/apps/awn-applet-awnterm/main_terminal' WARNING: failed to install schema `/schemas/apps/awn-applet-awnterm/main_terminal', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-awnterm/main_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf /usr/bin/install -c -m 644 awnterm.desktop '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c -m 644 awn-applet-awnterm.schemas '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/etc/gconf/schemas' /usr/bin/install -c -m 644 awn-applet-awnterm.schema-ini '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/schemas' make[5]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/awnterm' make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/awnterm' make[3]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/awnterm' Making install in maintained/bandwidth-monitor make[3]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/bandwidth-monitor' make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/bandwidth-monitor' (gconftool-2:14160): GConf-WARNING **: None of the resolved addresses are writable; saving configuration settings will not be possible Attached schema `/schemas/apps/awn-applet-bandwidth-monitor/unit' to key `/apps/awn-applet-bandwidth-monitor/unit' WARNING: failed to install schema `/schemas/apps/awn-applet-bandwidth-monitor/unit', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-bandwidth-monitor/unit', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-bandwidth-monitor/interface' to key `/apps/awn-applet-bandwidth-monitor/interface' WARNING: failed to install schema `/schemas/apps/awn-applet-bandwidth-monitor/interface', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-bandwidth-monitor/interface', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-bandwidth-monitor/draw_threshold' to key `/apps/awn-applet-bandwidth-monitor/draw_threshold' WARNING: failed to install schema `/schemas/apps/awn-applet-bandwidth-monitor/draw_threshold', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-bandwidth-monitor/draw_threshold', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-bandwidth-monitor/device_display_parameters' to key `/apps/awn-applet-bandwidth-monitor/device_display_parameters' WARNING: failed to install schema `/schemas/apps/awn-applet-bandwidth-monitor/device_display_parameters', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-bandwidth-monitor/device_display_parameters', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-bandwidth-monitor/background' to key `/apps/awn-applet-bandwidth-monitor/background' WARNING: failed to install schema `/schemas/apps/awn-applet-bandwidth-monitor/background', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-bandwidth-monitor/background', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-bandwidth-monitor/background_color' to key `/apps/awn-applet-bandwidth-monitor/background_color' WARNING: failed to install schema `/schemas/apps/awn-applet-bandwidth-monitor/background_color', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-bandwidth-monitor/background_color', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-bandwidth-monitor/border' to key `/apps/awn-applet-bandwidth-monitor/border' WARNING: failed to install schema `/schemas/apps/awn-applet-bandwidth-monitor/border', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-bandwidth-monitor/border', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-bandwidth-monitor/border_color' to key `/apps/awn-applet-bandwidth-monitor/border_color' WARNING: failed to install schema `/schemas/apps/awn-applet-bandwidth-monitor/border_color', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-bandwidth-monitor/border_color', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-bandwidth-monitor/label_control' to key `/apps/awn-applet-bandwidth-monitor/label_control' WARNING: failed to install schema `/schemas/apps/awn-applet-bandwidth-monitor/label_control', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-bandwidth-monitor/label_control', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-bandwidth-monitor/graph_zero' to key `/apps/awn-applet-bandwidth-monitor/graph_zero' WARNING: failed to install schema `/schemas/apps/awn-applet-bandwidth-monitor/graph_zero', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-bandwidth-monitor/graph_zero', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf /usr/bin/install -c -m 644 bandwidth-monitor.desktop '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c -m 644 CHANGELOG bwmprefs.py bandwidth-monitor.ui '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/bandwidth-monitor' /usr/bin/install -c awn-bwm.py '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/bandwidth-monitor' /usr/bin/install -c -m 644 images/icon.png '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/bandwidth-monitor/images' /usr/bin/install -c -m 644 awn-applet-bandwidth-monitor.schemas '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/etc/gconf/schemas' /usr/bin/install -c -m 644 awn-applet-bandwidth-monitor.schema-ini '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/schemas' make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/bandwidth-monitor' make[3]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/bandwidth-monitor' Making install in maintained/battery make[3]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/battery' make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/battery' (gconftool-2:14229): GConf-WARNING **: None of the resolved addresses are writable; saving configuration settings will not be possible Attached schema `/schemas/apps/awn-applet-battery/battery-udi' to key `/apps/awn-applet-battery/battery-udi' WARNING: failed to install schema `/schemas/apps/awn-applet-battery/battery-udi', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-battery/battery-udi', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-battery/level-notify-high' to key `/apps/awn-applet-battery/level-notify-high' WARNING: failed to install schema `/schemas/apps/awn-applet-battery/level-notify-high', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-battery/level-notify-high', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-battery/level-warn-low' to key `/apps/awn-applet-battery/level-warn-low' WARNING: failed to install schema `/schemas/apps/awn-applet-battery/level-warn-low', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-battery/level-warn-low', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-battery/low-level-unit' to key `/apps/awn-applet-battery/low-level-unit' WARNING: failed to install schema `/schemas/apps/awn-applet-battery/low-level-unit', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-battery/low-level-unit', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-battery/notify-high-level' to key `/apps/awn-applet-battery/notify-high-level' WARNING: failed to install schema `/schemas/apps/awn-applet-battery/notify-high-level', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-battery/notify-high-level', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-battery/theme' to key `/apps/awn-applet-battery/theme' WARNING: failed to install schema `/schemas/apps/awn-applet-battery/theme', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-battery/theme', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-battery/warn-low-level' to key `/apps/awn-applet-battery/warn-low-level' WARNING: failed to install schema `/schemas/apps/awn-applet-battery/warn-low-level', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-battery/warn-low-level', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf /usr/bin/install -c -m 644 battery.desktop '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c -m 644 battery.ui messagehandler.py '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/battery' /usr/bin/install -c battery.py '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/battery' /usr/bin/install -c -m 644 themes/gpm/battery-charged.svg themes/gpm/battery-charging-000.svg themes/gpm/battery-charging-020.svg themes/gpm/battery-charging-040.svg themes/gpm/battery-charging-060.svg themes/gpm/battery-charging-080.svg themes/gpm/battery-charging-100.svg themes/gpm/battery-discharging-000.svg themes/gpm/battery-discharging-020.svg themes/gpm/battery-discharging-040.svg themes/gpm/battery-discharging-060.svg themes/gpm/battery-discharging-080.svg themes/gpm/battery-discharging-100.svg themes/gpm/battery-missing.svg '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/battery/themes/gpm' /usr/bin/install -c -m 644 themes/oxygen/battery-charged.svg themes/oxygen/battery-charging-000.svg themes/oxygen/battery-charging-020.svg themes/oxygen/battery-charging-040.svg themes/oxygen/battery-charging-060.svg themes/oxygen/battery-charging-080.svg themes/oxygen/battery-charging-100.svg themes/oxygen/battery-discharging-000.svg themes/oxygen/battery-discharging-020.svg themes/oxygen/battery-discharging-040.svg themes/oxygen/battery-discharging-060.svg themes/oxygen/battery-discharging-080.svg themes/oxygen/battery-discharging-100.svg themes/oxygen/battery-missing.svg themes/oxygen/COPYING themes/oxygen/LGPL '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/battery/themes/oxygen' /usr/bin/install -c -m 644 awn-applet-battery.schemas '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/etc/gconf/schemas' /usr/bin/install -c -m 644 awn-applet-battery.schema-ini '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/schemas' make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/battery' make[3]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/battery' Making install in maintained/cairo-clock make[3]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/cairo-clock' make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/cairo-clock' (gconftool-2:14307): GConf-WARNING **: None of the resolved addresses are writable; saving configuration settings will not be possible Attached schema `/schemas/apps/awn-applet-cairo-clock/time-24-format' to key `/apps/awn-applet-cairo-clock/time-24-format' WARNING: failed to install schema `/schemas/apps/awn-applet-cairo-clock/time-24-format', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-cairo-clock/time-24-format', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-cairo-clock/time-date' to key `/apps/awn-applet-cairo-clock/time-date' WARNING: failed to install schema `/schemas/apps/awn-applet-cairo-clock/time-date', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-cairo-clock/time-date', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-cairo-clock/time-seconds' to key `/apps/awn-applet-cairo-clock/time-seconds' WARNING: failed to install schema `/schemas/apps/awn-applet-cairo-clock/time-seconds', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-cairo-clock/time-seconds', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-cairo-clock/show-seconds-hand' to key `/apps/awn-applet-cairo-clock/show-seconds-hand' WARNING: failed to install schema `/schemas/apps/awn-applet-cairo-clock/show-seconds-hand', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-cairo-clock/show-seconds-hand', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-cairo-clock/theme' to key `/apps/awn-applet-cairo-clock/theme' WARNING: failed to install schema `/schemas/apps/awn-applet-cairo-clock/theme', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-cairo-clock/theme', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-cairo-clock/custom-time-format' to key `/apps/awn-applet-cairo-clock/custom-time-format' WARNING: failed to install schema `/schemas/apps/awn-applet-cairo-clock/custom-time-format', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-cairo-clock/custom-time-format', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-cairo-clock/cities-timezones' to key `/apps/awn-applet-cairo-clock/cities-timezones' WARNING: failed to install schema `/schemas/apps/awn-applet-cairo-clock/cities-timezones', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-cairo-clock/cities-timezones', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-cairo-clock/show-weather' to key `/apps/awn-applet-cairo-clock/show-weather' WARNING: failed to install schema `/schemas/apps/awn-applet-cairo-clock/show-weather', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-cairo-clock/show-weather', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-cairo-clock/temperature-unit' to key `/apps/awn-applet-cairo-clock/temperature-unit' WARNING: failed to install schema `/schemas/apps/awn-applet-cairo-clock/temperature-unit', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-cairo-clock/temperature-unit', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-cairo-clock/wind-speed-unit' to key `/apps/awn-applet-cairo-clock/wind-speed-unit' WARNING: failed to install schema `/schemas/apps/awn-applet-cairo-clock/wind-speed-unit', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-cairo-clock/wind-speed-unit', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf /usr/bin/install -c -m 644 cairo-clock.desktop '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c -m 644 cairo-clock-logo.svg cairo-clock.ui analogclock.py locations.py sun.py weather.py '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/cairo-clock' /usr/bin/install -c cairo-clock.py '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/cairo-clock' /usr/bin/install -c -m 644 themes/gnome/clock-drop-shadow.svg themes/gnome/clock-face-shadow.svg themes/gnome/clock-face.svg themes/gnome/clock-frame.svg themes/gnome/clock-glass.svg themes/gnome/clock-hour-hand-shadow.svg themes/gnome/clock-hour-hand.svg themes/gnome/clock-marks.svg themes/gnome/clock-minute-hand-shadow.svg themes/gnome/clock-minute-hand.svg themes/gnome/clock-second-hand-shadow.svg themes/gnome/clock-second-hand.svg '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/cairo-clock/themes/gnome' /usr/bin/install -c -m 644 themes/onox/clock-drop-shadow.svg themes/onox/clock-face-shadow.svg themes/onox/clock-face.svg themes/onox/clock-frame.svg themes/onox/clock-glass.svg themes/onox/clock-hour-hand-shadow.svg themes/onox/clock-hour-hand.svg themes/onox/clock-marks.svg themes/onox/clock-minute-hand-shadow.svg themes/onox/clock-minute-hand.svg themes/onox/clock-second-hand-shadow.svg themes/onox/clock-second-hand.svg '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/cairo-clock/themes/onox' /usr/bin/install -c -m 644 themes/tango/clock-drop-shadow.svg themes/tango/clock-face-shadow.svg themes/tango/clock-face.svg themes/tango/clock-frame.svg themes/tango/clock-glass.svg themes/tango/clock-hour-hand-shadow.svg themes/tango/clock-hour-hand.svg themes/tango/clock-marks.svg themes/tango/clock-minute-hand-shadow.svg themes/tango/clock-minute-hand.svg themes/tango/clock-second-hand-shadow.svg themes/tango/clock-second-hand.svg '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/cairo-clock/themes/tango' /usr/bin/install -c -m 644 awn-applet-cairo-clock.schemas '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/etc/gconf/schemas' /usr/bin/install -c -m 644 awn-applet-cairo-clock.schema-ini '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/schemas' make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/cairo-clock' make[3]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/cairo-clock' Making install in maintained/comics make[3]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/comics' make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/comics' (gconftool-2:14394): GConf-WARNING **: None of the resolved addresses are writable; saving configuration settings will not be possible Attached schema `/schemas/apps/awn-applet-comics/user_agent' to key `/apps/awn-applet-comics/user_agent' WARNING: failed to install schema `/schemas/apps/awn-applet-comics/user_agent', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-comics/user_agent', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf /usr/bin/install -c -m 644 comics.desktop '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c -m 644 comics.sh comics_add.py comics_manage.py comics_view.py COPYING downloader.py main.py shared.py widgets.py '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/comics' /usr/bin/install -c comics.py '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/comics' /usr/bin/install -c -m 644 icons/comics-icon.svg icons/default.svg icons/error.svg '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/comics/icons' /usr/bin/install -c -m 644 feed/__init__.py feed/basic.py feed/rss.py feed/settings.py '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/comics/feed' /usr/bin/install -c -m 644 feeds/buttersafe.feed feeds/dilbert.feed feeds/peanuts.feed feeds/pearls.feed feeds/wizardofid.feed feeds/xkcd.feed '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/comics/feeds' /usr/bin/install -c -m 644 ui/comics.svg ui/logo.svg ui/manage.svg ui/add.ui ui/manage.ui ui/view.ui '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/comics/ui' /usr/bin/install -c -m 644 awn-applet-comics.schemas '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/etc/gconf/schemas' /usr/bin/install -c -m 644 awn-applet-comics.schema-ini '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/schemas' make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/comics' make[3]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/comics' Making install in maintained/cpufreq make[3]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/cpufreq' make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/cpufreq' (gconftool-2:14490): GConf-WARNING **: None of the resolved addresses are writable; saving configuration settings will not be possible Attached schema `/schemas/apps/awn-applet-cpufreq/cpu_number' to key `/apps/awn-applet-cpufreq/cpu_number' WARNING: failed to install schema `/schemas/apps/awn-applet-cpufreq/cpu_number', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-cpufreq/cpu_number', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf /usr/bin/install -c -m 644 cpufreq.desktop '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c -m 644 cpufreq.svg cpufreq.ui '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/cpufreq' /usr/bin/install -c cpufreq.py '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/cpufreq' /usr/bin/install -c -m 644 images/cpufreq-0.svg images/cpufreq-1.svg images/cpufreq-2.svg images/cpufreq-3.svg images/cpufreq-4.svg images/cpufreq-5.svg images/cpufreq-6.svg '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/cpufreq/images' /usr/bin/install -c -m 644 themes/moonbeam/index.theme '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/cpufreq/themes/moonbeam' /usr/bin/install -c -m 644 themes/moonbeam/scalable/cpufreq-0.svg themes/moonbeam/scalable/cpufreq-1.svg themes/moonbeam/scalable/cpufreq-2.svg themes/moonbeam/scalable/cpufreq-3.svg themes/moonbeam/scalable/cpufreq-4.svg themes/moonbeam/scalable/cpufreq-5.svg themes/moonbeam/scalable/cpufreq-6.svg themes/moonbeam/scalable/cpufreq-7.svg themes/moonbeam/scalable/cpufreq-8.svg themes/moonbeam/scalable/cpufreq-9.svg themes/moonbeam/scalable/cpufreq-10.svg themes/moonbeam/scalable/cpufreq-11.svg themes/moonbeam/scalable/cpufreq-12.svg themes/moonbeam/scalable/cpufreq-13.svg '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/cpufreq/themes/moonbeam/scalable' /usr/bin/install -c -m 644 awn-applet-cpufreq.schemas '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/etc/gconf/schemas' /usr/bin/install -c -m 644 awn-applet-cpufreq.schema-ini '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/schemas' make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/cpufreq' make[3]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/cpufreq' Making install in maintained/dialect make[3]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/dialect' make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/dialect' (gconftool-2:14577): GConf-WARNING **: None of the resolved addresses are writable; saving configuration settings will not be possible Attached schema `/schemas/apps/awn-applet-dialect/left' to key `/apps/awn-applet-dialect/left' WARNING: failed to install schema `/schemas/apps/awn-applet-dialect/left', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-dialect/left', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-dialect/middle' to key `/apps/awn-applet-dialect/middle' WARNING: failed to install schema `/schemas/apps/awn-applet-dialect/middle', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-dialect/middle', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-dialect/scroll' to key `/apps/awn-applet-dialect/scroll' WARNING: failed to install schema `/schemas/apps/awn-applet-dialect/scroll', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-dialect/scroll', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-dialect/overlay' to key `/apps/awn-applet-dialect/overlay' WARNING: failed to install schema `/schemas/apps/awn-applet-dialect/overlay', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-dialect/overlay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-dialect/scale' to key `/apps/awn-applet-dialect/scale' WARNING: failed to install schema `/schemas/apps/awn-applet-dialect/scale', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-dialect/scale', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-dialect/opacity' to key `/apps/awn-applet-dialect/opacity' WARNING: failed to install schema `/schemas/apps/awn-applet-dialect/opacity', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-dialect/opacity', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-dialect/layout' to key `/apps/awn-applet-dialect/layout' WARNING: failed to install schema `/schemas/apps/awn-applet-dialect/layout', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-dialect/layout', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-dialect/variant' to key `/apps/awn-applet-dialect/variant' WARNING: failed to install schema `/schemas/apps/awn-applet-dialect/variant', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-dialect/variant', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-dialect/toggle' to key `/apps/awn-applet-dialect/toggle' WARNING: failed to install schema `/schemas/apps/awn-applet-dialect/toggle', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-dialect/toggle', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf /usr/bin/install -c -m 644 dialect.desktop '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c -m 644 dialect.ui '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/dialect' /usr/bin/install -c dialect.py '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/dialect' /usr/bin/install -c -m 644 icons/ad.png icons/ae.png icons/af.png icons/al.png icons/am.png icons/ar.png icons/at.png icons/az.png icons/ba.png icons/bd.png icons/be.png icons/bg.png icons/bh.png icons/br.png icons/bt.png icons/by.png icons/ca.png icons/cd.png icons/ch.png icons/cn.png icons/cu.png icons/cz.png icons/de.png icons/dj.png icons/dk.png icons/dz.png icons/ee.png icons/eg.png icons/es.png icons/et.png icons/eu.png icons/fi.png icons/fo.png icons/fr.png icons/gb.png icons/ge.png icons/gh.png icons/gn.png icons/gr.png icons/hr.png '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/dialect/icons' /usr/bin/install -c -m 644 icons/hu.png icons/ie.png icons/il.png icons/in.png icons/iq.png icons/ir.png icons/is.png icons/it.png icons/jo.png icons/jp.png icons/kg.png icons/kh.png icons/km.png icons/kr.png icons/kw.png icons/kz.png icons/la.png icons/lb.png icons/lk.png icons/lt.png icons/lv.png icons/ly.png icons/ma.png icons/me.png icons/mk.png icons/mm.png icons/mn.png icons/mt.png icons/mv.png icons/mx.png icons/ng.png icons/nl.png icons/no.png icons/np.png icons/om.png icons/pk.png icons/pl.png icons/ps.png icons/pt.png icons/qa.png '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/dialect/icons' /usr/bin/install -c -m 644 icons/qc.png icons/ro.png icons/rs.png icons/ru.png icons/sa.png icons/sd.png icons/se.png icons/si.png icons/sk.png icons/so.png icons/sr.png icons/sy.png icons/th.png icons/tj.png icons/tn.png icons/tr.png icons/ua.png icons/un.png icons/us.png icons/uy.png icons/uz.png icons/vn.png icons/ye.png icons/yu.png icons/za.png '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/dialect/icons' /usr/bin/install -c -m 644 awn-applet-dialect.schemas '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/etc/gconf/schemas' /usr/bin/install -c -m 644 awn-applet-dialect.schema-ini '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/schemas' make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/dialect' make[3]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/dialect' Making install in maintained/digital-clock make[3]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/digital-clock' make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/digital-clock' make[5]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/digital-clock' /bin/bash /build/buildd/awn-extras-applets-0.4.0/shave/shave-libtool '../../../doltlibtool' --mode=install /usr/bin/install -c digital-clock.la '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/lib/awn/applets/digital-clock' libtool: install: warning: remember to run `libtool --finish /usr/lib/awn/applets/digital-clock' (gconftool-2:14672): GConf-WARNING **: None of the resolved addresses are writable; saving configuration settings will not be possible Attached schema `/schemas/apps/awn-applet-digital-clock/commands/calendar' to key `/apps/awn-applet-digital-clock/commands/calendar' WARNING: failed to install schema `/schemas/apps/awn-applet-digital-clock/commands/calendar', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-digital-clock/commands/calendar', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-digital-clock/commands/adjust_datetime' to key `/apps/awn-applet-digital-clock/commands/adjust_datetime' WARNING: failed to install schema `/schemas/apps/awn-applet-digital-clock/commands/adjust_datetime', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-digital-clock/commands/adjust_datetime', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-digital-clock/font_face' to key `/apps/awn-applet-digital-clock/font_face' WARNING: failed to install schema `/schemas/apps/awn-applet-digital-clock/font_face', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-digital-clock/font_face', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-digital-clock/font_color' to key `/apps/awn-applet-digital-clock/font_color' WARNING: failed to install schema `/schemas/apps/awn-applet-digital-clock/font_color', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-digital-clock/font_color', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-digital-clock/font_shadow_color' to key `/apps/awn-applet-digital-clock/font_shadow_color' WARNING: failed to install schema `/schemas/apps/awn-applet-digital-clock/font_shadow_color', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-digital-clock/font_shadow_color', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-digital-clock/hour12' to key `/apps/awn-applet-digital-clock/hour12' WARNING: failed to install schema `/schemas/apps/awn-applet-digital-clock/hour12', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-digital-clock/hour12', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-digital-clock/dbt' to key `/apps/awn-applet-digital-clock/dbt' WARNING: failed to install schema `/schemas/apps/awn-applet-digital-clock/dbt', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-digital-clock/dbt', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-digital-clock/show_date' to key `/apps/awn-applet-digital-clock/show_date' WARNING: failed to install schema `/schemas/apps/awn-applet-digital-clock/show_date', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-digital-clock/show_date', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf /usr/bin/install -c -m 644 digital-clock.desktop '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c -m 644 dg-prefs.ui '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/digital-clock' /usr/bin/install -c -m 644 awn-applet-digital-clock.schemas '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/etc/gconf/schemas' /usr/bin/install -c -m 644 awn-applet-digital-clock.svg '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/icons/hicolor/scalable/apps' /usr/bin/install -c -m 644 awn-applet-digital-clock.schema-ini '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/schemas' make[5]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/digital-clock' make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/digital-clock' make[3]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/digital-clock' Making install in maintained/feeds make[3]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/feeds' make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/feeds' (gconftool-2:14723): GConf-WARNING **: None of the resolved addresses are writable; saving configuration settings will not be possible Attached schema `/schemas/apps/awn-applet-feeds/notify' to key `/apps/awn-applet-feeds/notify' WARNING: failed to install schema `/schemas/apps/awn-applet-feeds/notify', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-feeds/notify', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-feeds/auto_update' to key `/apps/awn-applet-feeds/auto_update' WARNING: failed to install schema `/schemas/apps/awn-applet-feeds/auto_update', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-feeds/auto_update', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-feeds/update_interval' to key `/apps/awn-applet-feeds/update_interval' WARNING: failed to install schema `/schemas/apps/awn-applet-feeds/update_interval', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-feeds/update_interval', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-feeds/show_favicons' to key `/apps/awn-applet-feeds/show_favicons' WARNING: failed to install schema `/schemas/apps/awn-applet-feeds/show_favicons', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-feeds/show_favicons', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf /usr/bin/install -c -m 644 feeds.desktop '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c -m 644 classes.py prefs.py icons/awn-feeds.svg icons/awn-feeds-greader.svg icons/twitter-16x16.png '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/feeds' /usr/bin/install -c feeds.py '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/feeds' /usr/bin/install -c -m 644 awn-applet-feeds.schemas '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/etc/gconf/schemas' /usr/bin/install -c -m 644 ./icons/awn-feeds.svg ./icons/awn-feeds-greader.svg ./icons/twitter-16x16.png '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/feeds/icons' /usr/bin/install -c -m 644 awn-applet-feeds.schema-ini '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/schemas' make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/feeds' make[3]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/feeds' Making install in maintained/file-browser-launcher make[3]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/file-browser-launcher' make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/file-browser-launcher' (gconftool-2:14792): GConf-WARNING **: None of the resolved addresses are writable; saving configuration settings will not be possible Attached schema `/schemas/apps/awn-applet-file-browser-launcher/fb' to key `/apps/awn-applet-file-browser-launcher/fb' WARNING: failed to install schema `/schemas/apps/awn-applet-file-browser-launcher/fb', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-file-browser-launcher/fb', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-file-browser-launcher/lmb' to key `/apps/awn-applet-file-browser-launcher/lmb' WARNING: failed to install schema `/schemas/apps/awn-applet-file-browser-launcher/lmb', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-file-browser-launcher/lmb', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-file-browser-launcher/lmb_path' to key `/apps/awn-applet-file-browser-launcher/lmb_path' WARNING: failed to install schema `/schemas/apps/awn-applet-file-browser-launcher/lmb_path', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-file-browser-launcher/lmb_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-file-browser-launcher/mmb' to key `/apps/awn-applet-file-browser-launcher/mmb' WARNING: failed to install schema `/schemas/apps/awn-applet-file-browser-launcher/mmb', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-file-browser-launcher/mmb', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-file-browser-launcher/mmb_path' to key `/apps/awn-applet-file-browser-launcher/mmb_path' WARNING: failed to install schema `/schemas/apps/awn-applet-file-browser-launcher/mmb_path', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-file-browser-launcher/mmb_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-file-browser-launcher/show_bookmarks' to key `/apps/awn-applet-file-browser-launcher/show_bookmarks' WARNING: failed to install schema `/schemas/apps/awn-applet-file-browser-launcher/show_bookmarks', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-file-browser-launcher/show_bookmarks', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-file-browser-launcher/show_home' to key `/apps/awn-applet-file-browser-launcher/show_home' WARNING: failed to install schema `/schemas/apps/awn-applet-file-browser-launcher/show_home', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-file-browser-launcher/show_home', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-file-browser-launcher/show_local' to key `/apps/awn-applet-file-browser-launcher/show_local' WARNING: failed to install schema `/schemas/apps/awn-applet-file-browser-launcher/show_local', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-file-browser-launcher/show_local', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-file-browser-launcher/show_network' to key `/apps/awn-applet-file-browser-launcher/show_network' WARNING: failed to install schema `/schemas/apps/awn-applet-file-browser-launcher/show_network', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-file-browser-launcher/show_network', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-file-browser-launcher/show_filesystem' to key `/apps/awn-applet-file-browser-launcher/show_filesystem' WARNING: failed to install schema `/schemas/apps/awn-applet-file-browser-launcher/show_filesystem', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-file-browser-launcher/show_filesystem', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-file-browser-launcher/show_connect' to key `/apps/awn-applet-file-browser-launcher/show_connect' WARNING: failed to install schema `/schemas/apps/awn-applet-file-browser-launcher/show_connect', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-file-browser-launcher/show_connect', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-file-browser-launcher/places_open' to key `/apps/awn-applet-file-browser-launcher/places_open' WARNING: failed to install schema `/schemas/apps/awn-applet-file-browser-launcher/places_open', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-file-browser-launcher/places_open', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-file-browser-launcher/focus_entry' to key `/apps/awn-applet-file-browser-launcher/focus_entry' WARNING: failed to install schema `/schemas/apps/awn-applet-file-browser-launcher/focus_entry', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-file-browser-launcher/focus_entry', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-file-browser-launcher/mode' to key `/apps/awn-applet-file-browser-launcher/mode' WARNING: failed to install schema `/schemas/apps/awn-applet-file-browser-launcher/mode', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-file-browser-launcher/mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf /usr/bin/install -c -m 644 file-browser-launcher.desktop '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c -m 644 about.py prefs.py '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/file-browser-launcher' /usr/bin/install -c file-browser-launcher.py '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/file-browser-launcher' /usr/bin/install -c -m 644 awn-applet-file-browser-launcher.schemas '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/etc/gconf/schemas' /usr/bin/install -c -m 644 awn-applet-file-browser-launcher.schema-ini '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/schemas' make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/file-browser-launcher' make[3]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/file-browser-launcher' Making install in maintained/hardware-sensors make[3]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/hardware-sensors' make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/hardware-sensors' (gconftool-2:14852): GConf-WARNING **: None of the resolved addresses are writable; saving configuration settings will not be possible Attached schema `/schemas/apps/awn-applet-hardware-sensors/unit' to key `/apps/awn-applet-hardware-sensors/unit' WARNING: failed to install schema `/schemas/apps/awn-applet-hardware-sensors/unit', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-hardware-sensors/unit', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-hardware-sensors/timeout' to key `/apps/awn-applet-hardware-sensors/timeout' WARNING: failed to install schema `/schemas/apps/awn-applet-hardware-sensors/timeout', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-hardware-sensors/timeout', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-hardware-sensors/show_value_overlay' to key `/apps/awn-applet-hardware-sensors/show_value_overlay' WARNING: failed to install schema `/schemas/apps/awn-applet-hardware-sensors/show_value_overlay', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-hardware-sensors/show_value_overlay', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-hardware-sensors/font_size' to key `/apps/awn-applet-hardware-sensors/font_size' WARNING: failed to install schema `/schemas/apps/awn-applet-hardware-sensors/font_size', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-hardware-sensors/font_size', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-hardware-sensors/theme' to key `/apps/awn-applet-hardware-sensors/theme' WARNING: failed to install schema `/schemas/apps/awn-applet-hardware-sensors/theme', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-hardware-sensors/theme', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-hardware-sensors/hand_color' to key `/apps/awn-applet-hardware-sensors/hand_color' WARNING: failed to install schema `/schemas/apps/awn-applet-hardware-sensors/hand_color', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-hardware-sensors/hand_color', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-hardware-sensors/ids' to key `/apps/awn-applet-hardware-sensors/ids' WARNING: failed to install schema `/schemas/apps/awn-applet-hardware-sensors/ids', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-hardware-sensors/ids', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-hardware-sensors/labels' to key `/apps/awn-applet-hardware-sensors/labels' WARNING: failed to install schema `/schemas/apps/awn-applet-hardware-sensors/labels', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-hardware-sensors/labels', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-hardware-sensors/show' to key `/apps/awn-applet-hardware-sensors/show' WARNING: failed to install schema `/schemas/apps/awn-applet-hardware-sensors/show', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-hardware-sensors/show', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-hardware-sensors/dialog_row' to key `/apps/awn-applet-hardware-sensors/dialog_row' WARNING: failed to install schema `/schemas/apps/awn-applet-hardware-sensors/dialog_row', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-hardware-sensors/dialog_row', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-hardware-sensors/in_icon' to key `/apps/awn-applet-hardware-sensors/in_icon' WARNING: failed to install schema `/schemas/apps/awn-applet-hardware-sensors/in_icon', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-hardware-sensors/in_icon', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-hardware-sensors/high_values' to key `/apps/awn-applet-hardware-sensors/high_values' WARNING: failed to install schema `/schemas/apps/awn-applet-hardware-sensors/high_values', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-hardware-sensors/high_values', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-hardware-sensors/low_values' to key `/apps/awn-applet-hardware-sensors/low_values' WARNING: failed to install schema `/schemas/apps/awn-applet-hardware-sensors/low_values', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-hardware-sensors/low_values', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-hardware-sensors/high_alarms' to key `/apps/awn-applet-hardware-sensors/high_alarms' WARNING: failed to install schema `/schemas/apps/awn-applet-hardware-sensors/high_alarms', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-hardware-sensors/high_alarms', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-hardware-sensors/low_alarms' to key `/apps/awn-applet-hardware-sensors/low_alarms' WARNING: failed to install schema `/schemas/apps/awn-applet-hardware-sensors/low_alarms', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-hardware-sensors/low_alarms', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf /usr/bin/install -c -m 644 hardware-sensors.desktop '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c -m 644 sensoricon.py hardware-sensors.ui '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/hardware-sensors' /usr/bin/install -c hardware-sensors.py '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/hardware-sensors' /usr/bin/install -c -m 644 images/no_sensors.svg images/thermometer.png images/thermometer.svg '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/hardware-sensors/images' /usr/bin/install -c -m 644 interfaces/__init__.py interfaces/acpisensors.py interfaces/fileinterface.py interfaces/hddtempsensors.py interfaces/lmsensors.py interfaces/nvclocksensors.py interfaces/nvidiasensors.py interfaces/omnibooksensors.py interfaces/sensorinterface.py '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/hardware-sensors/interfaces' /usr/bin/install -c -m 644 sensorvalues/__init__.py sensorvalues/rpmvalue.py sensorvalues/sensorvalue.py sensorvalues/tempvalue.py sensorvalues/units.py sensorvalues/voltvalue.py '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/hardware-sensors/sensorvalues' /usr/bin/install -c -m 644 themes/dark/double.svg themes/dark/single.svg '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/hardware-sensors/themes/dark' /usr/bin/install -c -m 644 themes/transparent/double.svg themes/transparent/single.svg '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/hardware-sensors/themes/transparent' /usr/bin/install -c -m 644 themes/transparent_with_border/double.svg themes/transparent_with_border/single.svg '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/hardware-sensors/themes/transparent_with_border' /usr/bin/install -c -m 644 awn-applet-hardware-sensors.schemas '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/etc/gconf/schemas' /usr/bin/install -c -m 644 awn-applet-hardware-sensors.schema-ini '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/schemas' make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/hardware-sensors' make[3]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/hardware-sensors' Making install in maintained/mail make[3]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/mail' make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/mail' (gconftool-2:14966): GConf-WARNING **: None of the resolved addresses are writable; saving configuration settings will not be possible Attached schema `/schemas/apps/awn-applet-mail/backend' to key `/apps/awn-applet-mail/backend' WARNING: failed to install schema `/schemas/apps/awn-applet-mail/backend', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-mail/backend', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-mail/theme' to key `/apps/awn-applet-mail/theme' WARNING: failed to install schema `/schemas/apps/awn-applet-mail/theme', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-mail/theme', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-mail/email-client' to key `/apps/awn-applet-mail/email-client' WARNING: failed to install schema `/schemas/apps/awn-applet-mail/email-client', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-mail/email-client', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-mail/hide' to key `/apps/awn-applet-mail/hide' WARNING: failed to install schema `/schemas/apps/awn-applet-mail/hide', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-mail/hide', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-mail/show-network-errors' to key `/apps/awn-applet-mail/show-network-errors' WARNING: failed to install schema `/schemas/apps/awn-applet-mail/show-network-errors', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-mail/show-network-errors', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-mail/login-token' to key `/apps/awn-applet-mail/login-token' WARNING: failed to install schema `/schemas/apps/awn-applet-mail/login-token', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-mail/login-token', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-mail/timeout' to key `/apps/awn-applet-mail/timeout' WARNING: failed to install schema `/schemas/apps/awn-applet-mail/timeout', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-mail/timeout', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf /usr/bin/install -c -m 644 mail.desktop '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c -m 644 mail.ui '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/mail' /usr/bin/install -c mail.py '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/mail' /usr/bin/install -c -m 644 icons/error.svg icons/login.svg icons/read.svg icons/unread.svg '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/mail/icons' /usr/bin/install -c -m 644 themes/GMail/index.theme '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/mail/themes/GMail' /usr/bin/install -c -m 644 themes/GMail/scalable/error.svg themes/GMail/scalable/login.svg themes/GMail/scalable/read.svg themes/GMail/scalable/unread.svg '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/mail/themes/GMail/scalable' /usr/bin/install -c -m 644 themes/Reserved/index.theme '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/mail/themes/Reserved' /usr/bin/install -c -m 644 themes/Reserved/scalable/error.svg themes/Reserved/scalable/login.svg themes/Reserved/scalable/read.svg themes/Reserved/scalable/unread.svg '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/mail/themes/Reserved/scalable' /usr/bin/install -c -m 644 awn-applet-mail.schemas '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/etc/gconf/schemas' /usr/bin/install -c -m 644 awn-applet-mail.schema-ini '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/schemas' make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/mail' make[3]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/mail' Making install in maintained/media-control make[3]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/media-control' make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/media-control' (gconftool-2:15071): GConf-WARNING **: None of the resolved addresses are writable; saving configuration settings will not be possible Attached schema `/schemas/apps/awn-applet-media-control/tooltip_format' to key `/apps/awn-applet-media-control/tooltip_format' WARNING: failed to install schema `/schemas/apps/awn-applet-media-control/tooltip_format', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-media-control/tooltip_format', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-media-control/use_docklet' to key `/apps/awn-applet-media-control/use_docklet' WARNING: failed to install schema `/schemas/apps/awn-applet-media-control/use_docklet', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-media-control/use_docklet', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-media-control/docklet_mouseout_close' to key `/apps/awn-applet-media-control/docklet_mouseout_close' WARNING: failed to install schema `/schemas/apps/awn-applet-media-control/docklet_mouseout_close', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-media-control/docklet_mouseout_close', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-media-control/show_album_art' to key `/apps/awn-applet-media-control/show_album_art' WARNING: failed to install schema `/schemas/apps/awn-applet-media-control/show_album_art', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-media-control/show_album_art', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-media-control/album_art_size' to key `/apps/awn-applet-media-control/album_art_size' WARNING: failed to install schema `/schemas/apps/awn-applet-media-control/album_art_size', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-media-control/album_art_size', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf /usr/bin/install -c -m 644 media-control.desktop '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c -m 644 media-control.ui COPYING '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/media-control' /usr/bin/install -c media_control.py '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/media-control' /usr/bin/install -c -m 644 icons/COPYING icons/README icons/media-control.svg icons/missing-artwork.svg '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/media-control/icons' /usr/bin/install -c -m 644 awn-applet-media-control.schemas '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/etc/gconf/schemas' /usr/bin/install -c -m 644 awn-applet-media-control.schema-ini '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/schemas' make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/media-control' make[3]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/media-control' Making install in maintained/media-icons make[3]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/media-icons' make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/media-icons' /usr/bin/install -c -m 644 media-icons.desktop media-icon-next.desktop media-icon-previous.desktop '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c -m 644 COPYING '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/media-icons' /usr/bin/install -c media-icons.py '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/media-icons' /usr/bin/install -c -m 644 icons/COPYING icons/play.svg icons/backward.svg icons/forward.svg '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/media-icons/icons' make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/media-icons' make[3]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/media-icons' Making install in maintained/media-player make[3]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/media-player' make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/media-player' (gconftool-2:15190): GConf-WARNING **: None of the resolved addresses are writable; saving configuration settings will not be possible Attached schema `/schemas/apps/awn-applet-media-player/audiosink' to key `/apps/awn-applet-media-player/audiosink' WARNING: failed to install schema `/schemas/apps/awn-applet-media-player/audiosink', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-media-player/audiosink', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-media-player/videosink' to key `/apps/awn-applet-media-player/videosink' WARNING: failed to install schema `/schemas/apps/awn-applet-media-player/videosink', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-media-player/videosink', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-media-player/video_width' to key `/apps/awn-applet-media-player/video_width' WARNING: failed to install schema `/schemas/apps/awn-applet-media-player/video_width', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-media-player/video_width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-media-player/video_height' to key `/apps/awn-applet-media-player/video_height' WARNING: failed to install schema `/schemas/apps/awn-applet-media-player/video_height', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-media-player/video_height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-media-player/recent_items' to key `/apps/awn-applet-media-player/recent_items' WARNING: failed to install schema `/schemas/apps/awn-applet-media-player/recent_items', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-media-player/recent_items', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf /usr/bin/install -c -m 644 media-player.desktop '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c -m 644 media-player-prefs.ui COPYING '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/media-player' /usr/bin/install -c media_player.py '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/media-player' /usr/bin/install -c -m 644 icons/COPYING icons/README icons/media-player.png '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/media-player/icons' /usr/bin/install -c -m 644 awn-applet-media-player.schemas '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/etc/gconf/schemas' /usr/bin/install -c -m 644 awn-applet-media-player.schema-ini '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/schemas' make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/media-player' make[3]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/media-player' Making install in maintained/mount make[3]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/mount' make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/mount' (gconftool-2:15259): GConf-WARNING **: None of the resolved addresses are writable; saving configuration settings will not be possible Attached schema `/schemas/apps/awn-applet-mount/hidden-mountpoints' to key `/apps/awn-applet-mount/hidden-mountpoints' WARNING: failed to install schema `/schemas/apps/awn-applet-mount/hidden-mountpoints', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-mount/hidden-mountpoints', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-mount/execute-command' to key `/apps/awn-applet-mount/execute-command' WARNING: failed to install schema `/schemas/apps/awn-applet-mount/execute-command', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-mount/execute-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 /usr/bin/install -c -m 644 mount.desktop '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c -m 644 mount.ui '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/mount' /usr/bin/install -c mount.py '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/mount' /usr/bin/install -c -m 644 icons/mount.png icons/AUTHORS '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/mount/icons' /usr/bin/install -c -m 644 awn-applet-mount.schemas '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/etc/gconf/schemas' /usr/bin/install -c -m 644 awn-applet-mount.schema-ini '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/schemas' make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/mount' make[3]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/mount' Making install in maintained/places make[3]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/places' make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/places' /bin/bash /build/buildd/awn-extras-applets-0.4.0/shave/shave-libtool '../../../doltlibtool' --mode=install /usr/bin/install -c places.la '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/lib/awn/applets/places' libtool: install: warning: remember to run `libtool --finish /usr/lib/awn/applets/places' (gconftool-2:15350): GConf-WARNING **: None of the resolved addresses are writable; saving configuration settings will not be possible Attached schema `/schemas/apps/awn-applet-places/bg_normal_colour' to key `/apps/awn-applet-places/bg_normal_colour' WARNING: failed to install schema `/schemas/apps/awn-applet-places/bg_normal_colour', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-places/bg_normal_colour', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-places/text_normal_colour' to key `/apps/awn-applet-places/text_normal_colour' WARNING: failed to install schema `/schemas/apps/awn-applet-places/text_normal_colour', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-places/text_normal_colour', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-places/bg_hover_colour' to key `/apps/awn-applet-places/bg_hover_colour' WARNING: failed to install schema `/schemas/apps/awn-applet-places/bg_hover_colour', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-places/bg_hover_colour', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-places/text_hover_colour' to key `/apps/awn-applet-places/text_hover_colour' WARNING: failed to install schema `/schemas/apps/awn-applet-places/text_hover_colour', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-places/text_hover_colour', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-places/text_size' to key `/apps/awn-applet-places/text_size' WARNING: failed to install schema `/schemas/apps/awn-applet-places/text_size', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-places/text_size', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-places/menu_item_gradient_factor' to key `/apps/awn-applet-places/menu_item_gradient_factor' WARNING: failed to install schema `/schemas/apps/awn-applet-places/menu_item_gradient_factor', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-places/menu_item_gradient_factor', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-places/filemanager' to key `/apps/awn-applet-places/filemanager' WARNING: failed to install schema `/schemas/apps/awn-applet-places/filemanager', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-places/filemanager', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-places/applet_icon' to key `/apps/awn-applet-places/applet_icon' WARNING: failed to install schema `/schemas/apps/awn-applet-places/applet_icon', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-places/applet_icon', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-places/show_tooltips' to key `/apps/awn-applet-places/show_tooltips' WARNING: failed to install schema `/schemas/apps/awn-applet-places/show_tooltips', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-places/show_tooltips', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-places/border_width' to key `/apps/awn-applet-places/border_width' WARNING: failed to install schema `/schemas/apps/awn-applet-places/border_width', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-places/border_width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-places/border_colour' to key `/apps/awn-applet-places/border_colour' WARNING: failed to install schema `/schemas/apps/awn-applet-places/border_colour', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-places/border_colour', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-places/honour_gtk' to key `/apps/awn-applet-places/honour_gtk' WARNING: failed to install schema `/schemas/apps/awn-applet-places/honour_gtk', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-places/honour_gtk', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf /usr/bin/install -c -m 644 places.desktop '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c -m 644 awn-applet-places.schemas '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/etc/gconf/schemas' /usr/bin/install -c -m 644 awn-applet-places.schema-ini '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/schemas' make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/places' make[3]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/places' Making install in maintained/quit make[3]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/quit' make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/quit' (gconftool-2:15391): GConf-WARNING **: None of the resolved addresses are writable; saving configuration settings will not be possible Attached schema `/schemas/apps/awn-applet-quit/left-click-action' to key `/apps/awn-applet-quit/left-click-action' WARNING: failed to install schema `/schemas/apps/awn-applet-quit/left-click-action', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-quit/left-click-action', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-quit/log-out-command' to key `/apps/awn-applet-quit/log-out-command' WARNING: failed to install schema `/schemas/apps/awn-applet-quit/log-out-command', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-quit/log-out-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 Attached schema `/schemas/apps/awn-applet-quit/lock-screen-command' to key `/apps/awn-applet-quit/lock-screen-command' WARNING: failed to install schema `/schemas/apps/awn-applet-quit/lock-screen-command', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-quit/lock-screen-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 /usr/bin/install -c -m 644 quit.desktop quit-lock-screen.desktop quit-log-out.desktop quit-shut-down.desktop '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c quit.py '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/quit' /usr/bin/install -c -m 644 awn-applet-quit.schemas '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/etc/gconf/schemas' /usr/bin/install -c -m 644 awn-applet-quit.schema-ini '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/schemas' make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/quit' make[3]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/quit' Making install in maintained/slickswitcher make[3]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/slickswitcher' make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/slickswitcher' (gconftool-2:15442): GConf-WARNING **: None of the resolved addresses are writable; saving configuration settings will not be possible Attached schema `/schemas/apps/awn-applet-slickswitcher/active_border' to key `/apps/awn-applet-slickswitcher/active_border' WARNING: failed to install schema `/schemas/apps/awn-applet-slickswitcher/active_border', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-slickswitcher/active_border', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-slickswitcher/custom_back' to key `/apps/awn-applet-slickswitcher/custom_back' WARNING: failed to install schema `/schemas/apps/awn-applet-slickswitcher/custom_back', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-slickswitcher/custom_back', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-slickswitcher/custom_border' to key `/apps/awn-applet-slickswitcher/custom_border' WARNING: failed to install schema `/schemas/apps/awn-applet-slickswitcher/custom_border', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-slickswitcher/custom_border', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-slickswitcher/icon_border' to key `/apps/awn-applet-slickswitcher/icon_border' WARNING: failed to install schema `/schemas/apps/awn-applet-slickswitcher/icon_border', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-slickswitcher/icon_border', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-slickswitcher/normal_border' to key `/apps/awn-applet-slickswitcher/normal_border' WARNING: failed to install schema `/schemas/apps/awn-applet-slickswitcher/normal_border', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-slickswitcher/normal_border', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-slickswitcher/shadow_color' to key `/apps/awn-applet-slickswitcher/shadow_color' WARNING: failed to install schema `/schemas/apps/awn-applet-slickswitcher/shadow_color', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-slickswitcher/shadow_color', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-slickswitcher/shine_bottom' to key `/apps/awn-applet-slickswitcher/shine_bottom' WARNING: failed to install schema `/schemas/apps/awn-applet-slickswitcher/shine_bottom', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-slickswitcher/shine_bottom', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-slickswitcher/shine_hover_bottom' to key `/apps/awn-applet-slickswitcher/shine_hover_bottom' WARNING: failed to install schema `/schemas/apps/awn-applet-slickswitcher/shine_hover_bottom', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-slickswitcher/shine_hover_bottom', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-slickswitcher/shine_hover_top' to key `/apps/awn-applet-slickswitcher/shine_hover_top' WARNING: failed to install schema `/schemas/apps/awn-applet-slickswitcher/shine_hover_top', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-slickswitcher/shine_hover_top', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-slickswitcher/shine_top' to key `/apps/awn-applet-slickswitcher/shine_top' WARNING: failed to install schema `/schemas/apps/awn-applet-slickswitcher/shine_top', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-slickswitcher/shine_top', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-slickswitcher/text_color' to key `/apps/awn-applet-slickswitcher/text_color' WARNING: failed to install schema `/schemas/apps/awn-applet-slickswitcher/text_color', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-slickswitcher/text_color', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-slickswitcher/window_border' to key `/apps/awn-applet-slickswitcher/window_border' WARNING: failed to install schema `/schemas/apps/awn-applet-slickswitcher/window_border', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-slickswitcher/window_border', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-slickswitcher/window_main' to key `/apps/awn-applet-slickswitcher/window_main' WARNING: failed to install schema `/schemas/apps/awn-applet-slickswitcher/window_main', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-slickswitcher/window_main', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-slickswitcher/use_custom' to key `/apps/awn-applet-slickswitcher/use_custom' WARNING: failed to install schema `/schemas/apps/awn-applet-slickswitcher/use_custom', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-slickswitcher/use_custom', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-slickswitcher/width' to key `/apps/awn-applet-slickswitcher/width' WARNING: failed to install schema `/schemas/apps/awn-applet-slickswitcher/width', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-slickswitcher/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-slickswitcher/height' to key `/apps/awn-applet-slickswitcher/height' WARNING: failed to install schema `/schemas/apps/awn-applet-slickswitcher/height', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-slickswitcher/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-slickswitcher/background_mode' to key `/apps/awn-applet-slickswitcher/background_mode' WARNING: failed to install schema `/schemas/apps/awn-applet-slickswitcher/background_mode', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-slickswitcher/background_mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-slickswitcher/background_file' to key `/apps/awn-applet-slickswitcher/background_file' WARNING: failed to install schema `/schemas/apps/awn-applet-slickswitcher/background_file', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-slickswitcher/background_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 Attached schema `/schemas/apps/awn-applet-slickswitcher/use_custom_text' to key `/apps/awn-applet-slickswitcher/use_custom_text' WARNING: failed to install schema `/schemas/apps/awn-applet-slickswitcher/use_custom_text', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-slickswitcher/use_custom_text', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf /usr/bin/install -c -m 644 slickswitcher.desktop '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c -m 644 drawing.py prefs.py settings.py switch.py '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/slickswitcher' /usr/bin/install -c slickswitcher.py '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/slickswitcher' /usr/bin/install -c -m 644 icons/background.png icons/border.png icons/dialog.png icons/done.png icons/number.png icons/shine.png icons/windows.png '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/slickswitcher/icons' /usr/bin/install -c -m 644 awn-applet-slickswitcher.schemas '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/etc/gconf/schemas' /usr/bin/install -c -m 644 awn-applet-slickswitcher.schema-ini '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/schemas' make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/slickswitcher' make[3]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/slickswitcher' Making install in maintained/shiny-switcher make[3]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/shiny-switcher' make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/shiny-switcher' /bin/bash /build/buildd/awn-extras-applets-0.4.0/shave/shave-libtool '../../../doltlibtool' --mode=install /usr/bin/install -c shinyswitcher.la '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/lib/awn/applets/shinyswitcher' libtool: install: warning: remember to run `libtool --finish /usr/lib/awn/applets/shinyswitcher' (gconftool-2:15533): GConf-WARNING **: None of the resolved addresses are writable; saving configuration settings will not be possible Attached schema `/schemas/apps/awn-applet-shinyswitcher/rows' to key `/apps/awn-applet-shinyswitcher/rows' WARNING: failed to install schema `/schemas/apps/awn-applet-shinyswitcher/rows', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-shinyswitcher/rows', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-shinyswitcher/columns' to key `/apps/awn-applet-shinyswitcher/columns' WARNING: failed to install schema `/schemas/apps/awn-applet-shinyswitcher/columns', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-shinyswitcher/columns', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-shinyswitcher/background_alpha_active' to key `/apps/awn-applet-shinyswitcher/background_alpha_active' WARNING: failed to install schema `/schemas/apps/awn-applet-shinyswitcher/background_alpha_active', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-shinyswitcher/background_alpha_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 Attached schema `/schemas/apps/awn-applet-shinyswitcher/background_alpha_inactive' to key `/apps/awn-applet-shinyswitcher/background_alpha_inactive' WARNING: failed to install schema `/schemas/apps/awn-applet-shinyswitcher/background_alpha_inactive', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-shinyswitcher/background_alpha_inactive', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-shinyswitcher/applet_scale' to key `/apps/awn-applet-shinyswitcher/applet_scale' WARNING: failed to install schema `/schemas/apps/awn-applet-shinyswitcher/applet_scale', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-shinyswitcher/applet_scale', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-shinyswitcher/show_icon_mode' to key `/apps/awn-applet-shinyswitcher/show_icon_mode' WARNING: failed to install schema `/schemas/apps/awn-applet-shinyswitcher/show_icon_mode', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-shinyswitcher/show_icon_mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-shinyswitcher/scale_icon_mode' to key `/apps/awn-applet-shinyswitcher/scale_icon_mode' WARNING: failed to install schema `/schemas/apps/awn-applet-shinyswitcher/scale_icon_mode', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-shinyswitcher/scale_icon_mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-shinyswitcher/scale_icon_factor' to key `/apps/awn-applet-shinyswitcher/scale_icon_factor' WARNING: failed to install schema `/schemas/apps/awn-applet-shinyswitcher/scale_icon_factor', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-shinyswitcher/scale_icon_factor', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-shinyswitcher/win_grab_mode' to key `/apps/awn-applet-shinyswitcher/win_grab_mode' WARNING: failed to install schema `/schemas/apps/awn-applet-shinyswitcher/win_grab_mode', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-shinyswitcher/win_grab_mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-shinyswitcher/win_grab_method' to key `/apps/awn-applet-shinyswitcher/win_grab_method' WARNING: failed to install schema `/schemas/apps/awn-applet-shinyswitcher/win_grab_method', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-shinyswitcher/win_grab_method', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-shinyswitcher/win_active_icon_alpha' to key `/apps/awn-applet-shinyswitcher/win_active_icon_alpha' WARNING: failed to install schema `/schemas/apps/awn-applet-shinyswitcher/win_active_icon_alpha', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-shinyswitcher/win_active_icon_alpha', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-shinyswitcher/win_inactive_icon_alpha' to key `/apps/awn-applet-shinyswitcher/win_inactive_icon_alpha' WARNING: failed to install schema `/schemas/apps/awn-applet-shinyswitcher/win_inactive_icon_alpha', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-shinyswitcher/win_inactive_icon_alpha', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-shinyswitcher/mousewheel' to key `/apps/awn-applet-shinyswitcher/mousewheel' WARNING: failed to install schema `/schemas/apps/awn-applet-shinyswitcher/mousewheel', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-shinyswitcher/mousewheel', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-shinyswitcher/cache_expiry' to key `/apps/awn-applet-shinyswitcher/cache_expiry' WARNING: failed to install schema `/schemas/apps/awn-applet-shinyswitcher/cache_expiry', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-shinyswitcher/cache_expiry', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-shinyswitcher/scale_icon_position' to key `/apps/awn-applet-shinyswitcher/scale_icon_position' WARNING: failed to install schema `/schemas/apps/awn-applet-shinyswitcher/scale_icon_position', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-shinyswitcher/scale_icon_position', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-shinyswitcher/applet_border_width' to key `/apps/awn-applet-shinyswitcher/applet_border_width' WARNING: failed to install schema `/schemas/apps/awn-applet-shinyswitcher/applet_border_width', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-shinyswitcher/applet_border_width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-shinyswitcher/applet_border_colour' to key `/apps/awn-applet-shinyswitcher/applet_border_colour' WARNING: failed to install schema `/schemas/apps/awn-applet-shinyswitcher/applet_border_colour', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-shinyswitcher/applet_border_colour', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-shinyswitcher/grab_wallpaper' to key `/apps/awn-applet-shinyswitcher/grab_wallpaper' WARNING: failed to install schema `/schemas/apps/awn-applet-shinyswitcher/grab_wallpaper', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-shinyswitcher/grab_wallpaper', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-shinyswitcher/desktop_colour' to key `/apps/awn-applet-shinyswitcher/desktop_colour' WARNING: failed to install schema `/schemas/apps/awn-applet-shinyswitcher/desktop_colour', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-shinyswitcher/desktop_colour', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-shinyswitcher/queued_render_timer' to key `/apps/awn-applet-shinyswitcher/queued_render_timer' WARNING: failed to install schema `/schemas/apps/awn-applet-shinyswitcher/queued_render_timer', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-shinyswitcher/queued_render_timer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf /usr/bin/install -c -m 644 shinyswitcher.desktop '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c -m 644 shiny-prefs.ui shiny-prefs.py '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/shinyswitcher' /usr/bin/install -c -m 644 awn-applet-shinyswitcher.schemas '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/etc/gconf/schemas' /usr/bin/install -c -m 644 awn-applet-shinyswitcher.schema-ini '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/schemas' make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/shiny-switcher' make[3]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/shiny-switcher' Making install in maintained/sysmon make[3]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/sysmon' make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/sysmon' /bin/bash /build/buildd/awn-extras-applets-0.4.0/shave/shave-libtool '../../../doltlibtool' --mode=install /usr/bin/install -c sysmon.la '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/lib/awn/applets/sysmon' libtool: install: warning: remember to run `libtool --finish /usr/lib/awn/applets/sysmon' (gconftool-2:15605): GConf-WARNING **: None of the resolved addresses are writable; saving configuration settings will not be possible Attached schema `/schemas/apps/awn-applet-sysmon/icon/graph_type' to key `/apps/awn-applet-sysmon/icon/graph_type' WARNING: failed to install schema `/schemas/apps/awn-applet-sysmon/icon/graph_type', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-sysmon/icon/graph_type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-sysmon/icon/time_stamp' to key `/apps/awn-applet-sysmon/icon/time_stamp' WARNING: failed to install schema `/schemas/apps/awn-applet-sysmon/icon/time_stamp', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-sysmon/icon/time_stamp', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-sysmon/icon/update_timeout' to key `/apps/awn-applet-sysmon/icon/update_timeout' WARNING: failed to install schema `/schemas/apps/awn-applet-sysmon/icon/update_timeout', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-sysmon/icon/update_timeout', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-sysmon/dummy' to key `/apps/awn-applet-sysmon/dummy' WARNING: failed to install schema `/schemas/apps/awn-applet-sysmon/dummy', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-sysmon/dummy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-sysmon/time_stamp' to key `/apps/awn-applet-sysmon/time_stamp' WARNING: failed to install schema `/schemas/apps/awn-applet-sysmon/time_stamp', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-sysmon/time_stamp', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-sysmon/applet/dummy' to key `/apps/awn-applet-sysmon/applet/dummy' WARNING: failed to install schema `/schemas/apps/awn-applet-sysmon/applet/dummy', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-sysmon/applet/dummy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-sysmon/applet/icon_list' to key `/apps/awn-applet-sysmon/applet/icon_list' WARNING: failed to install schema `/schemas/apps/awn-applet-sysmon/applet/icon_list', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-sysmon/applet/icon_list', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-sysmon/applet/time_stamp' to key `/apps/awn-applet-sysmon/applet/time_stamp' WARNING: failed to install schema `/schemas/apps/awn-applet-sysmon/applet/time_stamp', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-sysmon/applet/time_stamp', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-sysmon/applet/render_bg' to key `/apps/awn-applet-sysmon/applet/render_bg' WARNING: failed to install schema `/schemas/apps/awn-applet-sysmon/applet/render_bg', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-sysmon/applet/render_bg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf /usr/bin/install -c -m 644 sysmon.desktop '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c -m 644 awn-applet-sysmon.schemas '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/etc/gconf/schemas' /usr/bin/install -c -m 644 awn-applet-sysmon.schema-ini '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/schemas' make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/sysmon' make[3]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/sysmon' Making install in maintained/thinkhdaps make[3]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/thinkhdaps' make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/thinkhdaps' /usr/bin/install -c -m 644 thinkhdaps.desktop '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c thinkhdaps.py '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/thinkhdaps' /usr/bin/install -c -m 644 icons/thinkhdaps-running.svg icons/thinkhdaps-paused.svg '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/thinkhdaps/icons' /usr/bin/install -c -m 644 images/thinkhdaps-logo.svg '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/thinkhdaps/images' make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/thinkhdaps' make[3]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/thinkhdaps' Making install in maintained/to-do make[3]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/to-do' make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/to-do' (gconftool-2:15696): GConf-WARNING **: None of the resolved addresses are writable; saving configuration settings will not be possible Attached schema `/schemas/apps/awn-applet-to-do/items' to key `/apps/awn-applet-to-do/items' WARNING: failed to install schema `/schemas/apps/awn-applet-to-do/items', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-to-do/items', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-to-do/details' to key `/apps/awn-applet-to-do/details' WARNING: failed to install schema `/schemas/apps/awn-applet-to-do/details', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-to-do/details', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-to-do/progress' to key `/apps/awn-applet-to-do/progress' WARNING: failed to install schema `/schemas/apps/awn-applet-to-do/progress', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-to-do/progress', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-to-do/priority' to key `/apps/awn-applet-to-do/priority' WARNING: failed to install schema `/schemas/apps/awn-applet-to-do/priority', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-to-do/priority', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-to-do/color' to key `/apps/awn-applet-to-do/color' WARNING: failed to install schema `/schemas/apps/awn-applet-to-do/color', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-to-do/color', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-to-do/title' to key `/apps/awn-applet-to-do/title' WARNING: failed to install schema `/schemas/apps/awn-applet-to-do/title', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-to-do/title', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-to-do/icon_type' to key `/apps/awn-applet-to-do/icon_type' WARNING: failed to install schema `/schemas/apps/awn-applet-to-do/icon_type', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-to-do/icon_type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-to-do/colors' to key `/apps/awn-applet-to-do/colors' WARNING: failed to install schema `/schemas/apps/awn-applet-to-do/colors', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-to-do/colors', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-to-do/category' to key `/apps/awn-applet-to-do/category' WARNING: failed to install schema `/schemas/apps/awn-applet-to-do/category', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-to-do/category', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-to-do/category_name' to key `/apps/awn-applet-to-do/category_name' WARNING: failed to install schema `/schemas/apps/awn-applet-to-do/category_name', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-to-do/category_name', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-to-do/expanded' to key `/apps/awn-applet-to-do/expanded' WARNING: failed to install schema `/schemas/apps/awn-applet-to-do/expanded', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-to-do/expanded', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-to-do/icon_opacity' to key `/apps/awn-applet-to-do/icon_opacity' WARNING: failed to install schema `/schemas/apps/awn-applet-to-do/icon_opacity', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-to-do/icon_opacity', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-to-do/confirm_items' to key `/apps/awn-applet-to-do/confirm_items' WARNING: failed to install schema `/schemas/apps/awn-applet-to-do/confirm_items', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-to-do/confirm_items', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-to-do/confirm_categories' to key `/apps/awn-applet-to-do/confirm_categories' WARNING: failed to install schema `/schemas/apps/awn-applet-to-do/confirm_categories', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-to-do/confirm_categories', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-to-do/use_custom_width' to key `/apps/awn-applet-to-do/use_custom_width' WARNING: failed to install schema `/schemas/apps/awn-applet-to-do/use_custom_width', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-to-do/use_custom_width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-to-do/custom_width' to key `/apps/awn-applet-to-do/custom_width' WARNING: failed to install schema `/schemas/apps/awn-applet-to-do/custom_width', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-to-do/custom_width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-to-do/color_low' to key `/apps/awn-applet-to-do/color_low' WARNING: failed to install schema `/schemas/apps/awn-applet-to-do/color_low', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-to-do/color_low', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-to-do/color_low_text' to key `/apps/awn-applet-to-do/color_low_text' WARNING: failed to install schema `/schemas/apps/awn-applet-to-do/color_low_text', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-to-do/color_low_text', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-to-do/color_med' to key `/apps/awn-applet-to-do/color_med' WARNING: failed to install schema `/schemas/apps/awn-applet-to-do/color_med', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-to-do/color_med', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-to-do/color_med_text' to key `/apps/awn-applet-to-do/color_med_text' WARNING: failed to install schema `/schemas/apps/awn-applet-to-do/color_med_text', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-to-do/color_med_text', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-to-do/color_high' to key `/apps/awn-applet-to-do/color_high' WARNING: failed to install schema `/schemas/apps/awn-applet-to-do/color_high', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-to-do/color_high', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-to-do/color_high_text' to key `/apps/awn-applet-to-do/color_high_text' WARNING: failed to install schema `/schemas/apps/awn-applet-to-do/color_high_text', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-to-do/color_high_text', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf /usr/bin/install -c -m 644 to-do.desktop '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c -m 644 to-do.py settings.py icon.py prefs.py '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/to-do' /usr/bin/install -c to-do.py '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/to-do' /usr/bin/install -c -m 644 awn-applet-to-do.schemas '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/etc/gconf/schemas' /usr/bin/install -c -m 644 awn-applet-to-do.schema-ini '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/schemas' make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/to-do' make[3]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/to-do' Making install in maintained/tomboy-applet make[3]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/tomboy-applet' make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/tomboy-applet' /usr/bin/install -c -m 644 tomboy-applet.desktop '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c tomboy-applet.py '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/tomboy-applet' make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/tomboy-applet' make[3]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/tomboy-applet' Making install in maintained/volume-control make[3]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/volume-control' make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/volume-control' (gconftool-2:15788): GConf-WARNING **: None of the resolved addresses are writable; saving configuration settings will not be possible Attached schema `/schemas/apps/awn-applet-volume-control/theme' to key `/apps/awn-applet-volume-control/theme' WARNING: failed to install schema `/schemas/apps/awn-applet-volume-control/theme', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-volume-control/theme', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-volume-control/device' to key `/apps/awn-applet-volume-control/device' WARNING: failed to install schema `/schemas/apps/awn-applet-volume-control/device', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-volume-control/device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-volume-control/track' to key `/apps/awn-applet-volume-control/track' WARNING: failed to install schema `/schemas/apps/awn-applet-volume-control/track', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-volume-control/track', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf /usr/bin/install -c -m 644 volume-control.desktop '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c -m 644 volume-control.ui volume-control.svg '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/volume-control' /usr/bin/install -c volume-control.py '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/volume-control' /usr/bin/install -c -m 644 themes/Black/index.theme '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/volume-control/themes/Black' /usr/bin/install -c -m 644 themes/Minimal/index.theme '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/volume-control/themes/Minimal' /usr/bin/install -c -m 644 themes/Black/scalable/audio-volume-muted.svg themes/Black/scalable/audio-volume-1.svg themes/Black/scalable/audio-volume-14.svg themes/Black/scalable/audio-volume-21.svg themes/Black/scalable/audio-volume-29.svg themes/Black/scalable/audio-volume-36.svg themes/Black/scalable/audio-volume-43.svg themes/Black/scalable/audio-volume-50.svg themes/Black/scalable/audio-volume-57.svg themes/Black/scalable/audio-volume-64.svg themes/Black/scalable/audio-volume-71.svg themes/Black/scalable/audio-volume-79.svg themes/Black/scalable/audio-volume-86.svg themes/Black/scalable/audio-volume-93.svg themes/Black/scalable/audio-volume-100.svg '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/volume-control/themes/Black/scalable' /usr/bin/install -c -m 644 themes/Minimal/scalable/audio-volume-muted.svg themes/Minimal/scalable/audio-volume-1.svg themes/Minimal/scalable/audio-volume-14.svg themes/Minimal/scalable/audio-volume-21.svg themes/Minimal/scalable/audio-volume-29.svg themes/Minimal/scalable/audio-volume-36.svg themes/Minimal/scalable/audio-volume-43.svg themes/Minimal/scalable/audio-volume-50.svg themes/Minimal/scalable/audio-volume-57.svg themes/Minimal/scalable/audio-volume-64.svg themes/Minimal/scalable/audio-volume-71.svg themes/Minimal/scalable/audio-volume-79.svg themes/Minimal/scalable/audio-volume-86.svg themes/Minimal/scalable/audio-volume-93.svg themes/Minimal/scalable/audio-volume-100.svg '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/volume-control/themes/Minimal/scalable' /usr/bin/install -c -m 644 awn-applet-volume-control.schemas '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/etc/gconf/schemas' /usr/bin/install -c -m 644 awn-applet-volume-control.schema-ini '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/schemas' make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/volume-control' make[3]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/volume-control' Making install in maintained/weather make[3]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/weather' make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/weather' (gconftool-2:15884): GConf-WARNING **: None of the resolved addresses are writable; saving configuration settings will not be possible Attached schema `/schemas/apps/awn-applet-weather/curved_dialog' to key `/apps/awn-applet-weather/curved_dialog' WARNING: failed to install schema `/schemas/apps/awn-applet-weather/curved_dialog', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-weather/curved_dialog', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-weather/location' to key `/apps/awn-applet-weather/location' WARNING: failed to install schema `/schemas/apps/awn-applet-weather/location', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-weather/location', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-weather/location_code' to key `/apps/awn-applet-weather/location_code' WARNING: failed to install schema `/schemas/apps/awn-applet-weather/location_code', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-weather/location_code', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-weather/map_maxwidth' to key `/apps/awn-applet-weather/map_maxwidth' WARNING: failed to install schema `/schemas/apps/awn-applet-weather/map_maxwidth', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-weather/map_maxwidth', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-weather/show-temperature-icon' to key `/apps/awn-applet-weather/show-temperature-icon' WARNING: failed to install schema `/schemas/apps/awn-applet-weather/show-temperature-icon', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-weather/show-temperature-icon', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-weather/temperature-font-size' to key `/apps/awn-applet-weather/temperature-font-size' WARNING: failed to install schema `/schemas/apps/awn-applet-weather/temperature-font-size', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-weather/temperature-font-size', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-weather/temperature-unit' to key `/apps/awn-applet-weather/temperature-unit' WARNING: failed to install schema `/schemas/apps/awn-applet-weather/temperature-unit', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-weather/temperature-unit', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-weather/theme' to key `/apps/awn-applet-weather/theme' WARNING: failed to install schema `/schemas/apps/awn-applet-weather/theme', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-weather/theme', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf /usr/bin/install -c -m 644 weather.desktop '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c -m 644 forecast.py weather.ui '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/weather' /usr/bin/install -c weather.py '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/weather' /usr/bin/install -c -m 644 icons/twc-logo.png '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/weather/icons' /usr/bin/install -c -m 644 themes/moonbeam/index.theme '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/weather/themes/moonbeam' /usr/bin/install -c -m 644 themes/moonbeam/scalable/weather-clear-night.png themes/moonbeam/scalable/weather-clear.png themes/moonbeam/scalable/weather-few-clouds-night.png themes/moonbeam/scalable/weather-few-clouds.png themes/moonbeam/scalable/weather-fog.png themes/moonbeam/scalable/weather-overcast.png themes/moonbeam/scalable/weather-severe-alert.png themes/moonbeam/scalable/weather-showers-scattered.png themes/moonbeam/scalable/weather-showers.png themes/moonbeam/scalable/weather-snow-and-rain.png themes/moonbeam/scalable/weather-snow.png themes/moonbeam/scalable/weather-storm.png '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/weather/themes/moonbeam/scalable' /usr/bin/install -c -m 644 awn-applet-weather.schemas '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/etc/gconf/schemas' /usr/bin/install -c -m 644 awn-applet-weather.schema-ini '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/schemas' make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/weather' make[3]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/weather' Making install in maintained/garbage make[3]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/garbage' make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/garbage' make[5]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/garbage' /bin/bash /build/buildd/awn-extras-applets-0.4.0/shave/shave-libtool '../../../doltlibtool' --mode=install /usr/bin/install -c garbage.la '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/lib/awn/applets/garbage' libtool: install: warning: remember to run `libtool --finish /usr/lib/awn/applets/garbage' (gconftool-2:15995): GConf-WARNING **: None of the resolved addresses are writable; saving configuration settings will not be possible Attached schema `/schemas/apps/awn-applet-garbage/confirm_empty' to key `/apps/awn-applet-garbage/confirm_empty' WARNING: failed to install schema `/schemas/apps/awn-applet-garbage/confirm_empty', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-garbage/confirm_empty', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-garbage/show_count' to key `/apps/awn-applet-garbage/show_count' WARNING: failed to install schema `/schemas/apps/awn-applet-garbage/show_count', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-garbage/show_count', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf /usr/bin/install -c -m 644 garbage.desktop '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c -m 644 awn-applet-garbage.schemas '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/etc/gconf/schemas' /usr/bin/install -c -m 644 awn-applet-garbage.schema-ini '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/schemas' make[5]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/garbage' make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/garbage' make[3]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/garbage' Making install in maintained/notification-area make[3]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/notification-area' make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/notification-area' make[5]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/notification-area' /bin/bash /build/buildd/awn-extras-applets-0.4.0/shave/shave-libtool '../../../doltlibtool' --mode=install /usr/bin/install -c notification-area.la '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/lib/awn/applets/notification-area' libtool: install: warning: remember to run `libtool --finish /usr/lib/awn/applets/notification-area' (gconftool-2:16060): GConf-WARNING **: None of the resolved addresses are writable; saving configuration settings will not be possible Attached schema `/schemas/apps/awn-applet-notification-area/icons_per_cell' to key `/apps/awn-applet-notification-area/icons_per_cell' WARNING: failed to install schema `/schemas/apps/awn-applet-notification-area/icons_per_cell', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-notification-area/icons_per_cell', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-notification-area/icon_size' to key `/apps/awn-applet-notification-area/icon_size' WARNING: failed to install schema `/schemas/apps/awn-applet-notification-area/icon_size', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-notification-area/icon_size', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-notification-area/extra_offset' to key `/apps/awn-applet-notification-area/extra_offset' WARNING: failed to install schema `/schemas/apps/awn-applet-notification-area/extra_offset', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-notification-area/extra_offset', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-notification-area/background_color' to key `/apps/awn-applet-notification-area/background_color' WARNING: failed to install schema `/schemas/apps/awn-applet-notification-area/background_color', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-notification-area/background_color', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-notification-area/border_color' to key `/apps/awn-applet-notification-area/border_color' WARNING: failed to install schema `/schemas/apps/awn-applet-notification-area/border_color', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-notification-area/border_color', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf /usr/bin/install -c -m 644 notification-area.desktop '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c -m 644 na-prefs.ui '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/notification-area' /usr/bin/install -c -m 644 awn-applet-notification-area.schemas '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/etc/gconf/schemas' /usr/bin/install -c -m 644 notification-area.svg '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/icons/hicolor/scalable/apps' /usr/bin/install -c -m 644 awn-applet-notification-area.schema-ini '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/schemas' make[5]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/notification-area' make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/notification-area' make[3]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/notification-area' Making install in maintained/showdesktop make[3]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/showdesktop' make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/showdesktop' make[5]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/showdesktop' /bin/bash /build/buildd/awn-extras-applets-0.4.0/shave/shave-libtool '../../../doltlibtool' --mode=install /usr/bin/install -c showdesktop.la '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/lib/awn/applets/showdesktop' libtool: install: warning: remember to run `libtool --finish /usr/lib/awn/applets/showdesktop' /usr/bin/install -c -m 644 showdesktop.desktop '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets' make[5]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/showdesktop' make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/showdesktop' make[3]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/showdesktop' Making install in unmaintained/awnsystemmonitor make[3]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/unmaintained/awnsystemmonitor' make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/unmaintained/awnsystemmonitor' /bin/bash /build/buildd/awn-extras-applets-0.4.0/shave/shave-libtool '../../../doltlibtool' --mode=install /usr/bin/install -c awnsystemmonitor.la '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/lib/awn/applets/awnsystemmonitor' libtool: install: warning: remember to run `libtool --finish /usr/lib/awn/applets/awnsystemmonitor' (gconftool-2:16179): GConf-WARNING **: None of the resolved addresses are writable; saving configuration settings will not be possible WARNING: failed to install schema `/schemas/apps/awn-cpumeter/prefs/graph_color', locale `C': Unable to store a value at key '/schemas/apps/awn-cpumeter/prefs/graph_color', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/awn-cpumeter/prefs/border_color', locale `C': Unable to store a value at key '/schemas/apps/awn-cpumeter/prefs/border_color', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/awn-cpumeter/prefs/border_width', locale `C': Unable to store a value at key '/schemas/apps/awn-cpumeter/prefs/border_width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/awn-cpumeter/prefs/do_gradient', locale `C': Unable to store a value at key '/schemas/apps/awn-cpumeter/prefs/do_gradient', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/awn-cpumeter/prefs/update_frequency', locale `en_US@piglatin': Unable to store a value at key '/schemas/apps/awn-cpumeter/prefs/update_frequency', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/awn-cpumeter/prefs/update_frequency', locale `C': Unable to store a value at key '/schemas/apps/awn-cpumeter/prefs/update_frequency', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf /usr/bin/install -c -m 644 awnsystemmonitor.desktop '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c -m 644 awnsystemmonitor.schemas '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/etc/gconf/schemas' make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/unmaintained/awnsystemmonitor' make[3]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/unmaintained/awnsystemmonitor' Making install in maintained/calendar make[3]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/calendar' make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/calendar' (gconftool-2:16211): GConf-WARNING **: None of the resolved addresses are writable; saving configuration settings will not be possible Attached schema `/schemas/apps/awn-applet-calendar/clock_background' to key `/apps/awn-applet-calendar/clock_background' WARNING: failed to install schema `/schemas/apps/awn-applet-calendar/clock_background', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-calendar/clock_background', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-calendar/clock_border' to key `/apps/awn-applet-calendar/clock_border' WARNING: failed to install schema `/schemas/apps/awn-applet-calendar/clock_border', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-calendar/clock_border', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-calendar/clock_foreground' to key `/apps/awn-applet-calendar/clock_foreground' WARNING: failed to install schema `/schemas/apps/awn-applet-calendar/clock_foreground', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-calendar/clock_foreground', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-calendar/graphic' to key `/apps/awn-applet-calendar/graphic' WARNING: failed to install schema `/schemas/apps/awn-applet-calendar/graphic', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-calendar/graphic', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-calendar/integration' to key `/apps/awn-applet-calendar/integration' WARNING: failed to install schema `/schemas/apps/awn-applet-calendar/integration', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-calendar/integration', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-calendar/password' to key `/apps/awn-applet-calendar/password' WARNING: failed to install schema `/schemas/apps/awn-applet-calendar/password', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-calendar/password', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-calendar/url' to key `/apps/awn-applet-calendar/url' WARNING: failed to install schema `/schemas/apps/awn-applet-calendar/url', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-calendar/url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-calendar/username' to key `/apps/awn-applet-calendar/username' WARNING: failed to install schema `/schemas/apps/awn-applet-calendar/username', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-calendar/username', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-calendar/twelve_hour_clock' to key `/apps/awn-applet-calendar/twelve_hour_clock' WARNING: failed to install schema `/schemas/apps/awn-applet-calendar/twelve_hour_clock', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-calendar/twelve_hour_clock', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-calendar/blinking_colon' to key `/apps/awn-applet-calendar/blinking_colon' WARNING: failed to install schema `/schemas/apps/awn-applet-calendar/blinking_colon', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-calendar/blinking_colon', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-calendar/clock_plain' to key `/apps/awn-applet-calendar/clock_plain' WARNING: failed to install schema `/schemas/apps/awn-applet-calendar/clock_plain', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-calendar/clock_plain', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-calendar/cal_appearance_index' to key `/apps/awn-applet-calendar/cal_appearance_index' WARNING: failed to install schema `/schemas/apps/awn-applet-calendar/cal_appearance_index', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-calendar/cal_appearance_index', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-calendar/clock_appearance_index' to key `/apps/awn-applet-calendar/clock_appearance_index' WARNING: failed to install schema `/schemas/apps/awn-applet-calendar/clock_appearance_index', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-calendar/clock_appearance_index', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf /usr/bin/install -c -m 644 calendar.desktop '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c -m 644 calendarlogin.py calendarprefs.py calthread.py evocal.py googlecal.py icscal.py owacal.py sevensegled.py '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/calendar' /usr/bin/install -c clockcal.py '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/calendar' /usr/bin/install -c -m 644 images/calendar-black.png images/calendar-blue.png images/calendar-gray.png images/calendar-green.png images/calendar-red.png images/calendar.png images/icon.png '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/calendar/images' /usr/bin/install -c -m 644 awn-applet-calendar.schemas '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/etc/gconf/schemas' /usr/bin/install -c -m 644 awn-applet-calendar.schema-ini '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/schemas' make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/calendar' make[3]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/calendar' Making install in maintained/notification-daemon make[3]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/notification-daemon' make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/notification-daemon' make[5]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/notification-daemon' /bin/bash /build/buildd/awn-extras-applets-0.4.0/shave/shave-libtool '../../../doltlibtool' --mode=install /usr/bin/install -c notification-daemon.la '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/lib/awn/applets/notification-daemon' libtool: install: warning: remember to run `libtool --finish /usr/lib/awn/applets/notification-daemon' (gconftool-2:16304): GConf-WARNING **: None of the resolved addresses are writable; saving configuration settings will not be possible Attached schema `/schemas/apps/awn-applet-notification-daemon/kill_standard_daemon' to key `/apps/awn-applet-notification-daemon/kill_standard_daemon' WARNING: failed to install schema `/schemas/apps/awn-applet-notification-daemon/kill_standard_daemon', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-notification-daemon/kill_standard_daemon', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-notification-daemon/honour_client_posxy' to key `/apps/awn-applet-notification-daemon/honour_client_posxy' WARNING: failed to install schema `/schemas/apps/awn-applet-notification-daemon/honour_client_posxy', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-notification-daemon/honour_client_posxy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-notification-daemon/use_theme' to key `/apps/awn-applet-notification-daemon/use_theme' WARNING: failed to install schema `/schemas/apps/awn-applet-notification-daemon/use_theme', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-notification-daemon/use_theme', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-notification-daemon/sound_enabled' to key `/apps/awn-applet-notification-daemon/sound_enabled' WARNING: failed to install schema `/schemas/apps/awn-applet-notification-daemon/sound_enabled', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-notification-daemon/sound_enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-notification-daemon/bg_colour' to key `/apps/awn-applet-notification-daemon/bg_colour' WARNING: failed to install schema `/schemas/apps/awn-applet-notification-daemon/bg_colour', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-notification-daemon/bg_colour', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-notification-daemon/text_colour' to key `/apps/awn-applet-notification-daemon/text_colour' WARNING: failed to install schema `/schemas/apps/awn-applet-notification-daemon/text_colour', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-notification-daemon/text_colour', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-notification-daemon/border_colour' to key `/apps/awn-applet-notification-daemon/border_colour' WARNING: failed to install schema `/schemas/apps/awn-applet-notification-daemon/border_colour', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-notification-daemon/border_colour', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-notification-daemon/border_width' to key `/apps/awn-applet-notification-daemon/border_width' WARNING: failed to install schema `/schemas/apps/awn-applet-notification-daemon/border_width', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-notification-daemon/border_width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-notification-daemon/gradient_factor' to key `/apps/awn-applet-notification-daemon/gradient_factor' WARNING: failed to install schema `/schemas/apps/awn-applet-notification-daemon/gradient_factor', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-notification-daemon/gradient_factor', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-notification-daemon/override_x' to key `/apps/awn-applet-notification-daemon/override_x' WARNING: failed to install schema `/schemas/apps/awn-applet-notification-daemon/override_x', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-notification-daemon/override_x', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-notification-daemon/override_y' to key `/apps/awn-applet-notification-daemon/override_y' WARNING: failed to install schema `/schemas/apps/awn-applet-notification-daemon/override_y', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-notification-daemon/override_y', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-notification-daemon/override_timeout' to key `/apps/awn-applet-notification-daemon/override_timeout' WARNING: failed to install schema `/schemas/apps/awn-applet-notification-daemon/override_timeout', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-notification-daemon/override_timeout', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-notification-daemon/show_icon' to key `/apps/awn-applet-notification-daemon/show_icon' WARNING: failed to install schema `/schemas/apps/awn-applet-notification-daemon/show_icon', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-notification-daemon/show_icon', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-notification-daemon/hide_opacity' to key `/apps/awn-applet-notification-daemon/hide_opacity' WARNING: failed to install schema `/schemas/apps/awn-applet-notification-daemon/hide_opacity', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-notification-daemon/hide_opacity', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-notification-daemon/default_sound' to key `/apps/awn-applet-notification-daemon/default_sound' WARNING: failed to install schema `/schemas/apps/awn-applet-notification-daemon/default_sound', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-notification-daemon/default_sound', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-notification-daemon/bold_text_body' to key `/apps/awn-applet-notification-daemon/bold_text_body' WARNING: failed to install schema `/schemas/apps/awn-applet-notification-daemon/bold_text_body', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-notification-daemon/bold_text_body', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf /usr/bin/install -c -m 644 notification-daemon.desktop '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c -m 644 awn-applet-notification-daemon.schemas '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/etc/gconf/schemas' /usr/bin/install -c -m 644 awn-applet-notification-daemon.schema-ini '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/schemas' make[5]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/notification-daemon' make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/notification-daemon' make[3]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/notification-daemon' Making install in maintained/cairo-menu make[3]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/cairo-menu' make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/cairo-menu' /bin/bash /build/buildd/awn-extras-applets-0.4.0/shave/shave-libtool '../../../doltlibtool' --mode=install /usr/bin/install -c cairo-menu.la '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/lib/awn/applets/cairo-menu' libtool: install: warning: remember to run `libtool --finish /usr/lib/awn/applets/cairo-menu' (gconftool-2:16367): GConf-WARNING **: None of the resolved addresses are writable; saving configuration settings will not be possible Attached schema `/schemas/apps/awn-applet-cairo-menu/bg_normal_colour' to key `/apps/awn-applet-cairo-menu/bg_normal_colour' WARNING: failed to install schema `/schemas/apps/awn-applet-cairo-menu/bg_normal_colour', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-cairo-menu/bg_normal_colour', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-cairo-menu/text_normal_colour' to key `/apps/awn-applet-cairo-menu/text_normal_colour' WARNING: failed to install schema `/schemas/apps/awn-applet-cairo-menu/text_normal_colour', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-cairo-menu/text_normal_colour', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-cairo-menu/bg_hover_colour' to key `/apps/awn-applet-cairo-menu/bg_hover_colour' WARNING: failed to install schema `/schemas/apps/awn-applet-cairo-menu/bg_hover_colour', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-cairo-menu/bg_hover_colour', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-cairo-menu/text_hover_colour' to key `/apps/awn-applet-cairo-menu/text_hover_colour' WARNING: failed to install schema `/schemas/apps/awn-applet-cairo-menu/text_hover_colour', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-cairo-menu/text_hover_colour', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-cairo-menu/text_size' to key `/apps/awn-applet-cairo-menu/text_size' WARNING: failed to install schema `/schemas/apps/awn-applet-cairo-menu/text_size', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-cairo-menu/text_size', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-cairo-menu/search_cmd' to key `/apps/awn-applet-cairo-menu/search_cmd' WARNING: failed to install schema `/schemas/apps/awn-applet-cairo-menu/search_cmd', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-cairo-menu/search_cmd', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-cairo-menu/search_show' to key `/apps/awn-applet-cairo-menu/search_show' WARNING: failed to install schema `/schemas/apps/awn-applet-cairo-menu/search_show', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-cairo-menu/search_show', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-cairo-menu/run_show' to key `/apps/awn-applet-cairo-menu/run_show' WARNING: failed to install schema `/schemas/apps/awn-applet-cairo-menu/run_show', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-cairo-menu/run_show', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-cairo-menu/fade_in' to key `/apps/awn-applet-cairo-menu/fade_in' WARNING: failed to install schema `/schemas/apps/awn-applet-cairo-menu/fade_in', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-cairo-menu/fade_in', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-cairo-menu/menu_item_gradient_factor' to key `/apps/awn-applet-cairo-menu/menu_item_gradient_factor' WARNING: failed to install schema `/schemas/apps/awn-applet-cairo-menu/menu_item_gradient_factor', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-cairo-menu/menu_item_gradient_factor', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-cairo-menu/menu_item_text_len' to key `/apps/awn-applet-cairo-menu/menu_item_text_len' WARNING: failed to install schema `/schemas/apps/awn-applet-cairo-menu/menu_item_text_len', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-cairo-menu/menu_item_text_len', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-cairo-menu/places_show' to key `/apps/awn-applet-cairo-menu/places_show' WARNING: failed to install schema `/schemas/apps/awn-applet-cairo-menu/places_show', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-cairo-menu/places_show', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-cairo-menu/filemanager' to key `/apps/awn-applet-cairo-menu/filemanager' WARNING: failed to install schema `/schemas/apps/awn-applet-cairo-menu/filemanager', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-cairo-menu/filemanager', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-cairo-menu/applet_icon' to key `/apps/awn-applet-cairo-menu/applet_icon' WARNING: failed to install schema `/schemas/apps/awn-applet-cairo-menu/applet_icon', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-cairo-menu/applet_icon', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-cairo-menu/activate_on_release' to key `/apps/awn-applet-cairo-menu/activate_on_release' WARNING: failed to install schema `/schemas/apps/awn-applet-cairo-menu/activate_on_release', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-cairo-menu/activate_on_release', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-cairo-menu/show_tooltips' to key `/apps/awn-applet-cairo-menu/show_tooltips' WARNING: failed to install schema `/schemas/apps/awn-applet-cairo-menu/show_tooltips', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-cairo-menu/show_tooltips', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-cairo-menu/show_logout' to key `/apps/awn-applet-cairo-menu/show_logout' WARNING: failed to install schema `/schemas/apps/awn-applet-cairo-menu/show_logout', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-cairo-menu/show_logout', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-cairo-menu/logout' to key `/apps/awn-applet-cairo-menu/logout' WARNING: failed to install schema `/schemas/apps/awn-applet-cairo-menu/logout', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-cairo-menu/logout', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-cairo-menu/border_colour' to key `/apps/awn-applet-cairo-menu/border_colour' WARNING: failed to install schema `/schemas/apps/awn-applet-cairo-menu/border_colour', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-cairo-menu/border_colour', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-cairo-menu/border_width' to key `/apps/awn-applet-cairo-menu/border_width' WARNING: failed to install schema `/schemas/apps/awn-applet-cairo-menu/border_width', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-cairo-menu/border_width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-cairo-menu/honour_gtk' to key `/apps/awn-applet-cairo-menu/honour_gtk' WARNING: failed to install schema `/schemas/apps/awn-applet-cairo-menu/honour_gtk', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-cairo-menu/honour_gtk', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-cairo-menu/aux_menu_names' to key `/apps/awn-applet-cairo-menu/aux_menu_names' WARNING: failed to install schema `/schemas/apps/awn-applet-cairo-menu/aux_menu_names', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-cairo-menu/aux_menu_names', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-cairo-menu/hidden_names' to key `/apps/awn-applet-cairo-menu/hidden_names' WARNING: failed to install schema `/schemas/apps/awn-applet-cairo-menu/hidden_names', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-cairo-menu/hidden_names', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-cairo-menu/run_cmd' to key `/apps/awn-applet-cairo-menu/run_cmd' WARNING: failed to install schema `/schemas/apps/awn-applet-cairo-menu/run_cmd', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-cairo-menu/run_cmd', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf /usr/bin/install -c -m 644 cairo-menu.desktop '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c -m 644 awn-applet-cairo-menu.schemas '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/etc/gconf/schemas' /bin/bash /build/buildd/awn-extras-applets-0.4.0/shave/shave-libtool '../../../doltlibtool' --mode=install /usr/bin/install -c gnome-menu-builder.la '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/lib/awn/applets/cairo-menu' libtool: install: warning: remember to run `libtool --finish /usr/lib/awn/applets/cairo-menu' /usr/bin/install -c -m 644 awn-applet-cairo-menu.schema-ini '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/schemas' make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/cairo-menu' make[3]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/cairo-menu' Making install in unmaintained/main-menu make[3]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/unmaintained/main-menu' make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/unmaintained/main-menu' /bin/bash /build/buildd/awn-extras-applets-0.4.0/shave/shave-libtool '../../../doltlibtool' --mode=install /usr/bin/install -c main-menu.la '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/lib/awn/applets/main-menu' libtool: install: warning: remember to run `libtool --finish /usr/lib/awn/applets/main-menu' /usr/bin/install -c -m 644 main-menu.desktop '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets' make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/unmaintained/main-menu' make[3]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/unmaintained/main-menu' Making install in unmaintained/MiMenu make[3]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/unmaintained/MiMenu' make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/unmaintained/MiMenu' /usr/bin/install -c -m 644 mimenu.desktop '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c -m 644 COPYING keyboard.py menus.py pathfinder.py '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/mimenu' /usr/bin/install -c mimenu.py '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/mimenu' /usr/bin/install -c -m 644 icons/icon.svg '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/mimenu/icons' make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/unmaintained/MiMenu' make[3]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/unmaintained/MiMenu' Making install in unmaintained/pandora make[3]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/unmaintained/pandora' make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/unmaintained/pandora' (gconftool-2:16524): GConf-WARNING **: None of the resolved addresses are writable; saving configuration settings will not be possible Attached schema `/schemas/apps/awn-applet-pandora/url' to key `/apps/awn-applet-pandora/url' WARNING: failed to install schema `/schemas/apps/awn-applet-pandora/url', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-pandora/url', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf /usr/bin/install -c -m 644 pandora.desktop '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c pandora.py '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/pandora' /usr/bin/install -c -m 644 icons/pandora.png '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/pandora/icons' /usr/bin/install -c -m 644 awn-applet-pandora.schemas '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/etc/gconf/schemas' /usr/bin/install -c -m 644 awn-applet-pandora.schema-ini '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/schemas' make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/unmaintained/pandora' make[3]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/unmaintained/pandora' Making install in unmaintained/stacks make[3]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/unmaintained/stacks' make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/unmaintained/stacks' (gconftool-2:16584): GConf-WARNING **: None of the resolved addresses are writable; saving configuration settings will not be possible Attached schema `/schemas/apps/awn-applet-stacks/backend_type' to key `/apps/awn-applet-stacks/backend_type' WARNING: failed to install schema `/schemas/apps/awn-applet-stacks/backend_type', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-stacks/backend_type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-stacks/backend' to key `/apps/awn-applet-stacks/backend' WARNING: failed to install schema `/schemas/apps/awn-applet-stacks/backend', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-stacks/backend', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-stacks/close_on_focusout' to key `/apps/awn-applet-stacks/close_on_focusout' WARNING: failed to install schema `/schemas/apps/awn-applet-stacks/close_on_focusout', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-stacks/close_on_focusout', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-stacks/rows' to key `/apps/awn-applet-stacks/rows' WARNING: failed to install schema `/schemas/apps/awn-applet-stacks/rows', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-stacks/rows', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-stacks/cols' to key `/apps/awn-applet-stacks/cols' WARNING: failed to install schema `/schemas/apps/awn-applet-stacks/cols', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-stacks/cols', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-stacks/icon_size' to key `/apps/awn-applet-stacks/icon_size' WARNING: failed to install schema `/schemas/apps/awn-applet-stacks/icon_size', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-stacks/icon_size', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-stacks/file_operations' to key `/apps/awn-applet-stacks/file_operations' WARNING: failed to install schema `/schemas/apps/awn-applet-stacks/file_operations', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-stacks/file_operations', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-stacks/composite_icon' to key `/apps/awn-applet-stacks/composite_icon' WARNING: failed to install schema `/schemas/apps/awn-applet-stacks/composite_icon', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-stacks/composite_icon', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-stacks/browsing' to key `/apps/awn-applet-stacks/browsing' WARNING: failed to install schema `/schemas/apps/awn-applet-stacks/browsing', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-stacks/browsing', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-stacks/applet_icon_empty' to key `/apps/awn-applet-stacks/applet_icon_empty' WARNING: failed to install schema `/schemas/apps/awn-applet-stacks/applet_icon_empty', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-stacks/applet_icon_empty', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-stacks/applet_icon_full' to key `/apps/awn-applet-stacks/applet_icon_full' WARNING: failed to install schema `/schemas/apps/awn-applet-stacks/applet_icon_full', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-stacks/applet_icon_full', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-stacks/item_count' to key `/apps/awn-applet-stacks/item_count' WARNING: failed to install schema `/schemas/apps/awn-applet-stacks/item_count', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-stacks/item_count', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-stacks/gui_type' to key `/apps/awn-applet-stacks/gui_type' WARNING: failed to install schema `/schemas/apps/awn-applet-stacks/gui_type', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-stacks/gui_type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-stacks/title' to key `/apps/awn-applet-stacks/title' WARNING: failed to install schema `/schemas/apps/awn-applet-stacks/title', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-stacks/title', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-stacks/sort_method' to key `/apps/awn-applet-stacks/sort_method' WARNING: failed to install schema `/schemas/apps/awn-applet-stacks/sort_method', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-stacks/sort_method', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-stacks/sort_folders_before_files' to key `/apps/awn-applet-stacks/sort_folders_before_files' WARNING: failed to install schema `/schemas/apps/awn-applet-stacks/sort_folders_before_files', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-stacks/sort_folders_before_files', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-stacks/sort_direction' to key `/apps/awn-applet-stacks/sort_direction' WARNING: failed to install schema `/schemas/apps/awn-applet-stacks/sort_direction', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-stacks/sort_direction', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-stacks/curved_gui/label_length' to key `/apps/awn-applet-stacks/curved_gui/label_length' WARNING: failed to install schema `/schemas/apps/awn-applet-stacks/curved_gui/label_length', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-stacks/curved_gui/label_length', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-stacks/curved_gui/label_text_color' to key `/apps/awn-applet-stacks/curved_gui/label_text_color' WARNING: failed to install schema `/schemas/apps/awn-applet-stacks/curved_gui/label_text_color', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-stacks/curved_gui/label_text_color', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-stacks/curved_gui/label_text_hover_color' to key `/apps/awn-applet-stacks/curved_gui/label_text_hover_color' WARNING: failed to install schema `/schemas/apps/awn-applet-stacks/curved_gui/label_text_hover_color', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-stacks/curved_gui/label_text_hover_color', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-stacks/curved_gui/label_background_color' to key `/apps/awn-applet-stacks/curved_gui/label_background_color' WARNING: failed to install schema `/schemas/apps/awn-applet-stacks/curved_gui/label_background_color', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-stacks/curved_gui/label_background_color', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-stacks/curved_gui/label_hover_background_color' to key `/apps/awn-applet-stacks/curved_gui/label_hover_background_color' WARNING: failed to install schema `/schemas/apps/awn-applet-stacks/curved_gui/label_hover_background_color', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-stacks/curved_gui/label_hover_background_color', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-stacks/curved_gui/label_border_color' to key `/apps/awn-applet-stacks/curved_gui/label_border_color' WARNING: failed to install schema `/schemas/apps/awn-applet-stacks/curved_gui/label_border_color', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-stacks/curved_gui/label_border_color', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-stacks/curved_gui/label_hover_border_color' to key `/apps/awn-applet-stacks/curved_gui/label_hover_border_color' WARNING: failed to install schema `/schemas/apps/awn-applet-stacks/curved_gui/label_hover_border_color', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-stacks/curved_gui/label_hover_border_color', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-stacks/curved_gui/use_awn_title_font' to key `/apps/awn-applet-stacks/curved_gui/use_awn_title_font' WARNING: failed to install schema `/schemas/apps/awn-applet-stacks/curved_gui/use_awn_title_font', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-stacks/curved_gui/use_awn_title_font', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-stacks/curved_gui/label_font' to key `/apps/awn-applet-stacks/curved_gui/label_font' WARNING: failed to install schema `/schemas/apps/awn-applet-stacks/curved_gui/label_font', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-stacks/curved_gui/label_font', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-stacks/curved_gui/layout_radius' to key `/apps/awn-applet-stacks/curved_gui/layout_radius' WARNING: failed to install schema `/schemas/apps/awn-applet-stacks/curved_gui/layout_radius', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-stacks/curved_gui/layout_radius', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-stacks/curved_gui/layout_interval' to key `/apps/awn-applet-stacks/curved_gui/layout_interval' WARNING: failed to install schema `/schemas/apps/awn-applet-stacks/curved_gui/layout_interval', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-stacks/curved_gui/layout_interval', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-stacks/curved_gui/layout_direction' to key `/apps/awn-applet-stacks/curved_gui/layout_direction' WARNING: failed to install schema `/schemas/apps/awn-applet-stacks/curved_gui/layout_direction', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-stacks/curved_gui/layout_direction', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-stacks/curved_gui/tooltips_enabled' to key `/apps/awn-applet-stacks/curved_gui/tooltips_enabled' WARNING: failed to install schema `/schemas/apps/awn-applet-stacks/curved_gui/tooltips_enabled', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-stacks/curved_gui/tooltips_enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-stacks/curved_gui/tooltip_bg_color1' to key `/apps/awn-applet-stacks/curved_gui/tooltip_bg_color1' WARNING: failed to install schema `/schemas/apps/awn-applet-stacks/curved_gui/tooltip_bg_color1', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-stacks/curved_gui/tooltip_bg_color1', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-stacks/curved_gui/tooltip_bg_color2' to key `/apps/awn-applet-stacks/curved_gui/tooltip_bg_color2' WARNING: failed to install schema `/schemas/apps/awn-applet-stacks/curved_gui/tooltip_bg_color2', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-stacks/curved_gui/tooltip_bg_color2', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-stacks/curved_gui/tooltip_border_color' to key `/apps/awn-applet-stacks/curved_gui/tooltip_border_color' WARNING: failed to install schema `/schemas/apps/awn-applet-stacks/curved_gui/tooltip_border_color', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-stacks/curved_gui/tooltip_border_color', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-stacks/curved_gui/tooltip_text_color' to key `/apps/awn-applet-stacks/curved_gui/tooltip_text_color' WARNING: failed to install schema `/schemas/apps/awn-applet-stacks/curved_gui/tooltip_text_color', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-stacks/curved_gui/tooltip_text_color', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-stacks/curved_gui/hoverbox_bg_color1' to key `/apps/awn-applet-stacks/curved_gui/hoverbox_bg_color1' WARNING: failed to install schema `/schemas/apps/awn-applet-stacks/curved_gui/hoverbox_bg_color1', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-stacks/curved_gui/hoverbox_bg_color1', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-stacks/curved_gui/hoverbox_bg_color2' to key `/apps/awn-applet-stacks/curved_gui/hoverbox_bg_color2' WARNING: failed to install schema `/schemas/apps/awn-applet-stacks/curved_gui/hoverbox_bg_color2', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-stacks/curved_gui/hoverbox_bg_color2', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-stacks/curved_gui/hoverbox_border_color' to key `/apps/awn-applet-stacks/curved_gui/hoverbox_border_color' WARNING: failed to install schema `/schemas/apps/awn-applet-stacks/curved_gui/hoverbox_border_color', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-stacks/curved_gui/hoverbox_border_color', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-stacks/curved_gui/hoverbox_contains_label' to key `/apps/awn-applet-stacks/curved_gui/hoverbox_contains_label' WARNING: failed to install schema `/schemas/apps/awn-applet-stacks/curved_gui/hoverbox_contains_label', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-stacks/curved_gui/hoverbox_contains_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 /usr/bin/install -c -m 644 stacks.desktop '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c -m 644 stacks_preferences.glade curved_stacks_preferences.glade stacks_backend.py stacks_backend_file.py stacks_backend_folder.py stacks_backend_plugger.py stacks_backend_trasher.py stacks_config.py stacks_glade.py stacks_gui_curved.py stacks_gui_dialog.py stacks_gui_trasher.py stacks_icons.py stacks_launcher.py stacks_vfs.py '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/stacks' /usr/bin/install -c stacks_applet.py '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/stacks' /usr/bin/install -c -m 644 icons/stacks-drop.svg icons/stacks-full.svg '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/stacks/icons' /usr/bin/install -c -m 644 awn-applet-stacks.schemas '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/etc/gconf/schemas' /usr/bin/install -c -m 644 awn-applet-stacks.schema-ini '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/schemas' make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/unmaintained/stacks' make[3]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/unmaintained/stacks' Making install in maintained/yama make[3]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/yama' make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/yama' /usr/bin/install -c -m 644 yama.desktop '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c yama.py '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/yama' make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/yama' make[3]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/yama' Making install in maintained/webapplet make[3]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/webapplet' make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/webapplet' /bin/bash /build/buildd/awn-extras-applets-0.4.0/shave/shave-libtool '../../../doltlibtool' --mode=install /usr/bin/install -c webapplet.la '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/lib/awn/applets/webapplet' libtool: install: warning: remember to run `libtool --finish /usr/lib/awn/applets/webapplet' (gconftool-2:16707): GConf-WARNING **: None of the resolved addresses are writable; saving configuration settings will not be possible Attached schema `/schemas/apps/awn-applet-webapplet/URI' to key `/apps/awn-applet-webapplet/URI' WARNING: failed to install schema `/schemas/apps/awn-applet-webapplet/URI', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-webapplet/URI', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-webapplet/HTML_engine' to key `/apps/awn-applet-webapplet/HTML_engine' WARNING: failed to install schema `/schemas/apps/awn-applet-webapplet/HTML_engine', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-webapplet/HTML_engine', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-webapplet/width' to key `/apps/awn-applet-webapplet/width' WARNING: failed to install schema `/schemas/apps/awn-applet-webapplet/width', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-webapplet/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-webapplet/height' to key `/apps/awn-applet-webapplet/height' WARNING: failed to install schema `/schemas/apps/awn-applet-webapplet/height', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-webapplet/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-webapplet/enable_location_dialog' to key `/apps/awn-applet-webapplet/enable_location_dialog' WARNING: failed to install schema `/schemas/apps/awn-applet-webapplet/enable_location_dialog', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-webapplet/enable_location_dialog', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-webapplet/first_start' to key `/apps/awn-applet-webapplet/first_start' WARNING: failed to install schema `/schemas/apps/awn-applet-webapplet/first_start', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-webapplet/first_start', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/awn-applet-webapplet/site' to key `/apps/awn-applet-webapplet/site' WARNING: failed to install schema `/schemas/apps/awn-applet-webapplet/site', locale `C': Unable to store a value at key '/schemas/apps/awn-applet-webapplet/site', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf /usr/bin/install -c -m 644 webapplet.desktop '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c -m 644 webapplet-websites.ini '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/webapplet' /usr/bin/install -c -m 644 icons/brightkite-22.png icons/brightkite.svg icons/digg-22.png icons/digg.svg icons/facebook-22.png icons/facebook.svg icons/friendfeed-22.png icons/friendfeed.svg icons/meebo-48.png icons/pandora-48.png icons/pingfm-22.png icons/pingfm.svg icons/rtm.png icons/twitter-22.png icons/twitter.svg '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/applets/webapplet/icons' /usr/bin/install -c -m 644 awn-applet-webapplet.schemas '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/etc/gconf/schemas' /usr/bin/install -c -m 644 awn-applet-webapplet.schema-ini '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/avant-window-navigator/schemas' make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/webapplet' make[3]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets/maintained/webapplet' make[3]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/applets' make[3]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets' make[2]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/applets' Making install in shared/python make[2]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/shared/python' make[3]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/shared/python' /usr/bin/install -c -m 644 __init__.py awnlib.py awnmediaplayers.py configbinder.py threadqueue.py '/build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/lib/python2.6/dist-packages/awn/extras' Byte-compiling python modules... __init__.py awnlib.py awnmediaplayers.py configbinder.py threadqueue.py Byte-compiling python modules (optimized versions) ... __init__.py awnlib.py awnmediaplayers.py configbinder.py threadqueue.py make[3]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/shared/python' make[2]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/shared/python' Making install in shared/vala make[2]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/shared/vala' make[2]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/shared/vala' Making install in po make[2]: Entering directory `/build/buildd/awn-extras-applets-0.4.0/po' installing af.gmo as /build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/locale/af/LC_MESSAGES/awn-extras.mo installing ar.gmo as /build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/locale/ar/LC_MESSAGES/awn-extras.mo installing ast.gmo as /build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/locale/ast/LC_MESSAGES/awn-extras.mo installing bg.gmo as /build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/locale/bg/LC_MESSAGES/awn-extras.mo installing ca.gmo as /build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/locale/ca/LC_MESSAGES/awn-extras.mo installing cs.gmo as /build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/locale/cs/LC_MESSAGES/awn-extras.mo installing csb.gmo as /build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/locale/csb/LC_MESSAGES/awn-extras.mo installing da.gmo as /build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/locale/da/LC_MESSAGES/awn-extras.mo installing de.gmo as /build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/locale/de/LC_MESSAGES/awn-extras.mo installing en_CA.gmo as /build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/locale/en_CA/LC_MESSAGES/awn-extras.mo installing en_GB.gmo as /build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/locale/en_GB/LC_MESSAGES/awn-extras.mo installing en_US@piglatin.gmo as /build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/locale/en_US@piglatin/LC_MESSAGES/awn-extras.mo installing es.gmo as /build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/locale/es/LC_MESSAGES/awn-extras.mo installing eu.gmo as /build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/locale/eu/LC_MESSAGES/awn-extras.mo installing fi.gmo as /build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/locale/fi/LC_MESSAGES/awn-extras.mo installing fr.gmo as /build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/locale/fr/LC_MESSAGES/awn-extras.mo installing he.gmo as /build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/locale/he/LC_MESSAGES/awn-extras.mo installing hu.gmo as /build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/locale/hu/LC_MESSAGES/awn-extras.mo installing id.gmo as /build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/locale/id/LC_MESSAGES/awn-extras.mo installing it.gmo as /build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/locale/it/LC_MESSAGES/awn-extras.mo installing ja.gmo as /build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/locale/ja/LC_MESSAGES/awn-extras.mo installing ko.gmo as /build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/locale/ko/LC_MESSAGES/awn-extras.mo installing lt.gmo as /build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/locale/lt/LC_MESSAGES/awn-extras.mo installing ms.gmo as /build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/locale/ms/LC_MESSAGES/awn-extras.mo installing nb.gmo as /build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/locale/nb/LC_MESSAGES/awn-extras.mo installing nl.gmo as /build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/locale/nl/LC_MESSAGES/awn-extras.mo installing nn.gmo as /build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/locale/nn/LC_MESSAGES/awn-extras.mo installing pl.gmo as /build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/locale/pl/LC_MESSAGES/awn-extras.mo installing pt.gmo as /build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/locale/pt/LC_MESSAGES/awn-extras.mo installing pt_BR.gmo as /build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/locale/pt_BR/LC_MESSAGES/awn-extras.mo installing ru.gmo as /build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/locale/ru/LC_MESSAGES/awn-extras.mo installing sk.gmo as /build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/locale/sk/LC_MESSAGES/awn-extras.mo installing sv.gmo as /build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/locale/sv/LC_MESSAGES/awn-extras.mo installing sv_SE.gmo as /build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/locale/sv_SE/LC_MESSAGES/awn-extras.mo installing th.gmo as /build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/locale/th/LC_MESSAGES/awn-extras.mo installing tr.gmo as /build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/locale/tr/LC_MESSAGES/awn-extras.mo installing uk.gmo as /build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/locale/uk/LC_MESSAGES/awn-extras.mo installing vi.gmo as /build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/locale/vi/LC_MESSAGES/awn-extras.mo installing zh_CN.gmo as /build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/locale/zh_CN/LC_MESSAGES/awn-extras.mo installing zh_TW.gmo as /build/buildd/awn-extras-applets-0.4.0/debian/tmp/usr/share/locale/zh_TW/LC_MESSAGES/awn-extras.mo make[2]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0/po' make[2]: Entering directory `/build/buildd/awn-extras-applets-0.4.0' make[3]: Entering directory `/build/buildd/awn-extras-applets-0.4.0' make[4]: Entering directory `/build/buildd/awn-extras-applets-0.4.0' *** Icon cache not updated. After install, run this: *** gtk-update-icon-cache -f -t /usr/share/icons/hicolor make[4]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0' make[3]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0' make[2]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0' make[1]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0' dh_install dh_installdocs dh_installchangelogs dh_installexamples dh_installman dh_installcatalogs dh_installcron dh_installdebconf dh_installcatalogs dh_installemacsen dh_installifupdown dh_installinfo dh_installinit dh_installmenu dh_installmime dh_installmodules dh_installlogcheck dh_installlogrotate dh_installpam dh_installppp dh_installudev dh_installwm dh_installxfonts dh_lintian dh_desktop dh_gconf dh_icons dh_perl dh_pysupport dh_scrollkeeper dh_usrlocal dh_link dh_compress dh_fixperms touch install-stamp dh binary-arch --before strip dh_strip --dbg-package=awn-applets-c-dbg dh_strip debug symbol extraction: disabling for PPA build dh_strip debug symbol extraction: not doing anything since NO_PKG_MANGLE is given dh_makeshlibs -a -n --exclude=* dh binary-arch --after makeshlibs dh_shlibdeps -a dpkg-shlibdeps: warning: symbol XUngrabKey used by debian/awn-applets-c-core/usr/lib/awn/applets/awnterm/awnterm.so found in none of the libraries. dpkg-shlibdeps: warning: symbol XGrabKey used by debian/awn-applets-c-core/usr/lib/awn/applets/awnterm/awnterm.so found in none of the libraries. dpkg-shlibdeps: warning: symbol XKeysymToKeycode used by debian/awn-applets-c-core/usr/lib/awn/applets/awnterm/awnterm.so found in none of the libraries. dpkg-shlibdeps: warning: symbol XGetModifierMapping used by debian/awn-applets-c-core/usr/lib/awn/applets/awnterm/awnterm.so found in none of the libraries. dpkg-shlibdeps: warning: symbol XFreeModifiermap used by debian/awn-applets-c-core/usr/lib/awn/applets/awnterm/awnterm.so found in none of the libraries. dpkg-shlibdeps: warning: symbol gtk_widget_get_sensitive used by debian/awn-applets-c-core/usr/lib/awn/applets/garbage/garbage.so found in none of the libraries. dpkg-shlibdeps: warning: dependency on libz.so.1 could be avoided if "debian/awn-applets-c-core/usr/lib/awn/applets/places/places.so debian/awn-applets-c-core/usr/lib/awn/applets/shinyswitcher/shinyswitcher.so debian/awn-applets-c-core/usr/lib/awn/applets/cairo-menu/cairo-menu.so debian/awn-applets-c-core/usr/lib/awn/applets/cairo-menu/gnome-menu-builder.so debian/awn-applets-c-core/usr/lib/awn/applets/awnterm/awnterm.so debian/awn-applets-c-core/usr/lib/awn/applets/garbage/garbage.so debian/awn-applets-c-core/usr/lib/awn/applets/showdesktop/showdesktop.so debian/awn-applets-c-core/usr/lib/awn/applets/notification-area/notification-area.so debian/awn-applets-c-core/usr/lib/awn/applets/sysmon/sysmon.so debian/awn-applets-c-core/usr/lib/awn/applets/notification-daemon/notification-daemon.so" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libfontconfig.so.1 could be avoided if "debian/awn-applets-c-core/usr/lib/awn/applets/places/places.so debian/awn-applets-c-core/usr/lib/awn/applets/shinyswitcher/shinyswitcher.so debian/awn-applets-c-core/usr/lib/awn/applets/cairo-menu/cairo-menu.so debian/awn-applets-c-core/usr/lib/awn/applets/cairo-menu/gnome-menu-builder.so debian/awn-applets-c-core/usr/lib/awn/applets/awnterm/awnterm.so debian/awn-applets-c-core/usr/lib/awn/applets/garbage/garbage.so debian/awn-applets-c-core/usr/lib/awn/applets/showdesktop/showdesktop.so debian/awn-applets-c-core/usr/lib/awn/applets/notification-area/notification-area.so debian/awn-applets-c-core/usr/lib/awn/applets/sysmon/sysmon.so debian/awn-applets-c-core/usr/lib/awn/applets/notification-daemon/notification-daemon.so" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libxml2.so.2 could be avoided if "debian/awn-applets-c-core/usr/lib/awn/applets/notification-daemon/notification-daemon.so" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libXext.so.6 could be avoided if "debian/awn-applets-c-core/usr/lib/awn/applets/notification-daemon/notification-daemon.so" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libdl.so.2 could be avoided if "debian/awn-applets-c-core/usr/lib/awn/applets/notification-daemon/notification-daemon.so" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libpixman-1.so.0 could be avoided if "debian/awn-applets-c-core/usr/lib/awn/applets/cairo-menu/cairo-menu.so debian/awn-applets-c-core/usr/lib/awn/applets/cairo-menu/gnome-menu-builder.so debian/awn-applets-c-core/usr/lib/awn/applets/notification-daemon/notification-daemon.so" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libfreetype.so.6 could be avoided if "debian/awn-applets-c-core/usr/lib/awn/applets/places/places.so debian/awn-applets-c-core/usr/lib/awn/applets/shinyswitcher/shinyswitcher.so debian/awn-applets-c-core/usr/lib/awn/applets/cairo-menu/cairo-menu.so debian/awn-applets-c-core/usr/lib/awn/applets/cairo-menu/gnome-menu-builder.so debian/awn-applets-c-core/usr/lib/awn/applets/awnterm/awnterm.so debian/awn-applets-c-core/usr/lib/awn/applets/garbage/garbage.so debian/awn-applets-c-core/usr/lib/awn/applets/showdesktop/showdesktop.so debian/awn-applets-c-core/usr/lib/awn/applets/notification-area/notification-area.so debian/awn-applets-c-core/usr/lib/awn/applets/sysmon/sysmon.so debian/awn-applets-c-core/usr/lib/awn/applets/notification-daemon/notification-daemon.so" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libgconf-2.so.4 could be avoided if "debian/awn-applets-c-core/usr/lib/awn/applets/notification-daemon/notification-daemon.so" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on librt.so.1 could be avoided if "debian/awn-applets-c-core/usr/lib/awn/applets/places/places.so debian/awn-applets-c-core/usr/lib/awn/applets/shinyswitcher/shinyswitcher.so debian/awn-applets-c-core/usr/lib/awn/applets/cairo-menu/cairo-menu.so debian/awn-applets-c-core/usr/lib/awn/applets/cairo-menu/gnome-menu-builder.so debian/awn-applets-c-core/usr/lib/awn/applets/awnterm/awnterm.so debian/awn-applets-c-core/usr/lib/awn/applets/garbage/garbage.so debian/awn-applets-c-core/usr/lib/awn/applets/showdesktop/showdesktop.so debian/awn-applets-c-core/usr/lib/awn/applets/notification-area/notification-area.so debian/awn-applets-c-core/usr/lib/awn/applets/sysmon/sysmon.so debian/awn-applets-c-core/usr/lib/awn/applets/notification-daemon/notification-daemon.so" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libxcb-render-util.so.0 could be avoided if "debian/awn-applets-c-core/usr/lib/awn/applets/cairo-menu/cairo-menu.so debian/awn-applets-c-core/usr/lib/awn/applets/cairo-menu/gnome-menu-builder.so debian/awn-applets-c-core/usr/lib/awn/applets/notification-daemon/notification-daemon.so" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libXi.so.6 could be avoided if "debian/awn-applets-c-core/usr/lib/awn/applets/notification-daemon/notification-daemon.so" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libxcb-render.so.0 could be avoided if "debian/awn-applets-c-core/usr/lib/awn/applets/cairo-menu/cairo-menu.so debian/awn-applets-c-core/usr/lib/awn/applets/cairo-menu/gnome-menu-builder.so debian/awn-applets-c-core/usr/lib/awn/applets/notification-daemon/notification-daemon.so" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libXinerama.so.1 could be avoided if "debian/awn-applets-c-core/usr/lib/awn/applets/notification-daemon/notification-daemon.so" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libXcursor.so.1 could be avoided if "debian/awn-applets-c-core/usr/lib/awn/applets/notification-daemon/notification-daemon.so" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libxcb.so.1 could be avoided if "debian/awn-applets-c-core/usr/lib/awn/applets/cairo-menu/cairo-menu.so debian/awn-applets-c-core/usr/lib/awn/applets/cairo-menu/gnome-menu-builder.so debian/awn-applets-c-core/usr/lib/awn/applets/notification-daemon/notification-daemon.so" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libpng12.so.0 could be avoided if "debian/awn-applets-c-core/usr/lib/awn/applets/cairo-menu/cairo-menu.so debian/awn-applets-c-core/usr/lib/awn/applets/cairo-menu/gnome-menu-builder.so debian/awn-applets-c-core/usr/lib/awn/applets/notification-daemon/notification-daemon.so" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libgthread-2.0.so.0 could be avoided if "debian/awn-applets-c-core/usr/lib/awn/applets/places/places.so debian/awn-applets-c-core/usr/lib/awn/applets/shinyswitcher/shinyswitcher.so debian/awn-applets-c-core/usr/lib/awn/applets/cairo-menu/cairo-menu.so debian/awn-applets-c-core/usr/lib/awn/applets/cairo-menu/gnome-menu-builder.so debian/awn-applets-c-core/usr/lib/awn/applets/awnterm/awnterm.so debian/awn-applets-c-core/usr/lib/awn/applets/garbage/garbage.so debian/awn-applets-c-core/usr/lib/awn/applets/showdesktop/showdesktop.so debian/awn-applets-c-core/usr/lib/awn/applets/notification-area/notification-area.so debian/awn-applets-c-core/usr/lib/awn/applets/sysmon/sysmon.so debian/awn-applets-c-core/usr/lib/awn/applets/notification-daemon/notification-daemon.so" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libXrandr.so.2 could be avoided if "debian/awn-applets-c-core/usr/lib/awn/applets/notification-daemon/notification-daemon.so" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libpangoft2-1.0.so.0 could be avoided if "debian/awn-applets-c-core/usr/lib/awn/applets/places/places.so debian/awn-applets-c-core/usr/lib/awn/applets/shinyswitcher/shinyswitcher.so debian/awn-applets-c-core/usr/lib/awn/applets/cairo-menu/cairo-menu.so debian/awn-applets-c-core/usr/lib/awn/applets/cairo-menu/gnome-menu-builder.so debian/awn-applets-c-core/usr/lib/awn/applets/awnterm/awnterm.so debian/awn-applets-c-core/usr/lib/awn/applets/garbage/garbage.so debian/awn-applets-c-core/usr/lib/awn/applets/showdesktop/showdesktop.so debian/awn-applets-c-core/usr/lib/awn/applets/notification-area/notification-area.so debian/awn-applets-c-core/usr/lib/awn/applets/sysmon/sysmon.so debian/awn-applets-c-core/usr/lib/awn/applets/notification-daemon/notification-daemon.so" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libdbus-1.so.3 could be avoided if "debian/awn-applets-c-extras/usr/lib/awn/applets/awnsystemmonitor/awnsystemmonitor.so debian/awn-applets-c-extras/usr/lib/awn/applets/digital-clock/digital-clock.so debian/awn-applets-c-extras/usr/lib/awn/applets/main-menu/main-menu.so debian/awn-applets-c-extras/usr/lib/awn/applets/webapplet/webapplet.so" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libz.so.1 could be avoided if "debian/awn-applets-c-extras/usr/lib/awn/applets/awnsystemmonitor/awnsystemmonitor.so debian/awn-applets-c-extras/usr/lib/awn/applets/digital-clock/digital-clock.so debian/awn-applets-c-extras/usr/lib/awn/applets/main-menu/main-menu.so debian/awn-applets-c-extras/usr/lib/awn/applets/webapplet/webapplet.so" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libdesktop-agnostic.so.0 could be avoided if "debian/awn-applets-c-extras/usr/lib/awn/applets/awnsystemmonitor/awnsystemmonitor.so debian/awn-applets-c-extras/usr/lib/awn/applets/digital-clock/digital-clock.so debian/awn-applets-c-extras/usr/lib/awn/applets/main-menu/main-menu.so debian/awn-applets-c-extras/usr/lib/awn/applets/webapplet/webapplet.so" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libfontconfig.so.1 could be avoided if "debian/awn-applets-c-extras/usr/lib/awn/applets/awnsystemmonitor/awnsystemmonitor.so debian/awn-applets-c-extras/usr/lib/awn/applets/digital-clock/digital-clock.so debian/awn-applets-c-extras/usr/lib/awn/applets/main-menu/main-menu.so debian/awn-applets-c-extras/usr/lib/awn/applets/webapplet/webapplet.so" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libatk-1.0.so.0 could be avoided if "debian/awn-applets-c-extras/usr/lib/awn/applets/awnsystemmonitor/awnsystemmonitor.so debian/awn-applets-c-extras/usr/lib/awn/applets/digital-clock/digital-clock.so debian/awn-applets-c-extras/usr/lib/awn/applets/main-menu/main-menu.so debian/awn-applets-c-extras/usr/lib/awn/applets/webapplet/webapplet.so" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libdesktop-agnostic-ui.so.0 could be avoided if "debian/awn-applets-c-extras/usr/lib/awn/applets/awnsystemmonitor/awnsystemmonitor.so debian/awn-applets-c-extras/usr/lib/awn/applets/digital-clock/digital-clock.so debian/awn-applets-c-extras/usr/lib/awn/applets/main-menu/main-menu.so debian/awn-applets-c-extras/usr/lib/awn/applets/webapplet/webapplet.so" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on librt.so.1 could be avoided if "debian/awn-applets-c-extras/usr/lib/awn/applets/awnsystemmonitor/awnsystemmonitor.so debian/awn-applets-c-extras/usr/lib/awn/applets/digital-clock/digital-clock.so debian/awn-applets-c-extras/usr/lib/awn/applets/main-menu/main-menu.so debian/awn-applets-c-extras/usr/lib/awn/applets/webapplet/webapplet.so" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libpthread.so.0 could be avoided if "debian/awn-applets-c-extras/usr/lib/awn/applets/awnsystemmonitor/awnsystemmonitor.so debian/awn-applets-c-extras/usr/lib/awn/applets/digital-clock/digital-clock.so debian/awn-applets-c-extras/usr/lib/awn/applets/main-menu/main-menu.so debian/awn-applets-c-extras/usr/lib/awn/applets/webapplet/webapplet.so" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libgio-2.0.so.0 could be avoided if "debian/awn-applets-c-extras/usr/lib/awn/applets/awnsystemmonitor/awnsystemmonitor.so debian/awn-applets-c-extras/usr/lib/awn/applets/digital-clock/digital-clock.so debian/awn-applets-c-extras/usr/lib/awn/applets/main-menu/main-menu.so debian/awn-applets-c-extras/usr/lib/awn/applets/webapplet/webapplet.so" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libgmodule-2.0.so.0 could be avoided if "debian/awn-applets-c-extras/usr/lib/awn/applets/awnsystemmonitor/awnsystemmonitor.so debian/awn-applets-c-extras/usr/lib/awn/applets/digital-clock/digital-clock.so debian/awn-applets-c-extras/usr/lib/awn/applets/main-menu/main-menu.so debian/awn-applets-c-extras/usr/lib/awn/applets/webapplet/webapplet.so" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libpango-1.0.so.0 could be avoided if "debian/awn-applets-c-extras/usr/lib/awn/applets/awnsystemmonitor/awnsystemmonitor.so debian/awn-applets-c-extras/usr/lib/awn/applets/digital-clock/digital-clock.so debian/awn-applets-c-extras/usr/lib/awn/applets/main-menu/main-menu.so debian/awn-applets-c-extras/usr/lib/awn/applets/webapplet/webapplet.so" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libgthread-2.0.so.0 could be avoided if "debian/awn-applets-c-extras/usr/lib/awn/applets/awnsystemmonitor/awnsystemmonitor.so debian/awn-applets-c-extras/usr/lib/awn/applets/digital-clock/digital-clock.so debian/awn-applets-c-extras/usr/lib/awn/applets/main-menu/main-menu.so debian/awn-applets-c-extras/usr/lib/awn/applets/webapplet/webapplet.so" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libdbus-glib-1.so.2 could be avoided if "debian/awn-applets-c-extras/usr/lib/awn/applets/awnsystemmonitor/awnsystemmonitor.so debian/awn-applets-c-extras/usr/lib/awn/applets/digital-clock/digital-clock.so debian/awn-applets-c-extras/usr/lib/awn/applets/main-menu/main-menu.so debian/awn-applets-c-extras/usr/lib/awn/applets/webapplet/webapplet.so" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libpangocairo-1.0.so.0 could be avoided if "debian/awn-applets-c-extras/usr/lib/awn/applets/awnsystemmonitor/awnsystemmonitor.so debian/awn-applets-c-extras/usr/lib/awn/applets/digital-clock/digital-clock.so debian/awn-applets-c-extras/usr/lib/awn/applets/main-menu/main-menu.so debian/awn-applets-c-extras/usr/lib/awn/applets/webapplet/webapplet.so" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libfreetype.so.6 could be avoided if "debian/awn-applets-c-extras/usr/lib/awn/applets/awnsystemmonitor/awnsystemmonitor.so debian/awn-applets-c-extras/usr/lib/awn/applets/digital-clock/digital-clock.so debian/awn-applets-c-extras/usr/lib/awn/applets/main-menu/main-menu.so debian/awn-applets-c-extras/usr/lib/awn/applets/webapplet/webapplet.so" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libpangoft2-1.0.so.0 could be avoided if "debian/awn-applets-c-extras/usr/lib/awn/applets/awnsystemmonitor/awnsystemmonitor.so debian/awn-applets-c-extras/usr/lib/awn/applets/digital-clock/digital-clock.so debian/awn-applets-c-extras/usr/lib/awn/applets/main-menu/main-menu.so debian/awn-applets-c-extras/usr/lib/awn/applets/webapplet/webapplet.so" were not uselessly linked against it (they use none of its symbols). dh_installdeb -a dh_gencontrol -a dpkg-gencontrol: warning: unknown substitution variable ${shlibs:Depends} dpkg-gencontrol: warning: unknown substitution variable ${misc:Depends} dpkg-gencontrol: warning: unknown substitution variable ${shlibs:Depends} dpkg-gencontrol: warning: unknown substitution variable ${misc:Depends} dh_md5sums -a dh_builddeb -a INFO: Disabling pkgbinarymangler for PPA build WARNING: not running pkgbinarymangler for this package, as requested warning, `debian/awn-applets-c-core/DEBIAN/control' contains user-defined field `Original-Maintainer' dpkg-deb: ignoring 1 warnings about the control file(s) dpkg-deb: building package `awn-applets-c-core' in `../awn-applets-c-core_0.4.0-0ubuntu1~ppa4_amd64.deb'. INFO: Disabling pkgbinarymangler for PPA build WARNING: not running pkgbinarymangler for this package, as requested warning, `debian/awn-applets-c-extras/DEBIAN/control' contains user-defined field `Original-Maintainer' dpkg-deb: ignoring 1 warnings about the control file(s) dpkg-deb: building package `awn-applets-c-extras' in `../awn-applets-c-extras_0.4.0-0ubuntu1~ppa4_amd64.deb'. INFO: Disabling pkgbinarymangler for PPA build WARNING: not running pkgbinarymangler for this package, as requested warning, `debian/python-awn-extras/DEBIAN/control' contains user-defined field `Original-Maintainer' dpkg-deb: ignoring 1 warnings about the control file(s) dpkg-deb: building package `python-awn-extras' in `../python-awn-extras_0.4.0-0ubuntu1~ppa4_amd64.deb'. INFO: Disabling pkgbinarymangler for PPA build WARNING: not running pkgbinarymangler for this package, as requested warning, `debian/awn-applets-c-dbg/DEBIAN/control' contains user-defined field `Original-Maintainer' dpkg-deb: ignoring 1 warnings about the control file(s) dpkg-deb: building package `awn-applets-c-dbg' in `../awn-applets-c-dbg_0.4.0-0ubuntu1~ppa4_amd64.deb'. dpkg-genchanges -B -mUbuntu/amd64 Build Daemon >../awn-extras-applets_0.4.0-0ubuntu1~ppa4_amd64.changes dpkg-genchanges: arch-specific upload - not including arch-independent packages dpkg-genchanges: warning: the current version (0.4.0-0ubuntu1~ppa4) is smaller than the previous one (0.4.0-0ubuntu1) dpkg-genchanges: binary-only upload - not including any source code dpkg-buildpackage: binary only upload (no source included) ****************************************************************************** Build finished at 20100417-0934 chroot-autobuild/build/buildd/awn-applets-c-core_0.4.0-0ubuntu1~ppa4_amd64.deb: new debian package, version 2.0. size 229628 bytes: control archive= 3288 bytes. 2366 bytes, 32 lines control 3891 bytes, 42 lines md5sums 1063 bytes, 23 lines * postinst #!/bin/sh 715 bytes, 19 lines * postrm #!/bin/sh 475 bytes, 13 lines * preinst #!/bin/sh 411 bytes, 7 lines * prerm #!/bin/sh Package: awn-applets-c-core Source: awn-extras-applets Version: 0.4.0-0ubuntu1~ppa4 Architecture: amd64 Maintainer: Ubuntu Developers Installed-Size: 956 Depends: libatk1.0-0 (>= 1.20.0), libawn1 (>= 0.3.9~bzr1890), libc6 (>= 2.4), libcairo2 (>= 1.4.10), libdbus-1-3 (>= 1.0.2), libdbus-glib-1-2 (>= 0.78), libdesktop-agnostic0, libfontconfig1 (>= 2.4.0), libfreetype6 (>= 2.2.1), libgconf2-4 (>= 2.13.5), libglib2.0-0 (>= 2.18.0), libgnome-menu2 (>= 2.15.4), libgtk2.0-0 (>= 2.16.0), libgtop2-7 (>= 2.20.0), libnotify1 (>= 0.4.4), libnotify1-gtk2.10, libpango1.0-0 (>= 1.14.0), libpixman-1-0, libpng12-0 (>= 1.2.13-4), libsexy2 (>= 0.1.8), libvte9 (>= 1:0.19.1), libwnck22 (>= 2.22.0), libx11-6, libxcb-render-util0 (>= 0.2.1+git1), libxcb-render0, libxcb1 (>= 1.1.92), libxcomposite1 (>= 1:0.3-1), libxcursor1 (>> 1.1.2), libxext6, libxfixes3 (>= 1:4.0.1), libxi6 (>= 2:1.2.0), libxinerama1, libxml2 (>= 2.6.27), libxrandr2 (>= 2:1.2.99.2), libxrender1, zlib1g (>= 1:1.1.4), gconf2 (>= 2.10.1-2), avant-window-navigator Recommends: awn-settings (>= 0.3.9~bzr1890), awn-applets-python-core, xdg-utils Suggests: awn-applets-c-extras, gconf-editor, python-gconf Replaces: awn-applets-python-core Section: gnome Priority: optional Homepage: https://launchpad.net/awn-extras Description: A collection of applets for avant-window-navigator Awn-extras-applets is a collection of applets for avant-window-navigator. It provides some extensions to the bar and some new features (like applets in the gnome-panel). . This package provides the core applets written in C: * awnterm: A pop-up terminal that lives in AWN. * cairo_main_menu: Displays a list of all the applications on your computer in a standard menu format. * notification-area : Replaces the gnome-panel notification area and shows it right on your dock * notification-daemon: Libnotify notification daemon implementation. * shinyswitcher: A workspace switcher supporting compiz and other WMs. * show desktop: Hides/shows all of the windows of the current viewport, similar to the showdesktop icon of gnome-panel. * sysmon: Display CPU activity and system stats on click. * places: Displays shortcuts in buttons. * garbage: A trash applet, like the one from gnome-panel. Original-Maintainer: Julien Lavergne chroot-autobuild/build/buildd/awn-applets-c-extras_0.4.0-0ubuntu1~ppa4_amd64.deb: new debian package, version 2.0. size 127196 bytes: control archive= 2650 bytes. 1492 bytes, 24 lines control 3321 bytes, 34 lines md5sums 919 bytes, 23 lines * postinst #!/bin/sh 557 bytes, 19 lines * postrm #!/bin/sh 485 bytes, 13 lines * preinst #!/bin/sh 253 bytes, 7 lines * prerm #!/bin/sh Package: awn-applets-c-extras Source: awn-extras-applets Version: 0.4.0-0ubuntu1~ppa4 Architecture: amd64 Maintainer: Ubuntu Developers Installed-Size: 564 Depends: libatk1.0-0 (>= 1.20.0), libawn1 (>= 0.3.9~bzr1890), libc6 (>= 2.4), libcairo2 (>= 1.2.4), libdbus-1-3 (>= 1.0.2), libdbus-glib-1-2 (>= 0.78), libdesktop-agnostic0, libfontconfig1 (>= 2.4.0), libfreetype6 (>= 2.2.1), libgconf2-4 (>= 2.13.5), libglib2.0-0 (>= 2.16.0), libgnome-menu2 (>= 2.15.4), libgtk2.0-0 (>= 2.16.0), libgtop2-7 (>= 2.20.0), libpango1.0-0 (>= 1.14.0), libwebkit-1.0-1 (>= 0~svn31841), zlib1g (>= 1:1.1.4), gconf2 (>= 2.10.1-2), avant-window-navigator Recommends: awn-settings (>= 0.3.9~bzr1890) Conflicts: awn-applets-python-extras (<< 0.4.0~rc1) Replaces: awn-applets-python-extras (<< 0.4.0~rc1) Section: gnome Priority: optional Homepage: https://launchpad.net/awn-extras Description: A collection of applets for avant-window-navigator Awn-extras-applets is a collection of applets for avant-window-navigator. It provides some extensions to the bar and some new features (like applets in the gnome-panel). . This package contains extras applets written in C: * awn-system-monitor: Display CPU activity and system stats on click. * digitalClock: A digital clock and calendar applet. * main-menu: Display a list of all the applications on your computer. * webapplet: Displays a web page. Original-Maintainer: Julien Lavergne chroot-autobuild/build/buildd/python-awn-extras_0.4.0-0ubuntu1~ppa4_amd64.deb: new debian package, version 2.0. size 36134 bytes: control archive= 1378 bytes. 881 bytes, 19 lines control 839 bytes, 9 lines md5sums 684 bytes, 18 lines * postinst #!/bin/sh 470 bytes, 13 lines * preinst #!/bin/sh 190 bytes, 7 lines * prerm #!/bin/sh Package: python-awn-extras Source: awn-extras-applets Version: 0.4.0-0ubuntu1~ppa4 Architecture: amd64 Maintainer: Ubuntu Developers Installed-Size: 192 Depends: python (>= 2.4), python-support (>= 0.7.1), python-gtk2, python-cairo, python-gobject, python-desktop-agnostic, python-dbus, python-awn Suggests: python-gnomekeyring | python-gnome2-desktop Conflicts: python-awnlib Replaces: python-awnlib Provides: python2.5-awn-extras, python2.6-awn-extras Section: python Priority: optional Homepage: https://launchpad.net/awn-extras Description: Python utilities for avant-window-navigator's applets These packages provides Python utilities to create and use Python applets. It also include awnlib, a collection of functions to simplify the creation of applets with Python. Original-Maintainer: Julien Lavergne chroot-autobuild/build/buildd/awn-applets-c-dbg_0.4.0-0ubuntu1~ppa4_amd64.deb: new debian package, version 2.0. size 782446 bytes: control archive= 1513 bytes. 726 bytes, 17 lines control 1577 bytes, 17 lines md5sums 514 bytes, 13 lines * postinst #!/bin/sh 470 bytes, 13 lines * preinst #!/bin/sh Package: awn-applets-c-dbg Source: awn-extras-applets Version: 0.4.0-0ubuntu1~ppa4 Architecture: amd64 Maintainer: Ubuntu Developers Installed-Size: 2100 Depends: awn-applets-c-core (= 0.4.0-0ubuntu1~ppa4), awn-applets-c-extras (= 0.4.0-0ubuntu1~ppa4) Section: debug Priority: extra Homepage: https://launchpad.net/awn-extras Description: A collection of applets for avant-window-navigator - debug symbols Awn-applets is a collection of applets for avant-window-navigator. It provides some extensions to the bar and some new features (like applets in the gnome-panel). . This package contains the debugging symbols. Original-Maintainer: Julien Lavergne chroot-autobuild/build/buildd/awn-applets-c-core_0.4.0-0ubuntu1~ppa4_amd64.deb: drwxr-xr-x root/root 0 2010-04-17 09:34 ./ drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/ drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/lib/ drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/lib/awn/ drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/lib/awn/applets/ drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/lib/awn/applets/cairo-menu/ -rw-r--r-- root/root 52712 2010-04-17 09:34 ./usr/lib/awn/applets/cairo-menu/cairo-menu.so -rw-r--r-- root/root 48448 2010-04-17 09:34 ./usr/lib/awn/applets/cairo-menu/gnome-menu-builder.so drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/lib/awn/applets/places/ -rw-r--r-- root/root 44304 2010-04-17 09:34 ./usr/lib/awn/applets/places/places.so drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/lib/awn/applets/awnterm/ -rw-r--r-- root/root 69312 2010-04-17 09:34 ./usr/lib/awn/applets/awnterm/awnterm.so drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/lib/awn/applets/notification-daemon/ -rw-r--r-- root/root 73768 2010-04-17 09:34 ./usr/lib/awn/applets/notification-daemon/notification-daemon.so drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/lib/awn/applets/sysmon/ -rw-r--r-- root/root 56448 2010-04-17 09:34 ./usr/lib/awn/applets/sysmon/sysmon.so drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/lib/awn/applets/showdesktop/ -rw-r--r-- root/root 14624 2010-04-17 09:34 ./usr/lib/awn/applets/showdesktop/showdesktop.so drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/lib/awn/applets/notification-area/ -rw-r--r-- root/root 65184 2010-04-17 09:34 ./usr/lib/awn/applets/notification-area/notification-area.so drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/lib/awn/applets/shinyswitcher/ -rw-r--r-- root/root 56608 2010-04-17 09:34 ./usr/lib/awn/applets/shinyswitcher/shinyswitcher.so drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/lib/awn/applets/garbage/ -rw-r--r-- root/root 31448 2010-04-17 09:34 ./usr/lib/awn/applets/garbage/garbage.so drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/share/ drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/share/icons/ drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/share/icons/hicolor/ drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/share/icons/hicolor/scalable/ drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/share/icons/hicolor/scalable/apps/ -rw-r--r-- root/root 23904 2010-04-17 09:34 ./usr/share/icons/hicolor/scalable/apps/notification-area.svg drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/share/avant-window-navigator/ drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/share/avant-window-navigator/schemas/ -rw-r--r-- root/root 1446 2010-04-17 09:34 ./usr/share/avant-window-navigator/schemas/awn-applet-awnterm.schema-ini -rw-r--r-- root/root 395 2010-04-17 09:34 ./usr/share/avant-window-navigator/schemas/awn-applet-garbage.schema-ini -rw-r--r-- root/root 1146 2010-04-17 09:34 ./usr/share/avant-window-navigator/schemas/awn-applet-sysmon.schema-ini -rw-r--r-- root/root 3088 2010-04-17 09:34 ./usr/share/avant-window-navigator/schemas/awn-applet-shinyswitcher.schema-ini -rw-r--r-- root/root 689 2010-04-17 09:34 ./usr/share/avant-window-navigator/schemas/awn-applet-notification-area.schema-ini -rw-r--r-- root/root 2723 2010-04-17 09:34 ./usr/share/avant-window-navigator/schemas/awn-applet-notification-daemon.schema-ini -rw-r--r-- root/root 1774 2010-04-17 09:34 ./usr/share/avant-window-navigator/schemas/awn-applet-cairo-menu.schema-ini -rw-r--r-- root/root 2464 2010-04-17 09:34 ./usr/share/avant-window-navigator/schemas/awn-applet-places.schema-ini drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/share/avant-window-navigator/applets/ -rw-r--r-- root/root 580 2010-04-17 09:34 ./usr/share/avant-window-navigator/applets/places.desktop -rw-r--r-- root/root 247 2010-04-17 09:34 ./usr/share/avant-window-navigator/applets/cairo-menu.desktop -rw-r--r-- root/root 379 2010-04-17 09:34 ./usr/share/avant-window-navigator/applets/notification-daemon.desktop -rw-r--r-- root/root 395 2010-04-17 09:34 ./usr/share/avant-window-navigator/applets/showdesktop.desktop -rw-r--r-- root/root 481 2010-04-17 09:34 ./usr/share/avant-window-navigator/applets/garbage.desktop -rw-r--r-- root/root 496 2010-04-17 09:34 ./usr/share/avant-window-navigator/applets/awnterm.desktop drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/share/avant-window-navigator/applets/notification-area/ -rw-r--r-- root/root 22864 2010-04-17 09:34 ./usr/share/avant-window-navigator/applets/notification-area/na-prefs.ui -rw-r--r-- root/root 292 2010-04-17 09:34 ./usr/share/avant-window-navigator/applets/notification-area.desktop drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/share/avant-window-navigator/applets/shinyswitcher/ -rw-r--r-- root/root 69108 2010-04-17 09:34 ./usr/share/avant-window-navigator/applets/shinyswitcher/shiny-prefs.ui -rw-r--r-- root/root 3117 2010-04-17 09:34 ./usr/share/avant-window-navigator/applets/shinyswitcher/shiny-prefs.py -rw-r--r-- root/root 321 2010-04-17 09:34 ./usr/share/avant-window-navigator/applets/sysmon.desktop -rw-r--r-- root/root 282 2010-04-17 09:34 ./usr/share/avant-window-navigator/applets/shinyswitcher.desktop drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/share/gconf/ drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/share/gconf/schemas/ -rw-r--r-- root/root 7958 2010-04-17 09:34 ./usr/share/gconf/schemas/awn-applet-cairo-menu.schemas -rw-r--r-- root/root 1868 2010-04-17 09:34 ./usr/share/gconf/schemas/awn-applet-awnterm.schemas -rw-r--r-- root/root 2078 2010-04-17 09:34 ./usr/share/gconf/schemas/awn-applet-notification-area.schemas -rw-r--r-- root/root 4892 2010-04-17 09:34 ./usr/share/gconf/schemas/awn-applet-places.schemas -rw-r--r-- root/root 7296 2010-04-17 09:34 ./usr/share/gconf/schemas/awn-applet-notification-daemon.schemas -rw-r--r-- root/root 8217 2010-04-17 09:34 ./usr/share/gconf/schemas/awn-applet-shinyswitcher.schemas -rw-r--r-- root/root 851 2010-04-17 09:34 ./usr/share/gconf/schemas/awn-applet-garbage.schemas -rw-r--r-- root/root 3397 2010-04-17 09:34 ./usr/share/gconf/schemas/awn-applet-sysmon.schemas drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/share/doc/ drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/share/doc/awn-applets-c-core/ -rw-r--r-- root/root 380 2009-08-14 12:07 ./usr/share/doc/awn-applets-c-core/changelog.gz -rw-r--r-- root/root 29449 2010-04-17 09:32 ./usr/share/doc/awn-applets-c-core/copyright -rw-r--r-- root/root 4247 2010-04-17 09:32 ./usr/share/doc/awn-applets-c-core/changelog.Debian.gz chroot-autobuild/build/buildd/awn-applets-c-extras_0.4.0-0ubuntu1~ppa4_amd64.deb: drwxr-xr-x root/root 0 2010-04-17 09:34 ./ drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/ drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/lib/ drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/lib/awn/ drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/lib/awn/applets/ drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/lib/awn/applets/digital-clock/ -rw-r--r-- root/root 39632 2010-04-17 09:34 ./usr/lib/awn/applets/digital-clock/digital-clock.so drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/lib/awn/applets/main-menu/ -rw-r--r-- root/root 19024 2010-04-17 09:34 ./usr/lib/awn/applets/main-menu/main-menu.so drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/lib/awn/applets/awnsystemmonitor/ -rw-r--r-- root/root 110144 2010-04-17 09:34 ./usr/lib/awn/applets/awnsystemmonitor/awnsystemmonitor.so drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/lib/awn/applets/webapplet/ -rw-r--r-- root/root 23104 2010-04-17 09:34 ./usr/lib/awn/applets/webapplet/webapplet.so drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/share/ drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/share/icons/ drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/share/icons/hicolor/ drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/share/icons/hicolor/scalable/ drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/share/icons/hicolor/scalable/apps/ -rw-r--r-- root/root 16187 2010-04-17 09:34 ./usr/share/icons/hicolor/scalable/apps/awn-applet-digital-clock.svg drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/share/avant-window-navigator/ drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/share/avant-window-navigator/schemas/ -rw-r--r-- root/root 745 2010-04-17 09:34 ./usr/share/avant-window-navigator/schemas/awn-applet-webapplet.schema-ini -rw-r--r-- root/root 1743 2010-04-17 09:34 ./usr/share/avant-window-navigator/schemas/awn-applet-digital-clock.schema-ini drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/share/avant-window-navigator/applets/ -rw-r--r-- root/root 320 2010-04-17 09:34 ./usr/share/avant-window-navigator/applets/main-menu.desktop drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/share/avant-window-navigator/applets/digital-clock/ -rw-r--r-- root/root 13616 2010-04-17 09:34 ./usr/share/avant-window-navigator/applets/digital-clock/dg-prefs.ui -rw-r--r-- root/root 224 2010-04-17 09:34 ./usr/share/avant-window-navigator/applets/webapplet.desktop -rw-r--r-- root/root 524 2010-04-17 09:34 ./usr/share/avant-window-navigator/applets/digital-clock.desktop -rw-r--r-- root/root 395 2010-04-17 09:34 ./usr/share/avant-window-navigator/applets/awnsystemmonitor.desktop drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/share/avant-window-navigator/applets/webapplet/ drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/share/avant-window-navigator/applets/webapplet/icons/ -rw-r--r-- root/root 1253 2010-04-17 09:34 ./usr/share/avant-window-navigator/applets/webapplet/icons/brightkite-22.png -rw-r--r-- root/root 18625 2010-04-17 09:34 ./usr/share/avant-window-navigator/applets/webapplet/icons/digg.svg -rw-r--r-- root/root 731 2010-04-17 09:34 ./usr/share/avant-window-navigator/applets/webapplet/icons/facebook-22.png -rw-r--r-- root/root 8215 2010-04-17 09:34 ./usr/share/avant-window-navigator/applets/webapplet/icons/facebook.svg -rw-r--r-- root/root 11136 2010-04-17 09:34 ./usr/share/avant-window-navigator/applets/webapplet/icons/pingfm.svg -rw-r--r-- root/root 673 2010-04-17 09:34 ./usr/share/avant-window-navigator/applets/webapplet/icons/pingfm-22.png -rw-r--r-- root/root 1208 2010-04-17 09:34 ./usr/share/avant-window-navigator/applets/webapplet/icons/friendfeed-22.png -rw-r--r-- root/root 9259 2010-04-17 09:34 ./usr/share/avant-window-navigator/applets/webapplet/icons/twitter.svg -rw-r--r-- root/root 2600 2010-04-17 09:34 ./usr/share/avant-window-navigator/applets/webapplet/icons/rtm.png -rw-r--r-- root/root 23894 2010-04-17 09:34 ./usr/share/avant-window-navigator/applets/webapplet/icons/brightkite.svg -rw-r--r-- root/root 1879 2010-04-17 09:34 ./usr/share/avant-window-navigator/applets/webapplet/icons/pandora-48.png -rw-r--r-- root/root 1105 2010-04-17 09:34 ./usr/share/avant-window-navigator/applets/webapplet/icons/digg-22.png -rw-r--r-- root/root 924 2010-04-17 09:34 ./usr/share/avant-window-navigator/applets/webapplet/icons/twitter-22.png -rw-r--r-- root/root 1368 2010-04-17 09:34 ./usr/share/avant-window-navigator/applets/webapplet/icons/meebo-48.png -rw-r--r-- root/root 16779 2010-04-17 09:34 ./usr/share/avant-window-navigator/applets/webapplet/icons/friendfeed.svg -rw-r--r-- root/root 1201 2010-04-17 09:34 ./usr/share/avant-window-navigator/applets/webapplet/webapplet-websites.ini drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/share/gconf/ drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/share/gconf/schemas/ -rw-r--r-- root/root 2533 2010-04-17 09:34 ./usr/share/gconf/schemas/awn-applet-webapplet.schemas -rw-r--r-- root/root 2163 2010-04-17 09:34 ./usr/share/gconf/schemas/awnsystemmonitor.schemas -rw-r--r-- root/root 3119 2010-04-17 09:34 ./usr/share/gconf/schemas/awn-applet-digital-clock.schemas drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/share/doc/ drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/share/doc/awn-applets-c-extras/ -rw-r--r-- root/root 380 2009-08-14 12:07 ./usr/share/doc/awn-applets-c-extras/changelog.gz -rw-r--r-- root/root 29449 2010-04-17 09:32 ./usr/share/doc/awn-applets-c-extras/copyright -rw-r--r-- root/root 4247 2010-04-17 09:32 ./usr/share/doc/awn-applets-c-extras/changelog.Debian.gz chroot-autobuild/build/buildd/python-awn-extras_0.4.0-0ubuntu1~ppa4_amd64.deb: drwxr-xr-x root/root 0 2010-04-17 09:34 ./ drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/ drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/share/ drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/share/python-support/ drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/share/python-support/python-awn-extras/ drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/share/python-support/python-awn-extras/awn/ drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/share/python-support/python-awn-extras/awn/extras/ -rw-r--r-- root/root 47971 2010-04-17 09:34 ./usr/share/python-support/python-awn-extras/awn/extras/awnlib.py -rw-r--r-- root/root 1258 2010-04-17 09:34 ./usr/share/python-support/python-awn-extras/awn/extras/__init__.py -rw-r--r-- root/root 10137 2010-04-17 09:34 ./usr/share/python-support/python-awn-extras/awn/extras/configbinder.py -rw-r--r-- root/root 3329 2010-04-17 09:34 ./usr/share/python-support/python-awn-extras/awn/extras/threadqueue.py -rw-r--r-- root/root 21519 2010-04-17 09:34 ./usr/share/python-support/python-awn-extras/awn/extras/awnmediaplayers.py -rw-r--r-- root/root 5 2010-04-17 09:32 ./usr/share/python-support/python-awn-extras/.version drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/share/doc/ drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/share/doc/python-awn-extras/ -rw-r--r-- root/root 380 2009-08-14 12:07 ./usr/share/doc/python-awn-extras/changelog.gz -rw-r--r-- root/root 29449 2010-04-17 09:32 ./usr/share/doc/python-awn-extras/copyright -rw-r--r-- root/root 4247 2010-04-17 09:32 ./usr/share/doc/python-awn-extras/changelog.Debian.gz chroot-autobuild/build/buildd/awn-applets-c-dbg_0.4.0-0ubuntu1~ppa4_amd64.deb: drwxr-xr-x root/root 0 2010-04-17 09:34 ./ drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/ drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/lib/ drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/lib/debug/ drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/lib/debug/usr/ drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/lib/debug/usr/lib/ drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/lib/debug/usr/lib/awn/ drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/lib/debug/usr/lib/awn/applets/ drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/lib/debug/usr/lib/awn/applets/cairo-menu/ -rw-r--r-- root/root 202963 2010-04-17 09:34 ./usr/lib/debug/usr/lib/awn/applets/cairo-menu/cairo-menu.so -rw-r--r-- root/root 132826 2010-04-17 09:34 ./usr/lib/debug/usr/lib/awn/applets/cairo-menu/gnome-menu-builder.so drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/lib/debug/usr/lib/awn/applets/places/ -rw-r--r-- root/root 66468 2010-04-17 09:34 ./usr/lib/debug/usr/lib/awn/applets/places/places.so drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/lib/debug/usr/lib/awn/applets/digital-clock/ -rw-r--r-- root/root 110469 2010-04-17 09:34 ./usr/lib/debug/usr/lib/awn/applets/digital-clock/digital-clock.so drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/lib/debug/usr/lib/awn/applets/awnterm/ -rw-r--r-- root/root 171947 2010-04-17 09:34 ./usr/lib/debug/usr/lib/awn/applets/awnterm/awnterm.so drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/lib/debug/usr/lib/awn/applets/main-menu/ -rw-r--r-- root/root 38049 2010-04-17 09:34 ./usr/lib/debug/usr/lib/awn/applets/main-menu/main-menu.so drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/lib/debug/usr/lib/awn/applets/notification-daemon/ -rw-r--r-- root/root 145542 2010-04-17 09:34 ./usr/lib/debug/usr/lib/awn/applets/notification-daemon/notification-daemon.so drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/lib/debug/usr/lib/awn/applets/sysmon/ -rw-r--r-- root/root 239441 2010-04-17 09:34 ./usr/lib/debug/usr/lib/awn/applets/sysmon/sysmon.so drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/lib/debug/usr/lib/awn/applets/awnsystemmonitor/ -rw-r--r-- root/root 280974 2010-04-17 09:34 ./usr/lib/debug/usr/lib/awn/applets/awnsystemmonitor/awnsystemmonitor.so drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/lib/debug/usr/lib/awn/applets/webapplet/ -rw-r--r-- root/root 62668 2010-04-17 09:34 ./usr/lib/debug/usr/lib/awn/applets/webapplet/webapplet.so drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/lib/debug/usr/lib/awn/applets/showdesktop/ -rw-r--r-- root/root 52965 2010-04-17 09:34 ./usr/lib/debug/usr/lib/awn/applets/showdesktop/showdesktop.so drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/lib/debug/usr/lib/awn/applets/notification-area/ -rw-r--r-- root/root 194293 2010-04-17 09:34 ./usr/lib/debug/usr/lib/awn/applets/notification-area/notification-area.so drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/lib/debug/usr/lib/awn/applets/shinyswitcher/ -rw-r--r-- root/root 113735 2010-04-17 09:34 ./usr/lib/debug/usr/lib/awn/applets/shinyswitcher/shinyswitcher.so drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/lib/debug/usr/lib/awn/applets/garbage/ -rw-r--r-- root/root 104754 2010-04-17 09:34 ./usr/lib/debug/usr/lib/awn/applets/garbage/garbage.so drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/share/ drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/share/doc/ drwxr-xr-x root/root 0 2010-04-17 09:34 ./usr/share/doc/awn-applets-c-dbg/ -rw-r--r-- root/root 380 2009-08-14 12:07 ./usr/share/doc/awn-applets-c-dbg/changelog.gz -rw-r--r-- root/root 29449 2010-04-17 09:32 ./usr/share/doc/awn-applets-c-dbg/copyright -rw-r--r-- root/root 4247 2010-04-17 09:32 ./usr/share/doc/awn-applets-c-dbg/changelog.Debian.gz awn-extras-applets_0.4.0-0ubuntu1~ppa4_amd64.changes: Format: 1.8 Date: Fri, 16 Apr 2010 21:06:38 +0200 Source: awn-extras-applets Binary: awn-applets-c-core awn-applets-c-extras awn-applets-python-core awn-applets-python-extras python-awn-extras awn-applets-c-dbg Architecture: amd64 Version: 0.4.0-0ubuntu1~ppa4 Distribution: jaunty Urgency: low Maintainer: Ubuntu/amd64 Build Daemon Changed-By: Julien Lavergne Description: awn-applets-c-core - A collection of applets for avant-window-navigator awn-applets-c-dbg - A collection of applets for avant-window-navigator - debug symbol awn-applets-c-extras - A collection of applets for avant-window-navigator awn-applets-python-core - A collection of applets for avant-window-navigator awn-applets-python-extras - A collection of applets for avant-window-navigator python-awn-extras - Python utilities for avant-window-navigator's applets Changes: awn-extras-applets (0.4.0-0ubuntu1~ppa4) jaunty; urgency=low . * Backport. Checksums-Sha1: 74505bb18ae49e8991875d7666a8b2a446f82653 229628 awn-applets-c-core_0.4.0-0ubuntu1~ppa4_amd64.deb 805b881d21e5a977af9644adb30e9894c641beef 127196 awn-applets-c-extras_0.4.0-0ubuntu1~ppa4_amd64.deb a31f00f166fe94b7c6f07a55d00496106f672979 36134 python-awn-extras_0.4.0-0ubuntu1~ppa4_amd64.deb 13185e684caca325c11a5542723ad1c8d1f1e041 782446 awn-applets-c-dbg_0.4.0-0ubuntu1~ppa4_amd64.deb Checksums-Sha256: 4c7eb4605fd8cb82d1a51fdff206b952610305074809d7faf2f5eb8750f307a1 229628 awn-applets-c-core_0.4.0-0ubuntu1~ppa4_amd64.deb 00f89d5f2c00d1fbfca58fa3c64477d2ebb55d1191d57ef2838e4a4fdd75a405 127196 awn-applets-c-extras_0.4.0-0ubuntu1~ppa4_amd64.deb f2fa6d6f7ab814e82a9993c790b280719fe4e5729bfb3dfb22e7292a6038e23b 36134 python-awn-extras_0.4.0-0ubuntu1~ppa4_amd64.deb cdee2a6bf567ff7315ed4f610f99d5d383a81f875eaa7ab455777da9b2e45079 782446 awn-applets-c-dbg_0.4.0-0ubuntu1~ppa4_amd64.deb Files: b3414a4cee350d23ff1a5a3e9fc71f90 229628 gnome optional awn-applets-c-core_0.4.0-0ubuntu1~ppa4_amd64.deb 8c4e4919f5dd0f618ea9bf3d5861cc05 127196 gnome optional awn-applets-c-extras_0.4.0-0ubuntu1~ppa4_amd64.deb 2cf7e10acb246bb8600e18ba799155b3 36134 python optional python-awn-extras_0.4.0-0ubuntu1~ppa4_amd64.deb bac934e2940b22aaa10c77fdd2dc928d 782446 debug extra awn-applets-c-dbg_0.4.0-0ubuntu1~ppa4_amd64.deb Original-Maintainer: Julien Lavergne ****************************************************************************** Built successfully Purging chroot-autobuild/build/buildd/awn-extras-applets-0.4.0 ------------------------------------------------------------------------------ /usr/bin/sudo dpkg --purge groff-base libxfixes-dev libx11-data m4 libgconf2-dev fontconfig-config libstartup-notification0-dev gettext file zlib1g-dev libhtml-parser-perl libwnck-dev ttf-dejavu libhunspell-1.2-0 libvte9 libcairo2 libvala0 libawn1 x11-common libidl-dev libgnome-menu2 python2.6 libx11-dev libxi6 libwnck22 automake libjpeg62 libvte-common libnotify-dev libxcursor1 x11proto-input-dev libexpat1-dev libjasper1 libpixman-1-dev libjpeg62-dev libxcomposite-dev libfontconfig1 libdbus-glib-1-2 libenchant1c2a libsexy2 libsysfs-dev libx11-6 libxres-dev libvte-dev xtrans-dev x11proto-randr-dev vala-awn psmisc libdesktop-agnostic-bin libglib2.0-0 libnewt0.52 libxinerama-dev libpango1.0-common libxdamage1 libxt6 libxml2-utils libdbus-1-dev libhtml-tree-perl libglib2.0-dev libgnome-menu-dev libxcb-render-util0 gconf2 libdirectfb-dev libhtml-tagset-perl libgtop2-common libxml2 x11proto-xext-dev pkg-config libthai-data libwebkit-dev libice6 intltool-debian libxrender1 liborbit2-dev libfontconfig1-dev libxml2-dev libxrandr-dev libxext-dev libcups2 libdirectfb-extra libxau-dev libxcb-render-util0-dev libaspell15 libxrender-dev ttf-dejavu-extra librsvg2-dev libpng12-dev libxft2 libpopt-dev x11proto-render-dev libxext6 libsysfs2 libsqlite3-0 libnotify1 libxinerama1 libawn-dev libdbus-glib-1-dev libxdamage-dev libsm-dev libncursesw5 gconf2-common libgsf-1-common libxdmcp-dev defoma ttf-dejavu-core librsvg2-2 libsexy-dev libcairo2-dev fontconfig libxcb-render0-dev liburi-perl libstartup-notification0 autotools-dev libcroco3 libicu38 liborbit2 python-support libpopt0 libfreetype6 libwnck-common libice-dev libwebkit-1.0-1 libatk1.0-0 libdbus-1-3 x11proto-fixes-dev libfreetype6-dev libgtk2.0-0 x11proto-damage-dev libidl0 libxcb1 libgtop2-dev libgtop2-7 html2text diffstat libgsf-1-114 libxrandr2 debhelper libpthread-stubs0 libthai0 python libncurses5-dev libxslt1.1 libmagic1 libdesktop-agnostic-dev libtiff4 libexpat1 bsdmainutils libdirectfb-1.0-0 libxau6 libpango1.0-dev vala-desktop-agnostic libxcursor-dev libxcomposite1 x11proto-composite-dev libgconf2-4 mime-support x11proto-core-dev whiptail intltool libts-0.0-0 libxcb1-dev libxi-dev valac libwww-perl shared-mime-info libxfixes3 libxdmcp6 libgtk2.0-dev po-debconf libatk1.0-dev quilt libxml-parser-perl libxft-dev libdesktop-agnostic0 libpng12-0 man-db x11proto-kb-dev libpixman-1-0 libpolkit-dbus2 x11proto-xinerama-dev libdatrie0 libdesktop-agnostic-cfg-gconf libpango1.0-0 libpthread-stubs0-dev ucf libgtk2.0-common gettext-base libsm6 libxcb-render0 libxres1 libpolkit2 x11proto-resource-dev autoconf (Reading database ... 19071 files and directories currently installed.) Removing libgconf2-dev ... Removing libwnck-dev ... Removing libwnck22 ... Purging configuration files for libwnck22 ... Removing libnotify-dev ... Removing libxres-dev ... Removing libvte-dev ... Removing vala-awn ... Removing libdesktop-agnostic-bin ... Removing libgnome-menu-dev ... Removing gconf2 ... Purging configuration files for gconf2 ... Removing libwebkit-dev ... Removing liborbit2-dev ... Removing librsvg2-dev ... Removing libpopt-dev ... Removing libnotify1 ... Purging configuration files for libnotify1 ... Removing libawn-dev ... Removing libdbus-glib-1-dev ... Removing librsvg2-2 ... Purging configuration files for librsvg2-2 ... Removing libsexy-dev ... Removing python-support ... Purging configuration files for python-support ... Removing libwnck-common ... Removing libwebkit-1.0-1 ... Purging configuration files for libwebkit-1.0-1 ... Removing libgtop2-dev ... Removing libgtop2-7 ... Purging configuration files for libgtop2-7 ... Removing libgsf-1-114 ... Purging configuration files for libgsf-1-114 ... Removing debhelper ... Removing python ... Purging configuration files for python ... Removing libncurses5-dev ... Removing libxslt1.1 ... Purging configuration files for libxslt1.1 ... Removing libdesktop-agnostic-dev ... Removing vala-desktop-agnostic ... Removing intltool ... Removing valac ... Removing libgtk2.0-dev ... Removing po-debconf ... Removing libatk1.0-dev ... Removing quilt ... Purging configuration files for quilt ... Removing libxml-parser-perl ... Removing man-db ... Purging configuration files for man-db ... Removing libdesktop-agnostic-cfg-gconf ... Removing libxres1 ... Purging configuration files for libxres1 ... Removing x11proto-resource-dev ... Removing groff-base ... Purging configuration files for groff-base ... Removing libstartup-notification0-dev ... Removing libvte9 ... Purging configuration files for libvte9 ... Removing libvala0 ... Purging configuration files for libvala0 ... Removing libawn1 ... Purging configuration files for libawn1 ... Removing libidl-dev ... Removing libgnome-menu2 ... Purging configuration files for libgnome-menu2 ... Removing python2.6 ... Purging configuration files for python2.6 ... Removing automake ... Removing libvte-common ... Removing libxcomposite-dev ... Removing libsexy2 ... Purging configuration files for libsexy2 ... Removing psmisc ... Purging configuration files for psmisc ... Removing libxinerama-dev ... Removing libxt6 ... Purging configuration files for libxt6 ... Removing libxml2-utils ... Removing libdbus-1-dev ... Removing libgtop2-common ... Removing intltool-debian ... Removing libxml2-dev ... Removing libxrandr-dev ... Removing libsqlite3-0 ... Purging configuration files for libsqlite3-0 ... Removing libxdamage-dev ... Removing libncursesw5 ... Purging configuration files for libncursesw5 ... Removing libgsf-1-common ... Removing libstartup-notification0 ... Purging configuration files for libstartup-notification0 ... Removing autotools-dev ... Removing libicu38 ... Purging configuration files for libicu38 ... Removing x11proto-damage-dev ... Removing html2text ... Purging configuration files for html2text ... Removing diffstat ... Removing bsdmainutils ... Purging configuration files for bsdmainutils ... Removing libpango1.0-dev ... Removing libxcursor-dev ... Removing x11proto-composite-dev ... Removing libgconf2-4 ... Purging configuration files for libgconf2-4 ... Removing mime-support ... Purging configuration files for mime-support ... Removing libxi-dev ... Removing libwww-perl ... Removing libxft-dev ... Removing libdesktop-agnostic0 ... Purging configuration files for libdesktop-agnostic0 ... Removing libpolkit-dbus2 ... Purging configuration files for libpolkit-dbus2 ... Removing x11proto-xinerama-dev ... Removing libpolkit2 ... Purging configuration files for libpolkit2 ... Removing autoconf ... Purging configuration files for autoconf ... Removing libxfixes-dev ... Removing m4 ... Removing gettext ... Removing libenchant1c2a ... Removing x11proto-randr-dev ... Removing libhtml-tree-perl ... Removing libglib2.0-dev ... Removing libaspell15 ... Purging configuration files for libaspell15 ... Removing gconf2-common ... Purging configuration files for gconf2-common ... Removing libcairo2-dev ... Removing libcroco3 ... Purging configuration files for libcroco3 ... Removing liborbit2 ... Purging configuration files for liborbit2 ... Removing x11proto-fixes-dev ... Removing libgtk2.0-0 ... Purging configuration files for libgtk2.0-0 ... Removing libidl0 ... Purging configuration files for libidl0 ... Removing libxrandr2 ... Purging configuration files for libxrandr2 ... Removing libtiff4 ... Purging configuration files for libtiff4 ... Removing libxcomposite1 ... Purging configuration files for libxcomposite1 ... Removing shared-mime-info ... Purging configuration files for shared-mime-info ... dpkg - warning: while removing shared-mime-info, directory `/usr/share/mime' not empty so not removed. Removing libpango1.0-0 ... Purging configuration files for libpango1.0-0 ... Removing libgtk2.0-common ... Removing gettext-base ... Removing libhtml-parser-perl ... Removing libhunspell-1.2-0 ... Purging configuration files for libhunspell-1.2-0 ... Removing libcairo2 ... Purging configuration files for libcairo2 ... Removing libxi6 ... Purging configuration files for libxi6 ... Removing libxcursor1 ... Purging configuration files for libxcursor1 ... Removing libjasper1 ... Purging configuration files for libjasper1 ... Removing libpixman-1-dev ... Removing libdbus-glib-1-2 ... Purging configuration files for libdbus-glib-1-2 ... Removing libpango1.0-common ... Purging font configuration of pango... Purging category xfont.. Purging configuration files for libpango1.0-common ... Removing libxdamage1 ... Purging configuration files for libxdamage1 ... Removing libdirectfb-dev ... Removing libhtml-tagset-perl ... Removing libxml2 ... Purging configuration files for libxml2 ... Removing libfontconfig1-dev ... Removing libxext-dev ... Removing libcups2 ... Purging configuration files for libcups2 ... Removing libdirectfb-extra ... Removing libxcb-render-util0-dev ... Removing libxrender-dev ... Removing libpng12-dev ... Removing libxft2 ... Purging configuration files for libxft2 ... Removing x11proto-render-dev ... Removing libxinerama1 ... Purging configuration files for libxinerama1 ... Removing libsm-dev ... Removing fontconfig ... Purging font configuration of fontconfig... Purging category cid.. Purging category truetype.. Purging category type1.. Updating fontconfig cache for /usr/share/fonts/truetype/ttf-dejavu Purging configuration files for fontconfig ... Removing libxcb-render0-dev ... Removing liburi-perl ... Removing libice-dev ... Removing libatk1.0-0 ... Purging configuration files for libatk1.0-0 ... Removing libdbus-1-3 ... Purging configuration files for libdbus-1-3 ... Removing libfreetype6-dev ... Removing libthai0 ... Purging configuration files for libthai0 ... Removing libdirectfb-1.0-0 ... Purging configuration files for libdirectfb-1.0-0 ... Removing libts-0.0-0 ... Purging configuration files for libts-0.0-0 ... Removing libxfixes3 ... Purging configuration files for libxfixes3 ... Removing libpng12-0 ... Purging configuration files for libpng12-0 ... Removing libpixman-1-0 ... Purging configuration files for libpixman-1-0 ... Removing libdatrie0 ... Purging configuration files for libdatrie0 ... Removing libsm6 ... Purging configuration files for libsm6 ... Removing zlib1g-dev ... Removing libx11-dev ... Removing libexpat1-dev ... Removing libjpeg62-dev ... Removing libfontconfig1 ... Purging configuration files for libfontconfig1 ... Removing libsysfs-dev ... Removing xtrans-dev ... Removing libxcb-render-util0 ... Purging configuration files for libxcb-render-util0 ... Removing x11proto-xext-dev ... Removing pkg-config ... Removing libthai-data ... Removing libice6 ... Purging configuration files for libice6 ... Removing libxrender1 ... Purging configuration files for libxrender1 ... Removing libxext6 ... Purging configuration files for libxext6 ... Removing libsysfs2 ... Purging configuration files for libsysfs2 ... Removing libfreetype6 ... Purging configuration files for libfreetype6 ... Removing libexpat1 ... Purging configuration files for libexpat1 ... Removing libxcb1-dev ... Removing x11proto-kb-dev ... Removing libpthread-stubs0-dev ... Removing libxcb-render0 ... Purging configuration files for libxcb-render0 ... Removing fontconfig-config ... Purging configuration files for fontconfig-config ... Removing ttf-dejavu ... Removing libjpeg62 ... Removing x11proto-input-dev ... Removing libx11-6 ... Purging configuration files for libx11-6 ... Removing libglib2.0-0 ... Purging configuration files for libglib2.0-0 ... Removing libxau-dev ... Removing ttf-dejavu-extra ... Purging configuration files for ttf-dejavu-extra ... Removing libxdmcp-dev ... Removing ttf-dejavu-core ... Purging configuration files for ttf-dejavu-core ... Removing libxcb1 ... Purging configuration files for libxcb1 ... Removing libpthread-stubs0 ... Removing libxau6 ... Purging configuration files for libxau6 ... Removing x11proto-core-dev ... Removing libxdmcp6 ... Purging configuration files for libxdmcp6 ... Removing ucf ... Purging configuration files for ucf ... Removing libx11-data ... Removing x11-common ... Purging configuration files for x11-common ... Removing defoma ... Purging configuration files for defoma ... Removing whiptail ... Removing file ... Purging configuration files for file ... Removing libnewt0.52 ... Purging configuration files for libnewt0.52 ... Removing libpopt0 ... Purging configuration files for libpopt0 ... Removing libmagic1 ... Purging configuration files for libmagic1 ... Processing triggers for libc6 ... ldconfig deferred processing now taking place ****************************************************************************** Finished at 20100417-0935 Build needed 00:01:54, 69352k disk space Can't open average time db /var/debbuild/avg-build-times Can't open average space db /var/debbuild/avg-build-space RUN: /usr/share/launchpad-buildd/slavebin/scan-for-processes ['/usr/share/launchpad-buildd/slavebin/scan-for-processes', '1696413-3355640'] Scanning for processes to kill in build /home/buildd/build-1696413-3355640/chroot-autobuild... RUN: /usr/share/launchpad-buildd/slavebin/umount-chroot ['umount-chroot', '1696413-3355640'] Unmounting chroot for build 1696413-3355640... RUN: /usr/share/launchpad-buildd/slavebin/remove-build ['remove-build', '1696413-3355640'] Removing build 1696413-3355640