sbuild (Debian sbuild) 0.63.1 (31 May 2012) on build02.raspbian.lan ╔══════════════════════════════════════════════════════════════════════════════╗ ║ foxtrotgps 1.1.1-2 (armhf) 10 Jul 2012 02:53 ║ ╚══════════════════════════════════════════════════════════════════════════════╝ Package: foxtrotgps Version: 1.1.1-2 Source Version: 1.1.1-2 Distribution: testing Machine Architecture: armhf Host Architecture: armhf Build Architecture: armhf W: line 7 [testing-armhf-sbuild]: Deprecated key ‘script-config’ used I: This option will be removed in the future; please update your configuration I: NOTICE: Log filtering will replace 'build/foxtrotgps-Sw5fU9/foxtrotgps-1.1.1' with '«PKGBUILDDIR»' I: NOTICE: Log filtering will replace 'build/foxtrotgps-Sw5fU9' with '«BUILDDIR»' I: NOTICE: Log filtering will replace 'var/lib/schroot/mount/testing-armhf-sbuild-3dd2ae18-5b2a-472a-aa08-8ef6b13b8cd3' with '«CHROOT»' ┌──────────────────────────────────────────────────────────────────────────────┐ │ Update chroot │ └──────────────────────────────────────────────────────────────────────────────┘ Hit http://repo.raspbian.lan testing InRelease Hit http://repo.raspbian.lan testing/main Sources Hit http://repo.raspbian.lan testing/main armhf Packages Ign http://repo.raspbian.lan testing/main Translation-en 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... Need to get 387 kB of source archives. Get:1 http://repo.raspbian.lan/raspbian/ testing/main foxtrotgps 1.1.1-2 (dsc) [1367 B] Get:2 http://repo.raspbian.lan/raspbian/ testing/main foxtrotgps 1.1.1-2 (tar) [379 kB] Get:3 http://repo.raspbian.lan/raspbian/ testing/main foxtrotgps 1.1.1-2 (diff) [6832 B] Fetched 387 kB in 0s (2023 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-JzrFbb/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 4 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 ... 10635 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 (>= 9), autotools-dev, intltool, libbluetooth-dev, libcurl4-gnutls-dev, libexif-dev, libgconf2-dev, libglade2-dev, libgps-dev, libgtk2.0-dev, libsoup2.4-dev, libsqlite3-dev, libxml2-dev Filtered Build-Depends: libc6-dev, gcc (>= 4:4.4.3), g++ (>= 4:4.4.3), make, dpkg-dev (>= 1.13.5), debhelper (>= 9), autotools-dev, intltool, libbluetooth-dev, libcurl4-gnutls-dev, libexif-dev, libgconf2-dev, libglade2-dev, libgps-dev, libgtk2.0-dev, libsoup2.4-dev, libsqlite3-dev, libxml2-dev dpkg-deb: building package `sbuild-build-depends-foxtrotgps-dummy' in `/«BUILDDIR»/resolver-d6vrM2/apt_archive/sbuild-build-depends-foxtrotgps-dummy.deb'. OK Reading package lists... ┌──────────────────────────────────────────────────────────────────────────────┐ │ Install foxtrotgps 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 autoconf automake autotools-dev bsdmainutils ca-certificates comerr-dev dbus dbus-x11 dconf-gsettings-backend dconf-service debhelper 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-pango-1.0 gir1.2-soup-2.4 glib-networking glib-networking-common glib-networking-services groff-base gsettings-desktop-schemas html2text intltool intltool-debian krb5-multidev libasprintf0c2 libatk1.0-0 libatk1.0-data libatk1.0-dev libavahi-client3 libavahi-common-data libavahi-common3 libbluetooth-dev libbluetooth3 libcairo-gobject2 libcairo-script-interpreter2 libcairo2 libcairo2-dev libcap2 libcroco3 libcups2 libcurl3-gnutls libcurl4-gnutls-dev libdatrie1 libdbus-1-3 libdbus-1-dev libdbus-glib-1-2 libdconf0 libelf1 libencode-locale-perl libexif-dev libexif12 libexpat1 libexpat1-dev libffi5 libfile-listing-perl libfontconfig1 libfontconfig1-dev libfreetype6 libfreetype6-dev libgconf-2-4 libgconf2-dev libgcrypt11 libgcrypt11-dev libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-common libgdk-pixbuf2.0-dev libgettextpo0 libgirepository-1.0-1 libglade2-0 libglade2-dev libglib2.0-0 libglib2.0-bin libglib2.0-data libglib2.0-dev libgnome-keyring-common libgnome-keyring0 libgnutls-dev libgnutls-openssl27 libgnutls26 libgnutlsxx27 libgpg-error-dev libgpg-error0 libgps-dev libgps20 libgssapi-krb5-2 libgssrpc4 libgtk2.0-0 libgtk2.0-common libgtk2.0-dev libhtml-parser-perl libhtml-tagset-perl libhtml-tree-perl libhttp-cookies-perl libhttp-date-perl libhttp-message-perl libhttp-negotiate-perl libice-dev libice6 libidn11 libidn11-dev libio-socket-ssl-perl libjasper1 libjbig0 libjpeg8 libjs-jquery libk5crypto3 libkadm5clnt-mit8 libkadm5srv-mit8 libkdb5-6 libkeyutils1 libkrb5-3 libkrb5-dev libkrb5support0 libldap-2.4-2 libldap2-dev liblwp-mediatypes-perl liblwp-protocol-https-perl libmagic1 libnet-http-perl libnet-ssleay-perl libp11-kit-dev 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 librtmp-dev librtmp0 libsasl2-2 libsm-dev libsm6 libsoup-gnome2.4-1 libsoup2.4-1 libsoup2.4-dev libsqlite3-0 libsqlite3-dev libssh2-1 libssh2-1-dev libssl1.0.0 libsystemd-login0 libtasn1-3 libtasn1-3-dev libthai-data libthai0 libtiff4 libunistring0 liburi-perl libusb-1.0-0 libwww-perl libwww-robotrules-perl libx11-6 libx11-data libx11-dev libxau-dev libxau6 libxcb-render0 libxcb-render0-dev libxcb-shm0 libxcb-shm0-dev libxcb1 libxcb1-dev libxcomposite-dev libxcomposite1 libxcursor-dev libxcursor1 libxdamage-dev libxdamage1 libxdmcp-dev libxdmcp6 libxext-dev libxext6 libxfixes-dev libxfixes3 libxft-dev libxft2 libxi-dev libxi6 libxinerama-dev libxinerama1 libxml-parser-perl libxml2 libxml2-dev libxml2-utils libxrandr-dev libxrandr2 libxrender-dev libxrender1 m4 man-db mime-support netbase openssl pkg-config po-debconf psmisc python python-minimal python2.7 python2.7-minimal shared-mime-info ttf-dejavu-core 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-xext-dev x11proto-xinerama-dev xorg-sgml-doctools xtrans-dev zlib1g-dev Suggested packages: autoconf2.13 autoconf-archive gnu-standards autoconf-doc libtool wamerican wordlist whois vacation doc-base dh-make gconf-defaults-service gettext-doc groff krb5-doc libcairo2-doc cups-common libcurl3-dbg rng-tools libgcrypt11-doc glade glade-gnome libglib2.0-doc gnome-keyring gnutls-doc gpsd krb5-user librsvg2-common 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 libsm-doc libsoup2.4-doc sqlite3-doc libauthen-ntlm-perl libxcb-doc libxext-doc less www-browser libmail-box-perl python-doc python-tk python2.7-doc binfmt-support Recommended packages: curl wget lynx-cur autopoint libgconf2-doc hicolor-icon-theme libgtk2.0-bin libio-socket-ip-perl libio-socket-inet6-perl javascript-common krb5-locales libwebkitgtk-1.0-0 libmozjs10d libsasl2-modules libhtml-form-perl libhtml-format-perl libhttp-daemon-perl libmailtools-perl libx11-doc xml-core ifupdown libmail-sendmail-perl The following NEW packages will be installed: adduser autoconf automake autotools-dev bsdmainutils ca-certificates comerr-dev dbus dbus-x11 dconf-gsettings-backend dconf-service debhelper 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-pango-1.0 gir1.2-soup-2.4 glib-networking glib-networking-common glib-networking-services groff-base gsettings-desktop-schemas html2text intltool intltool-debian krb5-multidev libasprintf0c2 libatk1.0-0 libatk1.0-data libatk1.0-dev libavahi-client3 libavahi-common-data libavahi-common3 libbluetooth-dev libbluetooth3 libcairo-gobject2 libcairo-script-interpreter2 libcairo2 libcairo2-dev libcap2 libcroco3 libcups2 libcurl3-gnutls libcurl4-gnutls-dev libdatrie1 libdbus-1-3 libdbus-1-dev libdbus-glib-1-2 libdconf0 libelf1 libencode-locale-perl libexif-dev libexif12 libexpat1 libexpat1-dev libffi5 libfile-listing-perl libfontconfig1 libfontconfig1-dev libfreetype6 libfreetype6-dev libgconf-2-4 libgconf2-dev libgcrypt11 libgcrypt11-dev libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-common libgdk-pixbuf2.0-dev libgettextpo0 libgirepository-1.0-1 libglade2-0 libglade2-dev libglib2.0-0 libglib2.0-bin libglib2.0-data libglib2.0-dev libgnome-keyring-common libgnome-keyring0 libgnutls-dev libgnutls-openssl27 libgnutls26 libgnutlsxx27 libgpg-error-dev libgpg-error0 libgps-dev libgps20 libgssapi-krb5-2 libgssrpc4 libgtk2.0-0 libgtk2.0-common libgtk2.0-dev libhtml-parser-perl libhtml-tagset-perl libhtml-tree-perl libhttp-cookies-perl libhttp-date-perl libhttp-message-perl libhttp-negotiate-perl libice-dev libice6 libidn11 libidn11-dev libio-socket-ssl-perl libjasper1 libjbig0 libjpeg8 libjs-jquery libk5crypto3 libkadm5clnt-mit8 libkadm5srv-mit8 libkdb5-6 libkeyutils1 libkrb5-3 libkrb5-dev libkrb5support0 libldap-2.4-2 libldap2-dev liblwp-mediatypes-perl liblwp-protocol-https-perl libmagic1 libnet-http-perl libnet-ssleay-perl libp11-kit-dev 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 librtmp-dev librtmp0 libsasl2-2 libsm-dev libsm6 libsoup-gnome2.4-1 libsoup2.4-1 libsoup2.4-dev libsqlite3-0 libsqlite3-dev libssh2-1 libssh2-1-dev libssl1.0.0 libsystemd-login0 libtasn1-3 libtasn1-3-dev libthai-data libthai0 libtiff4 libunistring0 liburi-perl libusb-1.0-0 libwww-perl libwww-robotrules-perl libx11-6 libx11-data libx11-dev libxau-dev libxau6 libxcb-render0 libxcb-render0-dev libxcb-shm0 libxcb-shm0-dev libxcb1 libxcb1-dev libxcomposite-dev libxcomposite1 libxcursor-dev libxcursor1 libxdamage-dev libxdamage1 libxdmcp-dev libxdmcp6 libxext-dev libxext6 libxfixes-dev libxfixes3 libxft-dev libxft2 libxi-dev libxi6 libxinerama-dev libxinerama1 libxml-parser-perl libxml2 libxml2-dev libxml2-utils libxrandr-dev libxrandr2 libxrender-dev libxrender1 m4 man-db mime-support netbase openssl pkg-config po-debconf psmisc python python-minimal python2.7 python2.7-minimal sbuild-build-depends-foxtrotgps-dummy shared-mime-info ttf-dejavu-core 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-xext-dev x11proto-xinerama-dev xorg-sgml-doctools xtrans-dev zlib1g-dev 0 upgraded, 238 newly installed, 0 to remove and 4 not upgraded. Need to get 1033 kB/77.1 MB of archives. After this operation, 210 MB of additional disk space will be used. Get:1 http://repo.raspbian.lan/raspbian/ testing/main libusb-1.0-0 armhf 2:1.0.11-1 [36.7 kB] Get:2 http://repo.raspbian.lan/raspbian/ testing/main libgps20 armhf 3.6-3 [233 kB] Get:3 http://repo.raspbian.lan/raspbian/ testing/main libexif-dev armhf 0.6.20-2 [407 kB] Get:4 http://repo.raspbian.lan/raspbian/ testing/main libglade2-0 armhf 1:2.6.4-1 [85.3 kB] Get:5 http://repo.raspbian.lan/raspbian/ testing/main libglade2-dev armhf 1:2.6.4-1 [132 kB] Get:6 http://repo.raspbian.lan/raspbian/ testing/main libgps-dev armhf 3.6-3 [138 kB] debconf: delaying package configuration, since apt-utils is not installed Fetched 1033 kB in 0s (3025 kB/s) Selecting previously unselected package libpcre3:armhf. (Reading database ... 10635 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 libgnutls-openssl27:armhf. Unpacking libgnutls-openssl27:armhf (from .../libgnutls-openssl27_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 libgssrpc4:armhf. Unpacking libgssrpc4:armhf (from .../libgssrpc4_1.10.1+dfsg-1_armhf.deb) ... Selecting previously unselected package libidn11:armhf. Unpacking libidn11:armhf (from .../libidn11_1.25-2_armhf.deb) ... Selecting previously unselected package libkadm5clnt-mit8:armhf. Unpacking libkadm5clnt-mit8:armhf (from .../libkadm5clnt-mit8_1.10.1+dfsg-1_armhf.deb) ... Selecting previously unselected package libkdb5-6:armhf. Unpacking libkdb5-6:armhf (from .../libkdb5-6_1.10.1+dfsg-1_armhf.deb) ... Selecting previously unselected package libkadm5srv-mit8:armhf. Unpacking libkadm5srv-mit8:armhf (from .../libkadm5srv-mit8_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-4_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 libbluetooth3:armhf. Unpacking libbluetooth3:armhf (from .../libbluetooth3_4.99-2_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.26.0-3_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-2_armhf.deb) ... Selecting previously unselected package libcairo-gobject2:armhf. Unpacking libcairo-gobject2:armhf (from .../libcairo-gobject2_1.12.2-2_armhf.deb) ... Selecting previously unselected package libcairo-script-interpreter2:armhf. Unpacking libcairo-script-interpreter2:armhf (from .../libcairo-script-interpreter2_1.12.2-2_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 librtmp0:armhf. Unpacking librtmp0:armhf (from .../librtmp0_2.4+20111222.git4e06e21-1_armhf.deb) ... Selecting previously unselected package libssh2-1:armhf. Unpacking libssh2-1:armhf (from .../libssh2-1_1.4.2-1_armhf.deb) ... Selecting previously unselected package libcurl3-gnutls:armhf. Unpacking libcurl3-gnutls:armhf (from .../libcurl3-gnutls_7.26.0-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.100-1_armhf.deb) ... Selecting previously unselected package libdconf0:armhf. Unpacking libdconf0:armhf (from .../libdconf0_0.12.1-2_armhf.deb) ... Selecting previously unselected package libexif12:armhf. Unpacking libexif12:armhf (from .../libexif12_0.6.20-2_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 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-6_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 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 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 libusb-1.0-0:armhf. Unpacking libusb-1.0-0:armhf (from .../libusb-1.0-0_2%3a1.0.11-1_armhf.deb) ... Selecting previously unselected package libgps20:armhf. Unpacking libgps20:armhf (from .../libgps20_3.6-3_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 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.3.1-1_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 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 x11-common. Unpacking x11-common (from .../x11-common_1%3a7.7+1_all.deb) ... Selecting previously unselected package libice6:armhf. Unpacking libice6:armhf (from .../libice6_2%3a1.0.8-2_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 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-2_armhf.deb) ... Selecting previously unselected package dconf-gsettings-backend:armhf. Unpacking dconf-gsettings-backend:armhf (from .../dconf-gsettings-backend_0.12.1-2_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 libgnutlsxx27:armhf. Unpacking libgnutlsxx27:armhf (from .../libgnutlsxx27_2.12.20-1_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-9_armhf.deb) ... Selecting previously unselected package man-db. Unpacking man-db (from .../man-db_2.6.2-1_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 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_20120623_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.19-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-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 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.76-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 comerr-dev. Unpacking comerr-dev (from .../comerr-dev_2.1-1.42.4-3_armhf.deb) ... Selecting previously unselected package krb5-multidev. Unpacking krb5-multidev (from .../krb5-multidev_1.10.1+dfsg-1_armhf.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 libexpat1-dev. Unpacking libexpat1-dev (from .../libexpat1-dev_2.1.0-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 libfontconfig1-dev. Unpacking libfontconfig1-dev (from .../libfontconfig1-dev_2.9.0-6_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-2_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 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 libpng12-dev. Unpacking libpng12-dev (from .../libpng12-dev_1.2.49-1_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.26.0-3_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-2_armhf.deb) ... Selecting previously unselected package libgpg-error-dev. Unpacking libgpg-error-dev (from .../libgpg-error-dev_1.10-3_armhf.deb) ... Selecting previously unselected package libgcrypt11-dev. Unpacking libgcrypt11-dev (from .../libgcrypt11-dev_1.5.0-3_armhf.deb) ... Selecting previously unselected package libtasn1-3-dev. Unpacking libtasn1-3-dev (from .../libtasn1-3-dev_2.13-2_armhf.deb) ... Selecting previously unselected package libp11-kit-dev. Unpacking libp11-kit-dev (from .../libp11-kit-dev_0.12-3_armhf.deb) ... Selecting previously unselected package libgnutls-dev. Unpacking libgnutls-dev (from .../libgnutls-dev_2.12.20-1_armhf.deb) ... Selecting previously unselected package libidn11-dev. Unpacking libidn11-dev (from .../libidn11-dev_1.25-2_armhf.deb) ... Selecting previously unselected package libkrb5-dev. Unpacking libkrb5-dev (from .../libkrb5-dev_1.10.1+dfsg-1_armhf.deb) ... Selecting previously unselected package libldap2-dev:armhf. Unpacking libldap2-dev:armhf (from .../libldap2-dev_2.4.28-1.1+rpi1_armhf.deb) ... Selecting previously unselected package librtmp-dev. Unpacking librtmp-dev (from .../librtmp-dev_2.4+20111222.git4e06e21-1_armhf.deb) ... Selecting previously unselected package libssh2-1-dev. Unpacking libssh2-1-dev (from .../libssh2-1-dev_1.4.2-1_armhf.deb) ... Selecting previously unselected package libcurl4-gnutls-dev. Unpacking libcurl4-gnutls-dev (from .../libcurl4-gnutls-dev_7.26.0-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 libjs-jquery. Unpacking libjs-jquery (from .../libjs-jquery_1.7.2+debian-2_all.deb) ... Selecting previously unselected package libexif-dev. Unpacking libexif-dev (from .../libexif-dev_0.6.20-2_armhf.deb) ... Selecting previously unselected package libgconf2-dev. Unpacking libgconf2-dev (from .../libgconf2-dev_3.2.5-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 libglade2-0. Unpacking libglade2-0 (from .../libglade2-0_1%3a2.6.4-1_armhf.deb) ... Selecting previously unselected package libxft-dev. Unpacking libxft-dev (from .../libxft-dev_2.3.1-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-4_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 libxml2-dev:armhf. Unpacking libxml2-dev:armhf (from .../libxml2-dev_2.8.0+dfsg1-4_armhf.deb) ... Selecting previously unselected package libglade2-dev. Unpacking libglade2-dev (from .../libglade2-dev_1%3a2.6.4-1_armhf.deb) ... Selecting previously unselected package libgps-dev. Unpacking libgps-dev (from .../libgps-dev_3.6-3_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 libsqlite3-dev. Unpacking libsqlite3-dev (from .../libsqlite3-dev_3.7.13-1_armhf.deb) ... Selecting previously unselected package libbluetooth-dev. Unpacking libbluetooth-dev (from .../libbluetooth-dev_4.99-2_armhf.deb) ... Selecting previously unselected package sbuild-build-depends-foxtrotgps-dummy. Unpacking sbuild-build-depends-foxtrotgps-dummy (from .../sbuild-build-depends-foxtrotgps-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 libgnutls-openssl27: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 libgssrpc4:armhf (1.10.1+dfsg-1) ... Setting up libidn11:armhf (1.25-2) ... Setting up libkadm5clnt-mit8:armhf (1.10.1+dfsg-1) ... Setting up libkdb5-6:armhf (1.10.1+dfsg-1) ... Setting up libkadm5srv-mit8: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-4) ... 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 libbluetooth3:armhf (4.99-2) ... 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.26.0-3) ... 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-2) ... Setting up libcairo-gobject2:armhf (1.12.2-2) ... Setting up libcairo-script-interpreter2:armhf (1.12.2-2) ... Setting up libcroco3:armhf (0.6.5-1) ... Setting up libcups2:armhf (1.5.3-1) ... Setting up librtmp0:armhf (2.4+20111222.git4e06e21-1) ... Setting up libssh2-1:armhf (1.4.2-1) ... Setting up libcurl3-gnutls:armhf (7.26.0-1) ... Setting up libdatrie1:armhf (0.2.5-3) ... Setting up libdbus-glib-1-2:armhf (0.100-1) ... Setting up libdconf0:armhf (0.12.1-2) ... Setting up libexif12:armhf (0.6.20-2) ... 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 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-6) ... Setting up libgdk-pixbuf2.0-common (2.26.1-1) ... Setting up libgdk-pixbuf2.0-0:armhf (2.26.1-1) ... Setting up libunistring0:armhf (0.9.3-5) ... Setting up libgettextpo0:armhf (0.18.1.1-9) ... Setting up libgnome-keyring-common (3.4.1-1) ... Setting up libgnome-keyring0:armhf (3.4.1-1) ... Setting up libusb-1.0-0:armhf (2:1.0.11-1) ... Setting up libgps20:armhf (3.6-3) ... Setting up libgtk2.0-common (2.24.10-1) ... Setting up libthai-data (0.1.18-1) ... Setting up libthai0:armhf (0.1.18-1) ... Setting up libxft2:armhf (2.3.1-1) ... 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 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 x11-common (1:7.7+1) ... 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 libpcrecpp0:armhf (1:8.30-5) ... Setting up libproxy0:armhf (0.3.1-5) ... 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-2) ... Setting up dconf-gsettings-backend:armhf (0.12.1-2) ... 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 libgnutlsxx27:armhf (2.12.20-1) ... 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-9) ... Setting up man-db (2.6.2-1) ... 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 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 (20120623) ... 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.19-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-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.76-1) ... Setting up libnet-http-perl (6.03-2) ... Setting up libwww-robotrules-perl (6.01-1) ... Setting up comerr-dev (2.1-1.42.4-3) ... Setting up krb5-multidev (1.10.1+dfsg-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 libexpat1-dev (2.1.0-1) ... Setting up libfreetype6-dev (2.4.9-1) ... Setting up libfontconfig1-dev (2.9.0-6) ... 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-2) ... 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 x11proto-render-dev (2:0.11.1-2) ... Setting up libxrender-dev:armhf (1:0.9.7-1) ... Setting up libpng12-dev (1.2.49-1) ... 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.26.0-3) ... 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-2) ... Setting up libgpg-error-dev (1.10-3) ... Setting up libgcrypt11-dev (1.5.0-3) ... Setting up libtasn1-3-dev (2.13-2) ... Setting up libp11-kit-dev (0.12-3) ... Setting up libgnutls-dev (2.12.20-1) ... Setting up libidn11-dev (1.25-2) ... Setting up libkrb5-dev (1.10.1+dfsg-1) ... Setting up libldap2-dev:armhf (2.4.28-1.1+rpi1) ... Setting up librtmp-dev (2.4+20111222.git4e06e21-1) ... Setting up libssh2-1-dev (1.4.2-1) ... Setting up libcurl4-gnutls-dev (7.26.0-1) ... Setting up libdbus-1-dev (1.6.0-1) ... Setting up libjs-jquery (1.7.2+debian-2) ... Setting up libexif-dev (0.6.20-2) ... Setting up libgconf2-dev (3.2.5-1) ... Setting up libgdk-pixbuf2.0-dev (2.26.1-1) ... Setting up libglade2-0 (1:2.6.4-1) ... Setting up libxft-dev (2.3.1-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-4) ... Setting up libgtk2.0-dev (2.24.10-1) ... Setting up libxml2-dev:armhf (2.8.0+dfsg1-4) ... Setting up libglade2-dev (1:2.6.4-1) ... Setting up libgps-dev (3.6-3) ... Setting up libsoup2.4-dev (2.38.1-2) ... Setting up libsqlite3-dev (3.7.13-1) ... Setting up libbluetooth-dev (4.99-2) ... 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-foxtrotgps-dummy (0.invalid.0) ... ┌──────────────────────────────────────────────────────────────────────────────┐ │ Build environment │ └──────────────────────────────────────────────────────────────────────────────┘ Kernel: Linux 3.2.0-2-mx5 armhf (armv7l) Toolchain package versions: binutils_2.22-6.1 dpkg-dev_1.16.4.3 g++-4.6_4.6.3-8+rpi1 gcc-4.6_4.6.3-8+rpi1 libc6-dev_2.13-33 libstdc++6_4.7.1-2+rpi1 libstdc++6-4.6-dev_4.6.3-8+rpi1 linux-libc-dev_3.2.21-1+rpi1 Package versions: adduser_3.113+nmu3 apt_0.9.3+rpi1 autoconf_2.69-1 automake_1:1.11.5-2 autotools-dev_20120608.1 base-files_6.9 base-passwd_3.5.26 bash_4.2-2 binutils_2.22-6.1 bsdmainutils_9.0.3 bsdutils_1:2.20.1-5.1 build-essential_11.5+b1 bzip2_1.0.6-3 ca-certificates_20120623 comerr-dev_2.1-1.42.4-3 coreutils_8.13-3.2 cpp_4:4.6.3-7 cpp-4.6_4.6.3-8+rpi1 dash_0.5.7-3 dbus_1.6.0-1 dbus-x11_1.6.0-1 dconf-gsettings-backend_0.12.1-2 dconf-service_0.12.1-2 debconf_1.5.44 debfoster_2.7-1.1 debhelper_9.20120608 debian-archive-keyring_2012.3 debianutils_4.3.1 diffutils_1:3.2-6 dpkg_1.16.4.3 dpkg-dev_1.16.4.3 e2fslibs_1.42.4-3 e2fsprogs_1.42.4-3 fakeroot_1.18.4-2 file_5.11-1 findutils_4.4.2-4 fontconfig_2.9.0-6 fontconfig-config_2.9.0-6 g++_4:4.6.3-6 g++-4.6_4.6.3-8+rpi1 gcc_4:4.6.3-7 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-8+rpi1 gcc-4.6-base_4.6.3-8+rpi1 gcc-4.7-base_4.7.1-2+rpi1 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-pango-1.0_1.30.0-1 gir1.2-soup-2.4_2.38.1-2 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-9 gsettings-desktop-schemas_3.4.2-1 gzip_1.5-1.1 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 krb5-multidev_1.10.1+dfsg-1 libacl1_2.2.51-8 libapt-pkg4.12_0.9.3+rpi1 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-8 libavahi-client3_0.6.31-1 libavahi-common-data_0.6.31-1 libavahi-common3_0.6.31-1 libblkid1_2.20.1-5.1 libbluetooth-dev_4.99-2 libbluetooth3_4.99-2 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-2 libcairo-script-interpreter2_1.12.2-2 libcairo2_1.12.2-2 libcairo2-dev_1.12.2-2 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 libcurl3-gnutls_7.26.0-1 libcurl4-gnutls-dev_7.26.0-1 libdatrie1_0.2.5-3 libdb5.1_5.1.29-4 libdbus-1-3_1.6.0-1 libdbus-1-dev_1.6.0-1 libdbus-glib-1-2_0.100-1 libdconf0_0.12.1-2 libdpkg-perl_1.16.4.3 libelf1_0.152-1+rpi1 libencode-locale-perl_1.03-1 libexif-dev_0.6.20-2 libexif12_0.6.20-2 libexpat1_2.1.0-1 libexpat1-dev_2.1.0-1 libffi5_3.0.10-3+b3 libfile-fcntllock-perl_0.14-2 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 libgc1c2_1:7.1-8 libgcc1_1:4.7.1-2+rpi1 libgconf-2-4_3.2.5-1 libgconf2-dev_3.2.5-1 libgcrypt11_1.5.0-3 libgcrypt11-dev_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 libgettextpo0_0.18.1.1-9 libgirepository-1.0-1_1.32.1-1 libglade2-0_1:2.6.4-1 libglade2-dev_1:2.6.4-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 libgnutls-dev_2.12.20-1 libgnutls-openssl27_2.12.20-1 libgnutls26_2.12.20-1 libgnutlsxx27_2.12.20-1 libgomp1_4.7.1-2+rpi1 libgpg-error-dev_1.10-3 libgpg-error0_1.10-3 libgps-dev_3.6-3 libgps20_3.6-3 libgssapi-krb5-2_1.10.1+dfsg-1 libgssrpc4_1.10.1+dfsg-1 libgtk2.0-0_2.24.10-1 libgtk2.0-common_2.24.10-1 libgtk2.0-dev_2.24.10-1 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 libice-dev_2:1.0.8-2 libice6_2:1.0.8-2 libidn11_1.25-2 libidn11-dev_1.25-2 libio-socket-ssl-perl_1.76-1 libjasper1_1.900.1-13 libjbig0_2.0-2 libjpeg8_8d-1 libjs-jquery_1.7.2+debian-2 libk5crypto3_1.10.1+dfsg-1 libkadm5clnt-mit8_1.10.1+dfsg-1 libkadm5srv-mit8_1.10.1+dfsg-1 libkdb5-6_1.10.1+dfsg-1 libkeyutils1_1.5.5-2 libkrb5-3_1.10.1+dfsg-1 libkrb5-dev_1.10.1+dfsg-1 libkrb5support0_1.10.1+dfsg-1 libldap-2.4-2_2.4.28-1.1+rpi1 libldap2-dev_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+20120614-1 libmagic1_5.11-1 libmount1_2.20.1-5.1 libmpc2_0.9-4 libmpfr4_3.1.0-5 libncurses5_5.9-10 libncursesw5_5.9-10 libnet-http-perl_6.03-2 libnet-ssleay-perl_1.48-1 libp11-kit-dev_0.12-3 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.26.0-3 libpixman-1-dev_0.26.0-3 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 libreadline6_6.2-8 librtmp-dev_2.4+20111222.git4e06e21-1 librtmp0_2.4+20111222.git4e06e21-1 libsasl2-2_2.1.25.dfsg1-4 libselinux1_2.1.9-5 libsemanage-common_2.1.6-6 libsemanage1_2.1.6-6 libsepol1_2.1.4-3 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 libsqlite3-dev_3.7.13-1 libss2_1.42.4-3 libssh2-1_1.4.2-1 libssh2-1-dev_1.4.2-1 libssl1.0.0_1.0.1c-3+rpi1 libstdc++6_4.7.1-2+rpi1 libstdc++6-4.6-dev_4.6.3-8+rpi1 libswitch-perl_2.16-2 libsystemd-login0_44-2 libtasn1-3_2.13-2 libtasn1-3-dev_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-6 libtimedate-perl_1.2000-1 libtinfo5_5.9-10 libunistring0_0.9.3-5 liburi-perl_1.60-1 libusb-0.1-4_2:0.1.12-20 libusb-1.0-0_2:1.0.11-1 libustr-1.0-1_1.0.4-3 libuuid1_2.20.1-5.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 libxau-dev_1:1.0.7-1 libxau6_1:1.0.7-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 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.3.1-1 libxft2_2.3.1-1 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-4 libxml2-dev_2.8.0+dfsg1-4 libxml2-utils_2.8.0+dfsg1-4 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 linux-libc-dev_3.2.21-1+rpi1 login_1:4.1.5.1-1 lsb-base_4.1+Debian7 m4_1.4.16-3 make_3.81-8.2 man-db_2.6.2-1 mawk_1.3.3-17 mime-support_3.52-1 mount_2.20.1-5.1 multiarch-support_2.13-33 ncurses-base_5.9-9 ncurses-bin_5.9-10 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-12+rpi1 perl-base_5.14.2-12+rpi1 perl-modules_5.14.2-12+rpi1 pkg-config_0.26-1 po-debconf_1.0.16+nmu2 psmisc_22.19-1 python_2.7.3~rc2-1 python-minimal_2.7.3~rc2-1 python2.7_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-core-dummy_0.invalid.0 sbuild-build-depends-foxtrotgps-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.1 x11-common_1:7.7+1 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-2 x11proto-randr-dev_1.3.2-2 x11proto-render-dev_2:0.11.1-2 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+20120614-1 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 Fri Jun 29 14:48:13 2012 UTC using DSA key ID 4B2B2B9E gpgv: Can't check signature: public key not found dpkg-source: warning: failed to verify signature on ./foxtrotgps_1.1.1-2.dsc dpkg-source: info: extracting foxtrotgps in foxtrotgps-1.1.1 dpkg-source: info: unpacking foxtrotgps_1.1.1.orig.tar.xz dpkg-source: info: unpacking foxtrotgps_1.1.1-2.debian.tar.xz 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_ALIAS_NAME=chroot:testing-armhf-sbuild SCHROOT_CHROOT_NAME=testing-armhf-sbuild SCHROOT_COMMAND=env SCHROOT_GID=108 SCHROOT_GROUP=buildd SCHROOT_SESSION_ID=testing-armhf-sbuild-3dd2ae18-5b2a-472a-aa08-8ef6b13b8cd3 SCHROOT_UID=106 SCHROOT_USER=buildd SHELL=/bin/sh TERM=xterm USER=buildd dpkg-buildpackage ───────────────── dpkg-buildpackage: source package foxtrotgps dpkg-buildpackage: source version 1.1.1-2 dpkg-source --before-build foxtrotgps-1.1.1 dpkg-buildpackage: host architecture armhf dpkg-source: info: using options from foxtrotgps-1.1.1/debian/source/options: --compression=xz --compression-level=9 fakeroot debian/rules clean dh clean --with autotools_dev dh_testdir dh_auto_clean dh_autotools-dev_restoreconfig dh_clean debian/rules build-arch dh build-arch --with autotools_dev dh_testdir -a dh_autotools-dev_updateconfig -a dh_auto_configure -a 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 whether to enable maintainer-specific portions of Makefiles... no checking for style of include used by make... GNU checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no 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 option to accept ISO C99... -std=gnu99 checking how to run the C preprocessor... gcc -std=gnu99 -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 whether NLS is requested... yes checking for intltool >= 0.23... 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 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 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... bg cs de es fi fr hu ru sk nl ja sr 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 -std=gnu99... /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 -std=gnu99 object... ok checking for dlfcn.h... yes checking for objdir... .libs checking if gcc -std=gnu99 supports -fno-rtti -fno-exceptions... no checking for gcc -std=gnu99 option to produce PIC... -fPIC -DPIC checking if gcc -std=gnu99 PIC flag -fPIC -DPIC works... yes checking if gcc -std=gnu99 static flag -static works... yes checking if gcc -std=gnu99 supports -c -o file.o... yes checking if gcc -std=gnu99 supports -c -o file.o... (cached) yes checking whether the gcc -std=gnu99 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 pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for GTK... yes checking for GLADE... yes checking for GCONF... yes checking for LIBCURL... yes checking for SQLITE... yes checking for LIBEXIF... yes checking for LIBXML... yes checking for LIBGPS... yes checking for BLUETOOTH... yes checking for gconftool-2... /usr/bin/gconftool-2 Using config source xml:merged:/etc/gconf/gconf.xml.defaults for schema installation Using $(sysconfdir)/gconf/schemas as install directory for schema files configure: creating ./config.status config.status: creating Makefile config.status: creating po/Makefile.in config.status: creating src/Makefile config.status: creating pixmaps/Makefile config.status: creating data/Makefile config.status: creating doc/Makefile config.status: creating contrib/Makefile config.status: creating config.h config.status: executing depfiles commands config.status: executing default-1 commands config.status: executing libtool commands config.status: executing po/stamp-it commands dh_auto_build -a make[1]: Entering directory `/«PKGBUILDDIR»' make all-recursive make[2]: Entering directory `/«PKGBUILDDIR»' Making all in po make[3]: Entering directory `/«PKGBUILDDIR»/po' file=`echo bg | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file bg.po file=`echo cs | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file cs.po file=`echo de | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file de.po file=`echo es | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file es.po file=`echo fi | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file fi.po file=`echo fr | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file fr.po file=`echo hu | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file hu.po file=`echo ru | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file ru.po file=`echo sk | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file sk.po file=`echo nl | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file nl.po file=`echo ja | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file ja.po file=`echo sr | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file sr.po make[3]: Leaving directory `/«PKGBUILDDIR»/po' Making all in src make[3]: Entering directory `/«PKGBUILDDIR»/src' gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -DPACKAGE_DATA_DIR="\"/usr/share\"" -DPACKAGE_PIXMAPS_DIR="\"/usr/share/pixmaps\"" -DPACKAGE_LOCALE_DIR="\"/usr/share/locale\"" -pthread -I/usr/include/gtk-2.0 -I/usr/lib/arm-linux-gnueabihf/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gtk-2.0 -I/usr/include/libxml2 -I/usr/lib/arm-linux-gnueabihf/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/libglade-2.0 -pthread -I/usr/include/gconf/2 -I/usr/include/dbus-1.0 -I/usr/lib/arm-linux-gnueabihf/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libexif -I/usr/include/libxml2 -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c support.c gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -DPACKAGE_DATA_DIR="\"/usr/share\"" -DPACKAGE_PIXMAPS_DIR="\"/usr/share/pixmaps\"" -DPACKAGE_LOCALE_DIR="\"/usr/share/locale\"" -pthread -I/usr/include/gtk-2.0 -I/usr/lib/arm-linux-gnueabihf/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gtk-2.0 -I/usr/include/libxml2 -I/usr/lib/arm-linux-gnueabihf/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/libglade-2.0 -pthread -I/usr/include/gconf/2 -I/usr/include/dbus-1.0 -I/usr/lib/arm-linux-gnueabihf/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libexif -I/usr/include/libxml2 -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c main.c gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -DPACKAGE_DATA_DIR="\"/usr/share\"" -DPACKAGE_PIXMAPS_DIR="\"/usr/share/pixmaps\"" -DPACKAGE_LOCALE_DIR="\"/usr/share/locale\"" -pthread -I/usr/include/gtk-2.0 -I/usr/lib/arm-linux-gnueabihf/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gtk-2.0 -I/usr/include/libxml2 -I/usr/lib/arm-linux-gnueabihf/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/libglade-2.0 -pthread -I/usr/include/gconf/2 -I/usr/include/dbus-1.0 -I/usr/lib/arm-linux-gnueabihf/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libexif -I/usr/include/libxml2 -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c interface.c gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -DPACKAGE_DATA_DIR="\"/usr/share\"" -DPACKAGE_PIXMAPS_DIR="\"/usr/share/pixmaps\"" -DPACKAGE_LOCALE_DIR="\"/usr/share/locale\"" -pthread -I/usr/include/gtk-2.0 -I/usr/lib/arm-linux-gnueabihf/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gtk-2.0 -I/usr/include/libxml2 -I/usr/lib/arm-linux-gnueabihf/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/libglade-2.0 -pthread -I/usr/include/gconf/2 -I/usr/include/dbus-1.0 -I/usr/lib/arm-linux-gnueabihf/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libexif -I/usr/include/libxml2 -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c callbacks.c gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -DPACKAGE_DATA_DIR="\"/usr/share\"" -DPACKAGE_PIXMAPS_DIR="\"/usr/share/pixmaps\"" -DPACKAGE_LOCALE_DIR="\"/usr/share/locale\"" -pthread -I/usr/include/gtk-2.0 -I/usr/lib/arm-linux-gnueabihf/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gtk-2.0 -I/usr/include/libxml2 -I/usr/lib/arm-linux-gnueabihf/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/libglade-2.0 -pthread -I/usr/include/gconf/2 -I/usr/include/dbus-1.0 -I/usr/lib/arm-linux-gnueabihf/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libexif -I/usr/include/libxml2 -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c map_management.c gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -DPACKAGE_DATA_DIR="\"/usr/share\"" -DPACKAGE_PIXMAPS_DIR="\"/usr/share/pixmaps\"" -DPACKAGE_LOCALE_DIR="\"/usr/share/locale\"" -pthread -I/usr/include/gtk-2.0 -I/usr/lib/arm-linux-gnueabihf/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gtk-2.0 -I/usr/include/libxml2 -I/usr/lib/arm-linux-gnueabihf/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/libglade-2.0 -pthread -I/usr/include/gconf/2 -I/usr/include/dbus-1.0 -I/usr/lib/arm-linux-gnueabihf/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libexif -I/usr/include/libxml2 -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c globals.c gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -DPACKAGE_DATA_DIR="\"/usr/share\"" -DPACKAGE_PIXMAPS_DIR="\"/usr/share/pixmaps\"" -DPACKAGE_LOCALE_DIR="\"/usr/share/locale\"" -pthread -I/usr/include/gtk-2.0 -I/usr/lib/arm-linux-gnueabihf/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gtk-2.0 -I/usr/include/libxml2 -I/usr/lib/arm-linux-gnueabihf/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/libglade-2.0 -pthread -I/usr/include/gconf/2 -I/usr/include/dbus-1.0 -I/usr/lib/arm-linux-gnueabihf/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libexif -I/usr/include/libxml2 -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c converter.c gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -DPACKAGE_DATA_DIR="\"/usr/share\"" -DPACKAGE_PIXMAPS_DIR="\"/usr/share/pixmaps\"" -DPACKAGE_LOCALE_DIR="\"/usr/share/locale\"" -pthread -I/usr/include/gtk-2.0 -I/usr/lib/arm-linux-gnueabihf/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gtk-2.0 -I/usr/include/libxml2 -I/usr/lib/arm-linux-gnueabihf/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/libglade-2.0 -pthread -I/usr/include/gconf/2 -I/usr/include/dbus-1.0 -I/usr/lib/arm-linux-gnueabihf/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libexif -I/usr/include/libxml2 -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c gps_functions.c gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -DPACKAGE_DATA_DIR="\"/usr/share\"" -DPACKAGE_PIXMAPS_DIR="\"/usr/share/pixmaps\"" -DPACKAGE_LOCALE_DIR="\"/usr/share/locale\"" -pthread -I/usr/include/gtk-2.0 -I/usr/lib/arm-linux-gnueabihf/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gtk-2.0 -I/usr/include/libxml2 -I/usr/lib/arm-linux-gnueabihf/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/libglade-2.0 -pthread -I/usr/include/gconf/2 -I/usr/include/dbus-1.0 -I/usr/lib/arm-linux-gnueabihf/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libexif -I/usr/include/libxml2 -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c init.c gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -DPACKAGE_DATA_DIR="\"/usr/share\"" -DPACKAGE_PIXMAPS_DIR="\"/usr/share/pixmaps\"" -DPACKAGE_LOCALE_DIR="\"/usr/share/locale\"" -pthread -I/usr/include/gtk-2.0 -I/usr/lib/arm-linux-gnueabihf/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gtk-2.0 -I/usr/include/libxml2 -I/usr/lib/arm-linux-gnueabihf/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/libglade-2.0 -pthread -I/usr/include/gconf/2 -I/usr/include/dbus-1.0 -I/usr/lib/arm-linux-gnueabihf/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libexif -I/usr/include/libxml2 -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c tile_management.c gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -DPACKAGE_DATA_DIR="\"/usr/share\"" -DPACKAGE_PIXMAPS_DIR="\"/usr/share/pixmaps\"" -DPACKAGE_LOCALE_DIR="\"/usr/share/locale\"" -pthread -I/usr/include/gtk-2.0 -I/usr/lib/arm-linux-gnueabihf/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gtk-2.0 -I/usr/include/libxml2 -I/usr/lib/arm-linux-gnueabihf/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/libglade-2.0 -pthread -I/usr/include/gconf/2 -I/usr/include/dbus-1.0 -I/usr/lib/arm-linux-gnueabihf/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libexif -I/usr/include/libxml2 -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c friends.c gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -DPACKAGE_DATA_DIR="\"/usr/share\"" -DPACKAGE_PIXMAPS_DIR="\"/usr/share/pixmaps\"" -DPACKAGE_LOCALE_DIR="\"/usr/share/locale\"" -pthread -I/usr/include/gtk-2.0 -I/usr/lib/arm-linux-gnueabihf/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gtk-2.0 -I/usr/include/libxml2 -I/usr/lib/arm-linux-gnueabihf/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/libglade-2.0 -pthread -I/usr/include/gconf/2 -I/usr/include/dbus-1.0 -I/usr/lib/arm-linux-gnueabihf/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libexif -I/usr/include/libxml2 -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c geo_photos.c gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -DPACKAGE_DATA_DIR="\"/usr/share\"" -DPACKAGE_PIXMAPS_DIR="\"/usr/share/pixmaps\"" -DPACKAGE_LOCALE_DIR="\"/usr/share/locale\"" -pthread -I/usr/include/gtk-2.0 -I/usr/lib/arm-linux-gnueabihf/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gtk-2.0 -I/usr/include/libxml2 -I/usr/lib/arm-linux-gnueabihf/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/libglade-2.0 -pthread -I/usr/include/gconf/2 -I/usr/include/dbus-1.0 -I/usr/lib/arm-linux-gnueabihf/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libexif -I/usr/include/libxml2 -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c poi.c gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -DPACKAGE_DATA_DIR="\"/usr/share\"" -DPACKAGE_PIXMAPS_DIR="\"/usr/share/pixmaps\"" -DPACKAGE_LOCALE_DIR="\"/usr/share/locale\"" -pthread -I/usr/include/gtk-2.0 -I/usr/lib/arm-linux-gnueabihf/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gtk-2.0 -I/usr/include/libxml2 -I/usr/lib/arm-linux-gnueabihf/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/libglade-2.0 -pthread -I/usr/include/gconf/2 -I/usr/include/dbus-1.0 -I/usr/lib/arm-linux-gnueabihf/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libexif -I/usr/include/libxml2 -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c util.c gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -DPACKAGE_DATA_DIR="\"/usr/share\"" -DPACKAGE_PIXMAPS_DIR="\"/usr/share/pixmaps\"" -DPACKAGE_LOCALE_DIR="\"/usr/share/locale\"" -pthread -I/usr/include/gtk-2.0 -I/usr/lib/arm-linux-gnueabihf/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gtk-2.0 -I/usr/include/libxml2 -I/usr/lib/arm-linux-gnueabihf/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/libglade-2.0 -pthread -I/usr/include/gconf/2 -I/usr/include/dbus-1.0 -I/usr/lib/arm-linux-gnueabihf/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libexif -I/usr/include/libxml2 -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c wp.c gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -DPACKAGE_DATA_DIR="\"/usr/share\"" -DPACKAGE_PIXMAPS_DIR="\"/usr/share/pixmaps\"" -DPACKAGE_LOCALE_DIR="\"/usr/share/locale\"" -pthread -I/usr/include/gtk-2.0 -I/usr/lib/arm-linux-gnueabihf/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gtk-2.0 -I/usr/include/libxml2 -I/usr/lib/arm-linux-gnueabihf/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/libglade-2.0 -pthread -I/usr/include/gconf/2 -I/usr/include/dbus-1.0 -I/usr/lib/arm-linux-gnueabihf/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libexif -I/usr/include/libxml2 -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c tracks.c gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -DPACKAGE_DATA_DIR="\"/usr/share\"" -DPACKAGE_PIXMAPS_DIR="\"/usr/share/pixmaps\"" -DPACKAGE_LOCALE_DIR="\"/usr/share/locale\"" -pthread -I/usr/include/gtk-2.0 -I/usr/lib/arm-linux-gnueabihf/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gtk-2.0 -I/usr/include/libxml2 -I/usr/lib/arm-linux-gnueabihf/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/libglade-2.0 -pthread -I/usr/include/gconf/2 -I/usr/include/dbus-1.0 -I/usr/lib/arm-linux-gnueabihf/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libexif -I/usr/include/libxml2 -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c exif.c gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -DPACKAGE_DATA_DIR="\"/usr/share\"" -DPACKAGE_PIXMAPS_DIR="\"/usr/share/pixmaps\"" -DPACKAGE_LOCALE_DIR="\"/usr/share/locale\"" -pthread -I/usr/include/gtk-2.0 -I/usr/lib/arm-linux-gnueabihf/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gtk-2.0 -I/usr/include/libxml2 -I/usr/lib/arm-linux-gnueabihf/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/libglade-2.0 -pthread -I/usr/include/gconf/2 -I/usr/include/dbus-1.0 -I/usr/lib/arm-linux-gnueabihf/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/libexif -I/usr/include/libxml2 -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c hrm_functions.c /bin/bash ../libtool --tag=CC --mode=link gcc -std=gnu99 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -export-dynamic -Wl,-z,relro -o foxtrotgps support.o main.o interface.o callbacks.o map_management.o globals.o converter.o gps_functions.o init.o tile_management.o friends.o geo_photos.o poi.o util.o wp.o tracks.o exif.o hrm_functions.o -pthread -lgtk-x11-2.0 -latk-1.0 -lgio-2.0 -lpangoft2-1.0 -lfreetype -lfontconfig -lgdk-x11-2.0 -lpangocairo-1.0 -lgdk_pixbuf-2.0 -lpango-1.0 -lcairo -lgobject-2.0 -lgthread-2.0 -lrt -lglib-2.0 -lglade-2.0 -lgtk-x11-2.0 -lxml2 -lgdk-x11-2.0 -latk-1.0 -lgio-2.0 -lpangoft2-1.0 -lpangocairo-1.0 -lgdk_pixbuf-2.0 -lcairo -lpango-1.0 -lfreetype -lfontconfig -lgobject-2.0 -lglib-2.0 -lgconf-2 -lglib-2.0 -lcurl -lsqlite3 -lexif -lxml2 -L/usr/usr/lib/arm-linux-gnueabihf -lgps -lbluetooth -lm libtool: link: gcc -std=gnu99 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wl,-z -Wl,relro -o foxtrotgps support.o main.o interface.o callbacks.o map_management.o globals.o converter.o gps_functions.o init.o tile_management.o friends.o geo_photos.o poi.o util.o wp.o tracks.o exif.o hrm_functions.o -pthread -Wl,--export-dynamic -lgthread-2.0 -lrt /usr/lib/libglade-2.0.so -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgio-2.0 -lpangoft2-1.0 -lpangocairo-1.0 -lgdk_pixbuf-2.0 /usr/lib/arm-linux-gnueabihf/libcairo.so -lpango-1.0 /usr/lib/arm-linux-gnueabihf/libfreetype.so -lfontconfig -lgobject-2.0 -lgconf-2 -lglib-2.0 /usr/lib/arm-linux-gnueabihf/libcurl-gnutls.so /usr/lib/arm-linux-gnueabihf/libsqlite3.so -lexif -lxml2 -L/usr/usr/lib/arm-linux-gnueabihf -lgps -lbluetooth -lm -pthread make[3]: Leaving directory `/«PKGBUILDDIR»/src' Making all in pixmaps make[3]: Entering directory `/«PKGBUILDDIR»/pixmaps' make[3]: Nothing to be done for `all'. make[3]: Leaving directory `/«PKGBUILDDIR»/pixmaps' Making all in data make[3]: Entering directory `/«PKGBUILDDIR»/data' LC_ALL=C /usr/bin/intltool-merge -d -u -c ../po/.intltool-merge-cache ../po foxtrotgps.desktop.in foxtrotgps.desktop Generating and caching the translation database Merging translations into foxtrotgps.desktop. LC_ALL=C /usr/bin/intltool-merge -s -u -c ../po/.intltool-merge-cache ../po apps_foxtrotgps.schemas.in apps_foxtrotgps.schemas Found cached translation database Merging translations into apps_foxtrotgps.schemas. make[3]: Leaving directory `/«PKGBUILDDIR»/data' Making all in doc make[3]: Entering directory `/«PKGBUILDDIR»/doc' make[3]: Nothing to be done for `all'. make[3]: Leaving directory `/«PKGBUILDDIR»/doc' Making all in contrib make[3]: Entering directory `/«PKGBUILDDIR»/contrib' make[3]: Nothing to be done for `all'. make[3]: Leaving directory `/«PKGBUILDDIR»/contrib' make[3]: Entering directory `/«PKGBUILDDIR»' make[3]: Nothing to be done for `all-am'. make[3]: Leaving directory `/«PKGBUILDDIR»' make[2]: Leaving directory `/«PKGBUILDDIR»' make[1]: Leaving directory `/«PKGBUILDDIR»' debian/rules override_dh_auto_test make[1]: Entering directory `/«PKGBUILDDIR»' # disabled make[1]: Leaving directory `/«PKGBUILDDIR»' fakeroot debian/rules binary-arch dh binary-arch --with autotools_dev dh_testroot -a dh_prep -a dh_installdirs -a debian/rules override_dh_auto_install make[1]: Entering directory `/«PKGBUILDDIR»' dh_auto_install -- DESTDIR=/«PKGBUILDDIR»/debian/foxtrotgps make[2]: Entering directory `/«PKGBUILDDIR»' Making install in po make[3]: Entering directory `/«PKGBUILDDIR»/po' linguas="bg cs de es fi fr hu ru sk nl ja sr "; \ for lang in $linguas; do \ dir=/«PKGBUILDDIR»/debian/foxtrotgps/usr/share/locale/$lang/LC_MESSAGES; \ /bin/bash /«PKGBUILDDIR»/install-sh -d $dir; \ if test -r $lang.gmo; then \ /usr/bin/install -c -m 644 $lang.gmo $dir/foxtrotgps.mo; \ echo "installing $lang.gmo as $dir/foxtrotgps.mo"; \ else \ /usr/bin/install -c -m 644 ./$lang.gmo $dir/foxtrotgps.mo; \ echo "installing ./$lang.gmo as" \ "$dir/foxtrotgps.mo"; \ fi; \ if test -r $lang.gmo.m; then \ /usr/bin/install -c -m 644 $lang.gmo.m $dir/foxtrotgps.mo.m; \ echo "installing $lang.gmo.m as $dir/foxtrotgps.mo.m"; \ else \ if test -r ./$lang.gmo.m ; then \ /usr/bin/install -c -m 644 ./$lang.gmo.m \ $dir/foxtrotgps.mo.m; \ echo "installing ./$lang.gmo.m as" \ "$dir/foxtrotgps.mo.m"; \ else \ true; \ fi; \ fi; \ done installing bg.gmo as /«PKGBUILDDIR»/debian/foxtrotgps/usr/share/locale/bg/LC_MESSAGES/foxtrotgps.mo installing cs.gmo as /«PKGBUILDDIR»/debian/foxtrotgps/usr/share/locale/cs/LC_MESSAGES/foxtrotgps.mo installing de.gmo as /«PKGBUILDDIR»/debian/foxtrotgps/usr/share/locale/de/LC_MESSAGES/foxtrotgps.mo installing es.gmo as /«PKGBUILDDIR»/debian/foxtrotgps/usr/share/locale/es/LC_MESSAGES/foxtrotgps.mo installing fi.gmo as /«PKGBUILDDIR»/debian/foxtrotgps/usr/share/locale/fi/LC_MESSAGES/foxtrotgps.mo installing fr.gmo as /«PKGBUILDDIR»/debian/foxtrotgps/usr/share/locale/fr/LC_MESSAGES/foxtrotgps.mo installing hu.gmo as /«PKGBUILDDIR»/debian/foxtrotgps/usr/share/locale/hu/LC_MESSAGES/foxtrotgps.mo installing ru.gmo as /«PKGBUILDDIR»/debian/foxtrotgps/usr/share/locale/ru/LC_MESSAGES/foxtrotgps.mo installing sk.gmo as /«PKGBUILDDIR»/debian/foxtrotgps/usr/share/locale/sk/LC_MESSAGES/foxtrotgps.mo installing nl.gmo as /«PKGBUILDDIR»/debian/foxtrotgps/usr/share/locale/nl/LC_MESSAGES/foxtrotgps.mo installing ja.gmo as /«PKGBUILDDIR»/debian/foxtrotgps/usr/share/locale/ja/LC_MESSAGES/foxtrotgps.mo installing sr.gmo as /«PKGBUILDDIR»/debian/foxtrotgps/usr/share/locale/sr/LC_MESSAGES/foxtrotgps.mo make[3]: Leaving directory `/«PKGBUILDDIR»/po' Making install in src make[3]: Entering directory `/«PKGBUILDDIR»/src' make[4]: Entering directory `/«PKGBUILDDIR»/src' test -z "/usr/bin" || /bin/mkdir -p "/«PKGBUILDDIR»/debian/foxtrotgps/usr/bin" /bin/bash ../libtool --mode=install /usr/bin/install -c foxtrotgps '/«PKGBUILDDIR»/debian/foxtrotgps/usr/bin' libtool: install: /usr/bin/install -c foxtrotgps /«PKGBUILDDIR»/debian/foxtrotgps/usr/bin/foxtrotgps make[4]: Nothing to be done for `install-data-am'. make[4]: Leaving directory `/«PKGBUILDDIR»/src' make[3]: Leaving directory `/«PKGBUILDDIR»/src' Making install in pixmaps make[3]: Entering directory `/«PKGBUILDDIR»/pixmaps' make[4]: Entering directory `/«PKGBUILDDIR»/pixmaps' make[4]: Nothing to be done for `install-exec-am'. test -z "/usr/share/pixmaps" || /bin/mkdir -p "/«PKGBUILDDIR»/debian/foxtrotgps/usr/share/pixmaps" /usr/bin/install -c -m 644 foxtrotgps.png foxtrotgps-friend.png foxtrotgps-photo.png foxtrotgps-poi.png foxtrotgps-wp.png foxtrotgps-myposition.png '/«PKGBUILDDIR»/debian/foxtrotgps/usr/share/pixmaps' make[4]: Leaving directory `/«PKGBUILDDIR»/pixmaps' make[3]: Leaving directory `/«PKGBUILDDIR»/pixmaps' Making install in data make[3]: Entering directory `/«PKGBUILDDIR»/data' make[4]: Entering directory `/«PKGBUILDDIR»/data' make[4]: Nothing to be done for `install-exec-am'. GCONF_CONFIG_SOURCE=xml:merged:/etc/gconf/gconf.xml.defaults \ /usr/bin/gconftool-2 --makefile-install-rule apps_foxtrotgps.schemas Attached schema `/schemas/apps/foxtrotgps/gpsd_host' to key `/apps/foxtrotgps/gpsd_host' WARNING: failed to install schema `/schemas/apps/foxtrotgps/gpsd_host', locale `ja': Unable to store a value at key '/schemas/apps/foxtrotgps/gpsd_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/gpsd_host', locale `C': Unable to store a value at key '/schemas/apps/foxtrotgps/gpsd_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/gpsd_host', locale `fi': Unable to store a value at key '/schemas/apps/foxtrotgps/gpsd_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/gpsd_host', locale `cs': Unable to store a value at key '/schemas/apps/foxtrotgps/gpsd_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/gpsd_host', locale `sr': Unable to store a value at key '/schemas/apps/foxtrotgps/gpsd_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/gpsd_host', locale `es': Unable to store a value at key '/schemas/apps/foxtrotgps/gpsd_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/gpsd_host', locale `fr': Unable to store a value at key '/schemas/apps/foxtrotgps/gpsd_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/gpsd_host', locale `hu': Unable to store a value at key '/schemas/apps/foxtrotgps/gpsd_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/foxtrotgps/gpsd_port' to key `/apps/foxtrotgps/gpsd_port' WARNING: failed to install schema `/schemas/apps/foxtrotgps/gpsd_port', locale `ja': Unable to store a value at key '/schemas/apps/foxtrotgps/gpsd_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/gpsd_port', locale `C': Unable to store a value at key '/schemas/apps/foxtrotgps/gpsd_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/gpsd_port', locale `fi': Unable to store a value at key '/schemas/apps/foxtrotgps/gpsd_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/gpsd_port', locale `cs': Unable to store a value at key '/schemas/apps/foxtrotgps/gpsd_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/gpsd_port', locale `sr': Unable to store a value at key '/schemas/apps/foxtrotgps/gpsd_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/gpsd_port', locale `es': Unable to store a value at key '/schemas/apps/foxtrotgps/gpsd_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/gpsd_port', locale `fr': Unable to store a value at key '/schemas/apps/foxtrotgps/gpsd_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/gpsd_port', locale `hu': Unable to store a value at key '/schemas/apps/foxtrotgps/gpsd_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/foxtrotgps/latlon_unit' to key `/apps/foxtrotgps/latlon_unit' WARNING: failed to install schema `/schemas/apps/foxtrotgps/latlon_unit', locale `ja': Unable to store a value at key '/schemas/apps/foxtrotgps/latlon_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 WARNING: failed to install schema `/schemas/apps/foxtrotgps/latlon_unit', locale `C': Unable to store a value at key '/schemas/apps/foxtrotgps/latlon_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 WARNING: failed to install schema `/schemas/apps/foxtrotgps/latlon_unit', locale `fi': Unable to store a value at key '/schemas/apps/foxtrotgps/latlon_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 WARNING: failed to install schema `/schemas/apps/foxtrotgps/latlon_unit', locale `cs': Unable to store a value at key '/schemas/apps/foxtrotgps/latlon_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 WARNING: failed to install schema `/schemas/apps/foxtrotgps/latlon_unit', locale `sr': Unable to store a value at key '/schemas/apps/foxtrotgps/latlon_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 WARNING: failed to install schema `/schemas/apps/foxtrotgps/latlon_unit', locale `es': Unable to store a value at key '/schemas/apps/foxtrotgps/latlon_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 WARNING: failed to install schema `/schemas/apps/foxtrotgps/latlon_unit', locale `fr': Unable to store a value at key '/schemas/apps/foxtrotgps/latlon_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 WARNING: failed to install schema `/schemas/apps/foxtrotgps/latlon_unit', locale `hu': Unable to store a value at key '/schemas/apps/foxtrotgps/latlon_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/foxtrotgps/alt_unit' to key `/apps/foxtrotgps/alt_unit' WARNING: failed to install schema `/schemas/apps/foxtrotgps/alt_unit', locale `ja': Unable to store a value at key '/schemas/apps/foxtrotgps/alt_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 WARNING: failed to install schema `/schemas/apps/foxtrotgps/alt_unit', locale `C': Unable to store a value at key '/schemas/apps/foxtrotgps/alt_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 WARNING: failed to install schema `/schemas/apps/foxtrotgps/alt_unit', locale `fi': Unable to store a value at key '/schemas/apps/foxtrotgps/alt_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 WARNING: failed to install schema `/schemas/apps/foxtrotgps/alt_unit', locale `cs': Unable to store a value at key '/schemas/apps/foxtrotgps/alt_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 WARNING: failed to install schema `/schemas/apps/foxtrotgps/alt_unit', locale `sr': Unable to store a value at key '/schemas/apps/foxtrotgps/alt_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 WARNING: failed to install schema `/schemas/apps/foxtrotgps/alt_unit', locale `es': Unable to store a value at key '/schemas/apps/foxtrotgps/alt_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 WARNING: failed to install schema `/schemas/apps/foxtrotgps/alt_unit', locale `fr': Unable to store a value at key '/schemas/apps/foxtrotgps/alt_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 WARNING: failed to install schema `/schemas/apps/foxtrotgps/alt_unit', locale `hu': Unable to store a value at key '/schemas/apps/foxtrotgps/alt_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/foxtrotgps/speed_unit' to key `/apps/foxtrotgps/speed_unit' WARNING: failed to install schema `/schemas/apps/foxtrotgps/speed_unit', locale `ja': Unable to store a value at key '/schemas/apps/foxtrotgps/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 WARNING: failed to install schema `/schemas/apps/foxtrotgps/speed_unit', locale `C': Unable to store a value at key '/schemas/apps/foxtrotgps/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 WARNING: failed to install schema `/schemas/apps/foxtrotgps/speed_unit', locale `fi': Unable to store a value at key '/schemas/apps/foxtrotgps/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 WARNING: failed to install schema `/schemas/apps/foxtrotgps/speed_unit', locale `cs': Unable to store a value at key '/schemas/apps/foxtrotgps/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 WARNING: failed to install schema `/schemas/apps/foxtrotgps/speed_unit', locale `sr': Unable to store a value at key '/schemas/apps/foxtrotgps/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 WARNING: failed to install schema `/schemas/apps/foxtrotgps/speed_unit', locale `es': Unable to store a value at key '/schemas/apps/foxtrotgps/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 WARNING: failed to install schema `/schemas/apps/foxtrotgps/speed_unit', locale `fr': Unable to store a value at key '/schemas/apps/foxtrotgps/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 WARNING: failed to install schema `/schemas/apps/foxtrotgps/speed_unit', locale `hu': Unable to store a value at key '/schemas/apps/foxtrotgps/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 Attached schema `/schemas/apps/foxtrotgps/repo_name' to key `/apps/foxtrotgps/repo_name' WARNING: failed to install schema `/schemas/apps/foxtrotgps/repo_name', locale `ja': Unable to store a value at key '/schemas/apps/foxtrotgps/repo_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 WARNING: failed to install schema `/schemas/apps/foxtrotgps/repo_name', locale `C': Unable to store a value at key '/schemas/apps/foxtrotgps/repo_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 WARNING: failed to install schema `/schemas/apps/foxtrotgps/repo_name', locale `fi': Unable to store a value at key '/schemas/apps/foxtrotgps/repo_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 WARNING: failed to install schema `/schemas/apps/foxtrotgps/repo_name', locale `cs': Unable to store a value at key '/schemas/apps/foxtrotgps/repo_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 WARNING: failed to install schema `/schemas/apps/foxtrotgps/repo_name', locale `sr': Unable to store a value at key '/schemas/apps/foxtrotgps/repo_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 WARNING: failed to install schema `/schemas/apps/foxtrotgps/repo_name', locale `es': Unable to store a value at key '/schemas/apps/foxtrotgps/repo_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 WARNING: failed to install schema `/schemas/apps/foxtrotgps/repo_name', locale `fr': Unable to store a value at key '/schemas/apps/foxtrotgps/repo_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 WARNING: failed to install schema `/schemas/apps/foxtrotgps/repo_name', locale `hu': Unable to store a value at key '/schemas/apps/foxtrotgps/repo_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/foxtrotgps/repos' to key `/apps/foxtrotgps/repos' WARNING: failed to install schema `/schemas/apps/foxtrotgps/repos', locale `ja': Unable to store a value at key '/schemas/apps/foxtrotgps/repos', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/repos', locale `C': Unable to store a value at key '/schemas/apps/foxtrotgps/repos', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/repos', locale `fi': Unable to store a value at key '/schemas/apps/foxtrotgps/repos', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/repos', locale `cs': Unable to store a value at key '/schemas/apps/foxtrotgps/repos', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/repos', locale `sr': Unable to store a value at key '/schemas/apps/foxtrotgps/repos', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/repos', locale `es': Unable to store a value at key '/schemas/apps/foxtrotgps/repos', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/repos', locale `fr': Unable to store a value at key '/schemas/apps/foxtrotgps/repos', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/repos', locale `hu': Unable to store a value at key '/schemas/apps/foxtrotgps/repos', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/foxtrotgps/auto_download' to key `/apps/foxtrotgps/auto_download' WARNING: failed to install schema `/schemas/apps/foxtrotgps/auto_download', locale `ja': Unable to store a value at key '/schemas/apps/foxtrotgps/auto_download', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/auto_download', locale `C': Unable to store a value at key '/schemas/apps/foxtrotgps/auto_download', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/auto_download', locale `fi': Unable to store a value at key '/schemas/apps/foxtrotgps/auto_download', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/auto_download', locale `cs': Unable to store a value at key '/schemas/apps/foxtrotgps/auto_download', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/auto_download', locale `sr': Unable to store a value at key '/schemas/apps/foxtrotgps/auto_download', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/auto_download', locale `es': Unable to store a value at key '/schemas/apps/foxtrotgps/auto_download', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/auto_download', locale `fr': Unable to store a value at key '/schemas/apps/foxtrotgps/auto_download', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/auto_download', locale `hu': Unable to store a value at key '/schemas/apps/foxtrotgps/auto_download', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/foxtrotgps/no_redownload' to key `/apps/foxtrotgps/no_redownload' WARNING: failed to install schema `/schemas/apps/foxtrotgps/no_redownload', locale `ja': Unable to store a value at key '/schemas/apps/foxtrotgps/no_redownload', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/no_redownload', locale `C': Unable to store a value at key '/schemas/apps/foxtrotgps/no_redownload', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/no_redownload', locale `fi': Unable to store a value at key '/schemas/apps/foxtrotgps/no_redownload', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/no_redownload', locale `cs': Unable to store a value at key '/schemas/apps/foxtrotgps/no_redownload', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/no_redownload', locale `sr': Unable to store a value at key '/schemas/apps/foxtrotgps/no_redownload', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/no_redownload', locale `es': Unable to store a value at key '/schemas/apps/foxtrotgps/no_redownload', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/no_redownload', locale `fr': Unable to store a value at key '/schemas/apps/foxtrotgps/no_redownload', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/no_redownload', locale `hu': Unable to store a value at key '/schemas/apps/foxtrotgps/no_redownload', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/foxtrotgps/tracklog_on' to key `/apps/foxtrotgps/tracklog_on' WARNING: failed to install schema `/schemas/apps/foxtrotgps/tracklog_on', locale `ja': Unable to store a value at key '/schemas/apps/foxtrotgps/tracklog_on', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/tracklog_on', locale `C': Unable to store a value at key '/schemas/apps/foxtrotgps/tracklog_on', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/tracklog_on', locale `fi': Unable to store a value at key '/schemas/apps/foxtrotgps/tracklog_on', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/tracklog_on', locale `cs': Unable to store a value at key '/schemas/apps/foxtrotgps/tracklog_on', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/tracklog_on', locale `sr': Unable to store a value at key '/schemas/apps/foxtrotgps/tracklog_on', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/tracklog_on', locale `es': Unable to store a value at key '/schemas/apps/foxtrotgps/tracklog_on', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/tracklog_on', locale `fr': Unable to store a value at key '/schemas/apps/foxtrotgps/tracklog_on', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/tracklog_on', locale `hu': Unable to store a value at key '/schemas/apps/foxtrotgps/tracklog_on', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/foxtrotgps/track_dir' to key `/apps/foxtrotgps/track_dir' WARNING: failed to install schema `/schemas/apps/foxtrotgps/track_dir', locale `ja': Unable to store a value at key '/schemas/apps/foxtrotgps/track_dir', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/track_dir', locale `C': Unable to store a value at key '/schemas/apps/foxtrotgps/track_dir', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/track_dir', locale `fi': Unable to store a value at key '/schemas/apps/foxtrotgps/track_dir', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/track_dir', locale `cs': Unable to store a value at key '/schemas/apps/foxtrotgps/track_dir', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/track_dir', locale `sr': Unable to store a value at key '/schemas/apps/foxtrotgps/track_dir', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/track_dir', locale `es': Unable to store a value at key '/schemas/apps/foxtrotgps/track_dir', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/track_dir', locale `fr': Unable to store a value at key '/schemas/apps/foxtrotgps/track_dir', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/track_dir', locale `hu': Unable to store a value at key '/schemas/apps/foxtrotgps/track_dir', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/foxtrotgps/global_x' to key `/apps/foxtrotgps/global_x' WARNING: failed to install schema `/schemas/apps/foxtrotgps/global_x', locale `ja': Unable to store a value at key '/schemas/apps/foxtrotgps/global_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 WARNING: failed to install schema `/schemas/apps/foxtrotgps/global_x', locale `C': Unable to store a value at key '/schemas/apps/foxtrotgps/global_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 WARNING: failed to install schema `/schemas/apps/foxtrotgps/global_x', locale `fi': Unable to store a value at key '/schemas/apps/foxtrotgps/global_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 WARNING: failed to install schema `/schemas/apps/foxtrotgps/global_x', locale `cs': Unable to store a value at key '/schemas/apps/foxtrotgps/global_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 WARNING: failed to install schema `/schemas/apps/foxtrotgps/global_x', locale `sr': Unable to store a value at key '/schemas/apps/foxtrotgps/global_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 WARNING: failed to install schema `/schemas/apps/foxtrotgps/global_x', locale `es': Unable to store a value at key '/schemas/apps/foxtrotgps/global_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 WARNING: failed to install schema `/schemas/apps/foxtrotgps/global_x', locale `fr': Unable to store a value at key '/schemas/apps/foxtrotgps/global_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 WARNING: failed to install schema `/schemas/apps/foxtrotgps/global_x', locale `hu': Unable to store a value at key '/schemas/apps/foxtrotgps/global_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/foxtrotgps/global_y' to key `/apps/foxtrotgps/global_y' WARNING: failed to install schema `/schemas/apps/foxtrotgps/global_y', locale `ja': Unable to store a value at key '/schemas/apps/foxtrotgps/global_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 WARNING: failed to install schema `/schemas/apps/foxtrotgps/global_y', locale `C': Unable to store a value at key '/schemas/apps/foxtrotgps/global_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 WARNING: failed to install schema `/schemas/apps/foxtrotgps/global_y', locale `fi': Unable to store a value at key '/schemas/apps/foxtrotgps/global_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 WARNING: failed to install schema `/schemas/apps/foxtrotgps/global_y', locale `cs': Unable to store a value at key '/schemas/apps/foxtrotgps/global_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 WARNING: failed to install schema `/schemas/apps/foxtrotgps/global_y', locale `sr': Unable to store a value at key '/schemas/apps/foxtrotgps/global_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 WARNING: failed to install schema `/schemas/apps/foxtrotgps/global_y', locale `es': Unable to store a value at key '/schemas/apps/foxtrotgps/global_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 WARNING: failed to install schema `/schemas/apps/foxtrotgps/global_y', locale `fr': Unable to store a value at key '/schemas/apps/foxtrotgps/global_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 WARNING: failed to install schema `/schemas/apps/foxtrotgps/global_y', locale `hu': Unable to store a value at key '/schemas/apps/foxtrotgps/global_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/foxtrotgps/global_zoom' to key `/apps/foxtrotgps/global_zoom' WARNING: failed to install schema `/schemas/apps/foxtrotgps/global_zoom', locale `ja': Unable to store a value at key '/schemas/apps/foxtrotgps/global_zoom', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/global_zoom', locale `C': Unable to store a value at key '/schemas/apps/foxtrotgps/global_zoom', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/global_zoom', locale `fi': Unable to store a value at key '/schemas/apps/foxtrotgps/global_zoom', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/global_zoom', locale `cs': Unable to store a value at key '/schemas/apps/foxtrotgps/global_zoom', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/global_zoom', locale `sr': Unable to store a value at key '/schemas/apps/foxtrotgps/global_zoom', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/global_zoom', locale `es': Unable to store a value at key '/schemas/apps/foxtrotgps/global_zoom', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/global_zoom', locale `fr': Unable to store a value at key '/schemas/apps/foxtrotgps/global_zoom', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/global_zoom', locale `hu': Unable to store a value at key '/schemas/apps/foxtrotgps/global_zoom', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/foxtrotgps/global_detail_zoom' to key `/apps/foxtrotgps/global_detail_zoom' WARNING: failed to install schema `/schemas/apps/foxtrotgps/global_detail_zoom', locale `ja': Unable to store a value at key '/schemas/apps/foxtrotgps/global_detail_zoom', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/global_detail_zoom', locale `C': Unable to store a value at key '/schemas/apps/foxtrotgps/global_detail_zoom', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/global_detail_zoom', locale `fi': Unable to store a value at key '/schemas/apps/foxtrotgps/global_detail_zoom', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/global_detail_zoom', locale `cs': Unable to store a value at key '/schemas/apps/foxtrotgps/global_detail_zoom', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/global_detail_zoom', locale `sr': Unable to store a value at key '/schemas/apps/foxtrotgps/global_detail_zoom', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/global_detail_zoom', locale `es': Unable to store a value at key '/schemas/apps/foxtrotgps/global_detail_zoom', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/global_detail_zoom', locale `fr': Unable to store a value at key '/schemas/apps/foxtrotgps/global_detail_zoom', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/global_detail_zoom', locale `hu': Unable to store a value at key '/schemas/apps/foxtrotgps/global_detail_zoom', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/foxtrotgps/myposition_lat' to key `/apps/foxtrotgps/myposition_lat' WARNING: failed to install schema `/schemas/apps/foxtrotgps/myposition_lat', locale `ja': Unable to store a value at key '/schemas/apps/foxtrotgps/myposition_lat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/myposition_lat', locale `C': Unable to store a value at key '/schemas/apps/foxtrotgps/myposition_lat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/myposition_lat', locale `fi': Unable to store a value at key '/schemas/apps/foxtrotgps/myposition_lat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/myposition_lat', locale `cs': Unable to store a value at key '/schemas/apps/foxtrotgps/myposition_lat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/myposition_lat', locale `sr': Unable to store a value at key '/schemas/apps/foxtrotgps/myposition_lat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/myposition_lat', locale `es': Unable to store a value at key '/schemas/apps/foxtrotgps/myposition_lat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/myposition_lat', locale `fr': Unable to store a value at key '/schemas/apps/foxtrotgps/myposition_lat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/myposition_lat', locale `hu': Unable to store a value at key '/schemas/apps/foxtrotgps/myposition_lat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/foxtrotgps/myposition_lon' to key `/apps/foxtrotgps/myposition_lon' WARNING: failed to install schema `/schemas/apps/foxtrotgps/myposition_lon', locale `ja': Unable to store a value at key '/schemas/apps/foxtrotgps/myposition_lon', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/myposition_lon', locale `C': Unable to store a value at key '/schemas/apps/foxtrotgps/myposition_lon', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/myposition_lon', locale `fi': Unable to store a value at key '/schemas/apps/foxtrotgps/myposition_lon', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/myposition_lon', locale `cs': Unable to store a value at key '/schemas/apps/foxtrotgps/myposition_lon', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/myposition_lon', locale `sr': Unable to store a value at key '/schemas/apps/foxtrotgps/myposition_lon', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/myposition_lon', locale `es': Unable to store a value at key '/schemas/apps/foxtrotgps/myposition_lon', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/myposition_lon', locale `fr': Unable to store a value at key '/schemas/apps/foxtrotgps/myposition_lon', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/myposition_lon', locale `hu': Unable to store a value at key '/schemas/apps/foxtrotgps/myposition_lon', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/foxtrotgps/fftimer_running' to key `/apps/foxtrotgps/fftimer_running' WARNING: failed to install schema `/schemas/apps/foxtrotgps/fftimer_running', locale `ja': Unable to store a value at key '/schemas/apps/foxtrotgps/fftimer_running', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/fftimer_running', locale `C': Unable to store a value at key '/schemas/apps/foxtrotgps/fftimer_running', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/fftimer_running', locale `fi': Unable to store a value at key '/schemas/apps/foxtrotgps/fftimer_running', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/fftimer_running', locale `cs': Unable to store a value at key '/schemas/apps/foxtrotgps/fftimer_running', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/fftimer_running', locale `sr': Unable to store a value at key '/schemas/apps/foxtrotgps/fftimer_running', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/fftimer_running', locale `es': Unable to store a value at key '/schemas/apps/foxtrotgps/fftimer_running', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/fftimer_running', locale `fr': Unable to store a value at key '/schemas/apps/foxtrotgps/fftimer_running', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/fftimer_running', locale `hu': Unable to store a value at key '/schemas/apps/foxtrotgps/fftimer_running', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/foxtrotgps/ffupdate_interval_minutes' to key `/apps/foxtrotgps/ffupdate_interval_minutes' WARNING: failed to install schema `/schemas/apps/foxtrotgps/ffupdate_interval_minutes', locale `ja': Unable to store a value at key '/schemas/apps/foxtrotgps/ffupdate_interval_minutes', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/ffupdate_interval_minutes', locale `C': Unable to store a value at key '/schemas/apps/foxtrotgps/ffupdate_interval_minutes', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/ffupdate_interval_minutes', locale `fi': Unable to store a value at key '/schemas/apps/foxtrotgps/ffupdate_interval_minutes', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/ffupdate_interval_minutes', locale `cs': Unable to store a value at key '/schemas/apps/foxtrotgps/ffupdate_interval_minutes', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/ffupdate_interval_minutes', locale `sr': Unable to store a value at key '/schemas/apps/foxtrotgps/ffupdate_interval_minutes', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/ffupdate_interval_minutes', locale `es': Unable to store a value at key '/schemas/apps/foxtrotgps/ffupdate_interval_minutes', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/ffupdate_interval_minutes', locale `fr': Unable to store a value at key '/schemas/apps/foxtrotgps/ffupdate_interval_minutes', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/ffupdate_interval_minutes', locale `hu': Unable to store a value at key '/schemas/apps/foxtrotgps/ffupdate_interval_minutes', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/foxtrotgps/me_msg' to key `/apps/foxtrotgps/me_msg' WARNING: failed to install schema `/schemas/apps/foxtrotgps/me_msg', locale `ja': Unable to store a value at key '/schemas/apps/foxtrotgps/me_msg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/me_msg', locale `C': Unable to store a value at key '/schemas/apps/foxtrotgps/me_msg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/me_msg', locale `fi': Unable to store a value at key '/schemas/apps/foxtrotgps/me_msg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/me_msg', locale `cs': Unable to store a value at key '/schemas/apps/foxtrotgps/me_msg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/me_msg', locale `sr': Unable to store a value at key '/schemas/apps/foxtrotgps/me_msg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/me_msg', locale `es': Unable to store a value at key '/schemas/apps/foxtrotgps/me_msg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/me_msg', locale `fr': Unable to store a value at key '/schemas/apps/foxtrotgps/me_msg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/me_msg', locale `hu': Unable to store a value at key '/schemas/apps/foxtrotgps/me_msg', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/foxtrotgps/nick' to key `/apps/foxtrotgps/nick' WARNING: failed to install schema `/schemas/apps/foxtrotgps/nick', locale `ja': Unable to store a value at key '/schemas/apps/foxtrotgps/nick', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/nick', locale `C': Unable to store a value at key '/schemas/apps/foxtrotgps/nick', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/nick', locale `fi': Unable to store a value at key '/schemas/apps/foxtrotgps/nick', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/nick', locale `cs': Unable to store a value at key '/schemas/apps/foxtrotgps/nick', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/nick', locale `sr': Unable to store a value at key '/schemas/apps/foxtrotgps/nick', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/nick', locale `es': Unable to store a value at key '/schemas/apps/foxtrotgps/nick', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/nick', locale `fr': Unable to store a value at key '/schemas/apps/foxtrotgps/nick', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/nick', locale `hu': Unable to store a value at key '/schemas/apps/foxtrotgps/nick', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/foxtrotgps/pass' to key `/apps/foxtrotgps/pass' WARNING: failed to install schema `/schemas/apps/foxtrotgps/pass', locale `ja': Unable to store a value at key '/schemas/apps/foxtrotgps/pass', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/pass', locale `C': Unable to store a value at key '/schemas/apps/foxtrotgps/pass', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/pass', locale `fi': Unable to store a value at key '/schemas/apps/foxtrotgps/pass', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/pass', locale `cs': Unable to store a value at key '/schemas/apps/foxtrotgps/pass', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/pass', locale `sr': Unable to store a value at key '/schemas/apps/foxtrotgps/pass', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/pass', locale `es': Unable to store a value at key '/schemas/apps/foxtrotgps/pass', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/pass', locale `fr': Unable to store a value at key '/schemas/apps/foxtrotgps/pass', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/pass', locale `hu': Unable to store a value at key '/schemas/apps/foxtrotgps/pass', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/foxtrotgps/geocode_correction' to key `/apps/foxtrotgps/geocode_correction' WARNING: failed to install schema `/schemas/apps/foxtrotgps/geocode_correction', locale `ja': Unable to store a value at key '/schemas/apps/foxtrotgps/geocode_correction', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/geocode_correction', locale `C': Unable to store a value at key '/schemas/apps/foxtrotgps/geocode_correction', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/geocode_correction', locale `fi': Unable to store a value at key '/schemas/apps/foxtrotgps/geocode_correction', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/geocode_correction', locale `cs': Unable to store a value at key '/schemas/apps/foxtrotgps/geocode_correction', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/geocode_correction', locale `sr': Unable to store a value at key '/schemas/apps/foxtrotgps/geocode_correction', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/geocode_correction', locale `es': Unable to store a value at key '/schemas/apps/foxtrotgps/geocode_correction', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/geocode_correction', locale `fr': Unable to store a value at key '/schemas/apps/foxtrotgps/geocode_correction', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/geocode_correction', locale `hu': Unable to store a value at key '/schemas/apps/foxtrotgps/geocode_correction', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/foxtrotgps/geocode_timezone' to key `/apps/foxtrotgps/geocode_timezone' WARNING: failed to install schema `/schemas/apps/foxtrotgps/geocode_timezone', locale `ja': Unable to store a value at key '/schemas/apps/foxtrotgps/geocode_timezone', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/geocode_timezone', locale `C': Unable to store a value at key '/schemas/apps/foxtrotgps/geocode_timezone', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/geocode_timezone', locale `fi': Unable to store a value at key '/schemas/apps/foxtrotgps/geocode_timezone', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/geocode_timezone', locale `cs': Unable to store a value at key '/schemas/apps/foxtrotgps/geocode_timezone', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/geocode_timezone', locale `sr': Unable to store a value at key '/schemas/apps/foxtrotgps/geocode_timezone', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/geocode_timezone', locale `es': Unable to store a value at key '/schemas/apps/foxtrotgps/geocode_timezone', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/geocode_timezone', locale `fr': Unable to store a value at key '/schemas/apps/foxtrotgps/geocode_timezone', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/geocode_timezone', locale `hu': Unable to store a value at key '/schemas/apps/foxtrotgps/geocode_timezone', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/foxtrotgps/hrm_bt_addr' to key `/apps/foxtrotgps/hrm_bt_addr' WARNING: failed to install schema `/schemas/apps/foxtrotgps/hrm_bt_addr', locale `ja': Unable to store a value at key '/schemas/apps/foxtrotgps/hrm_bt_addr', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/hrm_bt_addr', locale `C': Unable to store a value at key '/schemas/apps/foxtrotgps/hrm_bt_addr', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/hrm_bt_addr', locale `fi': Unable to store a value at key '/schemas/apps/foxtrotgps/hrm_bt_addr', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/hrm_bt_addr', locale `cs': Unable to store a value at key '/schemas/apps/foxtrotgps/hrm_bt_addr', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/hrm_bt_addr', locale `sr': Unable to store a value at key '/schemas/apps/foxtrotgps/hrm_bt_addr', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/hrm_bt_addr', locale `es': Unable to store a value at key '/schemas/apps/foxtrotgps/hrm_bt_addr', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/hrm_bt_addr', locale `fr': Unable to store a value at key '/schemas/apps/foxtrotgps/hrm_bt_addr', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/hrm_bt_addr', locale `hu': Unable to store a value at key '/schemas/apps/foxtrotgps/hrm_bt_addr', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/foxtrotgps/hrm_on' to key `/apps/foxtrotgps/hrm_on' WARNING: failed to install schema `/schemas/apps/foxtrotgps/hrm_on', locale `ja': Unable to store a value at key '/schemas/apps/foxtrotgps/hrm_on', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/hrm_on', locale `C': Unable to store a value at key '/schemas/apps/foxtrotgps/hrm_on', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/hrm_on', locale `fi': Unable to store a value at key '/schemas/apps/foxtrotgps/hrm_on', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/hrm_on', locale `cs': Unable to store a value at key '/schemas/apps/foxtrotgps/hrm_on', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/hrm_on', locale `sr': Unable to store a value at key '/schemas/apps/foxtrotgps/hrm_on', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/hrm_on', locale `es': Unable to store a value at key '/schemas/apps/foxtrotgps/hrm_on', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/hrm_on', locale `fr': Unable to store a value at key '/schemas/apps/foxtrotgps/hrm_on', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/foxtrotgps/hrm_on', locale `hu': Unable to store a value at key '/schemas/apps/foxtrotgps/hrm_on', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf test -z "/usr/share/foxtrotgps" || /bin/mkdir -p "/«PKGBUILDDIR»/debian/foxtrotgps/usr/share/foxtrotgps" /usr/bin/install -c -m 644 foxtrotgps.glade '/«PKGBUILDDIR»/debian/foxtrotgps/usr/share/foxtrotgps' test -z "/usr/share/applications" || /bin/mkdir -p "/«PKGBUILDDIR»/debian/foxtrotgps/usr/share/applications" /usr/bin/install -c -m 644 foxtrotgps.desktop '/«PKGBUILDDIR»/debian/foxtrotgps/usr/share/applications' test -z "/etc/gconf/schemas" || /bin/mkdir -p "/«PKGBUILDDIR»/debian/foxtrotgps/etc/gconf/schemas" /usr/bin/install -c -m 644 apps_foxtrotgps.schemas '/«PKGBUILDDIR»/debian/foxtrotgps/etc/gconf/schemas' make[4]: Leaving directory `/«PKGBUILDDIR»/data' make[3]: Leaving directory `/«PKGBUILDDIR»/data' Making install in doc make[3]: Entering directory `/«PKGBUILDDIR»/doc' make[4]: Entering directory `/«PKGBUILDDIR»/doc' make[4]: Nothing to be done for `install-exec-am'. test -z "/usr/share/man/man1" || /bin/mkdir -p "/«PKGBUILDDIR»/debian/foxtrotgps/usr/share/man/man1" /usr/bin/install -c -m 644 foxtrotgps.1 '/«PKGBUILDDIR»/debian/foxtrotgps/usr/share/man/man1' make[4]: Leaving directory `/«PKGBUILDDIR»/doc' make[3]: Leaving directory `/«PKGBUILDDIR»/doc' Making install in contrib make[3]: Entering directory `/«PKGBUILDDIR»/contrib' make[4]: Entering directory `/«PKGBUILDDIR»/contrib' test -z "/usr/bin" || /bin/mkdir -p "/«PKGBUILDDIR»/debian/foxtrotgps/usr/bin" /usr/bin/install -c convert2gpx convert2osm georss2foxtrotgps-poi poi2osm osb2foxtrot '/«PKGBUILDDIR»/debian/foxtrotgps/usr/bin' test -z "/usr/share/doc/foxtrotgps" || /bin/mkdir -p "/«PKGBUILDDIR»/debian/foxtrotgps/usr/share/doc/foxtrotgps" /usr/bin/install -c -m 644 README.osb2foxtrot '/«PKGBUILDDIR»/debian/foxtrotgps/usr/share/doc/foxtrotgps' test -z "/usr/share/man/man1" || /bin/mkdir -p "/«PKGBUILDDIR»/debian/foxtrotgps/usr/share/man/man1" /usr/bin/install -c -m 644 convert2gpx.1 convert2osm.1 '/«PKGBUILDDIR»/debian/foxtrotgps/usr/share/man/man1' make[4]: Leaving directory `/«PKGBUILDDIR»/contrib' make[3]: Leaving directory `/«PKGBUILDDIR»/contrib' make[3]: Entering directory `/«PKGBUILDDIR»' make[4]: Entering directory `/«PKGBUILDDIR»' make[4]: Nothing to be done for `install-exec-am'. test -z "/usr/share/doc/foxtrotgps" || /bin/mkdir -p "/«PKGBUILDDIR»/debian/foxtrotgps/usr/share/doc/foxtrotgps" /usr/bin/install -c -m 644 README COPYING AUTHORS ChangeLog INSTALL HACKING NEWS TODO '/«PKGBUILDDIR»/debian/foxtrotgps/usr/share/doc/foxtrotgps' make[4]: Leaving directory `/«PKGBUILDDIR»' make[3]: Leaving directory `/«PKGBUILDDIR»' make[2]: Leaving directory `/«PKGBUILDDIR»' # removing unused files rm -rf debian/foxtrotgps/usr/share/doc make[1]: Leaving directory `/«PKGBUILDDIR»' dh_install -a dh_installdocs -a dh_installchangelogs -a dh_installexamples -a dh_installman -a dh_installcatalogs -a dh_installcron -a dh_installdebconf -a dh_installemacsen -a dh_installifupdown -a dh_installinfo -a dh_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_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=foxtrotgps-dbg make[1]: Leaving directory `/«PKGBUILDDIR»' dh_makeshlibs -a dh_shlibdeps -a dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/foxtrotgps/usr/bin/foxtrotgps was not linked against libfontconfig.so.1 (it uses none of the library's symbols). dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/foxtrotgps/usr/bin/foxtrotgps was not linked against librt.so.1 (it uses none of the library's symbols). dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/foxtrotgps/usr/bin/foxtrotgps was not linked against libgio-2.0.so.0 (it uses none of the library's symbols). dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/foxtrotgps/usr/bin/foxtrotgps was not linked against libcairo.so.2 (it uses none of the library's symbols). dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/foxtrotgps/usr/bin/foxtrotgps was not linked against libgthread-2.0.so.0 (it uses none of the library's symbols). dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/foxtrotgps/usr/bin/foxtrotgps was not linked against libpangocairo-1.0.so.0 (it uses none of the library's symbols). dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/foxtrotgps/usr/bin/foxtrotgps was not linked against libfreetype.so.6 (it uses none of the library's symbols). dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/foxtrotgps/usr/bin/foxtrotgps was not linked against libpangoft2-1.0.so.0 (it uses none of the library's symbols). dh_installdeb -a dh_gencontrol -a dpkg-gencontrol: warning: package foxtrotgps: unused substitution variable ${perl:Depends} dh_md5sums -a debian/rules override_dh_builddeb make[1]: Entering directory `/«PKGBUILDDIR»' dh_builddeb -- -Zxz -z9 dpkg-deb: building package `foxtrotgps' in `../foxtrotgps_1.1.1-2_armhf.deb'. dpkg-deb: building package `foxtrotgps-dbg' in `../foxtrotgps-dbg_1.1.1-2_armhf.deb'. make[1]: Leaving directory `/«PKGBUILDDIR»' dpkg-genchanges -B -mbuildd >../foxtrotgps_1.1.1-2_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 foxtrotgps-1.1.1 dpkg-source: info: using options from foxtrotgps-1.1.1/debian/source/options: --compression=xz --compression-level=9 dpkg-buildpackage: binary only upload (no source included) ──────────────────────────────────────────────────────────────────────────────── Build finished at 20120710-0303 Finished ──────── I: Built successfully ┌──────────────────────────────────────────────────────────────────────────────┐ │ Changes │ └──────────────────────────────────────────────────────────────────────────────┘ foxtrotgps_1.1.1-2_armhf.changes: ───────────────────────────────── Format: 1.8 Date: Fri, 29 Jun 2012 15:55:47 +0200 Source: foxtrotgps Binary: foxtrotgps foxtrotgps-dbg Architecture: armhf Version: 1.1.1-2 Distribution: testing Urgency: low Maintainer: buildd Changed-By: Daniel Baumann Description: foxtrotgps - GTK+ mapping and GPS application foxtrotgps-dbg - GTK+ mapping and GPS application (debug) Changes: foxtrotgps (1.1.1-2) unstable; urgency=low . * Updating GPL boilerplate in copyright file. * Switching to xz compression. * Trimming lintian overrides. Checksums-Sha1: 2af2da330afb4241a2d9ef1d11912b23b0365f49 180626 foxtrotgps_1.1.1-2_armhf.deb aa7b8d0d65ae7802770fc0404a1b6586e1d245ab 214646 foxtrotgps-dbg_1.1.1-2_armhf.deb Checksums-Sha256: 05dbec4c8782adb7a17efb338d79c5a71347dcc34b1cfdc0da1d898d89808730 180626 foxtrotgps_1.1.1-2_armhf.deb 276451c8560e5d60b230b8fefa1edbde6e00edc56484651fadd820a36a8f7ae5 214646 foxtrotgps-dbg_1.1.1-2_armhf.deb Files: dff9be4351ee63ca5f83c53a4cbeb408 180626 comm optional foxtrotgps_1.1.1-2_armhf.deb 2c9625066d3caa891ce7a919bd245d61 214646 debug extra foxtrotgps-dbg_1.1.1-2_armhf.deb ┌──────────────────────────────────────────────────────────────────────────────┐ │ Package contents │ └──────────────────────────────────────────────────────────────────────────────┘ foxtrotgps_1.1.1-2_armhf.deb ──────────────────────────── new debian package, version 2.0. size 180626 bytes: control archive=1914 bytes. 872 bytes, 14 lines control 2581 bytes, 36 lines md5sums 185 bytes, 7 lines * postinst #!/bin/sh 160 bytes, 5 lines * postrm #!/bin/sh Package: foxtrotgps Version: 1.1.1-2 Architecture: armhf Maintainer: Daniel Baumann Installed-Size: 917 Depends: gconf2 (>= 2.28.1-2), gconf-service, libatk1.0-0 (>= 1.12.4), libbluetooth3 (>= 4.91), libc6 (>= 2.13-28), libcairo2 (>= 1.2.4), libcurl3-gnutls (>= 7.16.2), libexif12, libfontconfig1 (>= 2.9.0), libfreetype6 (>= 2.2.1), libgconf-2-4 (>= 2.31.1), libgdk-pixbuf2.0-0 (>= 2.22.0), libglade2-0 (>= 1:2.6.1), libglib2.0-0 (>= 2.31.8), libgps20 (>= 3.3), libgtk2.0-0 (>= 2.8.0), libpango1.0-0 (>= 1.14.0), libsqlite3-0 (>= 3.5.9), libxml2 (>= 2.7.4) Recommends: gpsd Suggests: python-beautifulsoup, python-feedparser Section: comm Priority: optional Homepage: http://www.foxtrotgps.org/ Description: GTK+ mapping and GPS application foxtrotGPS is a map and GPS application. By default, it uses maps from Openstreetmap. drwxr-xr-x root/root 0 2012-07-10 03:02 ./ drwxr-xr-x root/root 0 2012-07-10 03:02 ./usr/ drwxr-xr-x root/root 0 2012-07-10 03:02 ./usr/share/ drwxr-xr-x root/root 0 2012-07-10 03:02 ./usr/share/applications/ -rw-r--r-- root/root 988 2012-07-10 03:02 ./usr/share/applications/foxtrotgps.desktop drwxr-xr-x root/root 0 2012-07-10 03:02 ./usr/share/menu/ -rw-r--r-- root/root 322 2012-06-27 07:03 ./usr/share/menu/foxtrotgps drwxr-xr-x root/root 0 2012-07-10 03:02 ./usr/share/locale/ drwxr-xr-x root/root 0 2012-07-10 03:02 ./usr/share/locale/ru/ drwxr-xr-x root/root 0 2012-07-10 03:02 ./usr/share/locale/ru/LC_MESSAGES/ -rw-r--r-- root/root 4795 2012-07-10 03:02 ./usr/share/locale/ru/LC_MESSAGES/foxtrotgps.mo drwxr-xr-x root/root 0 2012-07-10 03:02 ./usr/share/locale/es/ drwxr-xr-x root/root 0 2012-07-10 03:02 ./usr/share/locale/es/LC_MESSAGES/ -rw-r--r-- root/root 25365 2012-07-10 03:02 ./usr/share/locale/es/LC_MESSAGES/foxtrotgps.mo drwxr-xr-x root/root 0 2012-07-10 03:02 ./usr/share/locale/hu/ drwxr-xr-x root/root 0 2012-07-10 03:02 ./usr/share/locale/hu/LC_MESSAGES/ -rw-r--r-- root/root 26071 2012-07-10 03:02 ./usr/share/locale/hu/LC_MESSAGES/foxtrotgps.mo drwxr-xr-x root/root 0 2012-07-10 03:02 ./usr/share/locale/cs/ drwxr-xr-x root/root 0 2012-07-10 03:02 ./usr/share/locale/cs/LC_MESSAGES/ -rw-r--r-- root/root 24117 2012-07-10 03:02 ./usr/share/locale/cs/LC_MESSAGES/foxtrotgps.mo drwxr-xr-x root/root 0 2012-07-10 03:02 ./usr/share/locale/fr/ drwxr-xr-x root/root 0 2012-07-10 03:02 ./usr/share/locale/fr/LC_MESSAGES/ -rw-r--r-- root/root 25569 2012-07-10 03:02 ./usr/share/locale/fr/LC_MESSAGES/foxtrotgps.mo drwxr-xr-x root/root 0 2012-07-10 03:02 ./usr/share/locale/ja/ drwxr-xr-x root/root 0 2012-07-10 03:02 ./usr/share/locale/ja/LC_MESSAGES/ -rw-r--r-- root/root 26755 2012-07-10 03:02 ./usr/share/locale/ja/LC_MESSAGES/foxtrotgps.mo drwxr-xr-x root/root 0 2012-07-10 03:02 ./usr/share/locale/sr/ drwxr-xr-x root/root 0 2012-07-10 03:02 ./usr/share/locale/sr/LC_MESSAGES/ -rw-r--r-- root/root 31088 2012-07-10 03:02 ./usr/share/locale/sr/LC_MESSAGES/foxtrotgps.mo drwxr-xr-x root/root 0 2012-07-10 03:02 ./usr/share/locale/de/ drwxr-xr-x root/root 0 2012-07-10 03:02 ./usr/share/locale/de/LC_MESSAGES/ -rw-r--r-- root/root 464 2012-07-10 03:02 ./usr/share/locale/de/LC_MESSAGES/foxtrotgps.mo drwxr-xr-x root/root 0 2012-07-10 03:02 ./usr/share/locale/fi/ drwxr-xr-x root/root 0 2012-07-10 03:02 ./usr/share/locale/fi/LC_MESSAGES/ -rw-r--r-- root/root 24951 2012-07-10 03:02 ./usr/share/locale/fi/LC_MESSAGES/foxtrotgps.mo drwxr-xr-x root/root 0 2012-07-10 03:02 ./usr/share/locale/bg/ drwxr-xr-x root/root 0 2012-07-10 03:02 ./usr/share/locale/bg/LC_MESSAGES/ -rw-r--r-- root/root 5654 2012-07-10 03:02 ./usr/share/locale/bg/LC_MESSAGES/foxtrotgps.mo drwxr-xr-x root/root 0 2012-07-10 03:02 ./usr/share/locale/nl/ drwxr-xr-x root/root 0 2012-07-10 03:02 ./usr/share/locale/nl/LC_MESSAGES/ -rw-r--r-- root/root 7237 2012-07-10 03:02 ./usr/share/locale/nl/LC_MESSAGES/foxtrotgps.mo drwxr-xr-x root/root 0 2012-07-10 03:02 ./usr/share/locale/sk/ drwxr-xr-x root/root 0 2012-07-10 03:02 ./usr/share/locale/sk/LC_MESSAGES/ -rw-r--r-- root/root 7216 2012-07-10 03:02 ./usr/share/locale/sk/LC_MESSAGES/foxtrotgps.mo drwxr-xr-x root/root 0 2012-07-10 03:02 ./usr/share/doc/ drwxr-xr-x root/root 0 2012-07-10 03:02 ./usr/share/doc/foxtrotgps/ -rw-r--r-- root/root 31981 2012-06-13 21:42 ./usr/share/doc/foxtrotgps/changelog.gz -rw-r--r-- root/root 3100 2012-06-29 07:41 ./usr/share/doc/foxtrotgps/changelog.Debian.gz -rw-r--r-- root/root 1905 2012-06-29 06:55 ./usr/share/doc/foxtrotgps/copyright drwxr-xr-x root/root 0 2012-07-10 03:02 ./usr/share/man/ drwxr-xr-x root/root 0 2012-07-10 03:02 ./usr/share/man/man1/ -rw-r--r-- root/root 1146 2012-07-10 03:02 ./usr/share/man/man1/foxtrotgps.1.gz -rw-r--r-- root/root 456 2012-07-10 03:02 ./usr/share/man/man1/convert2osm.1.gz -rw-r--r-- root/root 408 2012-07-10 03:02 ./usr/share/man/man1/convert2gpx.1.gz drwxr-xr-x root/root 0 2012-07-10 03:02 ./usr/share/lintian/ drwxr-xr-x root/root 0 2012-07-10 03:02 ./usr/share/lintian/overrides/ -rw-r--r-- root/root 44 2012-06-29 07:41 ./usr/share/lintian/overrides/foxtrotgps drwxr-xr-x root/root 0 2012-07-10 03:02 ./usr/share/foxtrotgps/ -rw-r--r-- root/root 285684 2012-07-10 03:02 ./usr/share/foxtrotgps/foxtrotgps.glade drwxr-xr-x root/root 0 2012-07-10 03:02 ./usr/share/pixmaps/ -rw-r--r-- root/root 7082 2012-06-27 07:03 ./usr/share/pixmaps/foxtrotgps.xpm -rw-r--r-- root/root 11317 2012-07-10 03:02 ./usr/share/pixmaps/foxtrotgps.png -rw-r--r-- root/root 2308 2012-07-10 03:02 ./usr/share/pixmaps/foxtrotgps-myposition.png -rw-r--r-- root/root 2445 2012-07-10 03:02 ./usr/share/pixmaps/foxtrotgps-wp.png -rw-r--r-- root/root 1093 2012-07-10 03:02 ./usr/share/pixmaps/foxtrotgps-poi.png -rw-r--r-- root/root 1231 2012-07-10 03:02 ./usr/share/pixmaps/foxtrotgps-photo.png -rw-r--r-- root/root 2842 2012-07-10 03:02 ./usr/share/pixmaps/foxtrotgps-friend.png drwxr-xr-x root/root 0 2012-07-10 03:02 ./usr/share/gconf/ drwxr-xr-x root/root 0 2012-07-10 03:02 ./usr/share/gconf/schemas/ -rw-r--r-- root/root 28338 2012-07-10 03:02 ./usr/share/gconf/schemas/apps_foxtrotgps.schemas drwxr-xr-x root/root 0 2012-07-10 03:02 ./usr/bin/ -rwxr-xr-x root/root 2042 2012-07-10 03:02 ./usr/bin/poi2osm -rwxr-xr-x root/root 3461 2012-07-10 03:02 ./usr/bin/convert2osm -rwxr-xr-x root/root 1535 2012-07-10 03:02 ./usr/bin/osb2foxtrot -rwxr-xr-x root/root 801 2012-07-10 03:02 ./usr/bin/convert2gpx -rwxr-xr-x root/root 2986 2012-07-10 03:02 ./usr/bin/georss2foxtrotgps-poi -rwxr-xr-x root/root 162868 2012-07-10 03:02 ./usr/bin/foxtrotgps foxtrotgps-dbg_1.1.1-2_armhf.deb ──────────────────────────────── new debian package, version 2.0. size 214646 bytes: control archive=642 bytes. 461 bytes, 15 lines control 338 bytes, 4 lines md5sums Package: foxtrotgps-dbg Source: foxtrotgps Version: 1.1.1-2 Architecture: armhf Maintainer: Daniel Baumann Installed-Size: 290 Depends: foxtrotgps (= 1.1.1-2) Section: debug Priority: extra Homepage: http://www.foxtrotgps.org/ Description: GTK+ mapping and GPS application (debug) foxtrotGPS is a map and GPS application. By default, it uses maps from Openstreetmap. . This package contains the debugging symbols. drwxr-xr-x root/root 0 2012-07-10 03:02 ./ drwxr-xr-x root/root 0 2012-07-10 03:02 ./usr/ drwxr-xr-x root/root 0 2012-07-10 03:02 ./usr/lib/ drwxr-xr-x root/root 0 2012-07-10 03:02 ./usr/lib/debug/ drwxr-xr-x root/root 0 2012-07-10 03:02 ./usr/lib/debug/.build-id/ drwxr-xr-x root/root 0 2012-07-10 03:02 ./usr/lib/debug/.build-id/87/ -rw-r--r-- root/root 218509 2012-07-10 03:02 ./usr/lib/debug/.build-id/87/fbc2cc614d988ca269d964650363a48040f735.debug drwxr-xr-x root/root 0 2012-07-10 03:02 ./usr/share/ drwxr-xr-x root/root 0 2012-07-10 03:02 ./usr/share/doc/ drwxr-xr-x root/root 0 2012-07-10 03:02 ./usr/share/doc/foxtrotgps-dbg/ -rw-r--r-- root/root 31981 2012-06-13 21:42 ./usr/share/doc/foxtrotgps-dbg/changelog.gz -rw-r--r-- root/root 3100 2012-06-29 07:41 ./usr/share/doc/foxtrotgps-dbg/changelog.Debian.gz -rw-r--r-- root/root 1905 2012-06-29 06:55 ./usr/share/doc/foxtrotgps-dbg/copyright ┌──────────────────────────────────────────────────────────────────────────────┐ │ Post Build │ └──────────────────────────────────────────────────────────────────────────────┘ ┌──────────────────────────────────────────────────────────────────────────────┐ │ Cleanup │ └──────────────────────────────────────────────────────────────────────────────┘ Purging /«BUILDDIR» Reading package lists... Building dependency tree... Reading state information... 0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded. Reading package lists... Building dependency tree... Reading state information... The following packages will be REMOVED: adduser* autoconf* automake* autotools-dev* bsdmainutils* ca-certificates* comerr-dev* dbus* dbus-x11* dconf-gsettings-backend* dconf-service* debhelper* 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-pango-1.0* gir1.2-soup-2.4* glib-networking* glib-networking-common* glib-networking-services* groff-base* gsettings-desktop-schemas* html2text* intltool* intltool-debian* krb5-multidev* libasprintf0c2* libatk1.0-0* libatk1.0-data* libatk1.0-dev* libavahi-client3* libavahi-common-data* libavahi-common3* libbluetooth-dev* libbluetooth3* libcairo-gobject2* libcairo-script-interpreter2* libcairo2* libcairo2-dev* libcap2* libcroco3* libcups2* libcurl3-gnutls* libcurl4-gnutls-dev* libdatrie1* libdbus-1-3* libdbus-1-dev* libdbus-glib-1-2* libdconf0* libelf1* libencode-locale-perl* libexif-dev* libexif12* libexpat1* libexpat1-dev* libffi5* libfile-listing-perl* libfontconfig1* libfontconfig1-dev* libfreetype6* libfreetype6-dev* libgconf-2-4* libgconf2-dev* libgcrypt11* libgcrypt11-dev* libgdk-pixbuf2.0-0* libgdk-pixbuf2.0-common* libgdk-pixbuf2.0-dev* libgettextpo0* libgirepository-1.0-1* libglade2-0* libglade2-dev* libglib2.0-0* libglib2.0-bin* libglib2.0-data* libglib2.0-dev* libgnome-keyring-common* libgnome-keyring0* libgnutls-dev* libgnutls-openssl27* libgnutls26* libgnutlsxx27* libgpg-error-dev* libgpg-error0* libgps-dev* libgps20* libgssapi-krb5-2* libgssrpc4* libgtk2.0-0* libgtk2.0-common* libgtk2.0-dev* libhtml-parser-perl* libhtml-tagset-perl* libhtml-tree-perl* libhttp-cookies-perl* libhttp-date-perl* libhttp-message-perl* libhttp-negotiate-perl* libice-dev* libice6* libidn11* libidn11-dev* libio-socket-ssl-perl* libjasper1* libjbig0* libjpeg8* libjs-jquery* libk5crypto3* libkadm5clnt-mit8* libkadm5srv-mit8* libkdb5-6* libkeyutils1* libkrb5-3* libkrb5-dev* libkrb5support0* libldap-2.4-2* libldap2-dev* liblwp-mediatypes-perl* liblwp-protocol-https-perl* libmagic1* libnet-http-perl* libnet-ssleay-perl* libp11-kit-dev* 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* librtmp-dev* librtmp0* libsasl2-2* libsm-dev* libsm6* libsoup-gnome2.4-1* libsoup2.4-1* libsoup2.4-dev* libsqlite3-0* libsqlite3-dev* libssh2-1* libssh2-1-dev* libssl1.0.0* libsystemd-login0* libtasn1-3* libtasn1-3-dev* libthai-data* libthai0* libtiff4* libunistring0* liburi-perl* libusb-1.0-0* libwww-perl* libwww-robotrules-perl* libx11-6* libx11-data* libx11-dev* libxau-dev* libxau6* libxcb-render0* libxcb-render0-dev* libxcb-shm0* libxcb-shm0-dev* libxcb1* libxcb1-dev* libxcomposite-dev* libxcomposite1* libxcursor-dev* libxcursor1* libxdamage-dev* libxdamage1* libxdmcp-dev* libxdmcp6* libxext-dev* libxext6* libxfixes-dev* libxfixes3* libxft-dev* libxft2* libxi-dev* libxi6* libxinerama-dev* libxinerama1* libxml-parser-perl* libxml2* libxml2-dev* libxml2-utils* libxrandr-dev* libxrandr2* libxrender-dev* libxrender1* m4* man-db* mime-support* netbase* openssl* pkg-config* po-debconf* psmisc* python* python-minimal* python2.7* python2.7-minimal* sbuild-build-depends-core-dummy* sbuild-build-depends-foxtrotgps-dummy* shared-mime-info* ttf-dejavu-core* 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-xext-dev* x11proto-xinerama-dev* xorg-sgml-doctools* xtrans-dev* zlib1g-dev* 0 upgraded, 0 newly installed, 239 to remove and 4 not upgraded. After this operation, 210 MB disk space will be freed. (Reading database ... 20245 files and directories currently installed.) Removing sbuild-build-depends-foxtrotgps-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 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 libcurl4-gnutls-dev ... Removing libkrb5-dev ... Removing krb5-multidev ... Removing comerr-dev ... 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 file ... Removing libglade2-dev ... Removing libgtk2.0-dev ... Removing libpango1.0-dev ... Removing libglade2-0 ... Purging configuration files for libglade2-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 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 libgdk-pixbuf2.0-dev ... Removing gir1.2-gdkpixbuf-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 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 libbluetooth-dev ... Removing libgps-dev ... Removing libgps20:armhf ... Purging configuration files for libgps20:armhf ... Removing libbluetooth3:armhf ... Purging configuration files for libbluetooth3:armhf ... 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 libcurl3-gnutls:armhf ... Purging configuration files for libcurl3-gnutls: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 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 libglib2.0-dev ... Removing libglib2.0-bin ... Purging configuration files for libglib2.0-bin ... Removing libelf1 ... Purging configuration files for libelf1 ... Removing libexif-dev ... Removing libexif12:armhf ... Purging configuration files for libexif12:armhf ... Removing python ... Purging configuration files for python ... Removing python2.7 ... Purging configuration files for python2.7 ... Removing libexpat1-dev ... Removing libexpat1:armhf ... Purging configuration files for libexpat1:armhf ... Removing shared-mime-info ... Purging configuration files for shared-mime-info ... Removing libidn11-dev ... Removing pkg-config ... 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 libssh2-1-dev ... Removing libssh2-1:armhf ... Purging configuration files for libssh2-1:armhf ... Removing librtmp-dev ... Removing librtmp0:armhf ... Purging configuration files for librtmp0:armhf ... Removing libldap2-dev:armhf ... Removing libldap-2.4-2:armhf ... Purging configuration files for libldap-2.4-2:armhf ... Removing libgnutls-dev ... Removing libgnutlsxx27:armhf ... Purging configuration files for libgnutlsxx27:armhf ... Removing libgnutls-openssl27:armhf ... Purging configuration files for libgnutls-openssl27:armhf ... Removing libgnutls26:armhf ... Purging configuration files for libgnutls26:armhf ... Removing libgcrypt11-dev ... Removing libgcrypt11:armhf ... Purging configuration files for libgcrypt11:armhf ... Removing libgdk-pixbuf2.0-common ... Removing libgettextpo0:armhf ... Removing libglib2.0-data ... Removing libgnome-keyring-common ... Removing libgpg-error-dev ... Removing libgpg-error0:armhf ... Purging configuration files for libgpg-error0:armhf ... Removing libkadm5srv-mit8:armhf ... Purging configuration files for libkadm5srv-mit8:armhf ... Removing libkadm5clnt-mit8:armhf ... Purging configuration files for libkadm5clnt-mit8:armhf ... Removing libkdb5-6:armhf ... Purging configuration files for libkdb5-6:armhf ... Removing libgssrpc4:armhf ... Purging configuration files for libgssrpc4: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 libsm-dev:armhf ... Removing libice-dev:armhf ... Removing libsm6:armhf ... Purging configuration files for libsm6:armhf ... Removing libice6:armhf ... Purging configuration files for libice6:armhf ... Removing libidn11:armhf ... Purging configuration files for libidn11: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 libp11-kit-dev ... 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 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 ... dpkg: warning: while removing libsasl2-2:armhf, directory '/usr/lib/sasl2' not empty so not removed. Removing libsqlite3-dev ... Removing libsqlite3-0:armhf ... Purging configuration files for libsqlite3-0:armhf ... Removing python-minimal ... Removing python2.7-minimal ... Purging configuration files for python2.7-minimal ... Removing libtasn1-3-dev ... Removing libtasn1-3:armhf ... Purging configuration files for libtasn1-3:armhf ... Removing libthai-data ... Removing libunistring0:armhf ... Purging configuration files for libunistring0:armhf ... Removing libusb-1.0-0:armhf ... Purging configuration files for libusb-1.0-0: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-6:armhf ... Purging configuration files for libx11-6:armhf ... Removing libx11-data ... Removing libxau-dev:armhf ... Removing libxcb-shm0:armhf ... Purging configuration files for libxcb-shm0:armhf ... Removing libxcb-render0:armhf ... Purging configuration files for libxcb-render0: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 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-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 │ └──────────────────────────────────────────────────────────────────────────────┘ Build Architecture: armhf Build-Space: 7248 Build-Time: 179 Distribution: testing Host Architecture: armhf Install-Time: 374 Job: foxtrotgps_1.1.1-2 Machine Architecture: armhf Package: foxtrotgps Package-Time: 573 Source-Version: 1.1.1-2 Space: 7248 Status: successful Version: 1.1.1-2 ──────────────────────────────────────────────────────────────────────────────── Finished at 20120710-0303 Build needed 00:09:33, 7248k disc space