RUN: /bin/echo ['echo', 'Forking build subprocess...'] Forking build subprocess... RUN: /usr/share/launchpad-buildd/slavebin/unpack-chroot ['unpack-chroot', '1686916-3339864', '/home/buildd/filecache-default/21e9d7c4b48c9cc80e593feff4ab876bb80e92c4'] Synching the system clock with the buildd NTP service... 16 Apr 21:36:42 ntpdate[11501]: adjust time server 10.211.37.1 offset 0.000353 sec Unpacking chroot for build 1686916-3339864 RUN: /usr/share/launchpad-buildd/slavebin/mount-chroot ['mount-chroot', '1686916-3339864'] Mounting chroot for build 1686916-3339864 RUN: /usr/share/launchpad-buildd/slavebin/apply-ogre-model ['apply-ogre-model', '1686916-3339864', 'universe'] Attempting OGRE for universe in build-1686916-3339864 No OGRE sources.list found. RUN: /usr/share/launchpad-buildd/slavebin/override-sources-list ['override-sources-list', '1686916-3339864', 'deb http://ftpmaster.internal/ubuntu lucid main universe'] Overriding sources.list in build-1686916-3339864 RUN: /usr/share/launchpad-buildd/slavebin/update-debian-chroot ['update-debian-chroot', '1686916-3339864'] Updating debian chroot for build 1686916-3339864 Get:1 http://ftpmaster.internal lucid Release.gpg [189B] Get:2 http://ftpmaster.internal lucid Release [57.2kB] Get:3 http://ftpmaster.internal lucid/main Packages [1360kB] Get:4 http://ftpmaster.internal lucid/universe Packages [5295kB] Fetched 6713kB in 18s (371kB/s) Reading package lists... Reading package lists... Building dependency tree... Reading state information... The following packages will be upgraded: apt apt-transport-https base-files bash debconf debconf-i18n dpkg dpkg-dev initramfs-tools initramfs-tools-bin libdrm-intel1 libdrm-nouveau1 libdrm-radeon1 libdrm2 libglib2.0-0 libgssapi-krb5-2 libk5crypto3 libkrb5-3 libkrb5support0 libldap-2.4-2 libpam-modules libpam-runtime libpam0g libplymouth2 libudev0 linux-libc-dev locales module-init-tools mountall plymouth python2.6-minimal udev 32 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 16.3MB of archives. After this operation, 12.3kB of additional disk space will be used. WARNING: The following packages cannot be authenticated! libpam-modules base-files bash dpkg debconf-i18n debconf apt libpam-runtime libpam0g python2.6-minimal libk5crypto3 libgssapi-krb5-2 libkrb5-3 libkrb5support0 libldap-2.4-2 libglib2.0-0 module-init-tools udev libudev0 initramfs-tools initramfs-tools-bin libdrm2 libdrm-intel1 libdrm-nouveau1 libdrm-radeon1 plymouth libplymouth2 mountall locales apt-transport-https dpkg-dev linux-libc-dev Authentication warning overridden. Get:1 http://ftpmaster.internal/ubuntu/ lucid/main libpam-modules 1.1.1-2ubuntu2 [351kB] Get:2 http://ftpmaster.internal/ubuntu/ lucid/main base-files 5.0.0ubuntu18 [80.2kB] Get:3 http://ftpmaster.internal/ubuntu/ lucid/main bash 4.1-2ubuntu2 [626kB] Get:4 http://ftpmaster.internal/ubuntu/ lucid/main dpkg 1.15.5.6ubuntu4 [2175kB] Get:5 http://ftpmaster.internal/ubuntu/ lucid/main debconf-i18n 1.5.28ubuntu4 [178kB] Get:6 http://ftpmaster.internal/ubuntu/ lucid/main debconf 1.5.28ubuntu4 [148kB] Get:7 http://ftpmaster.internal/ubuntu/ lucid/main apt 0.7.25.3ubuntu7 [1773kB] Get:8 http://ftpmaster.internal/ubuntu/ lucid/main libpam-runtime 1.1.1-2ubuntu2 [115kB] Get:9 http://ftpmaster.internal/ubuntu/ lucid/main libpam0g 1.1.1-2ubuntu2 [119kB] Get:10 http://ftpmaster.internal/ubuntu/ lucid/main python2.6-minimal 2.6.5-1ubuntu6 [1330kB] Get:11 http://ftpmaster.internal/ubuntu/ lucid/main libk5crypto3 1.8.1+dfsg-2 [104kB] Get:12 http://ftpmaster.internal/ubuntu/ lucid/main libgssapi-krb5-2 1.8.1+dfsg-2 [111kB] Get:13 http://ftpmaster.internal/ubuntu/ lucid/main libkrb5-3 1.8.1+dfsg-2 [319kB] Get:14 http://ftpmaster.internal/ubuntu/ lucid/main libkrb5support0 1.8.1+dfsg-2 [41.5kB] Get:15 http://ftpmaster.internal/ubuntu/ lucid/main libldap-2.4-2 2.4.21-0ubuntu4 [188kB] Get:16 http://ftpmaster.internal/ubuntu/ lucid/main libglib2.0-0 2.24.0-0ubuntu2 [1004kB] Get:17 http://ftpmaster.internal/ubuntu/ lucid/main module-init-tools 3.11.1-2ubuntu1 [94.7kB] Get:18 http://ftpmaster.internal/ubuntu/ lucid/main udev 151-10 [408kB] Get:19 http://ftpmaster.internal/ubuntu/ lucid/main libudev0 151-10 [117kB] Get:20 http://ftpmaster.internal/ubuntu/ lucid/main initramfs-tools 0.92bubuntu74 [87.3kB] Get:21 http://ftpmaster.internal/ubuntu/ lucid/main initramfs-tools-bin 0.92bubuntu74 [51.6kB] Get:22 http://ftpmaster.internal/ubuntu/ lucid/main libdrm2 2.4.18-1ubuntu3 [409kB] Get:23 http://ftpmaster.internal/ubuntu/ lucid/main libdrm-intel1 2.4.18-1ubuntu3 [409kB] Get:24 http://ftpmaster.internal/ubuntu/ lucid/main libdrm-nouveau1 2.4.18-1ubuntu3 [400kB] Get:25 http://ftpmaster.internal/ubuntu/ lucid/main libdrm-radeon1 2.4.18-1ubuntu3 [398kB] Get:26 http://ftpmaster.internal/ubuntu/ lucid/main plymouth 0.8.2-2 [106kB] Get:27 http://ftpmaster.internal/ubuntu/ lucid/main libplymouth2 0.8.2-2 [83.5kB] Get:28 http://ftpmaster.internal/ubuntu/ lucid/main mountall 2.12 [50.7kB] Get:29 http://ftpmaster.internal/ubuntu/ lucid/main locales 2.11+git20100304-3 [3552kB] Get:30 http://ftpmaster.internal/ubuntu/ lucid/main apt-transport-https 0.7.25.3ubuntu7 [81.3kB] Get:31 http://ftpmaster.internal/ubuntu/ lucid/main dpkg-dev 1.15.5.6ubuntu4 [653kB] Get:32 http://ftpmaster.internal/ubuntu/ lucid/main linux-libc-dev 2.6.32-21.32 [769kB] debconf: delaying package configuration, since apt-utils is not installed Fetched 16.3MB in 1s (8346kB/s) (Reading database ... 13244 files and directories currently installed.) Preparing to replace libpam-modules 1.1.1-2ubuntu1 (using .../libpam-modules_1.1.1-2ubuntu2_armel.deb) ... Unpacking replacement libpam-modules ... Setting up libpam-modules (1.1.1-2ubuntu2) ... (Reading database ... 13245 files and directories currently installed.) Preparing to replace base-files 5.0.0ubuntu14 (using .../base-files_5.0.0ubuntu18_armel.deb) ... Unpacking replacement base-files ... Setting up base-files (5.0.0ubuntu18) ... (Reading database ... 13244 files and directories currently installed.) Preparing to replace bash 4.1-2ubuntu1 (using .../bash_4.1-2ubuntu2_armel.deb) ... Unpacking replacement bash ... Setting up bash (4.1-2ubuntu2) ... Installing new version of config file /etc/bash.bashrc ... update-alternatives: using /usr/share/man/man7/bash-builtins.7.gz to provide /usr/share/man/man7/builtins.7.gz (builtins.7.gz) in auto mode. (Reading database ... 13244 files and directories currently installed.) Preparing to replace dpkg 1.15.5.6ubuntu3 (using .../dpkg_1.15.5.6ubuntu4_armel.deb) ... Unpacking replacement dpkg ... Setting up dpkg (1.15.5.6ubuntu4) ... (Reading database ... 13244 files and directories currently installed.) Preparing to replace debconf-i18n 1.5.28ubuntu3 (using .../debconf-i18n_1.5.28ubuntu4_all.deb) ... Unpacking replacement debconf-i18n ... Setting up debconf-i18n (1.5.28ubuntu4) ... (Reading database ... 13244 files and directories currently installed.) Preparing to replace debconf 1.5.28ubuntu3 (using .../debconf_1.5.28ubuntu4_all.deb) ... Unpacking replacement debconf ... Setting up debconf (1.5.28ubuntu4) ... (Reading database ... 13244 files and directories currently installed.) Preparing to replace apt 0.7.25.3ubuntu6 (using .../apt_0.7.25.3ubuntu7_armel.deb) ... Unpacking replacement apt ... Setting up apt (0.7.25.3ubuntu7) ... Processing triggers for libc-bin ... ldconfig deferred processing now taking place (Reading database ... 13244 files and directories currently installed.) Preparing to replace libpam-runtime 1.1.1-2ubuntu1 (using .../libpam-runtime_1.1.1-2ubuntu2_all.deb) ... Unpacking replacement libpam-runtime ... Setting up libpam-runtime (1.1.1-2ubuntu2) ... (Reading database ... 13244 files and directories currently installed.) Preparing to replace libpam0g 1.1.1-2ubuntu1 (using .../libpam0g_1.1.1-2ubuntu2_armel.deb) ... Unpacking replacement libpam0g ... Setting up libpam0g (1.1.1-2ubuntu2) ... Processing triggers for libc-bin ... ldconfig deferred processing now taking place (Reading database ... 13244 files and directories currently installed.) Preparing to replace python2.6-minimal 2.6.5-1ubuntu4 (using .../python2.6-minimal_2.6.5-1ubuntu6_armel.deb) ... Unpacking replacement python2.6-minimal ... Setting up python2.6-minimal (2.6.5-1ubuntu6) ... (Reading database ... 13244 files and directories currently installed.) Preparing to replace libk5crypto3 1.8+dfsg~alpha1-7ubuntu1 (using .../libk5crypto3_1.8.1+dfsg-2_armel.deb) ... Unpacking replacement libk5crypto3 ... Preparing to replace libgssapi-krb5-2 1.8+dfsg~alpha1-7ubuntu1 (using .../libgssapi-krb5-2_1.8.1+dfsg-2_armel.deb) ... Unpacking replacement libgssapi-krb5-2 ... Preparing to replace libkrb5-3 1.8+dfsg~alpha1-7ubuntu1 (using .../libkrb5-3_1.8.1+dfsg-2_armel.deb) ... Unpacking replacement libkrb5-3 ... Preparing to replace libkrb5support0 1.8+dfsg~alpha1-7ubuntu1 (using .../libkrb5support0_1.8.1+dfsg-2_armel.deb) ... Unpacking replacement libkrb5support0 ... Preparing to replace libldap-2.4-2 2.4.21-0ubuntu3 (using .../libldap-2.4-2_2.4.21-0ubuntu4_armel.deb) ... Unpacking replacement libldap-2.4-2 ... Preparing to replace libglib2.0-0 2.24.0-0ubuntu1 (using .../libglib2.0-0_2.24.0-0ubuntu2_armel.deb) ... Unpacking replacement libglib2.0-0 ... Preparing to replace module-init-tools 3.11.1-2 (using .../module-init-tools_3.11.1-2ubuntu1_armel.deb) ... Unpacking replacement module-init-tools ... Preparing to replace udev 151-8 (using .../archives/udev_151-10_armel.deb) ... Adding `local diversion of /sbin/udevadm to /sbin/udevadm.upgrade' Unpacking replacement udev ... Preparing to replace libudev0 151-8 (using .../libudev0_151-10_armel.deb) ... Unpacking replacement libudev0 ... Preparing to replace initramfs-tools 0.92bubuntu71 (using .../initramfs-tools_0.92bubuntu74_all.deb) ... Unpacking replacement initramfs-tools ... Preparing to replace initramfs-tools-bin 0.92bubuntu71 (using .../initramfs-tools-bin_0.92bubuntu74_armel.deb) ... Unpacking replacement initramfs-tools-bin ... Preparing to replace libdrm2 2.4.18-1ubuntu2 (using .../libdrm2_2.4.18-1ubuntu3_armel.deb) ... Unpacking replacement libdrm2 ... Preparing to replace libdrm-intel1 2.4.18-1ubuntu2 (using .../libdrm-intel1_2.4.18-1ubuntu3_armel.deb) ... Unpacking replacement libdrm-intel1 ... Preparing to replace libdrm-nouveau1 2.4.18-1ubuntu2 (using .../libdrm-nouveau1_2.4.18-1ubuntu3_armel.deb) ... Unpacking replacement libdrm-nouveau1 ... Preparing to replace libdrm-radeon1 2.4.18-1ubuntu2 (using .../libdrm-radeon1_2.4.18-1ubuntu3_armel.deb) ... Unpacking replacement libdrm-radeon1 ... Preparing to replace plymouth 0.8.1-4ubuntu1 (using .../plymouth_0.8.2-2_armel.deb) ... Unpacking replacement plymouth ... Preparing to replace libplymouth2 0.8.1-4ubuntu1 (using .../libplymouth2_0.8.2-2_armel.deb) ... Unpacking replacement libplymouth2 ... Preparing to replace mountall 2.10 (using .../mountall_2.12_armel.deb) ... Unpacking replacement mountall ... Preparing to replace locales 2.11+git20100304-2 (using .../locales_2.11+git20100304-3_all.deb) ... Unpacking replacement locales ... Preparing to replace apt-transport-https 0.7.25.3ubuntu6 (using .../apt-transport-https_0.7.25.3ubuntu7_armel.deb) ... Unpacking replacement apt-transport-https ... Preparing to replace dpkg-dev 1.15.5.6ubuntu3 (using .../dpkg-dev_1.15.5.6ubuntu4_all.deb) ... Unpacking replacement dpkg-dev ... Preparing to replace linux-libc-dev 2.6.32-19.28 (using .../linux-libc-dev_2.6.32-21.32_armel.deb) ... Unpacking replacement linux-libc-dev ... Setting up libkrb5support0 (1.8.1+dfsg-2) ... Setting up libk5crypto3 (1.8.1+dfsg-2) ... Setting up libkrb5-3 (1.8.1+dfsg-2) ... Setting up libgssapi-krb5-2 (1.8.1+dfsg-2) ... Setting up libldap-2.4-2 (2.4.21-0ubuntu4) ... Setting up libglib2.0-0 (2.24.0-0ubuntu2) ... Setting up module-init-tools (3.11.1-2ubuntu1) ... Installing new version of config file /etc/modprobe.d/blacklist-framebuffer.conf ... Setting up libudev0 (151-10) ... Setting up initramfs-tools-bin (0.92bubuntu74) ... Setting up libdrm2 (2.4.18-1ubuntu3) ... Setting up libdrm-intel1 (2.4.18-1ubuntu3) ... Setting up libdrm-nouveau1 (2.4.18-1ubuntu3) ... Setting up libdrm-radeon1 (2.4.18-1ubuntu3) ... Setting up libplymouth2 (0.8.2-2) ... Setting up locales (2.11+git20100304-3) ... Setting up apt-transport-https (0.7.25.3ubuntu7) ... Setting up dpkg-dev (1.15.5.6ubuntu4) ... Setting up linux-libc-dev (2.6.32-21.32) ... Setting up initramfs-tools (0.92bubuntu74) ... update-initramfs: deferring update (trigger activated) Setting up udev (151-10) ... Removing `local diversion of /sbin/udevadm to /sbin/udevadm.upgrade' update-initramfs: deferring update (trigger activated) Setting up mountall (2.12) ... Installing new version of config file /etc/init/mounted-tmp.conf ... Installing new version of config file /etc/init/mounted-varrun.conf ... Installing new version of config file /etc/init/mounted-dev.conf ... Setting up plymouth (0.8.2-2) ... Installing new version of config file /etc/init/plymouth-stop.conf ... update-initramfs: deferring update (trigger activated) Processing triggers for libc-bin ... ldconfig deferred processing now taking place Processing triggers for initramfs-tools ... RUN: /usr/share/launchpad-buildd/slavebin/sbuild-package ['sbuild-package', '1686916-3339864', 'lucid', '--nolog', '--batch', '--archive=ubuntu', '--dist=lucid', '--purpose=PRIMARY', '--comp=universe', 'awn-extras-applets_0.4.0-0ubuntu1.dsc'] Initiating build 1686916-3339864 with 0 processor cores. Automatic build of awn-extras-applets_0.4.0-0ubuntu1 on ivy by sbuild/armel 1.170.5 Build started at 20100416-2139 ****************************************************************************** awn-extras-applets_0.4.0-0ubuntu1.dsc exists in cwd ** Using build dependencies supplied by package: Build-Depends: debhelper (>= 7.0.50~), 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 dbus dbus-x11 defoma diffstat file fontconfig fontconfig-config gconf2 gconf2-common gettext gettext-base groff-base html2text intltool-debian iso-codes libaspell15 libatk1.0-0 libatk1.0-dev libavahi-client3 libavahi-common-data libavahi-common3 libawn1 libcairo2 libcairo2-dev libcroco3 libcups2 libdatrie1 libdbus-1-dev libdbus-glib-1-2 libdbus-glib-1-dev libdesktop-agnostic-cfg-gconf libdesktop-agnostic-dev libdesktop-agnostic0 libdirectfb-1.2-0 libdirectfb-dev libdirectfb-extra libenchant1c2a libexpat1 libexpat1-dev libffi5 libfontconfig1 libfontconfig1-dev libfreetype6 libfreetype6-dev libgail18 libgconf2-4 libgcrypt11-dev libglib2.0-dev libgnome-menu2 libgnutls-dev libgpg-error-dev libgsf-1-114 libgsf-1-common libgstreamer-plugins-base0.10-0 libgstreamer0.10-0 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 libicu42 libidl-dev libidl0 libjasper1 libjpeg62 libjpeg62-dev libmagic1 libncursesw5 libnewt0.52 libnotify1 liborbit2 liborbit2-dev libpango1.0-0 libpango1.0-common libpango1.0-dev libpixman-1-0 libpixman-1-dev libpng12-dev libpopt0 libpthread-stubs0 libpthread-stubs0-dev librsvg2-2 libsexy2 libsm-dev libsm6 libsoup2.4-1 libsoup2.4-dev libsqlite3-0 libstartup-notification0 libstartup-notification0-dev libsysfs-dev libsysfs2 libtasn1-3-dev libthai-data libthai0 libtiff4 libts-0.0-0 liburi-perl libvala0 libvte-common libvte9 libwebkit-1.0-2 libwebkit-1.0-common libwnck-common libwnck22 libwww-perl libx11-6 libx11-data libx11-dev libxau-dev libxau6 libxcb-atom1 libxcb-aux0 libxcb-event1 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-cairo python-gobject python-gtk2 python-vte python2.6 shared-mime-info tsconf ttf-dejavu-core 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 autoconf-archive gnu-standards autoconf-doc libtool wamerican wordlist whois vacation dh-make defoma-doc psfontmgr x-ttcidfont-conf dfontmgr gconf-defaults-service gettext-doc groff isoquery 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 libgcrypt11-doc libglib2.0-doc python-subunit gnutls-doc gnutls-bin guile-gnutls libvisual-0.4-plugins gstreamer-codec-install gnome-codec-install gstreamer0.10-tools gstreamer0.10-plugins 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 libsoup2.4-doc libcrypt-ssleay-perl libio-socket-ssl-perl less www-browser libmail-box-perl python-doc python-tk python-profiler python-gobject-dbg python-gtk2-doc python-numpy python2.6-doc python2.6-profiler procmail graphviz Recommended packages: consolekit libfont-freetype-perl curl wget lynx cvs aspell-en aspell-dictionary aspell6a-dictionary libatk1.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 xml-core libmail-sendmail-perl The following NEW packages will be installed: autoconf automake autotools-dev bsdmainutils dbus dbus-x11 debhelper defoma diffstat file fontconfig fontconfig-config gconf2 gconf2-common gettext gettext-base groff-base html2text intltool intltool-debian iso-codes libaspell15 libatk1.0-0 libatk1.0-dev libavahi-client3 libavahi-common-data libavahi-common3 libawn-dev libawn1 libcairo2 libcairo2-dev libcroco3 libcups2 libdatrie1 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.2-0 libdirectfb-dev libdirectfb-extra libenchant1c2a libexpat1 libexpat1-dev libffi5 libfontconfig1 libfontconfig1-dev libfreetype6 libfreetype6-dev libgail18 libgconf2-4 libgconf2-dev libgcrypt11-dev libglib2.0-dev libgnome-menu-dev libgnome-menu2 libgnutls-dev libgpg-error-dev libgsf-1-114 libgsf-1-common libgstreamer-plugins-base0.10-0 libgstreamer0.10-0 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 libicu42 libidl-dev libidl0 libjasper1 libjpeg62 libjpeg62-dev libmagic1 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-dev libpopt0 libpthread-stubs0 libpthread-stubs0-dev librsvg2-2 librsvg2-dev libsexy-dev libsexy2 libsm-dev libsm6 libsoup2.4-1 libsoup2.4-dev libsqlite3-0 libstartup-notification0 libstartup-notification0-dev libsysfs-dev libsysfs2 libtasn1-3-dev libthai-data libthai0 libtiff4 libts-0.0-0 liburi-perl libvala0 libvte-common libvte-dev libvte9 libwebkit-1.0-2 libwebkit-1.0-common libwebkit-dev libwnck-common libwnck-dev libwnck22 libwww-perl libx11-6 libx11-data libx11-dev libxau-dev libxau6 libxcb-atom1 libxcb-aux0 libxcb-event1 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-cairo python-gobject python-gtk2 python-support python-vte python2.6 quilt shared-mime-info tsconf ttf-dejavu-core 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, 209 newly installed, 0 to remove and 0 not upgraded. Need to get 63.8MB of archives. After this operation, 234MB of additional disk space will be used. WARNING: The following packages cannot be authenticated! x11-common libice6 x11proto-core-dev libice-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 libxres1 x11proto-resource-dev libxres-dev libmagic1 file libncursesw5 libnewt0.52 libpopt0 libsqlite3-0 mime-support python2.6 python ucf whiptail bsdmainutils gettext-base groff-base iso-codes libexpat1 liburi-perl libhtml-tagset-perl libhtml-parser-perl libhtml-tree-perl libwww-perl libxml-parser-perl libxml2 man-db psmisc python-support m4 autoconf autotools-dev automake dbus dbus-x11 html2text libcroco3 gettext intltool-debian po-debconf debhelper defoma diffstat libfreetype6 ttf-dejavu-core fontconfig-config libfontconfig1 fontconfig libdbus-glib-1-2 libidl0 liborbit2 gconf2-common libgconf2-4 gconf2 intltool libaspell15 libatk1.0-0 pkg-config zlib1g-dev libglib2.0-dev libatk1.0-dev libavahi-common-data libavahi-common3 libavahi-client3 libsysfs2 tsconf libts-0.0-0 libdirectfb-1.2-0 libpixman-1-0 libxcb-render0 libxcb-render-util0 libxrender1 libcairo2 libgtk2.0-common libcups2 libjpeg62 libjasper1 libpango1.0-common libdatrie1 libthai-data libthai0 libxft2 libpango1.0-0 libtiff4 libxcursor1 libxdamage1 libxi6 libxinerama1 libxrandr2 shared-mime-info libgtk2.0-0 libdesktop-agnostic0 libawn1 libfreetype6-dev x11proto-render-dev libxrender-dev libexpat1-dev libfontconfig1-dev libxft-dev libpng12-dev libdirectfb-extra libjpeg62-dev libsysfs-dev libdirectfb-dev libsm6 libsm-dev libpixman-1-dev libxcb-render0-dev libxcb-render-util0-dev libcairo2-dev libpango1.0-dev x11proto-xinerama-dev libxinerama-dev libxi-dev x11proto-randr-dev libxrandr-dev libxcursor-dev x11proto-damage-dev libxdamage-dev libxml2-utils libgtk2.0-dev libdesktop-agnostic-dev libdbus-1-dev libdbus-glib-1-dev libawn-dev libhunspell-1.2-0 libenchant1c2a libgail18 libidl-dev liborbit2-dev libgconf2-dev libgpg-error-dev libgcrypt11-dev libgnome-menu2 libgnome-menu-dev libtasn1-3-dev libgnutls-dev libgsf-1-common libgsf-1-114 libgstreamer0.10-0 libgstreamer-plugins-base0.10-0 libgtop2-common libgtop2-7 libgtop2-dev libicu42 libnotify1 libnotify-dev librsvg2-2 librsvg2-dev libsexy2 libxml2-dev libsexy-dev libsoup2.4-1 libsoup2.4-dev libxcb-atom1 libxcb-aux0 libxcb-event1 libstartup-notification0 libstartup-notification0-dev libvala0 libvte-common libvte9 python-cairo libffi5 python-gobject python-gtk2 python-vte libvte-dev libxslt1.1 libxt6 libwebkit-1.0-common libwebkit-1.0-2 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://ftpmaster.internal/ubuntu/ lucid/main x11-common 1:7.5+5ubuntu1 [308kB] Get:2 http://ftpmaster.internal/ubuntu/ lucid/main libice6 2:1.0.6-1 [45.9kB] Get:3 http://ftpmaster.internal/ubuntu/ lucid/main x11proto-core-dev 7.0.16-1 [92.2kB] Get:4 http://ftpmaster.internal/ubuntu/ lucid/main libice-dev 2:1.0.6-1 [57.2kB] Get:5 http://ftpmaster.internal/ubuntu/ lucid/main libxau6 1:1.0.5-1 [13.5kB] Get:6 http://ftpmaster.internal/ubuntu/ lucid/main libxdmcp6 1:1.0.3-1 [17.1kB] Get:7 http://ftpmaster.internal/ubuntu/ lucid/main libxcb1 1.5-2 [39.5kB] Get:8 http://ftpmaster.internal/ubuntu/ lucid/main libx11-data 2:1.3.2-1ubuntu3 [220kB] Get:9 http://ftpmaster.internal/ubuntu/ lucid/main libx11-6 2:1.3.2-1ubuntu3 [770kB] Get:10 http://ftpmaster.internal/ubuntu/ lucid/main libxau-dev 1:1.0.5-1 [17.2kB] Get:11 http://ftpmaster.internal/ubuntu/ lucid/main libxdmcp-dev 1:1.0.3-1 [20.8kB] Get:12 http://ftpmaster.internal/ubuntu/ lucid/main x11proto-input-dev 2.0-2 [62.5kB] Get:13 http://ftpmaster.internal/ubuntu/ lucid/main x11proto-kb-dev 1.0.4-1 [27.3kB] Get:14 http://ftpmaster.internal/ubuntu/ lucid/main xtrans-dev 1.2.5-1 [68.5kB] Get:15 http://ftpmaster.internal/ubuntu/ lucid/main libpthread-stubs0 0.3-2 [3200B] Get:16 http://ftpmaster.internal/ubuntu/ lucid/main libpthread-stubs0-dev 0.3-2 [2424B] Get:17 http://ftpmaster.internal/ubuntu/ lucid/main libxcb1-dev 1.5-2 [77.4kB] Get:18 http://ftpmaster.internal/ubuntu/ lucid/main libx11-dev 2:1.3.2-1ubuntu3 [3472kB] Get:19 http://ftpmaster.internal/ubuntu/ lucid/main libxext6 2:1.1.1-2 [37.7kB] Get:20 http://ftpmaster.internal/ubuntu/ lucid/main libxfixes3 1:4.0.4-1 [14.1kB] Get:21 http://ftpmaster.internal/ubuntu/ lucid/main libxcomposite1 1:0.4.1-1 [12.1kB] Get:22 http://ftpmaster.internal/ubuntu/ lucid/main x11proto-xext-dev 7.1.1-2 [27.2kB] Get:23 http://ftpmaster.internal/ubuntu/ lucid/main x11proto-fixes-dev 1:4.1.1-2 [15.5kB] Get:24 http://ftpmaster.internal/ubuntu/ lucid/main libxfixes-dev 1:4.0.4-1 [16.9kB] Get:25 http://ftpmaster.internal/ubuntu/ lucid/main x11proto-composite-dev 1:0.4.1-1 [13.3kB] Get:26 http://ftpmaster.internal/ubuntu/ lucid/main libxext-dev 2:1.1.1-2 [102kB] Get:27 http://ftpmaster.internal/ubuntu/ lucid/main libxcomposite-dev 1:0.4.1-1 [15.6kB] Get:28 http://ftpmaster.internal/ubuntu/ lucid/main libxres1 2:1.0.4-1 [10.9kB] Get:29 http://ftpmaster.internal/ubuntu/ lucid/main x11proto-resource-dev 1.1.0-1 [4106B] Get:30 http://ftpmaster.internal/ubuntu/ lucid/main libxres-dev 2:1.0.4-1 [13.0kB] Get:31 http://ftpmaster.internal/ubuntu/ lucid/main libmagic1 5.03-5ubuntu1 [389kB] Get:32 http://ftpmaster.internal/ubuntu/ lucid/main file 5.03-5ubuntu1 [47.4kB] Get:33 http://ftpmaster.internal/ubuntu/ lucid/main libncursesw5 5.7+20090803-2ubuntu3 [195kB] Get:34 http://ftpmaster.internal/ubuntu/ lucid/main libnewt0.52 0.52.10-5ubuntu1 [49.4kB] Get:35 http://ftpmaster.internal/ubuntu/ lucid/main libpopt0 1.15-1 [29.4kB] Get:36 http://ftpmaster.internal/ubuntu/ lucid/main libsqlite3-0 3.6.22-1 [264kB] Get:37 http://ftpmaster.internal/ubuntu/ lucid/main mime-support 3.48-1ubuntu1 [34.6kB] Get:38 http://ftpmaster.internal/ubuntu/ lucid/main python2.6 2.6.5-1ubuntu6 [2458kB] Get:39 http://ftpmaster.internal/ubuntu/ lucid/main python 2.6.5-0ubuntu1 [148kB] Get:40 http://ftpmaster.internal/ubuntu/ lucid/main ucf 3.0025 [68.1kB] Get:41 http://ftpmaster.internal/ubuntu/ lucid/main whiptail 0.52.10-5ubuntu1 [38.0kB] Get:42 http://ftpmaster.internal/ubuntu/ lucid/main bsdmainutils 8.0.1ubuntu1 [191kB] Get:43 http://ftpmaster.internal/ubuntu/ lucid/main gettext-base 0.17-8ubuntu3 [69.1kB] Get:44 http://ftpmaster.internal/ubuntu/ lucid/main groff-base 1.20.1-7 [1050kB] Get:45 http://ftpmaster.internal/ubuntu/ lucid/main iso-codes 3.12.1-1 [2642kB] Get:46 http://ftpmaster.internal/ubuntu/ lucid/main libexpat1 2.0.1-7ubuntu1 [112kB] Get:47 http://ftpmaster.internal/ubuntu/ lucid/main liburi-perl 1.52-1 [96.8kB] Get:48 http://ftpmaster.internal/ubuntu/ lucid/main libhtml-tagset-perl 3.20-2 [13.5kB] Get:49 http://ftpmaster.internal/ubuntu/ lucid/main libhtml-parser-perl 3.64-1 [110kB] Get:50 http://ftpmaster.internal/ubuntu/ lucid/main libhtml-tree-perl 3.23-1 [209kB] Get:51 http://ftpmaster.internal/ubuntu/ lucid/main libwww-perl 5.834-1 [401kB] Get:52 http://ftpmaster.internal/ubuntu/ lucid/main libxml-parser-perl 2.36-1.1build3 [307kB] Get:53 http://ftpmaster.internal/ubuntu/ lucid/main libxml2 2.7.6.dfsg-1ubuntu1 [767kB] Get:54 http://ftpmaster.internal/ubuntu/ lucid/main man-db 2.5.7-2 [1041kB] Get:55 http://ftpmaster.internal/ubuntu/ lucid/main psmisc 22.10-1 [56.0kB] Get:56 http://ftpmaster.internal/ubuntu/ lucid/main python-support 1.0.4ubuntu1 [32.0kB] Get:57 http://ftpmaster.internal/ubuntu/ lucid/main m4 1.4.13-3 [234kB] Get:58 http://ftpmaster.internal/ubuntu/ lucid/main autoconf 2.65-3ubuntu1 [772kB] Get:59 http://ftpmaster.internal/ubuntu/ lucid/main autotools-dev 20090611.1 [64.1kB] Get:60 http://ftpmaster.internal/ubuntu/ lucid/main automake 1:1.11.1-1 [608kB] Get:61 http://ftpmaster.internal/ubuntu/ lucid/main dbus 1.2.16-2ubuntu4 [174kB] Get:62 http://ftpmaster.internal/ubuntu/ lucid/main dbus-x11 1.2.16-2ubuntu4 [41.5kB] Get:63 http://ftpmaster.internal/ubuntu/ lucid/main html2text 1.3.2a-14build1 [94.2kB] Get:64 http://ftpmaster.internal/ubuntu/ lucid/main libcroco3 0.6.2-1 [89.5kB] Get:65 http://ftpmaster.internal/ubuntu/ lucid/main gettext 0.17-8ubuntu3 [1697kB] Get:66 http://ftpmaster.internal/ubuntu/ lucid/main intltool-debian 0.35.0+20060710.1 [31.6kB] Get:67 http://ftpmaster.internal/ubuntu/ lucid/main po-debconf 1.0.16 [224kB] Get:68 http://ftpmaster.internal/ubuntu/ lucid/main debhelper 7.4.15ubuntu1 [461kB] Get:69 http://ftpmaster.internal/ubuntu/ lucid/main defoma 0.11.10-4 [101kB] Get:70 http://ftpmaster.internal/ubuntu/ lucid/main diffstat 1.47-1build1 [23.0kB] Get:71 http://ftpmaster.internal/ubuntu/ lucid/main libfreetype6 2.3.11-1ubuntu2 [382kB] Get:72 http://ftpmaster.internal/ubuntu/ lucid/main ttf-dejavu-core 2.30-2 [1436kB] Get:73 http://ftpmaster.internal/ubuntu/ lucid/main fontconfig-config 2.8.0-2ubuntu1 [205kB] Get:74 http://ftpmaster.internal/ubuntu/ lucid/main libfontconfig1 2.8.0-2ubuntu1 [270kB] Get:75 http://ftpmaster.internal/ubuntu/ lucid/main fontconfig 2.8.0-2ubuntu1 [157kB] Get:76 http://ftpmaster.internal/ubuntu/ lucid/main libdbus-glib-1-2 0.84-1 [153kB] Get:77 http://ftpmaster.internal/ubuntu/ lucid/main libidl0 0.8.13-1 [92.8kB] Get:78 http://ftpmaster.internal/ubuntu/ lucid/main liborbit2 1:2.14.18-0.1 [243kB] Get:79 http://ftpmaster.internal/ubuntu/ lucid/main gconf2-common 2.28.1-0ubuntu1 [28.7kB] Get:80 http://ftpmaster.internal/ubuntu/ lucid/main libgconf2-4 2.28.1-0ubuntu1 [172kB] Get:81 http://ftpmaster.internal/ubuntu/ lucid/main gconf2 2.28.1-0ubuntu1 [57.1kB] Get:82 http://ftpmaster.internal/ubuntu/ lucid/main intltool 0.41.0-0ubuntu1 [52.5kB] Get:83 http://ftpmaster.internal/ubuntu/ lucid/main libaspell15 0.60.6-3ubuntu1 [587kB] Get:84 http://ftpmaster.internal/ubuntu/ lucid/main libatk1.0-0 1.30.0-0ubuntu2 [50.5kB] Get:85 http://ftpmaster.internal/ubuntu/ lucid/main pkg-config 0.22-1build2 [50.8kB] Get:86 http://ftpmaster.internal/ubuntu/ lucid/main zlib1g-dev 1:1.2.3.3.dfsg-15ubuntu1 [160kB] Get:87 http://ftpmaster.internal/ubuntu/ lucid/main libglib2.0-dev 2.24.0-0ubuntu2 [1097kB] Get:88 http://ftpmaster.internal/ubuntu/ lucid/main libatk1.0-dev 1.30.0-0ubuntu2 [107kB] Get:89 http://ftpmaster.internal/ubuntu/ lucid/main libavahi-common-data 0.6.25-1ubuntu6 [34.6kB] Get:90 http://ftpmaster.internal/ubuntu/ lucid/main libavahi-common3 0.6.25-1ubuntu6 [22.5kB] Get:91 http://ftpmaster.internal/ubuntu/ lucid/main libavahi-client3 0.6.25-1ubuntu6 [51.1kB] Get:92 http://ftpmaster.internal/ubuntu/ lucid/main libsysfs2 2.1.0-6 [19.9kB] Get:93 http://ftpmaster.internal/ubuntu/ lucid/main tsconf 1.0-7build1 [12.8kB] Get:94 http://ftpmaster.internal/ubuntu/ lucid/main libts-0.0-0 1.0-7build1 [29.3kB] Get:95 http://ftpmaster.internal/ubuntu/ lucid/main libdirectfb-1.2-0 1.2.8-5ubuntu2 [1083kB] Get:96 http://ftpmaster.internal/ubuntu/ lucid/main libpixman-1-0 0.16.4-1ubuntu2 [233kB] Get:97 http://ftpmaster.internal/ubuntu/ lucid/main libxcb-render0 1.5-2 [15.5kB] Get:98 http://ftpmaster.internal/ubuntu/ lucid/main libxcb-render-util0 0.3.6-1build1 [8960B] Get:99 http://ftpmaster.internal/ubuntu/ lucid/main libxrender1 1:0.9.5-1 [24.7kB] Get:100 http://ftpmaster.internal/ubuntu/ lucid/main libcairo2 1.8.10-2ubuntu1 [489kB] Get:101 http://ftpmaster.internal/ubuntu/ lucid/main libgtk2.0-common 2.20.0-0ubuntu4 [707kB] Get:102 http://ftpmaster.internal/ubuntu/ lucid/main libcups2 1.4.3-1 [205kB] Get:103 http://ftpmaster.internal/ubuntu/ lucid/main libjpeg62 6b-15ubuntu1 [79.9kB] Get:104 http://ftpmaster.internal/ubuntu/ lucid/main libjasper1 1.900.1-7 [133kB] Get:105 http://ftpmaster.internal/ubuntu/ lucid/main libpango1.0-common 1.28.0-0ubuntu2 [111kB] Get:106 http://ftpmaster.internal/ubuntu/ lucid/main libdatrie1 0.2.2-3 [22.4kB] Get:107 http://ftpmaster.internal/ubuntu/ lucid/main libthai-data 0.1.13-1 [196kB] Get:108 http://ftpmaster.internal/ubuntu/ lucid/main libthai0 0.1.13-1 [37.4kB] Get:109 http://ftpmaster.internal/ubuntu/ lucid/main libxft2 2.1.14-1ubuntu1 [48.4kB] Get:110 http://ftpmaster.internal/ubuntu/ lucid/main libpango1.0-0 1.28.0-0ubuntu2 [272kB] Get:111 http://ftpmaster.internal/ubuntu/ lucid/main libtiff4 3.9.2-2 [128kB] Get:112 http://ftpmaster.internal/ubuntu/ lucid/main libxcursor1 1:1.1.10-1 [21.6kB] Get:113 http://ftpmaster.internal/ubuntu/ lucid/main libxdamage1 1:1.1.2-1 [11.4kB] Get:114 http://ftpmaster.internal/ubuntu/ lucid/main libxi6 2:1.3-3 [50.9kB] Get:115 http://ftpmaster.internal/ubuntu/ lucid/main libxinerama1 2:1.1-2 [11.8kB] Get:116 http://ftpmaster.internal/ubuntu/ lucid/main libxrandr2 2:1.3.0-3 [25.3kB] Get:117 http://ftpmaster.internal/ubuntu/ lucid/main shared-mime-info 0.71-1ubuntu1 [418kB] Get:118 http://ftpmaster.internal/ubuntu/ lucid/main libgtk2.0-0 2.20.0-0ubuntu4 [2376kB] Get:119 http://ftpmaster.internal/ubuntu/ lucid/universe libdesktop-agnostic0 0.0.1~bzr383-0ubuntu3 [76.9kB] Get:120 http://ftpmaster.internal/ubuntu/ lucid/universe libawn1 0.4.0-0ubuntu1 [203kB] Get:121 http://ftpmaster.internal/ubuntu/ lucid/main libfreetype6-dev 2.3.11-1ubuntu2 [679kB] Get:122 http://ftpmaster.internal/ubuntu/ lucid/main x11proto-render-dev 2:0.11-1 [7404B] Get:123 http://ftpmaster.internal/ubuntu/ lucid/main libxrender-dev 1:0.9.5-1 [33.0kB] Get:124 http://ftpmaster.internal/ubuntu/ lucid/main libexpat1-dev 2.0.1-7ubuntu1 [193kB] Get:125 http://ftpmaster.internal/ubuntu/ lucid/main libfontconfig1-dev 2.8.0-2ubuntu1 [635kB] Get:126 http://ftpmaster.internal/ubuntu/ lucid/main libxft-dev 2.1.14-1ubuntu1 [63.8kB] Get:127 http://ftpmaster.internal/ubuntu/ lucid/main libpng12-dev 1.2.42-1ubuntu2 [255kB] Get:128 http://ftpmaster.internal/ubuntu/ lucid/main libdirectfb-extra 1.2.8-5ubuntu2 [30.5kB] Get:129 http://ftpmaster.internal/ubuntu/ lucid/main libjpeg62-dev 6b-15ubuntu1 [185kB] Get:130 http://ftpmaster.internal/ubuntu/ lucid/main libsysfs-dev 2.1.0-6 [33.4kB] Get:131 http://ftpmaster.internal/ubuntu/ lucid/main libdirectfb-dev 1.2.8-5ubuntu2 [797kB] Get:132 http://ftpmaster.internal/ubuntu/ lucid/main libsm6 2:1.1.1-1 [23.2kB] Get:133 http://ftpmaster.internal/ubuntu/ lucid/main libsm-dev 2:1.1.1-1 [27.1kB] Get:134 http://ftpmaster.internal/ubuntu/ lucid/main libpixman-1-dev 0.16.4-1ubuntu2 [249kB] Get:135 http://ftpmaster.internal/ubuntu/ lucid/main libxcb-render0-dev 1.5-2 [23.4kB] Get:136 http://ftpmaster.internal/ubuntu/ lucid/main libxcb-render-util0-dev 0.3.6-1build1 [6844B] Get:137 http://ftpmaster.internal/ubuntu/ lucid/main libcairo2-dev 1.8.10-2ubuntu1 [568kB] Get:138 http://ftpmaster.internal/ubuntu/ lucid/main libpango1.0-dev 1.28.0-0ubuntu2 [406kB] Get:139 http://ftpmaster.internal/ubuntu/ lucid/main x11proto-xinerama-dev 1.2-2 [4782B] Get:140 http://ftpmaster.internal/ubuntu/ lucid/main libxinerama-dev 2:1.1-2 [14.7kB] Get:141 http://ftpmaster.internal/ubuntu/ lucid/main libxi-dev 2:1.3-3 [132kB] Get:142 http://ftpmaster.internal/ubuntu/ lucid/main x11proto-randr-dev 1.3.1-1 [38.2kB] Get:143 http://ftpmaster.internal/ubuntu/ lucid/main libxrandr-dev 2:1.3.0-3 [33.7kB] Get:144 http://ftpmaster.internal/ubuntu/ lucid/main libxcursor-dev 1:1.1.10-1 [30.2kB] Get:145 http://ftpmaster.internal/ubuntu/ lucid/main x11proto-damage-dev 1:1.2.0-1 [10.2kB] Get:146 http://ftpmaster.internal/ubuntu/ lucid/main libxdamage-dev 1:1.1.2-1 [11.3kB] Get:147 http://ftpmaster.internal/ubuntu/ lucid/main libxml2-utils 2.7.6.dfsg-1ubuntu1 [87.8kB] Get:148 http://ftpmaster.internal/ubuntu/ lucid/main libgtk2.0-dev 2.20.0-0ubuntu4 [3704kB] Get:149 http://ftpmaster.internal/ubuntu/ lucid/universe libdesktop-agnostic-dev 0.0.1~bzr383-0ubuntu3 [11.2kB] Get:150 http://ftpmaster.internal/ubuntu/ lucid/main libdbus-1-dev 1.2.16-2ubuntu4 [25.4kB] Get:151 http://ftpmaster.internal/ubuntu/ lucid/main libdbus-glib-1-dev 0.84-1 [90.9kB] Get:152 http://ftpmaster.internal/ubuntu/ lucid/universe libawn-dev 0.4.0-0ubuntu1 [118kB] Get:153 http://ftpmaster.internal/ubuntu/ lucid/main libhunspell-1.2-0 1.2.8-6ubuntu1 [137kB] Get:154 http://ftpmaster.internal/ubuntu/ lucid/main libenchant1c2a 1.6.0-0ubuntu1 [79.8kB] Get:155 http://ftpmaster.internal/ubuntu/ lucid/main libgail18 2.20.0-0ubuntu4 [330kB] Get:156 http://ftpmaster.internal/ubuntu/ lucid/main libidl-dev 0.8.13-1 [83.1kB] Get:157 http://ftpmaster.internal/ubuntu/ lucid/main liborbit2-dev 1:2.14.18-0.1 [368kB] Get:158 http://ftpmaster.internal/ubuntu/ lucid/main libgconf2-dev 2.28.1-0ubuntu1 [194kB] Get:159 http://ftpmaster.internal/ubuntu/ lucid/main libgpg-error-dev 1.6-1ubuntu2 [37.4kB] Get:160 http://ftpmaster.internal/ubuntu/ lucid/main libgcrypt11-dev 1.4.4-5ubuntu2 [302kB] Get:161 http://ftpmaster.internal/ubuntu/ lucid/main libgnome-menu2 2.30.0-0ubuntu4 [53.6kB] Get:162 http://ftpmaster.internal/ubuntu/ lucid/main libgnome-menu-dev 2.30.0-0ubuntu4 [42.8kB] Get:163 http://ftpmaster.internal/ubuntu/ lucid/main libtasn1-3-dev 2.4-1 [272kB] Get:164 http://ftpmaster.internal/ubuntu/ lucid/main libgnutls-dev 2.8.5-2 [380kB] Get:165 http://ftpmaster.internal/ubuntu/ lucid/main libgsf-1-common 1.14.16-1ubuntu1 [58.5kB] Get:166 http://ftpmaster.internal/ubuntu/ lucid/main libgsf-1-114 1.14.16-1ubuntu1 [147kB] Get:167 http://ftpmaster.internal/ubuntu/ lucid/main libgstreamer0.10-0 0.10.28-1 [647kB] Get:168 http://ftpmaster.internal/ubuntu/ lucid/main libgstreamer-plugins-base0.10-0 0.10.28-1 [351kB] Get:169 http://ftpmaster.internal/ubuntu/ lucid/main libgtop2-common 2.26.1-0ubuntu2 [12.2kB] Get:170 http://ftpmaster.internal/ubuntu/ lucid/main libgtop2-7 2.26.1-0ubuntu2 [39.8kB] Get:171 http://ftpmaster.internal/ubuntu/ lucid/main libgtop2-dev 2.26.1-0ubuntu2 [96.6kB] Get:172 http://ftpmaster.internal/ubuntu/ lucid/main libicu42 4.2.1-3 [7337kB] Get:173 http://ftpmaster.internal/ubuntu/ lucid/main libnotify1 0.4.5-1ubuntu3 [19.3kB] Get:174 http://ftpmaster.internal/ubuntu/ lucid/main libnotify-dev 0.4.5-1ubuntu3 [15.8kB] Get:175 http://ftpmaster.internal/ubuntu/ lucid/main librsvg2-2 2.26.2-0ubuntu1 [93.9kB] Get:176 http://ftpmaster.internal/ubuntu/ lucid/main librsvg2-dev 2.26.2-0ubuntu1 [120kB] Get:177 http://ftpmaster.internal/ubuntu/ lucid/main libsexy2 0.1.11-2build2 [29.3kB] Get:178 http://ftpmaster.internal/ubuntu/ lucid/main libxml2-dev 2.7.6.dfsg-1ubuntu1 [709kB] Get:179 http://ftpmaster.internal/ubuntu/ lucid/main libsexy-dev 0.1.11-2build2 [30.1kB] Get:180 http://ftpmaster.internal/ubuntu/ lucid/main libsoup2.4-1 2.30.0-0ubuntu1 [147kB] Get:181 http://ftpmaster.internal/ubuntu/ lucid/main libsoup2.4-dev 2.30.0-0ubuntu1 [171kB] Get:182 http://ftpmaster.internal/ubuntu/ lucid/main libxcb-atom1 0.3.6-1build1 [9554B] Get:183 http://ftpmaster.internal/ubuntu/ lucid/main libxcb-aux0 0.3.6-1build1 [8060B] Get:184 http://ftpmaster.internal/ubuntu/ lucid/main libxcb-event1 0.3.6-1build1 [8732B] Get:185 http://ftpmaster.internal/ubuntu/ lucid/main libstartup-notification0 0.10-1build1 [16.6kB] Get:186 http://ftpmaster.internal/ubuntu/ lucid/main libstartup-notification0-dev 0.10-1build1 [17.5kB] Get:187 http://ftpmaster.internal/ubuntu/ lucid/main libvala0 0.8.0-0ubuntu1 [850kB] Get:188 http://ftpmaster.internal/ubuntu/ lucid/main libvte-common 1:0.23.5-0ubuntu1 [41.1kB] Get:189 http://ftpmaster.internal/ubuntu/ lucid/main libvte9 1:0.23.5-0ubuntu1 [537kB] Get:190 http://ftpmaster.internal/ubuntu/ lucid/main python-cairo 1.8.8-1 [45.6kB] Get:191 http://ftpmaster.internal/ubuntu/ lucid/main libffi5 3.0.9-1 [15.7kB] Get:192 http://ftpmaster.internal/ubuntu/ lucid/main python-gobject 2.21.1-0ubuntu3 [199kB] Get:193 http://ftpmaster.internal/ubuntu/ lucid/main python-gtk2 2.17.0-0ubuntu2 [694kB] Get:194 http://ftpmaster.internal/ubuntu/ lucid/main python-vte 1:0.23.5-0ubuntu1 [14.9kB] Get:195 http://ftpmaster.internal/ubuntu/ lucid/main libvte-dev 1:0.23.5-0ubuntu1 [345kB] Get:196 http://ftpmaster.internal/ubuntu/ lucid/main libxslt1.1 1.1.26-1ubuntu1 [224kB] Get:197 http://ftpmaster.internal/ubuntu/ lucid/main libxt6 1:1.0.7-1 [156kB] Get:198 http://ftpmaster.internal/ubuntu/ lucid/main libwebkit-1.0-common 1.2.0-1 [613kB] Get:199 http://ftpmaster.internal/ubuntu/ lucid/main libwebkit-1.0-2 1.2.0-1 [4111kB] Get:200 http://ftpmaster.internal/ubuntu/ lucid/main libwnck-common 1:2.30.0-0ubuntu1 [19.8kB] Get:201 http://ftpmaster.internal/ubuntu/ lucid/main libwnck22 1:2.30.0-0ubuntu1 [103kB] Get:202 http://ftpmaster.internal/ubuntu/ lucid/main libwnck-dev 1:2.30.0-0ubuntu1 [206kB] Get:203 http://ftpmaster.internal/ubuntu/ lucid/main quilt 0.48-5 [318kB] Get:204 http://ftpmaster.internal/ubuntu/ lucid/universe vala-desktop-agnostic 0.0.1~bzr383-0ubuntu3 [7150B] Get:205 http://ftpmaster.internal/ubuntu/ lucid/universe vala-awn 0.4.0-0ubuntu1 [110kB] Get:206 http://ftpmaster.internal/ubuntu/ lucid/main valac 0.8.0-0ubuntu1 [682kB] Get:207 http://ftpmaster.internal/ubuntu/ lucid/universe libdesktop-agnostic-cfg-gconf 0.0.1~bzr383-0ubuntu3 [15.5kB] Get:208 http://ftpmaster.internal/ubuntu/ lucid/universe libdesktop-agnostic-bin 0.0.1~bzr383-0ubuntu3 [10.6kB] Get:209 http://ftpmaster.internal/ubuntu/ lucid/main libwebkit-dev 1.2.0-1 [127kB] debconf: delaying package configuration, since apt-utils is not installed Fetched 63.8MB in 11s (5731kB/s) Selecting previously deselected package x11-common. (Reading database ... 13244 files and directories currently installed.) Unpacking x11-common (from .../x11-common_1%3a7.5+5ubuntu1_all.deb) ... Selecting previously deselected package libice6. Unpacking libice6 (from .../libice6_2%3a1.0.6-1_armel.deb) ... Selecting previously deselected package x11proto-core-dev. Unpacking x11proto-core-dev (from .../x11proto-core-dev_7.0.16-1_all.deb) ... Setting up x11-common (1:7.5+5ubuntu1) ... Selecting previously deselected package libice-dev. (Reading database ... 13364 files and directories currently installed.) Unpacking libice-dev (from .../libice-dev_2%3a1.0.6-1_armel.deb) ... Selecting previously deselected package libxau6. Unpacking libxau6 (from .../libxau6_1%3a1.0.5-1_armel.deb) ... Selecting previously deselected package libxdmcp6. Unpacking libxdmcp6 (from .../libxdmcp6_1%3a1.0.3-1_armel.deb) ... Selecting previously deselected package libxcb1. Unpacking libxcb1 (from .../libxcb1_1.5-2_armel.deb) ... Selecting previously deselected package libx11-data. Unpacking libx11-data (from .../libx11-data_2%3a1.3.2-1ubuntu3_all.deb) ... Selecting previously deselected package libx11-6. Unpacking libx11-6 (from .../libx11-6_2%3a1.3.2-1ubuntu3_armel.deb) ... Selecting previously deselected package libxau-dev. Unpacking libxau-dev (from .../libxau-dev_1%3a1.0.5-1_armel.deb) ... Selecting previously deselected package libxdmcp-dev. Unpacking libxdmcp-dev (from .../libxdmcp-dev_1%3a1.0.3-1_armel.deb) ... Selecting previously deselected package x11proto-input-dev. Unpacking x11proto-input-dev (from .../x11proto-input-dev_2.0-2_all.deb) ... Selecting previously deselected package x11proto-kb-dev. Unpacking x11proto-kb-dev (from .../x11proto-kb-dev_1.0.4-1_all.deb) ... Selecting previously deselected package xtrans-dev. Unpacking xtrans-dev (from .../xtrans-dev_1.2.5-1_all.deb) ... Selecting previously deselected package libpthread-stubs0. Unpacking libpthread-stubs0 (from .../libpthread-stubs0_0.3-2_armel.deb) ... Selecting previously deselected package libpthread-stubs0-dev. Unpacking libpthread-stubs0-dev (from .../libpthread-stubs0-dev_0.3-2_armel.deb) ... Selecting previously deselected package libxcb1-dev. Unpacking libxcb1-dev (from .../libxcb1-dev_1.5-2_armel.deb) ... Selecting previously deselected package libx11-dev. Unpacking libx11-dev (from .../libx11-dev_2%3a1.3.2-1ubuntu3_armel.deb) ... Selecting previously deselected package libxext6. Unpacking libxext6 (from .../libxext6_2%3a1.1.1-2_armel.deb) ... Selecting previously deselected package libxfixes3. Unpacking libxfixes3 (from .../libxfixes3_1%3a4.0.4-1_armel.deb) ... Selecting previously deselected package libxcomposite1. Unpacking libxcomposite1 (from .../libxcomposite1_1%3a0.4.1-1_armel.deb) ... Selecting previously deselected package x11proto-xext-dev. Unpacking x11proto-xext-dev (from .../x11proto-xext-dev_7.1.1-2_all.deb) ... Selecting previously deselected package x11proto-fixes-dev. Unpacking x11proto-fixes-dev (from .../x11proto-fixes-dev_1%3a4.1.1-2_all.deb) ... Selecting previously deselected package libxfixes-dev. Unpacking libxfixes-dev (from .../libxfixes-dev_1%3a4.0.4-1_armel.deb) ... Selecting previously deselected package x11proto-composite-dev. Unpacking x11proto-composite-dev (from .../x11proto-composite-dev_1%3a0.4.1-1_all.deb) ... Selecting previously deselected package libxext-dev. Unpacking libxext-dev (from .../libxext-dev_2%3a1.1.1-2_armel.deb) ... Selecting previously deselected package libxcomposite-dev. Unpacking libxcomposite-dev (from .../libxcomposite-dev_1%3a0.4.1-1_armel.deb) ... Selecting previously deselected package libxres1. Unpacking libxres1 (from .../libxres1_2%3a1.0.4-1_armel.deb) ... Selecting previously deselected package x11proto-resource-dev. Unpacking x11proto-resource-dev (from .../x11proto-resource-dev_1.1.0-1_all.deb) ... Selecting previously deselected package libxres-dev. Unpacking libxres-dev (from .../libxres-dev_2%3a1.0.4-1_armel.deb) ... Selecting previously deselected package libmagic1. Unpacking libmagic1 (from .../libmagic1_5.03-5ubuntu1_armel.deb) ... Selecting previously deselected package file. Unpacking file (from .../file_5.03-5ubuntu1_armel.deb) ... Selecting previously deselected package libncursesw5. Unpacking libncursesw5 (from .../libncursesw5_5.7+20090803-2ubuntu3_armel.deb) ... Selecting previously deselected package libnewt0.52. Unpacking libnewt0.52 (from .../libnewt0.52_0.52.10-5ubuntu1_armel.deb) ... Selecting previously deselected package libpopt0. Unpacking libpopt0 (from .../libpopt0_1.15-1_armel.deb) ... Selecting previously deselected package libsqlite3-0. Unpacking libsqlite3-0 (from .../libsqlite3-0_3.6.22-1_armel.deb) ... Selecting previously deselected package mime-support. Unpacking mime-support (from .../mime-support_3.48-1ubuntu1_all.deb) ... Selecting previously deselected package python2.6. Unpacking python2.6 (from .../python2.6_2.6.5-1ubuntu6_armel.deb) ... Selecting previously deselected package python. Unpacking python (from .../python_2.6.5-0ubuntu1_all.deb) ... Selecting previously deselected package ucf. Unpacking ucf (from .../archives/ucf_3.0025_all.deb) ... Moving old data out of the way Selecting previously deselected package whiptail. Unpacking whiptail (from .../whiptail_0.52.10-5ubuntu1_armel.deb) ... Selecting previously deselected package bsdmainutils. Unpacking bsdmainutils (from .../bsdmainutils_8.0.1ubuntu1_armel.deb) ... Selecting previously deselected package gettext-base. Unpacking gettext-base (from .../gettext-base_0.17-8ubuntu3_armel.deb) ... Selecting previously deselected package groff-base. Unpacking groff-base (from .../groff-base_1.20.1-7_armel.deb) ... Selecting previously deselected package iso-codes. Unpacking iso-codes (from .../iso-codes_3.12.1-1_all.deb) ... Selecting previously deselected package libexpat1. Unpacking libexpat1 (from .../libexpat1_2.0.1-7ubuntu1_armel.deb) ... Selecting previously deselected package liburi-perl. Unpacking liburi-perl (from .../liburi-perl_1.52-1_all.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 libhtml-parser-perl. Unpacking libhtml-parser-perl (from .../libhtml-parser-perl_3.64-1_armel.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.834-1_all.deb) ... Selecting previously deselected package libxml-parser-perl. Unpacking libxml-parser-perl (from .../libxml-parser-perl_2.36-1.1build3_armel.deb) ... Selecting previously deselected package libxml2. Unpacking libxml2 (from .../libxml2_2.7.6.dfsg-1ubuntu1_armel.deb) ... Selecting previously deselected package man-db. Unpacking man-db (from .../man-db_2.5.7-2_armel.deb) ... Selecting previously deselected package psmisc. Unpacking psmisc (from .../psmisc_22.10-1_armel.deb) ... Selecting previously deselected package python-support. Unpacking python-support (from .../python-support_1.0.4ubuntu1_all.deb) ... Selecting previously deselected package m4. Unpacking m4 (from .../archives/m4_1.4.13-3_armel.deb) ... Selecting previously deselected package autoconf. Unpacking autoconf (from .../autoconf_2.65-3ubuntu1_all.deb) ... Selecting previously deselected package autotools-dev. Unpacking autotools-dev (from .../autotools-dev_20090611.1_all.deb) ... Selecting previously deselected package automake. Unpacking automake (from .../automake_1%3a1.11.1-1_all.deb) ... Selecting previously deselected package dbus. Unpacking dbus (from .../dbus_1.2.16-2ubuntu4_armel.deb) ... Selecting previously deselected package dbus-x11. Unpacking dbus-x11 (from .../dbus-x11_1.2.16-2ubuntu4_armel.deb) ... Selecting previously deselected package html2text. Unpacking html2text (from .../html2text_1.3.2a-14build1_armel.deb) ... Selecting previously deselected package libcroco3. Unpacking libcroco3 (from .../libcroco3_0.6.2-1_armel.deb) ... Selecting previously deselected package gettext. Unpacking gettext (from .../gettext_0.17-8ubuntu3_armel.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.16_all.deb) ... Selecting previously deselected package debhelper. Unpacking debhelper (from .../debhelper_7.4.15ubuntu1_all.deb) ... Selecting previously deselected package defoma. Unpacking defoma (from .../defoma_0.11.10-4_all.deb) ... Selecting previously deselected package diffstat. Unpacking diffstat (from .../diffstat_1.47-1build1_armel.deb) ... Selecting previously deselected package libfreetype6. Unpacking libfreetype6 (from .../libfreetype6_2.3.11-1ubuntu2_armel.deb) ... Selecting previously deselected package ttf-dejavu-core. Unpacking ttf-dejavu-core (from .../ttf-dejavu-core_2.30-2_all.deb) ... Selecting previously deselected package fontconfig-config. Unpacking fontconfig-config (from .../fontconfig-config_2.8.0-2ubuntu1_all.deb) ... Selecting previously deselected package libfontconfig1. Unpacking libfontconfig1 (from .../libfontconfig1_2.8.0-2ubuntu1_armel.deb) ... Selecting previously deselected package fontconfig. Unpacking fontconfig (from .../fontconfig_2.8.0-2ubuntu1_armel.deb) ... Selecting previously deselected package libdbus-glib-1-2. Unpacking libdbus-glib-1-2 (from .../libdbus-glib-1-2_0.84-1_armel.deb) ... Selecting previously deselected package libidl0. Unpacking libidl0 (from .../libidl0_0.8.13-1_armel.deb) ... Selecting previously deselected package liborbit2. Unpacking liborbit2 (from .../liborbit2_1%3a2.14.18-0.1_armel.deb) ... Selecting previously deselected package gconf2-common. Unpacking gconf2-common (from .../gconf2-common_2.28.1-0ubuntu1_all.deb) ... Selecting previously deselected package libgconf2-4. Unpacking libgconf2-4 (from .../libgconf2-4_2.28.1-0ubuntu1_armel.deb) ... Selecting previously deselected package gconf2. Unpacking gconf2 (from .../gconf2_2.28.1-0ubuntu1_armel.deb) ... Selecting previously deselected package intltool. Unpacking intltool (from .../intltool_0.41.0-0ubuntu1_all.deb) ... Selecting previously deselected package libaspell15. Unpacking libaspell15 (from .../libaspell15_0.60.6-3ubuntu1_armel.deb) ... Selecting previously deselected package libatk1.0-0. Unpacking libatk1.0-0 (from .../libatk1.0-0_1.30.0-0ubuntu2_armel.deb) ... Selecting previously deselected package pkg-config. Unpacking pkg-config (from .../pkg-config_0.22-1build2_armel.deb) ... Selecting previously deselected package zlib1g-dev. Unpacking zlib1g-dev (from .../zlib1g-dev_1%3a1.2.3.3.dfsg-15ubuntu1_armel.deb) ... Selecting previously deselected package libglib2.0-dev. Unpacking libglib2.0-dev (from .../libglib2.0-dev_2.24.0-0ubuntu2_armel.deb) ... Selecting previously deselected package libatk1.0-dev. Unpacking libatk1.0-dev (from .../libatk1.0-dev_1.30.0-0ubuntu2_armel.deb) ... Selecting previously deselected package libavahi-common-data. Unpacking libavahi-common-data (from .../libavahi-common-data_0.6.25-1ubuntu6_armel.deb) ... Selecting previously deselected package libavahi-common3. Unpacking libavahi-common3 (from .../libavahi-common3_0.6.25-1ubuntu6_armel.deb) ... Selecting previously deselected package libavahi-client3. Unpacking libavahi-client3 (from .../libavahi-client3_0.6.25-1ubuntu6_armel.deb) ... Selecting previously deselected package libsysfs2. Unpacking libsysfs2 (from .../libsysfs2_2.1.0-6_armel.deb) ... Selecting previously deselected package tsconf. Unpacking tsconf (from .../tsconf_1.0-7build1_all.deb) ... Selecting previously deselected package libts-0.0-0. Unpacking libts-0.0-0 (from .../libts-0.0-0_1.0-7build1_armel.deb) ... Selecting previously deselected package libdirectfb-1.2-0. Unpacking libdirectfb-1.2-0 (from .../libdirectfb-1.2-0_1.2.8-5ubuntu2_armel.deb) ... Selecting previously deselected package libpixman-1-0. Unpacking libpixman-1-0 (from .../libpixman-1-0_0.16.4-1ubuntu2_armel.deb) ... Selecting previously deselected package libxcb-render0. Unpacking libxcb-render0 (from .../libxcb-render0_1.5-2_armel.deb) ... Selecting previously deselected package libxcb-render-util0. Unpacking libxcb-render-util0 (from .../libxcb-render-util0_0.3.6-1build1_armel.deb) ... Selecting previously deselected package libxrender1. Unpacking libxrender1 (from .../libxrender1_1%3a0.9.5-1_armel.deb) ... Selecting previously deselected package libcairo2. Unpacking libcairo2 (from .../libcairo2_1.8.10-2ubuntu1_armel.deb) ... Selecting previously deselected package libgtk2.0-common. Unpacking libgtk2.0-common (from .../libgtk2.0-common_2.20.0-0ubuntu4_all.deb) ... Selecting previously deselected package libcups2. Unpacking libcups2 (from .../libcups2_1.4.3-1_armel.deb) ... Selecting previously deselected package libjpeg62. Unpacking libjpeg62 (from .../libjpeg62_6b-15ubuntu1_armel.deb) ... Selecting previously deselected package libjasper1. Unpacking libjasper1 (from .../libjasper1_1.900.1-7_armel.deb) ... Selecting previously deselected package libpango1.0-common. Unpacking libpango1.0-common (from .../libpango1.0-common_1.28.0-0ubuntu2_all.deb) ... Selecting previously deselected package libdatrie1. Unpacking libdatrie1 (from .../libdatrie1_0.2.2-3_armel.deb) ... Selecting previously deselected package libthai-data. Unpacking libthai-data (from .../libthai-data_0.1.13-1_all.deb) ... Selecting previously deselected package libthai0. Unpacking libthai0 (from .../libthai0_0.1.13-1_armel.deb) ... Selecting previously deselected package libxft2. Unpacking libxft2 (from .../libxft2_2.1.14-1ubuntu1_armel.deb) ... Selecting previously deselected package libpango1.0-0. Unpacking libpango1.0-0 (from .../libpango1.0-0_1.28.0-0ubuntu2_armel.deb) ... Selecting previously deselected package libtiff4. Unpacking libtiff4 (from .../libtiff4_3.9.2-2_armel.deb) ... Selecting previously deselected package libxcursor1. Unpacking libxcursor1 (from .../libxcursor1_1%3a1.1.10-1_armel.deb) ... Selecting previously deselected package libxdamage1. Unpacking libxdamage1 (from .../libxdamage1_1%3a1.1.2-1_armel.deb) ... Selecting previously deselected package libxi6. Unpacking libxi6 (from .../libxi6_2%3a1.3-3_armel.deb) ... Selecting previously deselected package libxinerama1. Unpacking libxinerama1 (from .../libxinerama1_2%3a1.1-2_armel.deb) ... Selecting previously deselected package libxrandr2. Unpacking libxrandr2 (from .../libxrandr2_2%3a1.3.0-3_armel.deb) ... Selecting previously deselected package shared-mime-info. Unpacking shared-mime-info (from .../shared-mime-info_0.71-1ubuntu1_armel.deb) ... Selecting previously deselected package libgtk2.0-0. Unpacking libgtk2.0-0 (from .../libgtk2.0-0_2.20.0-0ubuntu4_armel.deb) ... Selecting previously deselected package libdesktop-agnostic0. Unpacking libdesktop-agnostic0 (from .../libdesktop-agnostic0_0.0.1~bzr383-0ubuntu3_armel.deb) ... Selecting previously deselected package libawn1. Unpacking libawn1 (from .../libawn1_0.4.0-0ubuntu1_armel.deb) ... Selecting previously deselected package libfreetype6-dev. Unpacking libfreetype6-dev (from .../libfreetype6-dev_2.3.11-1ubuntu2_armel.deb) ... Selecting previously deselected package x11proto-render-dev. Unpacking x11proto-render-dev (from .../x11proto-render-dev_2%3a0.11-1_all.deb) ... Selecting previously deselected package libxrender-dev. Unpacking libxrender-dev (from .../libxrender-dev_1%3a0.9.5-1_armel.deb) ... Selecting previously deselected package libexpat1-dev. Unpacking libexpat1-dev (from .../libexpat1-dev_2.0.1-7ubuntu1_armel.deb) ... Selecting previously deselected package libfontconfig1-dev. Unpacking libfontconfig1-dev (from .../libfontconfig1-dev_2.8.0-2ubuntu1_armel.deb) ... Selecting previously deselected package libxft-dev. Unpacking libxft-dev (from .../libxft-dev_2.1.14-1ubuntu1_armel.deb) ... Selecting previously deselected package libpng12-dev. Unpacking libpng12-dev (from .../libpng12-dev_1.2.42-1ubuntu2_armel.deb) ... Selecting previously deselected package libdirectfb-extra. Unpacking libdirectfb-extra (from .../libdirectfb-extra_1.2.8-5ubuntu2_armel.deb) ... Selecting previously deselected package libjpeg62-dev. Unpacking libjpeg62-dev (from .../libjpeg62-dev_6b-15ubuntu1_armel.deb) ... Selecting previously deselected package libsysfs-dev. Unpacking libsysfs-dev (from .../libsysfs-dev_2.1.0-6_armel.deb) ... Selecting previously deselected package libdirectfb-dev. Unpacking libdirectfb-dev (from .../libdirectfb-dev_1.2.8-5ubuntu2_armel.deb) ... Selecting previously deselected package libsm6. Unpacking libsm6 (from .../libsm6_2%3a1.1.1-1_armel.deb) ... Selecting previously deselected package libsm-dev. Unpacking libsm-dev (from .../libsm-dev_2%3a1.1.1-1_armel.deb) ... Selecting previously deselected package libpixman-1-dev. Unpacking libpixman-1-dev (from .../libpixman-1-dev_0.16.4-1ubuntu2_armel.deb) ... Selecting previously deselected package libxcb-render0-dev. Unpacking libxcb-render0-dev (from .../libxcb-render0-dev_1.5-2_armel.deb) ... Selecting previously deselected package libxcb-render-util0-dev. Unpacking libxcb-render-util0-dev (from .../libxcb-render-util0-dev_0.3.6-1build1_armel.deb) ... Selecting previously deselected package libcairo2-dev. Unpacking libcairo2-dev (from .../libcairo2-dev_1.8.10-2ubuntu1_armel.deb) ... Selecting previously deselected package libpango1.0-dev. Unpacking libpango1.0-dev (from .../libpango1.0-dev_1.28.0-0ubuntu2_armel.deb) ... Selecting previously deselected package x11proto-xinerama-dev. Unpacking x11proto-xinerama-dev (from .../x11proto-xinerama-dev_1.2-2_all.deb) ... Selecting previously deselected package libxinerama-dev. Unpacking libxinerama-dev (from .../libxinerama-dev_2%3a1.1-2_armel.deb) ... Selecting previously deselected package libxi-dev. Unpacking libxi-dev (from .../libxi-dev_2%3a1.3-3_armel.deb) ... Selecting previously deselected package x11proto-randr-dev. Unpacking x11proto-randr-dev (from .../x11proto-randr-dev_1.3.1-1_all.deb) ... Selecting previously deselected package libxrandr-dev. Unpacking libxrandr-dev (from .../libxrandr-dev_2%3a1.3.0-3_armel.deb) ... Selecting previously deselected package libxcursor-dev. Unpacking libxcursor-dev (from .../libxcursor-dev_1%3a1.1.10-1_armel.deb) ... Selecting previously deselected package x11proto-damage-dev. Unpacking x11proto-damage-dev (from .../x11proto-damage-dev_1%3a1.2.0-1_all.deb) ... Selecting previously deselected package libxdamage-dev. Unpacking libxdamage-dev (from .../libxdamage-dev_1%3a1.1.2-1_armel.deb) ... Selecting previously deselected package libxml2-utils. Unpacking libxml2-utils (from .../libxml2-utils_2.7.6.dfsg-1ubuntu1_armel.deb) ... Selecting previously deselected package libgtk2.0-dev. Unpacking libgtk2.0-dev (from .../libgtk2.0-dev_2.20.0-0ubuntu4_armel.deb) ... Selecting previously deselected package libdesktop-agnostic-dev. Unpacking libdesktop-agnostic-dev (from .../libdesktop-agnostic-dev_0.0.1~bzr383-0ubuntu3_armel.deb) ... Selecting previously deselected package libdbus-1-dev. Unpacking libdbus-1-dev (from .../libdbus-1-dev_1.2.16-2ubuntu4_armel.deb) ... Selecting previously deselected package libdbus-glib-1-dev. Unpacking libdbus-glib-1-dev (from .../libdbus-glib-1-dev_0.84-1_armel.deb) ... Selecting previously deselected package libawn-dev. Unpacking libawn-dev (from .../libawn-dev_0.4.0-0ubuntu1_armel.deb) ... Selecting previously deselected package libhunspell-1.2-0. Unpacking libhunspell-1.2-0 (from .../libhunspell-1.2-0_1.2.8-6ubuntu1_armel.deb) ... Selecting previously deselected package libenchant1c2a. Unpacking libenchant1c2a (from .../libenchant1c2a_1.6.0-0ubuntu1_armel.deb) ... Selecting previously deselected package libgail18. Unpacking libgail18 (from .../libgail18_2.20.0-0ubuntu4_armel.deb) ... Selecting previously deselected package libidl-dev. Unpacking libidl-dev (from .../libidl-dev_0.8.13-1_armel.deb) ... Selecting previously deselected package liborbit2-dev. Unpacking liborbit2-dev (from .../liborbit2-dev_1%3a2.14.18-0.1_armel.deb) ... Selecting previously deselected package libgconf2-dev. Unpacking libgconf2-dev (from .../libgconf2-dev_2.28.1-0ubuntu1_armel.deb) ... Selecting previously deselected package libgpg-error-dev. Unpacking libgpg-error-dev (from .../libgpg-error-dev_1.6-1ubuntu2_armel.deb) ... Selecting previously deselected package libgcrypt11-dev. Unpacking libgcrypt11-dev (from .../libgcrypt11-dev_1.4.4-5ubuntu2_armel.deb) ... Selecting previously deselected package libgnome-menu2. Unpacking libgnome-menu2 (from .../libgnome-menu2_2.30.0-0ubuntu4_armel.deb) ... Selecting previously deselected package libgnome-menu-dev. Unpacking libgnome-menu-dev (from .../libgnome-menu-dev_2.30.0-0ubuntu4_armel.deb) ... Selecting previously deselected package libtasn1-3-dev. Unpacking libtasn1-3-dev (from .../libtasn1-3-dev_2.4-1_armel.deb) ... Selecting previously deselected package libgnutls-dev. Unpacking libgnutls-dev (from .../libgnutls-dev_2.8.5-2_armel.deb) ... Selecting previously deselected package libgsf-1-common. Unpacking libgsf-1-common (from .../libgsf-1-common_1.14.16-1ubuntu1_all.deb) ... Selecting previously deselected package libgsf-1-114. Unpacking libgsf-1-114 (from .../libgsf-1-114_1.14.16-1ubuntu1_armel.deb) ... Selecting previously deselected package libgstreamer0.10-0. Unpacking libgstreamer0.10-0 (from .../libgstreamer0.10-0_0.10.28-1_armel.deb) ... Selecting previously deselected package libgstreamer-plugins-base0.10-0. Unpacking libgstreamer-plugins-base0.10-0 (from .../libgstreamer-plugins-base0.10-0_0.10.28-1_armel.deb) ... Selecting previously deselected package libgtop2-common. Unpacking libgtop2-common (from .../libgtop2-common_2.26.1-0ubuntu2_all.deb) ... Selecting previously deselected package libgtop2-7. Unpacking libgtop2-7 (from .../libgtop2-7_2.26.1-0ubuntu2_armel.deb) ... Selecting previously deselected package libgtop2-dev. Unpacking libgtop2-dev (from .../libgtop2-dev_2.26.1-0ubuntu2_armel.deb) ... Selecting previously deselected package libicu42. Unpacking libicu42 (from .../libicu42_4.2.1-3_armel.deb) ... Selecting previously deselected package libnotify1. Unpacking libnotify1 (from .../libnotify1_0.4.5-1ubuntu3_armel.deb) ... Selecting previously deselected package libnotify-dev. Unpacking libnotify-dev (from .../libnotify-dev_0.4.5-1ubuntu3_armel.deb) ... Selecting previously deselected package librsvg2-2. Unpacking librsvg2-2 (from .../librsvg2-2_2.26.2-0ubuntu1_armel.deb) ... Selecting previously deselected package librsvg2-dev. Unpacking librsvg2-dev (from .../librsvg2-dev_2.26.2-0ubuntu1_armel.deb) ... Selecting previously deselected package libsexy2. Unpacking libsexy2 (from .../libsexy2_0.1.11-2build2_armel.deb) ... Selecting previously deselected package libxml2-dev. Unpacking libxml2-dev (from .../libxml2-dev_2.7.6.dfsg-1ubuntu1_armel.deb) ... Selecting previously deselected package libsexy-dev. Unpacking libsexy-dev (from .../libsexy-dev_0.1.11-2build2_armel.deb) ... Selecting previously deselected package libsoup2.4-1. Unpacking libsoup2.4-1 (from .../libsoup2.4-1_2.30.0-0ubuntu1_armel.deb) ... Selecting previously deselected package libsoup2.4-dev. Unpacking libsoup2.4-dev (from .../libsoup2.4-dev_2.30.0-0ubuntu1_armel.deb) ... Selecting previously deselected package libxcb-atom1. Unpacking libxcb-atom1 (from .../libxcb-atom1_0.3.6-1build1_armel.deb) ... Selecting previously deselected package libxcb-aux0. Unpacking libxcb-aux0 (from .../libxcb-aux0_0.3.6-1build1_armel.deb) ... Selecting previously deselected package libxcb-event1. Unpacking libxcb-event1 (from .../libxcb-event1_0.3.6-1build1_armel.deb) ... Selecting previously deselected package libstartup-notification0. Unpacking libstartup-notification0 (from .../libstartup-notification0_0.10-1build1_armel.deb) ... Selecting previously deselected package libstartup-notification0-dev. Unpacking libstartup-notification0-dev (from .../libstartup-notification0-dev_0.10-1build1_armel.deb) ... Selecting previously deselected package libvala0. Unpacking libvala0 (from .../libvala0_0.8.0-0ubuntu1_armel.deb) ... Selecting previously deselected package libvte-common. Unpacking libvte-common (from .../libvte-common_1%3a0.23.5-0ubuntu1_all.deb) ... Selecting previously deselected package libvte9. Unpacking libvte9 (from .../libvte9_1%3a0.23.5-0ubuntu1_armel.deb) ... Selecting previously deselected package python-cairo. Unpacking python-cairo (from .../python-cairo_1.8.8-1_armel.deb) ... Selecting previously deselected package libffi5. Unpacking libffi5 (from .../libffi5_3.0.9-1_armel.deb) ... Selecting previously deselected package python-gobject. Unpacking python-gobject (from .../python-gobject_2.21.1-0ubuntu3_armel.deb) ... Selecting previously deselected package python-gtk2. Unpacking python-gtk2 (from .../python-gtk2_2.17.0-0ubuntu2_armel.deb) ... Selecting previously deselected package python-vte. Unpacking python-vte (from .../python-vte_1%3a0.23.5-0ubuntu1_armel.deb) ... Selecting previously deselected package libvte-dev. Unpacking libvte-dev (from .../libvte-dev_1%3a0.23.5-0ubuntu1_armel.deb) ... Selecting previously deselected package libxslt1.1. Unpacking libxslt1.1 (from .../libxslt1.1_1.1.26-1ubuntu1_armel.deb) ... Selecting previously deselected package libxt6. Unpacking libxt6 (from .../libxt6_1%3a1.0.7-1_armel.deb) ... Selecting previously deselected package libwebkit-1.0-common. Unpacking libwebkit-1.0-common (from .../libwebkit-1.0-common_1.2.0-1_all.deb) ... Selecting previously deselected package libwebkit-1.0-2. Unpacking libwebkit-1.0-2 (from .../libwebkit-1.0-2_1.2.0-1_armel.deb) ... Selecting previously deselected package libwnck-common. Unpacking libwnck-common (from .../libwnck-common_1%3a2.30.0-0ubuntu1_all.deb) ... Selecting previously deselected package libwnck22. Unpacking libwnck22 (from .../libwnck22_1%3a2.30.0-0ubuntu1_armel.deb) ... Selecting previously deselected package libwnck-dev. Unpacking libwnck-dev (from .../libwnck-dev_1%3a2.30.0-0ubuntu1_armel.deb) ... Selecting previously deselected package quilt. Unpacking quilt (from .../archives/quilt_0.48-5_all.deb) ... Selecting previously deselected package vala-desktop-agnostic. Unpacking vala-desktop-agnostic (from .../vala-desktop-agnostic_0.0.1~bzr383-0ubuntu3_all.deb) ... Selecting previously deselected package vala-awn. Unpacking vala-awn (from .../vala-awn_0.4.0-0ubuntu1_all.deb) ... Selecting previously deselected package valac. Unpacking valac (from .../valac_0.8.0-0ubuntu1_armel.deb) ... Selecting previously deselected package libdesktop-agnostic-cfg-gconf. Unpacking libdesktop-agnostic-cfg-gconf (from .../libdesktop-agnostic-cfg-gconf_0.0.1~bzr383-0ubuntu3_armel.deb) ... Selecting previously deselected package libdesktop-agnostic-bin. Unpacking libdesktop-agnostic-bin (from .../libdesktop-agnostic-bin_0.0.1~bzr383-0ubuntu3_armel.deb) ... Selecting previously deselected package libwebkit-dev. Unpacking libwebkit-dev (from .../libwebkit-dev_1.2.0-1_armel.deb) ... Setting up libice6 (2:1.0.6-1) ... Setting up x11proto-core-dev (7.0.16-1) ... Setting up libice-dev (2:1.0.6-1) ... Setting up libxau6 (1:1.0.5-1) ... Setting up libxdmcp6 (1:1.0.3-1) ... Setting up libxcb1 (1.5-2) ... Setting up libx11-data (2:1.3.2-1ubuntu3) ... Setting up libx11-6 (2:1.3.2-1ubuntu3) ... Setting up libxau-dev (1:1.0.5-1) ... Setting up libxdmcp-dev (1:1.0.3-1) ... Setting up x11proto-input-dev (2.0-2) ... Setting up x11proto-kb-dev (1.0.4-1) ... Setting up xtrans-dev (1.2.5-1) ... Setting up libpthread-stubs0 (0.3-2) ... Setting up libpthread-stubs0-dev (0.3-2) ... Setting up libxcb1-dev (1.5-2) ... Setting up libx11-dev (2:1.3.2-1ubuntu3) ... Setting up libxext6 (2:1.1.1-2) ... Setting up libxfixes3 (1:4.0.4-1) ... Setting up libxcomposite1 (1:0.4.1-1) ... Setting up x11proto-xext-dev (7.1.1-2) ... Setting up x11proto-fixes-dev (1:4.1.1-2) ... Setting up libxfixes-dev (1:4.0.4-1) ... Setting up x11proto-composite-dev (1:0.4.1-1) ... Setting up libxext-dev (2:1.1.1-2) ... Setting up libxcomposite-dev (1:0.4.1-1) ... Setting up libxres1 (2:1.0.4-1) ... Setting up x11proto-resource-dev (1.1.0-1) ... Setting up libxres-dev (2:1.0.4-1) ... Setting up libmagic1 (5.03-5ubuntu1) ... Setting up file (5.03-5ubuntu1) ... Setting up libncursesw5 (5.7+20090803-2ubuntu3) ... Setting up libnewt0.52 (0.52.10-5ubuntu1) ... Setting up libpopt0 (1.15-1) ... Setting up libsqlite3-0 (3.6.22-1) ... Setting up mime-support (3.48-1ubuntu1) ... update-alternatives: using /usr/bin/see to provide /usr/bin/view (view) in auto mode. Setting up python2.6 (2.6.5-1ubuntu6) ... Setting up python (2.6.5-0ubuntu1) ... Setting up ucf (3.0025) ... Setting up whiptail (0.52.10-5ubuntu1) ... Setting up bsdmainutils (8.0.1ubuntu1) ... update-alternatives: using /usr/bin/bsd-write to provide /usr/bin/write (write) in auto mode. Setting up gettext-base (0.17-8ubuntu3) ... Setting up groff-base (1.20.1-7) ... Setting up iso-codes (3.12.1-1) ... Setting up libexpat1 (2.0.1-7ubuntu1) ... Setting up liburi-perl (1.52-1) ... Setting up libhtml-tagset-perl (3.20-2) ... Setting up libhtml-parser-perl (3.64-1) ... Setting up libhtml-tree-perl (3.23-1) ... Setting up libwww-perl (5.834-1) ... Setting up libxml-parser-perl (2.36-1.1build3) ... Setting up libxml2 (2.7.6.dfsg-1ubuntu1) ... Setting up man-db (2.5.7-2) ... Building database of manual pages ... Setting up psmisc (22.10-1) ... Setting up python-support (1.0.4ubuntu1) ... Setting up m4 (1.4.13-3) ... Setting up autoconf (2.65-3ubuntu1) ... Setting up autotools-dev (20090611.1) ... Setting up automake (1:1.11.1-1) ... update-alternatives: using /usr/bin/automake-1.11 to provide /usr/bin/automake (automake) in auto mode. Setting up dbus (1.2.16-2ubuntu4) ... Adding system user `messagebus' (UID 101) ... Adding new group `messagebus' (GID 102) ... Adding new user `messagebus' (UID 101) with group `messagebus' ... Not creating home directory `/var/run/dbus'. Setting up dbus-x11 (1.2.16-2ubuntu4) ... Setting up html2text (1.3.2a-14build1) ... Setting up libcroco3 (0.6.2-1) ... Setting up gettext (0.17-8ubuntu3) ... Setting up intltool-debian (0.35.0+20060710.1) ... Setting up po-debconf (1.0.16) ... Setting up debhelper (7.4.15ubuntu1) ... Setting up defoma (0.11.10-4) ... Setting up diffstat (1.47-1build1) ... Setting up libfreetype6 (2.3.11-1ubuntu2) ... Setting up ttf-dejavu-core (2.30-2) ... Setting up fontconfig-config (2.8.0-2ubuntu1) ... Setting up libfontconfig1 (2.8.0-2ubuntu1) ... Setting up fontconfig (2.8.0-2ubuntu1) ... 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.. Cleaning up old fontconfig caches... done. Regenerating fonts cache... done. Setting up libdbus-glib-1-2 (0.84-1) ... Setting up libidl0 (0.8.13-1) ... Setting up liborbit2 (1:2.14.18-0.1) ... Setting up gconf2-common (2.28.1-0ubuntu1) ... Creating config file /etc/gconf/2/path with new version Setting up libgconf2-4 (2.28.1-0ubuntu1) ... Setting up gconf2 (2.28.1-0ubuntu1) ... update-alternatives: using /usr/bin/gconftool-2 to provide /usr/bin/gconftool (gconftool) in auto mode. Setting up intltool (0.41.0-0ubuntu1) ... Setting up libaspell15 (0.60.6-3ubuntu1) ... Setting up libatk1.0-0 (1.30.0-0ubuntu2) ... Setting up pkg-config (0.22-1build2) ... Setting up zlib1g-dev (1:1.2.3.3.dfsg-15ubuntu1) ... Setting up libglib2.0-dev (2.24.0-0ubuntu2) ... Setting up libatk1.0-dev (1.30.0-0ubuntu2) ... Setting up libavahi-common-data (0.6.25-1ubuntu6) ... Setting up libavahi-common3 (0.6.25-1ubuntu6) ... Setting up libavahi-client3 (0.6.25-1ubuntu6) ... Setting up libsysfs2 (2.1.0-6) ... Setting up tsconf (1.0-7build1) ... Setting up libts-0.0-0 (1.0-7build1) ... Setting up libdirectfb-1.2-0 (1.2.8-5ubuntu2) ... Setting up libpixman-1-0 (0.16.4-1ubuntu2) ... Setting up libxcb-render0 (1.5-2) ... Setting up libxcb-render-util0 (0.3.6-1build1) ... Setting up libxrender1 (1:0.9.5-1) ... Setting up libcairo2 (1.8.10-2ubuntu1) ... Setting up libgtk2.0-common (2.20.0-0ubuntu4) ... Setting up libcups2 (1.4.3-1) ... Setting up libjpeg62 (6b-15ubuntu1) ... Setting up libjasper1 (1.900.1-7) ... Setting up libpango1.0-common (1.28.0-0ubuntu2) ... 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 libdatrie1 (0.2.2-3) ... Setting up libthai-data (0.1.13-1) ... Setting up libthai0 (0.1.13-1) ... Setting up libxft2 (2.1.14-1ubuntu1) ... Setting up libpango1.0-0 (1.28.0-0ubuntu2) ... Setting up libtiff4 (3.9.2-2) ... Setting up libxcursor1 (1:1.1.10-1) ... Setting up libxdamage1 (1:1.1.2-1) ... Setting up libxi6 (2:1.3-3) ... Setting up libxinerama1 (2:1.1-2) ... Setting up libxrandr2 (2:1.3.0-3) ... Setting up shared-mime-info (0.71-1ubuntu1) ... Setting up libgtk2.0-0 (2.20.0-0ubuntu4) ... Setting up libdesktop-agnostic0 (0.0.1~bzr383-0ubuntu3) ... Setting up libawn1 (0.4.0-0ubuntu1) ... Setting up libfreetype6-dev (2.3.11-1ubuntu2) ... Setting up x11proto-render-dev (2:0.11-1) ... Setting up libxrender-dev (1:0.9.5-1) ... Setting up libexpat1-dev (2.0.1-7ubuntu1) ... Setting up libfontconfig1-dev (2.8.0-2ubuntu1) ... Setting up libxft-dev (2.1.14-1ubuntu1) ... Setting up libpng12-dev (1.2.42-1ubuntu2) ... Setting up libdirectfb-extra (1.2.8-5ubuntu2) ... Setting up libjpeg62-dev (6b-15ubuntu1) ... Setting up libsysfs-dev (2.1.0-6) ... Setting up libdirectfb-dev (1.2.8-5ubuntu2) ... Setting up libsm6 (2:1.1.1-1) ... Setting up libsm-dev (2:1.1.1-1) ... Setting up libpixman-1-dev (0.16.4-1ubuntu2) ... Setting up libxcb-render0-dev (1.5-2) ... Setting up libxcb-render-util0-dev (0.3.6-1build1) ... Setting up libcairo2-dev (1.8.10-2ubuntu1) ... Setting up libpango1.0-dev (1.28.0-0ubuntu2) ... Setting up x11proto-xinerama-dev (1.2-2) ... Setting up libxinerama-dev (2:1.1-2) ... Setting up libxi-dev (2:1.3-3) ... Setting up x11proto-randr-dev (1.3.1-1) ... Setting up libxrandr-dev (2:1.3.0-3) ... Setting up libxcursor-dev (1:1.1.10-1) ... Setting up x11proto-damage-dev (1:1.2.0-1) ... Setting up libxdamage-dev (1:1.1.2-1) ... Setting up libxml2-utils (2.7.6.dfsg-1ubuntu1) ... Setting up libgtk2.0-dev (2.20.0-0ubuntu4) ... Setting up libdesktop-agnostic-dev (0.0.1~bzr383-0ubuntu3) ... Setting up libdbus-1-dev (1.2.16-2ubuntu4) ... Setting up libdbus-glib-1-dev (0.84-1) ... Setting up libawn-dev (0.4.0-0ubuntu1) ... Setting up libhunspell-1.2-0 (1.2.8-6ubuntu1) ... Setting up libenchant1c2a (1.6.0-0ubuntu1) ... Setting up libgail18 (2.20.0-0ubuntu4) ... Setting up libidl-dev (0.8.13-1) ... Setting up liborbit2-dev (1:2.14.18-0.1) ... Setting up libgconf2-dev (2.28.1-0ubuntu1) ... Setting up libgpg-error-dev (1.6-1ubuntu2) ... Setting up libgcrypt11-dev (1.4.4-5ubuntu2) ... Setting up libgnome-menu2 (2.30.0-0ubuntu4) ... Setting up libgnome-menu-dev (2.30.0-0ubuntu4) ... Setting up libtasn1-3-dev (2.4-1) ... Setting up libgnutls-dev (2.8.5-2) ... Setting up libgsf-1-common (1.14.16-1ubuntu1) ... Setting up libgsf-1-114 (1.14.16-1ubuntu1) ... Setting up libgstreamer0.10-0 (0.10.28-1) ... Setting up libgstreamer-plugins-base0.10-0 (0.10.28-1) ... Setting up libgtop2-common (2.26.1-0ubuntu2) ... Setting up libgtop2-7 (2.26.1-0ubuntu2) ... Setting up libgtop2-dev (2.26.1-0ubuntu2) ... Setting up libicu42 (4.2.1-3) ... Setting up libnotify1 (0.4.5-1ubuntu3) ... Setting up libnotify-dev (0.4.5-1ubuntu3) ... Setting up librsvg2-2 (2.26.2-0ubuntu1) ... Setting up librsvg2-dev (2.26.2-0ubuntu1) ... Setting up libsexy2 (0.1.11-2build2) ... Setting up libxml2-dev (2.7.6.dfsg-1ubuntu1) ... Setting up libsexy-dev (0.1.11-2build2) ... Setting up libsoup2.4-1 (2.30.0-0ubuntu1) ... Setting up libsoup2.4-dev (2.30.0-0ubuntu1) ... Setting up libxcb-atom1 (0.3.6-1build1) ... Setting up libxcb-aux0 (0.3.6-1build1) ... Setting up libxcb-event1 (0.3.6-1build1) ... Setting up libstartup-notification0 (0.10-1build1) ... Setting up libstartup-notification0-dev (0.10-1build1) ... Setting up libvala0 (0.8.0-0ubuntu1) ... Setting up libvte-common (1:0.23.5-0ubuntu1) ... Setting up libvte9 (1:0.23.5-0ubuntu1) ... Setting up python-cairo (1.8.8-1) ... Setting up libffi5 (3.0.9-1) ... Setting up python-gobject (2.21.1-0ubuntu3) ... Setting up python-gtk2 (2.17.0-0ubuntu2) ... Setting up python-vte (1:0.23.5-0ubuntu1) ... Setting up libvte-dev (1:0.23.5-0ubuntu1) ... Setting up libxslt1.1 (1.1.26-1ubuntu1) ... Setting up libxt6 (1:1.0.7-1) ... Setting up libwebkit-1.0-common (1.2.0-1) ... Setting up libwebkit-1.0-2 (1.2.0-1) ... Setting up libwnck-common (1:2.30.0-0ubuntu1) ... Setting up libwnck22 (1:2.30.0-0ubuntu1) ... Setting up libwnck-dev (1:2.30.0-0ubuntu1) ... Setting up quilt (0.48-5) ... Setting up vala-desktop-agnostic (0.0.1~bzr383-0ubuntu3) ... Setting up vala-awn (0.4.0-0ubuntu1) ... Setting up valac (0.8.0-0ubuntu1) ... Setting up libdesktop-agnostic-cfg-gconf (0.0.1~bzr383-0ubuntu3) ... Setting up libdesktop-agnostic-bin (0.0.1~bzr383-0ubuntu3) ... Setting up libwebkit-dev (1.2.0-1) ... Processing triggers for libc-bin ... ldconfig deferred processing now taking place Processing triggers for python-support ... Checking correctness of source dependencies... Toolchain package versions: libc6-dev_2.11.1-0ubuntu5 make_3.81-7ubuntu1 dpkg-dev_1.15.5.6ubuntu4 g++-4.4_4.4.3-4ubuntu5 gcc-4.4_4.4.3-4ubuntu5 binutils_2.20.1-3ubuntu4 libstdc++6_4.4.3-4ubuntu5 libstdc++6-4.4-dev_4.4.3-4ubuntu5 ------------------------------------------------------------------------------ gpgv: Signature made Sun Apr 11 20:40:13 2010 UTC using DSA key ID 491E5389 gpgv: Can't check signature: public key not found dpkg-source: warning: failed to verify signature on ./awn-extras-applets_0.4.0-0ubuntu1.dsc dpkg-source: info: 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.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 dpkg-buildpackage: host architecture armel /usr/bin/fakeroot debian/rules clean dh --with quilt clean dh_testdir dh_auto_clean dh_quilt_unpatch No patch removed dh_clean debian/rules build dh --with quilt build dh_testdir dh_quilt_patch 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 debian/rules override_dh_auto_configure make[1]: Entering directory `/build/buildd/awn-extras-applets-0.4.0' ./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... gcc3 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) gcc3 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... armv7l-unknown-linux-gnueabi checking host system type... armv7l-unknown-linux-gnueabi 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... 805306365 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) 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... no, falling back to libtool checking whether NLS is requested... yes checking for intltool >= 0.34... 0.41.0 found checking for intltool-update... /usr/bin/intltool-update checking for intltool-merge... /usr/bin/intltool-merge checking for intltool-extract... /usr/bin/intltool-extract checking for xgettext... /usr/bin/xgettext checking for msgmerge... /usr/bin/msgmerge checking for msgfmt... /usr/bin/msgfmt checking for gmsgfmt... /usr/bin/msgfmt checking for perl... /usr/bin/perl checking for perl >= 5.8.1... 5.10.1 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 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.16 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 make[1]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0' 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 /usr/include/libawn/awn-utils.h:88: note: expected 'struct GtkMenu *' but argument is of type 'struct GtkWidget *' 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 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' debian/rules override_dh_auto_test make[1]: Entering directory `/build/buildd/awn-extras-applets-0.4.0' #Pass, tests don't pass for now. make[1]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0' /usr/bin/fakeroot debian/rules binary-arch dh --with quilt binary-arch dh_testroot -a dh_prep -a dh_installdirs -a dh_auto_install -a 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 '/bin/bash ../../../libtool' --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:6151): 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:6192): 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:6261): 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:6339): 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:6426): 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:6522): 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:6609): 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 '/bin/bash ../../../libtool' --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:6707): 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:6758): 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:6827): 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:6887): 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:7001): 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:7106): 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:7225): 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:7294): 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 '/bin/bash ../../../libtool' --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:7386): 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:7427): 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:7478): 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 '/bin/bash ../../../libtool' --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:7570): 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 '/bin/bash ../../../libtool' --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:7643): 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:7734): 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:7826): 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:7922): 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 '/bin/bash ../../../libtool' --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:8034): 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 '/bin/bash ../../../libtool' --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:8100): 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 '/bin/bash ../../../libtool' --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 '/bin/bash ../../../libtool' --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:8221): 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:8253): 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 '/bin/bash ../../../libtool' --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:8348): 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 '/bin/bash ../../../libtool' --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:8412): 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 '/bin/bash ../../../libtool' --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 '/bin/bash ../../../libtool' --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:8571): 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:8631): 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 '/bin/bash ../../../libtool' --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:8755): 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 -a dh_installdocs -a dh_installchangelogs -a dh_installexamples -a dh_installman -a dh_installcatalogs -a dh_installcron -a dh_installdebconf -a dh_installemacsen -a dh_installifupdown -a dh_installinfo -a dh_pysupport -a dh_installinit -a Duplicate specification "O=s" for option "O" dh_installmenu -a dh_installmime -a dh_installmodules -a dh_installlogcheck -a dh_installlogrotate -a dh_installpam -a dh_installppp -a dh_installudev -a dh_installwm -a dh_installxfonts -a dh_bugfiles -a dh_lintian -a dh_gconf -a dh_icons -a dh_perl -a dh_usrlocal -a dh_link -a dh_compress -a dh_fixperms -a debian/rules override_dh_strip make[1]: Entering directory `/build/buildd/awn-extras-applets-0.4.0' dh_strip --dbg-package=awn-applets-c-dbg dh_strip debug symbol extraction: all non-arch-all packages for this build platform armel: awn-applets-c-core awn-applets-c-extras python-awn-extras awn-applets-c-dbg dh_strip debug symbol extraction: not adding gnu debuglinks since --dbg-package is given dh_strip debug symbol extraction: packages to act on: awn-applets-c-core awn-applets-c-extras python-awn-extras awn-applets-c-dbg dh_strip debug symbol extraction: ignored packages: WARNING: not running pkgbinarymangler for this package, as requested dpkg-deb: warning: '/build/buildd/awn-extras-applets-0.4.0/debian/awn-applets-c-core-dbgsym/DEBIAN/control' contains user-defined field 'Original-Maintainer' dpkg-deb: warning: ignoring 1 warnings about the control file(s) dpkg-deb: building package `awn-applets-c-core-dbgsym' in `../awn-applets-c-core-dbgsym_0.4.0-0ubuntu1_armel.ddeb'. WARNING: not running pkgbinarymangler for this package, as requested dpkg-deb: warning: '/build/buildd/awn-extras-applets-0.4.0/debian/awn-applets-c-extras-dbgsym/DEBIAN/control' contains user-defined field 'Original-Maintainer' dpkg-deb: warning: ignoring 1 warnings about the control file(s) dpkg-deb: building package `awn-applets-c-extras-dbgsym' in `../awn-applets-c-extras-dbgsym_0.4.0-0ubuntu1_armel.ddeb'. make[1]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0' debian/rules override_dh_makeshlibs make[1]: Entering directory `/build/buildd/awn-extras-applets-0.4.0' dh_makeshlibs -a -n --exclude=* make[1]: Leaving directory `/build/buildd/awn-extras-applets-0.4.0' dh_shlibdeps -a dpkg-shlibdeps: warning: debian/awn-applets-c-core/usr/lib/awn/applets/awnterm/awnterm.so contains an unresolvable reference to symbol XKeysymToKeycode: it's probably a plugin. dpkg-shlibdeps: warning: 4 other similar warnings have been skipped (use -v to see them all). 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/cairo-menu/cairo-menu.so debian/awn-applets-c-core/usr/lib/awn/applets/shinyswitcher/shinyswitcher.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/showdesktop/showdesktop.so debian/awn-applets-c-core/usr/lib/awn/applets/garbage/garbage.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/cairo-menu/cairo-menu.so debian/awn-applets-c-core/usr/lib/awn/applets/shinyswitcher/shinyswitcher.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/showdesktop/showdesktop.so debian/awn-applets-c-core/usr/lib/awn/applets/garbage/garbage.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 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/cairo-menu/cairo-menu.so debian/awn-applets-c-core/usr/lib/awn/applets/shinyswitcher/shinyswitcher.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/showdesktop/showdesktop.so debian/awn-applets-c-core/usr/lib/awn/applets/garbage/garbage.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/cairo-menu/cairo-menu.so debian/awn-applets-c-core/usr/lib/awn/applets/shinyswitcher/shinyswitcher.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/showdesktop/showdesktop.so debian/awn-applets-c-core/usr/lib/awn/applets/garbage/garbage.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 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/cairo-menu/cairo-menu.so debian/awn-applets-c-core/usr/lib/awn/applets/shinyswitcher/shinyswitcher.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/showdesktop/showdesktop.so debian/awn-applets-c-core/usr/lib/awn/applets/garbage/garbage.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 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/cairo-menu/cairo-menu.so debian/awn-applets-c-core/usr/lib/awn/applets/shinyswitcher/shinyswitcher.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/showdesktop/showdesktop.so debian/awn-applets-c-core/usr/lib/awn/applets/garbage/garbage.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 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 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 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 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 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 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 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 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 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 libsoup-2.4.so.1 could be avoided if "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: unused substitution variable ${python:Versions} dpkg-gencontrol: warning: unknown substitution variable ${shlibs:Depends} dh_md5sums -a dh_builddeb -a pkgstriptranslations: processing control file: ./debian/awn-applets-c-core/DEBIAN/control, package awn-applets-c-core, directory ./debian/awn-applets-c-core ./debian/awn-applets-c-core/usr/share/avant-window-navigator/applets/showdesktop.desktop: does not have gettext domain, not stripping ./debian/awn-applets-c-core/usr/share/avant-window-navigator/applets/places.desktop: does not have gettext domain, not stripping ./debian/awn-applets-c-core/usr/share/avant-window-navigator/applets/sysmon.desktop: does not have gettext domain, not stripping ./debian/awn-applets-c-core/usr/share/avant-window-navigator/applets/garbage.desktop: does not have gettext domain, not stripping ./debian/awn-applets-c-core/usr/share/avant-window-navigator/applets/cairo-menu.desktop: does not have gettext domain, not stripping ./debian/awn-applets-c-core/usr/share/avant-window-navigator/applets/notification-daemon.desktop: does not have gettext domain, not stripping ./debian/awn-applets-c-core/usr/share/avant-window-navigator/applets/notification-area.desktop: does not have gettext domain, not stripping ./debian/awn-applets-c-core/usr/share/avant-window-navigator/applets/shinyswitcher.desktop: does not have gettext domain, not stripping ./debian/awn-applets-c-core/usr/share/avant-window-navigator/applets/awnterm.desktop: does not have gettext domain, not stripping pkgstriptranslations: awn-applets-c-core does not contain translations, skipping pkgstriptranslations: processing control file: ./debian/awn-applets-c-dbg/DEBIAN/control, package awn-applets-c-dbg, directory ./debian/awn-applets-c-dbg pkgstriptranslations: awn-applets-c-dbg does not contain translations, skipping pkgstriptranslations: processing control file: ./debian/awn-applets-c-extras/DEBIAN/control, package awn-applets-c-extras, directory ./debian/awn-applets-c-extras ./debian/awn-applets-c-extras/usr/share/avant-window-navigator/applets/main-menu.desktop: does not have gettext domain, not stripping ./debian/awn-applets-c-extras/usr/share/avant-window-navigator/applets/webapplet.desktop: does not have gettext domain, not stripping ./debian/awn-applets-c-extras/usr/share/avant-window-navigator/applets/awnsystemmonitor.desktop: does not have gettext domain, not stripping ./debian/awn-applets-c-extras/usr/share/avant-window-navigator/applets/digital-clock.desktop: does not have gettext domain, not stripping pkgstriptranslations: awn-applets-c-extras does not contain translations, skipping pkgstriptranslations: processing control file: ./debian/python-awn-extras/DEBIAN/control, package python-awn-extras, directory ./debian/python-awn-extras pkgstriptranslations: python-awn-extras does not contain translations, skipping pkgstriptranslations: preparing translation tarball awn-extras-applets_0.4.0-0ubuntu1_armel_translations.tar.gz...done (40 files) pkgmaintainermangler: Not overriding Maintainer for domain lists.ubuntu.com dpkg-deb: warning: 'debian/awn-applets-c-core/DEBIAN/control' contains user-defined field 'Original-Maintainer' dpkg-deb: warning: 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_armel.deb'. pkgstriptranslations: processing control file: ./debian/awn-applets-c-core/DEBIAN/control, package awn-applets-c-core, directory ./debian/awn-applets-c-core ./debian/awn-applets-c-core/usr/share/avant-window-navigator/applets/showdesktop.desktop: does not have gettext domain, not stripping ./debian/awn-applets-c-core/usr/share/avant-window-navigator/applets/places.desktop: does not have gettext domain, not stripping ./debian/awn-applets-c-core/usr/share/avant-window-navigator/applets/sysmon.desktop: does not have gettext domain, not stripping ./debian/awn-applets-c-core/usr/share/avant-window-navigator/applets/garbage.desktop: does not have gettext domain, not stripping ./debian/awn-applets-c-core/usr/share/avant-window-navigator/applets/cairo-menu.desktop: does not have gettext domain, not stripping ./debian/awn-applets-c-core/usr/share/avant-window-navigator/applets/notification-daemon.desktop: does not have gettext domain, not stripping ./debian/awn-applets-c-core/usr/share/avant-window-navigator/applets/notification-area.desktop: does not have gettext domain, not stripping ./debian/awn-applets-c-core/usr/share/avant-window-navigator/applets/shinyswitcher.desktop: does not have gettext domain, not stripping ./debian/awn-applets-c-core/usr/share/avant-window-navigator/applets/awnterm.desktop: does not have gettext domain, not stripping pkgstriptranslations: awn-applets-c-core does not contain translations, skipping pkgstriptranslations: processing control file: ./debian/awn-applets-c-dbg/DEBIAN/control, package awn-applets-c-dbg, directory ./debian/awn-applets-c-dbg pkgstriptranslations: awn-applets-c-dbg does not contain translations, skipping pkgstriptranslations: processing control file: ./debian/awn-applets-c-extras/DEBIAN/control, package awn-applets-c-extras, directory ./debian/awn-applets-c-extras ./debian/awn-applets-c-extras/usr/share/avant-window-navigator/applets/main-menu.desktop: does not have gettext domain, not stripping ./debian/awn-applets-c-extras/usr/share/avant-window-navigator/applets/webapplet.desktop: does not have gettext domain, not stripping ./debian/awn-applets-c-extras/usr/share/avant-window-navigator/applets/awnsystemmonitor.desktop: does not have gettext domain, not stripping ./debian/awn-applets-c-extras/usr/share/avant-window-navigator/applets/digital-clock.desktop: does not have gettext domain, not stripping pkgstriptranslations: awn-applets-c-extras does not contain translations, skipping pkgstriptranslations: processing control file: ./debian/python-awn-extras/DEBIAN/control, package python-awn-extras, directory ./debian/python-awn-extras pkgstriptranslations: python-awn-extras does not contain translations, skipping pkgstriptranslations: tarball already exists pkgmaintainermangler: Not overriding Maintainer for domain lists.ubuntu.com dpkg-deb: warning: 'debian/awn-applets-c-extras/DEBIAN/control' contains user-defined field 'Original-Maintainer' dpkg-deb: warning: 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_armel.deb'. pkgstriptranslations: processing control file: ./debian/awn-applets-c-core/DEBIAN/control, package awn-applets-c-core, directory ./debian/awn-applets-c-core ./debian/awn-applets-c-core/usr/share/avant-window-navigator/applets/showdesktop.desktop: does not have gettext domain, not stripping ./debian/awn-applets-c-core/usr/share/avant-window-navigator/applets/places.desktop: does not have gettext domain, not stripping ./debian/awn-applets-c-core/usr/share/avant-window-navigator/applets/sysmon.desktop: does not have gettext domain, not stripping ./debian/awn-applets-c-core/usr/share/avant-window-navigator/applets/garbage.desktop: does not have gettext domain, not stripping ./debian/awn-applets-c-core/usr/share/avant-window-navigator/applets/cairo-menu.desktop: does not have gettext domain, not stripping ./debian/awn-applets-c-core/usr/share/avant-window-navigator/applets/notification-daemon.desktop: does not have gettext domain, not stripping ./debian/awn-applets-c-core/usr/share/avant-window-navigator/applets/notification-area.desktop: does not have gettext domain, not stripping ./debian/awn-applets-c-core/usr/share/avant-window-navigator/applets/shinyswitcher.desktop: does not have gettext domain, not stripping ./debian/awn-applets-c-core/usr/share/avant-window-navigator/applets/awnterm.desktop: does not have gettext domain, not stripping pkgstriptranslations: awn-applets-c-core does not contain translations, skipping pkgstriptranslations: processing control file: ./debian/awn-applets-c-dbg/DEBIAN/control, package awn-applets-c-dbg, directory ./debian/awn-applets-c-dbg pkgstriptranslations: awn-applets-c-dbg does not contain translations, skipping pkgstriptranslations: processing control file: ./debian/awn-applets-c-extras/DEBIAN/control, package awn-applets-c-extras, directory ./debian/awn-applets-c-extras ./debian/awn-applets-c-extras/usr/share/avant-window-navigator/applets/main-menu.desktop: does not have gettext domain, not stripping ./debian/awn-applets-c-extras/usr/share/avant-window-navigator/applets/webapplet.desktop: does not have gettext domain, not stripping ./debian/awn-applets-c-extras/usr/share/avant-window-navigator/applets/awnsystemmonitor.desktop: does not have gettext domain, not stripping ./debian/awn-applets-c-extras/usr/share/avant-window-navigator/applets/digital-clock.desktop: does not have gettext domain, not stripping pkgstriptranslations: awn-applets-c-extras does not contain translations, skipping pkgstriptranslations: processing control file: ./debian/python-awn-extras/DEBIAN/control, package python-awn-extras, directory ./debian/python-awn-extras pkgstriptranslations: python-awn-extras does not contain translations, skipping pkgstriptranslations: tarball already exists pkgmaintainermangler: Not overriding Maintainer for domain lists.ubuntu.com dpkg-deb: warning: 'debian/python-awn-extras/DEBIAN/control' contains user-defined field 'Original-Maintainer' dpkg-deb: warning: ignoring 1 warnings about the control file(s) dpkg-deb: building package `python-awn-extras' in `../python-awn-extras_0.4.0-0ubuntu1_armel.deb'. pkgstriptranslations: processing control file: ./debian/awn-applets-c-core/DEBIAN/control, package awn-applets-c-core, directory ./debian/awn-applets-c-core ./debian/awn-applets-c-core/usr/share/avant-window-navigator/applets/showdesktop.desktop: does not have gettext domain, not stripping ./debian/awn-applets-c-core/usr/share/avant-window-navigator/applets/places.desktop: does not have gettext domain, not stripping ./debian/awn-applets-c-core/usr/share/avant-window-navigator/applets/sysmon.desktop: does not have gettext domain, not stripping ./debian/awn-applets-c-core/usr/share/avant-window-navigator/applets/garbage.desktop: does not have gettext domain, not stripping ./debian/awn-applets-c-core/usr/share/avant-window-navigator/applets/cairo-menu.desktop: does not have gettext domain, not stripping ./debian/awn-applets-c-core/usr/share/avant-window-navigator/applets/notification-daemon.desktop: does not have gettext domain, not stripping ./debian/awn-applets-c-core/usr/share/avant-window-navigator/applets/notification-area.desktop: does not have gettext domain, not stripping ./debian/awn-applets-c-core/usr/share/avant-window-navigator/applets/shinyswitcher.desktop: does not have gettext domain, not stripping ./debian/awn-applets-c-core/usr/share/avant-window-navigator/applets/awnterm.desktop: does not have gettext domain, not stripping pkgstriptranslations: awn-applets-c-core does not contain translations, skipping pkgstriptranslations: processing control file: ./debian/awn-applets-c-dbg/DEBIAN/control, package awn-applets-c-dbg, directory ./debian/awn-applets-c-dbg pkgstriptranslations: awn-applets-c-dbg does not contain translations, skipping pkgstriptranslations: processing control file: ./debian/awn-applets-c-extras/DEBIAN/control, package awn-applets-c-extras, directory ./debian/awn-applets-c-extras ./debian/awn-applets-c-extras/usr/share/avant-window-navigator/applets/main-menu.desktop: does not have gettext domain, not stripping ./debian/awn-applets-c-extras/usr/share/avant-window-navigator/applets/webapplet.desktop: does not have gettext domain, not stripping ./debian/awn-applets-c-extras/usr/share/avant-window-navigator/applets/awnsystemmonitor.desktop: does not have gettext domain, not stripping ./debian/awn-applets-c-extras/usr/share/avant-window-navigator/applets/digital-clock.desktop: does not have gettext domain, not stripping pkgstriptranslations: awn-applets-c-extras does not contain translations, skipping pkgstriptranslations: processing control file: ./debian/python-awn-extras/DEBIAN/control, package python-awn-extras, directory ./debian/python-awn-extras pkgstriptranslations: python-awn-extras does not contain translations, skipping pkgstriptranslations: tarball already exists pkgmaintainermangler: Not overriding Maintainer for domain lists.ubuntu.com dpkg-deb: warning: 'debian/awn-applets-c-dbg/DEBIAN/control' contains user-defined field 'Original-Maintainer' dpkg-deb: warning: 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_armel.deb'. dpkg-genchanges -B -mUbuntu/armel Build Daemon >../awn-extras-applets_0.4.0-0ubuntu1_armel.changes dpkg-genchanges: arch-specific upload - not including arch-independent packages dpkg-genchanges: binary-only upload - not including any source code Use of uninitialized value within %f2p in hash element at /usr/bin/dpkg-genchanges line 488. Use of uninitialized value within @_ in list assignment at /usr/share/perl5/Dpkg/Arch.pm line 321. Use of uninitialized value $b in string eq at /usr/share/perl5/Dpkg/Arch.pm line 323. Use of uninitialized value $_ in pattern match (m//) at /usr/share/perl5/Dpkg/Arch.pm line 260. Use of uninitialized value $arch in hash element at /usr/share/perl5/Dpkg/Arch.pm line 267. dpkg-buildpackage: binary only upload (no source included) ****************************************************************************** Build finished at 20100416-2200 Publishing chroot-autobuild/build/buildd/awn-extras-applets_0.4.0-0ubuntu1_armel_translations.tar.gz for rosetta. Publishing debug debs. chroot-autobuild/build/buildd/awn-applets-c-core_0.4.0-0ubuntu1_armel.deb: new debian package, version 2.0. size 196544 bytes: control archive= 2735 bytes. 2115 bytes, 32 lines control 3891 bytes, 42 lines md5sums 392 bytes, 7 lines * postinst #!/bin/sh 411 bytes, 7 lines * prerm #!/bin/sh Package: awn-applets-c-core Source: awn-extras-applets Version: 0.4.0-0ubuntu1 Architecture: armel Maintainer: Ubuntu Developers Installed-Size: 788 Depends: libatk1.0-0 (>= 1.29.3), 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.8.0), libfreetype6 (>= 2.2.1), libgconf2-4 (>= 2.27.0), libglib2.0-0 (>= 2.23.5), libgnome-menu2 (>= 2.27.92), libgtk2.0-0 (>= 2.18.0), libgtop2-7 (>= 2.20.0), libnotify1 (>= 0.4.5), libnotify1-gtk2.10, libpango1.0-0 (>= 1.14.0), libvte9 (>= 1:0.22.0), libwnck22 (>= 2.22.0), libx11-6 (>= 0), libxcomposite1 (>= 1:0.3-1), libxfixes3 (>= 1:4.0.1), 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_armel.deb: new debian package, version 2.0. size 118200 bytes: control archive= 2173 bytes. 1530 bytes, 24 lines control 3321 bytes, 34 lines md5sums 234 bytes, 7 lines * postinst #!/bin/sh 253 bytes, 7 lines * prerm #!/bin/sh Package: awn-applets-c-extras Source: awn-extras-applets Version: 0.4.0-0ubuntu1 Architecture: armel Maintainer: Ubuntu Developers Installed-Size: 508 Depends: libatk1.0-0 (>= 1.29.3), 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.8.0), libfreetype6 (>= 2.2.1), libgcc1 (>= 1:4.4.0), libgconf2-4 (>= 2.27.0), libglib2.0-0 (>= 2.16.0), libgnome-menu2 (>= 2.27.92), libgtk2.0-0 (>= 2.12.0), libgtop2-7 (>= 2.20.0), libpango1.0-0 (>= 1.14.0), libsoup2.4-1 (>= 2.4.0), libwebkit-1.0-2 (>= 1.1.1), 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_armel.deb: new debian package, version 2.0. size 36762 bytes: control archive= 1113 bytes. 855 bytes, 19 lines control 717 bytes, 9 lines md5sums 194 bytes, 7 lines * postinst #!/bin/sh 197 bytes, 7 lines * prerm #!/bin/sh Package: python-awn-extras Source: awn-extras-applets Version: 0.4.0-0ubuntu1 Architecture: armel Maintainer: Ubuntu Developers Installed-Size: 188 Depends: python (>= 2.4), python-support (>= 0.90.0), 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.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_armel.deb: new debian package, version 2.0. size 781332 bytes: control archive= 1160 bytes. 711 bytes, 17 lines control 1577 bytes, 17 lines md5sums Package: awn-applets-c-dbg Source: awn-extras-applets Version: 0.4.0-0ubuntu1 Architecture: armel Maintainer: Ubuntu Developers Installed-Size: 1900 Depends: awn-applets-c-core (= 0.4.0-0ubuntu1), awn-applets-c-extras (= 0.4.0-0ubuntu1) 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_armel.deb: drwxr-xr-x root/root 0 2010-04-16 21:58 ./ drwxr-xr-x root/root 0 2010-04-16 21:57 ./usr/ drwxr-xr-x root/root 0 2010-04-16 21:58 ./usr/share/ drwxr-xr-x root/root 0 2010-04-16 21:57 ./usr/share/icons/ drwxr-xr-x root/root 0 2010-04-16 21:57 ./usr/share/icons/hicolor/ drwxr-xr-x root/root 0 2010-04-16 21:57 ./usr/share/icons/hicolor/scalable/ drwxr-xr-x root/root 0 2010-04-16 21:57 ./usr/share/icons/hicolor/scalable/apps/ -rw-r--r-- root/root 23904 2010-04-16 21:57 ./usr/share/icons/hicolor/scalable/apps/notification-area.svg drwxr-xr-x root/root 0 2010-04-16 21:57 ./usr/share/doc/ drwxr-xr-x root/root 0 2010-04-16 21:58 ./usr/share/doc/awn-applets-c-core/ -rw-r--r-- root/root 4225 2010-04-16 21:45 ./usr/share/doc/awn-applets-c-core/changelog.Debian.gz -rw-r--r-- root/root 380 2009-08-14 13:07 ./usr/share/doc/awn-applets-c-core/changelog.gz -rw-r--r-- root/root 29449 2010-04-16 21:45 ./usr/share/doc/awn-applets-c-core/copyright drwxr-xr-x root/root 0 2010-04-16 21:58 ./usr/share/gconf/ drwxr-xr-x root/root 0 2010-04-16 21:58 ./usr/share/gconf/schemas/ -rw-r--r-- root/root 851 2010-04-16 21:57 ./usr/share/gconf/schemas/awn-applet-garbage.schemas -rw-r--r-- root/root 8217 2010-04-16 21:57 ./usr/share/gconf/schemas/awn-applet-shinyswitcher.schemas -rw-r--r-- root/root 7296 2010-04-16 21:57 ./usr/share/gconf/schemas/awn-applet-notification-daemon.schemas -rw-r--r-- root/root 3397 2010-04-16 21:57 ./usr/share/gconf/schemas/awn-applet-sysmon.schemas -rw-r--r-- root/root 1868 2010-04-16 21:57 ./usr/share/gconf/schemas/awn-applet-awnterm.schemas -rw-r--r-- root/root 4892 2010-04-16 21:57 ./usr/share/gconf/schemas/awn-applet-places.schemas -rw-r--r-- root/root 7958 2010-04-16 21:57 ./usr/share/gconf/schemas/awn-applet-cairo-menu.schemas -rw-r--r-- root/root 2078 2010-04-16 21:57 ./usr/share/gconf/schemas/awn-applet-notification-area.schemas drwxr-xr-x root/root 0 2010-04-16 21:57 ./usr/share/avant-window-navigator/ drwxr-xr-x root/root 0 2010-04-16 21:57 ./usr/share/avant-window-navigator/applets/ -rw-r--r-- root/root 395 2010-04-16 21:57 ./usr/share/avant-window-navigator/applets/showdesktop.desktop -rw-r--r-- root/root 580 2010-04-16 21:57 ./usr/share/avant-window-navigator/applets/places.desktop -rw-r--r-- root/root 321 2010-04-16 21:57 ./usr/share/avant-window-navigator/applets/sysmon.desktop -rw-r--r-- root/root 481 2010-04-16 21:57 ./usr/share/avant-window-navigator/applets/garbage.desktop -rw-r--r-- root/root 247 2010-04-16 21:57 ./usr/share/avant-window-navigator/applets/cairo-menu.desktop -rw-r--r-- root/root 379 2010-04-16 21:57 ./usr/share/avant-window-navigator/applets/notification-daemon.desktop drwxr-xr-x root/root 0 2010-04-16 21:57 ./usr/share/avant-window-navigator/applets/shinyswitcher/ -rw-r--r-- root/root 3117 2010-04-16 21:57 ./usr/share/avant-window-navigator/applets/shinyswitcher/shiny-prefs.py -rw-r--r-- root/root 69108 2010-04-16 21:57 ./usr/share/avant-window-navigator/applets/shinyswitcher/shiny-prefs.ui drwxr-xr-x root/root 0 2010-04-16 21:57 ./usr/share/avant-window-navigator/applets/notification-area/ -rw-r--r-- root/root 22864 2010-04-16 21:57 ./usr/share/avant-window-navigator/applets/notification-area/na-prefs.ui -rw-r--r-- root/root 292 2010-04-16 21:57 ./usr/share/avant-window-navigator/applets/notification-area.desktop -rw-r--r-- root/root 282 2010-04-16 21:57 ./usr/share/avant-window-navigator/applets/shinyswitcher.desktop -rw-r--r-- root/root 496 2010-04-16 21:57 ./usr/share/avant-window-navigator/applets/awnterm.desktop drwxr-xr-x root/root 0 2010-04-16 21:57 ./usr/share/avant-window-navigator/schemas/ -rw-r--r-- root/root 1446 2010-04-16 21:57 ./usr/share/avant-window-navigator/schemas/awn-applet-awnterm.schema-ini -rw-r--r-- root/root 1146 2010-04-16 21:57 ./usr/share/avant-window-navigator/schemas/awn-applet-sysmon.schema-ini -rw-r--r-- root/root 395 2010-04-16 21:57 ./usr/share/avant-window-navigator/schemas/awn-applet-garbage.schema-ini -rw-r--r-- root/root 2723 2010-04-16 21:57 ./usr/share/avant-window-navigator/schemas/awn-applet-notification-daemon.schema-ini -rw-r--r-- root/root 2464 2010-04-16 21:57 ./usr/share/avant-window-navigator/schemas/awn-applet-places.schema-ini -rw-r--r-- root/root 689 2010-04-16 21:57 ./usr/share/avant-window-navigator/schemas/awn-applet-notification-area.schema-ini -rw-r--r-- root/root 1774 2010-04-16 21:57 ./usr/share/avant-window-navigator/schemas/awn-applet-cairo-menu.schema-ini -rw-r--r-- root/root 3088 2010-04-16 21:57 ./usr/share/avant-window-navigator/schemas/awn-applet-shinyswitcher.schema-ini drwxr-xr-x root/root 0 2010-04-16 21:57 ./usr/lib/ drwxr-xr-x root/root 0 2010-04-16 21:57 ./usr/lib/awn/ drwxr-xr-x root/root 0 2010-04-16 21:57 ./usr/lib/awn/applets/ drwxr-xr-x root/root 0 2010-04-16 21:58 ./usr/lib/awn/applets/notification-daemon/ -rw-r--r-- root/root 47608 2010-04-16 21:58 ./usr/lib/awn/applets/notification-daemon/notification-daemon.so drwxr-xr-x root/root 0 2010-04-16 21:58 ./usr/lib/awn/applets/garbage/ -rw-r--r-- root/root 22308 2010-04-16 21:58 ./usr/lib/awn/applets/garbage/garbage.so drwxr-xr-x root/root 0 2010-04-16 21:58 ./usr/lib/awn/applets/sysmon/ -rw-r--r-- root/root 43024 2010-04-16 21:58 ./usr/lib/awn/applets/sysmon/sysmon.so drwxr-xr-x root/root 0 2010-04-16 21:58 ./usr/lib/awn/applets/shinyswitcher/ -rw-r--r-- root/root 38984 2010-04-16 21:58 ./usr/lib/awn/applets/shinyswitcher/shinyswitcher.so drwxr-xr-x root/root 0 2010-04-16 21:58 ./usr/lib/awn/applets/awnterm/ -rw-r--r-- root/root 51500 2010-04-16 21:58 ./usr/lib/awn/applets/awnterm/awnterm.so drwxr-xr-x root/root 0 2010-04-16 21:58 ./usr/lib/awn/applets/notification-area/ -rw-r--r-- root/root 47408 2010-04-16 21:58 ./usr/lib/awn/applets/notification-area/notification-area.so drwxr-xr-x root/root 0 2010-04-16 21:58 ./usr/lib/awn/applets/cairo-menu/ -rw-r--r-- root/root 34948 2010-04-16 21:58 ./usr/lib/awn/applets/cairo-menu/gnome-menu-builder.so -rw-r--r-- root/root 35008 2010-04-16 21:58 ./usr/lib/awn/applets/cairo-menu/cairo-menu.so drwxr-xr-x root/root 0 2010-04-16 21:58 ./usr/lib/awn/applets/places/ -rw-r--r-- root/root 30784 2010-04-16 21:58 ./usr/lib/awn/applets/places/places.so drwxr-xr-x root/root 0 2010-04-16 21:58 ./usr/lib/awn/applets/showdesktop/ -rw-r--r-- root/root 9796 2010-04-16 21:58 ./usr/lib/awn/applets/showdesktop/showdesktop.so chroot-autobuild/build/buildd/awn-applets-c-extras_0.4.0-0ubuntu1_armel.deb: drwxr-xr-x root/root 0 2010-04-16 21:58 ./ drwxr-xr-x root/root 0 2010-04-16 21:57 ./usr/ drwxr-xr-x root/root 0 2010-04-16 21:58 ./usr/share/ drwxr-xr-x root/root 0 2010-04-16 21:57 ./usr/share/icons/ drwxr-xr-x root/root 0 2010-04-16 21:57 ./usr/share/icons/hicolor/ drwxr-xr-x root/root 0 2010-04-16 21:57 ./usr/share/icons/hicolor/scalable/ drwxr-xr-x root/root 0 2010-04-16 21:57 ./usr/share/icons/hicolor/scalable/apps/ -rw-r--r-- root/root 16187 2010-04-16 21:57 ./usr/share/icons/hicolor/scalable/apps/awn-applet-digital-clock.svg drwxr-xr-x root/root 0 2010-04-16 21:57 ./usr/share/doc/ drwxr-xr-x root/root 0 2010-04-16 21:58 ./usr/share/doc/awn-applets-c-extras/ -rw-r--r-- root/root 4225 2010-04-16 21:45 ./usr/share/doc/awn-applets-c-extras/changelog.Debian.gz -rw-r--r-- root/root 380 2009-08-14 13:07 ./usr/share/doc/awn-applets-c-extras/changelog.gz -rw-r--r-- root/root 29449 2010-04-16 21:45 ./usr/share/doc/awn-applets-c-extras/copyright drwxr-xr-x root/root 0 2010-04-16 21:58 ./usr/share/gconf/ drwxr-xr-x root/root 0 2010-04-16 21:58 ./usr/share/gconf/schemas/ -rw-r--r-- root/root 3119 2010-04-16 21:57 ./usr/share/gconf/schemas/awn-applet-digital-clock.schemas -rw-r--r-- root/root 2163 2010-04-16 21:57 ./usr/share/gconf/schemas/awnsystemmonitor.schemas -rw-r--r-- root/root 2533 2010-04-16 21:57 ./usr/share/gconf/schemas/awn-applet-webapplet.schemas drwxr-xr-x root/root 0 2010-04-16 21:57 ./usr/share/avant-window-navigator/ drwxr-xr-x root/root 0 2010-04-16 21:57 ./usr/share/avant-window-navigator/applets/ drwxr-xr-x root/root 0 2010-04-16 21:57 ./usr/share/avant-window-navigator/applets/digital-clock/ -rw-r--r-- root/root 13616 2010-04-16 21:57 ./usr/share/avant-window-navigator/applets/digital-clock/dg-prefs.ui drwxr-xr-x root/root 0 2010-04-16 21:57 ./usr/share/avant-window-navigator/applets/webapplet/ drwxr-xr-x root/root 0 2010-04-16 21:57 ./usr/share/avant-window-navigator/applets/webapplet/icons/ -rw-r--r-- root/root 1368 2010-04-16 21:57 ./usr/share/avant-window-navigator/applets/webapplet/icons/meebo-48.png -rw-r--r-- root/root 8215 2010-04-16 21:57 ./usr/share/avant-window-navigator/applets/webapplet/icons/facebook.svg -rw-r--r-- root/root 11136 2010-04-16 21:57 ./usr/share/avant-window-navigator/applets/webapplet/icons/pingfm.svg -rw-r--r-- root/root 1208 2010-04-16 21:57 ./usr/share/avant-window-navigator/applets/webapplet/icons/friendfeed-22.png -rw-r--r-- root/root 9259 2010-04-16 21:57 ./usr/share/avant-window-navigator/applets/webapplet/icons/twitter.svg -rw-r--r-- root/root 23894 2010-04-16 21:57 ./usr/share/avant-window-navigator/applets/webapplet/icons/brightkite.svg -rw-r--r-- root/root 1253 2010-04-16 21:57 ./usr/share/avant-window-navigator/applets/webapplet/icons/brightkite-22.png -rw-r--r-- root/root 1105 2010-04-16 21:57 ./usr/share/avant-window-navigator/applets/webapplet/icons/digg-22.png -rw-r--r-- root/root 731 2010-04-16 21:57 ./usr/share/avant-window-navigator/applets/webapplet/icons/facebook-22.png -rw-r--r-- root/root 924 2010-04-16 21:57 ./usr/share/avant-window-navigator/applets/webapplet/icons/twitter-22.png -rw-r--r-- root/root 1879 2010-04-16 21:57 ./usr/share/avant-window-navigator/applets/webapplet/icons/pandora-48.png -rw-r--r-- root/root 673 2010-04-16 21:57 ./usr/share/avant-window-navigator/applets/webapplet/icons/pingfm-22.png -rw-r--r-- root/root 2600 2010-04-16 21:57 ./usr/share/avant-window-navigator/applets/webapplet/icons/rtm.png -rw-r--r-- root/root 18625 2010-04-16 21:57 ./usr/share/avant-window-navigator/applets/webapplet/icons/digg.svg -rw-r--r-- root/root 16779 2010-04-16 21:57 ./usr/share/avant-window-navigator/applets/webapplet/icons/friendfeed.svg -rw-r--r-- root/root 1201 2010-04-16 21:57 ./usr/share/avant-window-navigator/applets/webapplet/webapplet-websites.ini -rw-r--r-- root/root 320 2010-04-16 21:57 ./usr/share/avant-window-navigator/applets/main-menu.desktop -rw-r--r-- root/root 224 2010-04-16 21:57 ./usr/share/avant-window-navigator/applets/webapplet.desktop -rw-r--r-- root/root 395 2010-04-16 21:57 ./usr/share/avant-window-navigator/applets/awnsystemmonitor.desktop -rw-r--r-- root/root 524 2010-04-16 21:57 ./usr/share/avant-window-navigator/applets/digital-clock.desktop drwxr-xr-x root/root 0 2010-04-16 21:57 ./usr/share/avant-window-navigator/schemas/ -rw-r--r-- root/root 745 2010-04-16 21:57 ./usr/share/avant-window-navigator/schemas/awn-applet-webapplet.schema-ini -rw-r--r-- root/root 1743 2010-04-16 21:57 ./usr/share/avant-window-navigator/schemas/awn-applet-digital-clock.schema-ini drwxr-xr-x root/root 0 2010-04-16 21:57 ./usr/lib/ drwxr-xr-x root/root 0 2010-04-16 21:57 ./usr/lib/awn/ drwxr-xr-x root/root 0 2010-04-16 21:57 ./usr/lib/awn/applets/ drwxr-xr-x root/root 0 2010-04-16 21:58 ./usr/lib/awn/applets/digital-clock/ -rw-r--r-- root/root 26404 2010-04-16 21:58 ./usr/lib/awn/applets/digital-clock/digital-clock.so drwxr-xr-x root/root 0 2010-04-16 21:58 ./usr/lib/awn/applets/main-menu/ -rw-r--r-- root/root 14028 2010-04-16 21:58 ./usr/lib/awn/applets/main-menu/main-menu.so drwxr-xr-x root/root 0 2010-04-16 21:58 ./usr/lib/awn/applets/webapplet/ -rw-r--r-- root/root 18120 2010-04-16 21:58 ./usr/lib/awn/applets/webapplet/webapplet.so drwxr-xr-x root/root 0 2010-04-16 21:58 ./usr/lib/awn/applets/awnsystemmonitor/ -rw-r--r-- root/root 80224 2010-04-16 21:58 ./usr/lib/awn/applets/awnsystemmonitor/awnsystemmonitor.so chroot-autobuild/build/buildd/python-awn-extras_0.4.0-0ubuntu1_armel.deb: drwxr-xr-x root/root 0 2010-04-16 21:57 ./ drwxr-xr-x root/root 0 2010-04-16 21:57 ./usr/ drwxr-xr-x root/root 0 2010-04-16 21:57 ./usr/share/ drwxr-xr-x root/root 0 2010-04-16 21:57 ./usr/share/python-support/ -rw-r--r-- root/root 244 2010-04-16 21:57 ./usr/share/python-support/python-awn-extras.public drwxr-xr-x root/root 0 2010-04-16 21:57 ./usr/share/pyshared/ drwxr-xr-x root/root 0 2010-04-16 21:57 ./usr/share/pyshared/awn/ drwxr-xr-x root/root 0 2010-04-16 21:57 ./usr/share/pyshared/awn/extras/ -rw-r--r-- root/root 1258 2010-04-16 21:57 ./usr/share/pyshared/awn/extras/__init__.py -rw-r--r-- root/root 10137 2010-04-16 21:57 ./usr/share/pyshared/awn/extras/configbinder.py -rw-r--r-- root/root 47971 2010-04-16 21:57 ./usr/share/pyshared/awn/extras/awnlib.py -rw-r--r-- root/root 3329 2010-04-16 21:57 ./usr/share/pyshared/awn/extras/threadqueue.py -rw-r--r-- root/root 21519 2010-04-16 21:57 ./usr/share/pyshared/awn/extras/awnmediaplayers.py drwxr-xr-x root/root 0 2010-04-16 21:57 ./usr/share/doc/ drwxr-xr-x root/root 0 2010-04-16 21:58 ./usr/share/doc/python-awn-extras/ -rw-r--r-- root/root 4225 2010-04-16 21:45 ./usr/share/doc/python-awn-extras/changelog.Debian.gz -rw-r--r-- root/root 380 2009-08-14 13:07 ./usr/share/doc/python-awn-extras/changelog.gz -rw-r--r-- root/root 29449 2010-04-16 21:45 ./usr/share/doc/python-awn-extras/copyright chroot-autobuild/build/buildd/awn-applets-c-dbg_0.4.0-0ubuntu1_armel.deb: drwxr-xr-x root/root 0 2010-04-16 21:57 ./ drwxr-xr-x root/root 0 2010-04-16 21:58 ./usr/ drwxr-xr-x root/root 0 2010-04-16 21:57 ./usr/share/ drwxr-xr-x root/root 0 2010-04-16 21:57 ./usr/share/doc/ drwxr-xr-x root/root 0 2010-04-16 21:58 ./usr/share/doc/awn-applets-c-dbg/ -rw-r--r-- root/root 4225 2010-04-16 21:45 ./usr/share/doc/awn-applets-c-dbg/changelog.Debian.gz -rw-r--r-- root/root 380 2009-08-14 13:07 ./usr/share/doc/awn-applets-c-dbg/changelog.gz -rw-r--r-- root/root 29449 2010-04-16 21:45 ./usr/share/doc/awn-applets-c-dbg/copyright drwxr-xr-x root/root 0 2010-04-16 21:58 ./usr/lib/ drwxr-xr-x root/root 0 2010-04-16 21:58 ./usr/lib/debug/ drwxr-xr-x root/root 0 2010-04-16 21:58 ./usr/lib/debug/usr/ drwxr-xr-x root/root 0 2010-04-16 21:58 ./usr/lib/debug/usr/lib/ drwxr-xr-x root/root 0 2010-04-16 21:58 ./usr/lib/debug/usr/lib/awn/ drwxr-xr-x root/root 0 2010-04-16 21:58 ./usr/lib/debug/usr/lib/awn/applets/ drwxr-xr-x root/root 0 2010-04-16 21:58 ./usr/lib/debug/usr/lib/awn/applets/notification-daemon/ -rw-r--r-- root/root 122675 2010-04-16 21:58 ./usr/lib/debug/usr/lib/awn/applets/notification-daemon/notification-daemon.so drwxr-xr-x root/root 0 2010-04-16 21:58 ./usr/lib/debug/usr/lib/awn/applets/digital-clock/ -rw-r--r-- root/root 97660 2010-04-16 21:58 ./usr/lib/debug/usr/lib/awn/applets/digital-clock/digital-clock.so drwxr-xr-x root/root 0 2010-04-16 21:58 ./usr/lib/debug/usr/lib/awn/applets/garbage/ -rw-r--r-- root/root 93966 2010-04-16 21:58 ./usr/lib/debug/usr/lib/awn/applets/garbage/garbage.so drwxr-xr-x root/root 0 2010-04-16 21:58 ./usr/lib/debug/usr/lib/awn/applets/main-menu/ -rw-r--r-- root/root 33487 2010-04-16 21:58 ./usr/lib/debug/usr/lib/awn/applets/main-menu/main-menu.so drwxr-xr-x root/root 0 2010-04-16 21:58 ./usr/lib/debug/usr/lib/awn/applets/sysmon/ -rw-r--r-- root/root 226492 2010-04-16 21:58 ./usr/lib/debug/usr/lib/awn/applets/sysmon/sysmon.so drwxr-xr-x root/root 0 2010-04-16 21:58 ./usr/lib/debug/usr/lib/awn/applets/shinyswitcher/ -rw-r--r-- root/root 97486 2010-04-16 21:58 ./usr/lib/debug/usr/lib/awn/applets/shinyswitcher/shinyswitcher.so drwxr-xr-x root/root 0 2010-04-16 21:58 ./usr/lib/debug/usr/lib/awn/applets/awnterm/ -rw-r--r-- root/root 148044 2010-04-16 21:58 ./usr/lib/debug/usr/lib/awn/applets/awnterm/awnterm.so drwxr-xr-x root/root 0 2010-04-16 21:58 ./usr/lib/debug/usr/lib/awn/applets/webapplet/ -rw-r--r-- root/root 57618 2010-04-16 21:58 ./usr/lib/debug/usr/lib/awn/applets/webapplet/webapplet.so drwxr-xr-x root/root 0 2010-04-16 21:58 ./usr/lib/debug/usr/lib/awn/applets/notification-area/ -rw-r--r-- root/root 171333 2010-04-16 21:58 ./usr/lib/debug/usr/lib/awn/applets/notification-area/notification-area.so drwxr-xr-x root/root 0 2010-04-16 21:58 ./usr/lib/debug/usr/lib/awn/applets/cairo-menu/ -rw-r--r-- root/root 120507 2010-04-16 21:58 ./usr/lib/debug/usr/lib/awn/applets/cairo-menu/gnome-menu-builder.so -rw-r--r-- root/root 190310 2010-04-16 21:58 ./usr/lib/debug/usr/lib/awn/applets/cairo-menu/cairo-menu.so drwxr-xr-x root/root 0 2010-04-16 21:58 ./usr/lib/debug/usr/lib/awn/applets/places/ -rw-r--r-- root/root 58022 2010-04-16 21:58 ./usr/lib/debug/usr/lib/awn/applets/places/places.so drwxr-xr-x root/root 0 2010-04-16 21:58 ./usr/lib/debug/usr/lib/awn/applets/awnsystemmonitor/ -rw-r--r-- root/root 249628 2010-04-16 21:58 ./usr/lib/debug/usr/lib/awn/applets/awnsystemmonitor/awnsystemmonitor.so drwxr-xr-x root/root 0 2010-04-16 21:58 ./usr/lib/debug/usr/lib/awn/applets/showdesktop/ -rw-r--r-- root/root 49542 2010-04-16 21:58 ./usr/lib/debug/usr/lib/awn/applets/showdesktop/showdesktop.so awn-extras-applets_0.4.0-0ubuntu1_armel.changes: Format: 1.8 Date: Sun, 11 Apr 2010 22:38:55 +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: armel armel_translations Version: 0.4.0-0ubuntu1 Distribution: lucid Urgency: low Maintainer: Ubuntu/armel 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 Launchpad-Bugs-Fixed: 511256 545164 551119 552376 556175 558463 Changes: awn-extras-applets (0.4.0-0ubuntu1) lucid; urgency=low . * New upstream release. - Close cairo-menu after a click (LP: #511256) - Fix crash of awn-system-monitor (LP: #545164) - Fix crash when removing a volume >1 or adding volume >1 or using prefs while > 1 volumes is present (LP: #556175) - Fix crash of media-control when Rhythmbox quit (LP: #558463) - Fix crash of file-browser-launcher when there is no .gtk-bookmarks (LP: #551119) * debian/awn-c-extras.install: - Install icons and ini files for webapplets * debian/awn-python-core.install: - Install ui file for comics (LP: #552376) * debian/patches: - 03-remove-cairo-menu-pref.patch: Merged upstream. - 04-tomboy-threading-free.patch: Merged upstream. Checksums-Sha1: 412aeb53c9747c4a70230a7220eae455feab00e2 196544 awn-applets-c-core_0.4.0-0ubuntu1_armel.deb a71bb53e5dfcc4e9f4961166304805fde94225de 118200 awn-applets-c-extras_0.4.0-0ubuntu1_armel.deb 94ed3ae05225f6128af1a933cbc1a472510c6c57 36762 python-awn-extras_0.4.0-0ubuntu1_armel.deb 5ac0c9e58677f6f07e3b3a3d3dc879869d0b9e42 781332 awn-applets-c-dbg_0.4.0-0ubuntu1_armel.deb 5891dbfe077da787b4327a70496d58c527a43529 1019121 awn-extras-applets_0.4.0-0ubuntu1_armel_translations.tar.gz Checksums-Sha256: 35a2f3602b4b9347ba64f5bcd37129e8c73bb612854e04a8ddda5cf6b89ce3bb 196544 awn-applets-c-core_0.4.0-0ubuntu1_armel.deb 603a8c520e049e1d8c7726663dbaf08c603d72b3895d4787d92b3fc0dd60d033 118200 awn-applets-c-extras_0.4.0-0ubuntu1_armel.deb bb1b469b62d399e280a40f5b60f8e79e2adea506a9345d01957fc1d311e8fa17 36762 python-awn-extras_0.4.0-0ubuntu1_armel.deb 830ac99349d158e34d1fd7ae8911ff5f3bd622ae54c04c454c6e949fb3483489 781332 awn-applets-c-dbg_0.4.0-0ubuntu1_armel.deb f8c8974bebbb3c096d2743a846588e76ff71c0062eec325cd53ade7ba09d1939 1019121 awn-extras-applets_0.4.0-0ubuntu1_armel_translations.tar.gz Files: 55dbc152b77ce417a54ed0cdbd6d6460 196544 gnome optional awn-applets-c-core_0.4.0-0ubuntu1_armel.deb e2b18453984dfe47773750bd8917bd74 118200 gnome optional awn-applets-c-extras_0.4.0-0ubuntu1_armel.deb e83f8b093ef170268c267047aa731ded 36762 python optional python-awn-extras_0.4.0-0ubuntu1_armel.deb 95619eb2e570b7f97b1bcacc1c11b534 781332 debug extra awn-applets-c-dbg_0.4.0-0ubuntu1_armel.deb 02b9f52c4c0ddc7fedb6cfc77fb0afcc 1019121 raw-translations - awn-extras-applets_0.4.0-0ubuntu1_armel_translations.tar.gz Original-Maintainer: Julien Lavergne ****************************************************************************** Built successfully Purging chroot-autobuild/build/buildd/awn-extras-applets-0.4.0 ------------------------------------------------------------------------------ /usr/bin/sudo dpkg --purge groff-base libavahi-common3 libxfixes-dev libx11-data m4 libgconf2-dev fontconfig-config libstartup-notification0-dev gettext file zlib1g-dev libhtml-parser-perl libwnck-dev 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 libgstreamer0.10-0 python-gtk2 libxcb-event1 x11proto-input-dev libexpat1-dev libjasper1 libpixman-1-dev libjpeg62-dev libxcomposite-dev libfontconfig1 libdbus-glib-1-2 libenchant1c2a libgstreamer-plugins-base0.10-0 python-cairo libsexy2 libsysfs-dev libx11-6 libxres-dev libvte-dev xtrans-dev x11proto-randr-dev vala-awn psmisc libdesktop-agnostic-bin libnewt0.52 libxinerama-dev libpango1.0-common libxdamage1 libxt6 libffi5 libxml2-utils libdbus-1-dev libhtml-tree-perl libglib2.0-dev libgnome-menu-dev libxcb-render-util0 gconf2 libgpg-error-dev tsconf libdirectfb-dev libhtml-tagset-perl libgtop2-common libxml2 dbus x11proto-xext-dev pkg-config libthai-data libwebkit-dev libice6 intltool-debian libavahi-client3 libxrender1 liborbit2-dev libfontconfig1-dev libxml2-dev libtasn1-3-dev libxrandr-dev libxext-dev libcups2 libdirectfb-extra libxau-dev libdatrie1 libxcb-render-util0-dev libaspell15 libxrender-dev librsvg2-dev libpng12-dev libavahi-common-data libxft2 x11proto-render-dev libxext6 libsysfs2 libsqlite3-0 libnotify1 libxinerama1 libxcb-aux0 libawn-dev libdbus-glib-1-dev libxdamage-dev libsm-dev libncursesw5 iso-codes gconf2-common libgsf-1-common libxdmcp-dev defoma ttf-dejavu-core librsvg2-2 libsexy-dev libcairo2-dev libgail18 libxcb-render0-dev fontconfig liburi-perl libgcrypt11-dev libstartup-notification0 autotools-dev libcroco3 liborbit2 python-support libpopt0 libfreetype6 libwnck-common libice-dev libatk1.0-0 x11proto-fixes-dev libfreetype6-dev libgtk2.0-0 x11proto-damage-dev libidl0 libxcb1 libxcb-atom1 libgtop2-dev libgtop2-7 html2text diffstat libgsf-1-114 libxrandr2 debhelper libpthread-stubs0 libsoup2.4-dev libthai0 python-vte python libxslt1.1 libmagic1 python-gobject libdesktop-agnostic-dev libgnutls-dev libtiff4 libexpat1 bsdmainutils 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 libdirectfb-1.2-0 libxml-parser-perl libxft-dev libdesktop-agnostic0 man-db libsoup2.4-1 dbus-x11 x11proto-kb-dev libpixman-1-0 libwebkit-1.0-2 x11proto-xinerama-dev libwebkit-1.0-common libdesktop-agnostic-cfg-gconf libpango1.0-0 libpthread-stubs0-dev ucf libgtk2.0-common gettext-base libicu42 libsm6 libxcb-render0 libxres1 x11proto-resource-dev autoconf (Reading database ... 22215 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 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 libwnck-common ... 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 libsoup2.4-dev ... Removing python-vte ... Removing libdesktop-agnostic-dev ... Removing libgnutls-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 catpages as well as /var/cache/man hierarchy. Removing dbus-x11 ... Purging configuration files for dbus-x11 ... Removing libwebkit-1.0-2 ... Purging configuration files for libwebkit-1.0-2 ... Removing libwebkit-1.0-common ... Removing libdesktop-agnostic-cfg-gconf ... Removing libicu42 ... Purging configuration files for libicu42 ... 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 automake ... Removing libvte-common ... Removing python-gtk2 ... Removing libxcomposite-dev ... Removing libgstreamer-plugins-base0.10-0 ... Purging configuration files for libgstreamer-plugins-base0.10-0 ... Removing python-cairo ... 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 libtasn1-3-dev ... Removing libxrandr-dev ... Removing libxdamage-dev ... Removing iso-codes ... Removing libgsf-1-common ... Removing libgail18 ... Purging configuration files for libgail18 ... Removing libgcrypt11-dev ... Removing libstartup-notification0 ... Purging configuration files for libstartup-notification0 ... Removing autotools-dev ... Removing x11proto-damage-dev ... Removing libxcb-atom1 ... Purging configuration files for libxcb-atom1 ... Removing html2text ... Purging configuration files for html2text ... Removing diffstat ... Removing libxslt1.1 ... Purging configuration files for libxslt1.1 ... Removing python-gobject ... Purging configuration files for python-gobject ... 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 libxi-dev ... Removing libwww-perl ... Removing libxft-dev ... Removing libdesktop-agnostic0 ... Purging configuration files for libdesktop-agnostic0 ... Removing libsoup2.4-1 ... Purging configuration files for libsoup2.4-1 ... Removing x11proto-xinerama-dev ... Removing autoconf ... Purging configuration files for autoconf ... Removing libxfixes-dev ... Removing m4 ... Removing gettext ... Removing libgstreamer0.10-0 ... Purging configuration files for libgstreamer0.10-0 ... Removing libxcb-event1 ... Purging configuration files for libxcb-event1 ... Removing libdbus-glib-1-2 ... Purging configuration files for libdbus-glib-1-2 ... Removing libenchant1c2a ... Removing x11proto-randr-dev ... Removing libffi5 ... Purging configuration files for libffi5 ... Removing libhtml-tree-perl ... Removing libglib2.0-dev ... Removing libgpg-error-dev ... Removing libaspell15 ... Purging configuration files for libaspell15 ... Removing libxcb-aux0 ... Purging configuration files for libxcb-aux0 ... 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 python-support ... Purging configuration files for python-support ... 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 python ... Purging configuration files for python ... 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 python2.6 ... Purging configuration files for python2.6 ... 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 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 dbus ... Purging configuration files for dbus ... rmdir: failed to remove `/var/lib/dbus': No such file or directory 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 libsqlite3-0 ... Purging configuration files for libsqlite3-0 ... Removing libxinerama1 ... Purging configuration files for libxinerama1 ... Removing libsm-dev ... Removing libncursesw5 ... Purging configuration files for libncursesw5 ... Removing defoma ... Purging configuration files for defoma ... dpkg: warning: while removing defoma, directory '/etc/defoma' not empty so not removed. Removing libxcb-render0-dev ... Removing fontconfig ... Purging configuration files for fontconfig ... Removing liburi-perl ... Removing libice-dev ... Removing libatk1.0-0 ... Purging configuration files for libatk1.0-0 ... Removing libfreetype6-dev ... Removing libthai0 ... Purging configuration files for libthai0 ... Removing mime-support ... Purging configuration files for mime-support ... Removing whiptail ... Removing libxfixes3 ... Purging configuration files for libxfixes3 ... Removing libdirectfb-1.2-0 ... Purging configuration files for libdirectfb-1.2-0 ... Removing libpixman-1-0 ... Purging configuration files for libpixman-1-0 ... Removing libsm6 ... Purging configuration files for libsm6 ... Removing file ... Purging configuration files for file ... 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 libnewt0.52 ... Purging configuration files for libnewt0.52 ... 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 libavahi-client3 ... Purging configuration files for libavahi-client3 ... Removing libxrender1 ... Purging configuration files for libxrender1 ... Removing libdatrie1 ... Purging configuration files for libdatrie1 ... Removing libxext6 ... Purging configuration files for libxext6 ... Removing libsysfs2 ... Purging configuration files for libsysfs2 ... Removing libpopt0 ... Purging configuration files for libpopt0 ... Removing libfreetype6 ... Purging configuration files for libfreetype6 ... Removing libmagic1 ... Purging configuration files for libmagic1 ... Removing libexpat1 ... Purging configuration files for libexpat1 ... Removing libts-0.0-0 ... Purging configuration files for libts-0.0-0 ... Removing libxcb1-dev ... Removing x11proto-kb-dev ... Removing libpthread-stubs0-dev ... Removing libxcb-render0 ... Purging configuration files for libxcb-render0 ... Removing libavahi-common3 ... Purging configuration files for libavahi-common3 ... Removing fontconfig-config ... Purging configuration files for fontconfig-config ... Removing libjpeg62 ... Removing x11proto-input-dev ... Removing libx11-6 ... Purging configuration files for libx11-6 ... Removing tsconf ... Purging configuration files for tsconf ... Removing libxau-dev ... Removing libavahi-common-data ... Removing libxdmcp-dev ... Removing 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 ... Processing triggers for libc-bin ... ldconfig deferred processing now taking place ****************************************************************************** Finished at 20100416-2200 Build needed 00:14:29, 56872k 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', '1686916-3339864'] Scanning for processes to kill in build /home/buildd/build-1686916-3339864/chroot-autobuild... RUN: /usr/share/launchpad-buildd/slavebin/umount-chroot ['umount-chroot', '1686916-3339864'] Unmounting chroot for build 1686916-3339864... RUN: /usr/share/launchpad-buildd/slavebin/remove-build ['remove-build', '1686916-3339864'] Removing build 1686916-3339864