sbuild (Debian sbuild) 0.62.6 (07 Dec 2011) on build01.raspbian.lan ╔══════════════════════════════════════════════════════════════════════════════╗ ║ awn-extras-applets 0.4.0-5 (armhf) 24 Jun 2012 07:34 ║ ╚══════════════════════════════════════════════════════════════════════════════╝ Package: awn-extras-applets Version: 0.4.0-5 Source Version: 0.4.0-5 Distribution: testing Architecture: armhf I: NOTICE: Log filtering will replace 'build/awn-extras-applets-GYtw6e/awn-extras-applets-0.4.0' with '«PKGBUILDDIR»' I: NOTICE: Log filtering will replace 'build/awn-extras-applets-GYtw6e' with '«BUILDDIR»' I: NOTICE: Log filtering will replace 'var/lib/schroot/mount/testing-armhf-sbuild-5fdc5882-e2b2-4692-8fad-c4b05e5cc92b' with '«CHROOT»' ┌──────────────────────────────────────────────────────────────────────────────┐ │ Update chroot │ └──────────────────────────────────────────────────────────────────────────────┘ Get:1 http://repo.raspbian.lan testing InRelease [9318 B] Get:2 http://repo.raspbian.lan testing/main Sources [6131 kB] Get:3 http://repo.raspbian.lan testing/main armhf Packages [7108 kB] Ign http://repo.raspbian.lan testing/main Translation-en Fetched 13.2 MB in 43s (304 kB/s) Reading package lists... ┌──────────────────────────────────────────────────────────────────────────────┐ │ Fetch source files │ └──────────────────────────────────────────────────────────────────────────────┘ Check APT ───────── Checking available source versions... Download source files with APT ────────────────────────────── Reading package lists... Building dependency tree... Reading state information... NOTICE: 'awn-extras-applets' packaging is maintained in the 'Git' version control system at: git://github.com/gilir/awn-extras-debian.git Need to get 3258 kB of source archives. Get:1 http://repo.raspbian.lan/raspbian/ testing/main awn-extras-applets 0.4.0-5 (dsc) [2612 B] Get:2 http://repo.raspbian.lan/raspbian/ testing/main awn-extras-applets 0.4.0-5 (tar) [3234 kB] Get:3 http://repo.raspbian.lan/raspbian/ testing/main awn-extras-applets 0.4.0-5 (diff) [21.6 kB] Fetched 3258 kB in 0s (3497 kB/s) Download complete and in download only mode Check arch ────────── Merged Build-Depends: build-essential, fakeroot Filtered Build-Depends: build-essential, fakeroot dpkg-deb: building package `sbuild-build-depends-core-dummy' in `/«BUILDDIR»/resolver-OLhY6Z/apt_archive/sbuild-build-depends-core-dummy.deb'. OK Reading package lists... ┌──────────────────────────────────────────────────────────────────────────────┐ │ Install core build dependencies (apt-based resolver) │ └──────────────────────────────────────────────────────────────────────────────┘ Installing build dependencies Reading package lists... Building dependency tree... Reading state information... The following NEW packages will be installed: sbuild-build-depends-core-dummy debconf: delaying package configuration, since apt-utils is not installed 0 upgraded, 1 newly installed, 0 to remove and 9 not upgraded. Need to get 0 B/704 B of archives. After this operation, 0 B of additional disk space will be used. Selecting previously unselected package sbuild-build-depends-core-dummy. (Reading database ... 10659 files and directories currently installed.) Unpacking sbuild-build-depends-core-dummy (from .../sbuild-build-depends-core-dummy.deb) ... Setting up sbuild-build-depends-core-dummy (0.invalid.0) ... Merged Build-Depends: libc6-dev | libc-dev, gcc (>= 4:4.4.3), g++ (>= 4:4.4.3), make, dpkg-dev (>= 1.13.5), debhelper (>= 7.0.50~), intltool, libgnome-menu-dev, libgconf2-dev, librsvg2-dev, libgtop2-dev, libawn-dev (>= 0.4.1~bzr830), libwnck-dev, libsexy-dev, libnotify-dev (>= 0.7), libvte-dev, python (>= 2.6.6-3~), python-gtk2-dev, python-cairo-dev, valac (>= 0.7.7), libwebkitgtk-dev, libdesktop-agnostic-bin Filtered Build-Depends: libc6-dev, gcc (>= 4:4.4.3), g++ (>= 4:4.4.3), make, dpkg-dev (>= 1.13.5), debhelper (>= 7.0.50~), intltool, libgnome-menu-dev, libgconf2-dev, librsvg2-dev, libgtop2-dev, libawn-dev (>= 0.4.1~bzr830), libwnck-dev, libsexy-dev, libnotify-dev (>= 0.7), libvte-dev, python (>= 2.6.6-3~), python-gtk2-dev, python-cairo-dev, valac (>= 0.7.7), libwebkitgtk-dev, libdesktop-agnostic-bin dpkg-deb: building package `sbuild-build-depends-awn-extras-applets-dummy' in `/«BUILDDIR»/resolver-08EsqD/apt_archive/sbuild-build-depends-awn-extras-applets-dummy.deb'. OK Reading package lists... ┌──────────────────────────────────────────────────────────────────────────────┐ │ Install awn-extras-applets build dependencies (apt-based resolver) │ └──────────────────────────────────────────────────────────────────────────────┘ Installing build dependencies Reading package lists... Building dependency tree... Reading state information... The following extra packages will be installed: adduser aspell aspell-en autoconf automake autotools-dev bsdmainutils ca-certificates dbus dbus-x11 dconf-gsettings-backend dconf-service debhelper dictionaries-common file fontconfig fontconfig-config gconf-service gconf2 gconf2-common gettext gettext-base gir1.2-atk-1.0 gir1.2-freedesktop gir1.2-gconf-2.0 gir1.2-gdkpixbuf-2.0 gir1.2-glib-2.0 gir1.2-gtk-2.0 gir1.2-gtop-2.0 gir1.2-javascriptcoregtk-1.0 gir1.2-notify-0.7 gir1.2-pango-1.0 gir1.2-rsvg-2.0 gir1.2-soup-2.4 gir1.2-webkit-1.0 glib-networking glib-networking-common glib-networking-services groff-base gsettings-desktop-schemas html2text intltool intltool-debian iso-codes libaspell15 libasprintf0c2 libatk1.0-0 libatk1.0-data libatk1.0-dev libavahi-client3 libavahi-common-data libavahi-common3 libawn-dev libawn1 libblas3gf libcairo-gobject2 libcairo-script-interpreter2 libcairo2 libcairo2-dev libcap2 libcroco3 libcups2 libdatrie1 libdbus-1-3 libdbus-1-dev libdbus-glib-1-2 libdbus-glib-1-dev libdconf0 libdesktop-agnostic-bin libdesktop-agnostic-cfg-gconf libdesktop-agnostic-data libdesktop-agnostic-dev libdesktop-agnostic0 libdrm2 libelf1 libenchant1c2a libencode-locale-perl libexpat1 libexpat1-dev libffi-dev libffi5 libfile-listing-perl libfontconfig1 libfontconfig1-dev libfreetype6 libfreetype6-dev libgail18 libgconf-2-4 libgconf2-dev libgcrypt11 libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-common libgdk-pixbuf2.0-dev libgeoclue0 libgettextpo0 libgfortran3 libgirepository-1.0-1 libgl1-mesa-glx libglapi-mesa libglib2.0-0 libglib2.0-bin libglib2.0-data libglib2.0-dev libgnome-keyring-common libgnome-keyring0 libgnome-menu-dev libgnome-menu2 libgnutls26 libgpg-error0 libgssapi-krb5-2 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 libhttp-cookies-perl libhttp-date-perl libhttp-message-perl libhttp-negotiate-perl libhunspell-1.3-0 libice-dev libice6 libicu48 libio-socket-ssl-perl libjasper1 libjavascriptcoregtk-1.0-0 libjavascriptcoregtk-1.0-dev libjbig0 libjpeg8 libjs-jquery libk5crypto3 libkeyutils1 libkrb5-3 libkrb5support0 liblapack3gf libldap-2.4-2 liblwp-mediatypes-perl liblwp-protocol-https-perl libmagic1 libnet-http-perl libnet-ssleay-perl libnotify-dev libnotify4 liborc-0.4-0 libp11-kit0 libpango1.0-0 libpango1.0-dev libpcre3 libpcre3-dev libpcrecpp0 libpipeline1 libpixman-1-0 libpixman-1-dev libpng12-0 libpng12-dev libpopt0 libproxy0 libpthread-stubs0 libpthread-stubs0-dev libpython2.7 librsvg2-2 librsvg2-common librsvg2-dev libsasl2-2 libsexy-dev libsexy2 libsm-dev libsm6 libsoup-gnome2.4-1 libsoup2.4-1 libsoup2.4-dev libsqlite3-0 libssl-dev libssl1.0.0 libstartup-notification0 libstartup-notification0-dev libsystemd-login0 libtasn1-3 libthai-data libthai0 libtiff4 libunistring0 liburi-perl libvala-0.16-0 libvte-common libvte-dev libvte9 libwebkitgtk-1.0-0 libwebkitgtk-1.0-common libwebkitgtk-dev libwnck-common libwnck-dev libwnck22 libwww-perl libwww-robotrules-perl libx11-6 libx11-data libx11-dev libx11-xcb1 libxau-dev libxau6 libxcb-glx0 libxcb-render0 libxcb-render0-dev libxcb-shm0 libxcb-shm0-dev libxcb-util0 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 libxxf86vm1 m4 man-db mime-support netbase openssl pkg-config po-debconf psmisc python python-cairo python-cairo-dev python-dev python-gobject-2 python-gobject-2-dev python-gtk2 python-gtk2-dev python-minimal python-numpy python-support python2.7 python2.7-dev python2.7-minimal shared-mime-info ttf-dejavu-core valac valac-0.16 valac-0.16-vapi 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 xorg-sgml-doctools xtrans-dev zlib1g zlib1g-dev Suggested packages: aspell-doc spellutils autoconf2.13 autoconf-archive gnu-standards autoconf-doc libtool wamerican wordlist whois vacation dh-make ispell emacsen-common jed-extra gconf-defaults-service gettext-doc groff isoquery 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 rng-tools geoclue libglib2.0-doc gnome-keyring krb5-doc krb5-user libvisual-0.4-plugins gstreamer-codec-install gnome-codec-install gstreamer0.10-tools gstreamer0.10-plugins-base gvfs libgtk2.0-doc libdata-dump-perl libice-doc libjasper-runtime libcrypt-ssleay-perl ttf-baekmuk ttf-arphic-gbsn00lp ttf-arphic-bsmi00lp ttf-arphic-gkai00mp ttf-arphic-bkai00mp libpango1.0-doc imagemagick librsvg2-bin librsvg2-doc libsm-doc libsoup2.4-doc libauthen-ntlm-perl libxcb-doc libxext-doc less www-browser libmail-box-perl python-doc python-tk python-gobject-2-dbg python-gtk2-doc python-numpy-doc python-numpy-dbg python-nose gfortran python2.7-doc binfmt-support Recommended packages: curl wget lynx-cur autopoint enchant libgconf2-doc libgl1-mesa-dri hicolor-icon-theme libgtk2.0-bin hunspell-en-us hunspell-dictionary myspell-dictionary libio-socket-inet6-perl javascript-common krb5-locales notification-daemon libsasl2-modules libssl-doc libvte-doc gstreamer0.10-plugins-good gstreamer0.10-plugins-bad gstreamer0.10-ffmpeg libhtml-form-perl libhtml-format-perl libhttp-daemon-perl libmailtools-perl libx11-doc xml-core ifupdown libmail-sendmail-perl docbook-xsl The following NEW packages will be installed: adduser aspell aspell-en autoconf automake autotools-dev bsdmainutils ca-certificates dbus dbus-x11 dconf-gsettings-backend dconf-service debhelper dictionaries-common file fontconfig fontconfig-config gconf-service gconf2 gconf2-common gettext gettext-base gir1.2-atk-1.0 gir1.2-freedesktop gir1.2-gconf-2.0 gir1.2-gdkpixbuf-2.0 gir1.2-glib-2.0 gir1.2-gtk-2.0 gir1.2-gtop-2.0 gir1.2-javascriptcoregtk-1.0 gir1.2-notify-0.7 gir1.2-pango-1.0 gir1.2-rsvg-2.0 gir1.2-soup-2.4 gir1.2-webkit-1.0 glib-networking glib-networking-common glib-networking-services groff-base gsettings-desktop-schemas html2text intltool intltool-debian iso-codes libaspell15 libasprintf0c2 libatk1.0-0 libatk1.0-data libatk1.0-dev libavahi-client3 libavahi-common-data libavahi-common3 libawn-dev libawn1 libblas3gf libcairo-gobject2 libcairo-script-interpreter2 libcairo2 libcairo2-dev libcap2 libcroco3 libcups2 libdatrie1 libdbus-1-3 libdbus-1-dev libdbus-glib-1-2 libdbus-glib-1-dev libdconf0 libdesktop-agnostic-bin libdesktop-agnostic-cfg-gconf libdesktop-agnostic-data libdesktop-agnostic-dev libdesktop-agnostic0 libdrm2 libelf1 libenchant1c2a libencode-locale-perl libexpat1 libexpat1-dev libffi-dev libffi5 libfile-listing-perl libfontconfig1 libfontconfig1-dev libfreetype6 libfreetype6-dev libgail18 libgconf-2-4 libgconf2-dev libgcrypt11 libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-common libgdk-pixbuf2.0-dev libgeoclue0 libgettextpo0 libgfortran3 libgirepository-1.0-1 libgl1-mesa-glx libglapi-mesa libglib2.0-0 libglib2.0-bin libglib2.0-data libglib2.0-dev libgnome-keyring-common libgnome-keyring0 libgnome-menu-dev libgnome-menu2 libgnutls26 libgpg-error0 libgssapi-krb5-2 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 libhttp-cookies-perl libhttp-date-perl libhttp-message-perl libhttp-negotiate-perl libhunspell-1.3-0 libice-dev libice6 libicu48 libio-socket-ssl-perl libjasper1 libjavascriptcoregtk-1.0-0 libjavascriptcoregtk-1.0-dev libjbig0 libjpeg8 libjs-jquery libk5crypto3 libkeyutils1 libkrb5-3 libkrb5support0 liblapack3gf libldap-2.4-2 liblwp-mediatypes-perl liblwp-protocol-https-perl libmagic1 libnet-http-perl libnet-ssleay-perl libnotify-dev libnotify4 liborc-0.4-0 libp11-kit0 libpango1.0-0 libpango1.0-dev libpcre3 libpcre3-dev libpcrecpp0 libpipeline1 libpixman-1-0 libpixman-1-dev libpng12-0 libpng12-dev libpopt0 libproxy0 libpthread-stubs0 libpthread-stubs0-dev libpython2.7 librsvg2-2 librsvg2-common librsvg2-dev libsasl2-2 libsexy-dev libsexy2 libsm-dev libsm6 libsoup-gnome2.4-1 libsoup2.4-1 libsoup2.4-dev libsqlite3-0 libssl-dev libssl1.0.0 libstartup-notification0 libstartup-notification0-dev libsystemd-login0 libtasn1-3 libthai-data libthai0 libtiff4 libunistring0 liburi-perl libvala-0.16-0 libvte-common libvte-dev libvte9 libwebkitgtk-1.0-0 libwebkitgtk-1.0-common libwebkitgtk-dev libwnck-common libwnck-dev libwnck22 libwww-perl libwww-robotrules-perl libx11-6 libx11-data libx11-dev libx11-xcb1 libxau-dev libxau6 libxcb-glx0 libxcb-render0 libxcb-render0-dev libxcb-shm0 libxcb-shm0-dev libxcb-util0 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 libxxf86vm1 m4 man-db mime-support netbase openssl pkg-config po-debconf psmisc python python-cairo python-cairo-dev python-dev python-gobject-2 python-gobject-2-dev python-gtk2 python-gtk2-dev python-minimal python-numpy python-support python2.7 python2.7-dev python2.7-minimal sbuild-build-depends-awn-extras-applets-dummy shared-mime-info ttf-dejavu-core valac valac-0.16 valac-0.16-vapi 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 xorg-sgml-doctools xtrans-dev zlib1g-dev The following packages will be upgraded: zlib1g 1 upgraded, 289 newly installed, 0 to remove and 8 not upgraded. Need to get 5468 kB/144 MB of archives. After this operation, 368 MB of additional disk space will be used. Get:1 http://repo.raspbian.lan/raspbian/ testing/main zlib1g armhf 1:1.2.7.dfsg-13 [87.2 kB] Get:2 http://repo.raspbian.lan/raspbian/ testing/main libsqlite3-0 armhf 3.7.13-1 [413 kB] Get:3 http://repo.raspbian.lan/raspbian/ testing/main libx11-6 armhf 2:1.5.0-1 [836 kB] Get:4 http://repo.raspbian.lan/raspbian/ testing/main libglapi-mesa armhf 8.0.3-1 [64.5 kB] Get:5 http://repo.raspbian.lan/raspbian/ testing/main libx11-xcb1 armhf 2:1.5.0-1 [139 kB] Get:6 http://repo.raspbian.lan/raspbian/ testing/main libgl1-mesa-glx armhf 8.0.3-1 [157 kB] Get:7 http://repo.raspbian.lan/raspbian/ testing/main zlib1g-dev armhf 1:1.2.7.dfsg-13 [212 kB] Get:8 http://repo.raspbian.lan/raspbian/ testing/main libdesktop-agnostic-data armhf 0.3.92+dfsg-1 [5810 B] Get:9 http://repo.raspbian.lan/raspbian/ testing/main libdesktop-agnostic0 armhf 0.3.92+dfsg-1 [95.9 kB] Get:10 http://repo.raspbian.lan/raspbian/ testing/main libawn1 armhf 0.4.1~bzr830-2 [214 kB] Get:11 http://repo.raspbian.lan/raspbian/ testing/main libx11-dev armhf 2:1.5.0-1 [956 kB] Get:12 http://repo.raspbian.lan/raspbian/ testing/main libdesktop-agnostic-dev armhf 0.3.92+dfsg-1 [18.1 kB] Get:13 http://repo.raspbian.lan/raspbian/ testing/main libawn-dev armhf 0.4.1~bzr830-2 [131 kB] Get:14 http://repo.raspbian.lan/raspbian/ testing/main libgnome-menu2 armhf 3.0.1-4 [69.1 kB] Get:15 http://repo.raspbian.lan/raspbian/ testing/main libgnome-menu-dev armhf 3.0.1-4 [79.2 kB] Get:16 http://repo.raspbian.lan/raspbian/ testing/main libsexy2 armhf 0.1.11-2 [39.7 kB] Get:17 http://repo.raspbian.lan/raspbian/ testing/main libsexy-dev armhf 0.1.11-2 [45.2 kB] Get:18 http://repo.raspbian.lan/raspbian/ testing/main libvte-common all 1:0.28.2-4 [434 kB] Get:19 http://repo.raspbian.lan/raspbian/ testing/main libvte9 armhf 1:0.28.2-4 [704 kB] Get:20 http://repo.raspbian.lan/raspbian/ testing/main libvte-dev armhf 1:0.28.2-4 [734 kB] Get:21 http://repo.raspbian.lan/raspbian/ testing/main libdesktop-agnostic-cfg-gconf armhf 0.3.92+dfsg-1 [19.4 kB] Get:22 http://repo.raspbian.lan/raspbian/ testing/main libdesktop-agnostic-bin armhf 0.3.92+dfsg-1 [13.3 kB] debconf: delaying package configuration, since apt-utils is not installed Fetched 5468 kB in 1s (3367 kB/s) (Reading database ... 10659 files and directories currently installed.) Preparing to replace zlib1g:armhf 1:1.2.7.dfsg-11 (using .../zlib1g_1%3a1.2.7.dfsg-13_armhf.deb) ... Unpacking replacement zlib1g:armhf ... Setting up zlib1g:armhf (1:1.2.7.dfsg-13) ... Selecting previously unselected package libpcre3:armhf. (Reading database ... 10659 files and directories currently installed.) Unpacking libpcre3:armhf (from .../libpcre3_1%3a8.30-5_armhf.deb) ... Selecting previously unselected package libpipeline1:armhf. Unpacking libpipeline1:armhf (from .../libpipeline1_1.2.1-1_armhf.deb) ... Selecting previously unselected package libpopt0:armhf. Unpacking libpopt0:armhf (from .../libpopt0_1.16-7_armhf.deb) ... Selecting previously unselected package libssl1.0.0:armhf. Unpacking libssl1.0.0:armhf (from .../libssl1.0.0_1.0.1c-3+rpi1_armhf.deb) ... Selecting previously unselected package libasprintf0c2:armhf. Unpacking libasprintf0c2:armhf (from .../libasprintf0c2_0.18.1.1-9_armhf.deb) ... Selecting previously unselected package libgpg-error0:armhf. Unpacking libgpg-error0:armhf (from .../libgpg-error0_1.10-3_armhf.deb) ... Selecting previously unselected package libgcrypt11:armhf. Unpacking libgcrypt11:armhf (from .../libgcrypt11_1.5.0-3_armhf.deb) ... Selecting previously unselected package libp11-kit0:armhf. Unpacking libp11-kit0:armhf (from .../libp11-kit0_0.12-3_armhf.deb) ... Selecting previously unselected package libtasn1-3:armhf. Unpacking libtasn1-3:armhf (from .../libtasn1-3_2.13-2_armhf.deb) ... Selecting previously unselected package libgnutls26:armhf. Unpacking libgnutls26:armhf (from .../libgnutls26_2.12.20-1_armhf.deb) ... Selecting previously unselected package libkeyutils1:armhf. Unpacking libkeyutils1:armhf (from .../libkeyutils1_1.5.5-2_armhf.deb) ... Selecting previously unselected package libkrb5support0:armhf. Unpacking libkrb5support0:armhf (from .../libkrb5support0_1.10.1+dfsg-1_armhf.deb) ... Selecting previously unselected package libk5crypto3:armhf. Unpacking libk5crypto3:armhf (from .../libk5crypto3_1.10.1+dfsg-1_armhf.deb) ... Selecting previously unselected package libkrb5-3:armhf. Unpacking libkrb5-3:armhf (from .../libkrb5-3_1.10.1+dfsg-1_armhf.deb) ... Selecting previously unselected package libgssapi-krb5-2:armhf. Unpacking libgssapi-krb5-2:armhf (from .../libgssapi-krb5-2_1.10.1+dfsg-1_armhf.deb) ... Selecting previously unselected package libsasl2-2:armhf. Unpacking libsasl2-2:armhf (from .../libsasl2-2_2.1.25.dfsg1-4_armhf.deb) ... Selecting previously unselected package libldap-2.4-2:armhf. Unpacking libldap-2.4-2:armhf (from .../libldap-2.4-2_2.4.28-1.1+rpi1_armhf.deb) ... Selecting previously unselected package libmagic1:armhf. Unpacking libmagic1:armhf (from .../libmagic1_5.11-1_armhf.deb) ... Selecting previously unselected package libsqlite3-0:armhf. Unpacking libsqlite3-0:armhf (from .../libsqlite3-0_3.7.13-1_armhf.deb) ... Selecting previously unselected package libxml2:armhf. Unpacking libxml2:armhf (from .../libxml2_2.8.0+dfsg1-3_armhf.deb) ... Selecting previously unselected package libffi5:armhf. Unpacking libffi5:armhf (from .../libffi5_3.0.10-3+b3_armhf.deb) ... Selecting previously unselected package libglib2.0-0:armhf. Unpacking libglib2.0-0:armhf (from .../libglib2.0-0_2.32.3-1_armhf.deb) ... Selecting previously unselected package libatk1.0-data. Unpacking libatk1.0-data (from .../libatk1.0-data_2.4.0-2_all.deb) ... Selecting previously unselected package libatk1.0-0:armhf. Unpacking libatk1.0-0:armhf (from .../libatk1.0-0_2.4.0-2_armhf.deb) ... Selecting previously unselected package libavahi-common-data:armhf. Unpacking libavahi-common-data:armhf (from .../libavahi-common-data_0.6.31-1_armhf.deb) ... Selecting previously unselected package libavahi-common3:armhf. Unpacking libavahi-common3:armhf (from .../libavahi-common3_0.6.31-1_armhf.deb) ... Selecting previously unselected package libdbus-1-3:armhf. Unpacking libdbus-1-3:armhf (from .../libdbus-1-3_1.6.0-1_armhf.deb) ... Selecting previously unselected package libavahi-client3:armhf. Unpacking libavahi-client3:armhf (from .../libavahi-client3_0.6.31-1_armhf.deb) ... Selecting previously unselected package libexpat1:armhf. Unpacking libexpat1:armhf (from .../libexpat1_2.1.0-1_armhf.deb) ... Selecting previously unselected package libfreetype6:armhf. Unpacking libfreetype6:armhf (from .../libfreetype6_2.4.9-1_armhf.deb) ... Selecting previously unselected package ttf-dejavu-core. Unpacking ttf-dejavu-core (from .../ttf-dejavu-core_2.33-2_all.deb) ... Selecting previously unselected package fontconfig-config. Unpacking fontconfig-config (from .../fontconfig-config_2.9.0-6_all.deb) ... Selecting previously unselected package libfontconfig1:armhf. Unpacking libfontconfig1:armhf (from .../libfontconfig1_2.9.0-6_armhf.deb) ... Selecting previously unselected package libpixman-1-0:armhf. Unpacking libpixman-1-0:armhf (from .../libpixman-1-0_0.24.4-1_armhf.deb) ... Selecting previously unselected package libpng12-0:armhf. Unpacking libpng12-0:armhf (from .../libpng12-0_1.2.49-1_armhf.deb) ... Selecting previously unselected package libxau6:armhf. Unpacking libxau6:armhf (from .../libxau6_1%3a1.0.7-1_armhf.deb) ... Selecting previously unselected package libxdmcp6:armhf. Unpacking libxdmcp6:armhf (from .../libxdmcp6_1%3a1.1.1-1_armhf.deb) ... Selecting previously unselected package libxcb1:armhf. Unpacking libxcb1:armhf (from .../libxcb1_1.8.1-1_armhf.deb) ... Selecting previously unselected package libx11-data. Unpacking libx11-data (from .../libx11-data_2%3a1.5.0-1_all.deb) ... Selecting previously unselected package libx11-6:armhf. Unpacking libx11-6:armhf (from .../libx11-6_2%3a1.5.0-1_armhf.deb) ... Selecting previously unselected package libxcb-render0:armhf. Unpacking libxcb-render0:armhf (from .../libxcb-render0_1.8.1-1_armhf.deb) ... Selecting previously unselected package libxcb-shm0:armhf. Unpacking libxcb-shm0:armhf (from .../libxcb-shm0_1.8.1-1_armhf.deb) ... Selecting previously unselected package libxrender1:armhf. Unpacking libxrender1:armhf (from .../libxrender1_1%3a0.9.7-1_armhf.deb) ... Selecting previously unselected package libcairo2:armhf. Unpacking libcairo2:armhf (from .../libcairo2_1.12.2-1_armhf.deb) ... Selecting previously unselected package libcairo-gobject2:armhf. Unpacking libcairo-gobject2:armhf (from .../libcairo-gobject2_1.12.2-1_armhf.deb) ... Selecting previously unselected package libcairo-script-interpreter2:armhf. Unpacking libcairo-script-interpreter2:armhf (from .../libcairo-script-interpreter2_1.12.2-1_armhf.deb) ... Selecting previously unselected package libcroco3:armhf. Unpacking libcroco3:armhf (from .../libcroco3_0.6.5-1_armhf.deb) ... Selecting previously unselected package libcups2:armhf. Unpacking libcups2:armhf (from .../libcups2_1.5.3-1_armhf.deb) ... Selecting previously unselected package libdatrie1:armhf. Unpacking libdatrie1:armhf (from .../libdatrie1_0.2.5-3_armhf.deb) ... Selecting previously unselected package libdbus-glib-1-2:armhf. Unpacking libdbus-glib-1-2:armhf (from .../libdbus-glib-1-2_0.98-1_armhf.deb) ... Selecting previously unselected package libdconf0:armhf. Unpacking libdconf0:armhf (from .../libdconf0_0.12.1-1_armhf.deb) ... Selecting previously unselected package libdrm2:armhf. Unpacking libdrm2:armhf (from .../libdrm2_2.4.33-1_armhf.deb) ... Selecting previously unselected package libthai-data. Unpacking libthai-data (from .../libthai-data_0.1.18-1_all.deb) ... Selecting previously unselected package libthai0:armhf. Unpacking libthai0:armhf (from .../libthai0_0.1.18-1_armhf.deb) ... Selecting previously unselected package libxft2:armhf. Unpacking libxft2:armhf (from .../libxft2_2.2.0-3_armhf.deb) ... Selecting previously unselected package fontconfig. Unpacking fontconfig (from .../fontconfig_2.9.0-6_armhf.deb) ... Selecting previously unselected package libpango1.0-0:armhf. Unpacking libpango1.0-0:armhf (from .../libpango1.0-0_1.30.0-1_armhf.deb) ... Selecting previously unselected package libgtk2.0-common. Unpacking libgtk2.0-common (from .../libgtk2.0-common_2.24.10-1_all.deb) ... Selecting previously unselected package libjpeg8:armhf. Unpacking libjpeg8:armhf (from .../libjpeg8_8d-1_armhf.deb) ... Selecting previously unselected package libjasper1:armhf. Unpacking libjasper1:armhf (from .../libjasper1_1.900.1-13_armhf.deb) ... Selecting previously unselected package libjbig0:armhf. Unpacking libjbig0:armhf (from .../libjbig0_2.0-2_armhf.deb) ... Selecting previously unselected package libtiff4:armhf. Unpacking libtiff4:armhf (from .../libtiff4_3.9.6-5_armhf.deb) ... Selecting previously unselected package libgdk-pixbuf2.0-common. Unpacking libgdk-pixbuf2.0-common (from .../libgdk-pixbuf2.0-common_2.26.1-1_all.deb) ... Selecting previously unselected package libgdk-pixbuf2.0-0:armhf. Unpacking libgdk-pixbuf2.0-0:armhf (from .../libgdk-pixbuf2.0-0_2.26.1-1_armhf.deb) ... Selecting previously unselected package libxcomposite1:armhf. Unpacking libxcomposite1:armhf (from .../libxcomposite1_1%3a0.4.3-2_armhf.deb) ... Selecting previously unselected package libxfixes3:armhf. Unpacking libxfixes3:armhf (from .../libxfixes3_1%3a5.0-4_armhf.deb) ... Selecting previously unselected package libxcursor1:armhf. Unpacking libxcursor1:armhf (from .../libxcursor1_1%3a1.1.13-1_armhf.deb) ... Selecting previously unselected package libxdamage1:armhf. Unpacking libxdamage1:armhf (from .../libxdamage1_1%3a1.1.3-2_armhf.deb) ... Selecting previously unselected package libxext6:armhf. Unpacking libxext6:armhf (from .../libxext6_2%3a1.3.1-2_armhf.deb) ... Selecting previously unselected package libxi6:armhf. Unpacking libxi6:armhf (from .../libxi6_2%3a1.6.1-1_armhf.deb) ... Selecting previously unselected package libxinerama1:armhf. Unpacking libxinerama1:armhf (from .../libxinerama1_2%3a1.1.2-1_armhf.deb) ... Selecting previously unselected package libxrandr2:armhf. Unpacking libxrandr2:armhf (from .../libxrandr2_2%3a1.3.2-2_armhf.deb) ... Selecting previously unselected package shared-mime-info. Unpacking shared-mime-info (from .../shared-mime-info_1.0-1_armhf.deb) ... Selecting previously unselected package libgtk2.0-0:armhf. Unpacking libgtk2.0-0:armhf (from .../libgtk2.0-0_2.24.10-1_armhf.deb) ... Selecting previously unselected package libgail18:armhf. Unpacking libgail18:armhf (from .../libgail18_2.24.10-1_armhf.deb) ... Selecting previously unselected package gconf2-common. Unpacking gconf2-common (from .../gconf2-common_3.2.5-1_all.deb) ... Selecting previously unselected package libgconf-2-4:armhf. Unpacking libgconf-2-4:armhf (from .../libgconf-2-4_3.2.5-1_armhf.deb) ... Selecting previously unselected package libunistring0:armhf. Unpacking libunistring0:armhf (from .../libunistring0_0.9.3-5_armhf.deb) ... Selecting previously unselected package libgettextpo0:armhf. Unpacking libgettextpo0:armhf (from .../libgettextpo0_0.18.1.1-9_armhf.deb) ... Selecting previously unselected package libgfortran3:armhf. Unpacking libgfortran3:armhf (from .../libgfortran3_4.7.0-1.1+rpi_armhf.deb) ... Selecting previously unselected package libglapi-mesa:armhf. Unpacking libglapi-mesa:armhf (from .../libglapi-mesa_8.0.3-1_armhf.deb) ... Selecting previously unselected package libx11-xcb1:armhf. Unpacking libx11-xcb1:armhf (from .../libx11-xcb1_2%3a1.5.0-1_armhf.deb) ... Selecting previously unselected package libxcb-glx0:armhf. Unpacking libxcb-glx0:armhf (from .../libxcb-glx0_1.8.1-1_armhf.deb) ... Selecting previously unselected package libxxf86vm1:armhf. Unpacking libxxf86vm1:armhf (from .../libxxf86vm1_1%3a1.1.2-1_armhf.deb) ... Selecting previously unselected package libgl1-mesa-glx:armhf. Unpacking libgl1-mesa-glx:armhf (from .../libgl1-mesa-glx_8.0.3-1_armhf.deb) ... Selecting previously unselected package libgnome-keyring-common. Unpacking libgnome-keyring-common (from .../libgnome-keyring-common_3.4.1-1_all.deb) ... Selecting previously unselected package libgnome-keyring0:armhf. Unpacking libgnome-keyring0:armhf (from .../libgnome-keyring0_3.4.1-1_armhf.deb) ... Selecting previously unselected package libgstreamer0.10-0:armhf. Unpacking libgstreamer0.10-0:armhf (from .../libgstreamer0.10-0_0.10.36-1_armhf.deb) ... Selecting previously unselected package liborc-0.4-0:armhf. Unpacking liborc-0.4-0:armhf (from .../liborc-0.4-0_1%3a0.4.16-2_armhf.deb) ... Selecting previously unselected package iso-codes. Unpacking iso-codes (from .../iso-codes_3.36-1_all.deb) ... Selecting previously unselected package libgstreamer-plugins-base0.10-0:armhf. Unpacking libgstreamer-plugins-base0.10-0:armhf (from .../libgstreamer-plugins-base0.10-0_0.10.36-1_armhf.deb) ... Selecting previously unselected package libhunspell-1.3-0:armhf. Unpacking libhunspell-1.3-0:armhf (from .../libhunspell-1.3-0_1.3.2-4_armhf.deb) ... Selecting previously unselected package x11-common. Unpacking x11-common (from .../x11-common_1%3a7.6+13_all.deb) ... Selecting previously unselected package libice6:armhf. Unpacking libice6:armhf (from .../libice6_2%3a1.0.8-2_armhf.deb) ... Selecting previously unselected package libicu48:armhf. Unpacking libicu48:armhf (from .../libicu48_4.8.1.1-8_armhf.deb) ... Selecting previously unselected package libnotify4:armhf. Unpacking libnotify4:armhf (from .../libnotify4_0.7.5-1_armhf.deb) ... Selecting previously unselected package libpcrecpp0:armhf. Unpacking libpcrecpp0:armhf (from .../libpcrecpp0_1%3a8.30-5_armhf.deb) ... Selecting previously unselected package libproxy0:armhf. Unpacking libproxy0:armhf (from .../libproxy0_0.3.1-5_armhf.deb) ... Selecting previously unselected package librsvg2-2:armhf. Unpacking librsvg2-2:armhf (from .../librsvg2-2_2.36.1-1_armhf.deb) ... Selecting previously unselected package libsm6:armhf. Unpacking libsm6:armhf (from .../libsm6_2%3a1.2.1-2_armhf.deb) ... Selecting previously unselected package glib-networking-common. Unpacking glib-networking-common (from .../glib-networking-common_2.32.3-1_all.deb) ... Selecting previously unselected package glib-networking-services. Unpacking glib-networking-services (from .../glib-networking-services_2.32.3-1_armhf.deb) ... Selecting previously unselected package dconf-service. Unpacking dconf-service (from .../dconf-service_0.12.1-1_armhf.deb) ... Selecting previously unselected package dconf-gsettings-backend:armhf. Unpacking dconf-gsettings-backend:armhf (from .../dconf-gsettings-backend_0.12.1-1_armhf.deb) ... Selecting previously unselected package gsettings-desktop-schemas. Unpacking gsettings-desktop-schemas (from .../gsettings-desktop-schemas_3.4.2-1_all.deb) ... Selecting previously unselected package glib-networking:armhf. Unpacking glib-networking:armhf (from .../glib-networking_2.32.3-1_armhf.deb) ... Selecting previously unselected package libsoup2.4-1:armhf. Unpacking libsoup2.4-1:armhf (from .../libsoup2.4-1_2.38.1-2_armhf.deb) ... Selecting previously unselected package libsoup-gnome2.4-1:armhf. Unpacking libsoup-gnome2.4-1:armhf (from .../libsoup-gnome2.4-1_2.38.1-2_armhf.deb) ... Selecting previously unselected package libvala-0.16-0:armhf. Unpacking libvala-0.16-0:armhf (from .../libvala-0.16-0_0.16.0-2_armhf.deb) ... Selecting previously unselected package libxres1:armhf. Unpacking libxres1:armhf (from .../libxres1_2%3a1.0.6-1_armhf.deb) ... Selecting previously unselected package libxslt1.1:armhf. Unpacking libxslt1.1:armhf (from .../libxslt1.1_1.1.26-11_armhf.deb) ... Selecting previously unselected package libxt6:armhf. Unpacking libxt6:armhf (from .../libxt6_1%3a1.1.3-1_armhf.deb) ... Selecting previously unselected package libxcb-util0:armhf. Unpacking libxcb-util0:armhf (from .../libxcb-util0_0.3.8-2_armhf.deb) ... Selecting previously unselected package adduser. Unpacking adduser (from .../adduser_3.113+nmu3_all.deb) ... Selecting previously unselected package bsdmainutils. Unpacking bsdmainutils (from .../bsdmainutils_9.0.3_armhf.deb) ... Selecting previously unselected package groff-base. Unpacking groff-base (from .../groff-base_1.21-7_armhf.deb) ... Selecting previously unselected package man-db. Unpacking man-db (from .../man-db_2.6.1-2_armhf.deb) ... Selecting previously unselected package netbase. Unpacking netbase (from .../archives/netbase_5.0_all.deb) ... Selecting previously unselected package file. Unpacking file (from .../archives/file_5.11-1_armhf.deb) ... Selecting previously unselected package gettext-base. Unpacking gettext-base (from .../gettext-base_0.18.1.1-9_armhf.deb) ... Selecting previously unselected package libcap2. Unpacking libcap2 (from .../libcap2_1%3a2.22-1_armhf.deb) ... Selecting previously unselected package m4. Unpacking m4 (from .../archives/m4_1.4.16-3_armhf.deb) ... Selecting previously unselected package mime-support. Unpacking mime-support (from .../mime-support_3.52-1_all.deb) ... Selecting previously unselected package python2.7-minimal. Unpacking python2.7-minimal (from .../python2.7-minimal_2.7.3~rc2-2.1_armhf.deb) ... Selecting previously unselected package python2.7. Unpacking python2.7 (from .../python2.7_2.7.3~rc2-2.1_armhf.deb) ... Selecting previously unselected package python-minimal. Unpacking python-minimal (from .../python-minimal_2.7.3~rc2-1_all.deb) ... Selecting previously unselected package python. Unpacking python (from .../python_2.7.3~rc2-1_all.deb) ... Selecting previously unselected package python-support. Unpacking python-support (from .../python-support_1.0.14_all.deb) ... Selecting previously unselected package libaspell15. Unpacking libaspell15 (from .../libaspell15_0.60.7~20110707-1_armhf.deb) ... Selecting previously unselected package dictionaries-common. Unpacking dictionaries-common (from .../dictionaries-common_1.12.8_all.deb) ... Adding 'diversion of /usr/share/dict/words to /usr/share/dict/words.pre-dictionaries-common by dictionaries-common' Selecting previously unselected package aspell. Unpacking aspell (from .../aspell_0.60.7~20110707-1_armhf.deb) ... Selecting previously unselected package aspell-en. Unpacking aspell-en (from .../aspell-en_7.1-0-1_all.deb) ... Selecting previously unselected package autoconf. Unpacking autoconf (from .../autoconf_2.69-1_all.deb) ... Selecting previously unselected package autotools-dev. Unpacking autotools-dev (from .../autotools-dev_20120608.1_all.deb) ... Selecting previously unselected package automake. Unpacking automake (from .../automake_1%3a1.11.5-2_all.deb) ... Selecting previously unselected package openssl. Unpacking openssl (from .../openssl_1.0.1c-3+rpi1_armhf.deb) ... Selecting previously unselected package ca-certificates. Unpacking ca-certificates (from .../ca-certificates_20120212_all.deb) ... Selecting previously unselected package libsystemd-login0. Unpacking libsystemd-login0 (from .../libsystemd-login0_44-2_armhf.deb) ... Selecting previously unselected package dbus. Unpacking dbus (from .../dbus_1.6.0-1_armhf.deb) ... Selecting previously unselected package dbus-x11. Unpacking dbus-x11 (from .../dbus-x11_1.6.0-1_armhf.deb) ... Selecting previously unselected package html2text. Unpacking html2text (from .../html2text_1.3.2a-15_armhf.deb) ... Selecting previously unselected package gettext. Unpacking gettext (from .../gettext_0.18.1.1-9_armhf.deb) ... Selecting previously unselected package intltool-debian. Unpacking intltool-debian (from .../intltool-debian_0.35.0+20060710.1_all.deb) ... Selecting previously unselected package po-debconf. Unpacking po-debconf (from .../po-debconf_1.0.16+nmu2_all.deb) ... Selecting previously unselected package debhelper. Unpacking debhelper (from .../debhelper_9.20120608_all.deb) ... Selecting previously unselected package gconf-service. Unpacking gconf-service (from .../gconf-service_3.2.5-1_armhf.deb) ... Selecting previously unselected package psmisc. Unpacking psmisc (from .../psmisc_22.16-1_armhf.deb) ... Selecting previously unselected package gconf2. Unpacking gconf2 (from .../gconf2_3.2.5-1_armhf.deb) ... Selecting previously unselected package libgirepository-1.0-1. Unpacking libgirepository-1.0-1 (from .../libgirepository-1.0-1_1.32.1-1_armhf.deb) ... Selecting previously unselected package gir1.2-glib-2.0. Unpacking gir1.2-glib-2.0 (from .../gir1.2-glib-2.0_1.32.1-1_armhf.deb) ... Selecting previously unselected package gir1.2-atk-1.0. Unpacking gir1.2-atk-1.0 (from .../gir1.2-atk-1.0_2.4.0-2_armhf.deb) ... Selecting previously unselected package gir1.2-freedesktop. Unpacking gir1.2-freedesktop (from .../gir1.2-freedesktop_1.32.1-1_armhf.deb) ... Selecting previously unselected package gir1.2-gconf-2.0. Unpacking gir1.2-gconf-2.0 (from .../gir1.2-gconf-2.0_3.2.5-1_armhf.deb) ... Selecting previously unselected package gir1.2-gdkpixbuf-2.0. Unpacking gir1.2-gdkpixbuf-2.0 (from .../gir1.2-gdkpixbuf-2.0_2.26.1-1_armhf.deb) ... Selecting previously unselected package gir1.2-pango-1.0. Unpacking gir1.2-pango-1.0 (from .../gir1.2-pango-1.0_1.30.0-1_armhf.deb) ... Selecting previously unselected package gir1.2-gtk-2.0. Unpacking gir1.2-gtk-2.0 (from .../gir1.2-gtk-2.0_2.24.10-1_armhf.deb) ... Selecting previously unselected package libgtop2-common. Unpacking libgtop2-common (from .../libgtop2-common_2.28.4-3_all.deb) ... Selecting previously unselected package libgtop2-7. Unpacking libgtop2-7 (from .../libgtop2-7_2.28.4-3_armhf.deb) ... Selecting previously unselected package gir1.2-gtop-2.0. Unpacking gir1.2-gtop-2.0 (from .../gir1.2-gtop-2.0_2.28.4-3_armhf.deb) ... Selecting previously unselected package libjavascriptcoregtk-1.0-0. Unpacking libjavascriptcoregtk-1.0-0 (from .../libjavascriptcoregtk-1.0-0_1.8.1-2.1+rpi1_armhf.deb) ... Selecting previously unselected package libenchant1c2a. Unpacking libenchant1c2a (from .../libenchant1c2a_1.6.0-7_armhf.deb) ... Selecting previously unselected package libgeoclue0. Unpacking libgeoclue0 (from .../libgeoclue0_0.12.0-4_armhf.deb) ... Selecting previously unselected package libwebkitgtk-1.0-common. Unpacking libwebkitgtk-1.0-common (from .../libwebkitgtk-1.0-common_1.8.1-2.1+rpi1_all.deb) ... Selecting previously unselected package libwebkitgtk-1.0-0. Unpacking libwebkitgtk-1.0-0 (from .../libwebkitgtk-1.0-0_1.8.1-2.1+rpi1_armhf.deb) ... Selecting previously unselected package gir1.2-javascriptcoregtk-1.0. Unpacking gir1.2-javascriptcoregtk-1.0 (from .../gir1.2-javascriptcoregtk-1.0_1.8.1-2.1+rpi1_armhf.deb) ... Selecting previously unselected package gir1.2-notify-0.7. Unpacking gir1.2-notify-0.7 (from .../gir1.2-notify-0.7_0.7.5-1_armhf.deb) ... Selecting previously unselected package gir1.2-rsvg-2.0. Unpacking gir1.2-rsvg-2.0 (from .../gir1.2-rsvg-2.0_2.36.1-1_armhf.deb) ... Selecting previously unselected package gir1.2-soup-2.4. Unpacking gir1.2-soup-2.4 (from .../gir1.2-soup-2.4_2.38.1-2_armhf.deb) ... Selecting previously unselected package gir1.2-webkit-1.0. Unpacking gir1.2-webkit-1.0 (from .../gir1.2-webkit-1.0_1.8.1-2.1+rpi1_armhf.deb) ... Selecting previously unselected package liburi-perl. Unpacking liburi-perl (from .../liburi-perl_1.60-1_all.deb) ... Selecting previously unselected package libencode-locale-perl. Unpacking libencode-locale-perl (from .../libencode-locale-perl_1.03-1_all.deb) ... Selecting previously unselected package libhttp-date-perl. Unpacking libhttp-date-perl (from .../libhttp-date-perl_6.02-1_all.deb) ... Selecting previously unselected package libfile-listing-perl. Unpacking libfile-listing-perl (from .../libfile-listing-perl_6.04-1_all.deb) ... Selecting previously unselected package libhtml-tagset-perl. Unpacking libhtml-tagset-perl (from .../libhtml-tagset-perl_3.20-2_all.deb) ... Selecting previously unselected package libhtml-parser-perl. Unpacking libhtml-parser-perl (from .../libhtml-parser-perl_3.69-2_armhf.deb) ... Selecting previously unselected package libhtml-tree-perl. Unpacking libhtml-tree-perl (from .../libhtml-tree-perl_4.2-1_all.deb) ... Selecting previously unselected package liblwp-mediatypes-perl. Unpacking liblwp-mediatypes-perl (from .../liblwp-mediatypes-perl_6.02-1_all.deb) ... Selecting previously unselected package libhttp-message-perl. Unpacking libhttp-message-perl (from .../libhttp-message-perl_6.03-1_all.deb) ... Selecting previously unselected package libhttp-cookies-perl. Unpacking libhttp-cookies-perl (from .../libhttp-cookies-perl_6.00-2_all.deb) ... Selecting previously unselected package libhttp-negotiate-perl. Unpacking libhttp-negotiate-perl (from .../libhttp-negotiate-perl_6.00-2_all.deb) ... Selecting previously unselected package libnet-ssleay-perl. Unpacking libnet-ssleay-perl (from .../libnet-ssleay-perl_1.48-1_armhf.deb) ... Selecting previously unselected package libio-socket-ssl-perl. Unpacking libio-socket-ssl-perl (from .../libio-socket-ssl-perl_1.74-1_all.deb) ... Selecting previously unselected package libnet-http-perl. Unpacking libnet-http-perl (from .../libnet-http-perl_6.03-2_all.deb) ... Selecting previously unselected package liblwp-protocol-https-perl. Unpacking liblwp-protocol-https-perl (from .../liblwp-protocol-https-perl_6.03-1_all.deb) ... Selecting previously unselected package libwww-robotrules-perl. Unpacking libwww-robotrules-perl (from .../libwww-robotrules-perl_6.01-1_all.deb) ... Selecting previously unselected package libwww-perl. Unpacking libwww-perl (from .../libwww-perl_6.04-1_all.deb) ... Selecting previously unselected package libxml-parser-perl. Unpacking libxml-parser-perl (from .../libxml-parser-perl_2.41-1_armhf.deb) ... Selecting previously unselected package intltool. Unpacking intltool (from .../intltool_0.50.2-2_all.deb) ... Selecting previously unselected package pkg-config. Unpacking pkg-config (from .../pkg-config_0.26-1_armhf.deb) ... Selecting previously unselected package libelf1. Unpacking libelf1 (from .../libelf1_0.152-1+rpi1_armhf.deb) ... Selecting previously unselected package libglib2.0-data. Unpacking libglib2.0-data (from .../libglib2.0-data_2.32.3-1_all.deb) ... Selecting previously unselected package libglib2.0-bin. Unpacking libglib2.0-bin (from .../libglib2.0-bin_2.32.3-1_armhf.deb) ... Selecting previously unselected package libpcre3-dev. Unpacking libpcre3-dev (from .../libpcre3-dev_1%3a8.30-5_armhf.deb) ... Selecting previously unselected package zlib1g-dev:armhf. Unpacking zlib1g-dev:armhf (from .../zlib1g-dev_1%3a1.2.7.dfsg-13_armhf.deb) ... Selecting previously unselected package libglib2.0-dev. Unpacking libglib2.0-dev (from .../libglib2.0-dev_2.32.3-1_armhf.deb) ... Selecting previously unselected package libatk1.0-dev. Unpacking libatk1.0-dev (from .../libatk1.0-dev_2.4.0-2_armhf.deb) ... Selecting previously unselected package libdesktop-agnostic-data. Unpacking libdesktop-agnostic-data (from .../libdesktop-agnostic-data_0.3.92+dfsg-1_armhf.deb) ... Selecting previously unselected package libdesktop-agnostic0. Unpacking libdesktop-agnostic0 (from .../libdesktop-agnostic0_0.3.92+dfsg-1_armhf.deb) ... Selecting previously unselected package libawn1. Unpacking libawn1 (from .../libawn1_0.4.1~bzr830-2_armhf.deb) ... Selecting previously unselected package xorg-sgml-doctools. Unpacking xorg-sgml-doctools (from .../xorg-sgml-doctools_1%3a1.10-1_all.deb) ... Selecting previously unselected package x11proto-core-dev. Unpacking x11proto-core-dev (from .../x11proto-core-dev_7.0.23-1_all.deb) ... Selecting previously unselected package libxau-dev:armhf. Unpacking libxau-dev:armhf (from .../libxau-dev_1%3a1.0.7-1_armhf.deb) ... Selecting previously unselected package libxdmcp-dev:armhf. Unpacking libxdmcp-dev:armhf (from .../libxdmcp-dev_1%3a1.1.1-1_armhf.deb) ... Selecting previously unselected package x11proto-input-dev. Unpacking x11proto-input-dev (from .../x11proto-input-dev_2.2-1_all.deb) ... Selecting previously unselected package x11proto-kb-dev. Unpacking x11proto-kb-dev (from .../x11proto-kb-dev_1.0.6-1_all.deb) ... Selecting previously unselected package xtrans-dev. Unpacking xtrans-dev (from .../xtrans-dev_1.2.7-1_all.deb) ... Selecting previously unselected package libpthread-stubs0:armhf. Unpacking libpthread-stubs0:armhf (from .../libpthread-stubs0_0.3-3_armhf.deb) ... Selecting previously unselected package libpthread-stubs0-dev:armhf. Unpacking libpthread-stubs0-dev:armhf (from .../libpthread-stubs0-dev_0.3-3_armhf.deb) ... Selecting previously unselected package libxcb1-dev:armhf. Unpacking libxcb1-dev:armhf (from .../libxcb1-dev_1.8.1-1_armhf.deb) ... Selecting previously unselected package libx11-dev:armhf. Unpacking libx11-dev:armhf (from .../libx11-dev_2%3a1.5.0-1_armhf.deb) ... Selecting previously unselected package libpng12-dev. Unpacking libpng12-dev (from .../libpng12-dev_1.2.49-1_armhf.deb) ... Selecting previously unselected package libgdk-pixbuf2.0-dev. Unpacking libgdk-pixbuf2.0-dev (from .../libgdk-pixbuf2.0-dev_2.26.1-1_armhf.deb) ... Selecting previously unselected package libfreetype6-dev. Unpacking libfreetype6-dev (from .../libfreetype6-dev_2.4.9-1_armhf.deb) ... Selecting previously unselected package x11proto-render-dev. Unpacking x11proto-render-dev (from .../x11proto-render-dev_2%3a0.11.1-2_all.deb) ... Selecting previously unselected package libxrender-dev:armhf. Unpacking libxrender-dev:armhf (from .../libxrender-dev_1%3a0.9.7-1_armhf.deb) ... Selecting previously unselected package libexpat1-dev. Unpacking libexpat1-dev (from .../libexpat1-dev_2.1.0-1_armhf.deb) ... Selecting previously unselected package libfontconfig1-dev. Unpacking libfontconfig1-dev (from .../libfontconfig1-dev_2.9.0-6_armhf.deb) ... Selecting previously unselected package libxft-dev. Unpacking libxft-dev (from .../libxft-dev_2.2.0-3_armhf.deb) ... Selecting previously unselected package libice-dev:armhf. Unpacking libice-dev:armhf (from .../libice-dev_2%3a1.0.8-2_armhf.deb) ... Selecting previously unselected package libsm-dev:armhf. Unpacking libsm-dev:armhf (from .../libsm-dev_2%3a1.2.1-2_armhf.deb) ... Selecting previously unselected package libpixman-1-dev. Unpacking libpixman-1-dev (from .../libpixman-1-dev_0.24.4-1_armhf.deb) ... Selecting previously unselected package libxcb-render0-dev:armhf. Unpacking libxcb-render0-dev:armhf (from .../libxcb-render0-dev_1.8.1-1_armhf.deb) ... Selecting previously unselected package libxcb-shm0-dev:armhf. Unpacking libxcb-shm0-dev:armhf (from .../libxcb-shm0-dev_1.8.1-1_armhf.deb) ... Selecting previously unselected package libcairo2-dev. Unpacking libcairo2-dev (from .../libcairo2-dev_1.12.2-1_armhf.deb) ... Selecting previously unselected package libpango1.0-dev. Unpacking libpango1.0-dev (from .../libpango1.0-dev_1.30.0-1_armhf.deb) ... Selecting previously unselected package x11proto-xext-dev. Unpacking x11proto-xext-dev (from .../x11proto-xext-dev_7.2.1-1_all.deb) ... Selecting previously unselected package libxext-dev:armhf. Unpacking libxext-dev:armhf (from .../libxext-dev_2%3a1.3.1-2_armhf.deb) ... Selecting previously unselected package x11proto-xinerama-dev. Unpacking x11proto-xinerama-dev (from .../x11proto-xinerama-dev_1.2.1-2_all.deb) ... Selecting previously unselected package libxinerama-dev:armhf. Unpacking libxinerama-dev:armhf (from .../libxinerama-dev_2%3a1.1.2-1_armhf.deb) ... Selecting previously unselected package libxi-dev. Unpacking libxi-dev (from .../libxi-dev_2%3a1.6.1-1_armhf.deb) ... Selecting previously unselected package x11proto-randr-dev. Unpacking x11proto-randr-dev (from .../x11proto-randr-dev_1.3.2-2_all.deb) ... Selecting previously unselected package libxrandr-dev. Unpacking libxrandr-dev (from .../libxrandr-dev_2%3a1.3.2-2_armhf.deb) ... Selecting previously unselected package x11proto-fixes-dev. Unpacking x11proto-fixes-dev (from .../x11proto-fixes-dev_1%3a5.0-2_all.deb) ... Selecting previously unselected package libxfixes-dev. Unpacking libxfixes-dev (from .../libxfixes-dev_1%3a5.0-4_armhf.deb) ... Selecting previously unselected package libxcursor-dev:armhf. Unpacking libxcursor-dev:armhf (from .../libxcursor-dev_1%3a1.1.13-1_armhf.deb) ... Selecting previously unselected package x11proto-composite-dev. Unpacking x11proto-composite-dev (from .../x11proto-composite-dev_1%3a0.4.2-2_all.deb) ... Selecting previously unselected package libxcomposite-dev. Unpacking libxcomposite-dev (from .../libxcomposite-dev_1%3a0.4.3-2_armhf.deb) ... Selecting previously unselected package x11proto-damage-dev. Unpacking x11proto-damage-dev (from .../x11proto-damage-dev_1%3a1.2.1-2_all.deb) ... Selecting previously unselected package libxdamage-dev. Unpacking libxdamage-dev (from .../libxdamage-dev_1%3a1.1.3-2_armhf.deb) ... Selecting previously unselected package libxml2-utils. Unpacking libxml2-utils (from .../libxml2-utils_2.8.0+dfsg1-3_armhf.deb) ... Selecting previously unselected package libgtk2.0-dev. Unpacking libgtk2.0-dev (from .../libgtk2.0-dev_2.24.10-1_armhf.deb) ... Selecting previously unselected package libdesktop-agnostic-dev. Unpacking libdesktop-agnostic-dev (from .../libdesktop-agnostic-dev_0.3.92+dfsg-1_armhf.deb) ... Selecting previously unselected package libdbus-1-dev. Unpacking libdbus-1-dev (from .../libdbus-1-dev_1.6.0-1_armhf.deb) ... Selecting previously unselected package libdbus-glib-1-dev. Unpacking libdbus-glib-1-dev (from .../libdbus-glib-1-dev_0.98-1_armhf.deb) ... Selecting previously unselected package libawn-dev. Unpacking libawn-dev (from .../libawn-dev_0.4.1~bzr830-2_armhf.deb) ... Selecting previously unselected package libblas3gf. Unpacking libblas3gf (from .../libblas3gf_1.2.20110419-2_armhf.deb) ... Selecting previously unselected package libffi-dev:armhf. Unpacking libffi-dev:armhf (from .../libffi-dev_3.0.10-3+b3_armhf.deb) ... Selecting previously unselected package libgconf2-dev. Unpacking libgconf2-dev (from .../libgconf2-dev_3.2.5-1_armhf.deb) ... Selecting previously unselected package libgnome-menu2. Unpacking libgnome-menu2 (from .../libgnome-menu2_3.0.1-4_armhf.deb) ... Selecting previously unselected package libgnome-menu-dev. Unpacking libgnome-menu-dev (from .../libgnome-menu-dev_3.0.1-4_armhf.deb) ... Selecting previously unselected package libgtop2-dev. Unpacking libgtop2-dev (from .../libgtop2-dev_2.28.4-3_armhf.deb) ... Selecting previously unselected package libjs-jquery. Unpacking libjs-jquery (from .../libjs-jquery_1.7.2+debian-1_all.deb) ... Selecting previously unselected package liblapack3gf. Unpacking liblapack3gf (from .../liblapack3gf_3.3.1-1_armhf.deb) ... Selecting previously unselected package libnotify-dev. Unpacking libnotify-dev (from .../libnotify-dev_0.7.5-1_armhf.deb) ... Selecting previously unselected package libpython2.7. Unpacking libpython2.7 (from .../libpython2.7_2.7.3~rc2-2.1_armhf.deb) ... Selecting previously unselected package librsvg2-common:armhf. Unpacking librsvg2-common:armhf (from .../librsvg2-common_2.36.1-1_armhf.deb) ... Selecting previously unselected package librsvg2-dev. Unpacking librsvg2-dev (from .../librsvg2-dev_2.36.1-1_armhf.deb) ... Selecting previously unselected package libsexy2. Unpacking libsexy2 (from .../libsexy2_0.1.11-2_armhf.deb) ... Selecting previously unselected package libxml2-dev:armhf. Unpacking libxml2-dev:armhf (from .../libxml2-dev_2.8.0+dfsg1-3_armhf.deb) ... Selecting previously unselected package libsexy-dev. Unpacking libsexy-dev (from .../libsexy-dev_0.1.11-2_armhf.deb) ... Selecting previously unselected package libsoup2.4-dev. Unpacking libsoup2.4-dev (from .../libsoup2.4-dev_2.38.1-2_armhf.deb) ... Selecting previously unselected package libssl-dev. Unpacking libssl-dev (from .../libssl-dev_1.0.1c-3+rpi1_armhf.deb) ... Selecting previously unselected package libstartup-notification0. Unpacking libstartup-notification0 (from .../libstartup-notification0_0.12-1_armhf.deb) ... Selecting previously unselected package libstartup-notification0-dev. Unpacking libstartup-notification0-dev (from .../libstartup-notification0-dev_0.12-1_armhf.deb) ... Selecting previously unselected package libvte-common. Unpacking libvte-common (from .../libvte-common_1%3a0.28.2-4_all.deb) ... Selecting previously unselected package libvte9. Unpacking libvte9 (from .../libvte9_1%3a0.28.2-4_armhf.deb) ... Selecting previously unselected package libvte-dev. Unpacking libvte-dev (from .../libvte-dev_1%3a0.28.2-4_armhf.deb) ... Selecting previously unselected package libwnck-common. Unpacking libwnck-common (from .../libwnck-common_2.30.7-1_all.deb) ... Selecting previously unselected package libwnck22. Unpacking libwnck22 (from .../libwnck22_2.30.7-1_armhf.deb) ... Selecting previously unselected package x11proto-resource-dev. Unpacking x11proto-resource-dev (from .../x11proto-resource-dev_1.2.0-3_all.deb) ... Selecting previously unselected package libxres-dev. Unpacking libxres-dev (from .../libxres-dev_2%3a1.0.6-1_armhf.deb) ... Selecting previously unselected package libwnck-dev. Unpacking libwnck-dev (from .../libwnck-dev_2.30.7-1_armhf.deb) ... Selecting previously unselected package python-cairo. Unpacking python-cairo (from .../python-cairo_1.8.8-1_armhf.deb) ... Selecting previously unselected package python-cairo-dev. Unpacking python-cairo-dev (from .../python-cairo-dev_1.8.8-1_all.deb) ... Selecting previously unselected package python2.7-dev. Unpacking python2.7-dev (from .../python2.7-dev_2.7.3~rc2-2.1_armhf.deb) ... Selecting previously unselected package python-dev. Unpacking python-dev (from .../python-dev_2.7.3~rc2-1_all.deb) ... Selecting previously unselected package python-gobject-2. Unpacking python-gobject-2 (from .../python-gobject-2_2.28.6-10_armhf.deb) ... Selecting previously unselected package python-gobject-2-dev. Unpacking python-gobject-2-dev (from .../python-gobject-2-dev_2.28.6-10_all.deb) ... Selecting previously unselected package python-numpy. Unpacking python-numpy (from .../python-numpy_1%3a1.6.2-1_armhf.deb) ... Selecting previously unselected package python-gtk2. Unpacking python-gtk2 (from .../python-gtk2_2.24.0-3_armhf.deb) ... Selecting previously unselected package python-gtk2-dev. Unpacking python-gtk2-dev (from .../python-gtk2-dev_2.24.0-3_all.deb) ... Selecting previously unselected package valac-0.16-vapi. Unpacking valac-0.16-vapi (from .../valac-0.16-vapi_0.16.0-2_all.deb) ... Selecting previously unselected package valac-0.16. Unpacking valac-0.16 (from .../valac-0.16_0.16.0-2_armhf.deb) ... Selecting previously unselected package valac. Unpacking valac (from .../valac_0.16.0-2_all.deb) ... Selecting previously unselected package libdesktop-agnostic-cfg-gconf. Unpacking libdesktop-agnostic-cfg-gconf (from .../libdesktop-agnostic-cfg-gconf_0.3.92+dfsg-1_armhf.deb) ... Selecting previously unselected package libdesktop-agnostic-bin. Unpacking libdesktop-agnostic-bin (from .../libdesktop-agnostic-bin_0.3.92+dfsg-1_armhf.deb) ... Selecting previously unselected package libjavascriptcoregtk-1.0-dev. Unpacking libjavascriptcoregtk-1.0-dev (from .../libjavascriptcoregtk-1.0-dev_1.8.1-2.1+rpi1_armhf.deb) ... Selecting previously unselected package libwebkitgtk-dev. Unpacking libwebkitgtk-dev (from .../libwebkitgtk-dev_1.8.1-2.1+rpi1_armhf.deb) ... Selecting previously unselected package sbuild-build-depends-awn-extras-applets-dummy. Unpacking sbuild-build-depends-awn-extras-applets-dummy (from .../sbuild-build-depends-awn-extras-applets-dummy.deb) ... Setting up libpcre3:armhf (1:8.30-5) ... Setting up libpipeline1:armhf (1.2.1-1) ... Setting up libpopt0:armhf (1.16-7) ... Setting up libssl1.0.0:armhf (1.0.1c-3+rpi1) ... Setting up libasprintf0c2:armhf (0.18.1.1-9) ... Setting up libgpg-error0:armhf (1.10-3) ... Setting up libgcrypt11:armhf (1.5.0-3) ... Setting up libp11-kit0:armhf (0.12-3) ... Setting up libtasn1-3:armhf (2.13-2) ... Setting up libgnutls26:armhf (2.12.20-1) ... Setting up libkeyutils1:armhf (1.5.5-2) ... Setting up libkrb5support0:armhf (1.10.1+dfsg-1) ... Setting up libk5crypto3:armhf (1.10.1+dfsg-1) ... Setting up libkrb5-3:armhf (1.10.1+dfsg-1) ... Setting up libgssapi-krb5-2:armhf (1.10.1+dfsg-1) ... Setting up libsasl2-2:armhf (2.1.25.dfsg1-4) ... Setting up libldap-2.4-2:armhf (2.4.28-1.1+rpi1) ... Setting up libmagic1:armhf (5.11-1) ... Setting up libsqlite3-0:armhf (3.7.13-1) ... Setting up libxml2:armhf (2.8.0+dfsg1-3) ... Setting up libffi5:armhf (3.0.10-3+b3) ... Setting up libglib2.0-0:armhf (2.32.3-1) ... Setting up libatk1.0-data (2.4.0-2) ... Setting up libatk1.0-0:armhf (2.4.0-2) ... Setting up libavahi-common-data:armhf (0.6.31-1) ... Setting up libavahi-common3:armhf (0.6.31-1) ... Setting up libdbus-1-3:armhf (1.6.0-1) ... Setting up libavahi-client3:armhf (0.6.31-1) ... Setting up libexpat1:armhf (2.1.0-1) ... Setting up libfreetype6:armhf (2.4.9-1) ... Setting up ttf-dejavu-core (2.33-2) ... Setting up fontconfig-config (2.9.0-6) ... Setting up libfontconfig1:armhf (2.9.0-6) ... Setting up libpixman-1-0:armhf (0.24.4-1) ... Setting up libpng12-0:armhf (1.2.49-1) ... Setting up libxau6:armhf (1:1.0.7-1) ... Setting up libxdmcp6:armhf (1:1.1.1-1) ... Setting up libxcb1:armhf (1.8.1-1) ... Setting up libx11-data (2:1.5.0-1) ... Setting up libx11-6:armhf (2:1.5.0-1) ... Setting up libxcb-render0:armhf (1.8.1-1) ... Setting up libxcb-shm0:armhf (1.8.1-1) ... Setting up libxrender1:armhf (1:0.9.7-1) ... Setting up libcairo2:armhf (1.12.2-1) ... Setting up libcairo-gobject2:armhf (1.12.2-1) ... Setting up libcairo-script-interpreter2:armhf (1.12.2-1) ... Setting up libcroco3:armhf (0.6.5-1) ... Setting up libcups2:armhf (1.5.3-1) ... Setting up libdatrie1:armhf (0.2.5-3) ... Setting up libdbus-glib-1-2:armhf (0.98-1) ... Setting up libdconf0:armhf (0.12.1-1) ... Setting up libdrm2:armhf (2.4.33-1) ... Setting up libthai-data (0.1.18-1) ... Setting up libthai0:armhf (0.1.18-1) ... Setting up libxft2:armhf (2.2.0-3) ... Setting up fontconfig (2.9.0-6) ... Cleaning up old fontconfig caches... done. Regenerating fonts cache... done. Setting up libpango1.0-0:armhf (1.30.0-1) ... Setting up libgtk2.0-common (2.24.10-1) ... Setting up libjpeg8:armhf (8d-1) ... Setting up libjasper1:armhf (1.900.1-13) ... Setting up libjbig0:armhf (2.0-2) ... Setting up libtiff4:armhf (3.9.6-5) ... Setting up libgdk-pixbuf2.0-common (2.26.1-1) ... Setting up libgdk-pixbuf2.0-0:armhf (2.26.1-1) ... Setting up libxcomposite1:armhf (1:0.4.3-2) ... Setting up libxfixes3:armhf (1:5.0-4) ... Setting up libxcursor1:armhf (1:1.1.13-1) ... Setting up libxdamage1:armhf (1:1.1.3-2) ... Setting up libxext6:armhf (2:1.3.1-2) ... Setting up libxi6:armhf (2:1.6.1-1) ... Setting up libxinerama1:armhf (2:1.1.2-1) ... Setting up libxrandr2:armhf (2:1.3.2-2) ... Setting up shared-mime-info (1.0-1) ... Setting up libgtk2.0-0:armhf (2.24.10-1) ... Setting up libgail18:armhf (2.24.10-1) ... Setting up gconf2-common (3.2.5-1) ... Creating config file /etc/gconf/2/path with new version Setting up libgconf-2-4:armhf (3.2.5-1) ... Setting up libunistring0:armhf (0.9.3-5) ... Setting up libgettextpo0:armhf (0.18.1.1-9) ... Setting up libgfortran3:armhf (4.7.0-1.1+rpi) ... Setting up libglapi-mesa:armhf (8.0.3-1) ... Setting up libx11-xcb1:armhf (2:1.5.0-1) ... Setting up libxcb-glx0:armhf (1.8.1-1) ... Setting up libxxf86vm1:armhf (1:1.1.2-1) ... Setting up libgl1-mesa-glx:armhf (8.0.3-1) ... Setting up libgnome-keyring-common (3.4.1-1) ... Setting up libgnome-keyring0:armhf (3.4.1-1) ... Setting up libgstreamer0.10-0:armhf (0.10.36-1) ... Setting up liborc-0.4-0:armhf (1:0.4.16-2) ... Setting up iso-codes (3.36-1) ... Setting up libgstreamer-plugins-base0.10-0:armhf (0.10.36-1) ... Setting up libhunspell-1.3-0:armhf (1.3.2-4) ... Setting up x11-common (1:7.6+13) ... All runlevel operations denied by policy invoke-rc.d: policy-rc.d denied execution of start. Setting up libice6:armhf (2:1.0.8-2) ... Setting up libicu48:armhf (4.8.1.1-8) ... Setting up libnotify4:armhf (0.7.5-1) ... Setting up libpcrecpp0:armhf (1:8.30-5) ... Setting up libproxy0:armhf (0.3.1-5) ... Setting up librsvg2-2:armhf (2.36.1-1) ... Setting up libsm6:armhf (2:1.2.1-2) ... Setting up glib-networking-common (2.32.3-1) ... Setting up glib-networking-services (2.32.3-1) ... Setting up dconf-service (0.12.1-1) ... Setting up dconf-gsettings-backend:armhf (0.12.1-1) ... Setting up gsettings-desktop-schemas (3.4.2-1) ... Setting up glib-networking:armhf (2.32.3-1) ... Setting up libsoup2.4-1:armhf (2.38.1-2) ... Setting up libsoup-gnome2.4-1:armhf (2.38.1-2) ... Setting up libvala-0.16-0:armhf (0.16.0-2) ... Setting up libxres1:armhf (2:1.0.6-1) ... Setting up libxslt1.1:armhf (1.1.26-11) ... Setting up libxt6:armhf (1:1.1.3-1) ... Setting up libxcb-util0:armhf (0.3.8-2) ... Setting up adduser (3.113+nmu3) ... Setting up bsdmainutils (9.0.3) ... update-alternatives: using /usr/bin/bsd-write to provide /usr/bin/write (write) in auto mode. update-alternatives: using /usr/bin/bsd-from to provide /usr/bin/from (from) in auto mode. Setting up groff-base (1.21-7) ... Setting up man-db (2.6.1-2) ... Building database of manual pages ... Setting up netbase (5.0) ... Setting up file (5.11-1) ... Setting up gettext-base (0.18.1.1-9) ... Setting up libcap2 (1:2.22-1) ... Setting up m4 (1.4.16-3) ... Setting up mime-support (3.52-1) ... update-alternatives: using /usr/bin/see to provide /usr/bin/view (view) in auto mode. Setting up python2.7-minimal (2.7.3~rc2-2.1) ... Setting up python2.7 (2.7.3~rc2-2.1) ... Setting up python-minimal (2.7.3~rc2-1) ... Setting up python (2.7.3~rc2-1) ... Setting up python-support (1.0.14) ... Setting up libaspell15 (0.60.7~20110707-1) ... Setting up dictionaries-common (1.12.8) ... Setting up autoconf (2.69-1) ... Setting up autotools-dev (20120608.1) ... Setting up automake (1:1.11.5-2) ... update-alternatives: using /usr/bin/automake-1.11 to provide /usr/bin/automake (automake) in auto mode. Setting up openssl (1.0.1c-3+rpi1) ... Setting up ca-certificates (20120212) ... Updating certificates in /etc/ssl/certs... 151 added, 0 removed; done. Running hooks in /etc/ca-certificates/update.d....done. Setting up libsystemd-login0 (44-2) ... Setting up dbus (1.6.0-1) ... All runlevel operations denied by policy invoke-rc.d: policy-rc.d denied execution of start. Setting up dbus-x11 (1.6.0-1) ... Setting up html2text (1.3.2a-15) ... Setting up gettext (0.18.1.1-9) ... Setting up intltool-debian (0.35.0+20060710.1) ... Setting up po-debconf (1.0.16+nmu2) ... Setting up debhelper (9.20120608) ... Setting up gconf-service (3.2.5-1) ... Setting up psmisc (22.16-1) ... Setting up gconf2 (3.2.5-1) ... update-alternatives: using /usr/bin/gconftool-2 to provide /usr/bin/gconftool (gconftool) in auto mode. Setting up libgirepository-1.0-1 (1.32.1-1) ... Setting up gir1.2-glib-2.0 (1.32.1-1) ... Setting up gir1.2-atk-1.0 (2.4.0-2) ... Setting up gir1.2-freedesktop (1.32.1-1) ... Setting up gir1.2-gconf-2.0 (3.2.5-1) ... Setting up gir1.2-gdkpixbuf-2.0 (2.26.1-1) ... Setting up gir1.2-pango-1.0 (1.30.0-1) ... Setting up gir1.2-gtk-2.0 (2.24.10-1) ... Setting up libgtop2-common (2.28.4-3) ... Setting up libgtop2-7 (2.28.4-3) ... Setting up gir1.2-gtop-2.0 (2.28.4-3) ... Setting up libjavascriptcoregtk-1.0-0 (1.8.1-2.1+rpi1) ... Setting up libgeoclue0 (0.12.0-4) ... Setting up libwebkitgtk-1.0-common (1.8.1-2.1+rpi1) ... Setting up gir1.2-notify-0.7 (0.7.5-1) ... Setting up gir1.2-rsvg-2.0 (2.36.1-1) ... Setting up gir1.2-soup-2.4 (2.38.1-2) ... Setting up liburi-perl (1.60-1) ... Setting up libencode-locale-perl (1.03-1) ... Setting up libhttp-date-perl (6.02-1) ... Setting up libfile-listing-perl (6.04-1) ... Setting up libhtml-tagset-perl (3.20-2) ... Setting up libhtml-parser-perl (3.69-2) ... Setting up libhtml-tree-perl (4.2-1) ... Setting up liblwp-mediatypes-perl (6.02-1) ... Setting up libhttp-message-perl (6.03-1) ... Setting up libhttp-cookies-perl (6.00-2) ... Setting up libhttp-negotiate-perl (6.00-2) ... Setting up libnet-ssleay-perl (1.48-1) ... Setting up libio-socket-ssl-perl (1.74-1) ... Setting up libnet-http-perl (6.03-2) ... Setting up libwww-robotrules-perl (6.01-1) ... Setting up pkg-config (0.26-1) ... Setting up libelf1 (0.152-1+rpi1) ... Setting up libglib2.0-data (2.32.3-1) ... Setting up libglib2.0-bin (2.32.3-1) ... Setting up libpcre3-dev (1:8.30-5) ... Setting up zlib1g-dev:armhf (1:1.2.7.dfsg-13) ... Setting up libglib2.0-dev (2.32.3-1) ... Setting up libatk1.0-dev (2.4.0-2) ... Setting up libdesktop-agnostic-data (0.3.92+dfsg-1) ... Setting up libdesktop-agnostic0 (0.3.92+dfsg-1) ... Setting up libawn1 (0.4.1~bzr830-2) ... Setting up xorg-sgml-doctools (1:1.10-1) ... Setting up x11proto-core-dev (7.0.23-1) ... Setting up libxau-dev:armhf (1:1.0.7-1) ... Setting up libxdmcp-dev:armhf (1:1.1.1-1) ... Setting up x11proto-input-dev (2.2-1) ... Setting up x11proto-kb-dev (1.0.6-1) ... Setting up xtrans-dev (1.2.7-1) ... Setting up libpthread-stubs0:armhf (0.3-3) ... Setting up libpthread-stubs0-dev:armhf (0.3-3) ... Setting up libxcb1-dev:armhf (1.8.1-1) ... Setting up libx11-dev:armhf (2:1.5.0-1) ... Setting up libpng12-dev (1.2.49-1) ... Setting up libgdk-pixbuf2.0-dev (2.26.1-1) ... Setting up libfreetype6-dev (2.4.9-1) ... Setting up x11proto-render-dev (2:0.11.1-2) ... Setting up libxrender-dev:armhf (1:0.9.7-1) ... Setting up libexpat1-dev (2.1.0-1) ... Setting up libfontconfig1-dev (2.9.0-6) ... Setting up libxft-dev (2.2.0-3) ... Setting up libice-dev:armhf (2:1.0.8-2) ... Setting up libsm-dev:armhf (2:1.2.1-2) ... Setting up libpixman-1-dev (0.24.4-1) ... Setting up libxcb-render0-dev:armhf (1.8.1-1) ... Setting up libxcb-shm0-dev:armhf (1.8.1-1) ... Setting up libcairo2-dev (1.12.2-1) ... Setting up libpango1.0-dev (1.30.0-1) ... Setting up x11proto-xext-dev (7.2.1-1) ... Setting up libxext-dev:armhf (2:1.3.1-2) ... Setting up x11proto-xinerama-dev (1.2.1-2) ... Setting up libxinerama-dev:armhf (2:1.1.2-1) ... Setting up libxi-dev (2:1.6.1-1) ... Setting up x11proto-randr-dev (1.3.2-2) ... Setting up libxrandr-dev (2:1.3.2-2) ... Setting up x11proto-fixes-dev (1:5.0-2) ... Setting up libxfixes-dev (1:5.0-4) ... Setting up libxcursor-dev:armhf (1:1.1.13-1) ... Setting up x11proto-composite-dev (1:0.4.2-2) ... Setting up libxcomposite-dev (1:0.4.3-2) ... Setting up x11proto-damage-dev (1:1.2.1-2) ... Setting up libxdamage-dev (1:1.1.3-2) ... Setting up libxml2-utils (2.8.0+dfsg1-3) ... Setting up libgtk2.0-dev (2.24.10-1) ... Setting up libdesktop-agnostic-dev (0.3.92+dfsg-1) ... Setting up libdbus-1-dev (1.6.0-1) ... Setting up libdbus-glib-1-dev (0.98-1) ... Setting up libawn-dev (0.4.1~bzr830-2) ... Setting up libblas3gf (1.2.20110419-2) ... update-alternatives: using /usr/lib/libblas/libblas.so.3gf to provide /usr/lib/libblas.so.3gf (libblas.so.3gf) in auto mode. Setting up libffi-dev:armhf (3.0.10-3+b3) ... Setting up libgconf2-dev (3.2.5-1) ... Setting up libgnome-menu2 (3.0.1-4) ... Setting up libgnome-menu-dev (3.0.1-4) ... Setting up libgtop2-dev (2.28.4-3) ... Setting up libjs-jquery (1.7.2+debian-1) ... Setting up liblapack3gf (3.3.1-1) ... update-alternatives: using /usr/lib/lapack/liblapack.so.3gf to provide /usr/lib/liblapack.so.3gf (liblapack.so.3gf) in auto mode. Setting up libnotify-dev (0.7.5-1) ... Setting up libpython2.7 (2.7.3~rc2-2.1) ... Setting up librsvg2-common:armhf (2.36.1-1) ... Setting up librsvg2-dev (2.36.1-1) ... Setting up libxml2-dev:armhf (2.8.0+dfsg1-3) ... Setting up libsoup2.4-dev (2.38.1-2) ... Setting up libssl-dev (1.0.1c-3+rpi1) ... Setting up libstartup-notification0 (0.12-1) ... Setting up libstartup-notification0-dev (0.12-1) ... Setting up libvte-common (1:0.28.2-4) ... Setting up libvte9 (1:0.28.2-4) ... Setting up libvte-dev (1:0.28.2-4) ... Setting up libwnck-common (2.30.7-1) ... Setting up libwnck22 (2.30.7-1) ... Setting up x11proto-resource-dev (1.2.0-3) ... Setting up libxres-dev (2:1.0.6-1) ... Setting up libwnck-dev (2.30.7-1) ... Setting up python-cairo (1.8.8-1) ... Setting up python-cairo-dev (1.8.8-1) ... Setting up python2.7-dev (2.7.3~rc2-2.1) ... Setting up python-dev (2.7.3~rc2-1) ... Setting up python-gobject-2 (2.28.6-10) ... Setting up python-gobject-2-dev (2.28.6-10) ... Setting up python-numpy (1:1.6.2-1) ... Setting up python-gtk2 (2.24.0-3) ... Setting up python-gtk2-dev (2.24.0-3) ... Setting up valac-0.16-vapi (0.16.0-2) ... Setting up valac-0.16 (0.16.0-2) ... update-alternatives: using /usr/bin/valac-0.16 to provide /usr/bin/valac (valac) in auto mode. Setting up valac (0.16.0-2) ... Setting up libdesktop-agnostic-cfg-gconf (0.3.92+dfsg-1) ... Setting up libdesktop-agnostic-bin (0.3.92+dfsg-1) ... Processing triggers for dictionaries-common ... aspell-autobuildhash: processing: en [en-common] aspell-autobuildhash: processing: en [en-variant_0] aspell-autobuildhash: processing: en [en-variant_1] aspell-autobuildhash: processing: en [en-variant_2] aspell-autobuildhash: processing: en [en-w_accents-only] aspell-autobuildhash: processing: en [en-wo_accents-only] aspell-autobuildhash: processing: en [en_CA-variant_0] aspell-autobuildhash: processing: en [en_CA-variant_1] aspell-autobuildhash: processing: en [en_CA-w_accents-only] aspell-autobuildhash: processing: en [en_CA-wo_accents-only] aspell-autobuildhash: processing: en [en_GB-ise-w_accents-only] aspell-autobuildhash: processing: en [en_GB-ise-wo_accents-only] aspell-autobuildhash: processing: en [en_GB-ize-w_accents-only] aspell-autobuildhash: processing: en [en_GB-ize-wo_accents-only] aspell-autobuildhash: processing: en [en_GB-variant_0] aspell-autobuildhash: processing: en [en_GB-variant_1] aspell-autobuildhash: processing: en [en_US-w_accents-only] aspell-autobuildhash: processing: en [en_US-wo_accents-only] Setting up aspell (0.60.7~20110707-1) ... Processing triggers for dictionaries-common ... Setting up aspell-en (7.1-0-1) ... Processing triggers for dictionaries-common ... Setting up libenchant1c2a (1.6.0-7) ... Setting up libwebkitgtk-1.0-0 (1.8.1-2.1+rpi1) ... Setting up gir1.2-javascriptcoregtk-1.0 (1.8.1-2.1+rpi1) ... Setting up gir1.2-webkit-1.0 (1.8.1-2.1+rpi1) ... Setting up libsexy2 (0.1.11-2) ... Setting up libsexy-dev (0.1.11-2) ... Setting up libjavascriptcoregtk-1.0-dev (1.8.1-2.1+rpi1) ... Setting up libwebkitgtk-dev (1.8.1-2.1+rpi1) ... Setting up liblwp-protocol-https-perl (6.03-1) ... Setting up libwww-perl (6.04-1) ... Setting up libxml-parser-perl (2.41-1) ... Setting up intltool (0.50.2-2) ... Setting up sbuild-build-depends-awn-extras-applets-dummy (0.invalid.0) ... Processing triggers for libgdk-pixbuf2.0-0:armhf ... Processing triggers for python-support ... ┌──────────────────────────────────────────────────────────────────────────────┐ │ Build environment │ └──────────────────────────────────────────────────────────────────────────────┘ Kernel: Linux 3.2.0-2-mx5 armhf (armv7l) Toolchain package versions: binutils_2.22-6.1 dpkg-dev_1.16.3 g++-4.6_4.6.3-1.1+rpi2 gcc-4.6_4.6.3-1.1+rpi2 libc6-dev_2.13-33 libstdc++6_4.7.0-1.1+rpi libstdc++6-4.6-dev_4.6.3-1.1+rpi2 linux-libc-dev_3.2.18-1 Package versions: adduser_3.113+nmu3 apt_0.9.3+rpi1 aspell_0.60.7~20110707-1 aspell-en_7.1-0-1 autoconf_2.69-1 automake_1:1.11.5-2 autotools-dev_20120608.1 base-files_6.9 base-passwd_3.5.24 bash_4.2-2 binutils_2.22-6.1 bsdmainutils_9.0.3 bsdutils_1:2.20.1-5 build-essential_11.5+b1 bzip2_1.0.6-3 ca-certificates_20120212 coreutils_8.13-3.2 cpp_4:4.6.2-4 cpp-4.6_4.6.3-1.1+rpi2 dash_0.5.7-3 dbus_1.6.0-1 dbus-x11_1.6.0-1 dconf-gsettings-backend_0.12.1-1 dconf-service_0.12.1-1 debconf_1.5.43 debfoster_2.7-1.1 debhelper_9.20120608 debian-archive-keyring_2012.3 debianutils_4.3.1 dictionaries-common_1.12.8 diffutils_1:3.2-6 dpkg_1.16.3 dpkg-dev_1.16.3 e2fslibs_1.42.4-3 e2fsprogs_1.42.4-3 fakeroot_1.18.3-1 file_5.11-1 findutils_4.4.2-4 fontconfig_2.9.0-6 fontconfig-config_2.9.0-6 g++_4:4.6.2-4 g++-4.6_4.6.3-1.1+rpi2 gcc_4:4.6.2-4 gcc-4.4-base_4.4.7-1.1+rpi1 gcc-4.5-base_4.5.3-12+rpi1 gcc-4.6_4.6.3-1.1+rpi2 gcc-4.6-base_4.6.3-1.1+rpi2 gcc-4.7-base_4.7.0-1.1+rpi gconf-service_3.2.5-1 gconf2_3.2.5-1 gconf2-common_3.2.5-1 gettext_0.18.1.1-9 gettext-base_0.18.1.1-9 gir1.2-atk-1.0_2.4.0-2 gir1.2-freedesktop_1.32.1-1 gir1.2-gconf-2.0_3.2.5-1 gir1.2-gdkpixbuf-2.0_2.26.1-1 gir1.2-glib-2.0_1.32.1-1 gir1.2-gtk-2.0_2.24.10-1 gir1.2-gtop-2.0_2.28.4-3 gir1.2-javascriptcoregtk-1.0_1.8.1-2.1+rpi1 gir1.2-notify-0.7_0.7.5-1 gir1.2-pango-1.0_1.30.0-1 gir1.2-rsvg-2.0_2.36.1-1 gir1.2-soup-2.4_2.38.1-2 gir1.2-webkit-1.0_1.8.1-2.1+rpi1 glib-networking_2.32.3-1 glib-networking-common_2.32.3-1 glib-networking-services_2.32.3-1 gnupg_1.4.12-4 gpgv_1.4.12-4 grep_2.12-2 groff-base_1.21-7 gsettings-desktop-schemas_3.4.2-1 gzip_1.4-5 hostname_3.11 html2text_1.3.2a-15 initscripts_2.88dsf-22.1 insserv_1.14.0-3 intltool_0.50.2-2 intltool-debian_0.35.0+20060710.1 iso-codes_3.36-1 libacl1_2.2.51-7 libapt-pkg4.12_0.9.3+rpi1 libaspell15_0.60.7~20110707-1 libasprintf0c2_0.18.1.1-9 libatk1.0-0_2.4.0-2 libatk1.0-data_2.4.0-2 libatk1.0-dev_2.4.0-2 libattr1_1:2.4.46-7 libavahi-client3_0.6.31-1 libavahi-common-data_0.6.31-1 libavahi-common3_0.6.31-1 libawn-dev_0.4.1~bzr830-2 libawn1_0.4.1~bzr830-2 libblas3gf_1.2.20110419-2 libblkid1_2.20.1-5 libbz2-1.0_1.0.6-3 libc-bin_2.13-33 libc-dev-bin_2.13-33 libc6_2.13-33 libc6-dev_2.13-33 libcairo-gobject2_1.12.2-1 libcairo-script-interpreter2_1.12.2-1 libcairo2_1.12.2-1 libcairo2-dev_1.12.2-1 libcap2_1:2.22-1 libclass-isa-perl_0.36-3 libcomerr2_1.42.4-3 libcroco3_0.6.5-1 libcups2_1.5.3-1 libdatrie1_0.2.5-3 libdb5.1_5.1.29-1 libdbus-1-3_1.6.0-1 libdbus-1-dev_1.6.0-1 libdbus-glib-1-2_0.98-1 libdbus-glib-1-dev_0.98-1 libdconf0_0.12.1-1 libdesktop-agnostic-bin_0.3.92+dfsg-1 libdesktop-agnostic-cfg-gconf_0.3.92+dfsg-1 libdesktop-agnostic-data_0.3.92+dfsg-1 libdesktop-agnostic-dev_0.3.92+dfsg-1 libdesktop-agnostic0_0.3.92+dfsg-1 libdpkg-perl_1.16.3 libdrm2_2.4.33-1 libelf1_0.152-1+rpi1 libenchant1c2a_1.6.0-7 libencode-locale-perl_1.03-1 libexpat1_2.1.0-1 libexpat1-dev_2.1.0-1 libffi-dev_3.0.10-3+b3 libffi5_3.0.10-3+b3 libfile-fcntllock-perl_0.14-1 libfile-listing-perl_6.04-1 libfontconfig1_2.9.0-6 libfontconfig1-dev_2.9.0-6 libfreetype6_2.4.9-1 libfreetype6-dev_2.4.9-1 libgail18_2.24.10-1 libgc1c2_1:7.1-8 libgcc1_1:4.7.0-1.1+rpi libgconf-2-4_3.2.5-1 libgconf2-dev_3.2.5-1 libgcrypt11_1.5.0-3 libgdbm3_1.8.3-11 libgdk-pixbuf2.0-0_2.26.1-1 libgdk-pixbuf2.0-common_2.26.1-1 libgdk-pixbuf2.0-dev_2.26.1-1 libgeoclue0_0.12.0-4 libgettextpo0_0.18.1.1-9 libgfortran3_4.7.0-1.1+rpi libgirepository-1.0-1_1.32.1-1 libgl1-mesa-glx_8.0.3-1 libglapi-mesa_8.0.3-1 libglib2.0-0_2.32.3-1 libglib2.0-bin_2.32.3-1 libglib2.0-data_2.32.3-1 libglib2.0-dev_2.32.3-1 libgmp10_2:5.0.5+dfsg-2 libgnome-keyring-common_3.4.1-1 libgnome-keyring0_3.4.1-1 libgnome-menu-dev_3.0.1-4 libgnome-menu2_3.0.1-4 libgnutls26_2.12.20-1 libgomp1_4.7.0-1.1+rpi libgpg-error0_1.10-3 libgssapi-krb5-2_1.10.1+dfsg-1 libgstreamer-plugins-base0.10-0_0.10.36-1 libgstreamer0.10-0_0.10.36-1 libgtk2.0-0_2.24.10-1 libgtk2.0-common_2.24.10-1 libgtk2.0-dev_2.24.10-1 libgtop2-7_2.28.4-3 libgtop2-common_2.28.4-3 libgtop2-dev_2.28.4-3 libhtml-parser-perl_3.69-2 libhtml-tagset-perl_3.20-2 libhtml-tree-perl_4.2-1 libhttp-cookies-perl_6.00-2 libhttp-date-perl_6.02-1 libhttp-message-perl_6.03-1 libhttp-negotiate-perl_6.00-2 libhunspell-1.3-0_1.3.2-4 libice-dev_2:1.0.8-2 libice6_2:1.0.8-2 libicu48_4.8.1.1-8 libio-socket-ssl-perl_1.74-1 libjasper1_1.900.1-13 libjavascriptcoregtk-1.0-0_1.8.1-2.1+rpi1 libjavascriptcoregtk-1.0-dev_1.8.1-2.1+rpi1 libjbig0_2.0-2 libjpeg8_8d-1 libjs-jquery_1.7.2+debian-1 libk5crypto3_1.10.1+dfsg-1 libkeyutils1_1.5.5-2 libkrb5-3_1.10.1+dfsg-1 libkrb5support0_1.10.1+dfsg-1 liblapack3gf_3.3.1-1 libldap-2.4-2_2.4.28-1.1+rpi1 liblocale-gettext-perl_1.05-7 liblwp-mediatypes-perl_6.02-1 liblwp-protocol-https-perl_6.03-1 liblzma5_5.1.1alpha+20110809-3 libmagic1_5.11-1 libmount1_2.20.1-5 libmpc2_0.9-4 libmpfr4_3.1.0-5 libncurses5_5.9-8 libncursesw5_5.9-8 libnet-http-perl_6.03-2 libnet-ssleay-perl_1.48-1 libnotify-dev_0.7.5-1 libnotify4_0.7.5-1 liborc-0.4-0_1:0.4.16-2 libp11-kit0_0.12-3 libpam-modules_1.1.3-7.1 libpam-modules-bin_1.1.3-7.1 libpam-runtime_1.1.3-7.1 libpam0g_1.1.3-7.1 libpango1.0-0_1.30.0-1 libpango1.0-dev_1.30.0-1 libpcre3_1:8.30-5 libpcre3-dev_1:8.30-5 libpcrecpp0_1:8.30-5 libpipeline1_1.2.1-1 libpixman-1-0_0.24.4-1 libpixman-1-dev_0.24.4-1 libpng12-0_1.2.49-1 libpng12-dev_1.2.49-1 libpopt0_1.16-7 libproxy0_0.3.1-5 libpthread-stubs0_0.3-3 libpthread-stubs0-dev_0.3-3 libpython2.7_2.7.3~rc2-2.1 libreadline6_6.2-8 librsvg2-2_2.36.1-1 librsvg2-common_2.36.1-1 librsvg2-dev_2.36.1-1 libsasl2-2_2.1.25.dfsg1-4 libselinux1_2.1.9-5 libsemanage-common_2.1.6-2 libsemanage1_2.1.6-2 libsepol1_2.1.4-3 libsexy-dev_0.1.11-2 libsexy2_0.1.11-2 libslang2_2.2.4-10 libsm-dev_2:1.2.1-2 libsm6_2:1.2.1-2 libsoup-gnome2.4-1_2.38.1-2 libsoup2.4-1_2.38.1-2 libsoup2.4-dev_2.38.1-2 libsqlite3-0_3.7.13-1 libss2_1.42.2-2 libssl-dev_1.0.1c-3+rpi1 libssl1.0.0_1.0.1c-3+rpi1 libstartup-notification0_0.12-1 libstartup-notification0-dev_0.12-1 libstdc++6_4.7.0-1.1+rpi libstdc++6-4.6-dev_4.6.3-1.1+rpi2 libswitch-perl_2.16-2 libsystemd-login0_44-2 libtasn1-3_2.13-2 libtext-charwidth-perl_0.04-7 libtext-iconv-perl_1.7-5 libtext-wrapi18n-perl_0.06-7 libthai-data_0.1.18-1 libthai0_0.1.18-1 libtiff4_3.9.6-5 libtimedate-perl_1.2000-1 libtinfo5_5.9-8 libunistring0_0.9.3-5 liburi-perl_1.60-1 libusb-0.1-4_2:0.1.12-20 libustr-1.0-1_1.0.4-2 libuuid1_2.20.1-5 libvala-0.16-0_0.16.0-2 libvte-common_1:0.28.2-4 libvte-dev_1:0.28.2-4 libvte9_1:0.28.2-4 libwebkitgtk-1.0-0_1.8.1-2.1+rpi1 libwebkitgtk-1.0-common_1.8.1-2.1+rpi1 libwebkitgtk-dev_1.8.1-2.1+rpi1 libwnck-common_2.30.7-1 libwnck-dev_2.30.7-1 libwnck22_2.30.7-1 libwww-perl_6.04-1 libwww-robotrules-perl_6.01-1 libx11-6_2:1.5.0-1 libx11-data_2:1.5.0-1 libx11-dev_2:1.5.0-1 libx11-xcb1_2:1.5.0-1 libxau-dev_1:1.0.7-1 libxau6_1:1.0.7-1 libxcb-glx0_1.8.1-1 libxcb-render0_1.8.1-1 libxcb-render0-dev_1.8.1-1 libxcb-shm0_1.8.1-1 libxcb-shm0-dev_1.8.1-1 libxcb-util0_0.3.8-2 libxcb1_1.8.1-1 libxcb1-dev_1.8.1-1 libxcomposite-dev_1:0.4.3-2 libxcomposite1_1:0.4.3-2 libxcursor-dev_1:1.1.13-1 libxcursor1_1:1.1.13-1 libxdamage-dev_1:1.1.3-2 libxdamage1_1:1.1.3-2 libxdmcp-dev_1:1.1.1-1 libxdmcp6_1:1.1.1-1 libxext-dev_2:1.3.1-2 libxext6_2:1.3.1-2 libxfixes-dev_1:5.0-4 libxfixes3_1:5.0-4 libxft-dev_2.2.0-3 libxft2_2.2.0-3 libxi-dev_2:1.6.1-1 libxi6_2:1.6.1-1 libxinerama-dev_2:1.1.2-1 libxinerama1_2:1.1.2-1 libxml-parser-perl_2.41-1 libxml2_2.8.0+dfsg1-3 libxml2-dev_2.8.0+dfsg1-3 libxml2-utils_2.8.0+dfsg1-3 libxrandr-dev_2:1.3.2-2 libxrandr2_2:1.3.2-2 libxrender-dev_1:0.9.7-1 libxrender1_1:0.9.7-1 libxres-dev_2:1.0.6-1 libxres1_2:1.0.6-1 libxslt1.1_1.1.26-11 libxt6_1:1.1.3-1 libxxf86vm1_1:1.1.2-1 linux-libc-dev_3.2.18-1 login_1:4.1.5.1-1 lsb-base_4.1+Debian6 m4_1.4.16-3 make_3.81-8.2 man-db_2.6.1-2 mawk_1.3.3-17 mime-support_3.52-1 mount_2.20.1-5 multiarch-support_2.13-33 ncurses-base_5.9-7 ncurses-bin_5.9-8 netbase_5.0 openssl_1.0.1c-3+rpi1 passwd_1:4.1.5.1-1 patch_2.6.1-3 perl_5.14.2-11 perl-base_5.14.2-11 perl-modules_5.14.2-11 pkg-config_0.26-1 po-debconf_1.0.16+nmu2 psmisc_22.16-1 python_2.7.3~rc2-1 python-cairo_1.8.8-1 python-cairo-dev_1.8.8-1 python-dev_2.7.3~rc2-1 python-gobject-2_2.28.6-10 python-gobject-2-dev_2.28.6-10 python-gtk2_2.24.0-3 python-gtk2-dev_2.24.0-3 python-minimal_2.7.3~rc2-1 python-numpy_1:1.6.2-1 python-support_1.0.14 python2.7_2.7.3~rc2-2.1 python2.7-dev_2.7.3~rc2-2.1 python2.7-minimal_2.7.3~rc2-2.1 raspbian-archive-keyring_20120528.2 readline-common_6.2-8 sbuild-build-depends-awn-extras-applets-dummy_0.invalid.0 sbuild-build-depends-core-dummy_0.invalid.0 sed_4.2.1-10 sensible-utils_0.0.7 shared-mime-info_1.0-1 sysv-rc_2.88dsf-22.1 sysvinit_2.88dsf-22.1 sysvinit-utils_2.88dsf-22.1 tar_1.26-4 ttf-dejavu-core_2.33-2 tzdata_2012c-1 ucf_3.0025+nmu3 util-linux_2.20.1-5 valac_0.16.0-2 valac-0.16_0.16.0-2 valac-0.16-vapi_0.16.0-2 x11-common_1:7.6+13 x11proto-composite-dev_1:0.4.2-2 x11proto-core-dev_7.0.23-1 x11proto-damage-dev_1:1.2.1-2 x11proto-fixes-dev_1:5.0-2 x11proto-input-dev_2.2-1 x11proto-kb-dev_1.0.6-1 x11proto-randr-dev_1.3.2-2 x11proto-render-dev_2:0.11.1-2 x11proto-resource-dev_1.2.0-3 x11proto-xext-dev_7.2.1-1 x11proto-xinerama-dev_1.2.1-2 xorg-sgml-doctools_1:1.10-1 xtrans-dev_1.2.7-1 xz-utils_5.1.1alpha+20110809-3 zlib1g_1:1.2.7.dfsg-13 zlib1g-dev_1:1.2.7.dfsg-13 ┌──────────────────────────────────────────────────────────────────────────────┐ │ Build │ └──────────────────────────────────────────────────────────────────────────────┘ Unpack source ───────────── gpgv: keyblock resource `/sbuild-nonexistent/.gnupg/trustedkeys.gpg': file open error gpgv: Signature made Sun Apr 1 21:46:17 2012 UTC using RSA key ID 18F5FBCE gpgv: Can't check signature: public key not found dpkg-source: warning: failed to verify signature on ./awn-extras-applets_0.4.0-5.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: unpacking awn-extras-applets_0.4.0-5.debian.tar.gz dpkg-source: info: applying 02-shinyswitcher-default-layout.patch dpkg-source: info: applying 03-libnotify07.patch dpkg-source: info: applying 04-glib-single-include.patch Check disc space ──────────────── Sufficient free space for build User Environment ──────────────── HOME=/sbuild-nonexistent LOGNAME=buildd PATH=/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin:/usr/games SCHROOT_CHROOT_NAME=testing-armhf-sbuild SCHROOT_COMMAND=env SCHROOT_GID=108 SCHROOT_GROUP=buildd SCHROOT_SESSION_ID=testing-armhf-sbuild-5fdc5882-e2b2-4692-8fad-c4b05e5cc92b SCHROOT_UID=106 SCHROOT_USER=buildd SHELL=/bin/sh TERM=xterm USER=buildd dpkg-buildpackage ───────────────── dpkg-buildpackage: source package awn-extras-applets dpkg-buildpackage: source version 0.4.0-5 dpkg-source --before-build awn-extras-applets-0.4.0 dpkg-buildpackage: host architecture armhf fakeroot debian/rules clean dh --with python2 clean dh_testdir dh_auto_clean dh_clean debian/rules build-arch dh --with python2 build-arch dh_testdir -a debian/rules override_dh_auto_configure make[1]: Entering directory `/«PKGBUILDDIR»' dh_auto_configure -- --disable-pymod-checks --with-webkit checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... no checking for mawk... mawk checking whether make sets $(MAKE)... yes checking how to create a ustar tar archive... gnutar checking whether to enable maintainer-specific portions of Makefiles... no checking for style of include used by make... GNU checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking dependency style of gcc... none checking for library containing strerror... none required checking for gcc... (cached) gcc checking whether we are using the GNU C compiler... (cached) yes checking whether gcc accepts -g... (cached) yes checking for gcc option to accept ISO C89... (cached) none needed checking dependency style of gcc... (cached) none checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking build system type... arm-unknown-linux-gnueabihf checking host system type... arm-unknown-linux-gnueabihf 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.50.2 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.14.2 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.7 checking for python platform... linux2 checking for python script directory... ${prefix}/lib/python2.7/dist-packages checking for python extension module directory... ${exec_prefix}/lib/python2.7/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.6.0 Using config source xml:merged:/etc/gconf/gconf.xml.defaults for schema installation Using $(sysconfdir)/gconf/schemas as install directory for schema files checking for 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 `/«PKGBUILDDIR»' dh_auto_build -a make[1]: Entering directory `/«PKGBUILDDIR»' make[2]: Entering directory `/«PKGBUILDDIR»' Making all in applets make[3]: Entering directory `/«PKGBUILDDIR»/applets' Making all in maintained/animal-farm make[4]: Entering directory `/«PKGBUILDDIR»/applets/maintained/animal-farm' Generating and caching the translation database Merging translations into animal-farm.desktop. make[4]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/animal-farm' Making all in maintained/awnterm make[4]: Entering directory `/«PKGBUILDDIR»/applets/maintained/awnterm' make[5]: Entering directory `/«PKGBUILDDIR»/applets/maintained/awnterm' CC awn-terminal.o In file included from awn-terminal.c:41:0: /usr/include/glib-2.0/glib/gi18n.h:28:0: warning: "_" redefined [enabled by default] /usr/include/glib-2.0/glib/gi18n-lib.h:32:0: note: this is the location of the previous definition /usr/include/glib-2.0/glib/gi18n.h:29:0: warning: "Q_" redefined [enabled by default] /usr/include/glib-2.0/glib/gi18n-lib.h:33:0: note: this is the location of the previous definition /usr/include/glib-2.0/glib/gi18n.h:31:0: warning: "C_" redefined [enabled by default] /usr/include/glib-2.0/glib/gi18n-lib.h:35:0: note: this is the location of the previous definition awn-terminal.c: In function 'awn_terminal_applet_create_new_tab': awn-terminal.c:885:2: warning: 'vte_terminal_fork_command' is deprecated (declared at /usr/include/vte-0.0/vte/vtedeprecated.h:82) [-Wdeprecated-declarations] awn-terminal.c: In function 'awn_terminal_applet_exited_cb': awn-terminal.c:1035:3: warning: 'vte_terminal_fork_command' is deprecated (declared at /usr/include/vte-0.0/vte/vtedeprecated.h:82) [-Wdeprecated-declarations] 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 `/«PKGBUILDDIR»/applets/maintained/awnterm' make[4]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/awnterm' Making all in maintained/bandwidth-monitor make[4]: Entering directory `/«PKGBUILDDIR»/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 `/«PKGBUILDDIR»/applets/maintained/bandwidth-monitor' Making all in maintained/battery make[4]: Entering directory `/«PKGBUILDDIR»/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 `/«PKGBUILDDIR»/applets/maintained/battery' Making all in maintained/cairo-clock make[4]: Entering directory `/«PKGBUILDDIR»/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 `/«PKGBUILDDIR»/applets/maintained/cairo-clock' Making all in maintained/comics make[4]: Entering directory `/«PKGBUILDDIR»/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 `/«PKGBUILDDIR»/applets/maintained/comics' Making all in maintained/cpufreq make[4]: Entering directory `/«PKGBUILDDIR»/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 `/«PKGBUILDDIR»/applets/maintained/cpufreq' Making all in maintained/dialect make[4]: Entering directory `/«PKGBUILDDIR»/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 `/«PKGBUILDDIR»/applets/maintained/dialect' Making all in maintained/digital-clock make[4]: Entering directory `/«PKGBUILDDIR»/applets/maintained/digital-clock' make[5]: Entering directory `/«PKGBUILDDIR»/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 `/«PKGBUILDDIR»/applets/maintained/digital-clock' make[4]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/digital-clock' Making all in maintained/feeds make[4]: Entering directory `/«PKGBUILDDIR»/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 `/«PKGBUILDDIR»/applets/maintained/feeds' Making all in maintained/file-browser-launcher make[4]: Entering directory `/«PKGBUILDDIR»/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 `/«PKGBUILDDIR»/applets/maintained/file-browser-launcher' Making all in maintained/hardware-sensors make[4]: Entering directory `/«PKGBUILDDIR»/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 `/«PKGBUILDDIR»/applets/maintained/hardware-sensors' Making all in maintained/mail make[4]: Entering directory `/«PKGBUILDDIR»/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 `/«PKGBUILDDIR»/applets/maintained/mail' Making all in maintained/media-control make[4]: Entering directory `/«PKGBUILDDIR»/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 `/«PKGBUILDDIR»/applets/maintained/media-control' Making all in maintained/media-icons make[4]: Entering directory `/«PKGBUILDDIR»/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 `/«PKGBUILDDIR»/applets/maintained/media-icons' Making all in maintained/media-player make[4]: Entering directory `/«PKGBUILDDIR»/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 `/«PKGBUILDDIR»/applets/maintained/media-player' Making all in maintained/mount make[4]: Entering directory `/«PKGBUILDDIR»/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 `/«PKGBUILDDIR»/applets/maintained/mount' Making all in maintained/places make[4]: Entering directory `/«PKGBUILDDIR»/applets/maintained/places' CC applet.o applet.c: In function 'build_menu_widget': applet.c:491:7: warning: 'gdk_pixbuf_ref' is deprecated (declared at /usr/include/gdk-pixbuf-2.0/gdk-pixbuf/gdk-pixbuf-core.h:241): Use 'g_object_ref' instead [-Wdeprecated-declarations] applet.c:503:7: warning: 'gdk_pixbuf_ref' is deprecated (declared at /usr/include/gdk-pixbuf-2.0/gdk-pixbuf/gdk-pixbuf-core.h:241): Use 'g_object_ref' instead [-Wdeprecated-declarations] applet.c: In function '_button_clicked_event': applet.c:1207:7: warning: passing argument 1 of 'awn_utils_show_menu_images' from incompatible pointer type [enabled by default] /usr/include/libawn/awn-utils.h:88:6: 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 `/«PKGBUILDDIR»/applets/maintained/places' Making all in maintained/quit make[4]: Entering directory `/«PKGBUILDDIR»/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 `/«PKGBUILDDIR»/applets/maintained/quit' Making all in maintained/slickswitcher make[4]: Entering directory `/«PKGBUILDDIR»/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 `/«PKGBUILDDIR»/applets/maintained/slickswitcher' Making all in maintained/shiny-switcher make[4]: Entering directory `/«PKGBUILDDIR»/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 `/«PKGBUILDDIR»/applets/maintained/shiny-switcher' Making all in maintained/sysmon make[4]: Entering directory `/«PKGBUILDDIR»/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 `/«PKGBUILDDIR»/applets/maintained/sysmon' Making all in maintained/thinkhdaps make[4]: Entering directory `/«PKGBUILDDIR»/applets/maintained/thinkhdaps' Found cached translation database Merging translations into thinkhdaps.desktop. make[4]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/thinkhdaps' Making all in maintained/to-do make[4]: Entering directory `/«PKGBUILDDIR»/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 `/«PKGBUILDDIR»/applets/maintained/to-do' Making all in maintained/tomboy-applet make[4]: Entering directory `/«PKGBUILDDIR»/applets/maintained/tomboy-applet' Found cached translation database Merging translations into tomboy-applet.desktop. make[4]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/tomboy-applet' Making all in maintained/volume-control make[4]: Entering directory `/«PKGBUILDDIR»/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 `/«PKGBUILDDIR»/applets/maintained/volume-control' Making all in maintained/weather make[4]: Entering directory `/«PKGBUILDDIR»/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 `/«PKGBUILDDIR»/applets/maintained/weather' Making all in maintained/garbage make[4]: Entering directory `/«PKGBUILDDIR»/applets/maintained/garbage' make[5]: Entering directory `/«PKGBUILDDIR»/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 `/«PKGBUILDDIR»/applets/maintained/garbage' make[4]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/garbage' Making all in maintained/notification-area make[4]: Entering directory `/«PKGBUILDDIR»/applets/maintained/notification-area' make[5]: Entering directory `/«PKGBUILDDIR»/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 `/«PKGBUILDDIR»/applets/maintained/notification-area' make[4]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/notification-area' Making all in maintained/showdesktop make[4]: Entering directory `/«PKGBUILDDIR»/applets/maintained/showdesktop' make[5]: Entering directory `/«PKGBUILDDIR»/applets/maintained/showdesktop' CC applet.o LINK showdesktop.la Found cached translation database Merging translations into showdesktop.desktop. make[5]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/showdesktop' make[4]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/showdesktop' Making all in unmaintained/awnsystemmonitor make[4]: Entering directory `/«PKGBUILDDIR»/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 `/«PKGBUILDDIR»/applets/unmaintained/awnsystemmonitor' Making all in maintained/calendar make[4]: Entering directory `/«PKGBUILDDIR»/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 `/«PKGBUILDDIR»/applets/maintained/calendar' Making all in maintained/notification-daemon make[4]: Entering directory `/«PKGBUILDDIR»/applets/maintained/notification-daemon' make[5]: Entering directory `/«PKGBUILDDIR»/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 `/«PKGBUILDDIR»/applets/maintained/notification-daemon' make[4]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/notification-daemon' Making all in maintained/cairo-menu make[4]: Entering directory `/«PKGBUILDDIR»/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 `/«PKGBUILDDIR»/applets/maintained/cairo-menu' Making all in unmaintained/main-menu make[4]: Entering directory `/«PKGBUILDDIR»/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 `/«PKGBUILDDIR»/applets/unmaintained/main-menu' Making all in unmaintained/MiMenu make[4]: Entering directory `/«PKGBUILDDIR»/applets/unmaintained/MiMenu' Found cached translation database Merging translations into mimenu.desktop. make[4]: Leaving directory `/«PKGBUILDDIR»/applets/unmaintained/MiMenu' Making all in unmaintained/pandora make[4]: Entering directory `/«PKGBUILDDIR»/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 `/«PKGBUILDDIR»/applets/unmaintained/pandora' Making all in unmaintained/stacks make[4]: Entering directory `/«PKGBUILDDIR»/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 `/«PKGBUILDDIR»/applets/unmaintained/stacks' Making all in maintained/yama make[4]: Entering directory `/«PKGBUILDDIR»/applets/maintained/yama' Found cached translation database Merging translations into yama.desktop. make[4]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/yama' Making all in maintained/webapplet make[4]: Entering directory `/«PKGBUILDDIR»/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. Found cached translation database Merging translations into awn-applet-webapplet.schema-ini. GEN awn-applet-webapplet.schemas make[4]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/webapplet' make[3]: Leaving directory `/«PKGBUILDDIR»/applets' Making all in shared/python Making all in shared/vala Making all in po make[3]: Entering directory `/«PKGBUILDDIR»/po' make[3]: Leaving directory `/«PKGBUILDDIR»/po' make[2]: Leaving directory `/«PKGBUILDDIR»' make[1]: Leaving directory `/«PKGBUILDDIR»' debian/rules override_dh_auto_test make[1]: Entering directory `/«PKGBUILDDIR»' #Pass, tests don't pass for now. make[1]: Leaving directory `/«PKGBUILDDIR»' fakeroot debian/rules binary-arch dh --with python2 binary-arch dh_testroot -a dh_prep -a dh_installdirs -a dh_auto_install -a make[1]: Entering directory `/«PKGBUILDDIR»' Making install in applets make[2]: Entering directory `/«PKGBUILDDIR»/applets' Making install in maintained/animal-farm make[3]: Entering directory `/«PKGBUILDDIR»/applets/maintained/animal-farm' make[4]: Entering directory `/«PKGBUILDDIR»/applets/maintained/animal-farm' /usr/bin/install -c -m 644 animal-farm.desktop '/«PKGBUILDDIR»/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 '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/animal-farm/icons' /usr/bin/install -c -m 644 COPYING '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/animal-farm' /usr/bin/install -c animal-farm.py '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/animal-farm' make[4]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/animal-farm' make[3]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/animal-farm' Making install in maintained/awnterm make[3]: Entering directory `/«PKGBUILDDIR»/applets/maintained/awnterm' make[4]: Entering directory `/«PKGBUILDDIR»/applets/maintained/awnterm' make[5]: Entering directory `/«PKGBUILDDIR»/applets/maintained/awnterm' /bin/bash /«PKGBUILDDIR»/shave/shave-libtool '/bin/bash ../../../libtool' --mode=install /usr/bin/install -c awnterm.la '/«PKGBUILDDIR»/debian/tmp/usr/lib/awn/applets/awnterm' libtool: install: warning: remember to run `libtool --finish /usr/lib/awn/applets/awnterm' 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 '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c -m 644 awn-applet-awnterm.schemas '/«PKGBUILDDIR»/debian/tmp/etc/gconf/schemas' /usr/bin/install -c -m 644 awn-applet-awnterm.schema-ini '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/schemas' make[5]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/awnterm' make[4]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/awnterm' make[3]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/awnterm' Making install in maintained/bandwidth-monitor make[3]: Entering directory `/«PKGBUILDDIR»/applets/maintained/bandwidth-monitor' make[4]: Entering directory `/«PKGBUILDDIR»/applets/maintained/bandwidth-monitor' 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 '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c -m 644 CHANGELOG bwmprefs.py bandwidth-monitor.ui '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/bandwidth-monitor' /usr/bin/install -c awn-bwm.py '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/bandwidth-monitor' /usr/bin/install -c -m 644 images/icon.png '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/bandwidth-monitor/images' /usr/bin/install -c -m 644 awn-applet-bandwidth-monitor.schemas '/«PKGBUILDDIR»/debian/tmp/etc/gconf/schemas' /usr/bin/install -c -m 644 awn-applet-bandwidth-monitor.schema-ini '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/schemas' make[4]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/bandwidth-monitor' make[3]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/bandwidth-monitor' Making install in maintained/battery make[3]: Entering directory `/«PKGBUILDDIR»/applets/maintained/battery' make[4]: Entering directory `/«PKGBUILDDIR»/applets/maintained/battery' 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 '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c -m 644 battery.ui messagehandler.py '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/battery' /usr/bin/install -c battery.py '/«PKGBUILDDIR»/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 '/«PKGBUILDDIR»/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 '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/battery/themes/oxygen' /usr/bin/install -c -m 644 awn-applet-battery.schemas '/«PKGBUILDDIR»/debian/tmp/etc/gconf/schemas' /usr/bin/install -c -m 644 awn-applet-battery.schema-ini '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/schemas' make[4]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/battery' make[3]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/battery' Making install in maintained/cairo-clock make[3]: Entering directory `/«PKGBUILDDIR»/applets/maintained/cairo-clock' make[4]: Entering directory `/«PKGBUILDDIR»/applets/maintained/cairo-clock' 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 '/«PKGBUILDDIR»/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 '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/cairo-clock' /usr/bin/install -c cairo-clock.py '/«PKGBUILDDIR»/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 '/«PKGBUILDDIR»/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 '/«PKGBUILDDIR»/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 '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/cairo-clock/themes/tango' /usr/bin/install -c -m 644 awn-applet-cairo-clock.schemas '/«PKGBUILDDIR»/debian/tmp/etc/gconf/schemas' /usr/bin/install -c -m 644 awn-applet-cairo-clock.schema-ini '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/schemas' make[4]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/cairo-clock' make[3]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/cairo-clock' Making install in maintained/comics make[3]: Entering directory `/«PKGBUILDDIR»/applets/maintained/comics' make[4]: Entering directory `/«PKGBUILDDIR»/applets/maintained/comics' 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 '/«PKGBUILDDIR»/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 '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/comics' /usr/bin/install -c comics.py '/«PKGBUILDDIR»/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 '/«PKGBUILDDIR»/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 '/«PKGBUILDDIR»/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 '/«PKGBUILDDIR»/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 '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/comics/ui' /usr/bin/install -c -m 644 awn-applet-comics.schemas '/«PKGBUILDDIR»/debian/tmp/etc/gconf/schemas' /usr/bin/install -c -m 644 awn-applet-comics.schema-ini '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/schemas' make[4]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/comics' make[3]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/comics' Making install in maintained/cpufreq make[3]: Entering directory `/«PKGBUILDDIR»/applets/maintained/cpufreq' make[4]: Entering directory `/«PKGBUILDDIR»/applets/maintained/cpufreq' 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 '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c -m 644 cpufreq.svg cpufreq.ui '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/cpufreq' /usr/bin/install -c cpufreq.py '/«PKGBUILDDIR»/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 '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/cpufreq/images' /usr/bin/install -c -m 644 themes/moonbeam/index.theme '/«PKGBUILDDIR»/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 '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/cpufreq/themes/moonbeam/scalable' /usr/bin/install -c -m 644 awn-applet-cpufreq.schemas '/«PKGBUILDDIR»/debian/tmp/etc/gconf/schemas' /usr/bin/install -c -m 644 awn-applet-cpufreq.schema-ini '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/schemas' make[4]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/cpufreq' make[3]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/cpufreq' Making install in maintained/dialect make[3]: Entering directory `/«PKGBUILDDIR»/applets/maintained/dialect' make[4]: Entering directory `/«PKGBUILDDIR»/applets/maintained/dialect' 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 '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c -m 644 dialect.ui '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/dialect' /usr/bin/install -c dialect.py '/«PKGBUILDDIR»/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 '/«PKGBUILDDIR»/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 '/«PKGBUILDDIR»/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 '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/dialect/icons' /usr/bin/install -c -m 644 awn-applet-dialect.schemas '/«PKGBUILDDIR»/debian/tmp/etc/gconf/schemas' /usr/bin/install -c -m 644 awn-applet-dialect.schema-ini '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/schemas' make[4]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/dialect' make[3]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/dialect' Making install in maintained/digital-clock make[3]: Entering directory `/«PKGBUILDDIR»/applets/maintained/digital-clock' make[4]: Entering directory `/«PKGBUILDDIR»/applets/maintained/digital-clock' make[5]: Entering directory `/«PKGBUILDDIR»/applets/maintained/digital-clock' /bin/bash /«PKGBUILDDIR»/shave/shave-libtool '/bin/bash ../../../libtool' --mode=install /usr/bin/install -c digital-clock.la '/«PKGBUILDDIR»/debian/tmp/usr/lib/awn/applets/digital-clock' libtool: install: warning: remember to run `libtool --finish /usr/lib/awn/applets/digital-clock' 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 '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c -m 644 dg-prefs.ui '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/digital-clock' /usr/bin/install -c -m 644 awn-applet-digital-clock.schemas '/«PKGBUILDDIR»/debian/tmp/etc/gconf/schemas' /usr/bin/install -c -m 644 awn-applet-digital-clock.svg '/«PKGBUILDDIR»/debian/tmp/usr/share/icons/hicolor/scalable/apps' /usr/bin/install -c -m 644 awn-applet-digital-clock.schema-ini '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/schemas' make[5]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/digital-clock' make[4]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/digital-clock' make[3]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/digital-clock' Making install in maintained/feeds make[3]: Entering directory `/«PKGBUILDDIR»/applets/maintained/feeds' make[4]: Entering directory `/«PKGBUILDDIR»/applets/maintained/feeds' 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 '/«PKGBUILDDIR»/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 '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/feeds' /usr/bin/install -c feeds.py '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/feeds' /usr/bin/install -c -m 644 awn-applet-feeds.schemas '/«PKGBUILDDIR»/debian/tmp/etc/gconf/schemas' /usr/bin/install -c -m 644 ./icons/awn-feeds.svg ./icons/awn-feeds-greader.svg ./icons/twitter-16x16.png '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/feeds/icons' /usr/bin/install -c -m 644 awn-applet-feeds.schema-ini '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/schemas' make[4]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/feeds' make[3]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/feeds' Making install in maintained/file-browser-launcher make[3]: Entering directory `/«PKGBUILDDIR»/applets/maintained/file-browser-launcher' make[4]: Entering directory `/«PKGBUILDDIR»/applets/maintained/file-browser-launcher' 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 '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c -m 644 about.py prefs.py '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/file-browser-launcher' /usr/bin/install -c file-browser-launcher.py '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/file-browser-launcher' /usr/bin/install -c -m 644 awn-applet-file-browser-launcher.schemas '/«PKGBUILDDIR»/debian/tmp/etc/gconf/schemas' /usr/bin/install -c -m 644 awn-applet-file-browser-launcher.schema-ini '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/schemas' make[4]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/file-browser-launcher' make[3]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/file-browser-launcher' Making install in maintained/hardware-sensors make[3]: Entering directory `/«PKGBUILDDIR»/applets/maintained/hardware-sensors' make[4]: Entering directory `/«PKGBUILDDIR»/applets/maintained/hardware-sensors' 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 '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c -m 644 sensoricon.py hardware-sensors.ui '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/hardware-sensors' /usr/bin/install -c hardware-sensors.py '/«PKGBUILDDIR»/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 '/«PKGBUILDDIR»/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 '/«PKGBUILDDIR»/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 '/«PKGBUILDDIR»/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 '/«PKGBUILDDIR»/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 '/«PKGBUILDDIR»/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 '/«PKGBUILDDIR»/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 '/«PKGBUILDDIR»/debian/tmp/etc/gconf/schemas' /usr/bin/install -c -m 644 awn-applet-hardware-sensors.schema-ini '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/schemas' make[4]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/hardware-sensors' make[3]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/hardware-sensors' Making install in maintained/mail make[3]: Entering directory `/«PKGBUILDDIR»/applets/maintained/mail' make[4]: Entering directory `/«PKGBUILDDIR»/applets/maintained/mail' 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 '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c -m 644 mail.ui '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/mail' /usr/bin/install -c mail.py '/«PKGBUILDDIR»/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 '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/mail/icons' /usr/bin/install -c -m 644 themes/GMail/index.theme '/«PKGBUILDDIR»/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 '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/mail/themes/GMail/scalable' /usr/bin/install -c -m 644 themes/Reserved/index.theme '/«PKGBUILDDIR»/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 '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/mail/themes/Reserved/scalable' /usr/bin/install -c -m 644 awn-applet-mail.schemas '/«PKGBUILDDIR»/debian/tmp/etc/gconf/schemas' /usr/bin/install -c -m 644 awn-applet-mail.schema-ini '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/schemas' make[4]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/mail' make[3]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/mail' Making install in maintained/media-control make[3]: Entering directory `/«PKGBUILDDIR»/applets/maintained/media-control' make[4]: Entering directory `/«PKGBUILDDIR»/applets/maintained/media-control' 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 '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c -m 644 media-control.ui COPYING '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/media-control' /usr/bin/install -c media_control.py '/«PKGBUILDDIR»/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 '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/media-control/icons' /usr/bin/install -c -m 644 awn-applet-media-control.schemas '/«PKGBUILDDIR»/debian/tmp/etc/gconf/schemas' /usr/bin/install -c -m 644 awn-applet-media-control.schema-ini '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/schemas' make[4]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/media-control' make[3]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/media-control' Making install in maintained/media-icons make[3]: Entering directory `/«PKGBUILDDIR»/applets/maintained/media-icons' make[4]: Entering directory `/«PKGBUILDDIR»/applets/maintained/media-icons' /usr/bin/install -c -m 644 media-icons.desktop media-icon-next.desktop media-icon-previous.desktop '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c -m 644 COPYING '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/media-icons' /usr/bin/install -c media-icons.py '/«PKGBUILDDIR»/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 '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/media-icons/icons' make[4]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/media-icons' make[3]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/media-icons' Making install in maintained/media-player make[3]: Entering directory `/«PKGBUILDDIR»/applets/maintained/media-player' make[4]: Entering directory `/«PKGBUILDDIR»/applets/maintained/media-player' 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 '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c -m 644 media-player-prefs.ui COPYING '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/media-player' /usr/bin/install -c media_player.py '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/media-player' /usr/bin/install -c -m 644 icons/COPYING icons/README icons/media-player.png '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/media-player/icons' /usr/bin/install -c -m 644 awn-applet-media-player.schemas '/«PKGBUILDDIR»/debian/tmp/etc/gconf/schemas' /usr/bin/install -c -m 644 awn-applet-media-player.schema-ini '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/schemas' make[4]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/media-player' make[3]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/media-player' Making install in maintained/mount make[3]: Entering directory `/«PKGBUILDDIR»/applets/maintained/mount' make[4]: Entering directory `/«PKGBUILDDIR»/applets/maintained/mount' 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 '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c -m 644 mount.ui '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/mount' /usr/bin/install -c mount.py '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/mount' /usr/bin/install -c -m 644 icons/mount.png icons/AUTHORS '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/mount/icons' /usr/bin/install -c -m 644 awn-applet-mount.schemas '/«PKGBUILDDIR»/debian/tmp/etc/gconf/schemas' /usr/bin/install -c -m 644 awn-applet-mount.schema-ini '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/schemas' make[4]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/mount' make[3]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/mount' Making install in maintained/places make[3]: Entering directory `/«PKGBUILDDIR»/applets/maintained/places' make[4]: Entering directory `/«PKGBUILDDIR»/applets/maintained/places' /bin/bash /«PKGBUILDDIR»/shave/shave-libtool '/bin/bash ../../../libtool' --mode=install /usr/bin/install -c places.la '/«PKGBUILDDIR»/debian/tmp/usr/lib/awn/applets/places' libtool: install: warning: remember to run `libtool --finish /usr/lib/awn/applets/places' 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 '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c -m 644 awn-applet-places.schemas '/«PKGBUILDDIR»/debian/tmp/etc/gconf/schemas' /usr/bin/install -c -m 644 awn-applet-places.schema-ini '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/schemas' make[4]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/places' make[3]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/places' Making install in maintained/quit make[3]: Entering directory `/«PKGBUILDDIR»/applets/maintained/quit' make[4]: Entering directory `/«PKGBUILDDIR»/applets/maintained/quit' 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 '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c quit.py '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/quit' /usr/bin/install -c -m 644 awn-applet-quit.schemas '/«PKGBUILDDIR»/debian/tmp/etc/gconf/schemas' /usr/bin/install -c -m 644 awn-applet-quit.schema-ini '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/schemas' make[4]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/quit' make[3]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/quit' Making install in maintained/slickswitcher make[3]: Entering directory `/«PKGBUILDDIR»/applets/maintained/slickswitcher' make[4]: Entering directory `/«PKGBUILDDIR»/applets/maintained/slickswitcher' 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 '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c -m 644 drawing.py prefs.py settings.py switch.py '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/slickswitcher' /usr/bin/install -c slickswitcher.py '/«PKGBUILDDIR»/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 '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/slickswitcher/icons' /usr/bin/install -c -m 644 awn-applet-slickswitcher.schemas '/«PKGBUILDDIR»/debian/tmp/etc/gconf/schemas' /usr/bin/install -c -m 644 awn-applet-slickswitcher.schema-ini '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/schemas' make[4]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/slickswitcher' make[3]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/slickswitcher' Making install in maintained/shiny-switcher make[3]: Entering directory `/«PKGBUILDDIR»/applets/maintained/shiny-switcher' make[4]: Entering directory `/«PKGBUILDDIR»/applets/maintained/shiny-switcher' /bin/bash /«PKGBUILDDIR»/shave/shave-libtool '/bin/bash ../../../libtool' --mode=install /usr/bin/install -c shinyswitcher.la '/«PKGBUILDDIR»/debian/tmp/usr/lib/awn/applets/shinyswitcher' libtool: install: warning: remember to run `libtool --finish /usr/lib/awn/applets/shinyswitcher' 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 '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c -m 644 shiny-prefs.ui shiny-prefs.py '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/shinyswitcher' /usr/bin/install -c -m 644 awn-applet-shinyswitcher.schemas '/«PKGBUILDDIR»/debian/tmp/etc/gconf/schemas' /usr/bin/install -c -m 644 awn-applet-shinyswitcher.schema-ini '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/schemas' make[4]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/shiny-switcher' make[3]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/shiny-switcher' Making install in maintained/sysmon make[3]: Entering directory `/«PKGBUILDDIR»/applets/maintained/sysmon' make[4]: Entering directory `/«PKGBUILDDIR»/applets/maintained/sysmon' /bin/bash /«PKGBUILDDIR»/shave/shave-libtool '/bin/bash ../../../libtool' --mode=install /usr/bin/install -c sysmon.la '/«PKGBUILDDIR»/debian/tmp/usr/lib/awn/applets/sysmon' libtool: install: warning: remember to run `libtool --finish /usr/lib/awn/applets/sysmon' 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/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 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 /usr/bin/install -c -m 644 sysmon.desktop '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c -m 644 awn-applet-sysmon.schemas '/«PKGBUILDDIR»/debian/tmp/etc/gconf/schemas' /usr/bin/install -c -m 644 awn-applet-sysmon.schema-ini '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/schemas' make[4]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/sysmon' make[3]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/sysmon' Making install in maintained/thinkhdaps make[3]: Entering directory `/«PKGBUILDDIR»/applets/maintained/thinkhdaps' make[4]: Entering directory `/«PKGBUILDDIR»/applets/maintained/thinkhdaps' /usr/bin/install -c -m 644 thinkhdaps.desktop '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c thinkhdaps.py '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/thinkhdaps' /usr/bin/install -c -m 644 icons/thinkhdaps-running.svg icons/thinkhdaps-paused.svg '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/thinkhdaps/icons' /usr/bin/install -c -m 644 images/thinkhdaps-logo.svg '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/thinkhdaps/images' make[4]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/thinkhdaps' make[3]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/thinkhdaps' Making install in maintained/to-do make[3]: Entering directory `/«PKGBUILDDIR»/applets/maintained/to-do' make[4]: Entering directory `/«PKGBUILDDIR»/applets/maintained/to-do' 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 '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c -m 644 to-do.py settings.py icon.py prefs.py '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/to-do' /usr/bin/install -c to-do.py '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/to-do' /usr/bin/install -c -m 644 awn-applet-to-do.schemas '/«PKGBUILDDIR»/debian/tmp/etc/gconf/schemas' /usr/bin/install -c -m 644 awn-applet-to-do.schema-ini '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/schemas' make[4]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/to-do' make[3]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/to-do' Making install in maintained/tomboy-applet make[3]: Entering directory `/«PKGBUILDDIR»/applets/maintained/tomboy-applet' make[4]: Entering directory `/«PKGBUILDDIR»/applets/maintained/tomboy-applet' /usr/bin/install -c -m 644 tomboy-applet.desktop '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c tomboy-applet.py '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/tomboy-applet' make[4]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/tomboy-applet' make[3]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/tomboy-applet' Making install in maintained/volume-control make[3]: Entering directory `/«PKGBUILDDIR»/applets/maintained/volume-control' make[4]: Entering directory `/«PKGBUILDDIR»/applets/maintained/volume-control' 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 '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c -m 644 volume-control.ui volume-control.svg '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/volume-control' /usr/bin/install -c volume-control.py '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/volume-control' /usr/bin/install -c -m 644 themes/Black/index.theme '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/volume-control/themes/Black' /usr/bin/install -c -m 644 themes/Minimal/index.theme '/«PKGBUILDDIR»/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 '/«PKGBUILDDIR»/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 '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/volume-control/themes/Minimal/scalable' /usr/bin/install -c -m 644 awn-applet-volume-control.schemas '/«PKGBUILDDIR»/debian/tmp/etc/gconf/schemas' /usr/bin/install -c -m 644 awn-applet-volume-control.schema-ini '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/schemas' make[4]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/volume-control' make[3]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/volume-control' Making install in maintained/weather make[3]: Entering directory `/«PKGBUILDDIR»/applets/maintained/weather' make[4]: Entering directory `/«PKGBUILDDIR»/applets/maintained/weather' 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 '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c -m 644 forecast.py weather.ui '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/weather' /usr/bin/install -c weather.py '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/weather' /usr/bin/install -c -m 644 icons/twc-logo.png '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/weather/icons' /usr/bin/install -c -m 644 themes/moonbeam/index.theme '/«PKGBUILDDIR»/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 '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/weather/themes/moonbeam/scalable' /usr/bin/install -c -m 644 awn-applet-weather.schemas '/«PKGBUILDDIR»/debian/tmp/etc/gconf/schemas' /usr/bin/install -c -m 644 awn-applet-weather.schema-ini '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/schemas' make[4]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/weather' make[3]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/weather' Making install in maintained/garbage make[3]: Entering directory `/«PKGBUILDDIR»/applets/maintained/garbage' make[4]: Entering directory `/«PKGBUILDDIR»/applets/maintained/garbage' make[5]: Entering directory `/«PKGBUILDDIR»/applets/maintained/garbage' /bin/bash /«PKGBUILDDIR»/shave/shave-libtool '/bin/bash ../../../libtool' --mode=install /usr/bin/install -c garbage.la '/«PKGBUILDDIR»/debian/tmp/usr/lib/awn/applets/garbage' libtool: install: warning: remember to run `libtool --finish /usr/lib/awn/applets/garbage' 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 '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c -m 644 awn-applet-garbage.schemas '/«PKGBUILDDIR»/debian/tmp/etc/gconf/schemas' /usr/bin/install -c -m 644 awn-applet-garbage.schema-ini '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/schemas' make[5]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/garbage' make[4]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/garbage' make[3]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/garbage' Making install in maintained/notification-area make[3]: Entering directory `/«PKGBUILDDIR»/applets/maintained/notification-area' make[4]: Entering directory `/«PKGBUILDDIR»/applets/maintained/notification-area' make[5]: Entering directory `/«PKGBUILDDIR»/applets/maintained/notification-area' /bin/bash /«PKGBUILDDIR»/shave/shave-libtool '/bin/bash ../../../libtool' --mode=install /usr/bin/install -c notification-area.la '/«PKGBUILDDIR»/debian/tmp/usr/lib/awn/applets/notification-area' libtool: install: warning: remember to run `libtool --finish /usr/lib/awn/applets/notification-area' 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 '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c -m 644 na-prefs.ui '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/notification-area' /usr/bin/install -c -m 644 awn-applet-notification-area.schemas '/«PKGBUILDDIR»/debian/tmp/etc/gconf/schemas' /usr/bin/install -c -m 644 notification-area.svg '/«PKGBUILDDIR»/debian/tmp/usr/share/icons/hicolor/scalable/apps' /usr/bin/install -c -m 644 awn-applet-notification-area.schema-ini '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/schemas' make[5]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/notification-area' make[4]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/notification-area' make[3]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/notification-area' Making install in maintained/showdesktop make[3]: Entering directory `/«PKGBUILDDIR»/applets/maintained/showdesktop' make[4]: Entering directory `/«PKGBUILDDIR»/applets/maintained/showdesktop' make[5]: Entering directory `/«PKGBUILDDIR»/applets/maintained/showdesktop' /bin/bash /«PKGBUILDDIR»/shave/shave-libtool '/bin/bash ../../../libtool' --mode=install /usr/bin/install -c showdesktop.la '/«PKGBUILDDIR»/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 '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets' make[5]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/showdesktop' make[4]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/showdesktop' make[3]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/showdesktop' Making install in unmaintained/awnsystemmonitor make[3]: Entering directory `/«PKGBUILDDIR»/applets/unmaintained/awnsystemmonitor' make[4]: Entering directory `/«PKGBUILDDIR»/applets/unmaintained/awnsystemmonitor' /bin/bash /«PKGBUILDDIR»/shave/shave-libtool '/bin/bash ../../../libtool' --mode=install /usr/bin/install -c awnsystemmonitor.la '/«PKGBUILDDIR»/debian/tmp/usr/lib/awn/applets/awnsystemmonitor' libtool: install: warning: remember to run `libtool --finish /usr/lib/awn/applets/awnsystemmonitor' 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 `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 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 /usr/bin/install -c -m 644 awnsystemmonitor.desktop '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c -m 644 awnsystemmonitor.schemas '/«PKGBUILDDIR»/debian/tmp/etc/gconf/schemas' make[4]: Leaving directory `/«PKGBUILDDIR»/applets/unmaintained/awnsystemmonitor' make[3]: Leaving directory `/«PKGBUILDDIR»/applets/unmaintained/awnsystemmonitor' Making install in maintained/calendar make[3]: Entering directory `/«PKGBUILDDIR»/applets/maintained/calendar' make[4]: Entering directory `/«PKGBUILDDIR»/applets/maintained/calendar' 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 '/«PKGBUILDDIR»/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 '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/calendar' /usr/bin/install -c clockcal.py '/«PKGBUILDDIR»/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 '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/calendar/images' /usr/bin/install -c -m 644 awn-applet-calendar.schemas '/«PKGBUILDDIR»/debian/tmp/etc/gconf/schemas' /usr/bin/install -c -m 644 awn-applet-calendar.schema-ini '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/schemas' make[4]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/calendar' make[3]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/calendar' Making install in maintained/notification-daemon make[3]: Entering directory `/«PKGBUILDDIR»/applets/maintained/notification-daemon' make[4]: Entering directory `/«PKGBUILDDIR»/applets/maintained/notification-daemon' make[5]: Entering directory `/«PKGBUILDDIR»/applets/maintained/notification-daemon' /bin/bash /«PKGBUILDDIR»/shave/shave-libtool '/bin/bash ../../../libtool' --mode=install /usr/bin/install -c notification-daemon.la '/«PKGBUILDDIR»/debian/tmp/usr/lib/awn/applets/notification-daemon' libtool: install: warning: remember to run `libtool --finish /usr/lib/awn/applets/notification-daemon' 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 '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c -m 644 awn-applet-notification-daemon.schemas '/«PKGBUILDDIR»/debian/tmp/etc/gconf/schemas' /usr/bin/install -c -m 644 awn-applet-notification-daemon.schema-ini '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/schemas' make[5]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/notification-daemon' make[4]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/notification-daemon' make[3]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/notification-daemon' Making install in maintained/cairo-menu make[3]: Entering directory `/«PKGBUILDDIR»/applets/maintained/cairo-menu' make[4]: Entering directory `/«PKGBUILDDIR»/applets/maintained/cairo-menu' /bin/bash /«PKGBUILDDIR»/shave/shave-libtool '/bin/bash ../../../libtool' --mode=install /usr/bin/install -c cairo-menu.la '/«PKGBUILDDIR»/debian/tmp/usr/lib/awn/applets/cairo-menu' libtool: install: warning: remember to run `libtool --finish /usr/lib/awn/applets/cairo-menu' 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 '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c -m 644 awn-applet-cairo-menu.schemas '/«PKGBUILDDIR»/debian/tmp/etc/gconf/schemas' /bin/bash /«PKGBUILDDIR»/shave/shave-libtool '/bin/bash ../../../libtool' --mode=install /usr/bin/install -c gnome-menu-builder.la '/«PKGBUILDDIR»/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 '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/schemas' make[4]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/cairo-menu' make[3]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/cairo-menu' Making install in unmaintained/main-menu make[3]: Entering directory `/«PKGBUILDDIR»/applets/unmaintained/main-menu' make[4]: Entering directory `/«PKGBUILDDIR»/applets/unmaintained/main-menu' /bin/bash /«PKGBUILDDIR»/shave/shave-libtool '/bin/bash ../../../libtool' --mode=install /usr/bin/install -c main-menu.la '/«PKGBUILDDIR»/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 '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets' make[4]: Leaving directory `/«PKGBUILDDIR»/applets/unmaintained/main-menu' make[3]: Leaving directory `/«PKGBUILDDIR»/applets/unmaintained/main-menu' Making install in unmaintained/MiMenu make[3]: Entering directory `/«PKGBUILDDIR»/applets/unmaintained/MiMenu' make[4]: Entering directory `/«PKGBUILDDIR»/applets/unmaintained/MiMenu' /usr/bin/install -c -m 644 mimenu.desktop '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c -m 644 COPYING keyboard.py menus.py pathfinder.py '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/mimenu' /usr/bin/install -c mimenu.py '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/mimenu' /usr/bin/install -c -m 644 icons/icon.svg '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/mimenu/icons' make[4]: Leaving directory `/«PKGBUILDDIR»/applets/unmaintained/MiMenu' make[3]: Leaving directory `/«PKGBUILDDIR»/applets/unmaintained/MiMenu' Making install in unmaintained/pandora make[3]: Entering directory `/«PKGBUILDDIR»/applets/unmaintained/pandora' make[4]: Entering directory `/«PKGBUILDDIR»/applets/unmaintained/pandora' 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 '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c pandora.py '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/pandora' /usr/bin/install -c -m 644 icons/pandora.png '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/pandora/icons' /usr/bin/install -c -m 644 awn-applet-pandora.schemas '/«PKGBUILDDIR»/debian/tmp/etc/gconf/schemas' /usr/bin/install -c -m 644 awn-applet-pandora.schema-ini '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/schemas' make[4]: Leaving directory `/«PKGBUILDDIR»/applets/unmaintained/pandora' make[3]: Leaving directory `/«PKGBUILDDIR»/applets/unmaintained/pandora' Making install in unmaintained/stacks make[3]: Entering directory `/«PKGBUILDDIR»/applets/unmaintained/stacks' make[4]: Entering directory `/«PKGBUILDDIR»/applets/unmaintained/stacks' 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 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 /usr/bin/install -c -m 644 stacks.desktop '/«PKGBUILDDIR»/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 '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/stacks' /usr/bin/install -c stacks_applet.py '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/stacks' /usr/bin/install -c -m 644 icons/stacks-drop.svg icons/stacks-full.svg '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/stacks/icons' /usr/bin/install -c -m 644 awn-applet-stacks.schemas '/«PKGBUILDDIR»/debian/tmp/etc/gconf/schemas' /usr/bin/install -c -m 644 awn-applet-stacks.schema-ini '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/schemas' make[4]: Leaving directory `/«PKGBUILDDIR»/applets/unmaintained/stacks' make[3]: Leaving directory `/«PKGBUILDDIR»/applets/unmaintained/stacks' Making install in maintained/yama make[3]: Entering directory `/«PKGBUILDDIR»/applets/maintained/yama' make[4]: Entering directory `/«PKGBUILDDIR»/applets/maintained/yama' /usr/bin/install -c -m 644 yama.desktop '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c yama.py '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/yama' make[4]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/yama' make[3]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/yama' Making install in maintained/webapplet make[3]: Entering directory `/«PKGBUILDDIR»/applets/maintained/webapplet' make[4]: Entering directory `/«PKGBUILDDIR»/applets/maintained/webapplet' /bin/bash /«PKGBUILDDIR»/shave/shave-libtool '/bin/bash ../../../libtool' --mode=install /usr/bin/install -c webapplet.la '/«PKGBUILDDIR»/debian/tmp/usr/lib/awn/applets/webapplet' libtool: install: warning: remember to run `libtool --finish /usr/lib/awn/applets/webapplet' 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 '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets' /usr/bin/install -c -m 644 webapplet-websites.ini '/«PKGBUILDDIR»/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 '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/webapplet/icons' /usr/bin/install -c -m 644 awn-applet-webapplet.schemas '/«PKGBUILDDIR»/debian/tmp/etc/gconf/schemas' /usr/bin/install -c -m 644 awn-applet-webapplet.schema-ini '/«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/schemas' make[4]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/webapplet' make[3]: Leaving directory `/«PKGBUILDDIR»/applets/maintained/webapplet' make[3]: Entering directory `/«PKGBUILDDIR»/applets' make[3]: Leaving directory `/«PKGBUILDDIR»/applets' make[2]: Leaving directory `/«PKGBUILDDIR»/applets' Making install in shared/python make[2]: Entering directory `/«PKGBUILDDIR»/shared/python' make[3]: Entering directory `/«PKGBUILDDIR»/shared/python' /usr/bin/install -c -m 644 __init__.py awnlib.py awnmediaplayers.py configbinder.py threadqueue.py '/«PKGBUILDDIR»/debian/tmp/usr/lib/python2.7/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 `/«PKGBUILDDIR»/shared/python' make[2]: Leaving directory `/«PKGBUILDDIR»/shared/python' Making install in shared/vala make[2]: Entering directory `/«PKGBUILDDIR»/shared/vala' make[2]: Leaving directory `/«PKGBUILDDIR»/shared/vala' Making install in po make[2]: Entering directory `/«PKGBUILDDIR»/po' installing af.gmo as /«PKGBUILDDIR»/debian/tmp/usr/share/locale/af/LC_MESSAGES/awn-extras.mo installing ar.gmo as /«PKGBUILDDIR»/debian/tmp/usr/share/locale/ar/LC_MESSAGES/awn-extras.mo installing ast.gmo as /«PKGBUILDDIR»/debian/tmp/usr/share/locale/ast/LC_MESSAGES/awn-extras.mo installing bg.gmo as /«PKGBUILDDIR»/debian/tmp/usr/share/locale/bg/LC_MESSAGES/awn-extras.mo installing ca.gmo as /«PKGBUILDDIR»/debian/tmp/usr/share/locale/ca/LC_MESSAGES/awn-extras.mo installing cs.gmo as /«PKGBUILDDIR»/debian/tmp/usr/share/locale/cs/LC_MESSAGES/awn-extras.mo installing csb.gmo as /«PKGBUILDDIR»/debian/tmp/usr/share/locale/csb/LC_MESSAGES/awn-extras.mo installing da.gmo as /«PKGBUILDDIR»/debian/tmp/usr/share/locale/da/LC_MESSAGES/awn-extras.mo installing de.gmo as /«PKGBUILDDIR»/debian/tmp/usr/share/locale/de/LC_MESSAGES/awn-extras.mo installing en_CA.gmo as /«PKGBUILDDIR»/debian/tmp/usr/share/locale/en_CA/LC_MESSAGES/awn-extras.mo installing en_GB.gmo as /«PKGBUILDDIR»/debian/tmp/usr/share/locale/en_GB/LC_MESSAGES/awn-extras.mo installing en_US@piglatin.gmo as /«PKGBUILDDIR»/debian/tmp/usr/share/locale/en_US@piglatin/LC_MESSAGES/awn-extras.mo installing es.gmo as /«PKGBUILDDIR»/debian/tmp/usr/share/locale/es/LC_MESSAGES/awn-extras.mo installing eu.gmo as /«PKGBUILDDIR»/debian/tmp/usr/share/locale/eu/LC_MESSAGES/awn-extras.mo installing fi.gmo as /«PKGBUILDDIR»/debian/tmp/usr/share/locale/fi/LC_MESSAGES/awn-extras.mo installing fr.gmo as /«PKGBUILDDIR»/debian/tmp/usr/share/locale/fr/LC_MESSAGES/awn-extras.mo installing he.gmo as /«PKGBUILDDIR»/debian/tmp/usr/share/locale/he/LC_MESSAGES/awn-extras.mo installing hu.gmo as /«PKGBUILDDIR»/debian/tmp/usr/share/locale/hu/LC_MESSAGES/awn-extras.mo installing id.gmo as /«PKGBUILDDIR»/debian/tmp/usr/share/locale/id/LC_MESSAGES/awn-extras.mo installing it.gmo as /«PKGBUILDDIR»/debian/tmp/usr/share/locale/it/LC_MESSAGES/awn-extras.mo installing ja.gmo as /«PKGBUILDDIR»/debian/tmp/usr/share/locale/ja/LC_MESSAGES/awn-extras.mo installing ko.gmo as /«PKGBUILDDIR»/debian/tmp/usr/share/locale/ko/LC_MESSAGES/awn-extras.mo installing lt.gmo as /«PKGBUILDDIR»/debian/tmp/usr/share/locale/lt/LC_MESSAGES/awn-extras.mo installing ms.gmo as /«PKGBUILDDIR»/debian/tmp/usr/share/locale/ms/LC_MESSAGES/awn-extras.mo installing nb.gmo as /«PKGBUILDDIR»/debian/tmp/usr/share/locale/nb/LC_MESSAGES/awn-extras.mo installing nl.gmo as /«PKGBUILDDIR»/debian/tmp/usr/share/locale/nl/LC_MESSAGES/awn-extras.mo installing nn.gmo as /«PKGBUILDDIR»/debian/tmp/usr/share/locale/nn/LC_MESSAGES/awn-extras.mo installing pl.gmo as /«PKGBUILDDIR»/debian/tmp/usr/share/locale/pl/LC_MESSAGES/awn-extras.mo installing pt.gmo as /«PKGBUILDDIR»/debian/tmp/usr/share/locale/pt/LC_MESSAGES/awn-extras.mo installing pt_BR.gmo as /«PKGBUILDDIR»/debian/tmp/usr/share/locale/pt_BR/LC_MESSAGES/awn-extras.mo installing ru.gmo as /«PKGBUILDDIR»/debian/tmp/usr/share/locale/ru/LC_MESSAGES/awn-extras.mo installing sk.gmo as /«PKGBUILDDIR»/debian/tmp/usr/share/locale/sk/LC_MESSAGES/awn-extras.mo installing sv.gmo as /«PKGBUILDDIR»/debian/tmp/usr/share/locale/sv/LC_MESSAGES/awn-extras.mo installing sv_SE.gmo as /«PKGBUILDDIR»/debian/tmp/usr/share/locale/sv_SE/LC_MESSAGES/awn-extras.mo installing th.gmo as /«PKGBUILDDIR»/debian/tmp/usr/share/locale/th/LC_MESSAGES/awn-extras.mo installing tr.gmo as /«PKGBUILDDIR»/debian/tmp/usr/share/locale/tr/LC_MESSAGES/awn-extras.mo installing uk.gmo as /«PKGBUILDDIR»/debian/tmp/usr/share/locale/uk/LC_MESSAGES/awn-extras.mo installing vi.gmo as /«PKGBUILDDIR»/debian/tmp/usr/share/locale/vi/LC_MESSAGES/awn-extras.mo installing zh_CN.gmo as /«PKGBUILDDIR»/debian/tmp/usr/share/locale/zh_CN/LC_MESSAGES/awn-extras.mo installing zh_TW.gmo as /«PKGBUILDDIR»/debian/tmp/usr/share/locale/zh_TW/LC_MESSAGES/awn-extras.mo make[2]: Leaving directory `/«PKGBUILDDIR»/po' make[2]: Entering directory `/«PKGBUILDDIR»' make[3]: Entering directory `/«PKGBUILDDIR»' make[4]: Entering directory `/«PKGBUILDDIR»' *** Icon cache not updated. After install, run this: *** gtk-update-icon-cache -f -t /usr/share/icons/hicolor make[4]: Leaving directory `/«PKGBUILDDIR»' make[3]: Leaving directory `/«PKGBUILDDIR»' make[2]: Leaving directory `/«PKGBUILDDIR»' make[1]: Leaving directory `/«PKGBUILDDIR»' debian/rules override_dh_install make[1]: Entering directory `/«PKGBUILDDIR»' #Remove CHANGELOG,LGPL, AUTHORS, README, COPYING, .la, .a, pyo and pyc files. find /«PKGBUILDDIR»/debian/tmp/usr/lib/ -name *.a |xargs rm find /«PKGBUILDDIR»/debian/tmp/usr/lib -name *.la |xargs rm find /«PKGBUILDDIR»/debian/tmp/usr/lib -name *.pyc |xargs rm find /«PKGBUILDDIR»/debian/tmp/usr/lib -name *.pyo |xargs rm find /«PKGBUILDDIR»/debian/tmp/usr -name COPYING |xargs rm find /«PKGBUILDDIR»/debian/tmp/usr -name README |xargs rm find /«PKGBUILDDIR»/debian/tmp/usr -name AUTHORS |xargs rm find /«PKGBUILDDIR»/debian/tmp/usr -name LGPL |xargs rm find /«PKGBUILDDIR»/debian/tmp/usr -name CHANGELOG |xargs rm #Disable applets set -e; for applet in dropper mimenu vala-test python-test wobblyzini; do \ rm -f /«PKGBUILDDIR»/debian/tmp/usr/lib/awn/applets/${applet}/*.so \ rm -f /«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/${applet}/*.py; \ rm -f /«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/${applet}/icons/*.svg; \ rm -f /«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/${applet}/icons/*.png; \ rm -f /«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/${applet}/*.ui; \ rm -f /«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/${applet}.desktop; \ done #Make script executable chmod +x /«PKGBUILDDIR»/debian/tmp/usr/share/avant-window-navigator/applets/comics/comics.sh dh_install --fail-missing make[1]: Leaving directory `/«PKGBUILDDIR»' 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_installinit -a 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_installgsettings -a dh_bugfiles -a dh_ucf -a dh_lintian -a dh_gconf -a dh_icons -a dh_perl -a dh_python2 -a dh_usrlocal -a dh_link -a dh_compress -a dh_fixperms -a debian/rules override_dh_strip make[1]: Entering directory `/«PKGBUILDDIR»' dh_strip --dbg-package=awn-applets-c-dbg make[1]: Leaving directory `/«PKGBUILDDIR»' debian/rules override_dh_makeshlibs make[1]: Entering directory `/«PKGBUILDDIR»' dh_makeshlibs -pawn-applets-c-core -a -n --exclude=* dh_makeshlibs -pawn-applets-c-extras -a -n --exclude=* make[1]: Leaving directory `/«PKGBUILDDIR»' dh_shlibdeps -a dpkg-shlibdeps: warning: debian/awn-applets-c-core/usr/lib/awn/applets/shinyswitcher/shinyswitcher.so contains an unresolvable reference to symbol XFixesTranslateRegion: it's probably a plugin. dpkg-shlibdeps: warning: 3 other similar warnings have been skipped (use -v to see them all). dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/awn-applets-c-core/usr/lib/awn/applets/shinyswitcher/shinyswitcher.so debian/awn-applets-c-core/usr/lib/awn/applets/cairo-menu/cairo-menu.so debian/awn-applets-c-core/usr/lib/awn/applets/cairo-menu/gnome-menu-builder.so debian/awn-applets-c-core/usr/lib/awn/applets/awnterm/awnterm.so debian/awn-applets-c-core/usr/lib/awn/applets/notification-area/notification-area.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/awnsystemmonitor/awnsystemmonitor.so debian/awn-applets-c-core/usr/lib/awn/applets/notification-daemon/notification-daemon.so were not linked against libfontconfig.so.1 (they use none of the library's symbols). dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/awn-applets-c-core/usr/lib/awn/applets/shinyswitcher/shinyswitcher.so debian/awn-applets-c-core/usr/lib/awn/applets/cairo-menu/cairo-menu.so debian/awn-applets-c-core/usr/lib/awn/applets/cairo-menu/gnome-menu-builder.so debian/awn-applets-c-core/usr/lib/awn/applets/awnterm/awnterm.so debian/awn-applets-c-core/usr/lib/awn/applets/notification-area/notification-area.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/awnsystemmonitor/awnsystemmonitor.so debian/awn-applets-c-core/usr/lib/awn/applets/notification-daemon/notification-daemon.so were not linked against libfreetype.so.6 (they use none of the library's symbols). dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/awn-applets-c-core/usr/lib/awn/applets/shinyswitcher/shinyswitcher.so debian/awn-applets-c-core/usr/lib/awn/applets/cairo-menu/cairo-menu.so debian/awn-applets-c-core/usr/lib/awn/applets/cairo-menu/gnome-menu-builder.so debian/awn-applets-c-core/usr/lib/awn/applets/awnterm/awnterm.so debian/awn-applets-c-core/usr/lib/awn/applets/notification-area/notification-area.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/awnsystemmonitor/awnsystemmonitor.so debian/awn-applets-c-core/usr/lib/awn/applets/notification-daemon/notification-daemon.so were not linked against librt.so.1 (they use none of the library's symbols). dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/awn-applets-c-core/usr/lib/awn/applets/shinyswitcher/shinyswitcher.so debian/awn-applets-c-core/usr/lib/awn/applets/cairo-menu/cairo-menu.so debian/awn-applets-c-core/usr/lib/awn/applets/cairo-menu/gnome-menu-builder.so debian/awn-applets-c-core/usr/lib/awn/applets/awnterm/awnterm.so debian/awn-applets-c-core/usr/lib/awn/applets/notification-area/notification-area.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/awnsystemmonitor/awnsystemmonitor.so debian/awn-applets-c-core/usr/lib/awn/applets/notification-daemon/notification-daemon.so were not linked against libgthread-2.0.so.0 (they use none of the library's symbols). dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/awn-applets-c-core/usr/lib/awn/applets/shinyswitcher/shinyswitcher.so debian/awn-applets-c-core/usr/lib/awn/applets/cairo-menu/cairo-menu.so debian/awn-applets-c-core/usr/lib/awn/applets/cairo-menu/gnome-menu-builder.so debian/awn-applets-c-core/usr/lib/awn/applets/awnterm/awnterm.so debian/awn-applets-c-core/usr/lib/awn/applets/notification-area/notification-area.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/awnsystemmonitor/awnsystemmonitor.so debian/awn-applets-c-core/usr/lib/awn/applets/notification-daemon/notification-daemon.so were not linked against libpangoft2-1.0.so.0 (they use none of the library's symbols). dpkg-shlibdeps: warning: package could avoid a useless dependency if 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/places/places.so debian/awn-applets-c-extras/usr/lib/awn/applets/webapplet/webapplet.so debian/awn-applets-c-extras/usr/lib/awn/applets/sysmon/sysmon.so were not linked against libdbus-1.so.3 (they use none of the library's symbols). dpkg-shlibdeps: warning: package could avoid a useless dependency if 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/places/places.so debian/awn-applets-c-extras/usr/lib/awn/applets/webapplet/webapplet.so debian/awn-applets-c-extras/usr/lib/awn/applets/sysmon/sysmon.so were not linked against libfontconfig.so.1 (they use none of the library's symbols). dpkg-shlibdeps: warning: package could avoid a useless dependency if 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/places/places.so debian/awn-applets-c-extras/usr/lib/awn/applets/webapplet/webapplet.so debian/awn-applets-c-extras/usr/lib/awn/applets/sysmon/sysmon.so were not linked against libatk-1.0.so.0 (they use none of the library's symbols). dpkg-shlibdeps: warning: package could avoid a useless dependency if 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/places/places.so debian/awn-applets-c-extras/usr/lib/awn/applets/webapplet/webapplet.so debian/awn-applets-c-extras/usr/lib/awn/applets/sysmon/sysmon.so were not linked against libpangocairo-1.0.so.0 (they use none of the library's symbols). dpkg-shlibdeps: warning: package could avoid a useless dependency if 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/places/places.so debian/awn-applets-c-extras/usr/lib/awn/applets/webapplet/webapplet.so debian/awn-applets-c-extras/usr/lib/awn/applets/sysmon/sysmon.so were not linked against libfreetype.so.6 (they use none of the library's symbols). dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/awn-applets-c-extras/usr/lib/awn/applets/webapplet/webapplet.so was not linked against libjavascriptcoregtk-1.0.so.0 (it uses none of the library's symbols). dpkg-shlibdeps: warning: package could avoid a useless dependency if 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/places/places.so debian/awn-applets-c-extras/usr/lib/awn/applets/webapplet/webapplet.so debian/awn-applets-c-extras/usr/lib/awn/applets/sysmon/sysmon.so were not linked against librt.so.1 (they use none of the library's symbols). dpkg-shlibdeps: warning: package could avoid a useless dependency if 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/places/places.so debian/awn-applets-c-extras/usr/lib/awn/applets/webapplet/webapplet.so debian/awn-applets-c-extras/usr/lib/awn/applets/sysmon/sysmon.so were not linked against libpthread.so.0 (they use none of the library's symbols). dpkg-shlibdeps: warning: package could avoid a useless dependency if 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/places/places.so debian/awn-applets-c-extras/usr/lib/awn/applets/webapplet/webapplet.so debian/awn-applets-c-extras/usr/lib/awn/applets/sysmon/sysmon.so were not linked against libgio-2.0.so.0 (they use none of the library's symbols). dpkg-shlibdeps: warning: package could avoid a useless dependency if 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/places/places.so debian/awn-applets-c-extras/usr/lib/awn/applets/webapplet/webapplet.so debian/awn-applets-c-extras/usr/lib/awn/applets/sysmon/sysmon.so were not linked against libgmodule-2.0.so.0 (they use none of the library's symbols). dpkg-shlibdeps: warning: package could avoid a useless dependency if 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/places/places.so debian/awn-applets-c-extras/usr/lib/awn/applets/webapplet/webapplet.so debian/awn-applets-c-extras/usr/lib/awn/applets/sysmon/sysmon.so were not linked against libpango-1.0.so.0 (they use none of the library's symbols). dpkg-shlibdeps: warning: package could avoid a useless dependency if 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/places/places.so debian/awn-applets-c-extras/usr/lib/awn/applets/webapplet/webapplet.so debian/awn-applets-c-extras/usr/lib/awn/applets/sysmon/sysmon.so were not linked against libdbus-glib-1.so.2 (they use none of the library's symbols). dpkg-shlibdeps: warning: package could avoid a useless dependency if 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/places/places.so debian/awn-applets-c-extras/usr/lib/awn/applets/webapplet/webapplet.so debian/awn-applets-c-extras/usr/lib/awn/applets/sysmon/sysmon.so were not linked against libgthread-2.0.so.0 (they use none of the library's symbols). dpkg-shlibdeps: warning: package could avoid a useless dependency if 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/places/places.so debian/awn-applets-c-extras/usr/lib/awn/applets/webapplet/webapplet.so debian/awn-applets-c-extras/usr/lib/awn/applets/sysmon/sysmon.so were not linked against libpangoft2-1.0.so.0 (they use none of the library's symbols). dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/awn-applets-c-extras/usr/lib/awn/applets/webapplet/webapplet.so was not linked against libsoup-2.4.so.1 (it uses none of the library's symbols). dh_installdeb -a dh_gencontrol -a dpkg-gencontrol: warning: Depends field of package python-awn-extras: unknown substitution variable ${shlibs:Depends} dpkg-gencontrol: warning: package python-awn-extras: unused substitution variable ${python:Versions} dpkg-gencontrol: warning: Depends field of package awn-applets-c-dbg: unknown substitution variable ${shlibs:Depends} dpkg-gencontrol: warning: Depends field of package awn-applets-common: unknown substitution variable ${shlibs:Depends} dh_md5sums -a dh_builddeb -a dpkg-deb: building package `awn-applets-c-core' in `../awn-applets-c-core_0.4.0-5_armhf.deb'. dpkg-deb: building package `awn-applets-c-extras' in `../awn-applets-c-extras_0.4.0-5_armhf.deb'. dpkg-deb: building package `python-awn-extras' in `../python-awn-extras_0.4.0-5_armhf.deb'. dpkg-deb: building package `awn-applets-c-dbg' in `../awn-applets-c-dbg_0.4.0-5_armhf.deb'. dpkg-deb: building package `awn-applets-common' in `../awn-applets-common_0.4.0-5_armhf.deb'. dpkg-genchanges -B -mbuildd >../awn-extras-applets_0.4.0-5_armhf.changes dpkg-genchanges: arch-specific upload - not including arch-independent packages dpkg-genchanges: binary-only upload - not including any source code dpkg-source --after-build awn-extras-applets-0.4.0 dpkg-buildpackage: binary only upload (no source included) ──────────────────────────────────────────────────────────────────────────────── Build finished at 20120624-0757 Finished ──────── I: Built successfully ┌──────────────────────────────────────────────────────────────────────────────┐ │ Changes │ └──────────────────────────────────────────────────────────────────────────────┘ awn-extras-applets_0.4.0-5_armhf.changes: ───────────────────────────────────────── Format: 1.8 Date: Sun, 01 Apr 2012 19:32:37 +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 awn-applets-common Architecture: armhf Version: 0.4.0-5 Distribution: testing Urgency: low Maintainer: buildd Changed-By: Julien Lavergne Description: awn-applets-c-core - Collection of applets for Awn, written in C or Vala awn-applets-c-dbg - Collection of applets for avant-window-navigator - debug symbols awn-applets-c-extras - Collection of extras applets for Awn, written in C or Vala awn-applets-common - Collection of applets for avant-window-navigator - common files awn-applets-python-core - Collection of applets for Awn, written in python awn-applets-python-extras - Collection of extras applets for Awn, written in python python-awn-extras - Python bindings for avant-window-navigator's applets Closes: 597678 665509 Changes: awn-extras-applets (0.4.0-5) unstable; urgency=low . * debian/patches: - 04-glib-single-include.patch: Include only glib.h, to fix FTBFS with glib 2.32. Thanks Michael Biebl for the patch. (Closes: #665509) * debian/control: - Provide notification-daemon for notification-daemon applet. (Closes: #597678) - Update Standards-Version to 3.9.3, no change needed. - Update descriptions. Checksums-Sha1: 40c4d93ee982fa693cbed88b302616c1386e52b0 204790 awn-applets-c-core_0.4.0-5_armhf.deb 05481d26ade17c33b789b1d9402e33dc5aef7cd4 113408 awn-applets-c-extras_0.4.0-5_armhf.deb 53d5b2f3f46e8e0d7d22773b367bc9d030c05208 37314 python-awn-extras_0.4.0-5_armhf.deb cc5decea537eb1643ef6ab6cc2ec8e8098ff88ae 795920 awn-applets-c-dbg_0.4.0-5_armhf.deb 697e842e97f51e352cabe64b6def4a133ca8510e 118220 awn-applets-common_0.4.0-5_armhf.deb Checksums-Sha256: 9f9ee3df23e62548e8d3f71a521cbc37de98e14ab7dcb2eff219ff03bd09f101 204790 awn-applets-c-core_0.4.0-5_armhf.deb c50bb74e8590558d3b5977d24fe58437b4d2d02e83162545742b2cdc1196ec63 113408 awn-applets-c-extras_0.4.0-5_armhf.deb 3fe220ba998ed65c6dae04b624cbcee67b7250aeab6ea8ae19b9d0679d83664f 37314 python-awn-extras_0.4.0-5_armhf.deb d403ffd7890b5779b27087154076ff63596d53aee6998de567f1aba9f1e7533a 795920 awn-applets-c-dbg_0.4.0-5_armhf.deb 6106b6fd9d3cb2e8a1e16a4d73fd87eea67dd3eb46c1d52cbad75d8db2eae777 118220 awn-applets-common_0.4.0-5_armhf.deb Files: 9ffeba622787a1b9f190a41becbf1a97 204790 gnome optional awn-applets-c-core_0.4.0-5_armhf.deb afd7d9c6df57debd6e1b05c48dc5ba35 113408 gnome optional awn-applets-c-extras_0.4.0-5_armhf.deb 554ce4fe96520ceb7b7d9e989812b697 37314 python optional python-awn-extras_0.4.0-5_armhf.deb a95493d80c661368fbdbb5491e014bcb 795920 debug extra awn-applets-c-dbg_0.4.0-5_armhf.deb ecc35d01b82da16004313249ee484d0c 118220 gnome optional awn-applets-common_0.4.0-5_armhf.deb ┌──────────────────────────────────────────────────────────────────────────────┐ │ Package contents │ └──────────────────────────────────────────────────────────────────────────────┘ awn-applets-c-core_0.4.0-5_armhf.deb ──────────────────────────────────── new debian package, version 2.0. size 204790 bytes: control archive= 2349 bytes. 2158 bytes, 32 lines control 3467 bytes, 37 lines md5sums Package: awn-applets-c-core Source: awn-extras-applets Version: 0.4.0-5 Architecture: armhf Maintainer: Julien Lavergne Installed-Size: 703 Depends: gconf-service, libatk1.0-0 (>= 1.12.4), libawn1 (>= 0.4.0), libc6 (>= 2.13-28), libcairo2 (>= 1.4.10), libdbus-1-3 (>= 1.0.2), libdbus-glib-1-2 (>= 0.88), libdesktop-agnostic0 (>= 0.3.90), libfontconfig1 (>= 2.9.0), libfreetype6 (>= 2.2.1), libgcc1 (>= 1:4.4.0), libgconf-2-4 (>= 2.31.1), libgdk-pixbuf2.0-0 (>= 2.22.0), libglib2.0-0 (>= 2.24.0), libgnome-menu2 (>= 2.27.92), libgtk2.0-0 (>= 2.24.0), libgtop2-7 (>= 2.22.3), libnotify4 (>= 0.7.0), libpango1.0-0 (>= 1.14.0), libvte9 (>= 1:0.24.0), libwnck22 (>= 2.30.0-3), libx11-6, libxcomposite1 (>= 1:0.3-1), libxrender1, gconf2 (>= 2.28.1-2), awn-applets-common, avant-window-navigator Recommends: awn-settings, awn-applets-python-core, xdg-utils Suggests: awn-applets-c-extras, gconf-editor, python-gconf Breaks: avant-windows-navigator (<< 0.4.0-1), awn-applets-python-core (<< 0.4.0-1) Provides: notification-daemon Section: gnome Priority: optional Homepage: https://launchpad.net/awn-extras Description: Collection of applets for Awn, written in C or Vala 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: * awn-notification-daemon: Libnotify notification daemon implementation. * awn-system-monitor: Display CPU activity and system stats on click. * 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 * plugger: Displays mounted volumes and allows you to browse them. * shinyswitcher: A workspace switcher supporting compiz and other WMs. * showdesktop: Hides/shows all of the windows of the current viewport, similar to the showdesktop icon of gnome-panel. * garbage: A trash applet, like the one from gnome-panel. drwxr-xr-x root/root 0 2012-06-24 07:55 ./ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/avant-window-navigator/ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/avant-window-navigator/applets/ -rw-r--r-- root/root 379 2012-06-24 07:54 ./usr/share/avant-window-navigator/applets/notification-daemon.desktop -rw-r--r-- root/root 247 2012-06-24 07:54 ./usr/share/avant-window-navigator/applets/cairo-menu.desktop -rw-r--r-- root/root 282 2012-06-24 07:54 ./usr/share/avant-window-navigator/applets/shinyswitcher.desktop -rw-r--r-- root/root 395 2012-06-24 07:54 ./usr/share/avant-window-navigator/applets/awnsystemmonitor.desktop drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/avant-window-navigator/applets/shinyswitcher/ -rw-r--r-- root/root 3117 2012-06-24 07:54 ./usr/share/avant-window-navigator/applets/shinyswitcher/shiny-prefs.py -rw-r--r-- root/root 69108 2012-06-24 07:54 ./usr/share/avant-window-navigator/applets/shinyswitcher/shiny-prefs.ui -rw-r--r-- root/root 481 2012-06-24 07:54 ./usr/share/avant-window-navigator/applets/garbage.desktop -rw-r--r-- root/root 395 2012-06-24 07:54 ./usr/share/avant-window-navigator/applets/showdesktop.desktop -rw-r--r-- root/root 496 2012-06-24 07:54 ./usr/share/avant-window-navigator/applets/awnterm.desktop -rw-r--r-- root/root 292 2012-06-24 07:54 ./usr/share/avant-window-navigator/applets/notification-area.desktop drwxr-xr-x root/root 0 2012-06-24 07:54 ./usr/share/avant-window-navigator/applets/notification-area/ -rw-r--r-- root/root 22864 2012-06-24 07:54 ./usr/share/avant-window-navigator/applets/notification-area/na-prefs.ui drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/avant-window-navigator/schemas/ -rw-r--r-- root/root 689 2012-06-24 07:54 ./usr/share/avant-window-navigator/schemas/awn-applet-notification-area.schema-ini -rw-r--r-- root/root 1774 2012-06-24 07:54 ./usr/share/avant-window-navigator/schemas/awn-applet-cairo-menu.schema-ini -rw-r--r-- root/root 3087 2012-06-24 07:54 ./usr/share/avant-window-navigator/schemas/awn-applet-shinyswitcher.schema-ini -rw-r--r-- root/root 2723 2012-06-24 07:54 ./usr/share/avant-window-navigator/schemas/awn-applet-notification-daemon.schema-ini -rw-r--r-- root/root 395 2012-06-24 07:54 ./usr/share/avant-window-navigator/schemas/awn-applet-garbage.schema-ini -rw-r--r-- root/root 1446 2012-06-24 07:54 ./usr/share/avant-window-navigator/schemas/awn-applet-awnterm.schema-ini drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/gconf/ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/gconf/schemas/ -rw-r--r-- root/root 7296 2012-06-24 07:54 ./usr/share/gconf/schemas/awn-applet-notification-daemon.schemas -rw-r--r-- root/root 851 2012-06-24 07:54 ./usr/share/gconf/schemas/awn-applet-garbage.schemas -rw-r--r-- root/root 8217 2012-06-24 07:54 ./usr/share/gconf/schemas/awn-applet-shinyswitcher.schemas -rw-r--r-- root/root 7958 2012-06-24 07:54 ./usr/share/gconf/schemas/awn-applet-cairo-menu.schemas -rw-r--r-- root/root 2078 2012-06-24 07:54 ./usr/share/gconf/schemas/awn-applet-notification-area.schemas -rw-r--r-- root/root 2163 2012-06-24 07:54 ./usr/share/gconf/schemas/awnsystemmonitor.schemas -rw-r--r-- root/root 1868 2012-06-24 07:54 ./usr/share/gconf/schemas/awn-applet-awnterm.schemas drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/icons/ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/icons/hicolor/ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/icons/hicolor/scalable/ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/icons/hicolor/scalable/apps/ -rw-r--r-- root/root 23904 2012-06-24 07:54 ./usr/share/icons/hicolor/scalable/apps/notification-area.svg drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/doc/ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/doc/awn-applets-c-core/ -rw-r--r-- root/root 5138 2012-04-01 14:33 ./usr/share/doc/awn-applets-c-core/changelog.Debian.gz -rw-r--r-- root/root 29406 2010-07-17 04:07 ./usr/share/doc/awn-applets-c-core/copyright -rw-r--r-- root/root 380 2009-08-14 05:07 ./usr/share/doc/awn-applets-c-core/changelog.gz drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/lib/ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/lib/awn/ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/lib/awn/applets/ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/lib/awn/applets/cairo-menu/ -rw-r--r-- root/root 39600 2012-06-24 07:55 ./usr/lib/awn/applets/cairo-menu/gnome-menu-builder.so -rw-r--r-- root/root 40304 2012-06-24 07:55 ./usr/lib/awn/applets/cairo-menu/cairo-menu.so drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/lib/awn/applets/showdesktop/ -rw-r--r-- root/root 10312 2012-06-24 07:55 ./usr/lib/awn/applets/showdesktop/showdesktop.so drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/lib/awn/applets/awnterm/ -rw-r--r-- root/root 56328 2012-06-24 07:55 ./usr/lib/awn/applets/awnterm/awnterm.so drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/lib/awn/applets/shinyswitcher/ -rw-r--r-- root/root 41240 2012-06-24 07:55 ./usr/lib/awn/applets/shinyswitcher/shinyswitcher.so drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/lib/awn/applets/notification-daemon/ -rw-r--r-- root/root 54172 2012-06-24 07:55 ./usr/lib/awn/applets/notification-daemon/notification-daemon.so drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/lib/awn/applets/garbage/ -rw-r--r-- root/root 22944 2012-06-24 07:55 ./usr/lib/awn/applets/garbage/garbage.so drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/lib/awn/applets/awnsystemmonitor/ -rw-r--r-- root/root 89560 2012-06-24 07:55 ./usr/lib/awn/applets/awnsystemmonitor/awnsystemmonitor.so drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/lib/awn/applets/notification-area/ -rw-r--r-- root/root 53052 2012-06-24 07:55 ./usr/lib/awn/applets/notification-area/notification-area.so awn-applets-c-extras_0.4.0-5_armhf.deb ────────────────────────────────────── new debian package, version 2.0. size 113408 bytes: control archive= 2094 bytes. 1443 bytes, 23 lines control 3745 bytes, 39 lines md5sums Package: awn-applets-c-extras Source: awn-extras-applets Version: 0.4.0-5 Architecture: armhf Maintainer: Julien Lavergne Installed-Size: 428 Depends: libatk1.0-0 (>= 1.12.4), libawn1 (>= 0.4.0), libc6 (>= 2.13-28), libcairo2 (>= 1.2.4), libdbus-1-3 (>= 1.0.2), libdbus-glib-1-2 (>= 0.78), libdesktop-agnostic0 (>= 0.3.90), libfontconfig1 (>= 2.9.0), libfreetype6 (>= 2.2.1), libgdk-pixbuf2.0-0 (>= 2.22.0), libglib2.0-0 (>= 2.24.0), libgnome-menu2 (>= 2.27.92), libgtk2.0-0 (>= 2.12.0), libgtop2-7 (>= 2.22.3), libjavascriptcoregtk-1.0-0 (>= 1.5.1), libpango1.0-0 (>= 1.14.0), libsoup2.4-1 (>= 2.4.0), libwebkitgtk-1.0-0 (>= 1.3.10), gconf2 (>= 2.28.1-2), awn-applets-common, avant-window-navigator Recommends: awn-settings Breaks: awn-applets-python-extras (<< 0.4.0-1) Section: gnome Priority: optional Homepage: https://launchpad.net/awn-extras Description: Collection of extras applets for Awn, written in C or Vala 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: * digitalClock: A digital clock and calendar applet. * main-menu: Display a list of all the applications on your computer. * places: Displays shortcuts in buttons. * sysmon: Display CPU activity and system stats on click. * webapplet: Displays a web page. drwxr-xr-x root/root 0 2012-06-24 07:55 ./ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/avant-window-navigator/ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/avant-window-navigator/applets/ drwxr-xr-x root/root 0 2012-06-24 07:54 ./usr/share/avant-window-navigator/applets/digital-clock/ -rw-r--r-- root/root 13616 2012-06-24 07:54 ./usr/share/avant-window-navigator/applets/digital-clock/dg-prefs.ui -rw-r--r-- root/root 320 2012-06-24 07:54 ./usr/share/avant-window-navigator/applets/main-menu.desktop -rw-r--r-- root/root 524 2012-06-24 07:54 ./usr/share/avant-window-navigator/applets/digital-clock.desktop -rw-r--r-- root/root 580 2012-06-24 07:54 ./usr/share/avant-window-navigator/applets/places.desktop -rw-r--r-- root/root 224 2012-06-24 07:54 ./usr/share/avant-window-navigator/applets/webapplet.desktop -rw-r--r-- root/root 321 2012-06-24 07:54 ./usr/share/avant-window-navigator/applets/sysmon.desktop drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/avant-window-navigator/applets/webapplet/ drwxr-xr-x root/root 0 2012-06-24 07:54 ./usr/share/avant-window-navigator/applets/webapplet/icons/ -rw-r--r-- root/root 1105 2012-06-24 07:54 ./usr/share/avant-window-navigator/applets/webapplet/icons/digg-22.png -rw-r--r-- root/root 1879 2012-06-24 07:54 ./usr/share/avant-window-navigator/applets/webapplet/icons/pandora-48.png -rw-r--r-- root/root 731 2012-06-24 07:54 ./usr/share/avant-window-navigator/applets/webapplet/icons/facebook-22.png -rw-r--r-- root/root 18625 2012-06-24 07:54 ./usr/share/avant-window-navigator/applets/webapplet/icons/digg.svg -rw-r--r-- root/root 2600 2012-06-24 07:54 ./usr/share/avant-window-navigator/applets/webapplet/icons/rtm.png -rw-r--r-- root/root 16779 2012-06-24 07:54 ./usr/share/avant-window-navigator/applets/webapplet/icons/friendfeed.svg -rw-r--r-- root/root 924 2012-06-24 07:54 ./usr/share/avant-window-navigator/applets/webapplet/icons/twitter-22.png -rw-r--r-- root/root 11136 2012-06-24 07:54 ./usr/share/avant-window-navigator/applets/webapplet/icons/pingfm.svg -rw-r--r-- root/root 1253 2012-06-24 07:54 ./usr/share/avant-window-navigator/applets/webapplet/icons/brightkite-22.png -rw-r--r-- root/root 673 2012-06-24 07:54 ./usr/share/avant-window-navigator/applets/webapplet/icons/pingfm-22.png -rw-r--r-- root/root 1368 2012-06-24 07:54 ./usr/share/avant-window-navigator/applets/webapplet/icons/meebo-48.png -rw-r--r-- root/root 1208 2012-06-24 07:54 ./usr/share/avant-window-navigator/applets/webapplet/icons/friendfeed-22.png -rw-r--r-- root/root 23894 2012-06-24 07:54 ./usr/share/avant-window-navigator/applets/webapplet/icons/brightkite.svg -rw-r--r-- root/root 9259 2012-06-24 07:54 ./usr/share/avant-window-navigator/applets/webapplet/icons/twitter.svg -rw-r--r-- root/root 8215 2012-06-24 07:54 ./usr/share/avant-window-navigator/applets/webapplet/icons/facebook.svg -rw-r--r-- root/root 1201 2012-06-24 07:54 ./usr/share/avant-window-navigator/applets/webapplet/webapplet-websites.ini drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/avant-window-navigator/schemas/ -rw-r--r-- root/root 1743 2012-06-24 07:54 ./usr/share/avant-window-navigator/schemas/awn-applet-digital-clock.schema-ini -rw-r--r-- root/root 745 2012-06-24 07:54 ./usr/share/avant-window-navigator/schemas/awn-applet-webapplet.schema-ini -rw-r--r-- root/root 1146 2012-06-24 07:54 ./usr/share/avant-window-navigator/schemas/awn-applet-sysmon.schema-ini -rw-r--r-- root/root 2464 2012-06-24 07:54 ./usr/share/avant-window-navigator/schemas/awn-applet-places.schema-ini drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/gconf/ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/gconf/schemas/ -rw-r--r-- root/root 3397 2012-06-24 07:54 ./usr/share/gconf/schemas/awn-applet-sysmon.schemas -rw-r--r-- root/root 2533 2012-06-24 07:54 ./usr/share/gconf/schemas/awn-applet-webapplet.schemas -rw-r--r-- root/root 4892 2012-06-24 07:54 ./usr/share/gconf/schemas/awn-applet-places.schemas -rw-r--r-- root/root 3119 2012-06-24 07:54 ./usr/share/gconf/schemas/awn-applet-digital-clock.schemas drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/icons/ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/icons/hicolor/ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/icons/hicolor/scalable/ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/icons/hicolor/scalable/apps/ -rw-r--r-- root/root 16187 2012-06-24 07:54 ./usr/share/icons/hicolor/scalable/apps/awn-applet-digital-clock.svg drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/doc/ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/doc/awn-applets-c-extras/ -rw-r--r-- root/root 5138 2012-04-01 14:33 ./usr/share/doc/awn-applets-c-extras/changelog.Debian.gz -rw-r--r-- root/root 29406 2010-07-17 04:07 ./usr/share/doc/awn-applets-c-extras/copyright -rw-r--r-- root/root 380 2009-08-14 05:07 ./usr/share/doc/awn-applets-c-extras/changelog.gz drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/lib/ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/lib/awn/ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/lib/awn/applets/ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/lib/awn/applets/digital-clock/ -rw-r--r-- root/root 31116 2012-06-24 07:55 ./usr/lib/awn/applets/digital-clock/digital-clock.so drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/lib/awn/applets/sysmon/ -rw-r--r-- root/root 47712 2012-06-24 07:55 ./usr/lib/awn/applets/sysmon/sysmon.so drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/lib/awn/applets/places/ -rw-r--r-- root/root 31788 2012-06-24 07:55 ./usr/lib/awn/applets/places/places.so drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/lib/awn/applets/webapplet/ -rw-r--r-- root/root 18668 2012-06-24 07:55 ./usr/lib/awn/applets/webapplet/webapplet.so drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/lib/awn/applets/main-menu/ -rw-r--r-- root/root 14496 2012-06-24 07:55 ./usr/lib/awn/applets/main-menu/main-menu.so python-awn-extras_0.4.0-5_armhf.deb ─────────────────────────────────── new debian package, version 2.0. size 37314 bytes: control archive= 1065 bytes. 690 bytes, 17 lines control 633 bytes, 8 lines md5sums 167 bytes, 9 lines * postinst #!/bin/sh 271 bytes, 14 lines * prerm #!/bin/sh Package: python-awn-extras Source: awn-extras-applets Version: 0.4.0-5 Architecture: armhf Maintainer: Julien Lavergne Installed-Size: 190 Depends: python2.7 | python2.6, python (>= 2.6.6-7~), python (<< 2.8) Conflicts: python-awnlib Replaces: python-awnlib Provides: python2.6-awn-extras, python2.7-awn-extras Section: python Priority: optional Homepage: https://launchpad.net/awn-extras Description: Python bindings for avant-window-navigator's applets This package provides Python bindings to create and use Python applets with functions of libawn-extras. It also includes AWNLib, a collection of functions to simplify the creation of applets with Python. drwxr-xr-x root/root 0 2012-06-24 07:55 ./ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/pyshared/ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/pyshared/awn/ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/pyshared/awn/extras/ -rw-r--r-- root/root 21519 2012-06-24 07:54 ./usr/share/pyshared/awn/extras/awnmediaplayers.py -rw-r--r-- root/root 10137 2012-06-24 07:54 ./usr/share/pyshared/awn/extras/configbinder.py -rw-r--r-- root/root 47971 2012-06-24 07:54 ./usr/share/pyshared/awn/extras/awnlib.py -rw-r--r-- root/root 1258 2012-06-24 07:54 ./usr/share/pyshared/awn/extras/__init__.py -rw-r--r-- root/root 3329 2012-06-24 07:54 ./usr/share/pyshared/awn/extras/threadqueue.py drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/doc/ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/doc/python-awn-extras/ -rw-r--r-- root/root 5138 2012-04-01 14:33 ./usr/share/doc/python-awn-extras/changelog.Debian.gz -rw-r--r-- root/root 29406 2010-07-17 04:07 ./usr/share/doc/python-awn-extras/copyright -rw-r--r-- root/root 380 2009-08-14 05:07 ./usr/share/doc/python-awn-extras/changelog.gz drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/lib/ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/lib/python2.7/ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/lib/python2.7/dist-packages/ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/lib/python2.7/dist-packages/awn/ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/lib/python2.7/dist-packages/awn/extras/ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/lib/python2.6/ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/lib/python2.6/dist-packages/ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/lib/python2.6/dist-packages/awn/ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/lib/python2.6/dist-packages/awn/extras/ lrwxrwxrwx root/root 0 2012-06-24 07:55 ./usr/lib/python2.7/dist-packages/awn/extras/awnmediaplayers.py -> ../../../../../share/pyshared/awn/extras/awnmediaplayers.py lrwxrwxrwx root/root 0 2012-06-24 07:55 ./usr/lib/python2.7/dist-packages/awn/extras/configbinder.py -> ../../../../../share/pyshared/awn/extras/configbinder.py lrwxrwxrwx root/root 0 2012-06-24 07:55 ./usr/lib/python2.7/dist-packages/awn/extras/awnlib.py -> ../../../../../share/pyshared/awn/extras/awnlib.py lrwxrwxrwx root/root 0 2012-06-24 07:55 ./usr/lib/python2.7/dist-packages/awn/extras/__init__.py -> ../../../../../share/pyshared/awn/extras/__init__.py lrwxrwxrwx root/root 0 2012-06-24 07:55 ./usr/lib/python2.7/dist-packages/awn/extras/threadqueue.py -> ../../../../../share/pyshared/awn/extras/threadqueue.py lrwxrwxrwx root/root 0 2012-06-24 07:55 ./usr/lib/python2.6/dist-packages/awn/extras/awnmediaplayers.py -> ../../../../../share/pyshared/awn/extras/awnmediaplayers.py lrwxrwxrwx root/root 0 2012-06-24 07:55 ./usr/lib/python2.6/dist-packages/awn/extras/configbinder.py -> ../../../../../share/pyshared/awn/extras/configbinder.py lrwxrwxrwx root/root 0 2012-06-24 07:55 ./usr/lib/python2.6/dist-packages/awn/extras/awnlib.py -> ../../../../../share/pyshared/awn/extras/awnlib.py lrwxrwxrwx root/root 0 2012-06-24 07:55 ./usr/lib/python2.6/dist-packages/awn/extras/__init__.py -> ../../../../../share/pyshared/awn/extras/__init__.py lrwxrwxrwx root/root 0 2012-06-24 07:55 ./usr/lib/python2.6/dist-packages/awn/extras/threadqueue.py -> ../../../../../share/pyshared/awn/extras/threadqueue.py awn-applets-c-dbg_0.4.0-5_armhf.deb ─────────────────────────────────── new debian package, version 2.0. size 795920 bytes: control archive= 1100 bytes. 584 bytes, 16 lines control 1577 bytes, 17 lines md5sums Package: awn-applets-c-dbg Source: awn-extras-applets Version: 0.4.0-5 Architecture: armhf Maintainer: Julien Lavergne Installed-Size: 1888 Depends: awn-applets-c-extras (= 0.4.0-5) Section: debug Priority: extra Homepage: https://launchpad.net/awn-extras Description: Collection of applets for avant-window-navigator - debug symbols 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 the debugging symbols. drwxr-xr-x root/root 0 2012-06-24 07:55 ./ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/doc/ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/doc/awn-applets-c-dbg/ -rw-r--r-- root/root 5138 2012-04-01 14:33 ./usr/share/doc/awn-applets-c-dbg/changelog.Debian.gz -rw-r--r-- root/root 29406 2010-07-17 04:07 ./usr/share/doc/awn-applets-c-dbg/copyright -rw-r--r-- root/root 380 2009-08-14 05:07 ./usr/share/doc/awn-applets-c-dbg/changelog.gz drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/lib/ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/lib/debug/ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/lib/debug/usr/ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/lib/debug/usr/lib/ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/lib/debug/usr/lib/awn/ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/lib/debug/usr/lib/awn/applets/ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/lib/debug/usr/lib/awn/applets/digital-clock/ -rw-r--r-- root/root 105908 2012-06-24 07:55 ./usr/lib/debug/usr/lib/awn/applets/digital-clock/digital-clock.so drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/lib/debug/usr/lib/awn/applets/cairo-menu/ -rw-r--r-- root/root 124747 2012-06-24 07:55 ./usr/lib/debug/usr/lib/awn/applets/cairo-menu/gnome-menu-builder.so -rw-r--r-- root/root 194615 2012-06-24 07:55 ./usr/lib/debug/usr/lib/awn/applets/cairo-menu/cairo-menu.so drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/lib/debug/usr/lib/awn/applets/showdesktop/ -rw-r--r-- root/root 51015 2012-06-24 07:55 ./usr/lib/debug/usr/lib/awn/applets/showdesktop/showdesktop.so drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/lib/debug/usr/lib/awn/applets/awnterm/ -rw-r--r-- root/root 160684 2012-06-24 07:55 ./usr/lib/debug/usr/lib/awn/applets/awnterm/awnterm.so drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/lib/debug/usr/lib/awn/applets/sysmon/ -rw-r--r-- root/root 234952 2012-06-24 07:55 ./usr/lib/debug/usr/lib/awn/applets/sysmon/sysmon.so drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/lib/debug/usr/lib/awn/applets/shinyswitcher/ -rw-r--r-- root/root 101539 2012-06-24 07:55 ./usr/lib/debug/usr/lib/awn/applets/shinyswitcher/shinyswitcher.so drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/lib/debug/usr/lib/awn/applets/places/ -rw-r--r-- root/root 60295 2012-06-24 07:55 ./usr/lib/debug/usr/lib/awn/applets/places/places.so drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/lib/debug/usr/lib/awn/applets/notification-daemon/ -rw-r--r-- root/root 129745 2012-06-24 07:55 ./usr/lib/debug/usr/lib/awn/applets/notification-daemon/notification-daemon.so drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/lib/debug/usr/lib/awn/applets/webapplet/ -rw-r--r-- root/root 58332 2012-06-24 07:55 ./usr/lib/debug/usr/lib/awn/applets/webapplet/webapplet.so drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/lib/debug/usr/lib/awn/applets/garbage/ -rw-r--r-- root/root 100738 2012-06-24 07:55 ./usr/lib/debug/usr/lib/awn/applets/garbage/garbage.so drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/lib/debug/usr/lib/awn/applets/awnsystemmonitor/ -rw-r--r-- root/root 256965 2012-06-24 07:55 ./usr/lib/debug/usr/lib/awn/applets/awnsystemmonitor/awnsystemmonitor.so drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/lib/debug/usr/lib/awn/applets/main-menu/ -rw-r--r-- root/root 34545 2012-06-24 07:55 ./usr/lib/debug/usr/lib/awn/applets/main-menu/main-menu.so drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/lib/debug/usr/lib/awn/applets/notification-area/ -rw-r--r-- root/root 181846 2012-06-24 07:55 ./usr/lib/debug/usr/lib/awn/applets/notification-area/notification-area.so awn-applets-common_0.4.0-5_armhf.deb ──────────────────────────────────── new debian package, version 2.0. size 118220 bytes: control archive= 1664 bytes. 553 bytes, 15 lines control 3476 bytes, 43 lines md5sums Package: awn-applets-common Source: awn-extras-applets Version: 0.4.0-5 Architecture: armhf Maintainer: Julien Lavergne Installed-Size: 656 Section: gnome Priority: optional Homepage: https://launchpad.net/awn-extras Description: Collection of applets for avant-window-navigator - common files 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 common files like translations. drwxr-xr-x root/root 0 2012-06-24 07:55 ./ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/doc/ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/doc/awn-applets-common/ -rw-r--r-- root/root 5138 2012-04-01 14:33 ./usr/share/doc/awn-applets-common/changelog.Debian.gz -rw-r--r-- root/root 29406 2010-07-17 04:07 ./usr/share/doc/awn-applets-common/copyright -rw-r--r-- root/root 380 2009-08-14 05:07 ./usr/share/doc/awn-applets-common/changelog.gz drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/locale/ drwxr-xr-x root/root 0 2012-06-24 07:54 ./usr/share/locale/ca/ drwxr-xr-x root/root 0 2012-06-24 07:54 ./usr/share/locale/ca/LC_MESSAGES/ -rw-r--r-- root/root 9994 2012-06-24 07:54 ./usr/share/locale/ca/LC_MESSAGES/awn-extras.mo drwxr-xr-x root/root 0 2012-06-24 07:54 ./usr/share/locale/lt/ drwxr-xr-x root/root 0 2012-06-24 07:54 ./usr/share/locale/lt/LC_MESSAGES/ -rw-r--r-- root/root 1331 2012-06-24 07:54 ./usr/share/locale/lt/LC_MESSAGES/awn-extras.mo drwxr-xr-x root/root 0 2012-06-24 07:54 ./usr/share/locale/de/ drwxr-xr-x root/root 0 2012-06-24 07:54 ./usr/share/locale/de/LC_MESSAGES/ -rw-r--r-- root/root 6846 2012-06-24 07:54 ./usr/share/locale/de/LC_MESSAGES/awn-extras.mo drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/locale/pl/ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/locale/pl/LC_MESSAGES/ -rw-r--r-- root/root 9868 2012-06-24 07:55 ./usr/share/locale/pl/LC_MESSAGES/awn-extras.mo drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/locale/nn/ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/locale/nn/LC_MESSAGES/ -rw-r--r-- root/root 903 2012-06-24 07:55 ./usr/share/locale/nn/LC_MESSAGES/awn-extras.mo drwxr-xr-x root/root 0 2012-06-24 07:54 ./usr/share/locale/da/ drwxr-xr-x root/root 0 2012-06-24 07:54 ./usr/share/locale/da/LC_MESSAGES/ -rw-r--r-- root/root 551 2012-06-24 07:54 ./usr/share/locale/da/LC_MESSAGES/awn-extras.mo drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/locale/sv_SE/ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/locale/sv_SE/LC_MESSAGES/ -rw-r--r-- root/root 2185 2012-06-24 07:55 ./usr/share/locale/sv_SE/LC_MESSAGES/awn-extras.mo drwxr-xr-x root/root 0 2012-06-24 07:54 ./usr/share/locale/es/ drwxr-xr-x root/root 0 2012-06-24 07:54 ./usr/share/locale/es/LC_MESSAGES/ -rw-r--r-- root/root 14820 2012-06-24 07:54 ./usr/share/locale/es/LC_MESSAGES/awn-extras.mo drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/locale/th/ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/locale/th/LC_MESSAGES/ -rw-r--r-- root/root 1192 2012-06-24 07:55 ./usr/share/locale/th/LC_MESSAGES/awn-extras.mo drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/locale/pt/ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/locale/pt/LC_MESSAGES/ -rw-r--r-- root/root 1524 2012-06-24 07:55 ./usr/share/locale/pt/LC_MESSAGES/awn-extras.mo drwxr-xr-x root/root 0 2012-06-24 07:54 ./usr/share/locale/af/ drwxr-xr-x root/root 0 2012-06-24 07:54 ./usr/share/locale/af/LC_MESSAGES/ -rw-r--r-- root/root 1541 2012-06-24 07:54 ./usr/share/locale/af/LC_MESSAGES/awn-extras.mo drwxr-xr-x root/root 0 2012-06-24 07:54 ./usr/share/locale/it/ drwxr-xr-x root/root 0 2012-06-24 07:54 ./usr/share/locale/it/LC_MESSAGES/ -rw-r--r-- root/root 7715 2012-06-24 07:54 ./usr/share/locale/it/LC_MESSAGES/awn-extras.mo drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/locale/zh_CN/ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/locale/zh_CN/LC_MESSAGES/ -rw-r--r-- root/root 6510 2012-06-24 07:55 ./usr/share/locale/zh_CN/LC_MESSAGES/awn-extras.mo drwxr-xr-x root/root 0 2012-06-24 07:54 ./usr/share/locale/en_CA/ drwxr-xr-x root/root 0 2012-06-24 07:54 ./usr/share/locale/en_CA/LC_MESSAGES/ -rw-r--r-- root/root 1942 2012-06-24 07:54 ./usr/share/locale/en_CA/LC_MESSAGES/awn-extras.mo drwxr-xr-x root/root 0 2012-06-24 07:54 ./usr/share/locale/nb/ drwxr-xr-x root/root 0 2012-06-24 07:54 ./usr/share/locale/nb/LC_MESSAGES/ -rw-r--r-- root/root 1906 2012-06-24 07:54 ./usr/share/locale/nb/LC_MESSAGES/awn-extras.mo drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/locale/uk/ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/locale/uk/LC_MESSAGES/ -rw-r--r-- root/root 628 2012-06-24 07:55 ./usr/share/locale/uk/LC_MESSAGES/awn-extras.mo drwxr-xr-x root/root 0 2012-06-24 07:54 ./usr/share/locale/fr/ drwxr-xr-x root/root 0 2012-06-24 07:54 ./usr/share/locale/fr/LC_MESSAGES/ -rw-r--r-- root/root 43326 2012-06-24 07:54 ./usr/share/locale/fr/LC_MESSAGES/awn-extras.mo drwxr-xr-x root/root 0 2012-06-24 07:54 ./usr/share/locale/bg/ drwxr-xr-x root/root 0 2012-06-24 07:54 ./usr/share/locale/bg/LC_MESSAGES/ -rw-r--r-- root/root 11611 2012-06-24 07:54 ./usr/share/locale/bg/LC_MESSAGES/awn-extras.mo drwxr-xr-x root/root 0 2012-06-24 07:54 ./usr/share/locale/en_GB/ drwxr-xr-x root/root 0 2012-06-24 07:54 ./usr/share/locale/en_GB/LC_MESSAGES/ -rw-r--r-- root/root 1506 2012-06-24 07:54 ./usr/share/locale/en_GB/LC_MESSAGES/awn-extras.mo drwxr-xr-x root/root 0 2012-06-24 07:54 ./usr/share/locale/id/ drwxr-xr-x root/root 0 2012-06-24 07:54 ./usr/share/locale/id/LC_MESSAGES/ -rw-r--r-- root/root 2330 2012-06-24 07:54 ./usr/share/locale/id/LC_MESSAGES/awn-extras.mo drwxr-xr-x root/root 0 2012-06-24 07:54 ./usr/share/locale/fi/ drwxr-xr-x root/root 0 2012-06-24 07:54 ./usr/share/locale/fi/LC_MESSAGES/ -rw-r--r-- root/root 1571 2012-06-24 07:54 ./usr/share/locale/fi/LC_MESSAGES/awn-extras.mo drwxr-xr-x root/root 0 2012-06-24 07:54 ./usr/share/locale/eu/ drwxr-xr-x root/root 0 2012-06-24 07:54 ./usr/share/locale/eu/LC_MESSAGES/ -rw-r--r-- root/root 1545 2012-06-24 07:54 ./usr/share/locale/eu/LC_MESSAGES/awn-extras.mo drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/locale/ru/ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/locale/ru/LC_MESSAGES/ -rw-r--r-- root/root 11919 2012-06-24 07:55 ./usr/share/locale/ru/LC_MESSAGES/awn-extras.mo drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/locale/vi/ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/locale/vi/LC_MESSAGES/ -rw-r--r-- root/root 4432 2012-06-24 07:55 ./usr/share/locale/vi/LC_MESSAGES/awn-extras.mo drwxr-xr-x root/root 0 2012-06-24 07:54 ./usr/share/locale/ar/ drwxr-xr-x root/root 0 2012-06-24 07:54 ./usr/share/locale/ar/LC_MESSAGES/ -rw-r--r-- root/root 13447 2012-06-24 07:54 ./usr/share/locale/ar/LC_MESSAGES/awn-extras.mo drwxr-xr-x root/root 0 2012-06-24 07:54 ./usr/share/locale/ms/ drwxr-xr-x root/root 0 2012-06-24 07:54 ./usr/share/locale/ms/LC_MESSAGES/ -rw-r--r-- root/root 1541 2012-06-24 07:54 ./usr/share/locale/ms/LC_MESSAGES/awn-extras.mo drwxr-xr-x root/root 0 2012-06-24 07:54 ./usr/share/locale/hu/ drwxr-xr-x root/root 0 2012-06-24 07:54 ./usr/share/locale/hu/LC_MESSAGES/ -rw-r--r-- root/root 7255 2012-06-24 07:54 ./usr/share/locale/hu/LC_MESSAGES/awn-extras.mo drwxr-xr-x root/root 0 2012-06-24 07:54 ./usr/share/locale/en_US@piglatin/ drwxr-xr-x root/root 0 2012-06-24 07:54 ./usr/share/locale/en_US@piglatin/LC_MESSAGES/ -rw-r--r-- root/root 5073 2012-06-24 07:54 ./usr/share/locale/en_US@piglatin/LC_MESSAGES/awn-extras.mo drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/locale/sv/ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/locale/sv/LC_MESSAGES/ -rw-r--r-- root/root 8151 2012-06-24 07:55 ./usr/share/locale/sv/LC_MESSAGES/awn-extras.mo drwxr-xr-x root/root 0 2012-06-24 07:54 ./usr/share/locale/ja/ drwxr-xr-x root/root 0 2012-06-24 07:54 ./usr/share/locale/ja/LC_MESSAGES/ -rw-r--r-- root/root 8882 2012-06-24 07:54 ./usr/share/locale/ja/LC_MESSAGES/awn-extras.mo drwxr-xr-x root/root 0 2012-06-24 07:54 ./usr/share/locale/csb/ drwxr-xr-x root/root 0 2012-06-24 07:54 ./usr/share/locale/csb/LC_MESSAGES/ -rw-r--r-- root/root 6990 2012-06-24 07:54 ./usr/share/locale/csb/LC_MESSAGES/awn-extras.mo drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/locale/tr/ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/locale/tr/LC_MESSAGES/ -rw-r--r-- root/root 1139 2012-06-24 07:55 ./usr/share/locale/tr/LC_MESSAGES/awn-extras.mo drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/locale/zh_TW/ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/locale/zh_TW/LC_MESSAGES/ -rw-r--r-- root/root 9029 2012-06-24 07:55 ./usr/share/locale/zh_TW/LC_MESSAGES/awn-extras.mo drwxr-xr-x root/root 0 2012-06-24 07:54 ./usr/share/locale/he/ drwxr-xr-x root/root 0 2012-06-24 07:54 ./usr/share/locale/he/LC_MESSAGES/ -rw-r--r-- root/root 6078 2012-06-24 07:54 ./usr/share/locale/he/LC_MESSAGES/awn-extras.mo drwxr-xr-x root/root 0 2012-06-24 07:54 ./usr/share/locale/ast/ drwxr-xr-x root/root 0 2012-06-24 07:54 ./usr/share/locale/ast/LC_MESSAGES/ -rw-r--r-- root/root 9877 2012-06-24 07:54 ./usr/share/locale/ast/LC_MESSAGES/awn-extras.mo drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/locale/sk/ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/locale/sk/LC_MESSAGES/ -rw-r--r-- root/root 4391 2012-06-24 07:55 ./usr/share/locale/sk/LC_MESSAGES/awn-extras.mo drwxr-xr-x root/root 0 2012-06-24 07:54 ./usr/share/locale/cs/ drwxr-xr-x root/root 0 2012-06-24 07:54 ./usr/share/locale/cs/LC_MESSAGES/ -rw-r--r-- root/root 37413 2012-06-24 07:54 ./usr/share/locale/cs/LC_MESSAGES/awn-extras.mo drwxr-xr-x root/root 0 2012-06-24 07:54 ./usr/share/locale/ko/ drwxr-xr-x root/root 0 2012-06-24 07:54 ./usr/share/locale/ko/LC_MESSAGES/ -rw-r--r-- root/root 630 2012-06-24 07:54 ./usr/share/locale/ko/LC_MESSAGES/awn-extras.mo drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/locale/nl/ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/locale/nl/LC_MESSAGES/ -rw-r--r-- root/root 2800 2012-06-24 07:55 ./usr/share/locale/nl/LC_MESSAGES/awn-extras.mo drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/locale/pt_BR/ drwxr-xr-x root/root 0 2012-06-24 07:55 ./usr/share/locale/pt_BR/LC_MESSAGES/ -rw-r--r-- root/root 9884 2012-06-24 07:55 ./usr/share/locale/pt_BR/LC_MESSAGES/awn-extras.mo ┌──────────────────────────────────────────────────────────────────────────────┐ │ Post Build │ └──────────────────────────────────────────────────────────────────────────────┘ ┌──────────────────────────────────────────────────────────────────────────────┐ │ Cleanup │ └──────────────────────────────────────────────────────────────────────────────┘ Purging /«BUILDDIR» Reading package lists... Building dependency tree... Reading state information... 0 upgraded, 0 newly installed, 0 to remove and 8 not upgraded. Reading package lists... Building dependency tree... Reading state information... The following packages will be REMOVED: adduser* aspell* aspell-en* autoconf* automake* autotools-dev* bsdmainutils* ca-certificates* dbus* dbus-x11* dconf-gsettings-backend* dconf-service* debhelper* dictionaries-common* file* fontconfig* fontconfig-config* gconf-service* gconf2* gconf2-common* gettext* gettext-base* gir1.2-atk-1.0* gir1.2-freedesktop* gir1.2-gconf-2.0* gir1.2-gdkpixbuf-2.0* gir1.2-glib-2.0* gir1.2-gtk-2.0* gir1.2-gtop-2.0* gir1.2-javascriptcoregtk-1.0* gir1.2-notify-0.7* gir1.2-pango-1.0* gir1.2-rsvg-2.0* gir1.2-soup-2.4* gir1.2-webkit-1.0* glib-networking* glib-networking-common* glib-networking-services* groff-base* gsettings-desktop-schemas* html2text* intltool* intltool-debian* iso-codes* libaspell15* libasprintf0c2* libatk1.0-0* libatk1.0-data* libatk1.0-dev* libavahi-client3* libavahi-common-data* libavahi-common3* libawn-dev* libawn1* libblas3gf* libcairo-gobject2* libcairo-script-interpreter2* libcairo2* libcairo2-dev* libcap2* libcroco3* libcups2* libdatrie1* libdbus-1-3* libdbus-1-dev* libdbus-glib-1-2* libdbus-glib-1-dev* libdconf0* libdesktop-agnostic-bin* libdesktop-agnostic-cfg-gconf* libdesktop-agnostic-data* libdesktop-agnostic-dev* libdesktop-agnostic0* libdrm2* libelf1* libenchant1c2a* libencode-locale-perl* libexpat1* libexpat1-dev* libffi-dev* libffi5* libfile-listing-perl* libfontconfig1* libfontconfig1-dev* libfreetype6* libfreetype6-dev* libgail18* libgconf-2-4* libgconf2-dev* libgcrypt11* libgdk-pixbuf2.0-0* libgdk-pixbuf2.0-common* libgdk-pixbuf2.0-dev* libgeoclue0* libgettextpo0* libgfortran3* libgirepository-1.0-1* libgl1-mesa-glx* libglapi-mesa* libglib2.0-0* libglib2.0-bin* libglib2.0-data* libglib2.0-dev* libgnome-keyring-common* libgnome-keyring0* libgnome-menu-dev* libgnome-menu2* libgnutls26* libgpg-error0* libgssapi-krb5-2* 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* libhttp-cookies-perl* libhttp-date-perl* libhttp-message-perl* libhttp-negotiate-perl* libhunspell-1.3-0* libice-dev* libice6* libicu48* libio-socket-ssl-perl* libjasper1* libjavascriptcoregtk-1.0-0* libjavascriptcoregtk-1.0-dev* libjbig0* libjpeg8* libjs-jquery* libk5crypto3* libkeyutils1* libkrb5-3* libkrb5support0* liblapack3gf* libldap-2.4-2* liblwp-mediatypes-perl* liblwp-protocol-https-perl* libmagic1* libnet-http-perl* libnet-ssleay-perl* libnotify-dev* libnotify4* liborc-0.4-0* libp11-kit0* libpango1.0-0* libpango1.0-dev* libpcre3* libpcre3-dev* libpcrecpp0* libpipeline1* libpixman-1-0* libpixman-1-dev* libpng12-0* libpng12-dev* libpopt0* libproxy0* libpthread-stubs0* libpthread-stubs0-dev* libpython2.7* librsvg2-2* librsvg2-common* librsvg2-dev* libsasl2-2* libsexy-dev* libsexy2* libsm-dev* libsm6* libsoup-gnome2.4-1* libsoup2.4-1* libsoup2.4-dev* libsqlite3-0* libssl-dev* libssl1.0.0* libstartup-notification0* libstartup-notification0-dev* libsystemd-login0* libtasn1-3* libthai-data* libthai0* libtiff4* libunistring0* liburi-perl* libvala-0.16-0* libvte-common* libvte-dev* libvte9* libwebkitgtk-1.0-0* libwebkitgtk-1.0-common* libwebkitgtk-dev* libwnck-common* libwnck-dev* libwnck22* libwww-perl* libwww-robotrules-perl* libx11-6* libx11-data* libx11-dev* libx11-xcb1* libxau-dev* libxau6* libxcb-glx0* libxcb-render0* libxcb-render0-dev* libxcb-shm0* libxcb-shm0-dev* libxcb-util0* 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* libxxf86vm1* m4* man-db* mime-support* netbase* openssl* pkg-config* po-debconf* psmisc* python* python-cairo* python-cairo-dev* python-dev* python-gobject-2* python-gobject-2-dev* python-gtk2* python-gtk2-dev* python-minimal* python-numpy* python-support* python2.7* python2.7-dev* python2.7-minimal* sbuild-build-depends-awn-extras-applets-dummy* sbuild-build-depends-core-dummy* shared-mime-info* ttf-dejavu-core* valac* valac-0.16* valac-0.16-vapi* 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* xorg-sgml-doctools* xtrans-dev* zlib1g-dev* 0 upgraded, 0 newly installed, 290 to remove and 8 not upgraded. After this operation, 368 MB disk space will be freed. (Reading database ... 22818 files and directories currently installed.) Removing sbuild-build-depends-awn-extras-applets-dummy ... Removing libgconf2-dev ... Removing gconf2 ... Purging configuration files for gconf2 ... Removing dbus-x11 ... Purging configuration files for dbus-x11 ... Removing dbus ... All runlevel operations denied by policy invoke-rc.d: policy-rc.d denied execution of stop. Purging configuration files for dbus ... rmdir: failed to remove `/var/run/dbus': No such file or directory Removing adduser ... Purging configuration files for adduser ... Removing libwebkitgtk-dev ... Removing gir1.2-webkit-1.0 ... Removing libjavascriptcoregtk-1.0-dev ... Removing gir1.2-javascriptcoregtk-1.0 ... Removing libwebkitgtk-1.0-0 ... Purging configuration files for libwebkitgtk-1.0-0 ... Removing libsexy-dev ... Removing libsexy2 ... Purging configuration files for libsexy2 ... Removing libenchant1c2a ... Removing aspell-en ... Purging configuration files for aspell-en ... Removing aspell ... Removing intltool ... Removing automake ... Removing autoconf ... Purging configuration files for autoconf ... Removing autotools-dev ... Removing debhelper ... Removing man-db ... Purging configuration files for man-db ... Removing bsdmainutils ... Purging configuration files for bsdmainutils ... Removing libxml-parser-perl ... Removing libsoup2.4-dev ... Removing gir1.2-soup-2.4 ... Removing libsoup-gnome2.4-1:armhf ... Purging configuration files for libsoup-gnome2.4-1:armhf ... Removing libsoup2.4-1:armhf ... Purging configuration files for libsoup2.4-1:armhf ... Removing glib-networking:armhf ... Removing gsettings-desktop-schemas ... Removing dconf-gsettings-backend:armhf ... Removing dconf-service ... Removing dictionaries-common ... Removing 'diversion of /usr/share/dict/words to /usr/share/dict/words.pre-dictionaries-common by dictionaries-common' Purging configuration files for dictionaries-common ... Removing file ... Removing python-gtk2-dev ... Removing python-gtk2 ... Removing libwnck-dev ... Removing libwnck22 ... Purging configuration files for libwnck22 ... Removing libvte-dev ... Removing libvte9 ... Purging configuration files for libvte9 ... Removing librsvg2-dev ... Removing librsvg2-common:armhf ... Removing gir1.2-rsvg-2.0 ... Removing librsvg2-2:armhf ... Purging configuration files for librsvg2-2:armhf ... Removing libawn-dev ... Removing libdesktop-agnostic-dev ... Removing libgtk2.0-dev ... Removing libpango1.0-dev ... Removing libgail18:armhf ... Purging configuration files for libgail18:armhf ... Removing libdesktop-agnostic-bin ... Removing libdesktop-agnostic-cfg-gconf ... Removing libawn1 ... Purging configuration files for libawn1 ... Removing libdesktop-agnostic0 ... Purging configuration files for libdesktop-agnostic0 ... Removing gir1.2-gtk-2.0 ... Removing libgtk2.0-0:armhf ... Purging configuration files for libgtk2.0-0:armhf ... Removing gir1.2-pango-1.0 ... Removing libpango1.0-0:armhf ... Purging configuration files for libpango1.0-0:armhf ... Removing fontconfig ... Purging configuration files for fontconfig ... Removing libxft-dev ... Removing libxft2:armhf ... Purging configuration files for libxft2:armhf ... Removing libcairo2-dev ... Removing libfontconfig1-dev ... Removing python-cairo-dev ... Removing python-cairo ... Removing libcairo-script-interpreter2:armhf ... Purging configuration files for libcairo-script-interpreter2:armhf ... Removing gir1.2-freedesktop ... Removing libcairo-gobject2:armhf ... Purging configuration files for libcairo-gobject2:armhf ... Removing libcairo2:armhf ... Purging configuration files for libcairo2:armhf ... Removing libfontconfig1:armhf ... Purging configuration files for libfontconfig1:armhf ... Removing fontconfig-config ... Purging configuration files for fontconfig-config ... Removing gir1.2-gconf-2.0 ... Removing gconf-service ... Removing libgconf-2-4:armhf ... Purging configuration files for libgconf-2-4:armhf ... Removing gconf2-common ... Purging configuration files for gconf2-common ... Removing po-debconf ... Removing intltool-debian ... Removing gettext ... Removing gettext-base ... Removing libatk1.0-dev ... Removing gir1.2-atk-1.0 ... Removing libnotify-dev ... Removing libgdk-pixbuf2.0-dev ... Removing gir1.2-notify-0.7 ... Removing gir1.2-gdkpixbuf-2.0 ... Removing libgtop2-dev ... Removing gir1.2-gtop-2.0 ... Removing gir1.2-glib-2.0 ... Removing glib-networking-services ... Removing glib-networking-common ... Removing groff-base ... Purging configuration files for groff-base ... Removing html2text ... Purging configuration files for html2text ... Removing libgstreamer-plugins-base0.10-0:armhf ... Purging configuration files for libgstreamer-plugins-base0.10-0:armhf ... Removing iso-codes ... Removing libaspell15 ... Purging configuration files for libaspell15 ... Removing libasprintf0c2:armhf ... Removing libatk1.0-0:armhf ... Purging configuration files for libatk1.0-0:armhf ... Removing libatk1.0-data ... Removing libcups2:armhf ... Purging configuration files for libcups2:armhf ... Removing libavahi-client3:armhf ... Purging configuration files for libavahi-client3:armhf ... Removing libavahi-common3:armhf ... Purging configuration files for libavahi-common3:armhf ... Removing libavahi-common-data:armhf ... Removing python-numpy ... Removing liblapack3gf ... Purging configuration files for liblapack3gf ... Removing libblas3gf ... Purging configuration files for libblas3gf ... Removing libsystemd-login0 ... Purging configuration files for libsystemd-login0 ... Removing libcap2 ... Purging configuration files for libcap2 ... Removing libcroco3:armhf ... Purging configuration files for libcroco3:armhf ... Removing libthai0:armhf ... Purging configuration files for libthai0:armhf ... Removing libdatrie1:armhf ... Purging configuration files for libdatrie1:armhf ... Removing libgnome-keyring0:armhf ... Purging configuration files for libgnome-keyring0:armhf ... Removing libgeoclue0 ... Purging configuration files for libgeoclue0 ... Removing libdbus-glib-1-dev ... Removing libdbus-glib-1-2:armhf ... Purging configuration files for libdbus-glib-1-2:armhf ... Removing libdbus-1-dev ... Removing libdbus-1-3:armhf ... Purging configuration files for libdbus-1-3:armhf ... Removing libdconf0:armhf ... Purging configuration files for libdconf0:armhf ... Removing libdesktop-agnostic-data ... Removing libgl1-mesa-glx:armhf ... Purging configuration files for libgl1-mesa-glx:armhf ... Removing libdrm2:armhf ... Purging configuration files for libdrm2:armhf ... Removing valac ... Removing valac-0.16 ... Removing python-gobject-2-dev ... Removing libgnome-menu-dev ... Removing libglib2.0-dev ... Removing libglib2.0-bin ... Purging configuration files for libglib2.0-bin ... Removing libelf1 ... Purging configuration files for libelf1 ... Removing python-dev ... Removing python2.7-dev ... Removing python-gobject-2 ... Purging configuration files for python-gobject-2 ... Removing python-support ... Purging configuration files for python-support ... Removing python ... Purging configuration files for python ... Removing libpython2.7 ... Purging configuration files for libpython2.7 ... Removing python2.7 ... Purging configuration files for python2.7 ... Removing libexpat1-dev ... Removing libexpat1:armhf ... Purging configuration files for libexpat1:armhf ... Removing libffi-dev:armhf ... Removing shared-mime-info ... Purging configuration files for shared-mime-info ... Removing libstartup-notification0-dev ... Removing pkg-config ... Removing libvala-0.16-0:armhf ... Purging configuration files for libvala-0.16-0:armhf ... Removing libnotify4:armhf ... Purging configuration files for libnotify4:armhf ... Removing libjavascriptcoregtk-1.0-0 ... Purging configuration files for libjavascriptcoregtk-1.0-0 ... Removing libgtop2-7 ... Purging configuration files for libgtop2-7 ... Removing libgstreamer0.10-0:armhf ... Purging configuration files for libgstreamer0.10-0:armhf ... Removing libgnome-menu2 ... Purging configuration files for libgnome-menu2 ... Removing libgirepository-1.0-1 ... Purging configuration files for libgirepository-1.0-1 ... Removing libgdk-pixbuf2.0-0:armhf ... Purging configuration files for libgdk-pixbuf2.0-0:armhf ... Removing libglib2.0-0:armhf ... Purging configuration files for libglib2.0-0:armhf ... Removing libffi5:armhf ... Purging configuration files for libffi5:armhf ... Removing libfreetype6-dev ... Removing libfreetype6:armhf ... Purging configuration files for libfreetype6:armhf ... Removing libxslt1.1:armhf ... Purging configuration files for libxslt1.1:armhf ... Removing libldap-2.4-2:armhf ... Purging configuration files for libldap-2.4-2:armhf ... Removing libgnutls26:armhf ... Purging configuration files for libgnutls26:armhf ... Removing libgcrypt11:armhf ... Purging configuration files for libgcrypt11:armhf ... Removing libgdk-pixbuf2.0-common ... Removing libgettextpo0:armhf ... Removing libgfortran3:armhf ... Purging configuration files for libgfortran3:armhf ... Removing libglapi-mesa:armhf ... Purging configuration files for libglapi-mesa:armhf ... Removing libglib2.0-data ... Removing libgnome-keyring-common ... Removing libgpg-error0:armhf ... Purging configuration files for libgpg-error0:armhf ... Removing libgssapi-krb5-2:armhf ... Purging configuration files for libgssapi-krb5-2:armhf ... Removing libgtk2.0-common ... Purging configuration files for libgtk2.0-common ... Removing libgtop2-common ... Removing libhunspell-1.3-0:armhf ... Purging configuration files for libhunspell-1.3-0:armhf ... Removing libsm-dev:armhf ... Removing libice-dev:armhf ... Removing libxt6:armhf ... Purging configuration files for libxt6:armhf ... Removing libsm6:armhf ... Purging configuration files for libsm6:armhf ... Removing libice6:armhf ... Purging configuration files for libice6:armhf ... Removing libicu48:armhf ... Purging configuration files for libicu48:armhf ... Removing libjasper1:armhf ... Purging configuration files for libjasper1:armhf ... Removing libtiff4:armhf ... Purging configuration files for libtiff4:armhf ... Removing libjbig0:armhf ... Purging configuration files for libjbig0:armhf ... Removing libjpeg8:armhf ... Removing libjs-jquery ... Removing libkrb5-3:armhf ... Purging configuration files for libkrb5-3:armhf ... Removing libk5crypto3:armhf ... Purging configuration files for libk5crypto3:armhf ... Removing libkrb5support0:armhf ... Purging configuration files for libkrb5support0:armhf ... Removing libkeyutils1:armhf ... Purging configuration files for libkeyutils1:armhf ... Removing libmagic1:armhf ... Purging configuration files for libmagic1:armhf ... Removing liborc-0.4-0:armhf ... Purging configuration files for liborc-0.4-0:armhf ... Removing libp11-kit0:armhf ... Purging configuration files for libp11-kit0:armhf ... Removing libpcre3-dev ... Removing libpcrecpp0:armhf ... Purging configuration files for libpcrecpp0:armhf ... Removing libpcre3:armhf ... Purging configuration files for libpcre3:armhf ... Removing libpipeline1:armhf ... Purging configuration files for libpipeline1:armhf ... Removing libpixman-1-dev ... Removing libpixman-1-0:armhf ... Purging configuration files for libpixman-1-0:armhf ... Removing libpng12-dev ... Removing libpng12-0:armhf ... Purging configuration files for libpng12-0:armhf ... Removing libpopt0:armhf ... Purging configuration files for libpopt0:armhf ... Removing libproxy0:armhf ... Purging configuration files for libproxy0:armhf ... Removing libxcb-shm0-dev:armhf ... Removing libxcb-render0-dev:armhf ... Removing libxres-dev ... Removing libxrandr-dev ... Removing libxcursor-dev:armhf ... Removing libxrender-dev:armhf ... Removing libxinerama-dev:armhf ... Removing libxi-dev ... Removing libxdamage-dev ... Removing libxcomposite-dev ... Removing libxfixes-dev ... Removing libxext-dev:armhf ... Removing libx11-dev:armhf ... Removing libxcb1-dev:armhf ... Removing libpthread-stubs0-dev:armhf ... Removing libpthread-stubs0:armhf ... Removing libsasl2-2:armhf ... Purging configuration files for libsasl2-2:armhf ... Removing libsqlite3-0:armhf ... Purging configuration files for libsqlite3-0:armhf ... Removing libssl-dev ... Removing python-minimal ... Removing python2.7-minimal ... Purging configuration files for python2.7-minimal ... Removing libstartup-notification0 ... Purging configuration files for libstartup-notification0 ... Removing libtasn1-3:armhf ... Purging configuration files for libtasn1-3:armhf ... Removing libthai-data ... Removing libunistring0:armhf ... Purging configuration files for libunistring0:armhf ... Removing libvte-common ... Removing libwebkitgtk-1.0-common ... Removing libwnck-common ... Removing libxxf86vm1:armhf ... Purging configuration files for libxxf86vm1:armhf ... Removing libxres1:armhf ... Purging configuration files for libxres1:armhf ... Removing libxrandr2:armhf ... Purging configuration files for libxrandr2:armhf ... Removing libxcursor1:armhf ... Purging configuration files for libxcursor1:armhf ... Removing libxrender1:armhf ... Purging configuration files for libxrender1:armhf ... Removing libxinerama1:armhf ... Purging configuration files for libxinerama1:armhf ... Removing libxi6:armhf ... Purging configuration files for libxi6:armhf ... Removing libxfixes3:armhf ... Purging configuration files for libxfixes3:armhf ... Removing libxext6:armhf ... Purging configuration files for libxext6:armhf ... Removing libxdamage1:armhf ... Purging configuration files for libxdamage1:armhf ... Removing libxcomposite1:armhf ... Purging configuration files for libxcomposite1:armhf ... Removing libx11-xcb1:armhf ... Purging configuration files for libx11-xcb1:armhf ... Removing libx11-6:armhf ... Purging configuration files for libx11-6:armhf ... Removing libx11-data ... Removing libxau-dev:armhf ... Removing libxcb-util0:armhf ... Purging configuration files for libxcb-util0:armhf ... Removing libxcb-shm0:armhf ... Purging configuration files for libxcb-shm0:armhf ... Removing libxcb-render0:armhf ... Purging configuration files for libxcb-render0:armhf ... Removing libxcb-glx0:armhf ... Purging configuration files for libxcb-glx0:armhf ... Removing libxcb1:armhf ... Purging configuration files for libxcb1:armhf ... Removing libxau6:armhf ... Purging configuration files for libxau6:armhf ... Removing libxdmcp-dev:armhf ... Removing libxdmcp6:armhf ... Purging configuration files for libxdmcp6:armhf ... Removing libxml2-utils ... Removing libxml2-dev:armhf ... Removing libxml2:armhf ... Purging configuration files for libxml2:armhf ... Removing m4 ... Removing mime-support ... Purging configuration files for mime-support ... Removing psmisc ... Purging configuration files for psmisc ... Removing sbuild-build-depends-core-dummy ... Removing ttf-dejavu-core ... Removing valac-0.16-vapi ... Removing x11-common ... All runlevel operations denied by policy invoke-rc.d: policy-rc.d denied execution of stop. Purging configuration files for x11-common ... Removing x11proto-composite-dev ... Removing x11proto-damage-dev ... Removing x11proto-fixes-dev ... Removing x11proto-xext-dev ... Removing x11proto-resource-dev ... Removing x11proto-render-dev ... Removing x11proto-input-dev ... Removing x11proto-core-dev ... Removing x11proto-kb-dev ... Removing x11proto-randr-dev ... Removing x11proto-xinerama-dev ... Removing xorg-sgml-doctools ... Removing xtrans-dev ... Removing zlib1g-dev:armhf ... Removing libwww-perl ... Removing liblwp-protocol-https-perl ... Removing ca-certificates ... Removing dangling symlinks from /etc/ssl/certs... done. Purging configuration files for ca-certificates ... Removing dangling symlinks from /etc/ssl/certs... done. Removing libhttp-negotiate-perl ... Removing libhttp-cookies-perl ... Removing libhttp-message-perl ... Removing libencode-locale-perl ... Removing libfile-listing-perl ... Removing libhtml-tree-perl ... Removing libhtml-parser-perl ... Removing libhtml-tagset-perl ... Removing libhttp-date-perl ... Removing libio-socket-ssl-perl ... Removing liblwp-mediatypes-perl ... Removing libnet-http-perl ... Removing libnet-ssleay-perl ... Removing openssl ... Purging configuration files for openssl ... Removing libssl1.0.0:armhf ... Purging configuration files for libssl1.0.0:armhf ... Removing libwww-robotrules-perl ... Removing liburi-perl ... Removing netbase ... Purging configuration files for netbase ... ┌──────────────────────────────────────────────────────────────────────────────┐ │ Summary │ └──────────────────────────────────────────────────────────────────────────────┘ Architecture: armhf Build-Space: 52620 Build-Time: 813 Distribution: testing Install-Time: 480 Job: awn-extras-applets_0.4.0-5 Package: awn-extras-applets Package-Time: 1359 Source-Version: 0.4.0-5 Space: 52620 Status: successful Version: 0.4.0-5 ──────────────────────────────────────────────────────────────────────────────── Finished at 20120624-0757 Build needed 00:22:39, 52620k disc space